Chapter 134 XIO (NonStop Kernel XIO) Messages

The messages in this chapter are generated by the NonStop Kernel XIO subsystem. The subsystem ID displayed by these messages includes XIO 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.

100

Adapter record with name adapter-name for SAC sac-name was not found in CONFIG.

`adapter-name`	is the name of the adapter that corresponds to the concerned SAC.
`sac-name`	is the SAC name used to locate the requested adapter.

Cause The XIO subsystem did not find the adapter record in CONFIG.

Effect The installed XIO module failed.

Recovery Confirm that the correct configuration file has been used. If the error persists, contact your service provider and provide all relevant information as follows:

The Event Management Service (EMS) logs
Description of the problem and accompanying symptoms
The configuration file used
Supporting documentation such as processor dump

101

SAC record for SAC sac-name was not found in CONFIG.

sac-name

is the SAC name that was requested.

Cause The XIO subsystem did not find the SAC record in the CONFIG.

Effect The XIO module install failed.

Recovery Confirm that the correct configuration file has been used. If the error persists, contact your service provider and provide all relevant information as follows:

The Event Management Service (EMS) logs
Description of the problem and accompanying symptoms
The configuration file used
Supporting documentation such as processor dump

102

There is a mismatch in the product-id of the controller sac-name as specified in the CONFIG config-product-id, and hardware inventory hwinv-product-id.

`sac-name`	is the SAC name of the controller in the CONFIG.
`config-product-id`	is the product ID of the controller in the CONFIG.
`hwinv-product-id`	is the product ID of the controller in the hardware inventory table.

Cause The XIO subsystem found that the product ID for the controller in CONFIG is different from that in the hardware inventory table.

Effect The XIO subsystem built the module based on the CONFIG information.

Recovery Confirm that the correct configuration file has been used. If the error persists, contact your service provider and provide all relevant information as follows:

The Event Management Service (EMS) logs
Description of the problem and accompanying symptoms
The configuration file used
Supporting documentation such as processor dump

103

Error in installing the ServerNet device handle for SAC sac-name.

sac-name

is the SAC name that was requested.

Cause ServerNet Services returned an error to the XIO subsystem in the process of installing a device handle.

Effect The device handle for this module is invalid. I/O cannot be done on this device.

Recovery This event indicates an error occurred in ServerNet Services. Contact your service provider and provide all relevant information as follows:

The Event Management Service (EMS) logs
Description of the problem and accompanying symptoms
The configuration file used
Supporting documentation such as processor dump

104

Error in installing ServerNetId snet-id for device handle dev-handle used by SAC sac-name.

`snet-id`	is the ServerNet ID number.
`dev-handle`	is the ServerNet device handle number.
`sac-name`	is the SAC name that was requested.

Cause ServerNet Services returned an error for setting ServerNet ID.

Effect The controller fails to do any I/O.

Recovery This event indicates an error occurred in ServerNet Services. Contact your service provider and provide all relevant information as follows:

The Event Management Service (EMS) logs
Description of the problem and accompanying symptoms
The configuration file used
Supporting documentation such as processor dump

105

XIOMON timed out on an icepack setup response for icepack with tnet id snet-id, device handle dev-handle on adapter adapter-name.

`snet-id`	is the Servernet ID number of the ICEPACK.
`dev-handle`	is the ServerNet device handle number.
`adapter-name`	is the adapter name that corresponds to the SAC in this error.

Cause The ICEPACK setup response timed out.

Effect The ICEPACK was not set up properly.

Recovery This event is generated as a result of a hardware problem. Check the indicated hardware. If the error persists, contact your service provider and provide all relevant information as follows:

The Event Management Service (EMS) logs
Description of the problem and accompanying symptoms
The configuration file used
Supporting documentation such as processor dump

106

Error in allocating space for module table having nnn entries.

nnn

is the number of entries in the module table where the space allocation error occurred.

Cause Error was detected during an attempt to expand a module table.

Effect New modules cannot be added to the existing module table.

Recovery Try to remove some files that are not used from CONFIG. If this event occurs frequently, contact your service provider and provide all relevant information as follows:

The Event Management Service (EMS) logs
Description of the problem and accompanying symptoms
The configuration file used
Supporting documentation such as processor dump

107

XIOMON failed to setup the packetizer; tnet id snet-id, device handle dev-handle on adapter adapter-name.

`snet-id`	is the ServerNet ID number of the ICEPACK.
`dev-handle`	is the ServerNet device handle number.
`adapter-name`	is the adapter name that corresponds to the SAC in this error.

