Chapter 36 Expand Messages

Cause  On G-series RVUs, a SWITCH command or a hardware error has occurred. The SWITCH command can be issued programmatically or interactively.

Effect  The I/O process switches to its backup processor.

Recovery  No recovery action is necessary if the switch is due to a request. Otherwise, note the reason, contact your service provider, and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A SWITCH command or a hardware error has occurred. The SWITCH command can be issued programmatically or interactively.

Effect  The I/O process switches to its backup processor.

Recovery  No recovery action is necessary if the switch is due to a request. Otherwise, note the reason, contact your service provider, and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A SWITCH command or a hardware error has occurred. The SWITCH command can be issued programmatically or interactively.

Effect  The I/O process switches to the backup path.

Recovery  If a command caused the switch, no corrective action is needed. If not, note the reason, contact your service provider, and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  On G-series RVUs, a command or error has occurred that affected the summary state of an Expand object.

Effect  The summary state of the Expand object changes.

Recovery  If a command caused the state change, no corrective action is needed. If not, note the reason, contact your service provider, and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A command or error has occurred that affected the summary state of an Expand object.

Effect  The summary state of the Expand object changes.

Recovery  If a command caused the state change, no corrective action is needed. If not, note the reason, contact your service provider, and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The Expand subsystem has detected a missing, incorrect, or inconsistent SCF profile parameter. A fatal IOP error has occurred, which has caused the Expand line-handler process to stop.

Effect  The Expand line-handler process stops and cannot be used. The Expand line or path cannot be used, and the associated devices are deleted.

Recovery  Stop the Expand line-handler process with Subsystem Control Facility (SCF). The recovery action depends on the cause code, as follows:

Cause  On G-series RVUs, the Expand subsystem detected a missing, incorrect, or inconsistent SYSGEN parameter. A fatal IOP error occurred, which caused the Expand line-handler process to stop.

Effect  The Expand line-handler process stops and cannot be used. The Expand line or path cannot be used, and the associated devices are deleted.

Recovery  Stop the Expand line-handler process with the Configuration Utility Program (COUP). The recovery action depends on the cause code, as follows:

Cause  On G-series RVUs, an I/O bus error has occurred during a transfer. A SWAN concentrator may be generating a continuous I/O power-on interrupt.

Effect  The operation is retried, then the other path is tried. If #errnum is in the range 210 through 229, the operation can switch to the other processor.

If a SWAN concentrator is generating a continuous I/O power-on interrupt, the application trying to communicate with the specified line receives an error code (usually 231, I/O power on) in response to its I/O request.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Take the appropriate action, or contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An I/O bus error has occurred during a transfer. A controller may be generating a continuous I/O power-on interrupt.

Effect  The operation is retried, then the other path is tried. If #errnum is in the range 210 through 229, the operation can switch to the other processor.

If a controller is generating a continuous I/O power-on interrupt, the application trying to communicate with the specified line receives an error code (usually 231, I/O power on) in response to its I/O request. An HP Tandem Maintenance and Diagnostic System (TMDS) event is generated.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual. Take the appropriate action, or contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  On G-series RVUs, an error has occurred on the indicated line, and the I/O retry has not succeeded.

Effect  The Expand line-handler process retries for up to three CLB downloads. If the error persists, Expand brings down the line. For some errors (for instance, a modem error), the Expand line-handler process waits for the error to clear and then retries.

Recovery  This error usually indicates an Expand driver problem. Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

I/O Error Codes for Expand Message 4 (G-series RVUs) 

The I/O error codes returned for %status-mask are listed in Table 36-3.

Hardware Error Codes for Expand Message 4 (G-series RVUs) 

The hardware error codes returned for %status-mask are listed in Table 36-4.

Cause  An error has occurred on the indicated line, and the I/O retry has not succeeded.

Effect  If the error involves a controller ownership switch, the Expand line-handler process retries for up to three ownership switches. If the error persists, Expand brings down the line. For any other error (for instance, a modem error), the Expand line-handler process waits for the error to clear and then retries.

Recovery  This error usually indicates a hardware problem. Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Hardware Error Codes for Expand Message 4 (D-series RVUs) 

