HP StorageWorks XPath OS 7.4.X System Error Messages Reference Guide (AA-RVHGC-TE, September 2005)

ManualsBrandsHP ManualsStorageHP StorageWorks Multiprotocol Base 8-port Router

HP StorageWorks

XPath OS 7.4.x system error messages reference

guide

Part number: AA–RVHGC–TE

Third edition: September 2005

Summary of content (142 pages)

PAGE 1
HP StorageWorks XPath OS 7.4.
PAGE 2
Legal and notice information © Copyright 2005 Hewlett-Packard Development Company, L.P. © Copyright 2005 Brocade Communications Systems, Incorporated. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.
PAGE 3
Contents About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . Document conventions and symbols . . . . . . . . . . . . . . . . . . Rack stability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP technical support . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 4
CM-EVENT_FAN_REMOVE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CM-EVENT_FAN_UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CM-EVENT_FC_RSCN_AREA_OFFLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CM-EVENT_FC_RSCN_AREA_ONLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 5
CM-EVENT_PORT_DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CM-EVENT_PORT_ENABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CM-EVENT_PORT_ERROR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CM-EVENT_PORT_ICMP_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
CM-ZONE_DB_FAIL_28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CM-ZONE_DB_FAIL_29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CM-ZONE_DB_FAIL_30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CM-ZONE_DB_FAIL_31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 7
MS-SIGNAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 MS-SWITCH_OBJECT, ms_fetch_port_parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 MS-SWITCH_OBJECT, ms_init_cscn: Getting FabricInfo failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 MS-SWITCH_OBJECT, ms_init_cscn: Getting SwitchInfo failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 8
fabctl, Debug, WAN_TOV=, Max_hop= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fabctl, nbr_sm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fabctl, prtSCN, st= Topo= Spd= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . fabctl, RSCN, Fmt= ID= L= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 9
About this guide This document provides information to help you administer, operate, maintain, and troubleshoot HP StorageWorks Multi-protocol Routers (MP Routers) within your SAN. Intended audience This guide is intended for system administrators and technicians who are experienced with the following: • HP StorageWorks Fibre Channel Storage Area Network (SAN) switches • XPath Operating System (OS) 7.4.
PAGE 10
Document conventions and symbols Document conventions Table 1 Convention Element Medium blue text: Figure 1 Cross-reference links and e-mail addresses Medium blue, underlined text (http://www.hp.
PAGE 11
HP technical support Telephone numbers for worldwide technical support are listed on the HP support web site: http://www.hp.com/support/. Collect the following information before calling: • Technical support registration number (if applicable) • Product serial numbers • Product model names and numbers • Applicable error messages • Operating system type and revision level • Detailed, specific questions For continuous quality improvement, calls may be recorded or monitored.
PAGE 12
PAGE 13
1 Introduction to system error messages This chapter provides information on the XPath OS error log and event log. The following topics are discussed: • XPath OS logging next • Message severity levels, page 14 • These procedures explain error log management.
PAGE 14
Event log View this log using the eventShow command. It displays system events, such as port up, port down, link events, fabric segmentations, and logins. Events from this log are dumped into the error log as well. Use the eventSeverityShow command to view the possible events in the event log, as well as the default severity levels for those events. In the XPath OS, only specified event messages (persistent events) are saved in nonvolatile memory and restored to the event log after a reboot or power cycle.
PAGE 15
Table 5 Message severity levels Event level Description 0 = Panic Panic messages indicate that a specific software subsystem has detected a fatal or unrecoverable error condition. Examples are memory allocation failure, system call failure, and software detection of problems with the ASIC or with hardware subsystems. These errors usually indicate partial or complete failure of a subsystem.
PAGE 16
Sample error log message The following is a sample message from the error log: fabricAP:admin> errShow Error 239 ---------301 (EvtMgr): Jan 26 13:10:34 Info CM-EVENT_USER_LOGIN_SUCCESS, 4, User login: admin The fields in the sample message are described in Table 6. Table 6 Error log message field descriptions Example Variable name Description Error 239 Error Log Buffer Number Displays a rotating number that describes the position the message holds in the buffer.
PAGE 17
Viewing the event log To view the MP Router event log: 1. Log in to the MP Router as admin. 2. Issue the eventShow command: eventShow The following command displays all the messages in the event log, one at a time: fabricAP:admin> eventShow Clearing the event log To clear the MP Router event log: 1. Log in to the MP Router as admin. 2.
PAGE 18
Modifying the default action for an event XPath OS can respond to an event with one of the following actions: • none: The event is not logged. • log: The event is logged in the event log. • snmptrap: The event is reported to the SNMP process. • logandtrap: The event is logged in the event log and reported to the SNMP process. • persist: The event is logged in both RAM and NVRAM (nonvolatile RAM). The event is preserved over reboots and power cycles. To modify the default action for an event: 1.
PAGE 19
Table 7 Syslogd configuration commands (continued) Command Summary errShow Displays messages from the error log. errClear Clears messages from the error log. Configuring syslogd To route messages to a remote host, you need to configure the remote host and enable syslogd on the MP Router. Configuring syslogd on the remote host To route messages to a remote host, you need to configure the remote host and enable syslogd on the MP Router.
PAGE 20
3. Verify that the IP address was deleted, using the syslogdipShow command The following example shows how to disable sending of error log messages to a previously configured remote syslogd host whose IP address is 123.123.123.123: fabricAP:admin> syslogdipRemove 123.123.123.123 Module descriptions Table 8 lists the modules within the XPath OS that generate messages. The modules are listed alphabetically here and the messages themselves are presented alphabetically in ”Error messages” on page 21.
PAGE 21
2 Error messages XPath OS 7.4.x system error messages are described in the following sections: • Chassis Management messages, next • Diagnostics messages, page 79 • Fabric Control Daemon messages, page 81 • Fibre Channel Router messages, page 86 • Management Server messages, page 91 • Switch Access Layer messages, page 98 • Zone module messages, page 102 • Port log messages, page 107 Chassis Management messages This section describes the Chassis Management (CM) system error messages.
PAGE 22
Recommended action 1. Reboot or power cycle the MP Router. 2. If the problem persists, use the firmwareDownload command to update the firmware. Severity Critical CM-CSCN_NO_MORE_CHA Message process_id (EvtMgr): date time Error CM-CSCN_NO_MORE_CHA, 2, Can't alloc CSCN channel: Reject connect Probable cause The system cannot allocate the common service connection (CSCN) channel due to a rejected connection. This message usually indicates problems with the firmware.
PAGE 23
• snmp-access • syslog • fan • isw-port • isw-xlate The operation value is the action performed. Valid values are create, delete, and set. The name value is the user-defined value for the configuration variable that was changed. Recommended action No action is required.
PAGE 24
2. Use the celloPortTest command to verify whether the central ASIC is faulty. If the central ASIC is faulty, the switch needs to be replaced immediately. Severity Error CM-EVENT_DIAG_ASIC_TEST Message process_id (EvtMgr): date time Error CM-EVENT_DIAG_ASIC_TEST, 2, Diag diagportmailbox failed Probable cause The diagPortMailbox command failed for a port. Recommended action Use the portShow command to determine which port is faulty. If the port ASIC is faulty, do not use the port.
PAGE 25
Recommended action 1. Verify that the MP Router is cabled correctly for the test. Some diagnostic tests require special cabling configurations or loopback plugs. See the HP StorageWorks XPath OS 7.4.x command reference guide for information on this test. 2. Check for faulty cables, deteriorated SFP transceivers, or dirty connections. 3. Replace the cables and SFP transceivers, if necessary. 4. Use the portLoopbackTest command to determine which port of the pair in the crossPortTest is faulty.
PAGE 26
Recommended action 1. Verify that the MP Router is cabled correctly for the test. Some diagnostic tests require special cabling configurations or loopback plugs. 2. Verify that the SFP transceiver or loopback plug is seated correctly. 3. If the port continues to fail, it usually means that the port ASIC is faulty, so do not use the port. A faulty port ASIC does not affect any other port in the switch. The unit can be used until the port is needed to add switch capacity. 4.
PAGE 27
CM-EVENT_DIAG_POST_COMPLETE Message process_id (EvtMgr): date time Info CM-EVENT_DIAG_POST_COMPLETE, 4, Diag POST complete Probable cause The POST (power-on self-test) completed successfully. Recommended action No action is required.
PAGE 28
CM-EVENT_DIAG_XBAR_TEST Message process_id (EvtMgr): date time Error CM-EVENT_DIAG_XBAR_TEST, 2, Diag celloporttest failed Probable cause The celloPortTest command failed. The central ASIC, the port ASIC, or both might be faulty. Recommended action Rerun the test using one-to-one configuration (destination port equal source port) for all tested ports. If all ports fail, either the central ASIC or all the ports are faulty. If some ports run successfully, the failing ports are faulty.
PAGE 29
Recommended action No action is required. Severity Info CM-EVENT_FABRIC_ELEMENT_REBOOT Message process_id (EvtMgr): date time Info CM-EVENT_FABRIC_ELEMENT_REBOOT, 4, SYS-BOOT Restart reason: reason Probable cause A user-initiated switch reboot or power cycle occurred. Possible values for Restart reason are: • Reboot • Unknown Recommended action No action is required.
PAGE 30
CM-EVENT_FAN_INSERT Message process_id (EvtMgr): date time Info CM-EVENT_FAN_INSERT, 4, Fan n inserted Probable cause Fan n was inserted into the chassis. Recommended action No action is required. Severity Info CM-EVENT_FAN_REMOVE Message process_id (EvtMgr): date time Warning CM-EVENT_FAN_REMOVE, 1, Fan n removed Probable cause Fan n was removed from the chassis. Recommended action 1. Replace the missing fan FRU. 2. Check the fan status using the fanShow command. 3.
PAGE 31
CM-EVENT_FC_RSCN_AREA_OFFLINE Message process_id (EvtMgr): date time Critical CM-EVENT_FC_RSCN_AREA_OFFLINE, 1, FC RSCN area offline DAP 0xDAP Probable cause A device went offline. This condition could be caused by a device reboot or a link failure. DAP represents the domain:areaID:AL_PA of the device. Recommended action 1. Verify that the device is operating correctly. 2. Check the link status using the portShow command. 3. Verify that the SFP transceiver is seated correctly. 4.
PAGE 32
Recommended action 1. Verify that the switch was taken offline intentionally. If not, this message could indicate problems with the switch or a connection failure. 2. Verify that the switch is enabled and functioning. 3. Check the fabric status using the fabricShow command. 4. Verify that the interswitch links (ISLs) are cabled correctly. 5. Check for faulty cables, deteriorated SFP transceivers, or dirty connections. 6. Replace the cables and SFP transceivers, if necessary.
PAGE 33
CM-EVENT_FC_RSCN_PORT_OFFLINE Message process_id (EvtMgr): date time Critical CM-EVENT_FC_RSCN_PORT_OFFLINE, 1, FC RSCN port offline DAP 0xDAP Probable cause A device link has failed, which caused the device to go offline. DAP represents the domain:areaID:AL_PA of the device. Recommended action 1. Check the link status using the portShow command. 2. Verify that the SFP transceiver is seated correctly. 3. Check for faulty cables, deteriorated SFP transceivers, or dirty connections. 4.
PAGE 34
Recommended action No action is required. Severity Info CM-EVENT_FCIP_NTP_SYNC_STATE_DOWN Message process_id (EvtMgr): date time Warning CM-EVENT_FCIP_NTP_SYNC_STATE_DOWN, 3, NTP clock lost synchronization, disabling FCIP WAN_TOV enforcement. Probable cause The MP Router lost connectivity to the NTP server, and the switch clock has fallen out of synchronization. The FCIP service stops enforcing WAN_TOV timeouts for ports configured for this feature.
PAGE 35
CM-EVENT_FCIP_TUNNEL_UP Message process_id (EvtMgr): date time Info CM-EVENT_FCIP_TUNNEL_UP, 4, FCIP tunnel n up Probable cause FCIP tunnel n is up due to: • A switch reboot • An administrator enabling the FCIP tunnel Recommended action No action is required.
PAGE 36
Recommended action No action is required. Severity Info CM-EVENT_FCR_FABRIC_NO_LONGER_REACHABLE Message process_id (EvtMgr): date time Info CM-EVENT_FCR_FABRIC_NO_LONGER_REACHABLE, 4, FCR fabric no longer reachable at port n fabric id m Probable cause A fabric m at port n is no longer accessible through the backbone fabric. This condition could be caused by a link or switch failure. Recommended action No action is required.
PAGE 37
Recommended action No action is required. Severity Info CM-EVENT_FCR_ISWFAB (malloc) Message process_id (EvtMgr): date time Warning CM-EVENT_FCR_ISWFAB, 3, isw: malloc failed for value Probable cause A memory allocation failed. The system is low on memory, and possibly has a memory leak. The value is either a cfg, zone, or alias_name. Recommended action If the problem persists, reboot the switch.
PAGE 38
Recommended action Remove excess devices entries within LSAN zones so that the number of devices is within the range of the zone database limitations of the local FCR.
PAGE 39
CM-EVENT_FCR_LOCAL_PHANTOM_NWWN_ENTRY_EXHAUSTED Message process_id (EvtMgr): date time Warning CM-EVENT_FCR_LOCAL_PHANTOM_NWWN_ENTRY_EXHAUSTED, 3, FCR local phantom node WWN entries exhausted Probable cause The number of node WWNs in use is greater than the node WWN (NWWN) resources of the local FCR. Recommended action You might need to limit the number of node WWNs required by limiting the remote edge fabric connectivity (which limits the number of translate domains).
PAGE 40
Recommended action You might need to remove the proxy device slots by using the fcrProxyConfig command or limit proxy devices by removing LSAN zone entries. Severity Error CM-EVENT_FCR_LSAN_ZONE_ADDED Message process_id (EvtMgr): date time Info CM-EVENT_FCR_LSAN_ZONE_ADDED, 4, FCR LSAN zone added at port n Probable cause An LSAN zone was added in the edge fabric attached to port n. Recommended action No action is required.
PAGE 41
Recommended action No action is required. Severity Info CM-EVENT_FCR_LSAN_ZONE_DISABLED Message process_id (EvtMgr): date time Info CM-EVENT_FCR_LSAN_ZONE_DISABLED, 4, FCR LSAN zone disabled at port n Probable cause An LSAN zone was disabled in the edge fabric. Recommended action No action is required.
PAGE 42
Recommended action No action is required. Severity Info CM-EVENT_FCR_NEW_NR_PORT_ADDED Message process_id (EvtMgr): date time Info CM-EVENT_FCR_NEW_NR_PORT_ADDED, 4, FCR new NR_Port added at port n domain_id domID Probable cause An NR_Port was created at port n on domain domID. Recommended action No action is required.
PAGE 43
CM-EVENT_FCR_NODE_WWN_ROLL_OVER Message process_id (EvtMgr): date time Info CM-EVENT_FCR_NODE_WWN_ROLL_OVER, 4, FCR node wwn roll over Probable cause The node WWN pool rolled over and WWN entries not in use are reused as needed. Recommended action It is unlikely that WWN conflicts occur as a result of pool rollover unless the FCR is deployed in a very large meta-SAN environment with a large number of LSAN devices and fabrics, or there are highly dynamic changes to EX_Port connectivity.
PAGE 44
Recommended action 1. Verify that the device was intended to be taken offline. If it was not, verify that the device is functioning properly. 2. Verify that the SFP transceiver is seated correctly. 3. Check for faulty cables, deteriorated SFP transceivers, or dirty connections. 4. Replace the cables and SFP transceivers, if necessary.
PAGE 45
CM-EVENT_FCR_PORT_WWN_ROLL_OVER Message process_id (EvtMgr): date time Info CM-EVENT_FCR_PORT_WWN_ROLL_OVER, 4, FCR port wwn roll over Probable cause The port WWN pool rolled over and WWN entries not in use are reused as needed. Recommended action It is unlikely that WWN conflicts occur as a result of pool rollover unless the FCR is deployed in a very large meta-SAN environment with a large number of LSAN devices and fabrics, or there are highly dynamic changes to EX_Port connectivity.
PAGE 46
CM-EVENT_FCR_PROXY_DEVICE_CREATED Message process_id (EvtMgr): date time Info CM-EVENT_FCR_PROXY_DEVICE_CREATED, 4, FCR proxy device created at port n Probable cause A proxy device at port n was imported. Recommended action No action is required. Severity Info CM-EVENT_FCR_PROXY_DEVICE_DELETED Message process_id (EvtMgr): date time Info CM-EVENT_FCR_PROXY_DEVICE_DELETED, 4, FCR proxy device deleted at port n Probable cause A proxy device at port n was deleted. Recommended action No action is required.
PAGE 47
CM-EVENT_FCR_REMOTE_LSAN_ZONE_UPDATE Message process_id (EvtMgr): date time Info CM-EVENT_FCR_REMOTE_LSAN_ZONE_UPDATE, 4, FCR remote LSAN zone update:domian id n Probable cause An FCR received an update of LSAN zone information from another FCR. Recommended action No action is required.
PAGE 48
Recommended action No action is required. Severity Info CM-EVENT_FILE_SYSTEM_FULL Message process_id (EvtMgr): date time Error CM-EVENT_FILE_SYSTEM_FULL, 2, Partition name capacity is percentage% Probable cause An application is filling up the root partition of compact flash, threatening switch stability. The file system monitor tracks the capacity of up to six file partitions.
PAGE 49
Recommended action Increase the threshold of the partition or clean up the partition by removing temporary files. There is no specific command to change the threshold. 1. Use the configUpload command to upload the switch configuration. 2. Change the threshold value. 3. Use the configDownload command to download the file to the switch. CAUTION: These actions require a root login; contact your switch support supplier before performing these actions.
PAGE 50
CM-EVENT_ISCSI_LOGIN_FAILED Message process_id (EvtMgr): date time Error CM-EVENT_ISCSI_LOGIN_FAILED, 2, iSCSI login failed: login_level Probable cause An iSCSI initiator failed to successfully negotiate operational parameters with the target. Recommended action Check the list of parameters negotiated from the initiator. Look at the /var/log/messages file for the exact parameter that the switch expected but did not get from the initiator.
PAGE 51
CM-EVENT_ISCSI_SESSION_ESTABLISHED Message process_id (EvtMgr): date time Info CM-EVENT_ISCSI_SESSION_ESTABLISHED, 4, iSCSI session established: session_id Probable cause An iSCSI initiator successfully established a session to a target. Recommended action No action is required.
PAGE 52
CM-EVENT_MODULE_DOWN Message process_id (EvtMgr): date time Critical CM-EVENT_MODULE_DOWN, 1, Module down Probable cause One of the following three events has occurred: • When the switch is first powered on, the iomctlr daemon gets the image version number from nonvolatile memory and sends it to the cpmgr daemon.
PAGE 53
CM-EVENT_PORT_DISABLE Message process_id (EvtMgr): date time Warning CM-EVENT_PORT_DISABLE, 3, Port n disabled Probable cause Port n was disabled using the portDisable command or Advanced Web Tools. Recommended action This is an administrator-initiated operation. If the operation was intended, no action is required. Severity Warning CM-EVENT_PORT_DOWN Message process_id (EvtMgr): date time Warning CM-EVENT_PORT_DOWN, 3, FC port n down Probable cause FC port n is down. Recommended action 1.
PAGE 54
CM-EVENT_PORT_ERROR Message process_id (EvtMgr): date time Error CM-EVENT_PORT_ERROR, 2, Port error Probable cause An invalid full loop configuration was initiated or a port driver failed. Recommended action 1. Check the port configuration using the portCfgGige command or Advanced Web Tools. 2. Remove extra devices from the loop. If the error is due to a port driver failure, the system restarts the port.
PAGE 55
• IP header bad • Required option missing Recommended action 1. Check port configuration using the portShow, portCfgGige, and portCfgFcip commands or Advanced Web Tools. 2. Correct the IP configuration with an action appropriate to the error listed. 3. Check for an IP network outage. 4. Correct IP network issues as required. Severity Warning CM-EVENT_PORT_LINK_DOWN Message process_id (EvtMgr): date time Critical CM-EVENT_PORT_LINK_DOWN, 1, FC n link down Probable cause FC link n is down.
PAGE 56
CM-EVENT_PORT_STARTED Message process_id (EvtMgr): date time Warning CM-EVENT_PORT_STARTED, 3, Port n started Probable cause Port n was started using the portStart command or Advanced Web Tools. Recommended action This is an administrator-initiated operation. If the operation was intended, no action is required.
PAGE 57
CM-EVENT_POWER_DOWN Message process_id (EvtMgr): date time Warning CM-EVENT_POWER_DOWN, 3, Power n down Probable cause Power supply n is down, where n represents either power supply 1 or 2. Recommended action 1. Check the power supply status using the chassisShow command. 2. Try reseating the specified power supply. 3. If the problem persists, replace the failed power supply.
PAGE 58
CM-EVENT_POWER_UP Message process_id (EvtMgr): date time Info CM-EVENT_POWER_UP, 4, Power n up Probable cause Power supply n is operational, where n represents either power supply 1 or 2. Recommended action No action is required. Severity Info CM-EVENT_RPG_OPERATION Message process_id (EvtMgr): date time Warning CM-EVENT_RPG_OPERATION, 3, RPG operation Probable cause A firmware download operation was performed. Recommended action Use the version command to verify the installed version of the firmware.
PAGE 59
CM-EVENT_SFP_REMOVED Message process_id (EvtMgr): date time Warning CM-EVENT_SFP_REMOVED, 3, An SFP has been removed at port n Probable cause The SFP transceiver at port n was removed. Recommended action 1. Check the SFP transceiver status using the sfpShow command. 2. Replace any missing SFP transceivers. 3. Verify that the SFP transceiver is seated correctly. 4. Check for faulty cables, deteriorated SFP transceivers, or dirty connections. 5. Replace the cables and SFP transceivers if necessary.
PAGE 60
CM-EVENT_SHUTDOWN_TEMP_EXCEEDED_CLEAR Message process_id (EvtMgr): date time Info CM-EVENT_SHUTDOWN_TEMP_EXCEEDED_CLEAR, 4, Shutdown temperature exceeded clear, card n sensor s temp temp Probable cause The temperature warning has been cleared and the switch temperature is within operational range. Recommended action No action is required.
PAGE 61
CM-EVENT_SWITCH_READY Message process_id (EvtMgr): date time Info CM-EVENT_SWITCH_READY, 4, Switch ready Probable cause The switch is ready after a reboot or a firmware download operation. Recommended action No action is required.
PAGE 62
CM-EVENT_TEMPERATURE_SHUTDOWN Message process_id (EvtMgr): date time Critical CM-EVENT_TEMPERATURE_SHUTDOWN, 1, Switch shutdown due to shutdown temperature exceeded Probable cause At least two temperature sensors have crossed the shutdown temperature threshold. Temperature problems usually indicate problems with fans or the environment temperature. Recommended action 1. Wait until the switch has cooled down before rebooting and running diagnostics. 2.
PAGE 63
Recommended action No action is required. Severity Info CM-EVENT_WARNING_TEMP_EXCEEDED Message process_id (EvtMgr): date time Warning CM-EVENT_WARNING_TEMP_EXCEEDED, 3, Warning temperature exceeded, card n sensor s temp t Probable cause The warning temperature limit has been exceeded. The fan speed is automatically increased. Temperature problems usually indicate problems with fans or the environment temperature. Recommended action 1. Use the tempShow command to view the temperature of the MP Router. 2.
PAGE 64
CM-EVENT_ZONE_CHANGE Message process_id (EvtMgr): date time Info CM-EVENT_ZONE_CHANGE, 4, type operation: name Probable cause A change in the zoning configuration, where type is one of the following: • ZoneAlias • ZoneDB • ZoneFA • ZoneQL • ZoneSet • zone operation is one of the following: • save • bulk_created • clear name is one of the following: • ZONE_INFO • rn_zone.db Recommended action No action is required.
PAGE 65
CM-MEM_ALLOC_ERR Message process_id (EvtMgr): date time Critical CM-MEM_ALLOC_ERR, 1, fail to alloc memory Probable cause A memory resource is not available because of a memory leak. Recommended action 1. Use the top command to look for a memory leak. The top command displays memory usage on the switch and the daemons running. Most daemons should show approximately 1 MB. The nsd daemon typically shows 30 MB and the iswitchd daemon typically shows 50 MB.
PAGE 66
Recommended action Use the firmwareDownload command to reinstall the firmware. Severity Error CM-NVRAM_OPEN_ERR Message process_id (EvtMgr): date time Error CM-NVRAM_OPEN_ERR, 2, open() failed on /dev/nvram Probable cause The access permission for the /dev/nvram directory is incorrect due to faulty firmware. Recommended action Use the firmwareDownload command to reinstall the firmware.
PAGE 67
CM-ZONE_DB_FAIL_2 Message process_id (EvtMgr): date time Critical CM-ZONE_DB_FAIL_2, 1, Bad object type type function_name Probable cause A memory allocation failed. The system is low on memory or has a memory leak. Recommended action 1. Reboot or power cycle the MP Router. 2. If the problem persists, run the firmwareDownload command to upgrade the firmware.
PAGE 68
CM-ZONE_DB_FAIL_5 Message process_id (EvtMgr): date time Error CM-ZONE_DB_FAIL_5, 2, Send response failed function_name Probable cause An interprocess communication failure occurred, usually because of corrupt firmware. Recommended action 1. Reboot or power cycle the MP Router. 2. If the problem persists, run the firmwareDownload command to upgrade the firmware.
PAGE 69
CM-ZONE_DB_FAIL_9 Message process_id (EvtMgr): date time Error CM-ZONE_DB_FAIL_9, 2, Name name's type type doesn't match with one in zone Probable cause There is an illegal character or syntax error in the object name. Recommended action Check the object name syntax and retry the last action. See the HP StorageWorks XPath OS 7.4.x command reference guide for information on proper syntax.
PAGE 70
CM-ZONE_DB_FAIL_12 Message process_id (EvtMgr): date time Error CM-ZONE_DB_FAIL_12, 2, sl_init failed function_name Probable cause A string memory allocation failure occurred, which is usually caused by the system running low on memory or a memory leak. Recommended action 1. Reboot or power cycle the MP Router. 2. If the problem persists, run the firmwareDownload command to upgrade the firmware.
PAGE 71
Recommended action Delete excess objects or members from the zone database and retry the last action. Use the zoneRemove command to remove members from a zone. Use the zoneDelete command to remove unused zones from the zone database. Severity Error CM-ZONE_DB_FAIL_15 Message process_id (EvtMgr): date time Error CM-ZONE_DB_FAIL_15, 2, zone name has no member function_name Probable cause A zone is expected to have members while its aliases are being expanded. Recommended action 1.
PAGE 72
Recommended action 1. Reboot or power cycle the MP Router. 2. If the problem persists, run the firmwareDownload command to upgrade the firmware. Severity Error CM-ZONE_DB_FAIL_18 Message process_id (EvtMgr): date time Error CM-ZONE_DB_FAIL_18, 2, Failed to open file(file_name) function_name Probable cause The zone database file does not exist or was not found. Recommended action 1. Reboot or power cycle the MP Router. 2. If the problem persists, run the firmwareDownload command to upgrade the firmware.
PAGE 73
CM-ZONE_DB_FAIL_20 Message process_id (EvtMgr): date time Error CM-ZONE_DB_FAIL_20, 2, convert ascii to internal data structure failed function_name Probable cause An error was found in /etc/rn_zone.db. Recommended action 1. Reboot or power cycle the MP Router. 2. If the problem persists, run the firmwareDownload command to upgrade the firmware.
PAGE 74
CM-ZONE_DB_FAIL_23 Message process_id (EvtMgr): date time Error CM-ZONE_DB_FAIL_23, 2, Bad zone_config_ptr or size function_name Probable cause Data corruption was found in the zone database. Recommended action 1. Reboot or power cycle the MP Router. 2. If the problem persists, run the firmwareDownload command to upgrade the firmware.
PAGE 75
CM-ZONE_DB_FAIL_26 Message process_id (EvtMgr): date time Error CM-ZONE_DB_FAIL_26, 2, member list too long function_name Probable cause The number of members for the specified zone object exceeds the zone database limit of 128 KB. This error occurs only while importing the configuration file during a configDownload. Recommended action Edit the configuration file to make the zone database smaller. When downloading a configuration, the zone database must be below 128 KB.
PAGE 76
Recommended action Verify that you are using proper syntax for the operation and retry the command. For more information on command syntax, see the HP StorageWorks XPath OS 7.4.x command reference guide. Severity Error CM-ZONE_DB_FAIL_29 Message process_id (EvtMgr): date time Error CM-ZONE_DB_FAIL_29, 2, Trying to enable zone (name) that doesn't exist function_name Probable cause The admin is trying to enable a zone that does not exist in the zone database. Recommended action No action is required.
PAGE 77
Recommended action Verify that you are using proper syntax for the operation and retry the command. For more information on command syntax, see the HP StorageWorks XPath OS 7.4.x command reference guide. Severity Error CM-ZONE_DB_FAIL_32 Message process_id (EvtMgr): date time Error CM-ZONE_DB_FAIL_32, 2, file file_name does not exist. Not an error on 1st reboot after a new install function_name Probable cause The zone database does not exist on the switch.
PAGE 78
CM-ZONE_DB_FAIL_34 Message process_id (EvtMgr): date time Error CM-ZONE_DB_FAIL_34, 2, file file_name too big, bigger than size function_name Probable cause The resultant size of the zone database exceeds the supported limit. Recommended action Delete excess objects or members from the zone database and retry the last action. Use the zoneRemove command to remove members from a zone. Use the zoneDelete command to remove unused zones from the zone database.
PAGE 79
Diagnostics messages This section describes the Diagnostics (DIAG) system error messages. DIAG-CSCN_FAIL Message process_id (diagd): date time Error DIAG-CSCN_FAIL, 2, function_name:cscn-api-name failed Probable cause An error was reported to the API. Recommended action Reboot or power cycle the MP Router. Severity Error DIAG-DIAGAPI_FAIL Message process_id (diagd): date time Error DIAG-DIAGAPI_FAIL, 2, function_name:diag-api-name failed Probable cause An error was reported to the API.
PAGE 80
Recommended action 1. Use the top command to look for a memory leak. The top command displays memory usage on the switch and the daemons running. Most daemons should show approximately 1 MB. The nsd daemon typically shows 30 MB. If any daemon is running up to 10 MB or the nsd daemon shows above 50 MB, then there might be memory leak. 2. Check the last value in the memory line of the top command output for system free space.
PAGE 81
Fabric Control Daemon messages This section describes the Fabric Control Daemon (FAB) system error messages. FAB-CHA-ERR Message process_id (fabctl): date time Error FAB-CHA-ERR, 2, fabctl: Saved objid failed. Aborting save. Probable cause A fabric change error occurred. This condition is usually transitory. Recommended action Reboot or power cycle the MP Router.
PAGE 82
FAB-CSCN-ERR, fabctl: could not open xbar frame Q Message process_id (fabctl): date time Critical FAB-CSCN-ERR, 1, fabctl: could not open xbar frame Q Probable cause A CSCN connection to xbar frame Q failed. The xbar frame Q handles all Fibre Channel well-known address frames, such as 0xFFFFFE, 0xFFFFFD, and 0xFFFCxx. Recommended action Reboot or power cycle the MP Router.
PAGE 83
Recommended action 1. Use the top command to look for a memory leak. The top command displays memory usage on the switch and the daemons running. Most daemons should show approximately 1 MB. The nsd daemon typically shows 30 MB. If any daemon is running up to 10 MB or the nsd daemon shows above 50 MB, there might be memory leak. 2. Check the last value in the memory line of the top command output for system free space. This value varies, depending on configuration, but should be approximately 800 MB free.
PAGE 84
Recommended action No action is required. The daemon resends the request. Severity Warning FAB-OUT-RESOURCES, fabctl: MsgAlloc failed Message process_id (fabctl): date time Error FAB-OUT-RESOURCES, 2, fabctl: MsgAlloc failed "function_name" Probable cause A memory resource is not available. Recommended action 1. Use the top command to look for a memory leak. The top command displays memory usage on the switch and the daemons running. Most daemons should show approximately 1 MB.
PAGE 85
FAB-SHM-ERR, fabctl: signature not found Message process_id (fabctl): date time Error FAB-SHM-ERR, 2, fabctl: signature not found in the shared memory segment Probable cause The shared memory is not set properly. Recommended action Reboot or power cycle the MP Router. Severity Error FAB-SHM-ERR, fabctl_get_shm: shmat failed. Message process_id (fabctl): date time Error FAB-SHM-ERR, 2, fabctl_get_shm: shmat failed. errno = errno Probable cause Shared memory is not set properly.
PAGE 86
FAB-SHM-ERR, fabctl_restore_state Message process_id (fabctl): date time Error FAB-SHM-ERR, 2, fabctl_restore_state: shmat failed. errno = %d Probable cause A shared memory restore operation failed. Recommended action Reboot or power cycle the MP Router. Severity Error FAB-ZONE-ERR Message process_id (fabctl): date time Error FAB-ZONE-ERR, 2, fabctl: Open to ZSlib failed Probable cause The zone server library initialization failed because of an inability to set shared memory.
PAGE 87
Recommended action Troubleshooting can involve checking the physical health of the links, SFP transceivers, and switches in the fabric. Use commands, such as fabricShow, topologyShow, and switchShow to troubleshoot problems in the fabric. Severity Warning FCR-ISW (RSCN) Message process_id (iswitchd): date time Warning FCR-ISW, 3, pt number RSCN retransmitted x times command of command from source_domain to dest_domain Probable cause An RSCN is being retransmitted for a device from an FCR switch.
PAGE 88
FCR-ISWFAB (malloc failed) Message process_id (iswitchd): date time Warning FCR-ISWFAB, 3, isw: malloc failed for value Probable cause A memory allocation failed. The system is low on memory or has a memory leak. The value is either a configuration, a zone, or an alias name. Recommended action If the problem persists, reboot the switch.
PAGE 89
FCR-SHM_OPER ( failed to attach shared memory) Message process_id (iswitchd): date time Error FCR-SHM_OPER, 2, Failed to attach Shared Memory = unix_error Probable cause The FCR failed to attach shared memory. Recommended action Reboot the switch. Severity Error FCR-SHM_OPER (failed to get shared memory) Message process_id (iswitchd): date time Error FCR-SHM_OPER, 2, Failed to get Shared memory = value Probable cause The FCR failed to get shared memory. Recommended action Reboot the switch.
PAGE 90
FCR-ISW Message process_id (iswitchd): date time Warning FCR-ISW, 3, Ran out of trapped ELS slots dfid dfid sfid sfid did did sid sid ox_id ox_id Probable cause Resources for saving a copy of an ELS (extended link services) command are not available. This problem is usually transient, and might not require user action.
PAGE 91
Management Server messages This section describes the Management Server (MS) system error messages. MS-CSCN_CN_FAIL, Connection to SB failed Message process_id (msd): date time Critical MS-CSCN_CN_FAIL, 1, Connection to SB failed Probable cause The connection to the switchboard daemon failed. Recommended action Reboot or power cycle the MP Router.
PAGE 92
MS-OUT_RESOURCES Message process_id (msd): date time Error MS-OUT_RESOURCES, 2, [ms_svr_register_sb]: Malloc failed Probable cause A memory allocation failed. Typically, this problem is resolved without user intervention. Recommended action Wait a few minutes and retry the operation. Reboot or power cycle the MP Router.
PAGE 93
MS-PORT_OBJECT, Getting LinkAdminStatus object failed Message process_id (msd): date time Error MS-PORT_OBJECT, 2, Getting LinkAdminStatus object failed for port n Probable cause A request for link admin status failed. Typically, this problem is resolved without user intervention. Recommended action Wait a few minutes and retry the operation. Reboot or power cycle the MP Router.
PAGE 94
MS-PORT_OBJECT, Getting portOpType object failed Message process_id (msd): date time Error MS-PORT_OBJECT, 2, Getting portOpType object failed for port n Probable cause A request for port type failed. Typically, this problem is resolved without user intervention. Recommended action Wait a few minutes and retry the last operation. Reboot or power cycle the MP Router.
PAGE 95
MS-SHM_OPER, Failed to attach I2C Shared Memory Message process_id (msd): date time Critical MS-SHM_OPER, 1, Failed to attach I2C Shared Memory Probable cause A request to attach I2C shared memory failed. Recommended action 1. Reboot or power cycle the MP Router. 2. If the problem is not fixed with a reboot, use the firmwareDownload command to download a new version of the firmware.
PAGE 96
Recommended action 1. Reboot or power cycle the MP Router. 2. If the problem is not fixed with a reboot, use the firmwareDownload command to download a new version of the firmware. Severity Critical MS-SIGNAL Message process_id (msd): date time Critical MS-SIGNAL, 1, Received SIGTERM: Mgmt server exiting Probable cause The Management Server received a SIGTERM (signal termination) error. The Management Server fails. Recommended action Reboot or power cycle the MP Router.
PAGE 97
MS-SWITCH_OBJECT, ms_init_cscn: Getting FabricInfo failed Message process_id (msd): date time Error MS-SWITCH_OBJECT, 2, ms_init_cscn: Getting FabricInfo failed Probable cause An error occurred trying to fetch fabric related information. Typically, this problem is resolved without user intervention. It can be ignored unless seen repeatedly. Recommended action Reboot or power cycle the MP Router.
PAGE 98
MS-SWITCH_OBJECT, ms_init_cscn: Getting SwitchParams failed Message process_id (msd): date time Error MS-SWITCH_OBJECT, 2, ms_init_cscn: Getting SwitchParams failed Probable cause An error occurred trying to fetch switch settings. Typically, this problem is resolved without user intervention. It can be ignored unless seen repeatedly. Recommended action Reboot or power cycle the MP Router.
PAGE 99
Recommended action Reboot or power cycle the MP Router. Severity Critical SWAL-CSCN_TX_FAILURE Message process_id (module_name): date time Critical SWAL-CSCN_TX_FAILURE, 1, Fail to send for process function_name file_name line_number Probable cause A CSCN transmit failure occurred. There might be a CSCN connection problem. Recommended action Reboot or power cycle the MP Router.
PAGE 100
Recommended action Wait a few minutes and retry the operation. Reboot or power cycle the MP Router. Severity Warning SWAL-FCR_API_CSCN, Open to ISWITCHD failed Message process_id (module_name): date time Error SWAL-FCR_API_CSCN, 2, Open to ISWITCHD failed Probable cause An error occurred trying to connect to the iswitchd daemon. Typically, this problem is resolved without user intervention. It can be ignored unless seen repeatedly. Recommended action Wait a few minutes and retry the operation.
PAGE 101
SWAL-MS_API_CSCN (open to MS failed) Message process_id (module_name): date time Error SWAL-FCR_API_CSCN, 2, Open to MS failed Probable cause A connection to the Management Server failed. Either the MS daemon crashed or the system is out of resources. Typically, this problem is resolved without user intervention. Recommended action Wait a few minutes and retry the operation. Reboot or power cycle the MP Router.
PAGE 102
SWAL-SB_INIT_FAILURE Message process_id (module_name): date time Critical SWAL-SB_INIT_FAILURE, 1, Connection to SB failed: function_name file_name line_number Probable cause An error was encountered when initializing the CSCN connection to the SB. This is a rare message, and might indicate a problem with the XPath OS firmware.
PAGE 103
ZONE-CSCN_CN_FAIL Message process_id (zsd): date time Critical ZONE-CSCN_CN_FAIL, 1, CSCN initialization for interface/client failed Probable cause A problem occurred while initializing the ZSD zone daemon and establishing a CSCN connection with the interface or client process. This message usually indicates an XPath OS firmware problem. The interfaces or clients that might be affected are: • nscli_connect • sb_connect • sb_connect_comp • zs_cha_cb • zs_init_cscn Recommended action 1.
PAGE 104
ZONE-SHM_MALLOC Message process_id (zsd): date time Critical ZONE-SHM_MALLOC, 1, Shared memory allocation failed Probable cause A problem occurred while initializing the ZSD zone daemon and shared memory allocation. This message usually indicates an XPath OS firmware problem. Recommended action 1. Reboot or power cycle the MP Router. 2. If the problem persists, run the firmwareDownload command to upgrade the firmware.
PAGE 105
ZONE-ZONE_NOLICENSE Message process_id (zsd): date time Info ZONE-ZONE_NOLICENSE, 4, Missing required license Probable cause The required zoning license is missing. Recommended action Use the licenseAdd command to install the zoning license. For more information on installing a license, see the HP StorageWorks XPath OS 7.4.x administrator guide.
PAGE 106
• zs_update_brcd_zoneinfo • zsbrcdcmd_timer • zslib_activebrcd • zslib_addlist • zslib_build_activebrcd • zslib_replace_alias • zslib_update_brcdpacket_todb Recommended action 1. Reboot or power cycle the MP Router. 2. If the problem persists, run the firmwareDownload command to upgrade the firmware.
PAGE 107
ZONE-ZSD_ZONE Message process_id (zsd): date time Warning ZONE-ZSD_ZONE, 3, The num of zones exceeds 1024 Probable cause The maximum number of zones (1024) has been exceeded. Recommended action Delete excess zones and retry the last commit operation. Severity Warning Port log messages This section documents all messages displayed by the portLogShow command. The XPath OS maintains an internal port log of all port activity.
PAGE 108
Port log field descriptions The following is an example portLogShow command: FabricAP:admin> portLogShow 8 Total records present = 12 Number of records displayed = 12 Time Module Event Port Len Log info ------------------------------------------------------------------------------18:36:52.036 fabctl PrtSCN 08 0 st=1, Topo=2, Spd=0 18:36:52.361 WKA Rx 08 140 22fffffe,00000000,01a6ffff,04000000 18:36:52.362 fabctl PrtSCN 08 0 st=2, Topo=2, Spd=2 18:36:52.365 fabctl Debug 08 0 Loading routes 18:36:52.
PAGE 109
Port log modules The following are the modules that log messages to the port log: • Debug: Used by any module to add debug port log messages. • fabctl: Fabric Controller. Along with fabric controller functions, Login Server, FSPF, and Zone merge code runs in this program’s context. • nsd: Name Server. • msd: Management Server. • zsd: Zone Server. • rcsd: RCS daemon. • iswitchd: FCR daemon. • fc_port: FC port code. • fcipPort: FCIP port code. • iscsiPrti: SCSI port code.
PAGE 110
Recommended action No action is required. Severity Info csmsg, IOCTL, local domain Port Log message time csmsg IOCTL port len local domain = domainID Probable cause This message displays the domain ID of the MP Router and is generated during boot up or when the domain ID changes. Recommended action No action is required. Severity Info csmsg, IOCTL, Switch PID Format Port Log message time csmsg IOCTL port len Switch PID Format = PID_format Probable cause This message displays the MP Router PID format.
PAGE 111
Recommended action No action is required. Severity Info fabctl, Debug, distrib routes End Port Log message time fabctl Debug port len distrib routes End Probable cause This message provides the end of route calculation by FSPF. Recommended action No action is required. Severity Info fabctl, Debug, distrib routes start Port Log message time fabctl Debug port len distrib routes start Probable cause This message provides the start of route calculation by FSPF. Recommended action No action is required.
PAGE 112
Recommended action No action is required. Severity Info fabctl, Debug, fabSm:Init to Init Port Log message time fabctl Debug port len fabSm:Init to Init.L=line Probable cause This message provides the fabric controller state machine transitions. The line variable is for internal use only. Recommended action No action is required. Severity Info fabctl, Debug, fabSm:Init to LinkSt Port Log message time fabctl Debug port len fabSm:Init to LinkSt.
PAGE 113
Recommended action No action is required. Severity Info fabctl, Debug, fabSm:LinkSt to SendELP Port Log message time fabctl Debug port len fabSm:LinkSt to SendELP.L=line Probable cause This message provides the fabric controller state machine transitions. The line variable is for internal use only. Recommended action No action is required. Severity Info fabctl, Debug, fabSm:ProcessESC to RDIWait Port Log message time fabctl Debug port len fabSm:ProcessESC to RDIWait.
PAGE 114
Recommended action No action is required. Severity Info fabctl, Debug, fabSm:Unknown State to Init Port Log message time fabctl Debug port len fabSm:Unknown State to Init.L=line Probable cause This message provides the fabric controller state machine transitions. The line variable is for internal use only. Recommended action No action is required.
PAGE 115
The porttype values can be: • 0 - Type unknown • 1 - FC port • 0x7f - port disabled Recommended action No action is required. Severity Info fabctl, Debug, FSPF ILS Port Log message time fabctl Debug port len FSPF ILS 0xhex drpd. Dom unconf Probable cause The received SW_ILS frame destined for FSPF (either HELLO(0x14), LSU(0x15) or LSA(0x16)) was dropped because the domain ID is unconfirmed (fabric formation after a BF has not completed yet). Recommended action No action is required.
PAGE 116
fabctl, Debug, Invalid xbar cmd Port Log message time fabctl Debug port len Invalid xbar cmd 0xhex Probable cause The fabctl daemon received an invalid (unsupported) SW_ILS command. Recommended action No action is required. Severity Info fabctl, Debug, Loading routes Port Log message time fabctl Debug port len Loading routes Probable cause FSPF routes are getting loaded to the port. Recommended action No action is required.
PAGE 117
fabctl, Debug, routes purged Port Log message time fabctl Debug port len routes purged Probable cause FSPF routes were purged from the port. This action is typically occurs before route reload. Recommended action No action is required. Severity Info fabctl, Debug, SW_ILS Port Log message time fabctl Debug port len SW_ILS command dropped !EPort(T:hexvalue) Probable cause An SW_ILS received on a non-E-Port was dropped. Log prints the SW_ILS command and current port mode.
PAGE 118
fabctl, Debug, WAN_TOV=, Max_hop= Port Log message time fabctl Debug port len WAN_TOV=xx, Max_hop=xx Probable cause This message provides the WAN_TOV (wide area network time out value) and Max_hop count settings. See the configure command in the HP StorageWorks XPath OS 7.4.x command reference guide for more information these settings. Recommended action No action is required.
PAGE 119
Recommended action No action is required. Severity Info fabctl, RSCN, Fmt= ID= L= Port Log message time fabctl RSCN port len Fmt=rscn_format, ID=portidhex, L=payload_length Probable cause Specifies the RSCN Format, port ID and payload length. Possible values for the RSCN format are: • #define RSCN_PORTID_FORMAT 0x0 • #define RSCN_AREA_FORMAT0x1 • #define RSCN_DOMAIN_FORMAT0x2 • #define RSCN_FABRIC_FORMAT0x3 Recommended action No action is required.
PAGE 120
fabctl, Tx Port Log message time fabctl Tx port len 02fffffd,00fffffd,10ecffff, first_word_of_payload Probable cause This message provides a frame transmitted from fabctl. The first three words (word 0, word 1, and word 4) are displayed along with the first word of the payload. Recommended action No action is required. Severity Info nsd, Ct_out, ns query acc Port Log message time nsd Ct_out port len ns query acc CT_REQUEST number_of_entries Probable cause A valid Name Server reply was sent.
PAGE 121
nsd, Debug, got portdown for port Port Log message time nsd RSCN port len got portdown for port=port_number Probable cause The Name Server reports a port link down message; nsd stands for the Name Server daemon. This is the largest daemon running on the system (typically about 30 MB). Recommended action No action is required.
PAGE 122
nsd, RSCN, ns rscn gen Port Log message time nsd RSCN port len ns rscn gen Probable cause This message provides the RSCN generated due to local device coming online, fabric reformation, or zone configuration change. Log indicates the RSCN format and the affected Port ID (if applicable). The first byte indicates the RSCN format: • RSCN_PORTID_FORMAT0x0 • RSCN_AREA_FORMAT0x1 • RSCN_FABRIC_FORMAT0x3 Bytes 1–3 indicate the affected Port ID. Note that nsd stands for the Name Server daemon.
PAGE 123
WKA, Debug, dest_q_calc Port Log message time WKA Debug port len dest_q_calc: 0 pl_len! Probable cause This message specifies an attempt to classify an incoming frame with 0 payload length, based on the command type. Recommended action No action is required. Severity Info WKA, Debug, destq calc failed Port Log message time WKA Debug port len destq calc failed 6words_FCheader 6words_payload Probable cause The Fabric OS was unable to find a matching recipient for an incoming frame.
PAGE 124
Recommended action No action is required. Severity Info WKA, Debug, No ox_id Port Log message time WKA Debug port len No ox_id:sid=sid,did=did,ox_id=ox_id Probable cause An attempt to get a placeholder to store the exchange ID (ox_ID), which is used for handling an multi-frame sequence, failed. Recommended action No action is required.
PAGE 125
• The first six words from an internal WKA header. • The first six words from the internal routing header. • The first six words from the FC header. • From one to six words from the payload. The payload line is present only if a payload exists. Recommended action No action is required.
PAGE 126
WKA, Rx_Ack1 Port Log message time WKA Rx_Ack1 port len 02fffffd,00fffffd,11d5ffff, first_word_of_payload Probable cause The well-known-address daemon sent a CT frame. Fields logged are: • First word of FC header (R_CTL, destination address) • Second word of FC header (CS_CTL, source address) • Fifth word of FC header (OX_ID, RX_ID) • First word of the payload Recommended action No action is required.
PAGE 127
Glossary alias A logical grouping of elements in a fabric. An alias is a collection of port numbers and connected devices used to simplify the entry of port numbers and WWNs when creating zones.AL_PA Arbitrated loop physical address. A unique 8-bit value assigned during loop initialization to a port in an arbitrated loop. area number In Fabric OS 4.0 and later, ports on a switch are assigned a logical area number. Port area numbers can be viewed by issuing the switchShow command.
PAGE 128
error In the Fibre Channel industry, a missing or corrupted frame, timeout, loss of synchronization, or loss of signal (link errors). Ethernet Popular protocol for LANs. EX_Port A port that connects a router to an edge fabric. EX_Ports limit the scope of fabric services, but provide device connectivity using Fibre Channel network address translation (FC-NAT). exchange The highest-level Fibre Channel mechanism used for communication between N_Ports.
PAGE 129
FDMI Fabric Device Management Interface. A database service provided by the fabric for Nx_Ports. The primary use is by host bus adapters (HBAs) that register information about themselves and their ports. FIFO First in, first out. A storage method that retrieves the item stored for the longest time. FL_Port Fabric loop port. A port that is able to transmit under fabric protocol and also has arbitrated loop capabilities. Can be used to connect an NL_Port to a switch.
PAGE 130
LAN Local area network. A network in which transmissions typically take place over fewer than 5 kilometers (3.4 miles). LED Light-emitting diode. A device that indicates the status of elements on a switch. LSAN Logical storage area network. An LSAN enables device and storage connectivity that spans two or more fabrics. MALLOC Memory allocation. Usually refers to buffer credits. meta-SAN Two or more SANs connected using Fibre Channel Routers. These SANs can share resources, but are not merged.
PAGE 131
port log A record of all activity on a switch, kept in volatile memory. port name A user-defined alphanumeric name for a port. port_name The unique identifier assigned to a Fibre Channel port. Communicated during log in and port discovery. POST Power-on self-test. A series of tests run by a switch after it is turned on. principal switch The first switch to boot up in a fabric. Ensures unique domain IDs among roles. RCS Reliable Commit Service. Refers to HP-specific ILS command code.
PAGE 132
SNS See Simple Name Server (SNS). soft zone A zone consisting of zone members that are made visible to each other through client service requests. Typically, soft zones contain zone members that are visible to devices using Name Server exposure of zone members. The fabric does not enforce a soft zone. Note that well-known addresses are implicitly included in every zone. switch A fabric device providing bandwidth and high-speed routing of data using link-level addressing.
PAGE 133
trunking ports The ports in a set of trunked ISLs. TX Transmit. well-known address In Fibre Channel technology, a logical address defined by Fibre Channel standards as assigned to a specific function and stored on the switch. WWN World wide name. An identifier that is unique world-wide. Each entity in a fabric has a separate WWN. zone A set of devices and hosts attached to the same fabric and configured as being in the same zone.
PAGE 134
PAGE 135
Index A ASIC diagnostic test failure 23 audience 9 authorized reseller, HP 11 C celloMemTest command failure 24 celloPortTest command 24 celloPortTest command failure 28 cfgDelete command 45 cfgDisable command 45 cfgShow command 66 chassis management messages 21 chassisShow command 57 clearing event log 17 clearing system error log 16 CM_CSCN_CL_ERR 21 CM-CSCN_CNT_ERR 21 CM-CSCN_NO_MORE_CHA 22 CM-EVENT_CONFIG_CHANGE 22 CM-EVENT_CONSOLE_LOST_CARRIER_SIGNAL 23 CM-EVENT_DIAG_ASIC_REV 23 CM-EVENT_DIAG_ASIC_TES
PAGE 136
CM-EVENT_PORT_LINK_UP 55 CM-EVENT_PORT_STARTED 56 CM-EVENT_PORT_STOPPED 56 CM-EVENT_PORT_UP 56 CM-EVENT_POWER_DOWN 57 CM-EVENT_POWER_INSERT 57 CM-EVENT_POWER_REMOVE 57 CM-EVENT_POWER_UP 58 CM-EVENT_RPG_OPERATION 58 CM-EVENT_SFP_INSERTED 58 CM-EVENT_SFP_REMOVED 59 CM-EVENT_SHUTDOWN_TEMP_EXCEEDED 59 CM-EVENT_SHUTDOWN_TEMP_EXCEEDED_CLEAR 60 CM-EVENT_SWITCH_DISABLE 60 CM-EVENT_SWITCH_ENABLE 60 CM-EVENT_SWITCH_READY 61 CM-EVENT_SWITCH_STATUS_CHANGE 61 CM-EVENT_TEMPERATURE_SHUTDOWN 62 CM-EVENT_USER_LOGIN_SUCCESS
PAGE 137
tempShow 29, 30, 59 top 65, 80 topologyShow 87 trunkShow 111 tsClockServer 34 version 58 zoneDelete 45, 66, 78 zoneRemove 45, 66, 71, 78 zoneShow 45 configDownload command 48, 75 configUpload command 49 configure command 118 configuring syslog daemon 18 syslogd 19 connectivity failure 50 context resource allocation failure 83 conventions document 10 text symbols 10 crossPortTest command 25 CSCN buffer allocation failure 74, 79, 102 CSCN listen failure 82, 83 CSCN transmit failure 80, 99 csmsg, DRV, Got Rout
PAGE 138
CSCN listen 82, 83 CSCN transmit 80, 99 device link 33 diagnostic cross-port test 24 diagPortMailbox command 24 diagPortMem test 26 diagPortMemarm test 26 interprocess communication 68 iSCSI initiator 50 kernel module 98 management server 96 Management Server connection 101 memory allocation 37, 67, 92, 105 MSD daemon request 101 MSD daemon response 101 port driver 54 portLoopbackTest command 25 request for E_port information 92 request for FC parameters 92 request for link admin status 93 request for MP Ro
PAGE 139
MS-PORT_OBJECT, Getting portType object failed 94 MS-SHM_OPER, Failed to allocate Shared Memory 94 MS-SHM_OPER, Failed to attach I2C Shared Memory 95 MS-SHM_OPER, Failed to attach Shared Memory 95 MS-SHM_OPER, Failed to get I2C Shared Memory 95 MS-SIGNAL 96 MS-SWITCH_OBJECT, ms_fetch_port_parameter 96 MS-SWITCH_OBJECT, ms_init_cscn: Getting FabricInfo failed 97 MS-SWITCH_OBJECT, ms_init_cscn: Getting SwitchInfo failed 97 MS-SWITCH_OBJECT, ms_init_cscn: Getting SwitchName failed 97 MS-SWITCH_OBJECT, ms_init_
PAGE 140
trunkShow command 111 tsClockServer command 34 V version command 58 viewing event log 17 system error log 15 W warning, rack stability 10 web sites HP storage 11 HP Subscriber’s choice 11 WKA, Ct_in 122 WKA, Debug, dest_q_calc 123 WKA, Debug, destq calc failed 123 WKA, Debug, fill hdr failed 123 WKA, Debug, No ox_id 124 WKA, Debug, Send msg failed 124 WKA, Debug, sendbackrcvdmsg failed 124 WKA, Rx 125 WKA, Rx, No dest_q 125 WKA, Rx_Ack1 126 WKA, Tx_Ack1 126 X xbar daemon failure 91 xbar frame queue failu
PAGE 141
Figures
PAGE 142