Cause The XIOMON could not configure the ICEPACK.

Effect The ICEPACK was not set up properly.

Recovery This event is generated as a result of a hardware problem. Check the hardware indicated in this event. If the persists, contact your service provider and provide all relevant information as follows:

The Event Management Service (EMS) logs
Description of the problem and accompanying symptoms
The configuration file used
Supporting documentation such as processor dump

108

error-desc Adapter Name: adapter-name SLM Return Code: return-code SLM Error: error-detail CPU: cpu-number

`error-desc`	is a description of the error.
`adapter-name`	is the name of the adapter experiencing the error.
`return-code`	is the return code from the SCSI Lock Manager request.
`error-detail`	is the error detail from the SCSI Lock Manger request.
`cpu-number`	is the number of the CPU associated with the process that made the adapter configuration request that resulted in the error.

Cause The XIO subsystem was unable to acquire a lock on the adapter.

Effect Adapter configuration failed.

Recovery Contact your service provider and provide the following information:

The Event Management Service (EMS) logs
Description of the problem and accompanying symptoms
Supporting documentation such as a processor dump

109

error-desc [ ColInvoke return code: SCSI-return-code ] [ XIO return code: XIO-return-code ] [ SNet return code: ServerNet-return-code ] [ SNet NACK code: ServerNet-NACK-code ] [ SNet path: ServerNet-path ] [ CPU: CPU-number ] [ Colorado Reg Data0: register-data0 ] [ Colorado Reg Data1: register-data1 ] [ Colorado Reg Data2: register-data2 ] [ Colorado Reg Data3: register-data3 ] [ Colorado Reg Address0: register-address0 ] [ Colorado Reg Address1: register-address1 ] [ Colorado Reg Address2: register-address2 ] [ Colorado Reg Address3: register-address3 ]

`error-desc`	is a description of the error.
`SCSI-return-code`	is the SCSI MD return code resulting from the read or write request.
`XIO-return-code`	is the XIO return code resulting from the read or write request.
`ServerNet-return-code`	is the ServerNet return code resulting from the read or write request.
`ServerNet-NACK-code`	is the ServerNet NACK code resulting from the read or write request.
`ServerNet-path`	is the ServerNet path over which the read or write request was made.
`CPU-number`	is the number of the CPU associated with the error.
`register-data0 - register-data3` and`register-address0 - register-address3`	are adapter register data and pointers. There can be 4 sets of this information.

Cause The XIO subsystem was unable to configure hardware registers on the specified adapter.

Effect Adapter configuration failed.

Recovery This event is generated as a result of a hardware problem. Check the hardware indicated in this event. If the error persists, contact your service provider and provide all relevant information as follows:

The Event Management Service (EMS) logs
Description of the problem and accompanying symptoms
Supporting documentation such as a processor dump

110

error-desc[ XIO return code: XIO-return-code ] [ string1 ] [ value1 ] [ string2 ] [ value2 ] [ string3 ] [ value3 ] [ string4 ] [ value4 ] [ string5 ] [ value5 ] [ string6 ] [ value6 ]

`error-desc`	is a description of the event information.
XIO-return-code	is the XIO return code resulting from this error.
string1 - string6 and value1 - value6	are event-related descriptions and values related to these descriptions. There can be 6 sets of this information.

Cause Not applicable. This message is for informational purposes only and should be used only by software developers.

Effect Not applicable.

Recovery Not applicable.

111

error-descSituation: situation API-name failed Return Code: return-code Error Detail: error-detail [ Adapter Name: adapter-name ] [ Group/Module/Slot: group-number, module-number, slot-number ] [ Connector Num: connector-num ] [ Fiber Num: fiber-num ]

`error-desc`	is a description of the error.
`situation`	is the description of the scenario in which the failure occurred.
`API-name`	is the name of CONFIG API that was invoked.
`return-code`	is the error code returned by the CONFIG API.
`error-detail`	is the error detail returned by the CONFIG API.
`adapter-name`	is the adapter name.
`group-number`	is the group number for the adapter.
`module-number`	is the module number for the adapter.
`slot-number`	is the slot number for the adapter.
`connector-num`	is the connector number for the adapter.
`fiber-num`	is the fiber number for the adapter.

Cause XIOMON encountered a CONFIG error when requesting hardware information for the adapter in the Group/Module/Slot specified in the message.

Effect An XIO Module Install, Deinstall or Hardware change request failed.

Recovery Verify that the hardware is physically present. If the hardware is physically present and the error persists, contact your service provider and provide the following information:

