苏晓峥[joyson]

iSeries技术顾问资深系统顾问

现服役于紫光通用产品软件部

日志分类

2008-04-23 | System reference codes (B3xx)

标签：iseries src connection monitoring b2xx 参考代码

These error codes indicate a problem in the connection monitoring between the Hardware Management Console and a partition that is running on the managed system. The HMC posts these error codes into the error log in Service Focal Point but does not report them to the operating systems running on the managed system.

Use the following links to display the appropriate B3xx reference code table:

Table 1. (B301) Connection monitoring reference codes
Reference Code	Description/Action Perform all actions before exchanging Failing Items	Failing Item
B3010001	Hardware Management Console (HMC) or partition connection monitoring fault	NEXTLVL
B3010002	HMC or partition connection monitoring fault Perform the following steps: Verify the network between the HMC and the partition by pinging in both directions. Correct any problems that you detect. Reboot the HMC.	PTNNTWK
B3010004	HMC or partition connection monitoring fault	NEXTLVL
B3010012, B3010013, B3010019, B3010020, B3010023, B3010025, B3010026	HMC or partition connection monitoring fault	NEXTLVL
B3010027	HMC or partition connection monitoring fault Before using the entry in the Failing Items column, do the following: If you use short host names for the HMC and the partitions, ensure that you have correctly set up the short host names. For more information, see the instructions in "Using Network Adapters to Communicate with Partitions" in the Hardware Management Console for pSeries® Installation and Operations Guide. Correct any problems that you find, then verify that you can ping in both directions between the HMC and the partitions. If you do not use short host names or if the previous step does not correct the problem, use the Failing Item column.	NEXTLVL
B3010029, B301002B, B301002C, B301002D	HMC or partition connection monitoring fault	NEXTLVL

Table 2. (B302) Connection monitoring reference codes
Reference Code	Description/Action Perform all actions before exchanging Failing Items	Failing Item
B3020001	Hardware Management Console (HMC) or partition connection monitoring fault Before using the entry in the Failing Items column, do the following: If you use short host names for the HMC and the partitions, ensure that you have correctly set up the short host names. For more information, see the instructions in "Using Network Adapters to Communicate with Partitions" in the Hardware Management Console for pSeries Installation and Operations Guide. Correct any problems that you find, then verify that you can ping in both directions between the HMC and the partitions. If you do not use short host names or if the previous step does not correct the problem, use the Failing Item column.	NEXTLVL

