HP StorageWorks Fabric OS 5.0.0 Diagnostics and System Error Messages Reference Guide (AA-RW1SA-TE, May 2005)

ManualsBrandsHP ManualsStorageBrocade 4Gb SAN Switch w/ Power Pack

HP StorageWorks

Fabric OS 5.0.0 diagnostics and system error

messages

reference guide

Part number: AA–RW1SA–TE

First edition: May 2005

Summary of content (424 pages)

PAGE 1
HP StorageWorks Fabric OS 5.0.
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document conventions and symbols . . . . . . . . . . . . . . . . . . . . HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP Storage web site. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 4
AUTH-1018 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AUTH-1020 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AUTH-1022 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AUTH-1023 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 5
EM-1033 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EM-1034 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EM-1036 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EM-1041 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
FCPD-1003. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fibre Channel physical layer error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FCPH-1001. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fabric OS I/O kernel library module error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 7
FW-1051 . FW-1052 . FW-1113 . FW-1114 . FW-1115 . FW-1116 . FW-1117 . FW-1118 . FW-1119 . FW-1120 . FW-1121 . FW-1122 . FW-1123 . FW-1124 . FW-1125 . FW-1126 . FW-1127 . FW-1128 . FW-1129 . FW-1130 . FW-1131 . FW-1132 . FW-1133 . FW-1134 . FW-1135 . FW-1136 . FW-1137 . FW-1138 . FW-1139 . FW-1140 . FW-1141 . FW-1142 . FW-1143 . FW-1144 . FW-1160 . FW-1161 . FW-1162 . FW-1163 . FW-1164 . FW-1165 . FW-1166 . FW-1167 . FW-1168 . FW-1169 . FW-1170 . FW-1171 . FW-1172 . FW-1173 . FW-1174 . FW-1175 . FW-1176 .
PAGE 8
FW-1185 . FW-1186 . FW-1187 . FW-1188 . FW-1189 . FW-1190 . FW-1191 . FW-1192 . FW-1193 . FW-1194 . FW-1195 . FW-1216 . FW-1217 . FW-1218 . FW-1219 . FW-1240 . FW-1241 . FW-1242 . FW-1243 . FW-1244 . FW-1245 . FW-1246 . FW-1247 . FW-1248 . FW-1249 . FW-1250 . FW-1251 . FW-1272 . FW-1273 . FW-1274 . FW-1275 . FW-1296 . FW-1297 . FW-1298 . FW-1299 . FW-1300 . FW-1301 . FW-1302 . FW-1303 . FW-1304 . FW-1305 . FW-1306 . FW-1307 . FW-1308 . FW-1309 . FW-1310 . FW-1311 . FW-1312 . FW-1313 . FW-1314 . FW-1315 .
PAGE 9
FW-1324 . FW-1325 . FW-1326 . FW-1327 . FW-1328 . FW-1329 . FW-1330 . FW-1331 . FW-1332 . FW-1333 . FW-1334 . FW-1335 . FW-1336 . FW-1337 . FW-1338 . FW-1339 . FW-1340 . FW-1341 . FW-1342 . FW-1343 . FW-1344 . FW-1345 . FW-1346 . FW-1347 . FW-1348 . FW-1349 . FW-1350 . FW-1351 . FW-1352 . FW-1353 . FW-1354 . FW-1355 . FW-1356 . FW-1357 . FW-1358 . FW-1359 . FW-1360 . FW-1361 . FW-1362 . FW-1363 . FW-1364 . FW-1365 . FW-1366 . FW-1367 . FW-1368 . FW-1369 . FW-1370 . FW-1371 . FW-1372 . FW-1373 . FW-1374 .
PAGE 10
FW-1403 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1424 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1425 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1426 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1427 . . . . . . . .
PAGE 11
HIL-1501 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HIL-1502 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HIL-1503 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HIL-1504 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 12
NS-1004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parity data manager error messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDM-1001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDM-1002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDM-1003 . . . . . . . . . . . . . . . . . . . .
PAGE 13
SCN-1001 . . . . . . . Security error messages. SEC-1001. . . . . . . . SEC-1002. . . . . . . . SEC-1003. . . . . . . . SEC-1005. . . . . . . . SEC-1006. . . . . . . . SEC-1007. . . . . . . . SEC-1008. . . . . . . . SEC-1009. . . . . . . . SEC-1016. . . . . . . . SEC-1022. . . . . . . . SEC-1024. . . . . . . . SEC-1025. . . . . . . . SEC-1026. . . . . . . . SEC-1028. . . . . . . . SEC-1029. . . . . . . . SEC-1030. . . . . . . . SEC-1031. . . . . . . . SEC-1032. . . . . . . . SEC-1033. . . . . . . .
PAGE 14
SEC-1082. SEC-1083. SEC-1084. SEC-1085. SEC-1086. SEC-1088. SEC-1089. SEC-1090. SEC-1091. SEC-1092. SEC-1093. SEC-1094. SEC-1095. SEC-1096. SEC-1097. SEC-1098. SEC-1099. SEC-1100. SEC-1101. SEC-1102. SEC-1104. SEC-1105. SEC-1106. SEC-1107. SEC-1108. SEC-1110. SEC-1111. SEC-1112. SEC-1115. SEC-1116. SEC-1117. SEC-1118. SEC-1119. SEC-1121. SEC-1122. SEC-1123. SEC-1124. SEC-1126. SEC-1130. SEC-1135. SEC-1136. SEC-1137. SEC-1138. SEC-1139. SEC-1142. SEC-1145. SEC-1146. SEC-1153. SEC-1154. SEC-1155. SEC-1156.
PAGE 15
SEC-1167. SEC-1168. SEC-1170. SEC-1171. SEC-1172. SEC-1173. SEC-1174. SEC-1175. SEC-1176. SEC-1180. SEC-1181. SEC-1182. SEC-1183. SEC-1184. SEC-1185. SEC-1186. SEC-1187. SEC-1188. SEC-1189. SEC-1190. SEC-1191. SEC-1192. SEC-1193. SEC-1194. SEC-1195. SEC-1196. SEC-1197. SEC-1198. SEC-1199. SEC-1200. SEC-1201. SEC-1202. SEC-1250. SEC-1251. SEC-1253. SEC-1300. SEC-1301. SEC-1302. SEC-1303. SEC-1304. SEC-1305. SEC-1306. SEC-1307. SEC-1308. SEC-3001. SEC-3002. SEC-3003. SEC-3004. SEC-3005. SEC-3006. SEC-3007.
PAGE 16
SEC-3016. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-3017. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simple network management protocol error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP-1001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 17
UCST-1007. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UPATH error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UPTH-1001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User space software watchdog error messages . . . . . . . . . . . . USWD-1006. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Web Tools error messages . . . . . . . . . . . . . . . . . . . . . . . . . . WEBD-1001 . . . . . . . . . . . . . . . . . . . . .
PAGE 18
Contents
PAGE 19
About this guide This document provides information to assist fabric administrators in using the web-based graphical user interface to monitor and modify their HP StorageWorks switch fabrics.
PAGE 20
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 21
HP technical support Telephone numbers for worldwide technical support are listed on the following HP web site: http://www.hp.com/support/. From this web site, select the country of origin. NOTE: For continuous quality improvement, calls may be recorded or monitored.
PAGE 22
About this guide
PAGE 23
1 Introduction to system messages This guide supports Fabric OS v4.4.0 and contains system messages useful for diagnosing and fixing problems with switches and fabrics. The messages are organized alphabetically by module name. A module is a subsystem in Fabric OS. Each module generates a set of numbered messages. For each message, this guide provides message text, probable cause, recommended action, and severity level. Messages can have more than one cause and more than one corrective action.
PAGE 24
• The message format has changed. Previous versions of Fabric OS used the following format: severity, Module-alphaname, severity_number, message_text Error messages now use the following format: timestamp, [Module-Number], sequence-number, [AUDIT], severity, switch-chassis-name, message-text • All messages are saved in persistent storage in this release. Previous releases normally saved only Panic and Critical levels in persistent storage.
PAGE 25
ZONE-3002 Message , [ZONE-3002], , AUDIT, INFO, , User: , Role: , Event: , Status: , Info: \"\" created with \"\". Probable cause Indicates that a new zone object set was created with the specified zone object member or members added. A zone object may be an alias, zone member, zone, or zone configuration. The string "...
PAGE 26
ZONE-3004 Message , [ZONE-3004], , AUDIT, INFO, , User: , Role: , Event: , Status: , Info: \"\" removed from \"\". Probable cause Indicates that a specified zone object member or members have been removed from a specified zone object set. A zone object may be an alias, zone member, zone or zone configuration. The string "...
PAGE 27
Recommended action Verify that the event was planned. If the event was planned, no action is required. If the event was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO ZONE-3007 Message , [ZONE-3007], , AUDIT, INFO, , User: , Role: , Event: , Status: , Info: Zone configuration \"\" enabled.
PAGE 28
Recommended action Verify that the event was planned. If the event was planned, no action is required. If the event was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO ZONE-3010 Message , [ZONE-3010], , AUDIT, INFO, , User: , Role: , Event: , Status: , Info: Zone object \"\" copied to new zone object \"\".
PAGE 29
Recommended action Verify that the event was planned. If the event was planned, no action is required. If the event was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO Message severity levels The four levels of severity for messages are Critical, Error, Warning, and Info. In general, the definitions of these severity levels are broad and serve as general guidelines for troubleshooting.
PAGE 30
• System console, page 32 System message log (RASLog) Fabric OS maintains an internal system message log of all messages. For Fabric OS v4.4.0, this log is saved as a RASLog. Features of the system message log include the following: • The saving of all messages to nonvolatile storage. • A maximum of 1024 messages that can be saved in RAM. • Implementation as a circular buffer. When more than the maximum number of entries are added to the log file, old entries are overwritten by new ones.
PAGE 31
Dual-CP systems For both the Core Switch 2/64 and the SAN Director 2/128, each CP has a unique error log, depending on which CP was is when a message is reported. To fully understand message logging on the Core Switch 2/64 or the SAN Director 2/128, you should enable the system logging daemon, because the logs on the host computer are maintained in a single merged file for both CPs and are in sequential order.
PAGE 32
If a daemon fails to ping the SWD within the defined interval, or if the daemon terminates unexpectedly, the SWD dumps information to the panic dump files, which helps to diagnose the root cause of the unexpected failure. Use the pdShow command to view these files or the saveCore command to send them to a host workstation using FTP. The panic dump files and core files are intended for support personnel use only.
PAGE 33
Table 3 Commands to view and configure system logs (continued) Command Description errShow Displays the entire error log with page breaks. Use the -r option to show the messages in reverse order, from newest to oldest. pdShow Displays the contents of the panic dump and core dump files. portErrShow Displays the port error summary. portLogClear Clears the port log. If the port log is disabled, this commands enables it. portLogDisable Disables the port log facility.
PAGE 34
Table 3 Commands to view and configure system logs (continued) Command Description syslogDIpShow Displays the currently configured IP addresses that are recipients of system messages. syslogdFacility Changes the syslogd facility. traceDump Displays, initiates, or removes a Fabric OS module trace dump. traceFtp Displays, enables, or disables the trace auto-FTP or retrieves the trace dump file. traceTrig Sets, removes, or displays trace triggers.
PAGE 35
Table 4 Error message field description (continued) Example Variable name Description 4 Sequence Number The error message position in the log. When any messages are added to the log, this number is incremented. When this message reaches the last position in the error log and becomes the oldest message, it is deleted when a new message is added. In Fabric OS v4.4.0, the message sequence number starts at 1 after a firmwareDownload and increases up to a value of 2,147,483,647 (0x7ffffff).
PAGE 36
3. Click the Switch Events button. A Switch Events Report opens. 4. View the switch events and messages. In dual-domain switches, an Event button exists for each logical switch. Only messages relating to that switch (and chassis) are displayed. Dumping the system messages This procedure is valid for the HP StorageWorks SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch 2/16N, SAN Switch 2/32, SAN Switch 4/32, Core Switch 2/64, and SAN Director 2/128. To display the system message log with no page breaks: 1.
PAGE 37
2. Issue the errShow command: switch:admin> errShow Version: 4.4.0 2004/07/28-17:04:59, [FSSM-1002], 1,, INFO, switch, HA State is in sync Type to continue, Q to stop: 2004/07/28-17:04:59, [FSSM-1003], 2,, WARNING, switch, HA State out of sync Type to continue, Q to stop: 2004/07/28-17:04:51, [EM-1055], 3,, WARNING, switch, Media 27: Port media incompatible e. Reason: Configured port speed.
PAGE 38
• How large is the fabric? • Is the fabric redundant? 5. Issue the errDump command on each logical switch. 6. Issue the supportFtp command as needed to set up automatic FTP transfers and then issue the supportSave command. 7. Document the sequence of events by answering the following questions: • What happened just prior to the problem? • Is the problem repeatable? • If so, what are the steps to produce the problem? • What configuration was in place when the problem occurred? 8.
PAGE 39
Table 5 System module descriptions (continued) System module Description EM The EM manages and monitors the various field replaceable units (FRUs), including the port cards, CP blades, blower assemblies, power supplies, and World Wide Name (WWN) cards. EM controls the state of the FRUs during system startup, hot-plug sequences, and fault recovery.
PAGE 40
Table 5 System module descriptions (continued) System module Description FSS The Fabric OS state synchronization framework provides facilities by which the active CP can synchronize with the standby CP, enabling the standby CP to take control of the switch non-disruptively during failures and software upgrades. These facilities include version negotiation, state information transfer, and internal synchronization functions, enabling the transition from standby to active operation.
PAGE 41
Table 5 System module descriptions (continued) System module Description KSWD The Kernel Software Watchdog monitors daemons for unexpected terminations and hang conditions; KSWD informs the HAM module to take corrective actions, such as failover or reboot.
PAGE 42
Table 5 System module descriptions (continued) System module Description MQ Message queues are used for interprocess communication. Message queues allow many messages, each of variable length, to be queued. Any process or Interrupt Service Routine (ISR) can write messages to a message queue. Any process can read messages from a message queue.
PAGE 43
Table 5 System module descriptions (continued) System module Description PLAT Platform (Service) errors are generated from the port blade and CP blade of the Core Switch 2/64, the SAN Director 2/128, and the ASICs or motherboard components of all other switches. These error messages usually indicate hardware problems in these components, including problems resulting from the PCI buses, i2c bus, field-programmable gate array (FPGA), and power supply.
PAGE 44
Table 5 System module descriptions (continued) System module Description SS The supportSave command generates these error messages if problems are encountered. SULB The software upgrade library provides firmwareDownload command capability, which enables firmware upgrades to both CP blades with a single command, as well as nondestructive code load to all 4.x switches. These messages display if problems occur during the firmwareDownload procedure.
PAGE 45
Table 5 System module descriptions (continued) System module Description USWD The User-space Software Watchdog Daemon informs the KSWD about which daemons the watchdog subsystem monitors. The USWD daemon also helps the KSWD daemon to print debug information if a critical daemon has an unexpected termination. WEBD Indicates problems with the Web Tools module. ZOLB Indicates problems with the zone library module.
PAGE 46
Introduction to system messages
PAGE 47
2 Messages Authentication error messages AUTH-1001 Message timestamp, [AUTH-1001], sequence-number,, INFO, system-name, Operation-type has been successfully done. Probable cause The secret database operation has been updated using the secAuthSecret command. The values for Operation-type are set and remove. Recommended action No action is required. Severity INFO AUTH-1002 Message timestamp, [AUTH-1002], sequence-number,, ERROR, system-name, Operation-type has failed.
PAGE 48
AUTH-1003 Message timestamp, [AUTH-1003], sequence-number,, INFO, system-name, data-type type has been successfully set to setting value. Probable cause An authentication configuration value was set to a specified value. The data type is either authentication type or DH group type. Recommended action No action is required. Severity INFO AUTH-1004 Message timestamp, [AUTH-1004], sequence-number,, ERROR, system-name, Failed to set data type type to setting-value.
PAGE 49
Recommended action 1. Run the firmwareDownload command to reinstall the firmware. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3. Run the supportSave command and contact your switch service provider. Severity ERROR AUTH-1006 Message timestamp, [AUTH-1006], sequence-number,, WARNING, system-name, Failed to open authentication configuration-file. Probable cause An internal problem with the Secure Fabric OS. Recommended action 1.
PAGE 50
AUTH-1008 Message timestamp, [AUTH-1008], sequence-number,, ERROR, system-name, No security license, operation failed. Probable cause The switch does not have a security license. Recommended action Verify that the security license is installed using the licenseShow command. If necessary, reinstall the license using the licenseAdd command.
PAGE 51
Recommended action 1. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3. Run the supportSave command and contact your switch service provider.
PAGE 52
AUTH-1014 Message timestamp, [AUTH-1014], sequence-number,, ERROR, system-name, Invalid port value to operation: port port-number Probable cause Internal problem with the Secure Fabric OS. Recommended action 1. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3. Run the supportSave command and contact your switch service provider.
PAGE 53
AUTH-1018 Message timestamp, [AUTH-1018], sequence-number,, ERROR, system-name, Invalid value to check protocol type: port port-number Probable cause Internal problem with the Secure Fabric OS. Recommended action 1. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3. Run the supportSave command and contact your switch service provider.
PAGE 54
AUTH-1022 Message timestamp, [AUTH-1022], sequence-number,, ERROR, system-name, Failed to extract data-type from message payload: port port-number. Probable cause The authentication process failed to extract a particular value from the receiving payload. Recommended action This problem is usually transient, although the authentication may fail. 1. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. 2.
PAGE 55
4. Run the supportSave command and contact your switch service provider. Severity ERROR AUTH-1025 Message timestamp, [AUTH-1025], sequence-number,, ERROR, system-name, Failed to get data-type during authentication-phase: port port-number Probable cause The authentication process failed to get expected information during the specified authentication phase. Recommended action This problem is usually transient, although the authentication may fail. 1.
PAGE 56
Severity ERROR AUTH-1028 Message timestamp, [AUTH-1028], sequence-number,, ERROR, system-name, Failed to allocate data-type for operation-phase: port port-number Probable cause The authentication process failed because the system is low on memory. Data-type is the payload or structure that failed to get memory. Operation-phase specifies which operation of a particular authentication phase failed. Recommended action This problem is usually transient, although the authentication may fail. 1.
PAGE 57
Severity ERROR AUTH-1030 Message timestamp, [AUTH-1030], sequence-number,, ERROR, system-name, Invalid message code for message-phase message: port port-number Probable cause The receiving payload does not have a valid message code for a particular authentication phase. Recommended action This problem is usually transient, although the authentication may fail. 1. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. 2.
PAGE 58
AUTH-1032 Message timestamp, [AUTH-1032], sequence-number,, ERROR, system-name, Failed to generate data-type for message-payload payload: length data-length, error code error-code, port port-number Probable cause The authentication process failed to generate a particular data (that is, challenge, nonce, or response data) for an authentication payload. This usually relates to internal failure. A nonce is a single-use, usually random value used in authentication protocols to prevent replay attacks.
PAGE 59
AUTH-1034 Message timestamp, [AUTH-1034], sequence-number,, ERROR, system-name, Failed to validate name entity-name in authentication-message: port port-number Probable cause The entity name in the payload is not in the right format. Recommended action 1. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3.
PAGE 60
AUTH-1036 Message timestamp, [AUTH-1036], sequence-number,, ERROR, system-name, Invalid state state-value for authentication-phase: port port-number Probable cause The switch received an unexpected authentication message. Recommended action This problem is usually transient, although the authentication may fail. 1. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. 2.
PAGE 61
AUTH-1038 Message timestamp, [AUTH-1038], sequence-number,, ERROR, system-name, Failed to retrieve certificate during authentication-phase: port port-number Probable cause The PKI certificate is not installed properly. Recommended action 1. Reinstall the PKI certificate using the pkiCreate command. 2. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. 3.
PAGE 62
BL-1001 Message timestamp, [BL-1001], sequence-number,, INFO, system-name, Port Initialization Completed Probable cause The switch has completed initializing the ports. This message occurs only on the SAN Switch 4/32. Recommended action No action is required.
PAGE 63
BL-1003 Message timestamp, [BL-1003], sequence-number,, CRITICAL, system-name, Faulting blade in slot slot-number Probable cause A faulty blade in the specified slot number. This message occurs only on the Core Switch 2/64 and SAN Director 2/128. Recommended action 1. Make sure that the blade is seated correctly. If the blade is seated correctly, reboot or power cycle the blade. 2. Run the systemVerification command to verify that blade does not have hardware problems.
PAGE 64
BL-1006 Message timestamp, [BL-1006], sequence-number,, INFO, system-name, Blade slot-number NOT faulted. Peer blade slot-number experienced abrupt failure. Probable cause The errors (mostly synchronization errors) on this blade are harmless. Probably, the standby CP blade connected to the active CP blade has experienced transitory problems. This message occurs only on the Core Switch 2/64 and SAN Director 2/128. Recommended action Check the standby CP.
PAGE 65
BL-1008 Message timestamp, [BL-1008], sequence-number,, CRITICAL, system-name, Slot slot-number control-plane failure. Expected value: 0xvalue-1, Actual: 0xvalue-2 Probable cause Possibly the blade has experienced a hardware failure or was removed without following the recommended removal procedure. This message occurs only on the Core Switch 2/64 and SAN Director 2/128. Recommended action 1. Make sure that the blade is seated correctly. If the blade is seated correctly, reboot or power cycle the blade.
PAGE 66
BL-1010 Message timestamp, [BL-1010], sequence-number,, WARNING, system-name, Blade in slot slot-number inconsistent with the hardware settings. Probable cause A failover occurred while some hardware changes were being made on the previously active CP (such as changing the domain ID). This message occurs only on the Core Switch 2/64 and SAN Director 2/128. Recommended action No action is required. This blade has been reinitialized.
PAGE 67
BL-1012 Message timestamp, [BL-1012], sequence-number,, INFO, system-name, bport port-number port int. is disabled. status=0xinterrupt-status Port port-number will be re-enabled in 1 minute. Probable cause The port generated an excessive number of interrupts that may prove fatal to the switch operation. The port is disabled to prevent the CP from becoming too busy. The port-number is the blade port; this number may not correspond to a user port number.
PAGE 68
BL-1014 Message timestamp, [BL-1014], sequence-number,, INFO, system-name, bport port-number port int. is disabled. status=0xinterrupt-status Probable cause The port generated an excessive number of interrupts that may prove fatal to the switch operation. The port is disabled to prevent the CP from becoming too busy. The port-number is the blade port; this number may not correspond to a user port number. Recommended action Capture the console output during the following process: 1.
PAGE 69
4. If a hardware error exists, or if the slotPowerOff or slotPowerOn fails on the bladed switch, or if errors are encountered again: • On the Core Switch 2/64 or SAN Director 2/128, replace the blade FRU. • On the SAN Switch 2/32, replace the motherboard FRU. • On the HP StorageWorks SAN Switch 2/8V, SAN Switch 2/16V, or SAN Switch 4/32, replace the switch.
PAGE 70
BLOOM message that provides more information on the specific error. This message occurs only on the Core Switch 2/64 and SAN Director 2/128.
PAGE 71
Core edge routing module error messages CER-1001 Message timestamp, [CER-1001], sequence-number,, ERROR, system-name, HA Sync broken, since standby Advanced Performance Tuning module does not support Management Server (FMS). Probable cause The HA synchronization between the active and standby control processors (CPs) is broken because downlevel firmware is loaded on the standby CP. . Recommended action Run the firmwareDownload command to upgrade the firmware on the standby CP.
PAGE 72
• SAN Switch 2/16V fans run at approximately 9000 RPM. • SAN Switch 2/8V fans run at approximately 5500 RPM. The SAN Switch 2/8V has three fans, and the SAN Switch 2/16V has four fans. Values for the individual fans may appear in this message, but these parts cannot be replaced. The switch itself is a FRU.
PAGE 73
Probable cause Indicates that a fan FRU header could not be read or is not valid. The FRU is faulted. Recommended action 1. On Core Switch 2/64 or SAN Director 2/128, try reseating the specified FRU. 2. Reboot or power cycle the switch. 3. Run the systemVerification command to verify that the switch does not have hardware problems. Refer to the HP StorageWorks Fabric OS 4.x command reference guide for more information on this command. 4.
PAGE 74
Severity CRITICAL EM-1005 Message timestamp, [EM-1005], sequence-number,, CRITICAL, system-name, FRU-Id is shutting down Probable cause A blade in the specified slot or the switch (for non-bladed switches) is being shut down for environmental reasons; its temperature or voltage is out of range. The FRU-Id value is composed of a FRU-type string and an optional number to identify the unit, slot, or port. The FRU-Id value can be: • Switch for fixed-port-count switches.
PAGE 75
EM-1006 Message timestamp, [EM-1006], sequence-number,, CRITICAL, system-name, FRU-Id has faulted. Sensor(s) below minimum limits Probable cause The sensors show the voltage is below minimum limits. The blade in the specified slot is being shut down for environmental reasons; the voltage is too low. Recommended action Voltage problems on a blade are likely a hardware problem on the blade itself; replace the blade.
PAGE 76
EM-1008 Message timestamp, [EM-1008], sequence-number,, CRITICAL, system-name, Incompatible unit in FRU-Id is being faulted Probable cause A FRU inserted in the specified slot is not compatible with the switch software. The blade is not used. This message occurs only on the Core Switch 2/64 and SAN Director 2/128. Recommended action Replace the blade. Make sure the replacement is compatible with your switch type.
PAGE 77
EM-1010 Message timestamp, [EM-1010], sequence-number,, CRITICAL, system-name, Received unexpected power down for FRU-Id But FRU-Id still has power Probable cause The environmental monitor received an unexpected power-down notification from the specified FRU. However, the specified FRU still appears to be powered up after four seconds. This message occurs only on the Core Switch 2/64 and SAN Director 2/128. Recommended action Try reseating the blade.
PAGE 78
The FRU-Id value is composed of a FRU-type string and an optional number to identify the unit, slot, or port. The FRU-Id value can be: • Switch for fixed port count switches. • Slot 1 through Slot 10 for the Core Switch 2/64 and SAN Director 2/128. Recommended action 1. On Core Switch 2/64 and SAN Director 2/128, try reseating the indicated FRU. 2. If the message persists, reboot or power cycle the switch. 3. Run the systemVerification command to verify that the switch does not have hardware problems.
PAGE 79
If the message persists, replace the unit. Severity ERROR EM-1014 Message timestamp, [EM-1014], sequence-number,, ERROR, system-name, Unable to read sensor on FRU-Id (return-code) Probable cause The environmental monitor was unable to access the sensors on the specified FRU. The FRU-Id value is composed of a FRU-type string and an optional number to identify the unit, slot, or port. The FRU-Id value can be: • Switch for fixed port count switches.
PAGE 80
EM-1015 Message timestamp, [EM-1015], sequence-number,, WARNING, system-name, Warm recovery failed (Return-code) Probable cause A problem was discovered when performing consistency checks during a warm boot. Recommended action Perform a reboot or power cycle to clear the problem. Severity WARNING EM-1016 Message timestamp, [EM-1016], sequence-number,, WARNING, system-name, Cold recovery failed (Return-code) Probable cause Consistency checks during a cold boot discovered a problem.
PAGE 81
Recommended action Change and commit the new WWN value. Severity WARNING EM-1028 Message timestamp, [EM-1028], sequence-number,, ERROR, system-name, HIL Error: function failed to access FRU: FRU-Id (rc=return-code). Probable cause Problems were encountered when the software attempted to write to the memory of the FRU specified in the error message. The return code is for internal use only. This is a serious FRU hardware problem.
PAGE 82
EM-1029 Message timestamp, [EM-1029], sequence-number,, ERROR, system-name, FRU-Id I2C access problems (error-code): state current-state Probable cause Indicates that the I2C bus had problems and a timeout occurred. The FRU-Id value is composed of a FRU-type string and an optional number to identify the unit, slot, or port. The FRU-Id value can be: • Switch for fixed port count switches. • Slot 1 through Slot 10 for the Core Switch 2/64 and SAN Director 2/128.
PAGE 83
Probable cause The environmental monitor (EM) found a switch blade that is inserted, but at least one ejector switch is not latched. The blade in the specified slot is treated as not inserted. This message occurs only on the Core Switch 2/64 and SAN Director 2/128. Recommended action Close the ejector switch if the FRU is intended for use.
PAGE 84
The FRU-Id value is composed of a FRU-type string and an optional number to identify the unit, slot, or port. The FRU-Id value can be: • Switch for fixed port count switches. • Slot 1 through Slot 10 for the Core Switch 2/64 and SAN Director 2/128. • PS 1 through PS 4 (power supplies) for the Core Switch 2/64 and SAN Director 2/128, or PS 1 through PS 2 for the SAN Switch 2/32 and SAN Switch 4/32. The power supplies on the SAN Switch 2/8V and the SAN Switch 2/16V are not field replaceable.
PAGE 85
Severity WARNING EM-1041 Message timestamp, [EM-1041], sequence-number,, WARNING, system-name, Sensor values for FRU-Id: Sensor-Value Sensor-Value Sensor-Value Sensor-Value Sensor-Value Sensor-Value Sensor-Value Probable cause Sensors detected a warning condition. All significant sensors for the FRU are displayed; each contains a header. The FRU-Id value is composed of a FRU-type string and an optional number to identify the unit, slot, or port.
PAGE 86
EM-1042 Message timestamp, [EM-1042], sequence-number,, WARNING, system-name, Important FRU header data for FRU-Id is not valid). Probable cause The indicated FRU has an incorrect number of sensors in its FRU header-derived information. This could mean that the FRU header was corrupted or read incorrectly or corrupted in the object database, which contains information about all FRUs. The FRU-Id value is composed of a FRU-type string and an optional number to identify the unit, slot, or port.
PAGE 87
Recommended action The specified FRU is not responding to commands and should be replaced. Severity WARNING EM-1044 Message timestamp, [EM-1044], sequence-number,, WARNING, system-name, Can't power on FRU-Id, its logical switch is shut down Probable cause The specified FRU cannot be powered on because the associated logical switch is shut down. Recommended action Run the switchStart command on the associated logical switch.
PAGE 88
Severity WARNING EM-1046 Message timestamp, [EM-1046], sequence-number,, WARNING, system-name, Sysctrl reports error status for blade ID id-value for the blade in slot slot-number Probable cause The system controller encountered a blade with an unknown ID in the slot specified. This message occurs only on the Core Switch 2/64 and SAN Director 2/128. Recommended action If the blade ID listed is not correct, then the FRU header for the blade is corrupted and the blade must be replaced.
PAGE 89
EM-1048 Message timestamp, [EM-1048], sequence-number,, INFO, system-name, FRU-Id I2C access recovered: state current-state Probable cause The I2C bus problems have been resolved and I2C access to the FRU has become available again. The FRU-Id value is composed of a FRU-type string and an optional number to identify the unit, slot, or port. The FRU-Id value can be: • Switch for fixed port count switches. • Slot 1 through Slot 10 for the Core Switch 2/64 and SAN Director 2/128.
PAGE 90
• Slot 1 through Slot 10 for the Core Switch 2/64 and SAN Director 2/128. • PS 1 through PS 4 (power supplies) for the Core Switch 2/64 and SAN Director 2/128, or PS 1 through PS 2 for the SAN Switch 2/32 and SAN Switch 4/32. The power supplies on the SAN Switch 2/8V and the SAN Switch 2/16V are not field replaceable. • Fan 1 through Fan 3 for the Core Switch 2/64, SAN Director 2/128, and SAN Switch 4/32 (six fans in three FRUs). Fan 1 through Fan 6 for the SAN Switch 2/32 (six fans in three FRUs).
PAGE 91
Recommended action Verify that the unit was intended to be removed. Replace the unit as soon as possible. Severity INFO EM-1051 Message timestamp, [EM-1051], sequence-number,, INFO, system-name, FRU-Id: Inconsistency detected, FRU re-initialized Probable cause An inconsistent state was found in the FRU. This occurs if the state of the FRU was changing during a failover. The FRU is reinitialized and traffic may have been disrupted. Recommended action No action is required.
PAGE 92
• WWN 1 or WWN 2 for the Core Switch 2/64 and SAN Director 2/128. Only bladed switches have removable WWN cards. All other switches have a non-removable WWN component on the main logic board. The SAN Switch 2/8V has one power supply and three fans, and the SAN Switch 2/16V has two power supplies and four fans. Values for the individual fans and power supplies for these switches may appear, but these parts cannot be replaced. The switch itself is a FRU.
PAGE 93
The SAN Switch 2/8V has one power supply and three fans, and the SAN Switch 2/16V has two power supplies and four fans. Values for the individual fans and power supplies for these switches may appear, but these parts cannot be replaced. The switch itself is a FRU. Recommended action If the message is isolated, it may be a transient problem with the sensor hardware; monitor the error messages on the switch. If the message is persistent, replace the FRU.
PAGE 94
Severity WARNING Event management module error messages EVMD-1001 Message timestamp, [EVMD-1001], sequence-number,, WARNING, system-name, Event session killed, host IP = Host-IP-address, port = Host-TCP-port-number Probable cause The TCP socket is closed because of a TCP write error. Possible causes for this loss of connection include the following: • The API host application exits without notifying the switch. • The API host computer is shut down. • A network problem exists.
PAGE 95
Probable cause The specified switch port is isolated because of a segmentation due to mismatched configuration parameters. Recommended action 1. Based on the segmentation reason displayed with the message, look for a possible mismatch of relevant configuration parameters in the switches at both ends of the link. 2. Run the configure command to modify the appropriate switch parameters on both the local and remote switch.
PAGE 96
4. Run the fabStateShow command on both the receiving and transmitting switches. 5. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 6. Run the supportSave command and contact your switch service provider.
PAGE 97
Severity WARNING FABR-1006 Message timestamp, [FABR-1006], sequence-number,, WARNING, system-name, Node free error, caller: error-description Probable cause Fabric OS is trying to free or deallocate memory space that has already been deallocated. This message is rare and usually indicates a problem with Fabric OS. Recommended action In case of severe memory corruption, the system may recover by performing an automatic failover.
PAGE 98
FABR-1008 Message timestamp, [FABR-1008], sequence-number,, WARNING, system-name, error-description Probable cause Errors occurred during the request domain ID state; the information unit cannot be allocated or sent. If this message occurs with FABR-1005, the problem is usually transitory. Otherwise, this message is rare and usually indicates a problem with Fabric OS.
PAGE 99
FABR-1010 Message timestamp, [FABR-1010], sequence-number,, WARNING, system-name, error-description Probable cause Errors occurred while cleaning up the RDI (request domain ID). The error description provides further details. This message is rare and usually indicates a problem with Fabric OS. Recommended action If the message persists, run supportFtp as needed to set up automatic FTP transfers and then run the supportSave command and contact your switch service provider.
PAGE 100
Recommended action The fabric daemon takes proper action to recover from the error. If the message persists, run supportFtp as needed to set up automatic FTP transfers and then run the supportSave command and contact your switch service provider.
PAGE 101
Severity ERROR FABR-1015 Message timestamp, [FABR-1015], sequence-number,, ERROR, system-name, Insistent DID max retry exceeded: All E-Ports will be disabled. Switch is isolated. Probable cause The application exceeded RDI (request domain ID) requests for the insistent domain ID. All E_Ports are disabled, isolating the specified switch from the fabric. Recommended action Verify that the insistent domain ID is unique in the fabric and then reenable the E_Ports.
PAGE 102
Severity WARNING FABR-1019 Message timestamp, [FABR-1019], sequence-number,, CRITICAL, system-name, Critical fabric size (current-domains) exceeds supported configuration (supported-domains) Probable cause The switch is a value-line switch and has exceeded the limited fabric size; that is, a specified limit to the number of domains. This limit is defined by your specific value-line license key. The fabric size exceeds this specified limit and the grace period counter has started.
PAGE 103
FABR-1021 Message timestamp, [FABR-1021], sequence-number,, CRITICAL, system-name, Webtool is disabled Probable cause The switch has a value-line license and has a limited number of domains. If more than the specified number of domains are in the fabric, a counter is started to disable Web Tools. This grace period expired and Web Tools is disabled. Recommended action Bring the fabric size within the licensed limits.
PAGE 104
Probable cause The fabric size is within specified limits. Either a full fabric license was added or the size of the fabric was changed to within the licensed limit. Recommended action No action is required. Severity INFO FABR-1024 Message timestamp, [FABR-1024], sequence-number,, INFO, system-name, Initializing fabric size limit timer grace-period Probable cause The fabric size exceeds the limit set by your value-line switches.
PAGE 105
• DUAL_CR mode: Dual-credit flow control mode. In both of the previous modes, the buffer credits are fixed, based on the port configuration information. In this mode, the buffer credits are negotiated as part of ELP exchange. This mode also uses the R_RDY primitive for flow control. Recommended action No action is required.
PAGE 106
Severity WARNING FABS-1004 Message timestamp, [FABS-1004], sequence-number,, WARNING, system-name, function-name-and-description-of-problem process process-ID-number (current-command-name) pending-signal-number Probable cause An operation has been interrupted by a signal. This is usually an internal Fabric OS problem or file corruption. Recommended action Reboot or power cycle the switch.
PAGE 107
FABS-1006 Message timestamp, [FABS-1006], sequence-number,, WARNING, system-name, function-name-and-description-of-problem: object object-type-ID unit slot Probable cause There is no device in the slot with the specified object type ID in the system module record. This could indicate that a serious Fabric OS data problem on the switch.
PAGE 108
FABS-1008 Message timestamp, [FABS-1008], sequence-number,, WARNING, system-name, function-name: Media oid mapping failed Probable cause Fabric OS was unable to locate a necessary object handle. This is usually an internal Fabric OS problem or file corruption. Recommended action Reboot or power cycle the switch.
PAGE 109
2. If the message persists, run the firmwareDownload command to update the firmware. Severity WARNING Fibre Channel miscellaneous error messages FCMC-1001 Message timestamp, [FCMC-1001], sequence-number,, CRITICAL, system-name, function: failed-function-call failed, out of memory condition Probable cause The switch is low on memory and failed to allocate new memory for an information unit (IU). Recommended action A non-bladed switch reboots.
PAGE 110
Severity WARNING FCPD-1002 Message timestamp, [FCPD-1002], sequence-number,, WARNING, system-name, port port-number, bad R_CTL for fcp probing: 0xR_CTL-value Probable cause The response frame received on the specified port for an inquiry request contains an invalid value in the routing control field. Recommended action This can happen only if the firmware on the device controller on the specified port has a defect. Check with the device vendor for a firmware upgrade containing a defect fix.
PAGE 111
Fibre Channel physical layer error messages FCPH-1001 Message timestamp, [FCPH-1001], sequence-number,, CRITICAL, system-name, function: failed-function-call failed, out of memory condition Probable cause The switch is low on memory and failed to allocate new memory for a Fibre Channel driver instance. The function can only be fc_create. This function creates a Fibre Channel driver instance. The failed-function-call is kmalloc_wrapper failed. This function call is for kernel memory allocation.
PAGE 112
FLOOD error messages FLOD-1001 Message timestamp, [FLOD-1001], sequence-number,, WARNING, system-name, Unknown LSR type: port port-number, type LSR-header-type Probable cause The link state record (LSR) type is unknown. The only LSR header types are 1 for Unicast and 3 for Multicast. Recommended action No action is required. The record is discarded.
PAGE 113
Probable cause The LSU size exceeds what the system can support. Recommended action Reduce the number of switches in the fabric or reduce the number of redundant intersite links (ISLs) between two switches. Severity ERROR FLOD-1005 Message timestamp, [FLOD-1005], sequence-number,, WARNING, system-name, Invalid received domain ID: domain-number Probable cause The received LSR contained an invalid domain number. Recommended action No action is required. The LSR is discarded.
PAGE 114
Fabric shortest path first error messages FSPF-1001 Message timestamp, [FSPF-1001], sequence-number,, ERROR, system-name, Input Port port-number out of range Probable cause The specified input port number is out of range; it does not exist on the switch. Recommended action No action is required.
PAGE 115
Recommended action No action is required. The frame is discarded. Severity ERROR FSPF-1005 Message timestamp, [FSPF-1005], sequence-number,, ERROR, system-name, Wrong Section Id section-number, should be section-number, input port = port-number Probable cause An incorrect section ID has been reported from the specified input port. The section ID identifies a set of switches that share an identical topology database. The section ID is implemented inside the protocol.
PAGE 116
Fabric OS state synchronization framework error messages FSS-1001 Message timestamp, [FSS-1001], sequence-number,, WARNING, system-name, Application dropping HA data update. Probable cause An application dropped a high-availability (HA) data update. Recommended action 1. Run the haSyncStart command if the system is a dual-CP system; reboot the switch if it is a non-bladed system. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3.
PAGE 117
FSS-1003 Message timestamp, [FSS-1003], sequence-number,, WARNING, system-name, Application missing first HA data update Probable cause The FSS has dropped the update because an application has not set the transaction flag correctly. Recommended action 1. Run the haSyncStart command if the system is a dual-CP system; reboot the switch if it is a non-bladed system. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3.
PAGE 118
Probable cause The read system call to the FSS device failed. Recommended action Run supportFtp as needed to set up automatic FTP transfers and then run the supportSave command and contact your switch service provider. Severity WARNING FSS-1006 Message timestamp, [FSS-1006], sequence-number,, WARNING, system-name, No message available Probable cause Data is not available on the FSS device.
PAGE 119
Severity INFO FSSM-1003 Message timestamp, [FSSM-1003], sequence-number,, WARNING, system-name, HA State out of sync Probable cause The high-availability (HA) state for the active CP is out of synchronization with the HA state of the standby CP. If the active CP failover occurs when the HA state is out of sync, the failover is disruptive. Recommended action If this message was logged as a result of a user-initiated action (such as running the switchReboot command), then no action is required. 1.
PAGE 120
Fabric Watch module error messages FW-1001 Message timestamp, [FW-1001], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The internal temperature of the switch changed. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation. 1. To prevent recurring messages, disable the changed alarm for this threshold. 2.
PAGE 121
FW-1003 Message timestamp, [FW-1003], sequence-number,, WARNING, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The internal temperature of the switch rose above the high boundary to a value that may damage the switch. This message generally appears when a fan fails. If so, a fan-failure message accompanies this message. Recommended action Replace the fan.
PAGE 122
Probable cause The speed of the fan has changed. Fan problems usually contribute to temperature problems. Consistently abnormal fan speeds generally indicate that the fan is malfunctioning. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation. Severity INFO FW-1006 Message timestamp, [FW-1006], sequence-number,, WARNING, system-name, label, is below low boundary(High=high-value, Low=low-value).
PAGE 123
FW-1008 Message timestamp, [FW-1008], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The speed of the fan has changed from a value outside the acceptable range to a value within the acceptable range. Fan problems usually contribute to temperature problems. Consistently abnormal fan speeds generally indicate that the fan is failing. Recommended action No action is required.
PAGE 124
FW-1010 Message timestamp, [FW-1010], sequence-number,, WARNING, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The power supply is faulty. It is not producing enough power. Recommended action 1. Verify that you have installed the power supply correctly and that it is correctly seated in the chassis. 2. If the problem persists, replace the faulty power supply.
PAGE 125
Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation. Severity INFO FW-1033 Message timestamp, [FW-1033], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The temperature of the SFP changed. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 126
FW-1035 Message timestamp, [FW-1035], sequence-number,, WARNING, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The temperature of the SFP rose above the high boundary. Frequent fluctuations in temperature may indicate a deteriorating SFP. Recommended action Replace the SFP.
PAGE 127
Recommended action If this message occurs repeatedly, replace the SFP. Severity INFO FW-1038 Message timestamp, [FW-1038], sequence-number,, WARNING, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The receive power value of the SFP fell below the low boundary. The receive performance area measures the amount of incoming laser to help determine whether the SFP is in good working condition.
PAGE 128
FW-1040 Message timestamp, [FW-1040], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The receive power value of the SFP changed from a value outside the acceptable range to a value within the acceptable range. The receive performance area measures the amount of incoming laser to help determine whether the SFP is in good working condition.
PAGE 129
Probable cause The transmit power value of the SFP fell below the low boundary. The transmit-performance area measures the amount of outgoing laser to help determine whether the SFP is in good working condition. If the counter often exceeds the threshold, the SFP is deteriorating. Recommended action 1. Verify that your optical components are clean and function properly. 2. Check for damage from heat or age. 3. Replace deteriorating cables or SFPs.
PAGE 130
Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation. Severity INFO FW-1045 Message timestamp, [FW-1045], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The value of the SFP voltage changed. If the supplied voltage of the SFP transceiver is outside the normal range, this may indicate a hardware failure.
PAGE 131
FW-1047 Message timestamp, [FW-1047], sequence-number,, WARNING, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The value of the SFP voltage rose above the high boundary. The supplied current of the SFP transceiver is outside the normal range, indicating possible hardware failure. Recommended action Replace the SFP.
PAGE 132
Recommended action Replace the SFP. Severity INFO FW-1050 Message timestamp, [FW-1050], sequence-number,, WARNING, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The SFP voltage fell below the low boundary. Recommended action 1. Configure the low threshold to 1 so that the threshold triggers an alarm when the value falls to 0 (Out_of_Range). 2. If continuous or repeated alarms occur, replace the SFP before it deteriorates.
PAGE 133
FW-1052 Message timestamp, [FW-1052], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The value of the SFP voltage changed from a value outside the acceptable range to a value within the acceptable range. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 134
Probable cause The number of times E_Ports have gone down has fallen below the low boundary. E_Ports go down each time you remove a cable or SFP. SFP failures also cause E_Ports to go down. E_Ports going down may be caused by transient errors. A low number of E_Port failures means that the switch is functioning normally. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 135
Severity INFO FW-1117 Message timestamp, [FW-1117], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of fabric reconfigurations changed. The following actions can cause a fabric reconfiguration: • Two switches with the same domain ID have connected to one another. • Two fabrics are joined. • An E_Port went offline. • A principal link segmented from the fabric.
PAGE 136
Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation. Severity INFO FW-1119 Message timestamp, [FW-1119], sequence-number,, INFO, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of fabric reconfigurations rose above the high boundary.
PAGE 137
• An E_Port went offline. • A principal link segmented from the fabric. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation. Severity INFO FW-1121 Message timestamp, [FW-1121], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of domain ID changes changed.
PAGE 138
FW-1123 Message timestamp, [FW-1123], sequence-number,, INFO, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of domain ID changes rose above the high boundary. Domain ID changes occur when a conflict of domain IDs occur in a single fabric and the principal switch has to assign another domain ID to the switch. Recommended action No action is required.
PAGE 139
Probable cause The number of segmentations changed. Segmentation changes may occur due to: • Zone conflicts. • Domain conflicts. • Segmentation of the principal link between two switches. • Incompatible link parameters. During E_Port initialization, ports exchange link parameters. Rarely, incompatible parameters result in segmentation. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 140
FW-1127 Message timestamp, [FW-1127], sequence-number,, INFO, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of segmentations rose above the high boundary. Segmentation changes may occur due to: • Zone conflicts. • Domain conflicts. • Segmentation of the principal link between two switches. • Incompatible link parameters. During E_Port initialization, ports exchange link parameters.
PAGE 141
Severity INFO FW-1129 Message timestamp, [FW-1129], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of zone changes changed. Zone changes occur when a change is made to the effective zone configuration. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 142
FW-1131 Message timestamp, [FW-1131], sequence-number,, INFO, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of zone changes rose above the high boundary. Zone changes occur when a change is made to the effective zone configuration. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 143
Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation. Severity INFO FW-1134 Message timestamp, [FW-1134], sequence-number,, INFO, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of fabric logins fell below the low boundary. Fabric logins occur when a port or device initializes with the fabric. The event is called a fabric login or FLOGI.
PAGE 144
FW-1136 Message timestamp, [FW-1136], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of fabric logins changed from a value outside the acceptable range to a value within the acceptable range. Fabric logins occur when a port or device initializes with the fabric. The event is called a fabric login or FLOGI. Recommended action No action is required.
PAGE 145
Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation. Severity INFO FW-1139 Message timestamp, [FW-1139], sequence-number,, INFO, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of SFP state changes rose above the high boundary. SFP state changes occur when the SFP is inserted or removed. Recommended action No action is required.
PAGE 146
FW-1141 Message timestamp, [FW-1141], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of QuickLoop changes changed. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation. Severity INFO FW-1142 Message timestamp, [FW-1142], sequence-number,, INFO, system-name, label, is below low boundary(High=high-value, Low=low-value).
PAGE 147
Recommended action Verify that the cable is properly connected at both ends. This may be a transient error and may not require troubleshooting. Severity INFO FW-1144 Message timestamp, [FW-1144], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of QuickLoop changes changed from a value outside the acceptable range to a value within the acceptable range.
PAGE 148
FW-1161 Message timestamp, [FW-1161], sequence-number,, INFO, system-name, port-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of link failures that the port experiences fell below the low boundary. Link loss errors occur when a link experiences a loss of signal and fails. Both physical and hardware problems can cause link loss errors. Link loss errors frequently occur due to a loss of synchronization.
PAGE 149
FW-1163 Message timestamp, [FW-1163], sequence-number,, INFO, system-name, port-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of link failures that the port experiences changed from a value outside the acceptable range to a value within the acceptable range. Link loss errors occur when a link experiences a loss of signal and fails. Link loss errors frequently occur due to a loss of synchronization.
PAGE 150
FW-1165 Message timestamp, [FW-1165], sequence-number,, INFO, system-name, port-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of synchronization losses that the port experiences fell below the low boundary. Loss-of-synchronization errors frequently occur due to a faulty SFP or cable. Signal losses often create synchronization losses. A low number of synchronization losses means that the switch is functioning normally.
PAGE 151
FW-1167 Message timestamp, [FW-1167], sequence-number,, INFO, system-name, port-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of synchronization losses that the port experiences changed from a value outside the acceptable range to a value within the acceptable range. Loss-of-synchronization errors frequently occur due to a faulty SFP or cable. Signal losses often create synchronization losses.
PAGE 152
Probable cause The number of signal losses that the port experiences fell below the low boundary. Loss of signal generally indicates a physical problem. A low number of signal loss errors means that the switch is functioning normally. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 153
Severity INFO FW-1172 Message timestamp, [FW-1172], sequence-number,, INFO, system-name, port-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of protocol errors that the port experiences changed. Occasional protocol errors occur due to software glitches. Persistent protocol errors occur due to hardware problems. Recommended action Check both ends of your cable connection and verify that the cable and SFPs are not faulty.
PAGE 154
FW-1174 Message timestamp, [FW-1174], sequence-number,, WARNING, system-name, port-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of protocol errors that the port experiences rose above the high boundary. Occasional protocol errors occur due to software glitches. Persistent protocol errors occur due to hardware problems. Recommended action Check both ends of your connection and verify that your cable and SFP are not faulty.
PAGE 155
Probable cause The number of invalid words that the port experiences changed. Invalid words usually indicate a hardware problem with an SFP or cable. Recommended action Check both ends of your connections, your SFP, and your cable to verify that they are not faulty. Severity INFO FW-1177 Message timestamp, [FW-1177], sequence-number,, INFO, system-name, port-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit.
PAGE 156
FW-1179 Message timestamp, [FW-1179], sequence-number,, INFO, system-name, port-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of invalid words that the port experiences changed from a value outside the acceptable range to a value within the acceptable range. Invalid words usually indicate a hardware problem with an SFP or cable. Recommended action No action is required.
PAGE 157
FW-1181 Message timestamp, [FW-1181], sequence-number,, INFO, system-name, port-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of invalid CRCs that the port experiences fell below the low boundary. A low number of invalid CRCs means that the switch is functioning normally. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 158
Probable cause The number of invalid CRCs that the port experiences changed from a value outside the acceptable range to a value within the acceptable range. Frequent fluctuations in CRC errors generally indicate an aging fabric. Recommended action Respond to this message as is appropriate for the relevant policy of the end-user installation. 1. Check your SFPs, cables, and connections for faulty hardware. 2. Verify that all optical hardware is clean.
PAGE 159
Severity INFO FW-1186 Message timestamp, [FW-1186], sequence-number,, INFO, system-name, port-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The percentage of incoming traffic that the port experiences rose above the high boundary. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 160
FW-1188 Message timestamp, [FW-1188], sequence-number,, INFO, system-name, port-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The percentage of outgoing traffic that the port experiences changed. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 161
Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation. Severity INFO FW-1191 Message timestamp, [FW-1191], sequence-number,, INFO, system-name, port-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The percentage of outgoing traffic that the port experiences changed from a value outside the acceptable range to a value within the acceptable range.
PAGE 162
• Has become a trunk port Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation. Severity INFO FW-1193 Message timestamp, [FW-1193], sequence-number,, INFO, system-name, port-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of state changes that the port experiences fell below the low boundary.
PAGE 163
Probable cause The number of state changes that the port experiences rose above the high boundary. The state of the port has changed for one of the following reasons; the port: • Has gone offline • Has come online • Is testing • Is faulty • Has become an E_Port • Has become an F_Port • Has segmented • Has become a trunk port. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 164
Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation. Severity INFO FW-1216 Message timestamp, [FW-1216], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of AL_PA CRC errors changed. This indicates that errors were detected in the FC frame.
PAGE 165
Severity INFO FW-1218 Message timestamp, [FW-1218], sequence-number,, WARNING, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of CRC errors rose above the high boundary. This indicates that errors were detected in the FC frame. Invalid CRC messages occur when the number of CRC errors in Fibre Channel frames for specific source ID (S_ID) and destination ID (D_ID) pairs change.
PAGE 166
Severity INFO FW-1240 Message timestamp, [FW-1240], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of EE CRC errors changed. Invalid CRC messages occur when the number of CRC errors in Fibre Channel frames for specific source ID (S_ID) and destination ID (D_ID) pairs change. These messages may also be caused by dirty equipment, temperature fluctuations, and aging equipment.
PAGE 167
FW-1242 Message timestamp, [FW-1242], sequence-number,, WARNING, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of EE CRC errors rose above the high boundary. Invalid CRC messages occur when the number of CRC errors in Fibre Channel frames for specific source ID (S_ID) and destination ID (D_ID) pairs change. These messages may also be caused by dirty equipment, temperature fluctuations, and aging equipment.
PAGE 168
FW-1244 Message timestamp, [FW-1244], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of EE word frames that the switch receives changed. Receive-performance messages appear due to the number of word frames that travel from the configured S_ID to the D_ID pair. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 169
Probable cause The number of EE word frames that the switch receives rose above the high boundary. Receive-performance messages appear due to the number of word frames that travel from the configured S_ID to the D_ID pair. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 170
Severity INFO FW-1249 Message timestamp, [FW-1249], sequence-number,, INFO, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of EE word frames that the switch transmits fell below the low boundary. Transmit-performance messages appear due to the number of word frames that travel from the configured S_ID to the D_ID pair. Recommended action No action is required.
PAGE 171
FW-1251 Message timestamp, [FW-1251], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of EE word frames that the switch transmits changed from a value outside the acceptable range to a value within the acceptable range. Transmit-performance messages appear due to the number of word frames that travel from the configured S_ID to the D_ID pair. Recommended action No action is required.
PAGE 172
Probable cause The number of frame types or commands that the port receives fell below the low boundary. The port received SCSI Read, SCSI Write, SCSI Read and Write, SCSI Traffic, or IP commands in a frame. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation. Severity INFO FW-1274 Message timestamp, [FW-1274], sequence-number,, INFO, system-name, label, is above high boundary(High=Filter-counter, Low=Low-value).
PAGE 173
Severity INFO FW-1296 Message timestamp, [FW-1296], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of telnet violations changed. Telnet violations indicate that a telnet connection request was received from an unauthorized IP address. The TELNET_POLICY contains a list of TCP/IP addresses that are authorized to establish telnet connections to switches in the fabric.
PAGE 174
FW-1298 Message timestamp, [FW-1298], sequence-number,, WARNING, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of telnet violations rose above the high boundary. Telnet violations indicate that a telnet connection request was received from an unauthorized IP address. The TELNET_POLICY contains a list of TCP/IP addresses that are authorized to establish telnet connections to switches in the fabric.
PAGE 175
FW-1300 Message timestamp, [FW-1300], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of HTTP violations changed. HTTP violations indicate that a browser connection request was received from an unauthorized IP address. The HTTP_POLICY contains a list of TCP/IP addresses that are authorized to establish browser connections to the switches in the fabric.
PAGE 176
Probable cause The number of HTTP violations rose above the high boundary. HTTP violations indicate that a browser connection request was received from an unauthorized IP address. The HTTP_POLICY contains a list of TCP/IP addresses that are authorized to establish browser connections to the switches in the fabric. The IP addresses use the standard dot notation (for example, 255.255.255.255). Recommended action Run the errShow command to determine the IP address that sent the request.
PAGE 177
Recommended action Run the errShow command to determine the IP address that sent the request. Responses to security-class messages depend on user policies. Consult your security administrator for response strategies and policies. Severity INFO FW-1305 Message timestamp, [FW-1305], sequence-number,, INFO, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of API violations fess below the low boundary.
PAGE 178
FW-1307 Message timestamp, [FW-1307], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of API violations changed from a value outside the acceptable range to a value within the acceptable range. API violations indicate that an API connection request was received from an unauthorized IP address.
PAGE 179
Probable cause The number of RSNMP violations fell below the low boundary. RSNMP violations indicate that an SNMP get operation request was received from an unauthorized IP address. Recommended action No action is required. Severity INFO FW-1310 Message timestamp, [FW-1310], sequence-number,, WARNING, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of RSNMP violations rose above the high boundary.
PAGE 180
FW-1312 Message timestamp, [FW-1312], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of WSNMP violations changed. WSNMP violations indicate that an SNMP get/set operation request was received from an unauthorized IP address. Recommended action Run the errShow command to determine the IP address that sent the request. Responses to security-class messages depend on user policies.
PAGE 181
Recommended action Run the errShow command to determine the IP address that sent the request. Responses to security-class messages depend on user policies. Consult your security administrator for response strategies and policies. Severity WARNING FW-1315 Message timestamp, [FW-1315], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit.
PAGE 182
FW-1317 Message timestamp, [FW-1317], sequence-number,, INFO, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of SES violations fell below the low boundary. SES violations indicate that a SCSI Enclosure Services (SES) request was received from an unauthorized WWN. The SES_POLICY contains a list of WWNs of device ports that are allowed to access the SES Server functionality. Recommended action No action is required.
PAGE 183
Probable cause The number of SES violations changed from a value outside the acceptable range to a value within the acceptable range. SES violations indicate that a SCSI Enclosure Services (SES) request was received from an unauthorized WWN. The SES_POLICY contains a list of WWNs of device ports that are allowed to access the SES Server functionality. Recommended action No action is required.
PAGE 184
Severity INFO FW-1322 Message timestamp, [FW-1322], sequence-number,, WARNING, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of MS violations rose above the high boundary. MS violations indicate that a Management Server (MS) access request was received from an unauthorized WWN. The MS_POLICY contains a list of WWNs of device ports that are allowed to access the Management Server functionality.
PAGE 185
FW-1324 Message timestamp, [FW-1324], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of serial violations changed. Serial violations indicate that an unauthorized serial port request was received. The SERIAL_POLICY contains a list of switch WWNs for which serial port access is enabled. Recommended action Run the errShow command to determine the WWN of the device that sent the request.
PAGE 186
Probable cause The number of serial violations rose above the high boundary. Serial violations indicate that an unauthorized serial port request was received. The SERIAL_POLICY contains a list of switch WWNs for which serial port access is enabled. Recommended action Run the errShow command to determine the WWN of the device that sent the request. Responses to security-class messages depend on user policies. Consult your security administrator for response strategies and policies.
PAGE 187
Severity INFO FW-1329 Message timestamp, [FW-1329], sequence-number,, INFO, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of front panel violations fell below the low boundary. Front panel violations indicate that an unauthorized front panel request was received. The FRONTPANEL_POLICY contains a list of switch WWNs for which front panel access is enabled. Recommended action No action is required.
PAGE 188
FW-1331 Message timestamp, [FW-1331], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of front panel violations changed from a value outside the acceptable range to a value within the acceptable range. Front panel violations indicate that an unauthorized front panel request was received. The FRONTPANEL_POLICY contains a list of switch WWNs for which front panel access is enabled.
PAGE 189
Probable cause The number of SCC violations fell below the low boundary. SCC violations indicate that an unauthorized switch tried to join the fabric. The SCC_POLICY contains a list of switches by WWN that are allowed to be members of a fabric. Recommended action No action is required. Severity INFO FW-1334 Message timestamp, [FW-1334], sequence-number,, WARNING, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit.
PAGE 190
Severity INFO FW-1336 Message timestamp, [FW-1336], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of DCC violations has changed. DCC violations indicate that an unauthorized device tried to join the fabric. The DCC_POLICY allows for the specification of rules for binding device ports (typically HBA ports) to specific switch ports.
PAGE 191
FW-1338 Message timestamp, [FW-1338], sequence-number,, WARNING, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of DCC violations rose above the high boundary. DCC violations indicate that an unauthorized device tried to join the fabric. The DCC_POLICY allows for the specification of rules for binding device ports (typically HBA ports) to specific switch ports.
PAGE 192
FW-1340 Message timestamp, [FW-1340], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of login violations changed. Login violations indicate that a login failure was detected. Recommended action Run the errShow command to determine the IP location of the login attempt. Responses to security-class messages depend on user policies. Consult your security administrator for response strategies and policies.
PAGE 193
Recommended action Run the errShow command to determine the IP location of the login attempt. Responses to security-class messages depend on user policies. Consult your security administrator for response strategies and policies. Severity WARNING FW-1343 Message timestamp, [FW-1343], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit.
PAGE 194
Severity INFO FW-1345 Message timestamp, [FW-1345], sequence-number,, INFO, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of invalid timestamps fell below the low boundary. Invalid-timestamp violations indicate that a packet with an invalid timestamp was received from the primary fabric configuration server (FCS).
PAGE 195
Severity WARNING FW-1347 Message timestamp, [FW-1347], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of invalid timestamps changed from a value outside the acceptable range to a value within the acceptable range. Invalid-timestamp violations indicate that a packet with an invalid timestamp was received from the primary fabric configuration server (FCS).
PAGE 196
Severity INFO FW-1349 Message timestamp, [FW-1349], sequence-number,, INFO, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of invalid signatures fell below the low boundary. Invalid-signature violations indicate that a packet with an invalid signature was received from the primary fabric configuration server (FCS).
PAGE 197
Severity WARNING FW-1351 Message timestamp, [FW-1351], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of invalid signatures changed from a value outside the acceptable range to a value within the acceptable range. Invalid-signature violations indicate that a packet with an invalid signature was received from the primary fabric configuration server (FCS).
PAGE 198
Severity INFO FW-1353 Message timestamp, [FW-1353], sequence-number,, INFO, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of invalid certificates fell below the low boundary. A packet with an invalid certificate was received from the primary fabric configuration server (FCS).
PAGE 199
FW-1355 Message timestamp, [FW-1355], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of invalid certificates changed from a value outside the acceptable range to a value within the acceptable range. A packet with an invalid certificate has been received from the primary fabric configuration server (FCS).
PAGE 200
FW-1357 Message timestamp, [FW-1357], sequence-number,, INFO, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of authentication failures fell below the low boundary. Authentication failures can occur for many reasons. The switch on the other side may not support the protocol, have an invalid certificate, have a certificate that is not properly signed, or send unexpected packets.
PAGE 201
FW-1359 Message timestamp, [FW-1359], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of authentication failures changed from a value outside the acceptable range to a value within the acceptable range. Authentication failures can occur for many reasons.
PAGE 202
Probable cause The number of SLAP faulty packets fell below the low boundary. This counter keeps track of the number of unexpected SLAP packets and SLAP packets with faulty transmission IDs. Recommended action No action is required. Severity INFO FW-1362 Message timestamp, [FW-1362], sequence-number,, WARNING, system-name, label, is above high boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of SLAP faulty packets rose above the high boundary.
PAGE 203
FW-1364 Message timestamp, [FW-1364], sequence-number,, INFO, system-name, label, value has changed(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of time service (TS) out-of-sync violations changed. Recommended action Responses to security-class messages depend on user policies. Consult your security administrator for response strategies and policies.
PAGE 204
Recommended action Responses to security-class messages depend on user policies. Consult your security administrator for response strategies and policies. Severity WARNING FW-1367 Message timestamp, [FW-1367], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit.
PAGE 205
FW-1369 Message timestamp, [FW-1369], sequence-number,, INFO, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of no-FCS violations fell below the low boundary. This counter records how often the switch loses contact with the primary fabric configuration server (FCS) switch. When the primary FCS switch in the fabric sends its certificate to a switch, the receiving switch saves the WWN of that primary FCS switch.
PAGE 206
FW-1371 Message timestamp, [FW-1371], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of no-FCS violations changed from a value outside the acceptable range to a value within the acceptable range. This counter records how often the switch loses contact with the primary FCS switch.
PAGE 207
FW-1373 Message timestamp, [FW-1373], sequence-number,, INFO, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of incompatible security database violations fell below the low boundary. The number of secure switches with different version stamps was detected. When a switch is in secure mode, it connects only to another switch that is in secure mode and has a compatible security database.
PAGE 208
FW-1375 Message timestamp, [FW-1375], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of incompatible security database violations changed from a value outside the acceptable range to a value within the acceptable range. The number of secure switches with different version stamps have been detected.
PAGE 209
FW-1377 Message timestamp, [FW-1377], sequence-number,, INFO, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of illegal commands fell below the low boundary. This counter tracks how many times commands allowed only on the primary fabric configuration server (FCS) switch have been executed on a non-primary FCS switch.
PAGE 210
FW-1379 Message timestamp, [FW-1379], sequence-number,, INFO, system-name, label, is between high and low boundaries(High=high-value, Low=low-value). Current value is value unit. Probable cause The number of illegal commands changed from a value outside the acceptable range to a value within the acceptable range. This counter tracks how many times commands allowed only on the primary fabric configuration server (FCS) switch have been executed on a non-primary FCS switch.
PAGE 211
FW-1401 Message timestamp, [FW-1401], sequence-number,, INFO, system-name, label, is below low boundary(High=high-value, Low=low-value). Current value is value unit. Probable cause The flash usage percentage fell below the low boundary. Flash increases and decreases slightly with normal operation of the switch. Excessive permanent increases can lead to future problems. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 212
Probable cause The flash usage percentage changed from a value outside the acceptable range to a value within the acceptable range. Flash increases and decreases slightly with normal operation of the switch. Excessive permanent increases can lead to future problems. Recommended action No action is required. Respond to this message as is appropriate for the relevant policy of the end-user installation.
PAGE 213
FW-1426 Message timestamp, [FW-1426], sequence-number,, WARNING, system-name, Switch status change contributing factor Power supply: number-bad bad, number-missing absent. Probable cause The switch status is not in a healthy state because the number of faulty or missing power supplies is greater than or equal to the policy set by the switchStatusPolicySet command. Recommended action Replace the faulty or missing power supply.
PAGE 214
Recommended action Replace the missing power supply. Severity WARNING FW-1429 Message timestamp, [FW-1429], sequence-number,, WARNING, system-name, Switch status change contributing factor: Power supplies are not redundant. Probable cause The switch status is not in a healthy state because the power supplies are not in the correct slots for redundancy. Recommended action Rearrange the power supplies so that one is in an odd slot and other in an even slot to make them redundant.
PAGE 215
FW-1431 Message timestamp, [FW-1431], sequence-number,, WARNING, system-name, Switch status change contributing factor Fan: number-bad bad. Probable cause The switch status is not in a healthy state because the number of faulty fans is greater than or equal to the policy set by the switchStatusPolicySet command. A fan is faulty when sensor value is not in the acceptable range or is faulty. Recommended action Replace the faulty or deteriorating fan FRUs.
PAGE 216
Probable cause The switch status is not in a healthy state because the number of faulty control processors (CPs) is greater than or equal to the policy set by the switchStatusPolicySet command. The CPs are non-redundant. If you power cycle a SAN Director 2/128 chassis in dual-domain configuration, and then reset the micro-switch of the active CP before the heartbeat is up, both CPs to come up in a non-redundant state. Recommended action 1.
PAGE 217
Recommended action Run the saveCore command to clear out the kernel flash. Refer to the HP StorageWorks Fabric OS 4.x command reference guide for more information about this command. Severity WARNING FW-1436 Message timestamp, [FW-1436], sequence-number,, WARNING, system-name, Switch status change contributing factor Marginal ports: number-of-marginal-ports marginal ports.
PAGE 218
FW-1438 Message timestamp, [FW-1438], sequence-number,, WARNING, system-name, Switch status change contributing factor Missing SFPs: number-of-missing-SFPs missing SFPs. Probable cause The switch status is not in a healthy state because the number of missing SFPs is greater than or equal to the policy set by the switchStatusPolicySet command. Recommended action Run the switchStatusPolicySet command to modify the SFP policy or to add SFPs to the empty ports.
PAGE 219
Recommended action No action is required. Verify that the event was planned. Severity INFO FW-1441 Message timestamp, [FW-1441], sequence-number,, INFO, system-name, FRU-label state has changed to inserted. Probable cause The state of the specified FRU changed to inserted. This means that a FRU is inserted but not powered on. Recommended action No action is required. Verify that the event was planned.
PAGE 220
FW-1443 Message timestamp, [FW-1443], sequence-number,, INFO, system-name, FRU-label state has changed to off. Probable cause The state of the specified FRU changed to off. Recommended action No action is required. Verify that the event was planned. Severity INFO FW-1444 Message timestamp, [FW-1444], sequence-number,, WARNING, system-name, FRU-label state has changed to faulty. Probable cause The state of the specified FRU changed to faulty. Recommended action Replace the FRU.
PAGE 221
The active CP continues to function normally, but because the standby CP is not healthy, nondisruptive failover is not possible. Recommended action 1. Reboot the standby CP blade by ejecting the card and reseating it. 2. If the problem persists, replace the standby CP.
PAGE 222
Severity INFO HAM-1005 Message timestamp, [HAM-1005], sequence-number,, CRITICAL, system-name, error-text Probable cause The high-availability manager (HAM) has encountered a critical error. Recommended action 1. Run the haDump command and capture output. 2. Call your switch service provider.
PAGE 223
HAMK-1002 Message timestamp, [HAMK-1002], sequence-number,, WARNING, system-name, Heartbeat down Probable cause The active CP blade determined that the standby CP blade is down. This may occur as a result of an operator-initiated action, such as firmwareDownload, if the standby CP blade is reset or removed, or as a result of an error in the standby CP blade. Recommended action 1. Monitor the standby CP blade for a few minutes.
PAGE 224
Hardware independent layer error messages HIL-1101 Message timestamp, [HIL-1101], sequence-number,, ERROR, system-name, Slot slot-number faulted, nominal-voltage (measured-voltage) is above threshold. Probable cause The blade voltage is above threshold. This message is specific to the Core Switch 2/64 or SAN Director 2/128. Recommended action Replace the faulty blade.
PAGE 225
Probable cause The fan voltage is above threshold. Recommended action 1. Run the psShow command to verify the power supply status. 2. Try to reseat the faulty fan FRU and power supply FRU to verify that they are seated properly. 3. If the problem persists, replace the fan FRU or the power supply FRU as necessary. Severity ERROR HIL-1104 Message timestamp, [HIL-1104], sequence-number,, ERROR, system-name, Blower blower-number faulted, nominal-voltage (measured-voltage) is below threshold.
PAGE 226
For the SAN Switch 4/32, if the 12-volt level is faulty, replace one or both power supplies; if any other voltage is faulty, replace the entire switch. Severity ERROR HIL-1106 Message timestamp, [HIL-1106], sequence-number,, ERROR, system-name, Switch error, nominal-voltage (measured-voltage) below threshold. Probable cause Switch voltage is below threshold. This message is specific to non-bladed switches and is not applicable to the Core Switch 2/64 or SAN Director 2/128.
PAGE 227
Severity CRITICAL HIL-1108 Message timestamp, [HIL-1108], sequence-number,, CRITICAL, system-name, Switch faulted, nominal-voltage (measured-voltage) below threshold. System preparing for reset. Probable cause Switch voltage is below threshold. This message is specific to non-bladed switches and is not applicable to the Core Switch 2/64 or SAN Director 2/128. Recommended action For the SAN Switch 2/8V and SAN Switch 2/16V, replace the entire switch; these switches do not have FRUs.
PAGE 228
Severity WARNING HIL-1202 Message timestamp, [HIL-1202], sequence-number,, ERROR, system-name, Blower blower-number faulted, speed (measured-speed RPM) below threshold. Probable cause The specified fan speed (in RPM) fell below the minimum threshold. Recommended action Replace the fan FRU. Severity ERROR HIL-1203 Message timestamp, [HIL-1203], sequence-number,, ERROR, system-name, Fan fan-number faulted, speed (measured-speed RPM) above threshold.
PAGE 229
HIL-1204 Message timestamp, [HIL-1204], sequence-number,, ERROR, system-name, Fan fan-number faulted, speed (measured-speed RPM) below threshold. Probable cause The specified fan speed (in RPM) fell below the minimum threshold. This message is specific to non-bladed switches and is not applicable to the Core Switch 2/64 or SAN Director 2/128. Recommended action For the SAN Switch 2/32 and SAN Switch 4/32, replace the fan FRU.
PAGE 230
HIL-1206 Message timestamp, [HIL-1206], sequence-number,, ERROR, system-name, Fan fan-number sensor sensor-number, speed (measured-speed RPM) below threshold. Probable cause The specified fan speed (in RPM) fell below the minimum threshold. This problem can quickly cause the switch to overheat. This message is specific to non-bladed switches and is not applicable to the Core Switch 2/64 or SAN Director 2/128. Recommended action For the SAN Switch 2/32 and SAN Switch 4/32, replace the fan FRU.
PAGE 231
Probable cause Multiple fan FRUs failed on a switch. This message is often preceded by a low-fan-speed message. Recommended action Replace the faulty fan FRUs immediately. Severity ERROR HIL-1303 Message timestamp, [HIL-1303], sequence-number,, ERROR, system-name, One fan failed. Replace failed fan FRU immediately. Probable cause A fan FRU failed. This message is often preceded by a low-fan-speed message. Recommended action Replace the faulty fan FRU immediately.
PAGE 232
HIL-1305 Message timestamp, [HIL-1305], sequence-number,, ERROR, system-name, One or two fan(s) failed. Replace failed fan FRU(s) immediately. Probable cause One or two fan FRUs failed. This message is often preceded by a low-fan-speed message. Recommended action Replace the faulty fan FRUs immediately. Severity ERROR HIL-1306 Message timestamp, [HIL-1306], sequence-number,, ERROR, system-name, Three fans failed. Replace failed fan FRUs immediately. Probable cause Three fan FRUs failed.
PAGE 233
Severity ERROR HIL-1308 Message timestamp, [HIL-1308], sequence-number,, ERROR, system-name, All fans failed. Replace failed fan FRUs immediately. Probable cause All fans failed. This message is often preceded by a low-fan-speed message. Recommended action Replace the faulty fan FRUs immediately. Severity ERROR HIL-1309 Message timestamp, [HIL-1309], sequence-number,, ERROR, system-name, count fan FRU(s) failed. Replace failed fan FRU(s) immediately. Probable cause Multiple fans failed.
PAGE 234
Recommended action Install the missing fan FRU. Severity WARNING HIL-1402 Message timestamp, [HIL-1402], sequence-number,, WARNING, system-name, Two fan FRUs missing. Install fan FRUs immediately. Probable cause Two fan FRUs were removed. Recommended action Install the missing fan FRUs immediately. Severity WARNING HIL-1403 Message timestamp, [HIL-1403], sequence-number,, WARNING, system-name, All fan FRUs missing. Install fan FRUs immediately. Probable cause All fan FRUs were removed.
PAGE 235
Probable cause One or more fan FRUs were removed. Recommended action Install the missing fan FRUs immediately. Severity WARNING HIL-1501 Message timestamp, [HIL-1501], sequence-number,, WARNING, system-name, Slot slot-number, high temperature (measured-temperature). Probable cause The temperature of this blade rose above the warning threshold. Recommended action 1. Run the fanShow command to verify that all fans are operating properly. 2.
PAGE 236
Severity CRITICAL HIL-1503 Message timestamp, [HIL-1503], sequence-number,, CRITICAL, system-name, Slot slot-number, unit shutting down. Probable cause The temperature of this blade kept above the maximum threshold for at least two minutes. The blade is shut down to prevent further damage. This usually follows a high-temperature warning message. Recommended action 1. Run the fanShow command to verify all the fans are working properly. 2.
PAGE 237
HIL-1505 Message timestamp, [HIL-1505], sequence-number,, WARNING, system-name, High temperature (measured-temperature C) exceeds environmental specifications. Probable cause Temperature in the system rose above the warning threshold. Recommended action 1. Run the fanShow command to verify all the fans are working properly. 2. Make sure that the area is well ventilated and that the room temperature is within operational range of your switch.
PAGE 238
HIL-1507 Message timestamp, [HIL-1507], sequence-number,, CRITICAL, system-name, High temperature warning time expired. System preparing for shutdown. Probable cause Temperature in the system rose above the critical threshold. Recommended action Temperatures have probably caused damage to the switch; the system shuts down automatically. 1. To help prevent future problems, make sure that all the fans are working properly. 2.
PAGE 239
HIL-1509 Message timestamp, [HIL-1509], sequence-number,, CRITICAL, system-name, High temperature (measured-temperature C). Warning time expired. System preparing for shutdown. Probable cause Temperature in the system rose above the critical threshold. Temperature has probably caused damage to the switch; the system shuts down automatically. Recommended action 1. To help prevent future problems, make sure that all the fans are working properly. 2.
PAGE 240
HIL-1602 Message timestamp, [HIL-1602], sequence-number,, CRITICAL, system-name, All temperature sensors failed. Service immediately. Probable cause Temperature readings from all sensors are out of range. Recommended action 1. Run the fanShow command to verify that all fans are operating correctly. 2. Replace any deteriorating fan FRUs. 3. Run the tempShow command to verify temperature values. 4. If any sensor is too high, monitor the switch. Try rebooting or power cycling the switch.
PAGE 241
HLO-1002 Message timestamp, [HLO-1002], sequence-number,, ERROR, system-name, Incompatible Hello timeout HLO-timeout from port port-number, correct value correct-value Probable cause The HLO message is incompatible with the value specified in the FSPF protocol. The switch does not accept FSPF frames from the remote switch. In the Fabric OS, the HLO timeout value is not configurable, so this error can occur only when the HP StorageWorks switch is connected to a switch from another manufacturer.
PAGE 242
Health monitor error messages HMON-1001 Message timestamp, [HMON-1001], sequence-number,, CRITICAL, system-name, failure-description Probable cause A problem was encountered reading an essential file containing configuration information from the nonvolatile storage device. This could be the result of a missing file or a corrupt file system. Recommended action 1. Run the firmwareDownload command to reinstall the firmware to your switch. 2.
PAGE 243
Kernel software watchdog error messages KSWD-1003 Message timestamp, [KSWD-1003], sequence-number,, WARNING, system-name, kSWD: warning-message Probable cause A warning state exists within the system. Recommended action No action is required. Severity WARNING Kernel RAS trace module error messages KTRC-1001 Message timestamp, [KTRC-1001], sequence-number,, WARNING, system-name, Dump memory size exceeds dump file size Probable cause The dump memory size exceeds the dump file size.
PAGE 244
Probable cause The initial background dump has not completed. Recommended action No action is required. Severity INFO KTRC-1003 Message timestamp, [KTRC-1003], sequence-number,, ERROR, system-name, Cannot open ATA dump device Probable cause The ATA dump driver is not initialized properly. Recommended action Properly initialize the ATA dump driver.
PAGE 245
RASLog subsystem error messages LOG-1000 Message timestamp, [LOG-1000], sequence-number,, INFO, system-name, Previous message repeated repeat-count time(s) Probable cause The previous message was repeated the number of times specified. Recommended action No action is required. Severity INFO LOG-1001 Message timestamp, [LOG-1001], sequence-number,, CRITICAL, system-name, A log message was dropped Probable cause A log message was dropped. A trace dump file was created. Recommended action 1.
PAGE 246
Probable cause A message was not recorded by the error logging system. A trace dump file was created. The message may still be visible through SNMP or other management tools. Recommended action 1. Run the reboot command for non-bladed switches or the haFailover command on bladed switches. 2. Run the saveCore command to FTP core files to a server location. 3. Run supportFtp as needed to set up automatic FTP transfers. 4. Run the supportSave command and contact your switch service provider.
PAGE 247
An incarnation is a progressive number that identifies the most recent version of the link state record (LSR). The switch generates its local LSR when first enabled. Recommended action No action is required. The incarnation count begins again at 1 after reaching 239.
PAGE 248
Multicast path error messages MPTH-1001 Message timestamp, [MPTH-1001], sequence-number,, ERROR, system-name, Null parent, lsId = number Probable cause A null parent was reported. MPATH uses a tree structure in which the parent is used to connect to the root of the tree. Recommended action No action is required. Severity ERROR MPTH-1002 Message timestamp, [MPTH-1002], sequence-number,, ERROR, system-name, Null lsrP, lsId = ls-ID-number Probable cause A link state record is null.
PAGE 249
Probable cause The FSPF module determined that no minimum cost path (MPath) is available in the candidate list. Recommended action No action is required. Severity WARNING Message queue error messages MQ-1004 Message timestamp, [MQ-1004], sequence-number,, ERROR, system-name, mqRead, queue = queue-name, queue ID = queue-ID, type = message-type Probable cause An unexpected message was received in the specified message queue. The queue-name is always fspf_q.
PAGE 250
ERROR Management service error messages MS-1001 Message timestamp, [MS-1001], sequence-number,, WARNING, system-name, MS Platform Segmented port=port-number(reason-for-segmentation domain) Probable cause The management server (MS) segmented from another switch domain at the specified port-number due to errors or inconsistencies defined in the MS platform service. Recommended action Reboot or power cycle the switch.
PAGE 251
• No Resp for GCAP from No action is required. • GCAP sup but not PL by Set the flag for the MS Platform Service. • GCAP Rejected (reason =BUSY) by Run the firmwareDownload command to upgrade the firmware level on the switch to a level that supports reliable commit service (RCS). RCS is supported in Fabric OS v2.6, v3.1 and later, and v4.1 and later. • Reject EXGPLDB from Wait a few minutes and try the command again.
PAGE 252
MS-1004 Message timestamp, [MS-1004], sequence-number,, INFO, system-name, MS detected ONLY 1 Domain(d=domain-in-local-resource). Probable cause MS detected an unstable count of domains in its own local resource. Recommended action This message is often transitory. 1. The fabric may be reconfiguring, forming, or merging. Wait a few minutes and try the operation again. 2.
PAGE 253
MS-1006 Message timestamp, [MS-1006], sequence-number,, ERROR, system-name, MS Unexpected iu_data_sz=number-of-bytes Probable cause MS received IU data of unexpected size. The IU payload and the IU size may be inconsistent with each other or with the command that is currently being processed. Recommended action 1. Wait a few minutes and try the operation again. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3.
PAGE 254
MS-1008 Message timestamp, [MS-1008], sequence-number,, ERROR, system-name, MS Failure while initializing action Probable cause MS failed while initializing the specified action. The following actions may be displayed: • while writing to ms_els_q MS is unable to write a message to the MS Extended Link Service Queue. • while inserting timer to timer list MS is unable to add a timer to a resource. Recommended action This message is often transitory.
PAGE 255
Neighboring switch finite state machine error messages NBFS-1001 Message timestamp, [NBFS-1001], sequence-number,, INFO, system-name, Duplicate E_Port SCN from port portnumber in state state-change-name (state-change-number) Probable cause A duplicate E_Port State Change Number was reported. The neighbor finite state machine (NBFSM) states are as follows: • 0, Down • 1, Init • 2, Database Exchange • 3, Database Acknowledge Wait • 4, Database Wait • 5, Full Recommended action No action is required.
PAGE 256
• 4, Database Wait • 5, Full If this error occurs repeatedly, it means that the protocol implementation between two connected switches has problems. Recommended action Run the nbrStateShow command to check the neighbor state of the port listed in the message. If it is FULL, then this message can safely be ignored. Otherwise, run the portDisable and portEnable commands to refresh the port.
PAGE 257
Simple name server module error messages NS-1001 Message timestamp, [NS-1001], sequence-number,, WARNING, system-name, The response for request 0xCT-command-code from remote switch 0xDomain-ID is larger than the max frame size the remote switch can support! Probable cause The response payload exceeds the maximum frame size that the remote switch can handle. Recommended action Run the firmwareDownload command to upgrade the remote switch with v4.3 or later, or v3.
PAGE 258
NS-1003 Message timestamp, [NS-1003], sequence-number,, INFO, system-name, Number of local devices Current-local-device-count, exceeds the standby can support Local-device-count-that-standby-can-support, can't send update. Probable cause The name server on the standby CP has lower supported capability than the active CP due to different firmware versions running on the active and standby control processors (CPs). This means that the active and standby CPs are out of sync.
PAGE 259
Parity data manager error messages PDM-1001 Message timestamp, [PDM-1001], sequence-number,, WARNING, system-name, Failed to parse the pdm config Probable cause The PDM process could not parse the configuration file. This may be caused by a missing configuration file during the installation. Recommended action 1. Run the firmwareDownload command to reinstall the firmware. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3.
PAGE 260
Probable cause A syntax error occurred when trying to launch the PDM process. Recommended action 1. Run the firmwareDownload command to reinstall the firmware. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3. Run the supportSave command and contact your switch service provider. Severity WARNING PDM-1004 Message timestamp, [PDM-1004], sequence-number,, WARNING, system-name, Memory shortage Probable cause The PDM process ran out of memory. Recommended action 1.
PAGE 261
Severity WARNING PDM-1006 Message timestamp, [PDM-1006], sequence-number,, WARNING, system-name, Too many files in sync.conf Probable cause The configuration file sync.conf contains too many entries. Recommended action 1. Run the firmwareDownload command to reinstall the firmware. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3. Run the supportSave command and contact your switch service provider.
PAGE 262
PDM-1008 Message timestamp, [PDM-1008], sequence-number,, WARNING, system-name, Failed to get the number of uports Probable cause The PDM system call to getcfg failed. Recommended action 1. Run the firmwareDownload command to reinstall the firmware. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3. Run the supportSave command and contact your switch service provider.
PAGE 263
Recommended action 1. Run the firmwareDownload command to reinstall the firmware. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3. Run the supportSave command and contact your switch service provider. Severity WARNING PDM-1011 Message timestamp, [PDM-1011], sequence-number,, WARNING, system-name, File read failed: file-name Probable cause The PDM process could not read data from the specified file name. Recommended action 1.
PAGE 264
PDM-1013 Message timestamp, [PDM-1013], sequence-number,, WARNING, system-name, File empty: file-name Probable cause The switch configuration file /etc/fabos/fabos.[0|1].conf is empty. Recommended action 1. Run the firmwareDownload command to reinstall the firmware. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3. Run the supportSave command and contact your switch service provider.
PAGE 265
Recommended action 1. Run the firmwareDownload command to reinstall the firmware. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3. Run the supportSave command and contact your switch service provider. Severity CRITICAL PDM-1019 Message timestamp, [PDM-1019], sequence-number,, WARNING, system-name, File path or trigger too long Probable cause One line of the pdm.conf file is too long. Recommended action 1.
PAGE 266
PDM-1021 Message timestamp, [PDM-1021], sequence-number,, WARNING, system-name, Failed to download area port map Probable cause A system call failed. Recommended action 1. Run the firmwareDownload command to reinstall the firmware. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3. Run the supportSave command and contact your switch service provider.
PAGE 267
PDTR-1002 Message timestamp, [PDTR-1002], sequence-number,, INFO, system-name, informational message Probable cause Information was written to the panic dump and core dump files and a trap was generated. The watchdog register codes are as follows: • 0x10000000 bit set means that the watch dog timer (WDT) forced a core reset. • 0x20000000 bit set means that the WDT forced a chip reset. • All other code values are reserved.
PAGE 268
Port error messages PORT-1003 Message timestamp, [PORT-1003], sequence-number,, WARNING, system-name, Port port-number Faulted because of many Link Failures Probable cause The specified port is now disabled because the link on this port had multiple failures that exceed an internally set threshold on the port. This problem is typically related to hardware. Recommended action 1.
PAGE 269
Performance server error messages PS-1000 Message timestamp, [PS-1000], sequence-number,, CRITICAL, system-name, Failed to initialize Advanced Performance Monitoring. Probable cause An unexpected software error occurred in Advanced Performance Monitoring. The Performance Monitor failed to initialize. Recommended action The control processor (CP) should reboot or fail over automatically. If it does not, reboot or power cycle the switch to reinitiate the firmware.
PAGE 270
Probable cause An unexpected software error occurred in Advanced Performance Monitoring. The Performance Monitor tracing system failed to initialize. Recommended action Tracing is be available for Advanced Performance Monitoring, but other functions should perform normally. To reactivate tracing, reboot or fail over the CP. Severity ERROR PS-1003 Message timestamp, [PS-1003], sequence-number,, WARNING, system-name, Failed to set end-to-end monitoring mask on ISL ports.
PAGE 271
PS-1005 Message timestamp, [PS-1005], sequence-number,, WARNING, system-name, ISL monitor on port port stopped counting because no hardware resources are available Probable cause ISL and end-to-end monitors used all the hardware resources. Recommended action To resume counting, delete some end-to-end monitors sharing the same hardware resource pool.
PAGE 272
Probable cause The portSwap feature was enabled in the switch by the user. Recommended action No action is required. Severity INFO PSWP-1003 Message timestamp, [PSWP-1003], sequence-number,, INFO, system-name, Port Swap feature disabled Probable cause The portSwap feature was disabled in the switch by the user. Recommended action No action is required.
PAGE 273
Reliable commit service error messages RCS-1001 Message timestamp, [RCS-1001], sequence-number,, INFO, system-name, RCS has been disabled. Some switches in the fabric do not support this feature Probable cause The RCS feature was disabled on the local switch because not all switches in the fabric support RCS or the switch is in nonnative mode. Recommended action 1. Run the rcsInfoShow command to view RCS capability on the fabric. RCS is supported in Fabric OS v2.6, v3.1 and later, v4.1 and later. 2.
PAGE 274
Probable cause The specified RCS function failed to allocate memory. Recommended action 1. This message is usually transitory. Wait a few minutes and retry the command. 2. Check memory usage on the switch using the memShow command. 3. Reboot or power cycle the switch. Severity ERROR RCS-1004 Message timestamp, [RCS-1004], sequence-number,, ERROR, system-name, Application(application-name) not registered.(error-string) Probable cause The specified application did not register with RCS.
PAGE 275
2. If the reject is in the SFC phase, check whether the application license exists for the local domain and whether the application data is compatible. Severity INFO RCS-1006 Message timestamp, [RCS-1006], sequence-number,, INFO, system-name, State RCS-phase, Application application-ID, RCS CM. Domain domain-ID-that-sent-the-reject returned 0xreject-code. Probable cause A remote domain rejected an RCS phase initiated by an application on the local switch.
PAGE 276
Severity WARNING RPCD-1002 Message timestamp, [RPCD-1002], sequence-number,, WARNING, system-name, Missing certificate file. Secure RPCd is disabled. Probable cause An SSL certificate is missing. Recommended action To enable RPCD in secure mode, install a valid SSL certificate for the switch. Severity WARNING RPCD-1003 Message timestamp, [RPCD-1003], sequence-number,, WARNING, system-name, Permission denied accessing certificate file. Secure RPCd is disabled.
PAGE 277
Probable cause The SSL certificate file is corrupted. Recommended action To enable RPCD in secure mode, install a valid SSL certificate on the switch. Severity WARNING RPCD-1005 Message timestamp, [RPCD-1005], sequence-number,, WARNING, system-name, Missing private key file. Secure RPCd is disabled. Probable cause The private key file is missing. Recommended action Run the pkiCreate command to install a valid private key file.
PAGE 278
RPCD-1007 Message timestamp, [RPCD-1007], sequence-number,, WARNING, system-name, Invalid private file. Secure RPCd is disabled. Probable cause The private key file is corrupted. Recommended action Run the pkiCreate command to install a valid private key file.
PAGE 279
Probable cause The RTWR exhausted the maximum number of retries sending data to the specified domain. Details are as follows: • RTWR error message: Max retries exhausted • detail1: Port • detail2: Domain • detail3: Retry Count • detail4: Status • detail5: Process ID Recommended action 1. Run the fabricShow command to see if the specified domain ID is online. 2. Enable the switch with the specified domain ID. 3. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 4.
PAGE 280
• nsd • psd • snmpd • zoned • fspfd • tsd Recommended action If the message is caused by the system being busy, the condition is temporary. 1. If the message is caused by a hung daemon, the software watchdog causes the daemon to dump the core and reboot the switch. In this case, run the saveCore command to send the core files using FTP to a secure server location. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3.
PAGE 281
Severity ERROR SEC-1002 Message timestamp, [SEC-1002], sequence-number,, ERROR, system-name, Security data fails: reason-text Probable cause The receiving switch failed to validate the security database sent from the primary FCS switch. This can result from the data package being corrupted, the time stamp on the package being out of range (as a result of replay attack or out-of-sync time service), or the signature verification having failed.
PAGE 282
SEC-1005 Message timestamp, [SEC-1005], sequence-number,, INFO, system-name, Primary FCS receives data request from domain domain-number Probable cause The primary FCS received a data request from the specified domain. For example, if the switch fails to update the database or is attacked (data injection), a message is generated to the primary FCS to try to correct and resync with the rest of the switches in the fabric.
PAGE 283
SEC-1007 Message timestamp, [SEC-1007], sequence-number,, INFO, system-name, Security violation: Unauthorized host with IP address IP-address-of-the-violating-host tries to establish API connection. Probable cause A security violation was reported. The IP address of the unauthorized host is displayed in the message. Recommended action Check for unauthorized access to the switch through the API connection.
PAGE 284
Recommended action Check for unauthorized access to the switch through the telnet connection. Severity INFO SEC-1016 Message timestamp, [SEC-1016], sequence-number,, INFO, system-name, Security violation: Unauthorized host with IP address IP-address-of-the-violating-host tries to establish SSH connection. Probable cause A security violation was reported. The IP address of the unauthorized host is displayed in the message.
PAGE 285
SEC-1024 Message timestamp, [SEC-1024], sequence-number,, INFO, system-name, The DB-name security database is too large to fit in flash. Probable cause The size of the security database is too large for the flash memory. The size of the security database increases with the number of entries in each policy. Recommended action Reduce the size of the security database by reducing the number of entries within each policy.
PAGE 286
This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state. If a switch is in the error state, the database may not be correctly updated for that specific switch.
PAGE 287
Severity ERROR SEC-1030 Message timestamp, [SEC-1030], sequence-number,, ERROR, system-name, The length of the name invalid. Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence.
PAGE 288
SEC-1032 Message timestamp, [SEC-1032], sequence-number,, ERROR, system-name, Empty FCS list is not allowed. Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent.
PAGE 289
Probable cause The input list has an invalid member. Recommended action Verify your member names and then input the correct information. Severity ERROR SEC-1035 Message timestamp, [SEC-1035], sequence-number,, ERROR, system-name, Invalid device WWN device-WWN. Probable cause The specified WWN is invalid. Recommended action Enter the correct WWN value. Severity ERROR SEC-1036 Message timestamp, [SEC-1036], sequence-number,, ERROR, system-name, Invalid device name device-name.
PAGE 290
SEC-1037 Message timestamp, [SEC-1037], sequence-number,, ERROR, system-name, Invalid WWN format invalid-WWN. Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent.
PAGE 291
SEC-1040 Message timestamp, [SEC-1040], sequence-number,, ERROR, system-name, Invalid portlist (port-list). Cannot combine * with port member in the same portlist. Probable cause The port list contains the wildcard asterisk (*) character. Recommended action You cannot use the asterisk in a port list. Enter the port list values without wildcards. Severity ERROR SEC-1041 Message timestamp, [SEC-1041], sequence-number,, ERROR, system-name, Invalid port member port-member in portlist (port-list). reason.
PAGE 292
Probable cause The specified area member is not within the minimum and maximum values. Recommended action Use valid syntax when entering area numbers. Severity ERROR SEC-1043 Message timestamp, [SEC-1043], sequence-number,, ERROR, system-name, Invalid port range range-minimum - range-maximum. Probable cause The specified port is not within the minimum and maximum range. Recommended action Use valid syntax when entering port ranges.
PAGE 293
SEC-1045 Message timestamp, [SEC-1045], sequence-number,, ERROR, system-name, Too many port members. Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent.
PAGE 294
Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state.
PAGE 295
Recommended action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state. If a switch is in the error state, the database may be correctly updated for that specific switch. Severity ERROR SEC-1052 Message timestamp, [SEC-1052], sequence-number,, ERROR, system-name, Invalid input. Probable cause A corruption occurred during the distribution of the security database.
PAGE 296
Severity ERROR SEC-1054 Message timestamp, [SEC-1054], sequence-number,, ERROR, system-name, Invalid FCS list length list-length Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence.
PAGE 297
SEC-1056 Message timestamp, [SEC-1056], sequence-number,, ERROR, system-name, Invalid position new-position. Only number-of-members-in-FCS-list members in list. Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence.
PAGE 298
Probable cause The operation failed when writing to flash. Recommended action Run the saveCore command to move files off the kernel flash. Severity ERROR SEC-1062 Message timestamp, [SEC-1062], sequence-number,, ERROR, system-name, Invalid number of Domains in Domain List. Probable cause Either no domains are specified or domains greater than the maximum are specified. Recommended action Enter the correct number of domains.
PAGE 299
SEC-1064 Message timestamp, [SEC-1064], sequence-number,, ERROR, system-name, Failed to sign message. Probable cause The PKI objects on the switch are not in a valid state and the signature operation failed. Recommended action Run the pkiShow command to verify that all PKI objects are valid. If PKI objects are not valid, generate the PKI objects and install the certificate by following the field upgrade process.
PAGE 300
Severity ERROR SEC-1071 Message timestamp, [SEC-1071], sequence-number,, ERROR, system-name, No new data to apply. Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence.
PAGE 301
SEC-1073 Message timestamp, [SEC-1073], sequence-number,, ERROR, system-name, No FCS policy in list! Probable cause The specific policy type is empty. The security database is corrupted for unknown reasons. Recommended action Run supportFtp as needed to set up automatic FTP transfers and then run the supportSave command and contact your switch service provider. Severity ERROR SEC-1074 Message timestamp, [SEC-1074], sequence-number,, ERROR, system-name, Cannot execute the command on this switch.
PAGE 302
This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state. If a switch is in the error state, the database may not be correctly updated for that specific switch.
PAGE 303
SEC-1078 Message timestamp, [SEC-1078], sequence-number,, ERROR, system-name, No new data to abort. Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent.
PAGE 304
Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state.
PAGE 305
Severity ERROR SEC-1083 Message timestamp, [SEC-1083], sequence-number,, ERROR, system-name, Name already exists. Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence.
PAGE 306
SEC-1085 Message timestamp, [SEC-1085], sequence-number,, ERROR, system-name, Failed to create policy-name. Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent.
PAGE 307
This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state. If a switch is in the error state, the database may not be correctly updated for that specific switch.
PAGE 308
Severity ERROR SEC-1091 Message timestamp, [SEC-1091], sequence-number,, ERROR, system-name, No policy to remove. Probable cause There was a corruption during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database. This is a rare occurrence.
PAGE 309
SEC-1093 Message timestamp, [SEC-1093], sequence-number,, ERROR, system-name, New FCS list must have at least one member in common with current FCS list. Probable cause The new FCS list does not have a common member with the existing FCS list. Recommended action Resubmit the command with at least one member of the new FCS list in common with the current FCS list. Severity ERROR SEC-1094 Message timestamp, [SEC-1094], sequence-number,, ERROR, system-name, Policy member not found.
PAGE 310
This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state. If a switch is in the error state, the database may not be correctly updated for that specific switch.
PAGE 311
SEC-1098 Message timestamp, [SEC-1098], sequence-number,, ERROR, system-name, No active-or-defined FCS list. Probable cause The specified policy could not be found. Recommended action Run supportFtp as needed to set up automatic FTP transfers and then run the supportSave command and contact your switch service provider. Severity ERROR SEC-1099 Message timestamp, [SEC-1099], sequence-number,, ERROR, system-name, Please enable your switch before running secModeEnable.
PAGE 312
Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state.
PAGE 313
Severity ERROR SEC-1104 Message timestamp, [SEC-1104], sequence-number,, ERROR, system-name, Fail to get primary Certificate-or-public-key. Probable cause The switch failed to get either the primary certificate or a primary public key. Recommended action 1. Verify that the primary switch has a valid certificate installed and retry the operation. 2. If a valid certificate is not installed, install a certificate by following the procedure specified in the HP StorageWorks Secure Fabric OS user guide.
PAGE 314
SEC-1106 Message timestamp, [SEC-1106], sequence-number,, ERROR, system-name, Failed to sign message data. Probable cause Some PKI objects on the switch are not in a valid state; a signature operation failed. Recommended action 1. Run the pkiShow command and verify that all PKI objects exist on the switch. 2. If a failure to validate PKI objects occurs, follow the steps for re-creating PKI objects outlined in the HP StorageWorks Secure Fabric OS user guide.
PAGE 315
Probable cause A version reset operation failed either because the switch could not get all the required resources to perform the operation or because it failed to send the message to all switches in the fabric. Recommended action 1. Verify that the security event was planned. If so, run the secFabricShow command to verify that all switches in the fabric are in the ready state. 2. When all switches are in the ready state, retry the operation.
PAGE 316
SEC-1112 Message timestamp, [SEC-1112], sequence-number,, ERROR, system-name, FCS list must be the first entry in the Active Security policies, and the same as the current active FCS list in the switch. Probable cause Either a security policy download was attempted with an active policy that does not have the FCS policy as the first policy or the FCS policy is not the same as the current FCS policy on the switch.
PAGE 317
This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state. If a switch is in the error state, the database may not be correctly updated for that specific switch.
PAGE 318
SEC-1119 Message timestamp, [SEC-1119], sequence-number,, INFO, system-name, Secure mode has been enabled. Probable cause The secure Fabric OS was enabled by the secModeEnable command. Recommended action Verify that the security event was planned. If the security event was planned, no action is required. If the security event was not planned, take appropriate action as defined by your enterprise security policy.
PAGE 319
Recommended action Run the secFabricShow command to verify that all switches in fabric are in the ready state. When all switches are in the ready state, retry the operation. Severity INFO SEC-1123 Message timestamp, [SEC-1123], sequence-number,, INFO, system-name, Security database downloaded by Primary FCS. Probable cause The security database was successfully downloaded from the primary FCS. Recommended action No action is required.
PAGE 320
SEC-1126 Message timestamp, [SEC-1126], sequence-number,, INFO, system-name, Secure mode has been disabled. Probable cause A secure mode disable operation completed successfully. Recommended action Verify that the security event was planned. If the security event was planned, no action is required. If the security event was not planned, take appropriate action as defined by your enterprise security policy.
PAGE 321
Recommended action Verify that the security event was planned. If the security event was planned, no action is required. If the security event was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-1136 Message timestamp, [SEC-1136], sequence-number,, ERROR, system-name, Failed to verify signature data-type, MUA, policy, etc. Probable cause The receiving switch failed to validate the security database from the primary FCS switch.
PAGE 322
Recommended action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state. If a switch is in the error state, the database might not be correctly updated for that switch. Severity ERROR SEC-1138 Message timestamp, [SEC-1138], sequence-number,, INFO, system-name, Security database download received from Primary FCS. Probable cause A non-primary FCS switch received a security database download.
PAGE 323
SEC-1142 Message timestamp, [SEC-1142], sequence-number,, INFO, system-name, Reject new policies. reason-text. Probable cause The new polices are rejected for the reason specified. Recommended action Use proper syntax when entering policy information. Severity INFO SEC-1145 Message timestamp, [SEC-1145], sequence-number,, INFO, system-name, A security admin event has occurred. This message is for information purpose only.
PAGE 324
SEC-1146 Message timestamp, [SEC-1146], sequence-number,, INFO, system-name, PID changed: state. Probable cause The PID format of the switch was changed either to extended-edge PID or from extended-edge PID. If the DCC polices existed, all area ID values either increased or decreased by 16. The values wrap around after 128. If a DCC policy contains an area of 127 before changing to extended-edge PID, then the new area is 15, because of the wraparound. Recommended action No action is required.
PAGE 325
Probable cause Either the defined or the active policy could not be updated. If the policy database is very large, it might not be able to change the area ID because the new policy database exceeds the maximum size. This message can also occur when the switch is short of memory. The status values can be either defined, active, or both. A negative value means that a policy set was failed by the daemon. Recommended action Reduce the size of the policy database.
PAGE 326
SEC-1157 Message timestamp, [SEC-1157], sequence-number,, INFO, system-name, PID Change failed: reason defined-status active-status. Probable cause The provisioning resources for a security policy failed due to low memory or internal error. The status values can be either defined, active, or both. A negative value means that a policy set was failed by the daemon. Recommended action 1. Retry the failed command. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3.
PAGE 327
Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state.
PAGE 328
Severity ERROR SEC-1164 Message timestamp, [SEC-1164], sequence-number,, ERROR, system-name, Lockdown option cannot be applied on a non-FCS switch. Probable cause The attempt to enable security was made on a switch not present in the FCS list. Recommended action Add the switch into the FCS policy list when using the lockdown option to enable security. Severity ERROR SEC-1165 Message timestamp, [SEC-1165], sequence-number,, ERROR, system-name, Low memory, failed to enable security on all switches.
PAGE 329
Recommended action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state. If a switch is in the error state, the database might not be correctly updated for that specific switch. Severity ERROR SEC-1167 Message timestamp, [SEC-1167], sequence-number,, ERROR, system-name, Another FCS failover is in process. Command terminated. Probable cause This failover attempt cannot proceed because another failover is already in progress.
PAGE 330
SEC-1170 Message timestamp, [SEC-1170], sequence-number,, INFO, system-name, This command must be executed on the Primary FCS switch, the first reachable switch in the FCS list. Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence.
PAGE 331
SEC-1172 Message timestamp, [SEC-1172], sequence-number,, ERROR, system-name, Failed to identify role. Probable cause The switch is unable to determine its role (primary FCS or backup FCS) in the secure fabric. Recommended action 1. Verify that all switches in the fabric are in time synchronization with the primary and that no external entity is trying to access the fabric. 2. When verification is complete, retry the operation.
PAGE 332
Recommended action 1. Verify that all switches in the fabric are in time synchronization with the primary and that no external entity is trying to access the fabric. 2. When verification is complete, retry the operation. Severity ERROR SEC-1175 Message timestamp, [SEC-1175], sequence-number,, ERROR, system-name, Failed to install zone data. Probable cause The zone database could not be installed on the switch. Recommended action 1.
PAGE 333
SEC-1180 Message timestamp, [SEC-1180], sequence-number,, INFO, system-name, Added account user-name with role-name authorization. Probable cause The specified new account was created. Recommended action No action is required. Severity INFO SEC-1181 Message timestamp, [SEC-1181], sequence-number,, INFO, system-name, Deleted account user-name Probable cause The specified account was deleted. Recommended action No action is required.
PAGE 334
Severity INFO SEC-1183 Message timestamp, [SEC-1183], sequence-number,, ERROR, system-name, Policy to binary conversion error: Port port-number is out range. Probable cause A security database conversion failed because of an invalid value. Recommended action 1. Retry the command with a valid value. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3. Run the supportSave command and contact your switch service provider.
PAGE 335
Probable cause The switch database was enabled or disabled as the secondary AAA when RADUIS is the primary AAA mechanism. Recommended action No action is required. Severity INFO SEC-1186 Message timestamp, [SEC-1186], sequence-number,, INFO, system-name, action Radius Configuration. Probable cause The RADIUS configuration was enabled or disabled as the primary AAA mechanism. Recommended action No action is required.
PAGE 336
Severity INFO SEC-1188 Message timestamp, [SEC-1188], sequence-number,, INFO, system-name, Security violation: Unauthorized device device-node-name tries to flogin to area port-number of switch switch-wwn. Probable cause A DCC security violation was reported. The specified device attempted to log in using fabric login (FLOGI) to an unauthorized port. The DCC policy correlates specific devices to specific port locations. If the device changes connected port, it is not allowed to log in.
PAGE 337
INFO SEC-1190 Message timestamp, [SEC-1190], sequence-number,, INFO, system-name, Security violation: Unauthorized host with IP address IP-address tries to do SNMP read operation. Probable cause An SNMP security violation was reported. The specified unauthoized host attempted to perform a read SNMP operation. Recommended action 1. Check the RSNMP policy to verify that hosts allowed access to the fabric through SNMP read operations are included in the RSNMP policy. 2.
PAGE 338
SEC-1192 Message timestamp, [SEC-1192], sequence-number,, INFO, system-name, Security violation: Login failure attempt via connection-method. Probable cause A serial or modem login security violation was reported. The wrong password was used while trying to log in through a serial or modem connection; the login failed. Recommended action Use the correct password.
PAGE 339
Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state.
PAGE 340
Severity WARNING SEC-1197 Message timestamp, [SEC-1197], sequence-number,, INFO, system-name, Changed account user-name. Probable cause The specified account changed. Recommended action No action is required. Severity INFO SEC-1198 Message timestamp, [SEC-1198], sequence-number,, INFO, system-name, Security violation: Unauthorized host with IP address IP-address tries to establish API connection. Probable cause An API security violation was reported.
PAGE 341
SEC-1199 Message timestamp, [SEC-1199], sequence-number,, INFO, system-name, Security violation: Unauthorized access to serial port of switch switch-instance. Probable cause A serial connection policy security violation was reported. An attempt was made to access the serial console on the specified switch instance when it was disabled. Recommended action 1. Check to see whether an authorized access attempt is being made on the console. 2.
PAGE 342
SEC-1201 Message timestamp, [SEC-1201], sequence-number,, INFO, system-name, Security violation: MS device device-wwn operates on non-primary FCS switch. Probable cause An MS operation security violation was reported. An MS device operation occurred on a non-primary FCS switch. Recommended action 1. Check the management server policy and verify that the connection is allowed. 2. If the connection is allowed but not specified, enable the connection is MS policy. 3.
PAGE 343
SEC-1250 Message timestamp, [SEC-1250], sequence-number,, WARNING, system-name, DCC enforcement API failed: failed-action err=status, key=data Probable cause An internal error caused the DCC policy enforcement to fail. Recommended action 1. Retry the failed security command. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3. Run the supportSave command and contact your switch service provider.
PAGE 344
Probable cause An internal error caused the DCC policy update to fail in the provision, commit, or cancel phases. Recommended action 1. Retry the failed security command. 2. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 3. Run the supportSave command and contact your switch service provider. Severity ERROR SEC-1300 Message timestamp, [SEC-1300], sequence-number,, INFO, system-name, This switch is in VcEncode mode. Security is not supported.
PAGE 345
SEC-1302 Message timestamp, [SEC-1302], sequence-number,, INFO, system-name, This switch does not have all the required PKI objects correctly installed. Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence.
PAGE 346
Probable cause A corruption occurred during the distribution of the security database. This can occur only when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that an error occurred in the security database. This is a rare occurrence. Recommended action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state.
PAGE 347
2. If a failure to validate PKI objects occurs, follow the steps for re-creating PKI objects outlined in the HP StorageWorks Fabric OS user guide. 3. If PKI objects are valid, verify that an unauthorized switch is not trying to access the fabric. Severity INFO SEC-1307 Message timestamp, [SEC-1307], sequence-number,, INFO, system-name, Got response from Radius server radius-server-identity. Probable cause After some servers timed out, the specified RADIUS server responded to a switch request.
PAGE 348
SEC-3001 Message timestamp, [SEC-3001], sequence-number, AUDIT, INFO, system-name, User: user-name, role: user-role, Event: event-name, status: event-status, Info: security mode state-change:-enabled-or-disabled. Probable cause The security mode of the fabric was either enabled or disabled. Recommended action 1. Verify that the security event was planned. If the security event was planned, no action is required. 2.
PAGE 349
SEC-3003 Message timestamp, [SEC-3003], sequence-number, AUDIT, INFO, system-name, User: user-name, role: user-role, Event: event-name, status: event-status, Info: Create policy-name policy, with member-list entries. Probable cause A new security policy with entries was created. When you use a wildcard (for example, an asterisk) in creating a policy, the audit report displays the wildcard in the Event Info field. Recommended action 1. Verify that the security event was planned.
PAGE 350
SEC-3005 Message timestamp, [SEC-3005], sequence-number, AUDIT, INFO, system-name, User: user-name, role: user-role, Event: event-name, status: event-status, Info: Add members [members-added] to policy policy-name. Probable cause New members were added to a security policy. When you use a wildcard (for example, an asterisk) in adding members to a policy, the audit report displays the wildcard in the Event Info field. Recommended action 1. Verify that the security event was planned.
PAGE 351
SEC-3007 Message timestamp, [SEC-3007], sequence-number, AUDIT, INFO, system-name, User: user-name, role: user-role, Event: event-name, status: event-status, Info: Delete policy deleted-policy-name. Probable cause The user deleted the specified security policy. Recommended action 1. Verify that the security event was planned. If the security event was planned, no action is required. 2. If the security event was not planned, take appropriate action as defined by your enterprise security policy.
PAGE 352
Probable cause The pending security transaction was aborted. Recommended action 1. Verify that the security event was planned. If the security event was planned, no action is required. 2. If the security event was not planned, take appropriate action as defined by your enterprise security policy.
PAGE 353
Severity INFO SEC-3012 Message timestamp, [SEC-3012], sequence-number, AUDIT, INFO, system-name, User: user-name, role: user-role, Event: event-name, status: event-status, Info: Passwd set/reset on domain [domain-ID] for account(s) account-name. Probable cause The specified user reset the password for the specified user accounts. Recommended action 1. Verify that the security event was planned. If the security event was planned, no action is required. 2.
PAGE 354
SEC-3014 Message timestamp, [SEC-3014], sequence-number, AUDIT, INFO, system-name, User: user-name, role: user-role, Event: event-name, status: event-status, Info: event-option server event-data. Probable cause The specified user changed the RADIUS configuration. Recommended action 1. Verify that the security event was planned. If the security event was planned, no action is required. 2. If the security event was not planned, take appropriate action as defined by your enterprise security policy.
PAGE 355
Probable cause The specified user changed the RADIUS configuration. Recommended action 1. Verify that the security event was planned. If the security event was planned, no action is required. 2. If the security event was not planned, take appropriate action as defined by your enterprise security policy.
PAGE 356
Recommended action Verify that the IP address for the Ethernet and Fibre Channel interface is set correctly. If the specified reason is an initialization failure, the switch requires a reboot. Severity ERROR SNMP-1002 Message timestamp, [SNMP-1002], sequence-number,, ERROR, system-name, SNMP error-details initialization failed. Probable cause The initialization of the SNMP service failed; you cannot query the switch through SNMP. Recommended action Reboot or power cycle the switch.
PAGE 357
SNMP-1004 Message timestamp, [SNMP-1004], sequence-number,, ERROR, system-name, Incorrect SNMP configuration. Probable cause The SNMP configuration is incorrect and the SNMP service does not work correctly. Recommended action Try changing the SNMP configuration back to the default. Severity ERROR SupportSave command error messages SS-1000 Message timestamp, [SS-1000], sequence-number,, INFO, system-name, supportSave has ftp'ed support information to the host with IP address host-IP.
PAGE 358
Recommended action 1. Check the FTP server and settings. 2. Run the supportFtp command to set the FTP parameters. 3. After the FTP problem is corrected, rerun the supportSave command. Severity WARNING Software upgrade library error messages SULB-1001 Message timestamp, [SULB-1001], sequence-number,, WARNING, system-name, Firmwaredownload command has started. Probable cause The firmwareDownload command started.
PAGE 359
Severity INFO SULB-1003 Message timestamp, [SULB-1003], sequence-number,, INFO, system-name, Firmwarecommit has started. Probable cause The FirmwareCommit command started to update the secondary partition. Recommended action No action is required. Run the firmwareDownloadStatus command for more information. Severity INFO SULB-1005 Message timestamp, [SULB-1005], sequence-number,, INFO, system-name, Current Active CP is preparing to failover.
PAGE 360
Probable cause The previous standby became the active CP and is running the new firmware version. Recommended action No action is required. The firmwareDownload command is progressing as expected. Run the firmwareDownloadStatus command for more information. Severity INFO SULB-1007 Message timestamp, [SULB-1007], sequence-number,, INFO, system-name, Standby CP reboots. Probable cause The standby CP reboots. Recommended action No action is required.
PAGE 361
SULB-1009 Message timestamp, [SULB-1009], sequence-number,, INFO, system-name, Firmwaredownload command failed (0xfirmwaredownload-error-code). Probable cause The firmware download failed. The additional error code provides debugging information. The firmwareDownload error code contains two bytes.
PAGE 362
Table 6 Upgrade messages and code values (continued) Upgrade message Code Firmware directory structure is not compatible. 0x1b Failed to load kernel image. 0x1c Bootenv OSLoader is inconsistent. 0x1d Firmwaredownload failed because new image has not been committed. 0x1e Firmwarerestore failed. 0x1f Both images are mounted to the same device. 0x20 Error in removing packages. 0x21 Firmwaredownload is already in progress. 0x22 Firmwaredownload timeout.
PAGE 363
Table 6 Upgrade messages and code values (continued) Upgrade message Code Firmwaredownload failed due to Standby CP timeout. 0x50 Unable to check firmware version due to Standby CP timeout. 0x51 Firmwaredownload failed due to Standby CP timeout. 0x52 Firmwaredownload failed due to Standby CP timeout. 0x53 Standby CP failed to reboot and was not responding. 0x54 Firmwarecommit failed due to Standby CP timeout. 0x55 Unable to check firmware version due to Standby CP timeout.
PAGE 364
Table 6 Upgrade messages and code values (continued) Upgrade message Code Local CP is restoring its secondary partition. 0x6a Unable to restore the secondary partition. Please use firmwaredownloadstats and firmwareshow to see firmware status. 0x6b Firmwaredownload has started on Standby CP. It may take up to 10 minutes. 0x6c Firmwaredownload has completed successfully on Standby CP. 0x6d Standby CP reboots. 0x6e Standby CP failed to boo up. 0x6f Standby CP booted up with new firmware.
PAGE 365
Table 6 Upgrade messages and code values (continued) Upgrade message Code The original firmware has been restored successfully on Standby CP. 0x7e Unable to restore the original firmware on Standby CP. 0x7f Standby CP reboots. 0x80 Standby CP failed to reboot. 0x81 Standby CP booted up with new firmware. 0x82 Standby CP failed to boot up with new firmware. 0x83 An unexpected reboot occurred during firmwareDownload. The command is aborted. 0x84 Standby CP was not responding.
PAGE 366
Table 6 Upgrade messages and code values (continued) Upgrade message Code Firmwaredownload has completed successfully. 0x91 Firmwarecommit has completed successfully. 0x92 Firmwarecommit has started to restore the secondary partition. 0x93 Firmwarecommit failed. 0x94 The secondary partition has been restored successfully. 0x95 Table 7 lists upgrade states and their associated codes.
PAGE 367
Table 7 Upgrade state and code values (continued) Upgrade state Code SUS_PEER_FWC_BEGIN 0x32 SUS_PEER_FS_CHECK1 0x33 SUS_FINISH 0x34 SUS_COMMIT 0x35 Recommended action Run the firmwareDownload status command for more information. Refer to the HP StorageWorks Fabric OS 4.x procedures user guide for troubleshooting information. Severity INFO SULB-1010 Message timestamp, [SULB-1010], sequence-number,, INFO, system-name, Firmwarecommit failed (status=0xfirmwarecommit-error-code).
PAGE 368
Probable cause The switch was enabled before it was ready. Recommended action 1. If the message persists, run supportFtp as needed to set up automatic FTP transfers. 2. Run the supportSave command and contact your switch service provider. Severity ERROR SWCH-1002 Message timestamp, [SWCH-1002], sequence-number,, INFO, system-name, Security violation: Unauthorized device wwn-name-of-device tries to flogin to port port-number Probable cause The device is not present in the authorized profile list.
PAGE 369
Severity ERROR SWCH-1004 Message timestamp, [SWCH-1004], sequence-number,, ERROR, system-name, Blade attach failed during recovery, disabling slot = slot-number Probable cause A blade failed during failover or recovery. Recommended action On a Core Switch 2/64 or SAN Director 2/128 switch, first run the slotPowerOff commadn and then run the slotPowerOn command. On a SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch 2/32, or SAN Switch 4/32 switch, reboot or power cycle the switch.
PAGE 370
System controller error messages SYSC-1001 Message timestamp, [SYSC-1001], sequence-number,, CRITICAL, system-name, Failed to runname-of-program-that-could-not-be-run-(string):system-internal-error-m essage-(string) Probable cause During the boot sequence one of the programs would not run on the system. Recommended action 1. If the message is reported during a reboot after new firmware has been loaded, try reloading the firmware using the firmwareDownload command. 2.
PAGE 371
General system error messages SYSM-1001 Message timestamp, [SYSM-1001], sequence-number,, CRITICAL, system-name, No memory Probable cause The switch ran out of system memory. Recommended action 1. Run the memShow command to view the switch memory usage. 2. Reboot or power cycle the switch. Severity CRITICAL SYSM-1002 Message timestamp, [SYSM-1002], sequence-number,, INFO, system-name, number, Switch: switch-number Probable cause A user executed either the switchShutdown or switchReboot command.
PAGE 372
Probable cause The user executed the switchStart or switchReboot command. All services are brought back up after a temporary shutdown of that logical switch. Recommended action No action is required if the switchStart or switchReboot command was executed intentionally. Because reinitializing a switch is a disruptive operation and can stop I/O traffic, you may have to stop and restart the traffic during this process.
PAGE 373
• MANUAL is generated by the tracedump -n command • TRIGGER when triggered by a specific Message ID generated by critical RASLog message or RASLog message trigger setup using the traceTrig command Recommended action 1. Run the supportFtp and traceFtp commands as needed to set up automatic FTP transfers. 2. Run the supportSave command and contact your switch service provider.
PAGE 374
Severity ERROR TRCE-1004 Message timestamp, [TRCE-1004], sequence-number,, WARNING, system-name, Trace dump optional-slot-indicating-on-which-slot-the-dump-occurs was not transferred because trace auto-FTP disabled. Probable cause Trace dump files was created on the switch or the indicated slot, but was not automatically transferred from the switch because auto-FTP is disabled. Recommended action 1. Run the supportFtp command as needed to set up automatic FTP transfers. 2.
PAGE 375
TRCE-1006 Message timestamp, [TRCE-1006], sequence-number,, INFO, system-name, FTP Connectivity Test succeeded to FTP site 'FTP-target-configured-by-users.' Probable cause A connectivity test to the FTP host succeeded. Recommended action No action is required. Severity INFO TRCE-1007 Message timestamp, [TRCE-1007], sequence-number,, ERROR, system-name, Notification of this CP has failed. Parameters temporarily out of synch with other CP.
PAGE 376
Recommended action 1. Reboot the CP (dual-CP system) or restart the switch. 2. Run the traceFtp command to set up for automatic FTP transfers. 3. Run the supportFtp command as needed to set up automatic FTP transfers. 4. Run the supportSave command and contact your switch service provider. Severity CRITICAL TRCE-100 Message timestamp, [TRCE-1009], sequence-number,, ERROR, system-name, Unable to alert active CP that a dump has occurred.
PAGE 377
Severity ERROR TRCE-1011 Message timestamp, [TRCE-1011], sequence-number,, INFO, system-name, Trace dump manually transferred to target 'optional-string-to-indicate-which-slot-the-dump-is-ftped-out.': result. Probable cause A manual transfer of trace dump files occurred. Recommended action No action is required. Severity INFO Track change feature error messages TRCK-1001 Message timestamp, [TRCK-1001], sequence-number,, INFO, system-name, Successful login by user user.
PAGE 378
TRCK-1002 Message timestamp, [TRCK-1002], sequence-number,, INFO, system-name, Unsuccessful login by user user. Probable cause The track change feature recorded a failed login. This occurs if the user name or password is entered incorrectly. Normally, this message indicates a typing error by an authorized user. If this message occurs repeatedly, it may indicate an unauthorized user trying to gain access to a switch.
PAGE 379
The track change feature records any change to the configuration file in nonvolatile memory, including a configDownload. This message is not generated for a configUpload. All configuration changes occur through the PDM server, so the PDMIPC is the only task possible. Recommended action No action is required. Run the configShow command to view the configuration file.
PAGE 380
Time service error messages TS-1001 Message timestamp, [TS-1001], sequence-number,, WARNING, system-name, NTP Query failed: error-code Probable cause A Network Time Protocol (NTP) query to the configured external clock server failed. Local clock time on the principal or primary FCS switch is used for fabric synchronization. This may be logged during temporary operational issues, such as IP network connection issues to the external clock server. If it does not recur, it can be ignored.
PAGE 381
3. If the principal or primary FCS does not support the feature, either choose a different switch for the role or reset the clock server to LOCL. Severity WARNING TS-1006 Message timestamp, [TS-1006], sequence-number,, INFO, system-name, message Probable cause A time service event is occurring or failed. The message can be one of the following: • Init failed. Time Service exiting Probable cause: Initialization error or Time Server exits.
PAGE 382
Recommended action No action is required. Severity INFO UCST-1007 Message timestamp, [UCST-1007], sequence-number,, CRITICAL, system-name, Inconsistent route detected: Port = port-number, should be port-number Probable cause The switch detected an inconsistency in the routing database between the routing protocol and the hardware configuration. The first port number displayed is what the hardware has configured and the second port number displayed is what the protocol is using. Recommended action 1.
PAGE 383
User space software watchdog error messages USWD-1006 Message timestamp, [USWD-1006], sequence-number,, WARNING, system-name, uSWD: warning-message Probable cause A warning state exists in the system. This is an internal-use-only message. Recommended action No action is required. Severity WARNING Web Tools error messages WEBD-1001 Message timestamp, [WEBD-1001], sequence-number,, WARNING, system-name, Missing or Invalid Certificate file -- HTTPS is configured to be enabled but could not be started.
PAGE 384
WEBD-1002 Message timestamp, [WEBD-1002], sequence-number,, WARNING, system-name, Missing or Invalid Key file -- HTTPS is configured to be enabled but could not be started. Probable cause The SSL key file is either invalid or absent. Recommended action 1. Run the configure command to disable HTTPS. For more information on the configure command, refer to the HP StorageWorks Fabric OS 4.x command reference guide. 2. Install a valid key file and enable HTTPS again.
PAGE 385
Recommended action No action is required. Severity INFO WEBD-1005 Message timestamp, [WEBD-1005], sequence-number,, WARNING, system-name, HTTP server will be restarted for logfile truncation Probable cause The size of the HTTP logfile exceeds the maximum limit. Recommended action No action is required.
PAGE 386
Probable cause The IP address of the switch changed and the HTTP server was restarted. Recommended action No action is required. Severity INFO Zone library module error messages ZOLB-1001 Message timestamp, [ZOLB-1001], sequence-number,, ERROR, system-name, ZONELIB error-message Probable cause An internal timeout occurred on the IPC between the name server (NS) and the zoning modules. This usually indicates that the system was busy. Recommended action 1.
PAGE 387
The frame filter logic reported a failure when creating or adding zone groups during port login (PLOGI) trap processing. This message usually indicates problems when adding CAM entries before the filter setup. Recommended action 1. If the message persists, run the supportFtp command as needed to set up automatic FTP transfers. 2. Run the supportSave command and contact your switch service provider.
PAGE 388
Recommended action No action is required. Severity INFO ZONE-1005 Message timestamp, [ZONE-1005], sequence-number,, INFO, system-name, HARD & SOFT zones(zone-name, zone-name) definitions overlap. Probable cause A port is zoned with mixed devices (WWN and domain, portarea).
PAGE 389
Severity WARNING ZONE-1007 Message timestamp, [ZONE-1007], sequence-number,, INFO, system-name, Ioctl(function) in (error-message) at port (port-number) returns code (error-string) and reason string (reason-string) Probable cause Frame filter logic reported a failure during one of the IOCTL calls. The IOCTL call from which the failure is reported is listed as part of the error message. This is usually a programming error when adding CAM entries before the filter setup.
PAGE 390
ZONE-1010 Message timestamp, [ZONE-1010], sequence-number,, WARNING, system-name, WARNING Duplicate entries in zone(zone-name) specification. Probable cause Duplicate entries were detected in a zone object. A zone object member is specified twice in a given zone object. This message occurs only when enabling a zone configuration. Recommended action Check the members of the zone and delete the duplicate member.
PAGE 391
Severity WARNING ZONE-1014 Message timestamp, [ZONE-1014], sequence-number,, ERROR, system-name, Missing required license - license-name. Probable cause The required zoning license is missing. Recommended action Install the zoning license using the licenseAdd command. Refer to your switch supplier to obtain a zoning license if you do not have one.
PAGE 392
Probable cause The Fabric Assist (FA) zoning configuration has more than one initiator. The probable cause is incorrect entries in the FA zoning configuration. Recommended action Edit the zone database to ensure that only one initiator is set for each FA zone configuration.
PAGE 393
Probable cause The reliable commit service (RCS) had a transmit error. RCS is a protocol used to transmit changes to the configuration database within a fabric. Recommended action 1. Often this message indicates a transitory problem. Wait a few minutes and retry the command. 2. Make sure that your changes to the zone database are not overwriting the work of another admin. 3. Run the cfgTransShow command to determine whether any outstanding transactions are running on the local switches. 4.
PAGE 394
2. Run the supportSave command and contact your switch service provider. Severity INFO ZONE-1024 Message timestamp, [ZONE-1024], sequence-number,, INFO, system-name, information-message Probable cause The cfgSave command ran successfully. Recommended action No action is required.
PAGE 395
Probable cause The zoning transaction was aborted due to a variety of potential errors. The error-reason values are: • Zone Merge Received: The fabric is in the process of merging two zone databases. • Zone Config update Received: The fabric is in the process of updating the zone database. • Bad Zone Config: The new config is not viable. • Zoning Operation failed: A zoning operation failed. • Shell exited: The command shell exited. • Unknown: An error was received for an unknown reason.
PAGE 396
ZONE-1029 Message timestamp, [ZONE-1029], sequence-number,, WARNING, system-name, Restoring zone cfg from flash failed - bad config saved to config-file-name [return-code] Probable cause The zone configuration restored from the flash was faulty. Recommended action 1. This error saves the bad zone configuration in the zoned core file directory. Run the saveCore command to save the file. 2. If the message persists, run the supportFtp command as needed to set up automatic FTP transfers. 3.
PAGE 397
Glossary AL_PA Arbitrated-loop physical address. A unique 8-bit value assigned during loop initialization to a port in an arbitrated loop. Alternately, arbitrated-loop parameters. alias A logical grouping of elements in a fabric. An alias is a collection of port numbers and connected devices that simplify the entry of port numbers and WWNs during zone creation. ARB Arbitrative primitive signal. Applies only to an arbitrated-loop topology.
PAGE 398
BB_Credit Buffer-to-buffer credit. The number of frames that can be transmitted to a directly connected recipient or within an arbitrated loop. Determined by the number of receive buffers available. See also buffer-to-buffer flow control, EE_Credit. beacon A tool in which all of the port LEDs on a switch are set to flash from one side of the switch to the other, to enable identification of an individual switch in a large fabric. A switch can be set to beacon by a CLI command or through Advanced Web Tools.
PAGE 399
Class F service The class of frame-switching service for a direct connection between two switches, allowing communication of control traffic between the E_Ports. Includes acknowledgement of data delivery or nondelivery. class of service A specified set of delivery characteristics and attributes for frame delivery. CLI Command line interface. An interface that depends entirely on the use of commands, such as through telnet or SNMP, and does not involve a GUI. See also SNMP.
PAGE 400
DH-CHAP Diffie-Hellman Challenge-Handshake Authentication Protocol. An implementation of CHAP using Diffie-Hellman encryption. See also CHAP. digital certificate An electronic document issued by a certificate authority (CA) to an entity, containing the public key and identity of the entity. Entities in a secure fabric are authenticated based on these certificates. See also authentication, public key, PKI, PKI certification utility. director An HP StorageWorks Core Switch 2/64, or SAN Director 2/128.
PAGE 401
exchange The highest-level Fibre Channel mechanism used for communication between N_Ports. Composed of one or more related sequences, it can work in either one or both directions. fabric A collection of Fibre Channel switches and devices, such as hosts and storage. Also referred to as a switched fabric. See also cascade, SAN, topology. Fabric Manager An optionally licensed software feature. Fabric Manager is a GUI that allows for fabric-wide administration and management.
PAGE 402
FFFFF5 Well-known Fibre Channel address for a Class 6 multicast server. FFFFF6 Well-known Fibre Channel address for a clock synchronization server. FFFFF7 Well-known Fibre Channel address for a security key distribution server. FFFFF8 Well-known Fibre Channel address for an alias server. FFFFF9 Well-known Fibre Channel address for a QoS facilitator. FFFFFA Well-known Fibre Channel address for a management server. FFFFFB Well-known Fibre Channel address for a time server.
PAGE 403
firmware The basic operating system provided with the hardware. 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. See also Fx_Port. flash Programmable nonvolatile random access memory (NVRAM); memory that retains its contents without power. FLOGI Fabric login. The process by which an N_Port determines whether a fabric is present and if so, exchanges service parameters with it.
PAGE 404
G_Port Generic port. A port that can operate as either an E_Port or an F_Port. A port is defined as a G_Port when it is not yet connected or has not yet assumed a specific function in the fabric. gateway Hardware that connects incompatible networks by providing translation for both hardware and software. For example, an ATM gateway can connect a Fibre Channel link to an ATM connection. GBIC Gigabit interface converter.
PAGE 405
hot swappable A component that can be replaced under power. HTTP Hypertext Transfer Protocol. The standard TCP/IP transfer protocol used on the World Wide Web. hub A Fibre Channel wiring concentrator that collapses a loop topology into a physical star topology. Nodes are automatically added to the loop when active and removed when inactive. ICT Intracircuit test. ID_ID Insistent domain ID. A parameter of the configure command in the HP StorageWorks Fabric OS.
PAGE 406
key A string of data (usually a numeric value) shared between two entities and used to control a cryptographic algorithm. Usually selected from a large pool of possible keys to make unauthorized identification of the key difficult. See also key pair. key pair In public key cryptography, a pair of keys consisting of an entity's public and private key. The public key can be publicized, but the private key must be kept secret. L_Port Loop port.
PAGE 407
MIB Management Information Base. An SNMP structure that helps with device management, providing configuration and device information. MS Management Server. The Management Server allows a SAN management application to retrieve information and administer the fabric and interconnected elements, such as switches, servers, and storage devices. The MS is located at the Fibre Channel well-known address FFFFFAh. MTBF Mean time between failures. An expression of time, indicating the longevity of a device.
PAGE 408
NS Name Server. The service provided by a fabric switch that stores names, addresses, and attributes related to Fibre Channel objects. Can cache information for up to 15 minutes. Also known as Simple Name Server or as a directory service. See also Simple Name Server (SNS). Nx_Port A node port that can operate as either an N_Port or NL_Port. oversubscription A situation in which more nodes could potentially contend for a resource than the resource could simultaneously support (typically an ISL).
PAGE 409
PLOGI Port login. The port-to-port login process by which initiators establish sessions with targets. See also FLOGI. port In an HP StorageWorks switch environment, an SFP or GBIC receptacle on a switch to which an optic cable for another device is attached. port address In Fibre Channel technology, the port address is defined in hexadecimal. In the HP StorageWorks Fabric OS, a port address can be defined by a domain and port number combination or by area number.
PAGE 410
pstate Port State Machine. public device A device that supports arbitrated-loop protocol, can interpret 8-bit addresses, and can log in to the fabric. public key The public half of a key pair. See also key, key pair. queue A mechanism for each AL_PA address that allows for the collection of frames prior to sending them to the loop. QuickLoop An HP StorageWorks software product that allows multiple ports on a switch to create a logical loop.
PAGE 411
RSCN Registered state change notification. A switch function that allows notification of fabric changes to be sent from the switch to specified nodes. The fabric controller issues RSCN requests to N_Ports and NL_Ports, but only if they have registered to be notified of state changes in other N_Ports and NL_Ports. This registration is performed through the State Change Registration (SCR) Extended Link Service.
PAGE 412
security policy Rules that determine how security is implemented in a fabric. Security policies can be customized through HP StorageWorks Secure Fabric OS or HP StorageWorks Fabric Manager. server A computer that processes end-user applications or requests. SES SCSI Enclosure Services. A subset of the SCSI protocol that monitors temperature, power, and fan status for enclosed devices. SFP Small-form-factor pluggable. A transceiver used on 2 GBps switches that replaces the GBIC.
PAGE 413
striping A RAID technique for writing a file to multiple disks on a block-by-block basis, with or without parity. See also RAID. switch A fabric device that provides bandwidth and high-speed routing of data via link-level addressing. switch name The arbitrary name assigned to a switch. switch port A port on a switch. Switch ports can be E_Ports, F_Ports, or FL_Ports. syslog Syslog daemon, that is used to forward error messages. target A storage device on a Fibre Channel network. TC Track changes.
PAGE 414
transceiver A device that converts one form of signaling to another for transmission and reception; in fiber optics, optical to electrical. translate domain See xlate domain. Translative Mode A mode in which private devices can communicate with public devices across the fabric. transmission character A 10-bit character encoded according to the rules of the 8b/10b algorithm. transmission word A group of four transmission characters.
PAGE 415
well-known address With regard to Fibre Channel technology, a logical address defined by Fibre Channel standards as assigned to a specific function and stored on the switch. workstation A computer used to access and manage the fabric. Also called a management station or host. WWN World Wide Name. An identifier that is unique worldwide. Each entity in a fabric has a separate WWN. xlate domain Translate domain. A router virtual domain that represents an entire fabric.
PAGE 416
Glossary
PAGE 417
Index A BLL-1000 69 audit field 30 AUTH-1001 47 AUTH-1002 47 AUTH-1003 48 AUTH-1004 48 AUTH-1005 48 AUTH-1006 49 AUTH-1007 49 AUTH-1008 50 AUTH-1010 50 AUTH-1011 50 AUTH-1012 51 AUTH-1013 51 AUTH-1014 52 AUTH-1017 52 AUTH-1018 53 AUTH-1020 53 AUTH-1022 54 AUTH-1023 54 AUTH-1025 55 AUTH-1027 55 AUTH-1028 56 AUTH-1029 56 AUTH-1030 57 AUTH-1031 57 AUTH-1032 58 AUTH-1033 58 AUTH-1034 59 AUTH-1035 59 AUTH-1036 60 AUTH-1037 60 AUTH-1038 61 authorized reseller, HP 21 B BL-1001 BL-1002 BL-1003 BL-1004 BL-1006 BL
PAGE 418
EM-1050 90 EM-1051 91 EM-1052 91 EM-1053 92 EM-1055 93 EM-1056 93 EVMD-1001 94 example system message 34 F FABR-1001 94 FABR-1002 95 FABR-1003 95 FABR-1004 96 FABR-1005 96 FABR-1006 97 FABR-1007 97 FABR-1008 98 FABR-1009 98 FABR-1010 99 FABR-1011 99 FABR-1012 99 FABR-1013 100 FABR-1014 100 FABR-1015 101 FABR-1016 101 FABR-1017 101 FABR-1018 101 FABR-1019 102 FABR-1020 102 FABR-1021 103 FABR-1022 103 FABR-1023 103 FABR-1024 104 FABR-1029 104 FABS-1001 105 FABS-1002 105 FABS-1004 106 FABS-1005 106 FABS-1006
PAGE 419
FW-1130 FW-1131 FW-1132 FW-1133 FW-1134 FW-1135 FW-1136 FW-1137 FW-1138 FW-1139 FW-1140 FW-1141 FW-1142 FW-1143 FW-1144 FW-1160 FW-1161 FW-1162 FW-1163 FW-1164 FW-1165 FW-1166 FW-1167 FW-1168 FW-1169 FW-1170 FW-1171 FW-1172 FW-1173 FW-1174 FW-1175 FW-1176 FW-1177 FW-1178 FW-1179 FW-1180 FW-1181 FW-1182 FW-1183 FW-1184 FW-1185 FW-1186 FW-1187 FW-1188 FW-1189 FW-1190 FW-1191 FW-1192 FW-1193 FW-1194 FW-1195 FW-1216 FW-1217 FW-1218 FW-1219 FW-1240 FW-1241 FW-1242 FW-1243 141 142 142 142 143 143 144 144 144 145
PAGE 420
FW-1343 FW-1344 FW-1345 FW-1346 FW-1347 FW-1348 FW-1349 FW-1350 FW-1351 FW-1352 FW-1353 FW-1354 FW-1355 FW-1356 FW-1357 FW-1358 FW-1359 FW-1360 FW-1361 FW-1362 FW-1363 FW-1364 FW-1365 FW-1366 FW-1367 FW-1368 FW-1369 FW-1370 FW-1371 FW-1372 FW-1373 FW-1374 FW-1375 FW-1376 FW-1377 FW-1378 FW-1379 FW-1400 FW-1401 FW-1402 FW-1403 FW-1424 FW-1425 FW-1426 FW-1427 FW-1428 FW-1429 FW-1430 FW-1431 FW-1432 FW-1433 FW-1434 FW-1435 FW-1436 FW-1437 FW-1438 FW-1439 FW-1440 FW-1441 420 Index 193 193 194 194 195 195 196 1
PAGE 421
authorized reseller 21 storage web site 21 technical support 21 HTTP-1001 242 K KSWD-1003 243 KTRC-1001 243 KTRC-1002 243 KTRC-1003 244 KTRC-1004 244 L LOG-1000 245 LOG-1001 245 LOG-1002 245 looking up a system message 37 LSDB-1001 246 LSDB-1002 246 LSDB-1003 247 LSDB-1004 247 M message severity levels 29 MPTH-1001 248 MPTH-1002 248 MPTH-1003 248 MQ-1004 249 MS-1001 250 MS-1002 250 MS-1003 251 MS-1004 252 MS-1005 252 MS-1006 253 MS-1007 253 MS-1008 254 MS-1021 254 N NBFS-1001 255 NBFS-1002 255 NBFS-1003
PAGE 422
SEC-1016 284 SEC-1022 284 SEC-1024 285 SEC-1025 285 SEC-1026 285 SEC-1028 286 SEC-1029 286 SEC-1030 287 SEC-1031 287 SEC-1032 288 SEC-1033 288 SEC-1034 288 SEC-1035 289 SEC-1036 289 SEC-1037 290 SEC-1038 290 SEC-1040 291 SEC-1041 291 SEC-1042 291 SEC-1043 292 SEC-1044 292 SEC-1045 293 SEC-1046 293 SEC-1049 293 SEC-1050 294 SEC-1051 294 SEC-1052 295 SEC-1053 295 SEC-1054 296 SEC-1055 296 SEC-1056 297 SEC-1057 297 SEC-1059 297 SEC-1062 298 SEC-1063 298 SEC-1064 299 SEC-1065 299 SEC-1069 299 SEC-1071 300 SEC-1
PAGE 423
SEC-1181 333 SEC-1182 333 SEC-1183 334 SEC-1184 334 SEC-1185 334 SEC-1186 335 SEC-1187 335 SEC-1188 336 SEC-1189 336 SEC-1190 337 SEC-1191 337 SEC-1192 338 SEC-1193 338 SEC-1194 338 SEC-1195 339 SEC-1196 339 SEC-1197 340 SEC-1198 340 SEC-1199 341 SEC-1200 341 SEC-1201 342 SEC-1202 342 SEC-1250 343 SEC-1251 343 SEC-1253 343 SEC-1300 344 SEC-1301 344 SEC-1302 345 SEC-1303 345 SEC-1304 345 SEC-1305 346 SEC-1306 346 SEC-1307 347 SEC-1308 347 SEC-3001 348 SEC-3002 348 SEC-3003 349 SEC-3004 349 SEC-3005 350 SEC-3
PAGE 424
V view or configure the system message logs 32 viewing system messages from Advanced Web Tools 35 viewing the system messages with page breaks 36 W WEBD-1001 383 WEBD-1002 384 WEBD-1003 384 WEBD-1004 384 WEBD-1005 385 WEBD-1006 385 WEBD-1007 385 Z ZOLB-1001 386 ZONE-1002 386 ZONE-1003 387 ZONE-1004 387 ZONE-1005 388 ZONE-1006 388 ZONE-1007 389 ZONE-1008 389 ZONE-1010 390 ZONE-1012 390 ZONE-1013 390 ZONE-1014 391 ZONE-1015 391 ZONE-1017 391 ZONE-1018 392 ZONE-1019 392 ZONE-1022 393 ZONE-1023 393 ZONE-1024