The hardware error codes returned for %param1 are listed in Table 36-5.

I/O Error Codes for Expand Message 4 (D-series RVUs)

The I/O error codes returned for %param1 are listed in Table 36-6.

Cause  The operator has successfully returned the line to the system.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator has successfully returned the line to the system.

Effect  The operation is completed.

Recovery  Informational message only; no corrective action is needed.

Cause  This error has probably occurred for one of the following reasons:

Effect  The line goes down.

Recovery  If an operator command did not cause this message, perform the indicated recovery actions for any related messages (-4, 91, and 93) that precede this message. If the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  This error has probably occurred for one of the following reasons:

Effect  The line goes down.

Recovery  If an operator command did not cause this message, perform the indicated recovery actions for any related messages (-4, 91, and 93) that precede this message. If the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An internally inconsistent condition has been detected in the Expand line-handler process.

Effect  The line goes down.

Recovery  Attempt to restart the line. If the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An error was returned by the QIO subsystem.

Effect  The line goes down.

Recovery  Check the state of the QIO subsystem. If the QIO subsystem is functioning properly, attempt to restart the line. If the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An unexpected error was returned by the QIO subsystem.

Effect  The line goes down.

Recovery  Check the state of the QIO subsystem. If the QIO subsystem is functioning properly, attempt to restart the line. If the problem persists, contact your representative and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An error was returned by the NonStop TCP/IP process associated with the Expand-over-IP line-handler process.

Effect  The line goes down.

Recovery  Check the NonStop TCP/IP process associated with the Expand-over-IP line-handler process. See Appendix B, for a definition of the specified error. If the NonStop TCP/IP process is functioning properly, attempt to restart the line. If the problem persists, contact your representative and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A Level 2 connect or query response error was received

Effect  The line goes down.

Recovery  A connect or query response error indicates that the local and remote Expand-over-IP line-handler processes are incompatible or that an incorrect Internet Protocol (IP) address or port number was present in the connect or query message. Check the IP address and port number configurations in both the local and remote Expand-over-IP line-handler processes.

Cause  The NonStop TCP/IP process associated with the Expand-over-IP line-handler process has indicated that it is no longer the primary process, but a processor switch cannot be performed because other lines are active.

Effect  The line remains started, but it is not ready for data transfer. The most recent file-system error associated with the line will be 140 (FEMODEMERR). The line will become ready if the associated NonStop TCP/IP process becomes available in the processor or if the Expand-over-IP line-handler process is able to switch processors when the other lines become inactive.

Recovery  Check the configuration of the Expand-over-IP line and all other lines associated with the NonStop TCP/IP process to determine if reconfiguration is required.

Cause  Either the NonStop TCP/IP process associated with the Expand-over-IP line-handler process is not available or the line handler is configured to use IPv6 sockets with an associated TCP/IP process that does not support them.

Effect  The line remains started, but it is not ready for data transfer. The most recent file-system error associated with the line will be 140 (FEMODEMERR). The line will become ready if the associated NonStop TCP/IP process becomes available and supports the requested socket type.

Recovery  Ensure that the NonStop TCP/IP process associated with the Expand-over-IP line-handler process is functioning properly. If IPv6 sockets are desired, make sure the associated process supports such sockets.

Cause  The QIO subsystem is not available.

Effect  The line remains started, but is not ready for data transfer. The most recent file-system error associated with the line will be 140 (FEMODEMERR). The line will become ready if the QIO subsystem becomes available.

Recovery  Ensure that the QIO subsystem is functioning properly.

Cause  The Expand line-handler process has not received a connect response from the remote Expand line-handler process and the maximum number of connect requests have been sent.

Effect  The line goes down.

Recovery  Ensure that the remote Expand line-handler process is operational. Check the configuration of both the local and remote Expand line-handler processes.

Cause  The NonStop TCP/IP process associated with the Expand-over-IP line-handler process did not respond to a request from the Expand-over-IP line-handler process.

Effect  The line goes down.

Recovery  Check the NonStop TCP/IP process associated with the Expand-over-IP line-handler process. If the NonStop TCP/IP process is functioning properly, attempt to restart the line. If the problem persists, contact your representative and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An error was returned by the ATM subsystem.