Table 3. (B303) Connection monitoring reference codes
Reference Code	Description/Action Perform all actions before exchanging Failing Items	Failing Item
B3030001	The communication link between the service processor and the Hardware Management Console (HMC) failed. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 SPNETWK
B3030002	A single partition HMC link failed. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 PTNNTWK SPNETWK
B3030003	Multiple partition HMC links failed. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 PTNNTWK SPNETWK HMCMTWK
B3030004	All partition links for a single system to HMC failed. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 PTNNTWK SPNETWK
B3030005	All system links from one system to a single HMC failed. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 SPNETWK
B3030006	The links between a single HMC and a single managed system failed. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 SPNETWK
B3030007	A single HMC link to more than one managed system occurred. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 SPNETWK HMCNTWK
B3030008	One HMC link to another single HMC failed. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 HMCNTWK SPNETWK
B3030009	One HMC link to more than one HMC occurred. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 HMCMTWK SPNETWK
B303000A	The HMC lost links to all managed systems. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 SPNETWK
B303000B	Multiple HMCs lost links to a single managed system. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 SPNETWK HMCMTWK
B303000C	Multiple HMCs lost links to multiple managed systems. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 SPNETWK HMCMTWK
B303000D	Multiple HMCs lost links to multiple managed systems. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 SPNETWK HMCMTWK
B303000E	The Network Interface Card (NIC) failed Use the error codes offered in the HMC Focal Point to diagnose and repair the problem. For more information, see Using Service Focal Point. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	SYSNTWK
B303000F	A single partition HMC link failure occurred on a redundant path. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 PTNNTWK SPNETWK
B3030010	A single HMC link to one HMC failure occurred on a redundant path. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.
B3030011	Server firmware connection monitoring to the flexible service processor failed. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 SPNETWK
B3030012	Flexible service processor connection monitoring of server firmware failed. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 SPNETWK
B3030013	The communication path (mailbox) between server firmware and the flexible service processor failed. Note: This error might be a temporary condition caused by either the HMC or the system that the HMC is connected, being shutdown, restarted, upgraded or other intermittent conditions. While attempts are made to only report these errors when a connection has been lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.	FSPSP33 SPNETWK MAILBOX
B3031000	Customer reported a console problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031001	Customer reported a power problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031002	Customer reported a processor problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031003	Customer reported a LAN problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031004	Customer reported a software problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031005	Customer reported a input/output (I/O) problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031006	Customer reported a problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031007	Customer tested problem reporting by creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031100	Customer reported a problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031101	Customer reported a power problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031102	Customer reported a processor problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031103	Customer reported a LAN problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031104	Customer reported a software problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031105	Customer reported a input/output (I/O) problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031106	Customer reported a problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3031107	Customer tested problem reporting by creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem.
B3036600	The HMC failed to retrieve a dump from a managed system. If you have a redundant HMC environment, a peer HMC might have retrieved the dump. This might be a temporary problem. After receiving this error, perform the following steps: Ensure that there is connectivity between this HMC and managed System reported. Use the manage dumps utility to determine if dumps have been received from the managed system. If there is a peer HMC managing the same system, also check that HMC. Managed System Dumps can be retrieved by any HMC connected to the system. If there is a current dump from the managed system reported in the error, than the available dump has been retrieved.
B3036601	The HMC failed to retrieve a platform system dump from the managed system. If you have a redundant HMC environment, a peer HMC might have retrieved the dump. This might be a temporary problem. After receiving this error, perform the following steps: Use the manage dumps utility to determine if a dump of that type has been received from the managed system. If you have a peer HMC managing the same system, also check that HMC. Managed System Dumps can be retrieved by any HMC connected to the system. If there is a current dump of the type that failed from the managed system reported in the error, than the available dump of that type has been retrieved.
B3036602	The HMC failed to retrieve a dump from the service processor. If you have a redundant HMC environment, a peer HMC might have retrieved the dump. This might be a temporary problem. This might be a temporary problem. After receiving this error, perform the following steps: Use the manage dumps utility to determine if a dump of that type has been received from the managed system. If you have a peer HMC managing the same system, also check that HMC. Managed System Dumps can be retrieved by any HMC connected to the system. If there is a current dump of the type that failed from the managed system reported in the error, than the available dump of that type has been retrieved.
B3036604	The HMC failed to retrieve a power subsystem dump from the managed system. If you have a redundant HMC environment, a peer HMC might have retrieved the dump. This might be a temporary problem. After receiving this error, perform the following steps: Use the manage dumps utility to determine if a dump of that type has been received from the managed system. If you have a peer HMC managing the same system, also check that HMC. Managed System Dumps can be retrieved by any HMC connected to the system. If there is a current dump of the type that failed from the managed system reported in the error, than the available dump of that type has been retrieved.
B3036620	Primary HMC arbitration failure for domain {0} with peers {1}. Note: Domain indicates which domain the managed system belongs to. Peers indicate what HMC are also connected to the service processor. This error code indicates that this HMC did receive primary information from a peer HMC. To resolve this issue ensure that there is connectivity to the FSP and the other HMC connected to the managed system.
B3036625	Primary HMC arbitration failure for domain {0} with peers {1}. Note: Domain indicates which domain the managed system belongs to. Peers indicate what HMC are also connected to the service processor. This error code indicates that this HMC could not communicate with the service processor to either set itself as a primary or to determine if other HMCs are connected. To resolve this issue ensure that there is connectivity to the service processor and the other HMC connected to the managed system.

Table 4. (B31x) Connection monitoring reference codes
Reference Code	Description/Action Perform all actions before exchanging Failing Items	Failing Item
B3100500, B3112420	Ethernet network failure Do the following: Reseat your Ethernet card. Check your Ethernet cable connections. If the previous actions do not resolve the problem, contact your next level of support.	NEXTLVL