Chapter 10 CIP (Cluster I/O Protocols) Messages

The messages in this chapter are generated by the Cluster I/O Protocols. The subsystem ID displayed by these messages includes CIP as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15. Fault codes are documented in the Cluster I/O Protocols (CIP) Configuration and Management Manual.

–0001

-00001 CIP Manager switching from cpu processor-1 to cpu processor-2

`cpu processor-1`	is CPU where primary CIPMAN process used to run.
`cpu processor-2`	is CPU where primary CIPMAN process is now running.

Cause Backup CIPMAN process became primary CIPMAN process.

Effect Primary CIPMAN process is now running in a different CPU.

Recovery This is an informational message only; no corrective action is needed.

0001

000001 CIP Manager internal Error

Cause CIPMAN encountered an internal error.

Effect The primary CIPMAN process might change to the backup process.

Recovery This is a serious error. Contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable.

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.

0002

000002 CIP Manager internal trap

Cause CIPMAN encountered an internal error.

Effect The primary CIPMAN process might change to the backup process.

Recovery This is a serious error. Contact your service provider and provide all relevant information:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

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.

0003

000003 CIP Manager backup is up

Cause The backup CIPMAN process is started.

Effect CIPMAN is running as a NonStop process pair.

Recovery This is an informational message only; no corrective action is needed.

0004

000004 CIP Manager backup is down

Cause The primary CIPMAN process could not start a backup process. The processor in which CIPMAN is attempting to start the backup process might not be started.

Effect CIPMAN is not running as a NonStop process pair.

Recovery Start the processor in which CIPMAN is attempting to start the backup process.

0005

000005 CIP Manager backup create failure

Cause The primary CIPMAN process could not create a backup process although the processor in which CIPMAN is attempting to start the process is up.

Effect CIPMAN is not running as a NonStop process pair.

Recovery Switch the backup process to a different processor. For more information on switching a manager process to another processor, see the SCF Reference Manual for the Kernel Subsystem.




	NOTE: This switch might not be possible because CIPMAN must run in processors that $SYSTEM is running in.

0006

000006 CIP Manager checkpoint failure

Cause The primary CIPMAN process was unable to create a checkpoint with the backup process.

Effect The backup CIPMAN process does not have current information.

Recovery If this error persists, abort and restart the CIPMAN process. For more information on aborting and starting a manager process, see the SCF Reference Manual for the Kernel Subsystem.

5001

005001 CIP Manager Transient Fault CIPMAN Name: $ZZCIP Origin: source Severity: level Type Code: fault-code [ Type String: fault-text ] [ ErrorDetail1: optional-value ] [ ErrorDetail2: optional-value ] [ ErrorDetail3: optional-value ] [ ErrorDetail4: optional-value ] [ ErrorDetail5: optional-value-hex] [ Text: custom-text ]

`source`	specifies where the transient fault originated from. This field displays one of the following: Unrecognized Origin CIPMON CIPSREQ QIO Subsystem CIPSSRV NonStop Kernel CLIMAGT ITAPI DSM Subsystem NSK Configuration Routines CIP Manager Service Processor SCS CLIM GOOF
`level`	specifies this event as: informational warning fatal unrecognized
`fault-code`	is a number associated with this particular transient fault. If the transient fault originated within the CIP subsystem, the event message also displays text. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes. If the transient fault originated outside the CIP subsystem, the event message displays the error code received from the other subsystem or process.
`fault-text`	is a brief description of the cause of the transient fault. This field only appears if `fault-code` is associated with the CIP subsystem. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes.
`optional-value`	provides additional information about the event.
`optional-value-hex`	provides additional information about the event in hex form.
`custom-tex`t	provides additional information about the event.

Cause The CIPMAN process encountered a fault.

Effect The effect depends on the fault specified by fault-code.

Recovery The recovery depends on the fault specified by fault-code. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about CIP fault codes.

5002

005002 Object Available Process Name: $ZZCIP Event Number: CIPMAN available Reason: reason Previous State: state Current State: state [ Text: text ]

`reason`	specifies the reason that the process became available.
`state`	in the `Previous State` field, `state` specifies the state the process was in before becoming available. In the `Current State` field, `state` specifies the state of the process when it becomes available.
`text`	provides additional information about the event.

Cause The CIPMAN process is running and operational.

Effect Management of the CIP subsystem is now possible.

Recovery This is an informational message only; no corrective action is needed.

5003

005003 Object Unavailable Process Name: $ZZCIP Event Number: CIPMAN unavailable Reason: reason Previous State: state Current State: state [ Text: text ]

`reason`	specifies the reason that the process became unavailable.
`state`	in the `Previous State` field, `state` specifies the state the process was in before becoming unavailable. In the `Current State` field, `state` specifies the state of the process when it becomes unavailable.
`text`	provides additional information about the event.

Cause The CIPMAN process is non-operational, either due to an internal software fault or an operator request.

Effect The CIPMAN process terminates. Management of the CIP subsystem is now unavailable.

Recovery If the CIPMAN process was terminated due to an abort request to the persistence manager, you must restart the CIPMAN process by means of the persistence manager. For other causes of CIPMAN process termination, the CIPMAN process is automatically restarted by the persistence manager.

5004

005004 (Other) State Change Process Name: $ZZCIP Event Number: CIPMAN state change Reason: reason Previous State: state Current State: state [ Text: text ]

`reason`	specifies the reason that the process changed state.
`state`	in the `Previous State` field, `state` specifies the state the process was in before the state change. In the `Current State` field, `state` specifies the state of the process after the state change.
`text`	provides additional information about the event.

Cause The CIPMAN process changed from one state to another.

Effect If the CIPMAN process is now in the STOPPED state, the CIPMAN process has terminated.

Recovery If the CIPMAN process is in the STOPPED state due to an abort request to the persistence manager, you must restart the CIPMAN process by means of the persistence manager. For other causes of CIPMAN process termination, the CIPMAN process is automatically restarted by the persistence manager.

5005

Configuration Services operation operation error [ for record-type record [ record-name ] ] Error: error, Detail: detail [ Lock hold by process-name ]

operation

is the operation that was being performed when the error occurred. Possible values are:

1	Locking database
2	Unlocking database
3	Insert entry into database
4	Delete entry from database
5	Reading database entry
6	Updating database entry
7	Registration for event (by CRU type)
8	Registration for event (by event type)

record-type

is the record type involved in the configuration management operation (CLIM or PROVIDER).

record-name

is the name of the specific configuration record involved in the configuration management operation.

error

is the error code returned by a configuration management routine.

detail

is the error detail code returned by a configuration management routine.

process-name

provides the name of the process that is currently holding the lock to the configuration database. (The lock prevents the CIPMAN process from completing its configuration management operation.)

Cause An internal error occurred during a Configuration Services operation.

CIPMAN relies on registration for events with NonStop OS Configuration Services for fast notification of certain configuration and status changes related to CLIM hardware connectivity within the NonStop system. If CIPMAN fails to register with NonStop OS Configuration Services, CIPMAN still can detect configuration and status changes by means of periodic checks, although a delay may occur in detecting configuration and status changes. It might take longer for the CIPMAN to bring up the connection to a CLIM after changes in hardware connectivity with that CLIM.

Recovery Investigate the cause of the error. Reissue the failed SCF command if necessary.

If the CIPMAN appears to be slow in detecting configuration changes due to failure to register events with Configuration Services, and you want to accelerate recovery of the connectivity with a CLIM, try the SCF PRIMARY PROCESS $ZZCIP command to force the primary and backup CIPMAN processes to switch roles. Upon takeover, the new primary CIPMAN immediately checks the hardware connectivity status between the NonStop system and each configured CLIM.

5006

005006 CIP Manager terminated due to reason [ Processor processor does not have $SYSTEM running ] [ Text: text ]

reason

specifies the reason that the CIPMAN process terminated during initialization. Possible values are:

1	Invalid process name	Must be $ZZCIP to be valid.
2	Running in invalid processor	Must run in processors that $SYSTEM is running in.
3	Unable to interface with QIO	CIPMAN process requires access to QIO to be operational.

processor

specifies the processor in which the CIPMAN process was running that does not have the system process running.

text

provides additional information about the event.

Cause The CIPMAN process detected a problem in its environment during process initialization and cannot proceed.

Effect The CIPMAN process stops.

Recovery For an invalid process name, reconfigure the system to start CIPMAN with the process name $ZZCIP. For running in an invalid processor, change the configuration of CIPMAN so that both the primary and backup manager processes are started in the same processors as the primary and backup $SYSTEM processes (usually processors 0 and 1). For inability to interface with QIO, make sure that QIO is available and has a version that is compatible with the current CIPMAN process version.




	NOTE: The primary CIPMAN process does not have to be in the same processor as the primary system process. The primary CIPMAN process can be in the same processor as either the primary or backup system process. The same is true for the backup CIPMAN process.