Effect  The line goes down.

Recovery  Check the ATM subsystem. If the ATM subsystem is functioning properly, attempt to restart the line. If the problem persists, contact your representative and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The ATM line associated with the Expand-over-ATM line-handler process is not available.

Effect  The line remains started, but it is not ready for data transfer. The most recent file-system error associated with the line will be 140 (FEMODEMERR). The line will become ready if the associated NonStop TCP/IP process becomes available.

Recovery  Ensure that the ATM line associated with the Expand-over-ATM line-handler process is functioning properly.

Cause  The ATM permanent virtual circuit (PVC) used by the Expand-over-ATM line-handler process is not available.

Effect  The line remains started, but it is not ready for data transfer. The most recent file-system error associated with the line will be 140 (FEMODEMERR). The line will become ready if the associated PVC becomes available.

Recovery  Ensure that the PVC used by the Expand-over-ATM line-handler process is configured properly.

Cause  The ATM switched virtual circuit (SVC) used by the Expand-over-ATM line-handler process is not established.

Effect  The line remains started, but it is not ready for data transfer. The most recent file-system error associated with the line will be 140 (FEMODEMERR). The line will become ready if the associated SVC becomes established.

Recovery  Ensure that the SVC used by the Expand-over-ATM line-handler process is configured properly and that network connectivity is functional.

Cause  No response other than a timeout has been received from the ATM subsystem.

Effect  Call establishment for ATM failed to make a connection.

Recovery  Ensure that the SVC used by the Expand-over-ATM line-handler process is configured properly and that network connectivity is functional.

Cause  There is no process executing with the name specified on the ASSOCIATEDEV parameter for the line.

Effect  The Expand line cannot be started.

Recovery  Start the process whose name is specified on the ASSOCIATEDEV parameter for the line or change ASSOCIATEDEV to specify the name of an executing NAM process.

Cause  The Expand line handler received an error from the process whose name is specified on the ASSOCIATEDEV parameter for the line.

Effect  The Expand line goes to the not ready state.

Recovery  Contact your service provider and provide all relevant information as follows:

Cause  The number of Connect retries specified by the MAXRECONNECTS parameter is exhausted and the DOWNAFTERMAXRETRIES option is on.

Effect  The Expand line is aborted.

Recovery  Correct the problem causing the NAM process reconnects and restart the Expand line. The name of the NAM process is specified in the Expand line’s ASSOCIATEDEV parameter.

Cause  The line handler received a message from its NAM process that its connection is down.

Effect  The Expand line goes to the not ready state.

Recovery  Correct the problem causing the NAM process to lose its connection and restart the Expand line. The name of the NAM process is specified in the Expand line’s ASSOCIATEDEV parameter.

Cause  The line quality dropped below the threshold specified in the QUALITYTHRESHOLD setting and it remained below the threshold for longer than the time specified in QUALITYTIMER setting.

Effect  If the DOWNIFBADQUALITY setting is "ON", the line aborts. If the DOWNIFBADQUALITY setting is "OFF", a warning is issued.

Recovery  Correct the problem causing the low line quality and restart the Expand™ line.

Cause  The configured LIF name was not found in the SLSA subsystem.

Effect  The Expand line will signal line state 140, then continue to retry the connection to the LIFNAME.

Recovery  Check that the LIF is configured in the SLSA subsystem.

Cause  The configured LIF is in STOPPED state.

Effect  The Expand line will signal line state 140, then continue to retry the connection to the LIFNAME.

Recovery  Check that the LIF has been started.

Cause  The configured LIF access is in DOWN state.

Effect  The Expand line will signal line state 140, then continue to retry the connection to the LIFNAME.

Recovery  Check the access state of the configured LIF.

Cause  The LIF is inaccessible from the Expand line handler’s CPU or another line handler is already using the LIF.

Effect  The Expand line will signal line state 140, then continue to retry the connection to the LIFNAME.

Recovery  Check the access list associated with the LIF to verify that the Expand line handler’s CPU is included. Check that no other line handler is using the LIF.

Cause  An Expand line-handler process has reported a change in the line quality.

