HPStorageWorks Fabric OS 5.
Legalandnoticeinformation ©Copyright 2005 Hewlett-Packard Development Company, L.P. ©Copyright2005BrocadeCommunicationsSystems,Incorporated. Hewlett-PackardCompanymakesnowarrantyofanykindwithregardtothismaterial,including,butnotlimitedto,theimpliedwarrantiesofmerchantabilityandfit nessforaparticularpurpose.Hewlett-Packardshallnotbeliableforerrorscontainedhereinorforincidentalorconsequentialdamagesinconnectionwiththefurnis hing,performance,oruseofthismaterial.
Contents About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AUTH-1006 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . .
AUTH-1022 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AUTH-1023 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AUTH-1036 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BL-1010 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CER-1001 error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CER-1001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . .
EM-1010 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EM-1011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EM-1031 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . .
Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EM-1048 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FABS error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FABR-1001 . . . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FABR-1012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . .
Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FABR-1024 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FABS-1011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FICU-1002. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . .
FICU-1004. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FSPF error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FSPF-1001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FSSM errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FSSM-1002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1010 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . .
FW-1041. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1042. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1113 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . .
Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1125. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1137 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1168. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . .
FW-1179 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1180 . . . . . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1191. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1192. . . . . . . . .
Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1243 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1275. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1307 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . .
FW-1318. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1319. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1330 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . .
Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1342. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1354 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1366. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . .
FW-1377 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1378 . . . . . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1429. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1430. . . . . . . . .
Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FW-1441 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HIL-1102 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HIL-1103 . . . . . . .
Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HIL-1206 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HIL-1401 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
KTRC-1002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MFIC-1003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS-1008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . .
Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDM-1003. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDM-1017 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PS-1001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . .
Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RCS-1003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RPCD-1007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1033 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . .
SEC-1045 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1046 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1062 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . .
Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1078 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1091 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . .
SEC-1118 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1119 . . . . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1139 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1142 . . . . . . . .
Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1163 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1176 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1191 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . .
SEC-1202 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-1308 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . .
Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SEC-3011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . .
SS-1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SWCH-1002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRCE Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRCE-1001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRCK-1002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UPTH Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UPTH-1001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ZONE-1003. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . .
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ZONE-1018 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . .
ZONE-1032. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ZONE-1033. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ZONE-3003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Severity . . . . . . . . . . . .
5 6 Upgrade messages and code values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Upgrade state and code value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Fabric OS 5.
About this guide This installation guide provides information about: • Understanding system error messages • Troubleshooting system error messages • Switch diagnostics Intended audience This guide is intended for: • system administrators responsible for setting up HP StorageWorks Fibre Channel Storage Area Network (SAN) switches • technicians responsible for maintaining the Fabric Operating System (OS) Related documentation Documentation, including white papers and best practices documents, is available o
Document conventions and symbols Table 1 Document conventions Convention Element Medium blue text: Figure 1 Cross-reference links and e-mail addresses Medium blue, underlined text (http://www.hp.
HP technical support Telephone numbers for worldwide technical support are listed on the HP support web site: http://www.hp.com/support/. Collect the following information before calling: • Technical support registration number (if applicable) • Product serial numbers • Product model names and numbers • Applicable error messages • Operating system type and revision level • Detailed, specific questions For continuous quality improvement, calls may be recorded or monitored.
1 Introduction to System Messages This guide supports Fabric OS 5.x and contains system messages that you can use to diagnose and fix problems with the switch or fabric. The messages are organized alphabetically by module name. A module is a subsystem in the Fabric OS. Each module generates a set of numbered messages. For each message, this book provides message text, probable cause, recommended action, and severity level.
• System console, page 84 System message log (RASLog) The Fabric OS maintains an internal system message log of all messages. For Fabric OS 5.x, this log is saved as a RASLog. Features of the system message log include the following: • The system message log by default saves all messages to nonvolatile storage. • The system message log can save a maximum of 1024 messages in RAM. • The system message log is implemented as a circular buffer.
• cfgTransAbort • zoneObjectCopy • zoneObjectExpunge • zoneObjectRename Dual-CP systems For the Core Switch 2/64, SAN Director 2/128, and 4/256 SAN Director, each CP has a unique error log, depending on which CP was active when that message was reported. To fully understand message logging on these switches, 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.
Run 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. Trace dumps The Fabric OS produces trace dumps when problems are encountered within Fabric OS modules. You can initiate the sending of trace dump files to support personnel using the supportSave or traceFtp command. The Fabric OS trace dumps files are intended for support personnel use only.
Table 2 Commands used to view or configure the system logs (continued) Command Description portLogEventShow Displays which port log events are currently being reported. portLoginShow Displays port logins. portLogPdisc Sets or clear the debug pdisc_flag. portLogReset Enables the port log facility. portLogResize Resizes the port log to the specified number of entries. portLogShow Displays the port log, with page breaks.
The fields in the error message are described in table below. Table 3 Error message field description Example Variable Name Description 2004/07/22-10:12:3 Date and Time Stamp 3 The system time (UTC) when the message was generated on the switch. The RASLog subsystem will support an internationalized timestamp format base on the “LOCAL” setting. [EM-1031] Message Module and Message Number Displays the message module and number.
Table 3 Error message field description (continued) Example Variable Name Description switchname Switch name or chassis name, depending on the action; for example, HA messages typically show the chassis name and login failures show the logical switch name. This field displays the defined switch name or the chassis name of the switch. This value is truncated if it is over 16 characters in length.
Viewing the system messages with page breaks This procedure is valid for HP StorageWorks Fabric OS 5.x switches. To display the system message log, with page breaks: 1. Log in to the switch as admin. 2. At the command line, enter the errShow command: switch:admin> errShow Version: 5.0.
Gathering information Common steps and questions to ask yourself when troubleshooting a system message are as follows: 1. What is the current Fabric OS level? 2. What is the switch hardware version? 3. Is the switch operational? 4. Assess impact and urgency: • Is the switch down? • Is it a standalone switch? • How large is the fabric? • Is the fabric redundant? 5. Run the errDump command on each logical switch. 6.
Table 4 System module descriptions (continued) System module Description EM The environmental monitor (EM) manages and monitors the various FRUs (field replaceable units), including the port cards, CP blades, blower assemblies, power supplies, and WWN (World Wide Name) cards. EM controls the state of the FRUs during system startup, hot-plug sequences, and fault recovery.
Table 4 System module descriptions (continued) System module Description FSSM The Fabric OS state synchronization management module is defined both as a component and a service. A component is a module in Fabric OS implementing a related set of functionality. A service is a collection of components grouped together to achieve a modular software architecture. FW FW is the Fabric Watch module.
Table 4 System module descriptions (continued) System module Description KTRC • LOG • RASLog subsystem. LSDB • The link state database is a part of the FSPF protocol that maintains records on the status of port links. This database is used to route frames. MFIC • MS-FICON messages relate to FICON installations. FICON-CUP messages are displayed under the FICU module. MPTH • Multicast path uses the shortest path first (SPF) algorithm to dynamically compute a broadcast tree.
Table 4 System module descriptions (continued) System module Description PSWP The portswap feature and associated commands generate these error messages. RCS The reliable commit service daemon generates log entries when it receives a request from the zoning, security, or management server for passing data messages to switches in the fabric. RCS then requests RTWR (reliable transport write and read) to deliver the message.
Table 4 System module descriptions (continued) System module Description TRCK The track change feature tracks the following events: • Turning on or off the track change feature • CONFIG_CHANGE • LOGIN • LOGOUT • FAILED_LOGIN If any of these events occurs, a message is sent to the system message log. Additionally, if the SNMP trap option is enabled, an SNMP trap is also sent. For information on configuring the track change feature, refer to the HP StorageWorks Fabric OS 5.
2 Error messages AUTH error messages AUTH-1001 Message , [AUTH-1001], ,, INFO, , has been successfully done. Probable Cause Indicates that the secret database operation has been updated using the secAuthSecret command. The values for Operation type can be "set" or "remove". Recommended Action No action is required. Severity INFO Message , [AUTH-1002], ,, ERROR, , has failed.
Severity INFO AUTH-1004 Message , [AUTH-1004], ,, ERROR, , Failed to set type to . Probable Cause Indicates that the authUtil command has failed to set the authentication configuration value. The data type can be either authentication type or DH group type. Recommended Action Retry the authUtil command. Run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
Recommended Action Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR AUTH-1007 Message , [AUTH-1007], ,, ERROR, , The proposed authentication protocol(s) are not supported: port .
Probable Cause Indicates an internal problem with the Secure Fabric OS. Recommended Action Reboot or power cycle the switch. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
AUTH-1013 Message , [AUTH-1013], ,, WARNING, , Can not perform authentication request message: port , message code Probable Cause Indicates that the system is running low on resources when receiving an authentication request. Recommended Action Usually this problem is transient. The authentication might fail. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands.
Recommended Action Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
AUTH-1022 Message , [AUTH-1022], ,, ERROR, , Failed to extract from payload: port . Probable Cause Indicates the authentication process failed to extract a particular value from the receiving payload. Recommended Action Usually this problem is transient. The authentication might fail. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands.
AUTH-1025 Message , [AUTH-1025], ,, ERROR, , Failed to get during : port Probable Cause Indicates the authentication process failed to get expected information during the specified authentication phase. Recommended Action Usually this problem is transient. The authentication might fail. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands.
AUTH-1028 Message , [AUTH-1028], ,, ERROR, , Failed to allocate for : port Probable Cause Indicates that 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 Usually this problem is transient. The authentication might fail.
Probable Cause Indicates the receiving payload does not have valid message code for a particular authentication phase. Recommended Action Usually this problem is transient. The authentication might fail. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
Severity ERROR AUTH-1033 Message , [AUTH-1033], ,, ERROR, , Disable port due to unauthorized switch Probable Cause Indicates that an entity was not configured in the SCC policy and tried to connect to the port. Recommended Action Add the entity's WWN to the SCC policy and reinitialize authentication by using the portDisable and portEnable commands or the switchDisable and switchEnable commands.
Recommended Action Usually this problem is transient. The authentication might fail. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
Severity ERROR AUTH-1038 Message , [AUTH-1038], ,, ERROR, , Failed to retrieve certificate during : port Probable Cause Indicates that the PKI certificate is not installed properly. Recommended Action Reinstall the PKI certificate, using the pkiCreate command. Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands.
Probable Cause Indicates that the switch has completed initializing the ports. This message occurs only on the SAN Switch 4/32. Recommended Action No action is required. Severity INFO BL-1002 Message , [BL-1002], ,, CRITICAL, , Init Failed: DISABLED because internal ports were not ONLINE, Probable Cause Indicates that the blade initiation failed because one or more of the internal ports was not online.
Severity CRITICAL BL-1004 Message , [BL-1004], ,, CRITICAL, , Suppressing blade fault in slot Probable Cause Indicates that the specified blade experienced a failure but was not faulted due to a user setting. This message occurs on only the Core Switch 2/64, SAN Director 2/128, and 4/256 SAN Director. Recommended Action Reboot or power cycle the blade, using the slotPowerOff and slotPowerOn commands.
Probable Cause Indicates that a failover occurred while a blade was initializing on the previously active CP. This message occurs on only the Core Switch 2/64, SAN Director 2/128, and 4/256 SAN Director. Recommended Action No action is required. The blade is reinitialized. Because reinitializing a blade is a disruptive operation and can stop I/O traffic, you might have to stop and restart the traffic during this process.
Severity CRITICAL BL-1010 Message , [BL-1010], ,, WARNING, , Blade in slot inconsistent with the hardware settings. Probable Cause Indicates that a failover occurred while some hardware changes were being made on the previously active CP (such as changing the domain ID). This message occurs on only the Core Switch 2/64, SAN Director 2/128, and 4/256 SAN Director. Recommended Action No action is required. This blade has been reinitialized.
BL-1012 Message , [BL-1012], ,, ERROR, , bport port int. is disabled. status=0x Port will be re-enabled in 1 minute. Probable Cause Indicates that the port generated an excessive number of interrupts that might prove fatal to the switch operation. The port is disabled to prevent the CP from becoming too busy. The bport is the blade port; this number might not correspond to a user port number.
BL-1014 Message , [BL-1014], ,, ERROR, , bport port int. is disabled. status=0x Probable Cause Indicates that the port generated an excessive number of interrupts that might prove fatal to the switch operation. The port is disabled to prevent the CP from becoming too busy. The bport is the blade port; this number might not correspond to a user port number.
• On the 4/8 SAN Switch, 4/16 SAN Switch, SAN Switch 2/8V, SAN Switch 2/16V, or SAN Switch 4/32, replace the switch. Severity ERROR BL-1016 Message , [BL-1016], ,, CRITICAL, , Blade port in slot failed to enable. Probable Cause Indicates that the specified blade port has failed to get enabled. Recommended Action Make sure that the blade is seated correctly. If the blade is seated correctly, reboot or power cycle the blade.
Recommended Action No action is required. Severity INFO BLL Error Messaages BLL-1000 Message , [BLL-1000], ,, CRITICAL, , ASIC driver detected Slot port as faulty (reason: ) Probable Cause Indicates that a blade regulation problem was reported on the specified slot number. The blade is faulted. This message occurs on only the Core Switch 2/64 and SAN Director 2/128.
If the message persists, replace the blade. Severity CRITICAL CDR error messages CDR-1001 Message , [CDR-1001], ,, WARNING, , Port port fault. Please change the SFP or check cable Probable Cause Indicates either a deteriorated SFP, an incompatible SFP pair, or a faulty cable between peer ports. Recommended Action Verify that you are using compatible SFPs on the peer ports.
CONF error messages CONF-1000 Message , [CONF-1000], ,, WARNING, , configDownload completed successfully but Zoning and Security parts were ignored Probable Cause Indicates that the user with the switchadmin role does not have permission to update the Zoning and Security configurations, so the Zoning and Security configurations are skipped while downloading the configuration file. Recommended Action No action is required.
Severity CRITICAL EM-1002 Message , [EM-1002], ,, CRITICAL, , System fan(s) status Probable Cause Indicates that a nonbladed system has overheated and is going to shut down. Before doing so, all fan speeds are dumped to the console. Recommended Action Verify that the location temperature is within the operational range of the switch. Refer to the hardware reference manual for the environmental temperature range of your switch.
On the Core Switch 2/64, SAN Director 2/128, and 4/256 SAN Director, replace the specified FRU. For the SAN Switch 2/32, replace the motherboard FRU. For the 4/8 SAN Switch, 4/16 SAN Switch, SAN Switch 2/8V, SAN Switch 2/16V, and SAN Switch 4/32 you must replace the switch. Severity CRITICAL EM-1004 Message , [EM-1004], ,, CRITICAL, , failed to power on Probable Cause Indicates that a FRU failed to power on and is not being used.
Probable Cause Indicates that a blade in the specified slot or the switch (for nonbladed 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. • Slot 1 through Slot 10 for the Core Switch 2/64, SAN Director 2/128, and 4/256 SAN Director.
For the 4/8 SAN Switch, 4/16 SAN Switch, SAN Switch 2/8V, and SAN Switch 2/16V you must replace the switch. Severity CRITICAL EM-1008 Message , [EM-1008], ,, CRITICAL, , Unit in faulted, incompatible with chassis option Probable Cause Indicates that a blade inserted in the specified slot is not compatible with the switch chassisConfig option. The blade is faulted.
Try reseating the FRU. If the message persists, replace the FRU. Severity CRITICAL EM-1010 Message , [EM-1010], ,, CRITICAL, , Received unexpected power down for But still has power Probable Cause Indicates that 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.
Probable Cause Indicates that a switch blade failed to transition from one state to another. It is faulted. The specific failed target state is displayed in the message. There are serious internal Fabric OS configuration or hardware problems on the switch. 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.
Recommended Action If the fruInfoSet command was being run, try the command again; otherwise, the update is automatically reattempted. If it continues to fail, try reseating the FRU. If the message persists, replace the FRU. Severity ERROR EM-1014 Message , [EM-1014], ,, ERROR, , Unable to read sensor on () Probable Cause Indicates that the environmental monitor was unable to access the sensors on the specified FRU.
Probable Cause Indicates that a problem was discovered when performing consistency checks during a warm boot. Recommended Action A reboot or power cycle is required to clear the situation. Severity WARNING EM-1016 Message , [EM-1016], ,, WARNING, , Cold recovery failed () Probable Cause Indicates that consistency checks during a cold boot discovered a problem. Recommended Action Monitor the switch.
Probable Cause Indicates that there was a failure to read chassis type from the system. Recommended Action Verify that the CP blade is operational and properly seated in the slot. Severity CRITICAL EM-1019 Message , [EM-1019], ,, WARNING, , Current chassis configuration option is not compatible with standby firmware version (Pre 4.
• WWN 1 or WWN 2 for the Core Switch 2/64, SAN Director 2/128, and 4/256 SAN Director. 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 might display, but these parts cannot be replaced: the entire switch is a FRU.
Severity ERROR EM-1031 Message , [EM-1031], ,, ERROR, , ejector not closed Probable Cause Indicates that the environmental monitor (EM) has 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, SAN Director 2/128, and 4/256 SAN Director. Recommended Action Close the ejector switch if the FRU is intended for use.
Probable Cause Indicates that the specified FRU has been marked as faulty for the specified reason. 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, SAN Director 2/128, and 4/256 SAN Director.
Recommended Action Check that the identified AC circuit switch is turned on, that the power cord is properly attached and undamaged, and that the power source is operating properly. Severity ERROR EM-1036 Message , [EM-1036], ,, WARNING, , is not accessible. Probable Cause Indicates that the specified FRU does not seem to be present on the switch. If the FRU is a WWN card, then default WWN and IP addresses are used for the switch.
• WWN 1 or WWN 2 for the Core Switch 2/64, SAN Director 2/128, and 4/256 SAN Director. 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 might display, but these parts cannot be replaced: the entire switch is a FRU.
The 4/8 SAN Switch, 4/16 SAN Switch has 4 fans and 1 power supply, but these parts cannot be replaced: the entire switch is a FRU. Recommended Action Try reseating the FRU. If the message persists, replace the FRU. Severity WARNING EM-1043 Message , [EM-1043], ,, WARNING, , Can't power . Probable Cause Indicates that the specified FRU cannot be powered on or off.
been faulted, because it is indicating a predicted failure. If new_state is Down (not enough power), a newly inserted port blade was not powered on because there was not enough power available. Recommended Action The Core Switch 2/64 requires two power supplies for a fully populated chassis; however, you should always operate the system with four operating power supplies for redundancy.
EM-1048 Message , [EM-1048], ,, INFO, , I2C access recovered: state Probable Cause Indicates that 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.
• PS 1 through PS 4 (power supplies) for the Core Switch 2/64, SAN Director 2/128, and 4/256 SAN Director, 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).
Severity INFO EM-1051 Message , [EM-1051], ,, INFO, , : Inconsistency detected, FRU re-initialized Probable Cause Indicates that 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 might have been disrupted. Recommended Action No action is required.
• voltages in volts • temperature in Celsius • fan speeds in RPM Recommended Action If the message is isolated, it might be a transient problem with the sensor hardware; monitor the error messages on the switch. If the message is persistent, without other environmental errors, replace the FRU. If the message is persistent, and there are other associated environmental messages, follow the actions for those messages.
EM-1055 Message , [EM-1055], ,, WARNING, , : Port media incompatible. Reason: Probable Cause Indicates that an incompatible port media is detected. The possible causes are: • The port media is not capable of running at the configured port speed. • The port media generates too much heat to be used in the slot. Recommended Action Verify that the media can be run at the configured port speed.
Severity WARNING EM-1058 Message , [EM-1058], ,, WARNING, , Switch gets reset: Probable Cause Indicates the switch is getting an automatic reset. This is usually a transient problem. Recommended Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
• The API host computer is shut down. • There has been a network problem. • The Ethernet cable is not properly connected to the switch. • A user has unplugged the Ethernet cable and then plugged it back in. Recommended Action This problem can be transient; try to reestablish the connection. If the cause is a network or Ethernet cable problem, you must fix the problem before you can reestablish an API session. Verify that your workstation has a TCP connection to the switch.
FABR-1003 Message , [FABR-1003], ,, WARNING, , port : ILS bad size , wanted Probable Cause Indicates that an internal link service (ILS) information unit of invalid size has been received. The neighbor switch has sent an invalid sized payload. Recommended Action Investigate the neighbor switch for problems. Run the errShow command on the neighbor switch to view the error log for additional messages.
FABR-1005 Message , [FABR-1005], ,, WARNING, , : port : status 0x () xid = 0x Probable Cause Indicates that the application failed to send an async command for the specified port. The message provides additional details regarding the reason for the failure and the exchange ID of the command. This can happen if a port is about to go down.
Recommended Action In case of severe memory corruption, the system might recover by performing an automatic failover. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
FABR-1010 Message , [FABR-1010], ,, WARNING, , Probable Cause Indicates that the 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 the Fabric OS. Recommended Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
Severity WARNING FABR-1013 Message , [FABR-1013], ,, CRITICAL, , No Memory: pid= file=
Probable Cause Indicates that 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. Run the fabricShow command to view the domain IDs across the fabric and the configure command to change the insistent domain ID mode. Refer to the HP StorageWorks Fabric OS 5.
Probable Cause Indicates that a failure occurred when trying to set the principal switch using the fabricPrincipal command. The message notifies the user that the switch failed to become the principal switch because either: • The switch joined an existing fabric and bypassed the F0 state. • The fabric already contains a principal switch that has a lower WWN. Recommended Action Make sure that no other switches is configured as the principal switch.
Recommended Action Bring the fabric size within the licensed limits. Either a full fabric license must be added or the size of the fabric must be changed to within the licensed limit. Contact your switch provider to obtain a full fabric license. Severity CRITICAL FABR-1021 Message , [FABR-1021], ,, CRITICAL, , Webtool is disabled Probable Cause Indicates that this switch has a value-line license and has a limited number of domains.
FABR-1023 Message , [FABR-1023], ,, INFO, , Fabric size is within supported configuration (). Fabric limit timer () stopped at . Probable Cause Indicates that 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.
• R_RDY mode: Receiver-ready flow control mode. This is the Fibre Channel standard protocol, that uses R_RDY primitive for flow control. • 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.
Probable Cause Indicates that an internal problem has been detected by the software. This is usually an internal Fabric OS problem or file corruption. Recommended Action Reboot or power cycle the switch. If the message persists, run the firmwareDownload command to update the firmware.
FABS-1006 Message , [FABS-1006], ,, WARNING, , : object
FABS-1008 Message , [FABS-1008], ,, WARNING, , : Media oid mapping failed Probable Cause Indicates that the 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.
FABS-1011 Message , [FABS-1011], ,, ERROR, , []:Invalid input state 0x Probable Cause An unrecognized state code was used in an internal Fabric OS message for a FRU. Recommended Action Reboot or power-cycle the CP or system. If the message persists, run the firmwareDownload command to update the firmware.
Try reseating the blade If this is a valid blade and reseating doesn't help, then replace the blade Severity ERROR FABS-1014 Message , [FABS-1014], ,, ERROR, , []:Unknown FRU type 0x Probable Cause An unrecognized of FRU has been discovered in the system. This may be caused by an incorrect FRU header, inability to read the FRU header, or the FRU may not be supported by this platform or Fabric OS version.
FCMC error messages FCMC-1001 Message , [FCMC-1001], ,, CRITICAL, , : failed, out of memory condition Probable Cause Indicates that the switch is low on memory and failed to allocate new memory for an information unit (IU). Recommended Action A nonbladed switch will automatically reboot. For a bladed switch, the active CP blade will automatically fail over and the standby CP will become the active CP.
Probable Cause Indicates that the response frame received on the specified port for a 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.
FICU error messages FICU-1001 Message , [FICU-1001], ,, ERROR, , : config failed rc = Probable Cause Indicates that one of the configuration management functions failed. The key variable is part of the Fabric OS configuration database and is for support use only. The error variable is an internal error number. Recommended Action Execute an haFailover on the switch if it has redundant CPs or reboot the switch.
Recommended Action Run the licenseShow command to check the installed licenses on the switch. The switch cannot be managed using FICON-CUP commands until the FICON-CUP license is installed. Contact your switch supplier for a FICON-CUP license. Run the licenseAdd command to add the license to your switch.
FICU-1006 Message , [FICU-1006], ,, WARNING, , Control Device Allegiance Reset (Logical Path: 0x:0x) Probable Cause Indicates that the path with the specified PID and channel image ID lost allegiance to a FICON-CUP device. Recommended Action Check if the FICON channel corresponding to the PID in the message is functioning correctly.
Severity WARNING FICU-1009 Message , [FICU-1009], ,, WARNING, , FMS Mode enable failed due to insufficient frame filtering resources on some ports Probable Cause Indicates that the frame filtering resources required to enable FICON Management Server mode (fmsmode) were not available on some of the ports. Recommended Action Use the perfDelFilterMonitor command to delete the filter-based performance monitors used on all ports to free up the resources.
Probable Cause Indicates that the FICON-CUP daemon failed to get switch RNID from the management server due to a Fabric OS problem. The domain variable displays the domain ID of the target switch for this RNID. The error variable is an internal error number. Recommended Action If this is a bladed switch, execute the haFailover command. If the problem persists, or if this is a nonbladed switch, download a new firmware version using the firmwareDownload command. Refer to the HP StorageWorks Fabric OS 5.
on core PID mode and the HP StorageWorks Fabric OS 5.x command reference guide for information on the configure command and ficoncupset command. Severity WARNING FICU-1005 Message , [FICU-1005], ,, ERROR, , Failed to initialize rc = Probable Cause Indicates that an initialization of a module within the FICON-CUP daemon failed. Recommended Action Download a new firmware version using the firmwareDownload command.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING FICU-1008 Message , [FICU-1008], ,, WARNING, , FMS mode has been enabled. Port: has been disabled due to port address conflict. Probable Cause Indicates that the specified port was disabled when the switch was enabled for FICON Management Server mode (fmsmode).
Recommended Action Use the portDisable command to disable the specified port causing the address conflict. Severity WARNING FLOD error messages FLOD-1001 Message , [FLOD-1001], ,, WARNING, , Unknown LSR type: port , type Probable Cause Indicates that the link state record (LSR) type is unknown. The following two LSR header types are the only known types: 1 - Unicast and 3 - Multicast. Recommended Action No action is required.
Recommended Action Reduce the number of switches in the fabric or reduce the number of redundant ISLs between two switches. Severity ERROR FLOD-1005 Message , [FLOD-1005], ,, WARNING, , Invalid received domain ID: Probable Cause Indicates that the received LSR contained an invalid domain number. The switch will correct this condition automatically. Recommended Action No action is required. The LSR is discarded.
Severity ERROR FSPF-1002 Message , [FSPF-1002], ,, INFO, , Wrong neighbor ID () in Hello message from port , expected ID = Probable Cause Indicates that the switch received the wrong domain ID from a neighbor (adjacent) switch in the HELLO message from a specified port. This might happen when a domain ID for a switch has been changed. Recommended Action No action is required.
Recommended Action Use a frame analyzer to verify that the reported section ID is 0. Any connected (other manufacturer) switch with a section ID other than 0 is incompatible in a fabric of switches. Disconnect the offending switch. Severity ERROR FSPF-1006 Message , [FSPF-1006], ,, ERROR, , FSPF Version not supported, input port = Probable Cause Indicates that the FSPF version is not supported on the specified input port.
Probable Cause Indicates that an application has sent too many concurrent high availability (HA) data updates. Recommended Action Run the haSyncStart command if this is a dual-CP system, or reboot the switch if it is a nonbladed system. The haSyncStart command will automatically run the haSyncStop command if required. If the message persists, run supportFtp and traceFtp -e (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
FSS-1005 Message , [FSS-1005], ,, WARNING, , FSS read failure Probable Cause Indicates that the read system call to the FSS device failed. Recommended Action If the message persists, run supportFtp and traceFtp -e (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
FSSM-1003 Message , [FSSM-1003], ,, WARNING, , HA State out of sync Probable Cause Indicates that the 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.
Probable Cause Indicates that the internal temperature of the switch has changed. Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. To prevent recurring messages, disable the changed alarm for this threshold. If you receive a temperature-related message, check for an accompanying fan-related message and check fan performance. If all fans are functioning normally, check the climate control in your lab.
FW-1004 Message , [FW-1004], ,, INFO, ,
Severity WARNING FW-1007 Message , [FW-1007], ,, WARNING, ,
If the power supply is functioning below the acceptable boundary, verify that it is seated correctly in the chassis. Run the psShow command to view the status of the power supply. If the power supply continues to be a problem, replace the faulty power supply. Severity INFO FW-1010 Message , [FW-1010], ,, WARNING, ,
Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. Severity INFO FW-1033 Message , [FW-1033], ,, INFO, ,
Recommended Action Frequent fluctuations in temperature might indicate a deteriorating SFP. Replace the SFP. Severity WARNING FW-1036 Message , [FW-1036], ,, INFO, ,
Probable Cause Indicates that the receive power value of the SFP has fallen below the low boundary. The receive performance area measures the amount of incoming laser to help you determine if the SFP is in good working condition or not. If the counter often exceeds the threshold, the SFP is deteriorating. Recommended Action Verify that your optical components are clean and function properly. Replace deteriorating cables or SFPs. Check for damage from heat or age.
FW-1041 Message , [FW-1041], ,, INFO, ,
Recommended Action Replace the SFP. Severity WARNING FW-1044 Message , [FW-1044], ,, INFO, ,
Probable Cause Indicates that the value of the SFP voltage has fallen below the low boundary. Recommended Action Verify that your optical components are clean and function properly. Replace deteriorating cables or SFPs. Check for damage from heat or age. Severity WARNING FW-1047 Message , [FW-1047], ,, WARNING, ,
Probable Cause Indicates that the value of the SFP voltage has changed. Recommended Action Frequent voltage fluctuations are an indication that the SFP is deteriorating. Replace the SFP. Severity INFO FW-1050 Message , [FW-1050], ,, WARNING, ,
Probable Cause Indicates that the value of the SFP voltage has changed from a value outside of the acceptable range to a value within the acceptable range. Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. Severity INFO FW-1113 Message , [FW-1113], ,, INFO, ,
FW-1115 Message , [FW-1115], ,, INFO, ,
• an E_Port has gone offline. • a principal link has segmented from the fabric. Recommended Action Verify that the cable is properly connected at both ends. Verify that the SFPs have not become faulty. An inexplicable fabric reconfiguration might be a transient error and might not require troubleshooting. Severity INFO FW-1118 Message , [FW-1118], ,, INFO, ,
Severity INFO FW-1120 Message , [FW-1120], ,, INFO, ,
Probable Cause Indicates that the number of domain ID changes has fallen below the low boundary. Domain ID changes occur when there is a conflict of domain IDs in a single fabric and the principal switch has to assign another domain ID to the switch. Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. A low number of domain ID changes means that the fabric is functioning normally.
FW-1125 Message , [FW-1125], ,, INFO, ,
FW-1127 Message , [FW-1127], ,, INFO, ,
FW-1129 Message , [FW-1129], ,, INFO, ,
Severity INFO FW-1132 Message , [FW-1132], ,, INFO, ,
Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. A low number of fabric logins means that the fabric is functioning normally. Severity INFO FW-1135 Message , [FW-1135], ,, INFO, ,
Probable Cause Indicates that the number of SFP state changes has changed. SFP state changes occur when the SFP is inserted or removed. Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. Severity INFO FW-1138 Message , [FW-1138], ,, INFO, ,
FW-1140 Message , [FW-1140], ,, INFO, ,
can cause link loss errors. Link loss errors frequently occur due to a loss of synchronization. Check for concurrent loss of synchronization errors and, if applicable, troubleshoot them. Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. A low number of link loss errors means that the switch is functioning normally.
FW-1164 Message , [FW-1164], ,, INFO, , ,
Recommended Action Check both ends of your cable connection. Verify that the cable and SFPs are not faulty. If you continue to experience loss-of-synchronization errors, troubleshoot your HBA and contact your switch service provider. Severity WARNING FW-1167 Message , [FW-1167], ,, INFO, , ,
Probable Cause Indicates that the number of signal losses that the port experiences has fallen below the low boundary. Loss of signal generally indicates a physical problem. Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. A low number of signal loss errors means that the switch is functioning normally.
FW-1172 Message , [FW-1172], ,, INFO, , ,
Severity WARNING FW-1175 Message , [FW-1175], ,, INFO, , ,
Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. A low number of invalid words means that the switch is functioning normally. Severity INFO FW-1178 Message , [FW-1178], ,, WARNING, , ,
Probable Cause Indicates that the number of invalid CRCs that the port experiences has changed. Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. Frequent fluctuations in CRC errors generally indicate an aging fabric. Check your SFPs, cables, and connections for faulty hardware. Verify that all optical hardware is clean.
Probable Cause Indicates that the number of invalid CRCs that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range. Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. Frequent fluctuations in CRC errors generally indicate an aging fabric. Check your SFPs, cables, and connections for faulty hardware. Verify that all optical hardware is clean.
FW-1186 Message , [FW-1186], ,, INFO, , ,
Severity INFO FW-1189 Message , [FW-1189], ,, INFO, , ,
Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. Severity INFO FW-1192 Message , [FW-1192], ,, INFO, , ,
FW-1194 Message , [FW-1194], ,, WARNING, , ,
dirty equipment, temperature fluctuations, and aging equipment. You should set your high boundaries to five- or six-digit figures, as only large numbers of messages indicate a problem in this area. Recommended Action Verify that your optical components are clean and function properly. Replace deteriorating cables or SFPs. Check for damage from heat or age.
Severity WARNING FW-1219 Message , [FW-1219], ,, INFO, ,
Probable Cause Indicates that the number of EE CRC errors has fallen below the low 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 might also be caused by dirty equipment, temperature fluctuations, and aging equipment. Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation.
Severity INFO FW-1244 Message , [FW-1244], ,, INFO, ,
Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. Severity INFO FW-1247 Message , [FW-1247], ,, INFO, ,
Probable Cause Indicates that the number of EE word frames that the switch transmits has fallen 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. Respond to this message as is appropriate to the particular policy of the end-user installation.
FW-1272 Message , [FW-1272], ,, INFO, ,
Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation. Severity INFO FW-1275 Message , [FW-1275], ,, INFO, ,
FW-1297 Message , [FW-1297], ,, INFO, ,
authorized to establish telnet connections to switches in the fabric. The IP addresses use standard "dot" notation (for example, 255.255.255.255). Recommended Action No action is required. Severity INFO FW-1300 Message , [FW-1300], ,, INFO, ,
FW-1302 Message , [FW-1302], ,, WARNING, ,
addresses that are authorized to establish API connections to switches in the fabric. The IP addresses use standard "dot" notation (for example, 255.255.255.255). 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.
FW-1307 Message , [FW-1307], ,, INFO, ,
Severity INFO FW-1310 Message , [FW-1310], ,, WARNING, ,
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-1313 Message , [FW-1313], ,, INFO, ,
Probable Cause Indicates that the number of WSNMP violations has changed from a value outside of the acceptable range to a value within the acceptable range. WSNMP violations indicate that an SNMP "get/set" operation request has been received from an unauthorized IP address. Recommended Action No action is required. Severity INFO FW-1316 Message , [FW-1316], ,, INFO, ,
FW-1318 Message , [FW-1318], ,, WARNING, ,
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. Severity INFO FW-1321 Message , [FW-1321], ,, INFO, ,
FW-1323 Message , [FW-1323], ,, INFO, ,
Recommended Action No action is required. Severity INFO FW-1326 Message , [FW-1326], ,, WARNING, ,
Probable Cause Indicates that the number of front panel violations has changed. Front panel violations indicate that an unauthorized front panel request has been received. The FRONTPANEL_POLICY contains a list of switch WWNs for which front panel 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.
FW-1331 Message , [FW-1331], ,, INFO, ,
Recommended Action No action is required. Severity INFO FW-1334 Message , [FW-1334], ,, WARNING, ,
Probable Cause Indicates that 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. DCC policies ensure that whenever a device performs an FLOGI request, the WWN specified in the FLOGI is validated to be connected to the authorized port.
Recommended Action Run the errShow command to determine the device WWN, switch WWN, and switch port. Responses to security-class messages depend on user policies. Consult your security administrator for response strategies and policies. Severity WARNING FW-1339 Message , [FW-1339], ,, INFO, ,
FW-1341 Message , [FW-1341], ,, INFO, ,
FW-1344 Message , [FW-1344], ,, INFO, ,
Probable Cause Indicates that the number of invalid timestamps has risen above the high boundary. Invalid-timestamp violations indicate a packet with an invalid timestamp has been received from the primary FCS. When the primary fabric configuration server (FCS) downloads a new configuration to other switches in the fabric, the packet is tagged with a timestamp. The receiving switch compares this timestamp to its current time. If the difference is too great, it rejects the packet.
Recommended Action Responses to security-class messages depend on user policies. Consult your security administrator for response strategies and policies. Severity INFO FW-1349 Message , [FW-1349], ,, INFO, ,
FW-1351 Message , [FW-1351], ,, INFO, ,
Probable Cause Indicates that the number of invalid certificates has fallen below the low boundary. This violation indicates that a packet with an invalid certificate has been received from the primary FCS. Before a new primary FCS switch sends any configuration data to any switch in the fabric, it first sends its certificate to all the switches in the fabric.
Severity INFO FW-1356 Message , [FW-1356], ,, INFO, ,
Probable Cause Indicates that the number of authentication failures has risen above the high boundary. Authentication failures can occur for many reasons. The switch on the other side might not support the protocol, have an invalid certificate, not be signed properly or send unexpected packets. The port where authentication fails is segmented. This counter keeps track of the number of authentication failures. Recommended Action Responses to security-class messages depend on user policies.
FW-1361 Message , [FW-1361], ,, INFO, ,
Severity INFO FW-1364 Message , [FW-1364], ,, INFO, ,
Severity WARNING FW-1367 Message , [FW-1367], ,, INFO, ,
sends its certificate to a switch, the receiving switch saves the WWN of that primary FCS switch. If a secure switch finds that there are no FCSs in the fabric, but it still has the WWN of the last primary FCS switch, it increments this counter and resets the WWN of the primary FCS to all zeroes. Recommended Action No action is required. Severity INFO FW-1370 Message , [FW-1370], ,, WARNING, ,
FW-1372 Message , [FW-1372], ,, INFO, ,
compatible security database. A compatible security database means that the version stamp and FCS policy matches exactly. Recommended Action Responses to security-class messages depend on user policies. Consult your security administrator for response strategies and policies. Severity WARNING FW-1375 Message , [FW-1375], ,, INFO, ,
FW-1377 Message , [FW-1377], ,, INFO, ,
primary FCS switch have been executed on a non-primary FCS switch. There are many commands that can be executed only on the primary FCS switch as well as one security command that can be executed only on a backup FCS switch. The counter increments every time someone issues one of these commands on a switch where it is not allowed. Recommended Action No action is required.
FW-1402 Message , [FW-1402], ,, WARNING, ,
Severity WARNING FW-1425 Message , [FW-1425], ,, INFO, , Switch status changed from to HEALTHY. Probable Cause Indicates that the switch status has changed to a healthy state. This occurred because a policy is no longer violated. The valid values are MARGINAL or DOWN. Recommended Action No action is required. Respond to this message as is appropriate to the particular policy of the end-user installation.
Severity WARNING FW-1428 Message , [FW-1428], ,, WARNING, , Switch status change contributing factor Power supply: absent. Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the number of missing power supplies is greater than or equal to the policy set by the switchStatusPolicySet command. Recommended Action Replace the missing power supply.
Recommended Action Replace the FRU with the faulty temperature sensor. Severity WARNING FW-1431 Message , [FW-1431], ,, WARNING, , Switch status change contributing factor Fan: bad. Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the number of faulty fans is greater than or equal to the policy set by the switchStatusPolicySet command.
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, this will cause both CPs to come up in a non-redundant state. Recommended Action Run the firmwareShow command to verify that both CPs have compatible firmware levels. Run the firmwareDownload command to install the same level of firmware to both CPs. Replace any faulty CPs.
FW-1436 Message , [FW-1436], ,, WARNING, , Switch status change contributing factor Marginal ports: marginal ports. (Port(s) ) Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the number of marginal ports is greater than or equal to the policy set using the switchStatusPolicySet command.
Severity WARNING FW-1439 Message , [FW-1439], ,, WARNING, , Switch status change contributing factor Switch offline. Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the switch is offline. Recommended Action Run the switchEnable command. Severity WARNING FW-1440 Message , [FW-1440], ,, INFO, , state has changed to .
FW-1442 Message , [FW-1442], ,, INFO, , state has changed to . Probable Cause Indicates that specified FRU’s state has changed to "on". Recommended Action No action is required. Verify that the event was planned. Severity INFO FW-1443 Message , [FW-1443], ,, INFO, , state has changed to . Probable Cause Indicates that specified FRU’s state has changed to "off".
HAM error messages HAM-1001 Message , [HAM-1001], ,, CRITICAL, , Standby CP is not Healthy, device status BAD, severity = Probable Cause Indicates that a standby CP device error is reported by the high-availability manager (HAM) Health Monitor, with a specific device and severity level. The severity level can be critical, major, or minor.
• Processor rebooted - Fastboot • Processor rebooted - Giveup Master:SYSM • Processor rebooted - CP Faulty:SYSM • Processor rebooted - FirmwareDownload • Processor rebooted - ConfigDownload:MS • Processor rebooted - ChangeWWN:EM • Processor rebooted - Reboot:WebTool • Processor rebooted - Fastboot:WebTool • Processor rebooted - Software Fault:Software Watchdog • Processor rebooted - Software Fault:Kernel Panic • Processor rebooted - Software Fault:ASSERT • Processor rebooted - Reboot:SNMP • Processor reboot
HAMK-1003 Message , [HAMK-1003], ,, INFO, , Heartbeat up Probable Cause Indicates that the active CP blade detects the standby CP blade. This message indicates that the standby CP blade is available to take over in case a failure happens on the active CP blade. This message is typically seen when the standby CP blade reboots. Recommended Action No action is required. This message means that the standby CP is healthy.
Severity ERROR HIL-1102 Message , [HIL-1102], ,, ERROR, , Slot faulted, () is below threshold. Probable Cause Indicates that the blade voltage is below threshold. This message is specific to the Core Switch 2/64, SAN Director 2/128, or 4/256 SAN Director. Recommended Action Replace the faulty blade.
Try to reseat the fan FRU and power supply FRU and verify that they are seated properly. If the problem persists, replace the fan FRU or the power supply FRU as necessary. Severity ERROR HIL-1105 Message , [HIL-1105], ,, ERROR, , Switch error, () above threshold. Probable Cause Indicates that the switch voltage is above threshold.
Probable Cause Indicates that the switch voltage is above threshold. This message is specific to nonbladed switches and is not applicable to the Core Switch 2/64, SAN Director 2/128, or 4/256 SAN Director. Recommended Action For the 4/8 SAN Switch, 4/16 SAN Switch, SAN Switch 2/8V and SAN Switch 2/16V, the entire switch must be replaced, because these switches do not have FRUs. For the SAN Switch 2/32 and SAN Switch 4/32, replace the motherboard FRU.
For the SAN Switch 2/32 and SAN Switch 4/32, if the fan problem causes the switch to have temperature problems, replace the fan FRU. Severity WARNING HIL-1202 Message , [HIL-1202], ,, ERROR, , Blower faulted, speed ( RPM) below threshold. Probable Cause Indicates that the specified fan speed (in RPM) has fallen below the minimum threshold.
HIL-1204 Message , [HIL-1204], ,, ERROR, , Fan faulted, speed ( RPM) below threshold. Probable Cause Indicates that the specified fan speed (in RPM) has fallen below the minimum threshold. This message is specific to nonbladed switches and is not applicable to the Core Switch 2/64, SAN Director 2/128, or 4/256 SAN Director. Recommended Action Run the tempShow command to verify that the switch temperatures are within operational range.
HIL-1206 Message , [HIL-1206], ,, ERROR, , Fan sensor speed ( RPM) below threshold. Probable Cause Indicates that the specified fan speed (in RPM) has fallen below the minimum threshold. This problem can quickly cause the switch to overheat. This message is specific to nonbladed switches and is not applicable to the Core Switch 2/64, SAN Director 2/128, or 4/256 SAN Director.
HIL-1301 Message , [HIL-1301], ,, ERROR, , 1 blower failed. Replace failed blower assembly immediately. Probable Cause Indicates that a fan FRU has failed. This message is often preceded by a low speed error message. This problem can quickly cause the switch to overheat. Recommended Action Run the tempShow command to check if the switch temperatures are too high. Refer to the hardware reference manual for the temperature range of your switch.
HIL-1303 Message , [HIL-1303], ,, ERROR, , One fan failed. Replace failed fan FRU immediately. Probable Cause Indicates that a fan FRU has failed. This message is often preceded by a low fan speed message. Recommended Action Run the tempShow command to check if the switch temperatures are too high. Refer to the hardware reference manual for the temperature range of your switch. Run the fanShow command to verify that the fan is faulty.
Recommended Action Run the tempShow command to check if the switch temperatures are too high. Refer to the hardware reference manual for the temperature range of your switch. Run the fanShow command to verify that the fans are faulty. For the SAN Switch 2/32 and SAN Switch 4/32, replace the fan FRU. For the 4/8 SAN Switch, SAN Switch 2/8V and SAN Switch 2/16V, the entire switch must be replaced, because these switches do not have FRUs.
Severity ERROR HIL-1308 Message , [HIL-1308], ,, ERROR, , All fans failed. Replace failed fan FRUs immediately. Probable Cause Indicates that all fans have failed. This message is often preceded by a low fan speed message. Recommended Action Run the tempShow command to check if the switch temperatures are too high. Refer to the hardware reference manual for the temperature range of your switch. Run the fanShow command to verify that the fans are faulty.
Probable Cause Indicates that multiple fans have failed. This message is often preceded by a low fan speed message. Recommended Action For the SAN Switch 2/32 and SAN Switch 4/32, replace the fan FRU. For the 4/8 SAN Switch, 4/16 SAN Switch, SAN Switch 2/8V and SAN Switch 2/16V, the entire switch must be replaced, because these switches do not have FRUs. Severity WARNING HIL-1401 Message , [HIL-1401], ,, WARNING, , One fan FRU missing. Install fan FRU immediately.
Recommended Action Install the missing fan FRUs immediately. Severity WARNING HIL-1404 Message , [HIL-1404], ,, WARNING, , fan FRU(s) missing. Install fan FRU(s) immediately. Probable Cause Indicates that one or more fan FRUs have been removed. Recommended Action Install the missing fan FRUs immediately.
Probable Cause Indicates that the temperature of this blade has risen above the critical threshold. This usually follows a high-temperature message. This message only occurs on the Core Switch 2/64, SAN Director 2/128, and 4/256 SAN Director. Recommended Action Run the tempShow command to monitor switch temperatures. Refer to the hardware reference manual for the temperature range of your switch. Run the fanShow command to verify all the fans are working properly.
Recommended Action No action is required. Severity INFO HIL-1505 Message , [HIL-1505], ,, WARNING, , High temperature ( C) exceeds environmental specifications. Probable Cause Indicates that temperatures in the system have risen above the warning threshold. Recommended Action Run the tempShow command to monitor switch temperatures. Refer to the hardware reference manual for the temperature range of your switch.
HIL-1507 Message , [HIL-1507], ,, CRITICAL, , High temperature warning time expired. System preparing for shutdown. Probable Cause Indicates that temperatures in the system have risen above the critical threshold. This message only occurs on the SAN Switch 2/16V, SAN Switch 2/8V, and SAN Switch 2/32. Recommended Action Temperatures have probably caused damage to the switch and the system shuts down automatically.
HIL-1509 Message , [HIL-1509], ,, CRITICAL, , High temperature ( C). Warning time expired. System preparing for shutdown. Probable Cause Indicates that temperatures in the system have risen above the critical threshold. Recommended Action Temperatures have probably caused damage to the switch and the system shuts down automatically. To help prevent future problems, make sure that all the fans are working properly.
Recommended Action Run the fanShow command to verify that all fans are operating correctly. Replace any deteriorating fan FRUs. Run the tempShow command to verify temperature values. If any sensor is too high, monitor the switch. Try rebooting or power cycling the switch.
HLO-1003 Message , [HLO-1003], ,, ERROR, , Invalid Hello received from port , Domain = , Remote Port = Probable Cause Indicates that the HLO message received was invalid and the frame was dropped. The HP StorageWorks switch will not accept FSPF frames from the remote switch. The switch has received an invalid HLO because either the domain or port number in the HLO message has an invalid value.
Probable Cause Indicates that the PID format was changed by the administrator. Recommended Action No action is required. For more information on PID, format refer to the HP StorageWorks Fabric OS 5.x administrator’s guide. Severity INFO KSWD error messages KSWD-1003 Message , [KSWD-1003], ,, WARNING, , kSWD: Probable Cause Indicates a warning state within the system. A critical application error was reported in the watchdog subsystem.
Recommended Action No action is required. Severity WARNING KTRC-1002 Message , [KTRC-1002], ,, INFO, , Concurrent trace dumping. Probable Cause Indicates that the initial background dump has not completed. Recommended Action No action is required. Severity INFO KTRC-1003 Message , [KTRC-1003], ,, ERROR, , Cannot open ATA dump device Probable Cause Indicates that the ATA dump driver is not initialized properly.
LOG Error Messages LOG-1000 Message , [LOG-1000], ,, INFO, , Previous message repeated time(s) Probable Cause Indicates that the previous message repeated the number of times specified by the repeat count. Recommended Action No action is required. Severity INFO LOG-1001 Message , [LOG-1001], ,, CRITICAL, , A log message was dropped Probable Cause Indicates that a log message was dropped.
Run the saveCore command to FTP core files to a server location. It is normal behavior if there are no core files to transfer. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
Probable Cause Indicates that there is no local link state record entry in the link state database. The switch should always generate its own local entry when starting up. An "incarnation" is a progressive number that identifies the most recent version of the LSR (link state record). The switch generates its local link state record when first enabled. By disabling and enabling the switch, a new local link state record is generated. Recommended Action Run the switchDisable and switchEnable commands.
MFIC-1002 Message , [MFIC-1002], ,, INFO, , Chassis FRU header not programmed for switch NID, using defaults (applies only to FICON environments). Probable Cause Indicates that custom switch node descriptor (NID) fields have not been programmed in nonvolatile storage. The default values are used. The Switch NID is used only in the following SB ELS frames: Request Node Identification Data (RNID) and Registered Link Incident Record (RLIR).
Probable Cause Indicates that 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 , [MPTH-1002], ,, ERROR, , Null lsrP, lsId = Probable Cause Indicates that a link state record is null. Recommended Action No action is required.
Probable Cause Indicates that an unexpected message has been received in the specified message queue. The queue name is always fspf_q. The queue ID and message type can be any of the following: • 2 - MSG_TX • 3 - MSG_INTR • 4 - MSG_STR • 6 - MSG_ASYNC_IU • 7 - MSG_LINIT_IU • 8 - MSG_RSCN • 9 - MSG_IOCTL • 10 - MSG_ACCEPT • 11 - MSG_IU_FREE • 12 - MSG_US • 13 - MSG_EXT_RSCN • 14 - MSG_RDTS_START • 15 - MSG_RDTS_SENDEFP • 16 - MSG_RDTS_RESET Recommended Action No action is required.
Probable Cause The MS platform service is unstable. The can be one of the following: • The switch did not respond to a request for GCAP (MS Get Capabilities) command. Recommended Action: No action is required. • The GCAP (MS Get Capabilities) is supported but the flag for MS platform service is not set. Recommended Action: Set the flag for the MS Platform Service.
Run the fabricShow command or the secFabricShow command to verify that the number of domains matches the Management Server known domains. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity INFO MS-1004 Message , [MS-1004], ,, INFO, , MS detected ONLY 1 Domain(d=).
MS-1006 Message , [MS-1006], ,, ERROR, , MS Unexpected iu_data_sz= Probable Cause Indicates that MS received IU data of unexpected size. The IU payload and the IU size might be inconsistent with each other or with the command that is currently being processed. This message is often transitory. Recommended Action Wait a few minutes and try the operation again.
Recommended Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR NBFS Error Messages NBFS-1001 Message , [NBFS-1001], ,, INFO, , Duplicate E_Port SCN from port in state () Probable Cause Indicates that a duplicate E_Port State Change Number was reported.
If this error occurs repeatedly, it means 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.
Severity WARNING NS-1002 Message , [NS-1002], ,, WARNING, , Remote switch 0x has firmware revision lower than 2.2: which is not supported! Probable Cause Indicates that the local switch cannot interact with the remote switch due to incompatible or obsolete firmware.
Probable Cause Indicates that 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 CPs. This means that the active and standby CPs are out of sync. Any execution of the haFailover or firmwareDownload commands will be disruptive.
PDM-1003 Message , [PDM-1003], ,, WARNING, , pdm [-d] -S -s Probable Cause Indicates that a syntax error occurred when trying to launch the PDM process. Recommended Action Run the firmwareDownload command to reinstall the firmware. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
Severity WARNING PDM-1006 Message , [PDM-1006], ,, WARNING, , Too many files in sync.conf Probable Cause Indicates that the configuration file sync.conf contains too many entries. Recommended Action Run the firmwareDownload command to reinstall the firmware. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING PDM-1009 Message , [PDM-1009], ,, WARNING, , Can't update Port Config Data Probable Cause Indicates that the PDM system call to setcfg failed. Recommended Action Run the firmwareDownload command to reinstall the firmware.
Recommended Action Run the firmwareDownload command to reinstall the firmware. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING PDM-1012 Message , [PDM-1012], ,, WARNING, , File write failed: Probable Cause Indicates that the PDM process could not write data to the specified file name.
Probable Cause Indicates that a system call failed. Recommended Action Run the firmwareDownload command to reinstall the firmware. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING PDM-1017 Message , [PDM-1017], ,, CRITICAL, , System (): Probable Cause Indicates that a system call failed.
PDM-1020 Message , [PDM-1020], ,, WARNING, , Long path name (/), Skip Probable Cause Indicates that the indicated file path name is too long. The limit is 49 characters. Recommended Action Use short path name for the files to be replicated. Severity WARNING PDM-1021 Message , [PDM-1021], ,, WARNING, , Failed to download area port map Probable Cause Indicates that a system call failed.
Severity INFO PDTR-1002 Message , [PDTR-1002], ,, INFO, , < informational message > Probable Cause This message indicates that information has been written to the panic dump and core dump files and a trap 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.
Probable Cause Indicates that the standby CP is being reset. This message is typically generated by a CP that is in the process of becoming the active CP. Note that in certain circumstances a CP may experience a double reset and reboot twice in a row. A CP can recover automatically even if it has rebooted twice. Recommended Action No action is required.
Severity INFO PS Error Messages PS-1000 Message , [PS-1000], ,, CRITICAL, , Failed to initialize Advanced Performance Monitoring. Probable Cause Indicates that an unexpected software error has occurred in Advanced Performance Monitoring. The Performance Monitor has failed to initialize. Recommended Action The CP should reboot (or fail over) automatically. If it does not, reboot or power cycle the switch to reinitiate the firmware.
Recommended Action Tracing will not be available for Advanced Performance Monitoring, but other functions should function normally. To retry activating tracing, reboot (or fail over) the CP. Severity ERROR PS-1003 Message , [PS-1003], ,, WARNING, , Failed to set end-to-end monitoring mask on ISL ports. Probable Cause Indicates that the restoring configuration has attempted to set the end-to-end monitoring mask on at least one ISL port.
Recommended Action To resume counting, delete some end-to-end monitors sharing the same hardware resource pool. Severity WARNING PSWP Error Messages PSWP-1001 Message , [PSWP-1001], ,, INFO, , Areas for port and port are swapped.
Recommended Action No action is required. Severity INFO PSWP-1004 Message , [PSWP-1004], ,, WARNING, , Port Swap configuration does not match Chassis configuration for switch . Erasing port swap tables... Probable Cause Indicates that the portSwap configuration contradicts the chassis configuration. Recommended Action Redefine the port swap configuration so that it matches the chassis configuration.
Probable Cause Indicates that the RCS feature has been enabled. RCS must be capable on all switches in the fabric to be enabled. If all switches are capable, it is automatically enabled. Recommended Action No action is required. Severity INFO RCS-1003 Message , [RCS-1003], ,, ERROR, , Failed to allocate memory: () Probable Cause Indicates that the specified RCS function failed to allocate memory.
RCS-1005 Message , [RCS-1005], ,, INFO, , State , Application returned 0x. Probable Cause Indicates that a receiving switch is rejecting an RCS phase. Recommended Action If the reject is in ACA phase, wait several minutes and then retry the operation from the sender switch. If the reject is in the SFC phase, check if the application license exists for the local domain and if the application data is compatible.
Probable Cause Indicates that a switch in the fabric does not support the current size of the zone database. The variable displays the maximum size of the zone database this switch can accept. Recommended Action Reduce the zone database size.
Recommended Action To enable RPCD in secure mode, install a valid SSL certificate on the switch. Severity WARNING RPCD-1003 Message , [RPCD-1003], ,, WARNING, , Permission denied accessing certificate file. Secure RPCd is disabled. Probable Cause Indicates that the SSL certificate file configured on the switch could not be accessed because root did not have read access.
Severity WARNING RPCD-1006 Message , [RPCD-1006], ,, WARNING, , Permission denied accessing private key file. Secure RPCd is disabled. Probable Cause Indicates that the private key file configured on the switch could not be accessed because root did not have read access. Recommended Action Change the file system access level for the private key file to have root read-level access.
Severity ERROR RTWR-1002 Message , [RTWR-1002], ,, WARNING, , RTWR 0x, 0x, 0x, 0x, 0x Probable Cause Indicates that the RTWR has exhausted the maximum number of retries sending data to the specified domain.
SCN Error Messages SCN-1001 Message , [SCN-1001], ,, CRITICAL, , SCN queue overflow for process Probable Cause Indicates that an attempt to write an SCN (state change notification) message to a specific queue has failed because the SCN queue for the specified daemon name is full. This might be caused by the daemon hanging or if the system is busy.
switches commit to the new database or none of them update to the new database. This process can fail if one switch in the fabric is busy or in an error state that cannot accept the database. Recommended Action RCS is used when the security database is changed by a command run by security (for example, secPolicySave, secPolicyActivate, or secVersionReset). If the switch is busy, the command might fail the first time only; retry after the first fail.
Severity WARNING SEC-1005 Message , [SEC-1005], ,, INFO, , Primary FCS receives data request from domain Probable Cause Indicates that 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.
Probable Cause Indicates that 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. Severity INFO SEC-1008 Message , [SEC-1008], ,, INFO, , Security violation: Unauthorized host with IP address tries to establish HTTP connection.
Probable Cause Indicates that 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 SSH connection. Severity INFO SEC-1022 Message , [SEC-1022], ,, WARNING, , Failed to PKI objects. Probable Cause Indicates that the security server failed to generate or validate either the public or private key pair or the CSR.
Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur 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 occurence. Recommended Action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state.
SEC-1029 Message , [SEC-1029], ,, ERROR, , Invalid character in . Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur 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 occurence.
Severity WARNING SEC-1032 Message , [SEC-1032], ,, ERROR, , Empty FCS list is not allowed. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur 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 occurence.
Recommended Action Verify your member names, and input the correct information. Severity ERROR SEC-1035 Message , [SEC-1035], ,, ERROR, , Invalid device WWN . Probable Cause Indicates that the specified WWN is invalid. Recommended Action Enter the correct WWN value. Severity ERROR SEC-1036 Message , [SEC-1036], ,, ERROR, , Invalid device name .
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-1038 Message , [SEC-1038], ,, ERROR, , Invalid domain . Probable Cause Indicates that there has been a corruption during the distribution of the security database.
Probable Cause Indicates that the port member is invalid for one of the following reasons: • The value is not a number. • The value is too long. Valid numbers must be between one and three characters long. • The value cannot be parsed due to invalid characters. Recommended Action Use valid syntax when entering port members. Severity ERROR SEC-1042 Message , [SEC-1042], ,, ERROR, , Invalid area member in portlist ().
Probable Cause Indicates that the specified member is a duplicate in the input list. The list can be a policy list or a switch member list. Recommended Action Do not specify any duplicates. Severity ERROR SEC-1045 Message , [SEC-1045], ,, ERROR, , Too many port members. Probable Cause Indicates that there has been a corruption during the distribution of the security database.
SEC-1049 Message , [SEC-1049], ,, ERROR, , Invalid switch name . Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur 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 occurence.
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-1052 Message , [SEC-1052], ,, ERROR, , Invalid input. Probable Cause Indicates that there has been a corruption during the distribution of the security database.
Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur 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 occurence. Recommended Action Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be in the ready state.
SEC-1057 Message , [SEC-1057], ,, ERROR, , No change. Both positions are the same. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur 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 occurence.
SEC-1063 Message , [SEC-1063], ,, ERROR, , Failed to reset statistics. Probable Cause Indicates that either the type or the domains specified are invalid. Recommended Action Enter valid input. Severity ERROR SEC-1064 Message , [SEC-1064], ,, ERROR, , Failed to sign message. Probable Cause Indicates that the PKI objects on the switch are not in a valid state and the signature operation failed.
SEC-1069 Message , [SEC-1069], ,, ERROR, , Security Database is corrupted. Probable Cause Indicates that the security database is corrupted for unknown reasons. Recommended Action Run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR SEC-1071 Message , [SEC-1071], ,, ERROR, , No new data to apply.
SEC-1073 Message , [SEC-1073], ,, ERROR, , No FCS policy in list! Probable Cause Indicates that 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; then run the supportSave command and contact your switch service provider.
Severity ERROR SEC-1076 Message , [SEC-1076], ,, ERROR, , NoNodeWWNZoning option has been changed. Probable Cause Indicates that the NoNodeWWNZoning option has been changed. If the option is turned on, a zone member can be added using node WWNs, but the member will not be able to communicate with others nodes in the zone. Recommended Action Reenable the current zone configuration for the change to take effect.
Severity ERROR SEC-1079 Message , [SEC-1079], ,, ERROR, , Invalid policy name . Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur 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 occurence.
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-1082 Message , [SEC-1082], ,, ERROR, , Failed to create policy. Probable Cause Indicates that the security policy was not created due to faulty imput or low resources.
Recommended Action No action is required. Severity ERROR SEC-1085 Message , [SEC-1085], ,, ERROR, , Failed to create . Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur 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 occurence.
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-1089 Message , [SEC-1089], ,, ERROR, , Policy name not found. Please, use secPolicyCreate.
SEC-1091 Message , [SEC-1091], ,, ERROR, , No policy to remove. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur 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 occurence.
Severity ERROR SEC-1094 Message , [SEC-1094], ,, ERROR, , Policy member not found. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur 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 occurence.
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-1097 Message , [SEC-1097], ,, ERROR, , Cannot find policy set. Probable Cause Indicates that the specified policy could not be found.
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-1100 Message , [SEC-1100], ,, ERROR, , FCS switch present. Command terminated. Probable Cause Indicates that there has been a corruption during the distribution of the security database.
Probable Cause Indicates that the switch failed to download certificate, security database, or policies. This can happen when switch does not get enough resources to complete the operation, fabric has not stabilized, or policy database is an invalid format. Recommended Action Wait for fabric to become stable and then retry the operation. If the policy database is in an illegal format (with configDownload), correct the format and retry the operation.
SEC-1106 Message , [SEC-1106], ,, ERROR, , Failed to sign message data. Probable Cause Indicates that some PKI objects on the switch are not in a valid state, and a signature operation failed. Recommended Action Run the pkiShow command and verify that all PKI objects exist on the switch. If a failure to validate PKI objects occurs, follow the steps for re-creating PKI objects outlined in the Secure Fabric OS User's Guide.
Severity ERROR SEC-1110 Message , [SEC-1110], ,, ERROR, , FCS list must be the first entry in the [Defined Security policies] section. Fail to download defined database. Probable Cause Indicates that a security policy download is attempted with a defined policy that does not have the FCS policy as the first policy. The FCS policy is required to be the first policy in the defined security database.
Severity ERROR SEC-1115 Message , [SEC-1115], ,, ERROR, , No primary FCS to failover. Probable Cause Indicates that during an attempted secFcsFailover, no primary FCS is present in the fabric. 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-1118 Message , [SEC-1118], ,, INFO, , Fail to set SNMP string. Probable Cause Indicates that the SNMP string could not be set. Recommended Action Usually this problem is transient. Retry the command. Severity INFO SEC-1119 Message , [SEC-1119], ,, INFO, , Secure mode has been enabled. Probable Cause Indicates that the secure Fabric OS was enabled by the secModeEnable command.
SEC-1122 Message , [SEC-1122], ,, INFO, , Error code: , . Probable Cause Indicates that one of the switches in the fabric could not communicate with the primary FCS. 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.
SEC-1126 Message , [SEC-1126], ,, INFO, , Secure mode has been disabled. Probable Cause Indicates that 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.
SEC-1136 Message , [SEC-1136], ,, ERROR, , Failed to verify signature . Probable Cause Indicates that the receiving switch fails to validate the security database sending from the primary FCS switch. This message usually indicates that the data package is corrupted, the time stamp on the package is out of range as a result of a replay attack or out-of-sync time service, or the signature verification failed.
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-1139 Message , [SEC-1139], ,, ERROR, , THe RSNMP_POLICY cannot exist without the WSNMP_POLICY.
Probable Cause Indicates one of the following has occurred: • The names for the specified policies have changed. • The passwords have changed for the specified accounts. • The SNMP community strings have been changed. 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.
SEC-1154 Message , [SEC-1154], ,, INFO, , PID change failed: . Probable Cause Indicates that 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 because the new policy database exceeds the maximum size. This message can also be caused when the switch is short of memory. The status values can be either defined, active, or both.
Severity INFO SEC-1157 Message , [SEC-1157], ,, INFO, , PID Change failed: . Probable Cause Indicates that 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 Retry the failed command.
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 INFO SEC-1160 Message , [SEC-1160], ,, INFO, , Duplicate port in port list (). Probable Cause Indicates that there has been a corruption during the distribution of the security database.
Recommended Action Add the switch into the FCS policy list when using the lockdown option to enable security. Severity ERROR SEC-1165 Message , [SEC-1165], ,, ERROR, , Low memory, failed to enable security on all switches. Probable Cause Indicates that the system is low on memory. Recommended Action Wait a few minutes and try the command again.
Recommended Action Verify that the security event was planned. If the security event was planned, retry FCS failover after current failover has completed, if this switch should become primary FCS. If the security event was not planned, take appropriate action as defined by your enterprise security policy. Severity ERROR SEC-1168 Message , [SEC-1168], ,, ERROR, , Primary FCS failover is busy. Please retry later.
SEC-1171 Message , [SEC-1171], ,, ERROR, , Disabled secure mode due to invalid security object. Probable Cause Indicates that the switch is segmented, and secure mode is disabled on the switch because there was no license present or no PKI objects. Recommended Action Run the pkiShow command to check if all PKI objects exist. If they do not exit, run the pkiCreate command to create them for the switch. Run the licenseAdd command to install the required license key.
SEC-1174 Message , [SEC-1174], ,, ERROR, , Failed to set password. Probable Cause Indicates that the FCS or non-FCS password could not be set. Recommended Action 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. When verification is complete, retry the operation.
SEC-1180 Message , [SEC-1180], ,, INFO, , Added account with authorization. Probable Cause Indicates that the specified new account has been created. Recommended Action No action is required. Severity INFO SEC-1181 Message , [SEC-1181], ,, INFO, , Deleted account Probable Cause Indicates that the specified account has been deleted. Recommended Action No action is required.
SEC-1183 Message , [SEC-1183], ,, ERROR, , Policy to binary conversion error: Port is out range. Probable Cause Indicates that a security database conversion has failed because of an invalid value. Recommended Action Retry the command with a valid value. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
SEC-1186 Message , [SEC-1186], ,, INFO, , Radius Configuration. Probable Cause Indicates that the RADIUS configuration was enabled or disabled as the primary AAA mechanism. Recommended Action No action is required. Severity INFO SEC-1187 Message , [SEC-1187], ,, INFO, , Security violation: Unauthorized switch tries to join secure fabric.
access to the fabric, this is a valid violation message and an unauthorized entity is trying to access your fabric. Take appropriate action, as defined by your enterprise security policy. Severity INFO SEC-1189 Message , [SEC-1189], ,, INFO, , Security violation: Unauthorized host with IP address tries to do SNMP write operation. Probable Cause Indicates that an SNMP security violation was reported.
SEC-1191 Message , [SEC-1191], ,, INFO, , Security violation: Unauthorized host with IP address tries to establish HTTP connection. Probable Cause Indicates that an HTTP security violation was reported. The specified unauthorized host attempted to establish an HTTP connection. Recommended Action Check if the host IP address specified in the message can be used to manage the fabric through an HTTP connection.
Severity INFO SEC-1194 Message , [SEC-1194], ,, WARNING, , This switch does not have all the required PKI objects correctly installed. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur 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 occurence.
Recommended Action Reset the default admin and user account names on the switch that reported the warning and retry enabling security. Severity WARNING SEC-1197 Message , [SEC-1197], ,, INFO, , Changed account . Probable Cause Indicates that the specified account has changed. Recommended Action No action is required.
Probable Cause Indicates that a serial connection policy security violation was reported. An attempt was made to access the serial console on the specified switch instance when it is disabled. Recommended Action Check to see if an authorized access attempt is being made on the console. If so, add the switch WWN to the serial policy. If the host is not allowed access to the fabric, this is a valid violation message and an unauthorized entity is trying to access your fabric.
SEC-1202 Message , [SEC-1202], ,, INFO, , Security violation: Unauthorized access from MS device node name , device port name . Probable Cause Indicates that a MS security violation was reported. The unauthorized device specified in the message attempted to establish a connection. Recommended Action Check the MS server policy and verify that the connection is allowed.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR SEC-1253 Message , [SEC-1253], ,, ERROR, , Bad DCC interface state during , state=. Probable Cause Indicates that an internal error has caused the DCC policy update to fail in the provision, commit, or cancel phases. Recommended Action Retry the failed security command.
Severity INFO SEC-1302 Message , [SEC-1302], ,, INFO, , This switch does not have all the required PKI objects correctly installed. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur 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 occurence.
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 INFO SEC-1305 Message , [SEC-1305], ,, INFO, , This switch has no zoning license. Probable Cause Indicates that there has been a corruption during the distribution of the security database.
Probable Cause Indicates that after some servers timed out, the specified RADIUS server responded to a switch request. Recommended Action If the message appears frequently, move the responding server to the top of the RADIUS server configuration list using the aaaConfig command. Severity INFO SEC-1308 Message , [SEC-1308], ,, INFO, , All Radius servers have failed to respond.
Probable Cause Indicates that the security mode of the fabric was either enabled or disabled. 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.
SEC-3004 Message , [SEC-3004], , AUDIT, INFO, , User: , Role: , Event: , Status: , Info: Create policy. Probable Cause Indicates that a new security policy has been created. When you use a wildcard (for example, an asterisk) in creating member for a policy, the audit report displays the wildcard in the event info field. Recommended Action Verify that the security event was planned.
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-3007 Message , [SEC-3007], , AUDIT, INFO, , User: , Role: , Event: , Status: , Info: Delete policy .
Probable Cause Indicates that the pending security transaction is aborted. 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.
SEC-3012 Message , [SEC-3012], , AUDIT, INFO, , User: , Role: , Event: , Status: , Info: Passwd set/reset on domain [] for account(s) . Probable Cause Indicates that the user has reset the password for the specified user accounts. Recommended Action Verify that the security event was planned. If the security event was planned, no action is required.
Severity INFO SEC-3015 Message , [SEC-3015], , AUDIT, INFO, , User: , Role: , Event: , Status: , Info: server to position . Probable Cause Indicates that the specified user has changed the position of the RADIUS server. Recommended Action Verify that the security event was planned. If the security event was planned, no action is required.
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 SNMP Error Messages SNMP-1001 Message , [SNMP-1001], ,, ERROR, , SNMP service is not available . Probable Cause Indicates that the SNMP service could not be started because of the specified Reason.
Recommended Action Retry changing the SNMP community strings from the primary switch. Severity ERROR SNMP-1004 Message , [SNMP-1004], ,, ERROR, , Incorrect SNMP configuration. Probable Cause Indicates that the SNMP configuration is incorrect and the SNMP service will not work correctly. Recommended Action Change the SNMP configuration back to the default.
Recommended Action Check the FTP server and settings. Run the supportFtp command to set the FTP parameters. After the FTP problem is corrected, rerun the supportSave command. Severity WARNING LB Error Messages SULB-1001 Message , [SULB-1001], ,, WARNING, , Firmwaredownload command has started. Probable Cause Indicates that the firmwareDownload command has started.
Probable Cause Indicates the firmwareCommit or firmwareRestore command has started to update the secondary partition. Recommended Action No action is required. Run the firmwareDownloadStatus command for more information. Severity INFO SULB-1005 Message , [SULB-1005], ,, INFO, , Current Active CP is preparing to failover. Probable Cause Indicates that the forced failover was successful and the standby CP is now the active CP.
Probable Cause Indicates that the standby CP will reboot. Recommended Action No action is required. The firmwareDownload command is progressing as expected. Run the firmwareDownloadStatus command for more information. Severity INFO SULB-1008 Message , [SULB-1008], ,, INFO, , Standby CP booted successfully with new firmware. Probable Cause Indicates that the standby CP has rebooted successfully. Recommended Action No action is required.
Table 5 lists the upgrade message and the associated code for that message. Table 5 Upgrade messages and code values Upgrade messages Code "Image is up-to-date. No need to download." 0xF "Boot environment variable is inconsistent." 0x10 "Bootenv OSRootPartition is inconsistent." 0x11 "Can't access package list (.plist) file." 0x12 "RPM database is inconsistent." 0x13 "Ran out of memory." 0x14 "Firmwaredownload failed due to out of disk space or timeout.
Table 5 Upgrade messages and code values (continued) Upgrade messages 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.
Table 5 Upgrade messages and code values (continued) Upgrade messages Code "Firmwarecommit has started on Standby CP." 0x77 "Firmwarecommit has completed successfully on Standby CP." 0x78 "Standby CP booted up with new firmware." 0x79 "Standby CP failed to boot up with new firmware." 0x7a "Firmwarecommit has started on both Active and Standby CPs." 0x7b "Firmwarecommit has completed successfully on Active CP." 0x7c "Firmwarecommit failed on Active CP.
Table 6 lists the upgrade state and the associated code value for that state. This information is transient within the Boot ROM environment and is provided here only for assisting support personnel in the debug process.
Recommended Action Run the firmwareCommit command. If this message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
Probable Cause Indicates that the slot state has been detected as inconsistent during failover or recovery. Recommended Action On a Core Switch 2/64, SAN Director 2/128, or 4/256 SAN Director switch, run the slotPowerOff and then the slotPowerOn command. On a 4/8 SAN Switch, 4/16 SAN Switch, SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch 2/32, or SAN Switch 4/32 switch, reboot or power cycle the switch.
SYSC Error Messages SYSC-1001 Message , [SYSC-1001], ,, CRITICAL, , Failed to run : Probable Cause Indicates that during the boot sequence, one of the programs would not run on the system. Recommended Action If the message is reported during a reboot after new firmware has been loaded, try reloading the firmware using the firmwareDownload command.
Probable Cause Indicates that during system startup the option configuration file corresponding to the chassis config option read could not be found. This indicates that the option is not supported on this platform running this version of the command. It could also indicate that the current option number could not be read form the chassis option storage device (the WWN card). This message only occurs on the SAN Director 2/128 and 4/256 SAN Director.
Severity INFO SYSM-1003 Message , [SYSM-1003], ,, INFO, , , Switch: Probable Cause Indicates that the user executed the switchStart or switchReboot command. This indicates that all services are brought back up after a temporary shutdown of that logical switch. Recommended Action No action is required if the switchStart command was executed intentionally.
• PANICDUMP generated by panic dump • WATCHDOG EXPIRED generated by hardware watchdog expiration • MANUAL 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 Run supportFtp and traceFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
TRCE-1004 Message , [TRCE-1004], ,, WARNING, , Trace dump< optional slot indicating on which slot the dump occurs > was not transferred because trace auto-FTP disabled. Probable Cause Indicates that trace dump files have been created on the switch or the indicated slot but are not automatically transferred from the switch because auto-FTP is disabled. Recommended Action Run supportFtp to set up and enable automatic FTP transfers.
Recommended Action No action is required. Severity INFO TRCE-1007 Message , [TRCE-1007], ,, ERROR, , Notification of this CP has failed. Parameters temporarily out of synch with other CP. Probable Cause Indicates that the active CP is unable to alert the standby CP of a change in trace status. This message is only applicable to the Core Switch 2/64, SAN Director 2/128, and 4/256 SAN Director. Recommended Action This message is often transitory.
Probable Cause Indicates that the standby CP is unable to communicate trace information to active CP. This message is only applicable to the Core Switch 2/64, SAN Director 2/128, and 4/256 SAN Director. Recommended Action Run the haShow command to verify that the current CP is standby and the active CP is active. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command on both CPs and contact your switch service provider.
TRCK Error Messages TRCK-1001 Message , [TRCK-1001], ,, INFO, , Successful login by user . Probable Cause Indicates that the track change feature recorded a successful login. Recommended Action No action is required. Severity INFO TRCK-1002 Message , [TRCK-1002], ,, INFO, , Unsuccessful login by user . Probable Cause Indicates that the track change feature recorded a failed login.
TRCK-1004 Message , [TRCK-1004], ,, INFO, , Config file change from task: Probable Cause Indicates that the track change feature recorded a configuration change for the switch. 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.
TS Error Messages TS-1001 Message , [TS-1001], ,, WARNING, , NTP Query failed: Probable Cause Indicates that 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 might 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.
TS-1006 Message , [TS-1006], ,, INFO, , Probable Cause Indicates that a time service event is occurring or has failed. The message might be one of the following: • Init failed. Time Service exiting Probable Cause: Initialization error, Time Server exits.
Probable Cause Indicates that 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 Run the switchDisable command and then the switchEnable command to reset the routing database. Run the uRouteShow command to display the new routing tables.
USWD Error Messages USWD-1006 Message , [USWD-1006], ,, WARNING, , uSWD: Probable Cause Indicates a warning state in the system. This is an internal use only message. Recommended Action No action is required. Severity WARNING WEBD Error Messages WEBD-1001 Message , [WEBD-1001], ,, WARNING, , Missing or Invalid Certificate file -- HTTPS is configured to be enabled but could not be started.
Severity WARNING WEBD-1003 Message , [WEBD-1003], ,, INFO, , HTTP/HTTPS interface disabled Probable Cause Indicates that the HTTP/HTTPS interface is disabled. This is logged when HTTP/HTTPS is disabled through the configure command. Recommended Action Run the configure command to enable HTTP/HTTPS. For more information on the configure command, refer to the HP StorageWorks Fabric OS 5.x command reference guide.
WEBD-1006 Message , [WEBD-1006], ,, INFO, , HTTP server restarted due to logfile truncation Probable Cause Indicates that the size of HTTP logfile exceeded the maximum limit. Recommended Action No action is required.
ZONE Error Messages ZONE-1002 Message , [ZONE-1002], ,, WARNING, , WWN zoneTypeCheck or zoneGroupCheck warning() at port() Probable Cause Indicates that a zone filter or zone group check failure occurred. The frame filter logic reported a failure when creating or adding zone groups during PLOGI trap processing. This messages usually indicates problems when adding CAM entries before the filter setup.
is, using one method or the other to define all objects in the zoning database. If the devices on the port are defined by a mixture of port IDs and WWNs, the zone enforcement is session based. If the S_ID list of the hardware-enforced zoning overflows (over the S_ID limit), the hardware zone enforcement changes to session-based zoning. Recommended Action No action is required.
ZONE-1007 Message , [ZONE-1007], ,, INFO, , Ioctl() in () at port () returns code () and reason string () Probable Cause Indicates that 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.
Severity WARNING ZONE-1012 Message , [ZONE-1012], ,, WARNING, , WARNING - All ports are offline. Probable Cause Indicates that all the ports in a zone are offline. Recommended Action Check the device connection. Severity WARNING ZONE-1013 Message , [ZONE-1013], ,, WARNING, , Quick Loop not supported. Probable Cause Indicates that the QuickLoop feature is not supported in the current code release.
ZONE-1015 Message , [ZONE-1015], ,, WARNING, , Not owner of the current transaction Probable Cause Indicates that a zoning change operation is not allowed because the zoning transaction is opened by another task. Indicates concurrent modification of the zone database by multiple administers. Recommended Action Wait until the previous transaction is completed. Verify that only one administrator is working with the zone database at a time.
QuickLoop zones are not supported in Fabric OS v4.x. Recommended Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR ZONE-1019 Message , [ZONE-1019], ,, ERROR, , Transaction Commit failed.
ZONE-1023 Message , [ZONE-1023], ,, INFO, , Switch connected to port () is busy. Retry zone merge Probable Cause Indicates that the switch is retrying the merge operation. This usually occurs if the switch on the other side of the port is busy. Recommended Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
ZONE-1027 Message , [ZONE-1027], ,, ERROR, , Zoning transaction aborted - Probable Cause Indicates that the zoning transaction was aborted due to a variety of potential errors. The error reason variable can be one of the following: • 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.
ZONE-1029 Message , [ZONE-1029], ,, WARNING, , Restoring zone cfg from flash failed - bad config saved to [] Probable Cause Indicates that the zone configuration restored from the flash was faulty. Recommended Action This error will save the faulty zone configuration in the zoned core file directory. Run the saveCore command to save the file.
Severity ERROR ZONE-1032 Message , [ZONE-1032], ,, ERROR, , Domain Max Zone DB size Probable Cause Indicates that the specified domain does not have enough memory for the the zone database being commited. Recommended Action Reduce the size of the zone database and retry the operation.
ZONE-1035 Message , [ZONE-1035], ,, ERROR, , Unable to rename to : error message Probable Cause Indicates that the Fabric OS cannot rename the zone configuration file. Typically the zone configuration is too large for the memory available on the switch. Recommended Action Reduce the size of the zone database and retry the operation.
ZONE-1038 Message , [ZONE-1038], ,, ERROR, , Unable to allocate memory for : error message Probable Cause Indicates that the Fabric OS cannot allocate enough memory for the zone configuration file. Typically the zone configuration is too large for the memory available on the switch. Recommended Action Reduce the size of the zone database and retry the operation.
ZONE-1041 Message , [ZONE-1041], ,, WARNING, ,Unstable link detected during merge at port . Probable Cause Indicates a possible unstable link, or faulty cable. Recommended Action Check the SFP and cable at the specified port and verify that they are not faulty. Replace the SFP and cable as neccessary.
A zone object may be an alias, zone member, zone or zone configuration. The string "..." appears at the end of the zone object member list if the list was truncated in the message. 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.
ZONE-3005 Message , [ZONE-3005], , AUDIT, INFO, , User: , Role: , Event: , Status: , Info: All zone information cleared from transaction buffer. Probable Cause Indicates that all zone information has been cleared from the transaction buffer. Recommended Action Verify that the event was planned. If the event was planned, no action is required.
Severity INFO ZONE-3008 Message , [ZONE-3008], , AUDIT, INFO, , User: , Role: , Event: , Status: , Info: Current zone configuration saved to flash. Probable Cause Indicates that the current zone configuration has been saved to flash. Recommended Action Verify that the event was planned. If the event was planned, no action is required.
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-3011 Message , [ZONE-3011], , AUDIT, INFO, , User: , Role: , Event: , Status: , Info: Zone object \"\" expunged. Probable Cause Indicates that a zone object has been expunged.
Error messages
Index A C audience 77 audit logging 82 AUTH-1001 95 AUTH-1003 95 AUTH-1004 96 AUTH-1005 96 AUTH-1006 96 AUTH-1007 97 AUTH-1008 97 AUTH-1010 97 AUTH-1011 98 AUTH-1012 98 AUTH-1013 99 AUTH-1014 99 AUTH-1017 99 AUTH-1018 100 AUTH-1020 100 AUTH-1022 101 AUTH-1023 101 AUTH-1025 102 AUTH-1027 102 AUTH-1028 103 AUTH-1029 103 AUTH-1030 103 AUTH-1031 104 AUTH-1032 104 AUTH-1033 105 AUTH-1034 105 AUTH-1035 105 AUTH-1036 106 AUTH-1037 106 AUTH-1038 107 authorized reseller, HP 79 clearing the system message log 88 c
F FABR-1002 140 FABR-1003 141 FABR-1004 141 FABR-1005 142 FABR-1006 142 FABR-1007 142 FABR-1008 143 FABR-1009 143 FABR-1010 144 FABR-1011 144 FABR-1012 144 FABR-1013 145 FABR-1014 145 FABR-1015 145 FABR-1016 146 FABR-1017 146 FABR-1018 146 FABR-1019 147 FABR-1020 147 FABR-1021 148 FABR-1022 148 FABR-1023 149 FABR-1024 149 FABR-1029 149 FABR-1030 150 FABS-1002 150 FABS-1004 151 FABS-1005 151 FABS-1006 152 FABS-1007 152 FABS-1008 153 FABS-1009 153 FABS-1010 153 FABS-1011 154 FABS-1012 154 FABS-1013 154 FABS-1
FW-1134 FW-1135 FW-1136 FW-1137 FW-1138 FW-1139 FW-1140 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 FW-1244 FW-1245 FW-1246 FW-1247 FW-1248 FW-1249 FW-1250 FW-1251 191 192 192 192 193 193 194 194 194 195
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 FW-1442 FW-1443 FW-1444 237 237 238 238 239 239 239 240 240 241 241 241 242 242 242 243 243 243 244 244
KTRC-1004 280 L LOG-1000 281 LOG-1001 281 LOG-1002 281 looking up a system message 88 LSDB-1001 282 LSDB-1002 282 LSDB-1003 282 LSDB-1004 283 M message severity levels 81 MFIC-1001 283 MFIC-1002 284 MFIC-1003 284 MPTH-1001 284 MPTH-1002 285 MPTH-1003 285 MQ-1004 285 MS-1001 286 MS-1002 286 MS-1003 287 MS-1004 288 MS-1005 288 MS-1006 289 MS-1008 289 MS-1021 289 N NBFS-1001 290 NBFS-1002 290 NBFS-1003 291 NS-1001 291 NS-1002 292 NS-1003 292 NS-1004 292 O overview of the system messages 81 P panic dump an
SEC-1028 317 SEC-1029 318 SEC-1030 318 SEC-1031 318 SEC-1032 319 SEC-1033 319 SEC-1034 319 SEC-1035 320 SEC-1036 320 SEC-1037 320 SEC-1038 321 SEC-1040 321 SEC-1041 321 SEC-1042 322 SEC-1043 322 SEC-1044 322 SEC-1045 323 SEC-1046 323 SEC-1049 324 SEC-1050 324 SEC-1051 324 SEC-1052 325 SEC-1053 325 SEC-1054 325 SEC-1055 326 SEC-1056 326 SEC-1057 327 SEC-1059 327 SEC-1062 327 SEC-1063 328 SEC-1064 328 SEC-1065 328 SEC-1069 329 SEC-1071 329 SEC-1072 329 SEC-1073 330 SEC-1074 330 SEC-1075 330 SEC-1076 331 SEC-1
SEC-1186 359 SEC-1187 359 SEC-1188 359 SEC-1189 360 SEC-1190 360 SEC-1191 361 SEC-1192 361 SEC-1193 361 SEC-1194 362 SEC-1195 362 SEC-1196 362 SEC-1197 363 SEC-1198 363 SEC-1199 363 SEC-1200 364 SEC-1201 364 SEC-1202 365 SEC-1250 365 SEC-1251 365 SEC-1253 366 SEC-1300 366 SEC-1301 366 SEC-1302 367 SEC-1303 367 SEC-1304 367 SEC-1305 368 SEC-1306 368 SEC-1307 368 SEC-1308 369 SEC-3001 369 SEC-3002 370 SEC-3003 370 SEC-3004 371 SEC-3005 371 SEC-3006 371 SEC-3007 372 SEC-3008 372 SEC-3009 372 SEC-3010 373 SEC-3
W warning rack stability 79 web sites HP storage 79 HP Subscriber’s choice 79 WEBD-1001 399 WEBD-1002 399 WEBD-1003 400 WEBD-1004 400 WEBD-1005 400 WEBD-1006 401 WEBD-1007 401 Z ZOLB-1001 401 ZONE-1002 402 ZONE-1003 402 ZONE-1004 402 ZONE-1005 403 ZONE-1006 403 ZONE-1007 404 ZONE-1008 404 ZONE-1010 404 ZONE-1012 405 ZONE-1013 405 ZONE-1014 405 ZONE-1015 406 ZONE-1017 406 ZONE-1018 406 ZONE-1019 407 ZONE-1022 407 ZONE-1023 408 ZONE-1024 408 ZONE-1026 408 ZONE-1027 409 ZONE-1028 409 ZONE-1029 410 ZONE-1030 4