5007

005007 CIP Manager-info CIPMAN Name: $ZZCIP Text: text

text

provides additional information about this event.

This event is sent to $ZLOG only.

Cause CIPMAN started up and is using this event to report its information (including VPROC). Also, when CIPMAN enters or exits PowerOn recovery handling mode.

Effect This is an informational message only; no corrective action is needed.

Recovery This is an informational message only; no corrective action is needed.

5101

005101 CIPMON Transient Fault CIPMON Name: $ZZCIP.monitor-name Origin: source Severity: level Type Code: fault-code [ Type String: fault-text ] [ ErrorDetail1: optional-value ] [ ErrorDetail2: optional-value (optional-value-hex) ] [ ErrorDetail3: optional-value (optional-value-hex) ] [ ErrorDetail4: optional-value (optional-value-hex) ] [ ErrorDetail5: (optional-value-hex ] [ Text: custom-text ] [ Manager: manager-name ]

`monitor-name`	specifies the CIP monitor process that had a transient fault.
`source`	specifies where the transient fault originated. This field displays one of the following: Unrecognized Origin CIPMON CIPSREQ QIO Subsystem CIPSSRV NonStop Kernel CLIMAGT ITAPI DSM subsystem NSK Configuration Routines CIP Manager Service Processor SCS CLIM GOOF
`level`	specifies this event as: informational warning fatal unrecognized
`fault-code`	is a number associated with this particular transient fault. If the transient fault originated within the CIP subsystem, the event message also displays text. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes. If the transient fault originated outside the CIP subsystem, the event message displays the error code received from the other subsystem or process.
`fault-text`	is a brief description of the cause of the transient fault. This field only appears if `fault-code` is associated with the CIP subsystem. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes.
`optional-value`	provides additional information about the event.
`optional-value-hex`	provides additional information about the event in hex format.
`custom-text`	provides additional information about the event.
`manager-name`	specifies the name of the parent CIPMAN process for the CIPMON.

Cause A CIPMON process encountered a fault.

Effect The effect depends on the fault specified by fault-code.

Recovery The recovery depends on the fault specified by fault-code. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes.

5102

005102 Object Available CIPMON Name: $ZZCIP.monitor-name Event Number: CIPMON available Reason: reason Previous State: state Current State: state [ Text: text ]

`monitor-name`	specifies the CIPMON process that became available.
`reason`	specifies the reason that the CIPMON process became available.
`state`	in the `Previous State` field, `state` specifies the state the CIPMON was in before becoming available. In the `Current State` field, `state` specifies the state of the CIPMON after it becomes available.
`text`	provides additional information about the event.

Cause A monitor process became available and the CIP subsystem can access it.

Effect The system can access the monitor process.

Recovery This is an informational message only; no corrective action is needed.

5103

005103 Object Unavailable CIPMON Name: $ZZCIP.monitor-name Event Number: CIPMON unavailable Reason: reason Previous State: state Current State: state [ Text: text ]

`monitor-name`	specifies the CIPMON process that became unavailable.
`reason`	specifies the reason that the CIPMON process became unavailable.
`state`	in the `Previous State` field, `state` specifies the state the CIPMON was in before becoming unavailable. In the `Current State` field, `state` specifies the state of the CIPMON after it becomes unavailable.
`text`	provides additional information about the event.

Cause The CIPMON process has been aborted or stopped, or a fault has occurred.

Effect There is a loss of service to the CIP subsystem from the processor that the CIPMON process was running in.

Recovery Reload the processor if necessary. If CIPMON process was terminated because of an abort request to the persistence manager, you must restart the CIPMON process by using the persistence manager. For other causes of CIPMON process termination, the CIPMON process should be automatically restarted by the persistence manager.

5104

005104 (Other) State Change CIPMON Name: $ZZCIP.monitor-name Event Number: CIPMON state change Reason: reason Previous State: state Current State: state [ Text: text ]

`monitor-name`	specifies the CIPMON process that had a state change.
`reason`	specifies the reason that the CIPMON had a state change.
state	in the `Previous State` field, `state` specifies the state the CIPMON was in before the state change. In the `Current State` field, `state` specifies the state of the CIPMON after the state change.
`text`	provides additional information about the event.

Cause CIPMON process change from one state to another.

Effect This is an informational message only; no corrective action is needed.

Recovery This is an informational message only; no corrective action is needed.

5105

005105 Resource Unavailable Monitor - $ZZCIP.monitor-name count resource shortage reports for resource of type resource [ text ]

`monitor-name`	specifies the CIPMON process that had a resource shortage.
`count`	the number of resource allocation failures since the last report.
`resource`	indicates the type of resource that cannot be allocated; for example: Memory Heap QIO Pool QIO Space
`text`	provides additional information about the failure of resource allocations.

Cause Failures encountered during resource allocation.

Effect The CIPMON cannot obtain resources, which can lead to termination of the specified CIPMON.

Recovery Find out why resources are not available, and fix the problem if possible.

5106

005106 CIPMON-info Monitor - $ZZCIP.monitor-name Text: text

`monitor-name`	specifies the CIPMON process that generated this event.
text	provides additional information about this event.

This message is sent to $ZLOG only.

Cause A CIPMON process dropped a message while processing the messages from the queue.

Effect This is an informational message only; no corrective action is needed.

Recovery This is an informational message only; no corrective action is needed.

5107

005107 CIP Internal Report Unrecoverable Fault - process terminated, CIPMON Name: $ZZCIP.monitor-name Origin: source Severity: level Type Code: fault-code [ Type String: fault-text ] Detected at line line-number in file source-filename

[ Text: custom-text ]

`monitor-name`	specifies the CIPMON process that encountered the problem.
`source`	specifies where the fault originated. This field displays one of the following: Unrecognized Origin CIPMON CIPSREQ QIO Subsystem CIPSSRV NonStop Kernel CLIMAGT ITAPI DSM Subsystem NSK Configuration Routines CIP Manager Service Processor SCS CLIM GOOF
`level`	specifies this event as fatal.
`fault-code`	is a number associated with this particular transient fault. If the transient fault originated within the CIP subsystem, the event message also displays text. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes. If the transient fault originated outside the CIP subsystem, the event message displays the error code received from the other subsystem or process.
`fault-text`	is a brief description of the cause of the transient fault. This field only appears if `fault-code` is associated with the CIP subsystem. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes.
`line-number`	specifies the line of code in which this fault is encountered.
`source-filename`	specifies the name of the source file in which this fault is encountered.
`custom-text`	is additional information describing the reason for the fault.

Cause A CIPMON process encountered an unrecoverable fault.

Effect The CIPMON process is terminated.

Recovery The recovery depends on the fault specified by fault-code. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes.

5201

005201 CLIM Transient Fault CLIM Name: $ZZCIP.clim-name Origin: source Severity: level Type Code: fault-code [ Type String: fault-text ] [ ErrorDetail1: optional-value (optional-value-hex) ] [ ErrorDetail2: optional-value (optional-value-hex) ] [ ErrorDetail3: optional-value (optional-value-hex) ] [ ErrorDetail4: optional-value (optional-value-hex) ] [ ErrorDetail5: optional-value-hex][ Text: custom-text ] [ Manager: manager-name ]

`clim-name`	specifies the CLIM where the transient fault occurred.
`source`	specifies where the transient fault originated. This field displays one of the following: Unrecognized Origin CIPMON CIPSREQ QIO Subsystem CIPSSRV NonStop Kernel CLIMAGT ITAPI DSM Subsystem NSK Configuration Routines CIP Manager Service Processor SCS CLIM GOOF
`level`	specifies this event as: informational warning fatal unrecognized
`fault-code`	is a number associated with this particular transient fault. If the transient fault originated within the CIP subsystem, the event message also displays text. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes. If the transient fault originated outside the CIP subsystem, the event message displays the error code received from the other subsystem or process.
`fault-text`	is a brief description of the cause of the transient fault. This field only appears if `fault-code` is associated with the CIP subsystem. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes.
`optional-value`	is additional information about the event.
`optional-value-hex`	is additional information about the event in hex format.
`custom-text`	provides additional information about the event.
`manager-name`	specifies the parent CIPMAN process for the CLIM.

Cause The CLIM encountered a fault.

Effect The effect depends on the fault specified by fault-code.

Recovery Recovery depends on the fault specified by fault-code. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes.

5202

005202 Object Available CLIM Name: $ZZCIP.clim-name Event Number: CLIM available Reason: reason Previous State: state Current State: state [ Text: text ]

`clim-name`	specifies the CLIM that became available.
`reason`	specifies the reason that the CLIM became available.
`state`	in the `Previous State` field, `state` specifies the state the CLIM was in before becoming available. In the `Current State` field, `state` specifies the state of the CLIM after it becomes available.
`text`	provides additional information about the event.

Cause The CLIM became available and the CIP subsystem can access it.

Effect The system can access the CLIM.

Recovery This is an informational message only; no corrective action is needed.

5203

005203 Object Unavailable CLIM Name: $ZZCIP.clim-name Event Number: CLIM unavailable Reason: reason Previous State: state Current State: state [ Text: text ]

`clim-name`	specifies the CLIM that became unavailable.
`reason`	specifies the reason that the CLIM became unavailable.
`state`	in the `Previous State` field, `state` specifies the state the CLIM was in before becoming unavailable. In the `Current State` field, `state` specifies the state of the CLIM after it becomes unavailable.
`text`	provides additional information about the event.

Cause The CIP subsystem cannot access the CLIM because the CLIM was aborted or stopped, or because a failure occurred.

Effect The CIP subsystem cannot communicate with the network through the CLIM.

Recovery If the CLIM is in the STOPPED state, start the CLIM. If the problem was a hardware failure, replace the CLIM. Use the SCF STATUS CLIM command to check for a hardware connectivity problem. Otherwise, check event 5201 for possible a software failure, and correct the problem according to information in that event.

5204

005204 (Other) State Change CLIM Name: $ZZCIP.clim-name Event Number: CLIM state change Reason: reason Previous State: state Current State: state [ Text: text ]

`clim-name`	specifies the CLIM that had a state change.
`reason`	specifies the reason that the CLIM had a state change.
`state`	in the `Previous State` field, `state` specifies the state the CLIM was in before the state change. In the `Current State` field, `state` specifies the state of the CLIM after the state change.
`text`	provides additional information about the event.

Cause A CLIM changed from one state to another.

Effect If the CLIM is in the STARTED state, the system can access the network through the CLIM; otherwise, the CLIM is unavailable.

Recovery If the CLIM is in the STOPPED state, start the CLIM.

5205

005205 CLIM Configuration Change CLIM Name: $ZZCIP.clim-name Type: operation [ Reason: text ]

`clim-name`	specifies the CLIM that had a change in its configuration.
`operation`	indicates the type of configuration change operation that occurred; for example, Add object, Delete object start, Delete object complete, Alter object.
`text`	provides additional information about the configuration change.

This message is sometimes sent to $ZLOG only.

Cause A CLIM object has been added, deleted, or altered within the CIP subsystem and configuration database by an SCF [ ADD | DELETE | ALTER ] CLIM command.

Effect An attribute of the CLIM object has been altered (after the Alter object operation), a new CLIM object is available to the CIP subsystem (after an Add object operation), or the CLIM object is no longer in the CIP subsystem and configuration database (after a Delete object operation).

Recovery This is an informational message only; no corrective action is needed.

5206

005206 Bad Configuration Record for CLIM object: $ZZCIP.clim-name Severity: level, Error: record-error

[ Current Version = version1, Minimum Version = version2 Record Version = version3, Record Minimum Version = version4 ]

[ Header Length = header-length, Expected Length = expected-length ] [ Command State = state ] [ Location = clim-location ] [ Operation Mode = operation-mode ] [ Number of connection points per fabric = connpts ] [ First X-fabric Location = clim-location ] [ Associated Provider = provider-name ] [ CLIM type = clim-type ]

clim-name

specifies the CLIM that had a bad configuration record.

level

specifies this event as warning or fatal.

record-error

indicates the type of error within the configuration record.

version1

indicates the current version of the CIP subsystem configuration record.

version2

indicates the earliest version of the CIP subsystem configuration record that can be supported by the current CIPMAN process.

version3

indicates the version of CLIM configuration record.

version4

indicates the minimum version of CLIM configuration record that is compatible with the current CLIM configuration record.

header-length

indicates the length specified in the configuration record.

expected-length

indicates the length expected in the configuration record based on the actual size of the record.

state

specifies the command state the CLIM.

clim-location

indicates the CLIM location specified within the CLIM configuration record in these forms:

[group].[module].[slot].[port]

[For NonStop BladeSystem: group].[module].[slot].[port].[fiber]

svnet-id

indicates the base ServerNet address specified in the CLIM configuration record.

actual-svnet-id

indicates the actual base ServerNet address based on the CLIM location.

clim-type

indicates the type of CLIM specified in the CLIM configuration record.

operation-mode

indicates the operation mode of CLIM specified in the CLIM configuration record.

connpts

indicates the number of connection points per ServerNet fabric for the CLIM specified in the CLIM configuration record.

provider-name

indicates the PROVIDER specified in the CLIM configuration record to be associated with the CLIM.

clim-type

indicates the type of CLIM specified in the CLIM configuration record.

Cause The CIPMAN read CIP subsystem configuration database records during initialization and information in a CLIM record is either unusable or incorrect.

Effect If information is unusable (fatal error), then the CLIM object is not added to the CIP subsystem and that CLIM object cannot be used. Otherwise, a default value is used for the value that was not correct.

Recovery This is an informational message only; no corrective action is needed.

5207

005207 CLIM Access Gained CLIM Name: $ZZCIP.clim-name Processor: cpu Reason: reason [ Text: text ]

`clim-name`	specifies the CLIM that became accessible from a processor.
`cpu`	shows the processor that gained access to the CLIM.
`reason`	gives the reason the CLIM became accessible.
`text`	provides additional information about the event.

Cause A CLIM object was accessible from a processor.

Effect Data can be sent to and received from the network through the CLIM.

Recovery This is an informational message only; no corrective action is needed.

5208

005208 CLIM Access Lost CLIM Name: $ZZCIP.clim-name Processor: cpu Reason: reason Origin: source Severity: level Type Code: fault-code [ Type String: fault-text ] [ Text: custom-text ]

`clim-name`	specifies the CLIM that became inaccessible from a processor.
`cpu`	shows the processor that lost access to the CLIM.
`reason`	gives the reason the CLIM became inaccessible.
`source`	specifies where loss of access originated from. This field displays one of the following: Unrecognized Origin CIPMON CIPSREQ QIO Subsystem CIPSSRV NonStop Kernel CLIMAGT ITAPI DSM Subsystem NSK Configuration Routines CIP Manager Service Processor SCS CLIM GOOF
`level`	specifies this event as informational, warning, fatal, or unrecognized.
`fault-code`	is a number associated with this particular loss of access. If the access lost originated within the CIP subsystem, the event message also displays text. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes. If the access lost originated outside the CIP subsystem, the event message displays the error code received from the other subsystem or process.
`fault-text`	is a brief description of the cause of the loss of access. This field only appears if `fault-code` is associated with the CIP subsystem. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes.
`custom-text`	provides additional information describing the reason for the access lost.

Cause A CLIM object was inaccessible from a processor.

Effect The effect depends on the fault specified by the fault-code.

Recovery The recovery depends on the fault specified by the fault-code. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes.

5209

005209 CLIM Hardware Connectivity Change CLIM Name: $ZZCIP.clim-name Connectivity on fabric at location clim-location has changed

[ Status: connected to CLIM hardware hardware-id | Status: no connectivity | Status: port not configured for CLIM connectivity | Status: CLIM is not configured to be connected at this location | Status: CLIM is not configured to be connected to this system | Status: operation mode of CLIM does not match expected value | Status: number of connection points for CLIM does not match expected value | Status: location is not supported for CLIM connectivity on this system | Status: unknown connection status | Status: unrecognized connection status = conn-status-val ]

[ Text: text ]

clim-name

specifies the CLIM whose hardware connectivity has changed.

fabric

identifies the ServerNet fabric (X or Y) over which connectivity to the CLIM has changed:

1	X-Fabric
2	Y-Fabric
4	Fabric-Unknown

clim-location

indicates the location where the hardware connectivity has changed, shown in either of these forms:

[group].[module].[slot].[port]

For NonStop BladeSystem: [group].[module].[slot].[port].[fiber]

hardware-id

provides information about the specific hardware currently connected at the specified location.

conn-status-val

provides numerical value of connection status.

text

provides additional information about the event.

Cause Connectivity with a CLIM object at one specific location has changed.

Effect If CLIM is now connected, it can now be accessed over the specified fabric. Otherwise, the CLIM cannot be accessed over the specified fabric/location.

Recovery If CLIM is not connected or non-CLIM is connected at the specified location, then you must make sure that the correct CLIM is connected at the specified location and that the CLIM and the ServerNet switch are configured correctly.

5210

005210 CLIM Hardware Available CLIM Name: $ZZCIP.clim-name CLIM is now [partially] physically available Hardware ID: hardware-id

[ Text: text ]

`clim-name`	specifies the CLIM that became physically available at the configured location.
`hardware-id`	provides information about the specific CLIM hardware available.
`text`	provides additional information about the event.

Cause A CLIM hardware is now available at the configured location.

Effect The specified CLIM object can now be accessed.

Recovery This is an informational message only; no corrective action is needed.

5211

005211 CLIM Hardware Unavailable CLIM Name: $ZZCIP.clim-name CLIM is now unavailable Reason: reason

[ Text: text ]

clim-name

specifies the CLIM that became unavailable (due to physical connectivity problem).

reasons

provides reason CLIM is now unavailable:

2	Not connected.	No devices connected at configured location.
4	Different devices on different connection points.	Different devices are connected on different connection points corresponding to the same configured location.
7	Connectivity status unknown.	Connectivity status is unknown.
9	Connection problem on one or more connection points.	Different devices are connected at different connection points corresponding to the same configured location.

text

provides additional information about the event.

Cause A configured CLIM object is now unusable due to a problem with hardware connectivity. This can be caused by no CLIM connected at the configured location, different devices connected on different fabrics corresponding to the same configured location, or other connectivity problems.

Effect The specified CLIM object cannot be accessed.

Recovery Make sure that the correct CLIM hardware is connected at the correct locations and that the CLIM and the ServerNet switch are configured correctly.

5212

005212 CLIM Link Pulse Up CLIM Name: $ZZCIP.clim-name Interface interface-name link pulse is [ persistently ] up

`clim-name`	specifies the CLIM that has a change in link pulse status for one of its interfaces.
`interface-name`	specifies the specific interface within the specified CLIM that has its link pulse status changed to UP state.

Cause CLIM reported that link pulse status of one of its interfaces is now up.

Effect This error can communicate with the TCP/IP network through that interface.

Recovery This is an informational message only; no corrective action is needed.

5213

005213 CLIM Link Pulse Down CLIM Name: $ZZCIP.clim-name Interface interface-name link pulse is [ persistently ] down

`clim-name`	specifies the CLIM that has a change in link-pulse status for one of its interfaces.
`interface-name`	specifies the specific interface within the specified CLIM that has its link-pulse status changed to the DOWN state.

Cause The CLIM reported that the link pulse status of one of its interfaces is now down, most likely from the loss of physical connectivity between that interface and the network.

Effect The CLIM cannot communicate with the TCP/IP network through that interface.

Recovery Check the physical connection between the CLIM and the network.

5214

005214 CLIM Interface Up CLIM Name: $ZZCIP.clim-name Interface interface-name is available

`clim-name`	specifies the CLIM that has a change in one of its interface's status.
`interface-name`	specifies the interface within the specified CLIM that has changed to operational.

Cause The CLIM reported that one of its interfaces is now operational.

Effect The CLIM can be made to communicate with the network via this interface. If resources associated with this interface are already running on the failover interface, the resources will stay on the failover interface until the failover interface fails or you issue a SWITCH CLIM request to move the resources back to the home interface. If resources associated with this interface are not active anywhere, the CIP subsystem automatically attempts to bring up the resources on this interface and enable communication with the network via this interface.

Recovery This is an informational message only; no corrective action is needed.

5215

005215 CLIM Interface Down CLIM Name: $ZZCIP.clim-name Interface interface-name is down [ reason ]

`clim-name`	specifies the CLIM that has a change in one of its interface's status.
`interface-name`	specifies the specific interface within the specified CLIM that has changed to DOWN state.
`reason`	specifies the specific reason the CLIM has changed to DOWN state.

Cause The CLIM reported that one of its interfaces is now down.

Effect The CLIM cannot communicate with the TCP/IP network via that interface. If this interface is configured for failover and the interface is not brought down by you, the CIP subsystem will automatically attempt to move all resources associated with this interface over to the failover interface, if possible. If the interface is brought down by you, no failover attempt is made.

Recovery Bring that interface back up if it is needed.




	NOTE: The operation to bring interface back up must be done on the CLIM and cannot be done on the NonStop server.

5216

005216 CLIM CIPSSRV Process Down CLIM Name: $ZZCIP.clim-name CIPSSRV process cipssrv-id has gone down

`clim-name`	specifies the CLIM that has lost one of its CIPSSRV process.
`cipssrv-id`	is the identifier for the specific CIPSSRV process within the specified CLIM that has gone down.

Cause The CLIM reported that one of its CIPSSRV processes has gone down.

Effect The CLIM cannot make socket connections across the network. The CLIM brings down all socket connections on that CLIM and then restarts all CIPSSRV processes.

Recovery None. This is an informational event. The CLIM should automatically recover. If the CLIM does not become operational within a reasonable amount of time, check to make sure that all CIP subsystem software is running properly on that CLIM.

5218

005218 CLIM Physical Interface Detected CLIM Name: $ZZCIP.clim-name Interface interface-name is detected

`clim-name`	is the CLIM that has a change in one of its physical interface’s status.
`interface-name`	is the specific detected interface physical within the specified CLIM.

Cause The CLIM reported that one of its physical interfaces is detected and is now available.

Effect That physical interface is now available for use.

Recovery This is an informational message only; no corrective action is needed.

5219

005219 CLIM Physical Interface Removed CLIM Name: $ZZCIP.clim-name Interface interface-name is removed

`clim-name`	is the CLIM that has a change in one of its physical interface’s status.
`interface-name`	is the specific physical interface within the specified CLIM that has been removed.

Cause The CLIM reported that one of its physical interfaces is removed and is now completely unavailable.

Effect The physical interface is now completely unavailable and will no longer be shown.

Recovery Determine the problem with the physical interface (probably a hardware problem), and then fix the problem.




	NOTE: The operation to bring physical interface back up must be done on the CLIM; the operation cannot be done on the NonStop system.

5220

005220 CLIM Interface Bring Up Problem CLIM Name: $ZZCIP.clim-name Interface interface-name bring up was unsuccessful [ Reason: reason ]

`clim-name`	is the CLIM in which an interface was unable to be brought up successfully.
`interface-name`	is the specific interface that has problem being brought up.
`reason`	is the specific reason the CLIM was unable to bring up the interface.

Cause The CLIM reported that it was not able to bring up one of its interfaces.

Effect CLIM cannot communicate with the TCP/IP network via that interface.

Recovery If the problem persists and interface remains unavailable for an extended period of time, try to identify the cause of the problem and fix the problem on the CLIM.




	NOTE: The operation to fix interface problem is most likely have to be done on the CLIM and not on the NonStop system.

5221

005221 CLIM Interface Failover Initiated Interface interface-name is being moved from CLIM clim-name to CLIM Reason: reason

`interface-name`	is the specific interface that is being moved from one CLIM to a different CLIM.
`clim-name`	is the CLIM where the interface original resided.
`reason`	is the reason for failover; for example, interface failure, CLIM access failure, or operator initiated.

Cause An interface is being moved from one CLIM to a different CLIM because of an operator request or failure of either the original CLIM or the interface on the original CLIM.

Effect The interface is no longer accessible from the original CLIM.

Recovery This is an informational message only; no corrective action is needed.

5222

005222 CLIM Interface Failover Success CLIM Name: $ZZCIP.clim-name Interface interface-name move to CLIM clim-name is successful

`clim-name`	is the CLIM where the interface is currently running on because of failover.
`interface-name`	is the specific interface being brought up on a CLIM because of a failover operation.

Cause An interface is brought up successfully on a new CLIM as part of a failover operation.

Effect The CLIM can communicate with the TCP/IP network via that interface.

Recovery This is an informational message only; no corrective action is needed.

5223

005223 CLIM Interface Failover Problem CLIM Name: $ZZCIP.clim-name Interface interface-name move to CLIM clim-name fail [ Reason: reason ]

`clim-name`	is the specific interface being brought up on a CLIM because of a failover operation.
`interface-name`	is the CLIM where the interface tries to run.
`reason`	is the specific reason for the interface bring-up failure.

Cause The CLIM reported that it was not able to bring up the failover interface.

Effect The CLIM cannot communicate with the TCP/IP network via that interface.

Recovery If the problem persists and interface remains unavailable for an extended period of time, try to identify the cause of the problem and fix the problem on the CLIM.




	NOTE: The operation to fix interface problem probably has to be done on the CLIM and not on the NonStop system.

5224

005224 CLIM Interface Recovery Complete CLIM Name: $ZZCIP.clim-name Interface interface-name is successfully brought up

`clim-name`	is the CLIM where an interface is brought up successfully.
`interface-name`	is the specific interface that is brought up successfully after previous failures.

Cause The CLIM reported that it was able to bring up one of its interfaces after previous failures.

Effect The CLIM can communicate with the TCP/IP network via that interface.

Recovery This is an informational message reporting successful recovery from event 5220 and or 5223; no corrective action is needed.

5225

005225 CLIM Interface Failover Config Invalid CLIM Name: $ZZCIP.clim-name Failover configuration for interface interface-name is invalid Reason: reason

clim-name

is the CLIM where an interface is configured with the failover configuration that is invalid.

interface-name

is the specific interface that has the invalid failover configuration.

reason

is the specific reason that the failover configuration of the interface is invalid. Reasons include:

Failover interface does not exist	The CLIM or the interface is not present on the CLIM.
Failover interface does not support failover.	Slave or tunnel interface.
Failover interface not associated with Provider	The failover interface is in a different PROVIDER.
Home and failover interface do not form a pair	The interfaces are not configured as brothers; for example, the failover interface configures a different interface as its failover interface.
Failover interface is already in use by another interface	Cannot configure interface as a failover interface for more than one interface.
Tunnel interface name already in use on the failover CLIM.	Another tunnel interface already has the same interface name as this tunnel interface on the failover CLIM.
Failover CLIM has an incorrect interface configuration	The failover CLIM does not have either a configuration of its interface or a different version of the configuration from the last known version.

Cause The failover configuration of the specified interface is invalid.

Effect The specified interface cannot be failed over.

Recovery Correct the failover configuration of the specified interface. Make this correction on the CLIM; the correction cannot be done on the NonStop system.

If the reason is “failover CLIM has incorrect configuration,” make sure that the failover CLIM has the latest configuration and that the home CLIM for that interface has been brought to the STARTED state at least once since the last configuration change on the home CLIM.

5226

005226 CLIM Interface Failover Config OK CLIM Name: $ZZCIP.clim-name Failover configuration for interface interface-name is now valid

`clim-name`	is the CLIM where an interface is configured with the failover configuration that was previously invalid.
`interface-name`	is the specific interface that previously had the invalid failover configuration and is now OK.

Cause The CIP subsystem reports that an interface that previously could not be failed over because of an invalid failover configuration now has a valid failover configuration and can be failed over.

Effect The specified interface can now be failed over if the failover interface is available.

Recovery This is an informational message reporting successful recovery from event 5225; no corrective action is needed.

5227

005227 CLIM Event CLIM Name: $ZZCIP.clim-name [ Logged by CLIM at: clim-time ] event-detail

`clim-name`	is the CLIM where an event is generated.
`clim-time`	is the time on the CLIM where this event is generated.
`event-detail`	describes the event occurred on the CLIM.

Cause An event logged on the CLIM’s evlog (an event log). The event described the cause.

Effect None. These events are informational.

Recovery For informational events, no corrective action is necessary. Check the events that indicate problem on the CLIM hardware or software.




	NOTE: The operation to fix a problem (if any) must to be done on the CLIM and not on the NonStop system.

5228

005228 CLIM Interoperability Error. The version of a CIP component on CLIM Name: $ZZCIP.clim-name is not compatible with the version of other actively running CIP components.

clim-name

is the CLIM that contains the offending component.

Cause The CIP subsystem has detected that the named CLIM contains a component that is not compatible with other actively running components on the NonStop host or other CLIMs.

Effect The CLIM on which the offending component is detected will remain offline until the indicated interoperability problem is fixed.

Recovery To recover, the operator needs to appropriately update the offending CLIM or the NonStop host and other active CLIMs for the whole CIP subsystem to be fully interoperable.

NOTE: You can obtain the CLIM software version by entering:

climcmd clim-name cat/etc/vproc

5230

005230 CLIM Duplicate Address Detected Reporting CLIM Name: $ZZCIP.clim-name Address Type: address-type event-detail Logged by CLIM at: clim-time

`clim-name`	is the CLIM which detected the duplicate address.
`address-type`	is the type of the duplicate address that has been detected. Duplicate IP address— Duplicate IP address has been detected within the same network. Duplicate MAC address— Duplicate MAC address has been detected within the same network.
`event-detail`	is the duplicate address in detail detected by the CLIM.
`clim-time`	is the time-stamp on the CLIM when the duplicate address was detected.

Cause A duplicate address within the same network has been detected by the CLIM. The reported address has already been used on the same network.

Effect Depends on the address type specified in address-type

Duplicate IP address— Potential loss of network connectivity for sockets using the source IP address.
Duplicate MAC address— Loss of network connectivity through the interface with the MAC address.

Recovery Check network configuration for the entire network to identify the actual root cause of the problem. If necessary, reconfigure the interface on the CLIM that is associated with the duplicate address.




	NOTE: The problem (if any) should be fixed on the CLIM and not on the NonStop system. This event is present in both $ZLOG and $0. Emphasis should be ON.

5231

005231 CLIM Debug Info Collection Event CLIM Name: $ZZCIP.clim-name event-detail Initiated by NonStop user: nonstop-user-id

`clim-name`	is the CLIM from which the debug information is collected.
`event-detail`	is the complete command syntax of the CLIMDBUG tool invocation along with the completion code of the command. A non-zero completion code indicates that the command failed.
`nonstop-user-id`	is the ID of the NonStop user who initiated the request (Safeguard alias or the NonStop user ID).

Cause Invocation of CLIMDBUG tool by any NonStop SUPER group user which results in either success or failure scenario.

Effect Creation of PAK file on the NonStop host which contains the .tgz files present in the /home/debuginfo/directory on the CLIM. For successful invocations, the transferred .tgz files get deleted from the CLIM.

Recovery For informational events, no corrective action is necessary.

5232

005232 CLIMIPTABLES Log Message Reporting CLIM Name: $ZZCIP.clim-name event-detailLogged by CLIM at: clim-time

`clim-name`	is the CLIM from which the iptables log message is generated.
`event-detail`	describes the log message generated by iptables.
`clim-time`	specifies the time on the CLIM when the log message is generated.

Cause A log message generated by a CLIM when the user sets the LOG option for a rule using the CLIMIPTABLES utility.

Effect None. The log message displays information on a packet that matches the rule. It is generally for informational purposes.

Recovery For informational events, no corrective action is necessary.




	NOTE: This operation occurred on the CLIM, not on the NonStop system.

5233

005233 CLIM Interface Association Invalid CLIM Name: $ZZCIP.clim-name Interface interface-name association with PROVIDER prov-name is not valid Reason: reason

`clim-name`	is the CLIM where an interface is configured with a PROVIDER that does not exist or is not an IPDATA PROVIDER.
`interface-name`	is the specific interface that has an invalid PROVIDER association.
`prov-name`	is the PROVIDER name currently associated with the specified interface.
`reason`	is the specific reason the associated PROVIDER of the interface is not valid. This includes: PROVIDER does not exist Not an IPDATA PROVIDER

Cause The specified interface does not have an association with a valid IPDATA PROVIDER.

Effect Specified interface cannot be used.

Recovery Correct the configuration of the specified interface or add the missing IPDATA PROVIDER on the NonStop system. Interface configuration must be performed on the CLIM using the climconfig command, and cannot be performed on the NonStop system.

5234

005234 CLIM Interface Association OK CLIM Name: $ZZCIP.clim-name Interface interface-name is now associated with a valid IPDATA PROVIDER prov-name

`clim-name`	is the CLIM where an interface was previously configured with a PROVIDER that did not exist or was not an IPDATA PROVIDER.
`interface-name`	is the specific interface that previously had an invalid PROVIDER association which is now OK.
`prov-name`	is the IPDATA PROVIDER name currently associated with the specified interface.

Cause The CIP subsystem reports an interface which previously could not be used due to an invalid PROVIDER association is now associated with a valid IPDATA PROVIDER and can be used.

Effect Specified interface can now be used.

Recovery None. This is an informational event reporting successful recovery from event 5233.

5235

005235 CLIM MultiProv Configuration Conversion CLIM Name: $ZZCIP.clim-name event-detail Logged by CLIM at: clim-time

`clim-name`	is the CLIM whose configuration is being converted.
`event-detail`	describes the type of conversion being performed and indicates whether the operation succeed or failed.
`clim-time`	specifies the time on the CLIM when this CLIM configuration conversion was initiated.

Cause An attempt to convert the CLIM configuration to match what is configured on NSK. Turn support for MULTIPROV (association with multiple providers on the same CLIM) ON or OFF.

Effect If the conversion attempt succeeded, these events are informational about changes in the CLIM configuration. However, if the conversion attempt failed, CLIM might not come to a STARTED state.

Recovery If the conversion attempt is successful, none. If the conversion attempt failed, verify that the configuration on the CLIM is consistent with the configuration of the CLIM object on the NonStop system. In particular, if the CLIM is configured on the NonStop system with MULTIPROV set to OFF, all network resources on the CLIM must not be associated with any specific PROVIDER or all network resources on the CLIM must be associated with the IPDATA PROVIDER specified by the PROVIDER attribute of the CLIM object.




	NOTE: The operation occurred on the CLIM and not on the NonStop system, although it is controlled by the NonStop system configuration.

5239

005239 CLIM Authentication Event CLIM Name: clim-time [ Logged by CLIM at: clim-time ] event-detail

`clim-name`	is the CLIM where the event is generated.
`clim-time`	is the time on the CLIM where this event is generated.
`event-detail`	describes the authentication event that occurred on the CLIM.

Cause An authentication event related to the login activity is logged on the CLIM’s evlog (event log). The event-detail describes this event. This event indicates the login activity on the CLIM, not on the NonStop system.

Effect None. These events are informational.

Recovery For informational events, no corrective action is necessary.




	NOTE: This event is logged under the EMS collector $ZCLA which is available from RVU J06.16 onwards.

5301

005301 PROVIDER Transient Fault PROVIDER Name: $ZZCIP.provider-name Origin: source Severity: level Type Code: fault-code [ Type String: fault-text ] [ ErrorDetail1: optional-value (optional-value-hex) ] [ ErrorDetail2: optional-value (optional-value-hex) ] [ ErrorDetail3: optional-value (optional-value-hex) ] [ ErrorDetail4: optional-value (optional-value-hex) ] [ ErrorDetail5: optional-value-hex ] [ Text: custom-text ] [ Manager: manager-name ]

`provider-name`	specifies the PROVIDER where the transient fault occurred.
`source`	specifies where the transient fault originated from. This field displays one of: Unrecognized Origin CIPMON CIPSREQ QIO Subsystem CIPSSRV NonStop Kernel CLIMAGT ITAPI DSM Subsystem NSK Configuration Routines CIP Manager Service Processor SCS CLIM GOOF
`level`	specifies this event as informational, warning, fatal, or unrecognized.
`fault-code`	provides a number associated with this particular transient fault. If the transient fault originated within the CIP subsystem, the event message also displays text. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes. If the transient fault originated outside the CIP subsystem, the event message displays the error code received from the other subsystem or process.
`fault-text`	provides a brief description of the cause of the transient fault. This field only appears if `fault-code` is associated with the CIP subsystem. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes.
`optional-value`	is additional information about the event.
`optional-value-hex`	is additional information about the event in hex format.
`custom-text`	provides additional information about the event.
`manager-name`	specifies the parent CIPMAN process for the PROVIDER.

Cause A PROVIDER encountered a fault.

Effect The effect depends on the fault specified by fault-code.

Recovery The recovery depends on the fault specified by fault-code. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes.

5302

005302 Object Available PROVIDER Name: $ZZCIP.provider-name Event Number: PROVIDER available Reason: reason Previous State: state Current State: state [ Text: text ]

`provider-name`	specifies the PROVIDER that became available.
`reason`	specifies the reason that the PROVIDER became available.
`state`	in the `Previous State` field, `state` specifies the state the PROVIDER was in before becoming available. In the `Current State` field, `state` specifies the state of the PROVIDER after it became available.
`text`	provides additional information about the event.

Cause A PROVIDER became available and the CIP subsystem can access it.

Effect The system can access the PROVIDER.

Recovery This is an informational message only; no corrective action is needed.

5303

005303 Object Unavailable PROVIDER Name: $ZZCIP.provider-name Event Number: PROVIDER unavailable Reason: reason Previous State: state Current State: state [ Text: text ]

`provider-name`	specifies the PROVIDER that became unavailable.
`reason`	specifies the reason that the PROVIDER became unavailable.
`state`	in the `Previous State` field, `state` specifies the state the PROVIDER was in before becoming unavailable. In the `Current State` field, `state` specifies the state of the PROVIDER after it became unavailable.
`text`	provides additional information about the event.

Cause CIP subsystem cannot access the PROVIDER because the PROVIDER was aborted or stopped, or because a failure occurred.

Effect The CIP subsystem cannot communicate with the network through the PROVIDER.

Recovery Start the PROVIDER. Make sure the associated CLIM object is available.

5304

005304 (Other) State Change PROVIDER Name: $ZZCIP.provider-name

Event Number: PROVIDER state change

Reason: reason

Previous State: state

Current State: state

[ Text: text ]

`provider-name`	specifies the PROVIDER that had a state change.
`reason`	specifies the reason that the PROVIDER had a state change.
`state`	in the `Previous State` field, `state` specifies the state the PROVIDER was in before the state change. In the `Current State` field, `state` specifies the state of the PROVIDER after the state change.
`text`	provides additional information about the event.

Cause A PROVIDER changed from one state to another.

Effect If the PROVIDER is in the STARTED state, the system can access the network through the PROVIDER; otherwise, the PROVIDER is unavailable.

Recovery If the PROVIDER is in the STOPPED state, start the PROVIDER.

5305

005305 PROVIDER Configuration Change PROVIDER Name: $ZZCIP.provider-name Type: operation [ Reason: text ]

`provider-name`	specifies the PROVIDER that had a change in its configuration.
`operation`	indicates the type of configuration change operation that occurred, for example: Add object Delete object Start object complete Delete object complete Alter object
`text`	provides additional information about the configuration change.

Effect The attribute of the PROVIDER object has been altered. After the Alter object operation, including command state change through an SCF START/STOP/ABORT PROVIDER command, a new PROVIDER object is available to the CIP subsystem (Add object operation), or the PROVIDER object is no longer in the CIP subsystem and configuration database (Delete object operation).

Recovery This is an informational message only; no corrective action is needed.

5306

005306 Bad Configuration Record for PROVIDER object: $ZZCIP.provider-name Severity: level, Error: record-error

[ Current Version = version1, Minimum Version = version2 Record Version = version3, Record Minimum Version = version4 ]

[ Header Length = header-length, Expected Length = expected-length ] [ Command State = state ] [ Provider Type = provider-type ] [ TP Name = tp-name ] [ Hostname = host-name ] [ Associated CLIM = clim-name ] [ IP Address = ip-address ] [ Number of Share Ports = share-ports ] [ IP Address Family = family ] [ TCP Listen Queue Min = listen-queue ] [ BRecvPort (port-index) = brecv-port ]

`provider-name`	specifies the PROVIDER that had a bad configuration record.
`level`	specifies this event as warning or fatal.
`record-error`	indicates the type of error within the configuration record.
`version1`	indicates the current version of the CIP subsystem configuration record.
`version2`	indicates the earliest version of the CIP subsystem configuration record that the current CIPMAN process can support.
`version3`	indicates the version of PROVIDER configuration record.
`version4`	indicates the minimum version of PROVIDER configuration record that is compatible with the current PROVIDER configuration record.
`header-length`	indicates the length specified in the configuration record.
`expected-length`	indicates the length expected in the configuration record based on the actual size of the record.
`state`	specifies the command state the PROVIDER.
`provider-type`	indicates the type of Provider specified in the PROVIDER configuration record.
`tp-name`	indicates the name of the Transport Provider process associated with the PROVIDER object as specified in the PROVIDER configuration record.
`host-name`	indicates the host name associated with the PROVIDER object as specified in the PROVIDER configuration record.
`clim-name`	indicates the CLIM specified in the PROVIDER configuration record to be associated with the PROVIDER.
`ip-address`	indicates the IP address specified in the PROVIDER configuration record to be associated with the PROVIDER.
`share-ports`	indicates the number of share ports specified in the PROVIDER configuration record.
`family`	indicates the IP address family associated with the PROVIDER object as specified in the PROVIDER configuration record.
`listen-queue`	indicates the minimum TCP listen queue depth specified in the PROVIDER configuration record.
`port-index`	indicates the offset of UDP broadcast receive port specified in the PROVIDER configuration record that is in error
`brecv-port`	indicates the UDP broadcast receive port number specified in the PROVIDER configuration record that is in error.

Cause When CIPMAN reads CIP subsystem configuration database records during initialization, information in a PROVIDER record is either unusable or incorrect.

Effect If information is unusable (fatal error), then the PROVIDER object is not added to the CIP subsystem and that PROVIDER object cannot be used. Otherwise, a default value is used for the value that was not correct.

Recovery This is an informational message only; no corrective action is needed.

5307

005307 CIPLIB Trace Buffer Full, TrcRec: trace-record-type, Size: record-size

trace-record-type

is the record type being traced when the buffer full condition was detected. The record type can be one of these values:

161	Logic record
162	EMS event record
163	Protocol request received record
164	Protocol request sent record
165	Data received record
166	Data sent record

record-size

is the size of the trace record.

Cause The trace buffer for the PROV object is full.

Effect Tracing for the PROV will be stopped.

Recovery This is an informational message only; no corrective action is needed.

5308

005308 PROVIDER Inconsistent Configuration PROVIDER Name: $ZZCIP. prov-name TCP/IP Configuration of CLIMs associated with PROVIDER are inconsistent [ Text: text]

`prov-name`	specifies the PROVIDER that is associated with multiple CLIMs with inconsistent TCP/IP parameters.
`text`	provides additional information about the event.

Cause TCP/IP parameters of different CLIMs associated with the specified PROVIDER are not consistent with one another.

Effect Unable to create a new socket associated with the specified PROVIDER.

Recovery Check TCP/IP configurations of CLIMs associated with the specified PROVIDER and make sure that they are consistent with each other. Note: The operation to fix the TCP/IP configuration problem must be done on the CLIM and not on the NonStop host.

5309

005309 PROVIDER Configuration Resolved PROVIDER Name: $ZZCIP.prov-name TCP/IP Configuration of CLIMs associated with PROVIDER are OK

prov-name

specifies the PROVIDER.

Cause TCP/IP parameters of CLIM(s) associated with the specified PROVIDER are now consistent with one another.

Effect New socket associated with the specified PROVIDER can be created when PROVIDER is in STARTED state.

Recovery None. This is an informational event.

5321

005321 CIPLIB Send Data Failed, So: socket, Err: error, Func: cip-protocol-message-function

socket

is the address of the socket control block.

error

is the error returned from the send operation.

cip-protocol-message-function

is the CIP protocol message function. The CIP protocol message functions are.

0x01	DATA_FUNC_ACCEPTED, Incoming connection accepted.
0x02	DATA_FUNC_BIND, Bind.
0x03	DATA_FUNC_CLOSE, Close.
0x04	DATA_FUNC_CONNECT, Connect.
0x05	DATA_FUNC_CREATE_SOCKET, Create socket.
0x06	DATA_FUNC_GETSOCKOPT, GETSOCKOPT.
0x07	DATA_FUNC_INCOMING_REQ, Incoming connection.
0x08	DATA_FUNC_IOCTL, IOCTL.
0x09	DATA_FUNC_LISTEN, Listen.
0x0a	DATA_FUNC_SOCKET_MIGRATED, Socket migrated.
0x0b	DATA_FUNC_SOCKET_PREP_MIGRATE, Prepare to migrate.
0x0c	DATA_FUNC_RECV_DATA, Data for RECV request.
0x0d	DATA_FUNC_RECVFROM_DATA, Data for a RECVFROM request.
0x0e	DATA_FUNC_RECVMSG_DATA, Data for a RECVMSG request.
0x0f	DATA_FUNC_SETSOCKOPT, Setsockopt.
0x10	0x10 - DATA_FUNC_SHUTDOWN, Shutdown.
0x11	DATA_FUNC_SOCKET_ERROR, Socket operation error.
0x12	DATA_FUNC_SOCKET_SEND, SEND data request.
0x13	DATA_FUNC_SOCKET_SENDTO, SENDTO data request.
0x14	DATA_FUNC_SOCKET_SENDMSG, SENDMSG data request.
0x15	DATA_FUNC_ACCEPT_MORE.
0x16	DATA_FUNC_BYTES_RECVD, Byte count update for received data.
0x17	DATA_FUNC_BYTES_SENT, Byte count update for data sent.
0x18	DATA_FUNC_CONNECT_NSK, Connect.
0x19	DATA_FUNC_CONNECT_COMPLETED, Connect completed.
0x100	DATA_FUNC_PORT_RESERVATION, Port reservation.
0x101	DATA_FUNC_PORT_INUSE, Port reservation in use.
0x102	DATA_FUNC_PORT_FREE, Port reservation free.
0x103	DATA_FUNC_PORT_TABLE_UPDATE, Port reservation update.
0x104	DATA_FUNC_RESET_CONNECT, Reset connection.
0x105	DATA_FUNC_MULTICAST, Multicast configuration update.

Cause A send data operation for a socket failed with the specified error code. Possibly the communication link between the host and the CLIM went down.

Effect An EIO error will be returned to the application as an indication that the send operation failed.

Recovery This is an informational message only; no corrective action is needed.

5322

005322 CIPLIB Send Socket Err Failed, Err: error, Func: cip-protocol-message-function, So Err: socket-error, Clim Hndl clim-socket-handle

`error`	is the error code for the send operation.
`cip-protocol-message-function`	is the CIP protocol message function.
`socket-error`	is the socket error detected when processing the CIPPROTO message response.
`clim-socket-handle`	is the internal identifier for the CLIM socket.

Cause CIP detected an error condition while processing a CIPPROTO message response. The error condition required that a CIPPROTO socket error message be sent to the CLIM. The send operation failed. Possibly while processing a CIPPROTO message response, CIP cannot find the host socket specified in the response. Also, a typical error condition for the send failure is communication between the host and the CLIM is lost.

Effect None.

Recovery This is an informational message only; no corrective action is needed.

5323

005323 CIPLIB MD Get Failed, So: socket, Err: allocation-error, Size: allocation-size, Parm: cip-protocol-message-function

`socket`	is the address of the socket control block.
`allocation-error`	is the error returned by SM_MD_GET_( ).
`allocation-size`	is the requested size of the MD.
`cip-protocol-message-function`	is the CIP protocol message function.

Cause Allocation of an MD (message buffer descriptor) to send a protocol message from the host to the CLIM failed. A typical cause is insufficient QIO memory space.

Effect An ENOMEM error will be returned to the application.

Recovery This is an informational message only; no corrective action is needed.

5324

005324 CIPLIB Data In MD Get Failed: So socket, Func cip-protocol-message-function, Len length

`socket`	is the address of the socket control block.
`cip-protocol-message-function`	is the CIP protocol message function.
`length`	is the requested size for the data.

Cause Allocation of an MD (message buffer descriptor) for a data message from the CLIM failed. A typical cause is insufficient QIO memory space.

Effect An ENOSPC error will be returned to the application.

Recovery This is an informational message only; no corrective action is needed.

5326

005326 CIPLIB Send To Global Q Failed, Class: message-class, Type: request-type, CPU Mask: cpu-mask-value, CPU Rem: cpu-mask-value

message-class

is the migration request class. Possible values are:

2	monSocketMigrClass, Socket migration class

request-type

is the migration request type. Possible values are:

1	SockMigr_Who_Has_Req, request to start a migration for accept_nw2 or accept_nw3 request
2	SockMigr_Req, migration response to a SockMigr_Who_Has_Req
3	SockMigr_Cont_Req, migration response to a SockMigr_Who_Has_Req with more socket data
4	SockMigr_Acc4Req, migration auto accept request
5	SockMigr_Acc4Rep, migration auto accept reply
6	SockMigr_Acc4Cancel, migration auto accept 4 cancel request
7	SockMigr_Acc4Rep_Error, migration auto accept error reply
8	SockMigr_Acc4Con_Rep, migration auto accept continue reply
9	SockMigr_OSS_Req, socket operation to be performed in owning the CPU
10	SockMigr_OSSCont_Req, continue OSS operation request
11	SockMigr_OSS_Rsp, OSS socket operation complete
12	SockMigr_OSSCont_Rsp, continue OSS operation replay
12	SockMigr_OSSCancel, cancel OSS operation

cpu-mask-value

is a bit map indicating the CPUs to which the migration request should be sent.

cpu-mask-value

is a bit map indicating the CPUs to which the send operation failed.

Cause A send operation to the Global Q failed for a migration request failed. A typical cause is that the target CPU for the send operation is down.

Effect The migration request will complete with an error, and the error will be returned to the application.

Recovery This is an informational message only; no corrective action is needed.

5327

005327 CIPLIB Proto Msg Len Invalid, Func: cip-protocol-message-function, Rcv: received-length, Exptd: expected-length

`cip-protocol-message-function`	is the CIP protocol message function.
`received-length`	is the received message length.
`expected-length`	is the expected message length.

Cause A CIPPROTO message was received from the CLIM and had a length that did not match the expected length for the CIPPROTO function. Possible causes of this error include a host software internal error about expecting an incorrect length, or a CLIM software internal error generating an incorrect length response.

Effect The CLIM will be aborted.

Recovery This is an informational message only; no corrective action is needed.

5328

005328 CIPLIB Proto Func Unknown, Func: cip-protocol-message-function, Len: length

`cip-protocol-message-function`	is the CIP protocol message function. For the defined values, see message 5321.
`length`	is the length of the message received.

Cause A CIPPROTO message was received from the CLIM with an unknown function code. A CLIM software internal error which resulted in an incorrect message being formatted could have occurred.

Effect The CLIM will be aborted.

Recovery This is an informational message only; no corrective action is needed.

5329

005329 CIPLIB Proto Func Expected, Func: CIP-protocol-message-function, Len: length

`cip-protocol-message-function`	is the CIP protocol message function.
`length`	is the length of the message received.

Cause A CIPPROTO message was received from the CLIM on the protocol path which was not expected. A CLIM software internal error which resulted in an incorrect message being formatted could have occurred.

Effect The CLIM will be aborted.

Recovery This is an informational message only; no corrective action is needed.

5330

005330 CIPLIB Invalid IP Addr Len, So: socket, Family: family, Rcvd: received-addr-len, Exptd: expected-addr-len

`socket`	is the address of the socket control block.
`family`	is the address family.
`received-addr-len`	is the received address length.
`expected-addr-len`	is the expected address length.

Cause The length of the IP address in a received CIPPROTO message was invalid. The length of the IP address did not match what was expected for the IP address family. A host software internal error expecting an incorrect length or a CLIM software internal error generating an incorrect length address could have occurred.

Effect An EINVAL error will be returned to the application.

Recovery This is an informational message only; no corrective action is needed.

5331

005331 CIPLIB So New Failed, So: listening-socket, Src hndl: clim-socket-handle, Err creation-error

`listening-socket`	is the address of the socket control block for the listening socket.
`clim-socket-handle`	is the internal identifier for the CLIM socket.
`creation-error`	is the size of the trace record.

Cause An incoming connection was received but a new socket for the incoming connection could not be created. A typical cause is insufficient memory in the host to allocate a socket control block.

Effect The incoming connection will be reset.

Recovery This is an informational message only; no corrective action is needed.

5332

005332 CIPLIB Send Proto Failed: So socket, Err error, Func cip-protocol-message-function, Cpu cpu, Pin pin

`socket`	is the address of the socket control block for the listening socket.
`error`	is the error returned for the send operation.
`cip-protocol-message-function`	is the CIP protocol message function.
`cpu`	is the CPU of the creator of the socket.
`pin`	is the PIN of the creator of the socket.

Cause A send data operation for a CIPPROTO message failed. Perhaps the communication link between the host and the CLIM went down.

Effect The current application request which triggered the CIPPROTO message to be sent will receive the error or the next application request will receive the error.

Recovery This is an informational message only; no corrective action is needed.

5333

005333 CIPLIB CLIM So Create Failed: So socket, Err error, Cpu cpu, Pin pin

`socket`	is the address of the socket control block.
`error`	is the socket creation error.
`cpu`	is the CPU of the creator of the socket.
`pin`	is the PIN of the creator of the socket.

Cause A CIPPROTO Socket create response was received with an error indicating that the creation of a socket on a CLIM failed.

Effect In a non-MCP environment, the creation error will be returned to the application. In an MCP environment, the error is returned to the application only if creation responses from all of the CLIMs' requests were sent to return an error. If one or more CLIMs returned a successful completion, the event indicates that the socket was not created on some of the CLIMs.

Recovery This is an informational message only; no corrective action is needed.

5352

005352 CIPLIB Socket Migration Unexpected, CPU: cpu, Port: ip-port ip-address

`cpu`	is the CPU of the originator of the request.
`ip-port`	is the IP port from the originator.
`ip-address`	is the IP address from the originator.

Cause A migration request was received for a socket that does not exist. A typical cause is that the socket was closed during the processing of the request.

Effect A error will be returned to the migration request. The application request that generated the migration request will be terminated with the error.

Recovery This is an informational message only; no corrective action is needed.

5401

005401 text

text

shows 12 different text strings depending on the detected error condition.

Cause A non-severe internal error was detected.

Effect The current operation will be terminated with an error. The error will be returned in the current outstanding application request or the next application request.

Recovery This is an informational message only; no corrective action is needed.

5501

005501 ROUTE Transient Fault ROUTE Name: $ZZCIP.prov-name.route-name Origin: source Severity: level Type Code: fault-code [ Type String: fault-text ] [ ErrorDetail1: optional-value (optional-value-hex) ] [ ErrorDetail2: optional-value (optional-value-hex) ] [ ErrorDetail3: optional-value (optional-value-hex) ] [ ErrorDetail4: optional-value (optional-value-hex) ] [ ErrorDetail5: optional-value-hex ] [ Text: custom-text ]

`prov-name`	is the parent PROVIDER for the ROUTE that had a bad configuration record.
`route-name`	is the ROUTE that had a bad configuration record.
`source`	specifies where the transient fault originated from. This field displays one of the following: Unrecognized Origin CIPMON CIPSREQ QIO Subsystem CIPSSRV NonStop Kernel CLIMAGT ITAPI DSM Subsystem NSK Configuration Routines CIP Manager Service Processor SCS CLIM GOOF
`level`	specifies this event as informational, warning, fatal, or unrecognized.
`fault-code`	is a number associated with this particular transient fault. If the transient fault originated within the CIP subsystem, the event message also displays text. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes. If the transient fault originated outside the CIP subsystem, the event message displays the error code received from the other subsystem or process.
`fault-text`	is a brief description of the cause of the transient fault. This field only appears if `fault-code` is associated with the CIP subsystem. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes.
`optional-value`	provides additional information about the event.
`optional-value-hex`	provides additional information about the event in hex format.
`custom-text`	provides additional information about the event.

Cause A ROUTE encountered a fault.

Effect The effect depends on the fault specified by fault-code.

Recovery The recovery depends on the fault specified by fault-code. See the Cluster I/O Protocols (CIP) Configuration and Management Manual for more information about the CIP fault codes.

5505

005505 ROUTE Configuration Change ROUTE Name: $ZZCIP.prov-name.route-name Type: operation [ Reason: text ]

`prov-name`	is the parent PROVIDER for the ROUTE that had a change in its configuration.
`route-name`	is the ROUTE that had a change in its configuration.
`operation`	indicates the type of configuration change operation that occurred; for example, Add object, Delete object start, or Delete object complete.
`text`	provides additional information about the configuration change.

Cause A ROUTE object has been added or deleted within the CIP subsystem and configuration database by an SCF [ ADD | DELETE ] ROUTE command.

Effect A new ROUTE object is available to the CIP subsystem (after the Add object operation), or the ROUTE object is no longer in the CIP subsystem and configuration database (after the Delete object operation).

Recovery This is an informational message only; no corrective action is needed.

5506

005506 Bad Configuration Record for ROUTE object: $ZZCIP.prov-name.route-name Severity: level, Error: record-error

[ Current Version = version1, Minimum Version = version2 Record Version = version3, Record Minimum Version = version4 ]

[ Header Length = header-length, Expected Length = expected-length ] [ Associated CLIM = clim-name ] [ Parent PROVIDER = prov-name ] [ IP Address Family = family ] [ Priority = priority ]

`prov-name`	is the parent PROVIDER for the ROUTE that had a bad configuration record.
`route-name`	is the ROUTE that had a bad configuration record.
`level`	specifies this event as warning or fatal.
`record-error`	indicates the type of error within the configuration record.
`version1`	indicates the current version of the CIP subsystem configuration record.
`version2`	indicates the earliest version of the CIP subsystem configuration record that can be supported by the current CIPMAN process.
`version3`	indicates the version of ROUTE configuration record.
`version4`	indicates the minimum version of ROUTE configuration record that is compatible with the current ROUTE configuration record.
`header-length`	indicates the length specified in the configuration record.
`expected-length`	indicates the length expected in the configuration record based on the actual size of the record.
`clim-name`	indicates the CLIM specified in the ROUTE configuration record to be associated with the ROUTE.
`family`	indicates the IP address family associated with the ROUTE object as specified in the ROUTE configuration record.
`priority`	indicates the priority of the ROUTE object as specified in the ROUTE configuration record.

Cause When CIPMAN reads CIP subsystem configuration database records during initialization, information in a ROUTE record is either unusable or incorrect.

Effect If information is unusable (fatal error), then the ROUTE object is not added to the CIP subsystem and that ROUTE object cannot be used. Otherwise, a default value is used for the value that was not correct.

Recovery This is an informational message only; no corrective action is needed.