Effect  The system reports the problem and continues processing.

Recovery  If this message occurs repeatedly, examine the retransmission quality of the communications lines and use whatever corrective measures are appropriate for those lines.

Cause  An Expand line-handler process has reported a change in the line quality.

Effect  The system reports the problem and continues processing.

Recovery  If this message occurs repeatedly, examine the retransmission quality of the communications lines and use whatever corrective measures are appropriate for those lines.

Cause  If xxx is 001, the network control process ($NCP) has determined that all paths to system nnn are unavailable.

If xxx is 004, the Expand line-handler process has reported an end-to-end protocol error.

If xxx is 999, the Expand line-handler process has reported a recovery from a soft failure, possibly related to path timing.

Effect  $NCP attempts to reestablish the connection over the same path; if this attempt fails, $NCP seeks an alternate path.

Recovery  Informational message only; no corrective action is needed unless other related messages, such as Expand message 45, are displayed for the line. In that case, perform the recovery for the related message.

Cause  If xxx is 001, the network control process ($NCP) has determined that all paths to system nnn are unavailable.

If xxx is 004, the Expand line-handler process has reported an end-to-end protocol error.

If xxx is 999, the Expand line-handler process has reported a recovery from a soft failure, possibly related to path timing.

Effect  $NCP attempts to reestablish the connection over the same path; if this attempt fails, $NCP seeks an alternate path.

Recovery  Informational message only; no corrective action is needed unless other related messages, such as Expand message 45, are displayed for the line. In that case, perform the recovery for the related message.

Cause  The line is ready to accept network requests.

For a direct-connect line-handler process, this message appears after both Expand line-handler processes (local and remote) have exchanged Set Asynchronous Balanced Mode/Unnumbered Acknowledgment (SABM/UA) sequences.

For the X.25 interface, this message displays when the Expand line-handler process is informed that a virtual circuit is established, or when the Expand line-handler process learns of the virtual circuit by querying the X.25 access process.

Effect  A connection is successfully established with a remote system.

Recovery  Informational message only; no corrective action is needed.

Cause  The line is ready to accept network requests.

For a direct-connect line-handler process, this message appears after both Expand line-handler processes (local and remote) have exchanged Set Asynchronous Balanced Mode/Unnumbered Acknowledgment (SABM/UA) sequences.

For the X.25 interface, this message displays when the Expand line-handler process is informed that a virtual circuit is established, or when the Expand line-handler process learns of the virtual circuit by querying the X.25 access process.

Effect  A connection is successfully established with a remote system.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator has brought down a line, or an error has brought it down.

Effect  The Expand line-handler process is not ready to accept further network requests. The network control process ($NCP) must find an alternate communication path.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Appropriate recovery depends on the file-system error that occurred and on the line type, as follows:

Cause  The operator has brought down a line, or an error has brought it down.

Effect  The Expand line-handler process is not ready to accept further network requests. The network control process ($NCP) must find an alternate communication path.

Recovery  See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Appropriate recovery depends on the file-system error that occurred and on the line type, as follows:

Cause  A successful connect exchange has occurred with the network control process ($NCP) at the remote system nnn.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  A successful connect exchange has occurred with the network control process ($NCP) at the remote system nnn.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  An Expand line-handler process did not receive an end-to-end acknowledgment within the configured L4TIMEOUT time. The Expand line-handler process then sent a request for the acknowledgment and again did not receive it within the configured L4TIMEOUT time. The Expand line-handler process retried its request for acknowledgment L4RETRIES times before the network control process ($NCP) issued this message.

Effect  The connection to the indicated system is lost. $NCP attempts to reestablish the connection first over the same path and then over another path, if it has a lower time factor.

Recovery  Appropriate recovery actions depend on the cause of the failure to acknowledge. For instance, if congestion in the network is indicated, check the configuration to ensure that each Expand line-handler process has sufficient pool space. Check the statistics for pool space usage in intermediate systems along the path, and increase the configured pool space if necessary. Check for other sources of congestion (such as high-speed incoming lines and low-speed outgoing lines at a node), and reconfigure lines as needed.