The Event Management Service (EMS) logs
Description of the problem and accompanying symptoms
Supporting documentation such as a processor dump

112

error-desc Situation: situation API-name failed Return Code: error-code SAC Name: SAC-name [ ServerNet Device Handle: device-handle ] [ ServerNet ID: ServerNet-ID ] [ Side: ServerNet-path ] [ Sub Device No: subdevice-num ] [ Interrupt Base Address: interrupt-base-address]

`error-desc`	is a description of the error.
`situation`	is the description of the scenario in which the failure occurred.
`API-name`	is the name of ServerNet API that was invoked.
`error-code`	is the error code returned from the ServerNet API that was invoked.
`SAC-name`	is the ServerNet Addressable Controller (SAC) name.
`device-handle`	is the ServerNet Device Handle associated with the request.
`ServerNet-ID`	is the ServerNet ID associated with the request.
`ServerNet-path`	is the ServerNet path being used for the request.
`subdevice-num`	is the SubDevice Number associated with the request.
`interrupt-base-address`	is the base address for the interrupt.

Cause XIOMON encountered a ServerNet error while processing a XIO Module Install, Deinstall or Hardware Change request.

Effect An XIO Module Install, Deinstall or Hardware change request failed.

Recovery Verify that the hardware is physically present. If the hardware is physically present and the error persists, contact your service provider and provide the following information:

The Event Management Service (EMS) logs
Description of the problem and accompanying symptoms
Supporting documentation such as a processor dump

113

error-desc Situation: situation API-name failed Request Code: request-code Return Code: return-code Adapter Name: adapter-name [ ServerNetID: ServerNet-ID ] [ Packetizer Device Handle: device-handle ] [ TNET code: ServerNet-return-code Path: ServerNet-path ]

`error-desc`	is a description of the error.
`situation`	is the description of the scenario in which the failure occurred.
`API-name`	is the name of the SCSI Module Driver API that was invoked.
`request-code`	is the SCSI Module Driver request code associated with the initialization request.
`return-code`	is the return code from the SCSI Module Driver API that was invoked.
`adapter-name`	is the adapter name.
`ServerNet-id`	is the ServerNet ID assigned to the adapter.
`device-handle`	is the ServerNet Device Handle assigned to the adapter.
`ServerNet-return-code`	is the return code from the ServerNet operation associated with the error.
`ServerNet-path`	is the ServerNet path associated with the error.

Cause XIOMON encountered a SCSI Module Driver error while attempting to initialize the packetizer associated with the adapter.

Effect XIO Module Install or Hardware change request failed.

Recovery Check the ServerNet Path related to the adapter. Ensure the adapter is properly seated and the related ServerNet paths are up. If the problem still persists, then please contact your service provider and provide all relevant information as follows:

The Event Management Service (EMS) logs
The OSM or TSM ServerNet IA (ServerNet Incident Analysis) report
Description of the problem and accompanying symptoms
Supporting documentation such as a processor dump

114

error-descSituation: situation API-name failed Return Code: return-code

`error-desc`	is a description of the error.
`situation`	is the description of the scenario in which the failure occurred.
`API-name`	is the name of the API that was invoked.
`return-code`	is the error code returned by the API.

Cause An API returned an error.

Effect The API error that was returned was logged.

Recovery Not applicable. This message is for informational purposes only.

115

Module Driver request to ServerNet timed out during Colorado setup tnet id tnet-id, device handle snet-dev-handle on adapter adapter-name

`tnet-id`	is the ServerNet ID of the Colorado.
`snet-dev-handle`	is the ServerNet device handle.
`adapter-name`	is the adapter name that corresponds to the ServerNet Addresable Controller (SAC) in this event.

Cause The Colorado setup response timed out.

Effect This Colorado was not set up properly.

Recovery This event was caused by a hardware problem. Check the indicated hardware.

116

Error in deinstalling the ServerNet device handle for SAC sac-name

sac-name

is the ServerNet Addressable Controller (SAC) name that was requested.

Cause ServerNet Services returned an error to the XIO subsystem during the deinstallation of a device handle.

Effect The device handle for this module is invalid. I/O operations cannot be performed on this device.

Recovery This event indicates an internal error in ServerNet Services. Contact your service provider or the Global Mission Critical Solution Center (GMCSC), as directed by your local operating procedures. Provide relevant information, such as:

The system number
Descriptions of the problem and accompanying symptoms
Details from the message or messages being generated
Supporting documentation such as Event Management Service (EMS) logs
Trace files or saveabend files, if generated
Processor memory dumps, if the problem has resulted in a halted processor