SRDB ID |
|
Synopsis |
|
Date |
21990 |
|
hpost failure - couldn't determine current bus config |
|
15 Mar 2000 |
On running hpost on a newly created domain, it fails as follows :-
% hpost -l127
Opening SNMP server library...
Significant contents of /export/home/ssp/.postrc:
#
logfile
Reading centerplane asics to obtain bus configuration...
Failure to determine current centerplane bus configuration.
Dumping centerplane state to file...
System state (mask=30000) dumped to:
/var/opt/SUNWssp/adm/testdm/xfstate.0310.1100.47
Exitcode = 79: Not -C, couldn't determine current bus config
POST (level=127, verbose=20) execution time 2:09
SOLUTION SUMMARY:
The solution is to run the hpost command with the -C option.
The reason for the failure is that the centerplane of the
E10K has never been configured. If a bringup was run instead
of hpost, this would automatically configure the backplane for you.
From the man page of hpost :
-C Do the initial configuration of the centerplane.
If -C is not invoked, hpost assumes that one or
more other domains in the same physical platform
have already been configured and are running.
hpost probes the centerplane to determine the bus
configuration, the only configuration it consid-
ers. If hpost cannot determine a valid confi-
guration from this probe, it immediately fails.
Therefore the command :
% hpost -l127 -C
Should work fine. After the first hpost with a -C, you can run hpost
against any subsequent domains which are built.
CAUTION : Running hpost -C on a platform which has running domains
will cause these domains to fail/panic/arbstop. hpost -C should
never be run on a platform which already has running domains.
SUBMITTER: Cormac Hogan
APPLIES TO: Hardware/Ultra Enterprise/Servers/Enterprise 10000
ATTACHMENTS:
Copyright (c) 1997-2003 Sun Microsystems, Inc.