Cause  An Expand line-handler process has not received an end-to-end acknowledgment within the configured L4TIMEOUT time. The Expand line-handler process then sent a request for the acknowledgment and again did not receive it within the configured L4TIMEOUT time. The Expand line-handler process retried its request for acknowledgment L4RETRIES times before the network control process ($NCP) issued this message.

Effect  The connection to the indicated system is lost. $NCP attempts to reestablish the connection first over the same path and then over another path, if it has a lower time factor.

Recovery  Appropriate recovery actions depend on the cause of the failure to acknowledge. For instance, if congestion in the network is indicated, check the configuration to ensure that each Expand line-handler process has sufficient pool space. Check the statistics for pool space usage in intermediate systems along the path, and increase the configured pool space if necessary. Check for other sources of congestion (such as high-speed incoming lines and low-speed outgoing lines at a node), and reconfigure lines as needed.

Cause  A change in processor status has occurred at system nnn.

This message is sent only by a network control process ($NCP) with Network Monitor Console (NMC) status. It is usually sent at connection time or when the processor status has changed.

Effect  The system reports the problem and continues processing.

Recovery  Informational message only; no corrective action is needed.

Cause  A change in processor status has occurred at system nnn.

This message is sent only by a network control process ($NCP) with Network Monitor Console (NMC) status. It is usually sent at connection time or when the processor status has changed.

Effect  The system reports the problem and continues processing.

Recovery  Informational message only; no corrective action is needed.

Cause  The network control process ($NCP) did not receive a status message from the $NCP at system nnn during three time intervals. $NCP automatically seeks an alternate path.

Effect  The system reports the problem and continues processing.

Recovery  Informational message only; no corrective action is needed unless other related messages, such as Expand message 45, are displayed for that line. In that case, perform the recovery for the related message.

Cause  The network control process ($NCP) did not receive a status message from the $NCP at system nnn during three time intervals. $NCP automatically seeks an alternate path.

Effect  The system reports the problem and continues processing.

Recovery  Informational message only; no corrective action is needed unless other related messages, such as Expand message 45, are displayed for that line. In that case, perform the recovery for the related message.

Cause  The Expand subsystem has detected a missing, incorrect, or inconsistent modifier. Causes for specified cause codes are described above. For additional codes and their descriptions, see message 91 (G-series RVUs).

Effect  The effect depends on the cause code, as follows:

For the effect of additional codes and their descriptions, see message 91 (G-series RVUs).

Recovery  The recovery action depends on the cause code, as follows:

For the recovery of additional codes and their descriptions, see message 91 (G-series RVUs).

Cause  An Expand line-handler process or the network control process ($NCP) has detected an internally inconsistent condition. See Table 36-7 for more information.

Effect  $NCP reports the condition and continues processing.

Recovery  The recovery action depends on the cause code, as follows:

Cause  An Expand line-handler process or the network control process ($NCP) has detected an internally inconsistent condition. See Table 36-8 for more information.

Effect  $NCP reports the condition and continues processing.

Recovery  The recovery action depends on the cause code, as follows:

Cause  The Expand subsystem has detected a missing, incorrect, or inconsistent modifier. Causes for specified cause codes are described above. For additional codes and their descriptions, see message 93 (G-series RVUs).

Effect  The effect depends on the cause code, as follows:

For the effect of additional codes and their descriptions, see message 93 (G-series RVUs).

Recovery  The recovery action depends on the cause code, as follows:

For the recovery of additional codes and their descriptions, see message 93 (G-series RVUs).

Cause  The Expand subsystem has detected a missing, incorrect, or inconsistent modifier. Causes for specified cause codes are described above.

Effect  The effect depends on the cause code, as follows:

Recovery  The recovery action depends on the cause code, as follows:

Cause  The Expand subsystem has detected a missing, incorrect, or inconsistent SYSGEN parameter. Causes for specified cause codes are described above.

Effect  The effect depends on the cause code, as follows:

Recovery  The recovery action depends on the cause code, as follows:

Cause  An error has aborted network traffic.

Effect  A message is sent for each system where traffic was aborted.

Recovery  Informational message only; no corrective action is needed. However, if cause codes 01 through 04 occur frequently, you may want to trace the problem. Run traces on the network control process ($NCP) and on the Expand line-handler process if you can identify which Expand line-handler process is involved. In the case of code 04 (ownership switch), trace the backup processes as well.

Cause  An error has aborted network traffic.

Effect  A message is sent for each system where traffic was aborted.

Recovery  Informational message only; no corrective action is needed. However, if cause codes 01 through 04 occur frequently, you may want to trace the problem. Run traces on the network control process ($NCP) and on the Expand line-handler process if you can identify which Expand line-handler process is involved. In the case of code 04 (ownership switch), trace the backup processes as well.

Cause  The communications line interface processor (CLIP) associated with an Expand line was successfully downloaded.

Effect  The operation is finished.

Recovery  If this message occurs once, it is an informational message only; no corrective action is needed. However, if it occurs repeatedly, check first for related hardware problems with the CLIP; also check for configuration problems. If neither kind of problem is apparent, turn automatic downloading off and take a CLIP dump.

Cause  The communications line interface processor (CLIP) associated with an Expand line was successfully downloaded.

Effect  The operation is finished.

Recovery  If this message occurs once, it is an informational message only; no corrective action is needed. However, if it occurs repeatedly, check first for related hardware problems with the CLIP; also check for configuration problems. If neither kind of problem is apparent, turn automatic downloading off and take a CLIP dump.

Cause  The connection to the concentrator or the concentrator hardware failed while attempting to download the CLIP or the CIU associated with an Expand™ line.

This message is usually accompanied by another operator message or by a file-system error message.

Effect  The CLIP or CIU is not downloaded and remains in the starting and boot states.

Recovery  Analyze the failure by looking at the ConMgr error code given by param3 in the text message and at the accompanying operator message. Then issue a Subsystem Control Facility (SCF) STOP command against the line before trying to start it again. See Appendix B, for more information on the specified error.

Cause  The 3650/6100 Communications Subsystem (CSS) family controller hardware failed while attempting to download the CLIP or the CIU associated with an Expand line.

This message is usually accompanied by another operator message or by a file-system error message.

Effect  The CLIP or CIU is not downloaded and remains in the starting and boot states.

Recovery  Analyze the failure by looking at the CSM error code given by param3 in the text message and at the accompanying operator message. Then issue a Subsystem Control Facility (SCF) STOP command against the line before trying to start it again. See Appendix B, for more information on the specified error.

Figure 36-1 CLIP Status Byte (G-series RVUs)

Cause  The Concentrator Manager (ConMgr) or the I/O process received a status-probe response from the CLIP associated with an Expand line. The probe indicates that this CLIP is in the boot state instead of the run state, either because it was powered off and then on again or because of some internal software or hardware problem.

Effect  The communications access process (CAP) attempts to download the CLIP again. If the CAP cannot do so on the primary path, it attempts a download on another path.

Recovery  Decode the CLIP status byte to determine which error occurred. If the CLIP does not restart automatically, try to restart it manually. If the problem persists and if the CLIP status indicates a software problem, take a CLIP dump. Note the CLIP status value, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Figure 36-2 CLIP Status Byte (D-series RVUs)

Cause  The Communications Subsystem Manager (CSM) or the I/O process received a status-probe response from the CLIP associated with an Expand line. The probe indicates that this CLIP is in the boot state instead of the run state, either because it was powered off and then on again or because of some internal software or hardware problem.

Effect  The communications access process (CAP) attempts to download the CLIP again. If the CAP cannot do so on the primary path, it attempts a download on another path.

Recovery  Decode the CLIP status byte to determine which error occurred. If the CLIP does not restart automatically, try to restart it manually by using the Subsystem Control Facility (SCF) LOAD LINE command or, for C-series systems, the Communications Management Interface (CMI) CONTROL LINE, LOAD command. If the problem persists and if the CLIP status indicates a software problem, take a CLIP dump. Note the CLIP status value, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A command to the CLB of a ServerNet wide area network (SWAN) concentrator (associated with an Expand line) has been rejected. This message normally displays when the concentrator is powered on or off, or when processors are switched.

Effect  In most cases, the concentrator and the host recover (become synchronized).

Recovery  If the error persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A command to the CLB of a 3650/6100 Communications Subsystem (CSS) (associated with an Expand line) has been rejected, indicating that the break-out board (BOB) was not properly synchronized with the host system. This message normally displays when the BOB is powered on or off, or when processors are switched.

Effect  In most cases, the BOB and the host recover (become synchronized).

Recovery  If the error persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The CLIP associated with an Expand line has failed to respond to a periodic probe by a line-handler process, and a NO RESPONSE message was received.

Effect  In most cases, the affected I/O process tries to recover.

Recovery  If this message occurs once, no corrective action is needed. See Appendix B, for more information on the specified error. However, if it occurs repeatedly, then note the values of %param3 and %param4, contact your service provider, and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The CLIP associated with an Expand line has failed to respond to a periodic probe by a line-handler process, and a NO RESPONSE message was received.

Effect  In most cases, the affected I/O process tries to recover.

Recovery  If this message occurs once, no corrective action is needed. See Appendix B, for more information on the specified error. However, if it occurs repeatedly, then note the values of %param3 and %param4, contact your service provider, and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A problem has occurred in the CLB protocol between the CLIP and the Expand line-handler process. These errors often occur during a path switch.

Effect  Generally, the Expand subsystem recovers automatically; if it cannot recover, the Expand subsystem brings down the line.

Recovery  If this error did not occur during a path switch, note the values of #err, %param1, and %param2; contact your service provider; and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A problem has occurred in the CLB protocol between the CLIP and the Expand™ line-handler process. These errors often occur during a path switch.

Effect  Generally, the Expand subsystem recovers automatically; if it cannot recover, the Expand subsystem brings down the line.

Recovery  If this error did not occur during a path switch, note the values of #err, %param1, and %param2; contact your service provider; and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The communications line interface processor (CLIP) associated with an Expand line has hit an unexpected breakpoint.

Effect  The CLIP stops.

Recovery  Note the values of all parameters, contact your service provider, and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The communications line interface processor (CLIP) associated with an Expand line has hit an unexpected breakpoint.

Effect  The CLIP stops.

Recovery  Note the values of all parameters, contact your service provider, and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The communications line interface processor (CLIP) associated with an Expand line has received a line configuration different from that in the I/O process.

Effect  The line does not come up.

Recovery  Note the values of all parameters, contact your service provider, and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The communications line interface processor (CLIP) associated with an Expand line has received a line configuration different from that in the I/O process.

Effect  The line does not come up.

Recovery  Note the values of all parameters, contact your service provider, and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The communications line interface processor (CLIP) associated with an Expand line has responded to the I/O process with a function (F) and modifier (M), defined in %param1.

Effect  The Expand subsystem tries to clear the error by reloading the CLIP. If this action does not succeed or if it cannot be done, the Expand subsystem resets the CLIP and brings the line down.

Recovery  Note the values of all parameters, contact your service provider, and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The communications line interface processor (CLIP) associated with an Expand line has responded to the I/O process with a function (F) and modifier (M), defined in %param1.

Effect  The Expand subsystem tries to clear the error by reloading the CLIP. If this action does not succeed or if it cannot be done, the Expand subsystem resets the CLIP and brings the line down.

Recovery  Note the values of all parameters, contact your service provider, and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A process creation failure has occurred.

Effect  The network control process ($NCP) will attempt to create the backup process again after a period of time has elapsed.

Recovery  Informational message only; no corrective action is needed. However, if the problem persists, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A rebalance was started either manually or automatically.

Effect  The multi-CPU path indicated by system-name is being rebalanced.

Recovery  Informational message only; no corrective action is needed.

Cause  Extended-memory usage has increased above 70% and then above 90%, and then dropped back below 70% of the EXTMEMSIZE base-size value.

Effect  None.

Recovery  Informational message only. Increase Expand line handler device parameter EXTMEMSIZE to a higher value to avoid the generation of this message.

Cause  The Expand line handler was not able to respond to the timed message sent by the network control process ($NCP).

Effect  $NCP waits another 60 seconds for the message.

Recovery  Informational message only; no corrective action is needed.