NX Os

Cisco MDS 9000 Family and Nexus 7000
Series NX-OS System Messages Reference

August 2012
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-26589-01

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this
URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Cisco MDS 9000 Family and Nexus 7000 Series NX-OS System Messages Reference
© 2012 Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface xvii
Audience xvii
Organization xvii
Document Conventions xviii
Documentation Feedback xviii
Obtaining Documentation and Submitting a Service Request xix
CHAPTER 1 Introduction to System Messages for Cisco NX-OS 1-1
System Log Message Format 1-1

Syslog Format On a Resident Switch 1-1
Syslog Format On a Remote-Logging Server 1-3
Capturing System Messages and History 1-5

Saving the System Messages Log 1-5
Logging System Messages to a Syslog Server 1-5
CHAPTER 2 System Messages and Recovery Procedures for the Cisco MDS 9000 and Nexus 7000 Family 2-1
AAA Messages 2-1
AAA-1 2-1
AAA-2 2-1
AAA-3 2-2
AAA-6 2-2
AAM Messages 2-2
AAM-2 2-2
AAM-3 2-2
ACLLOG Messages 2-3
ACLLOG-4 2-3
ACLLOG-6 2-3
ACLMGR Messages 2-3
ACLMGR-2 2-4
ACLMGR-3 2-5
ACLMGR-4 2-6
ACLMGR-6 2-7
ACLQOS Messages 2-8
ACLQOS-SLOT#-2 2-8
Cisco MDS 9000 Family and Nexus 7000 Series NX-OS System Messages Reference
OL-26589-01 i
Contents
S e n d d o c u m e n t c o m m e n t s t o n ex u s 7 k - f e e d b a ck - d o c @ c i s c o . c o m
ACLQOS-SLOT#-3 2-8
ACLQOS-SLOT#-4 2-9
ACLQOS-SLOT#-5 2-10
ACLTCAM Messages 2-11
ACLTCAM-2 2-11
ACLTCAM-3 2-14
ACLTCAM-4 2-16
ACLTCAM-6 2-17
ACL Messages 2-17
ACL-2 2-17
ACL-3 2-19
ACL-4 2-19
ACL-5 2-20
ACL-6 2-20
AMM Messages 2-21
AMM-SLOT#-0 2-21
AMM-SLOT#-2 2-22
AMM-SLOT#-6 2-22
ASCII-CFG Messages 2-22
ASCII-CFG-2 2-22
ASCII-CFG-3 2-24
ASCII-CFG-6 2-24
ASSOC MGR Messages 2-25
ASSOC MGR-0 2-25
ASSOC MGR-1 2-25
ASSOC MGR-2 2-26
ASSOC MGR-3 2-26
ASSOC MGR-4 2-26
ASSOC MGR-5 2-26
ASSOC MGR-6 2-26
ASSOC MGR-7 2-28
BFDC Messages 2-28
BFDC-SLOT#-2 2-28
BFD Messages 2-28
BFD-3 2-28
BFD-4 2-29
BFD-5 2-29
BFD-6 2-31
BIOS DAEMON Messages 2-31
BIOS DAEMON-2 2-31
ii OL-26589-01
Contents
BIOS DAEMON-5 2-32

BIOS DAEMON-SLOT#-2 2-32
BIOS DAEMON-SLOT#-5 2-33
BOOTUP TEST Messages 2-33
BOOTUP TEST-2 2-33
BOOTVAR Messages 2-33
BOOTVAR-2 2-34
BOOTVAR-3 2-34
BOOTVAR-5 2-35
BOOTVAR-6 2-37
CALLHOME Messages 2-37
CALLHOME-2 2-37
CALLHOME-3 2-38
CALLHOME-6 2-39
CDP Messages 2-39
CDP-2 2-39
CDP-3 2-39
CDP-4 2-40
CDP-5 2-41
CDP-6 2-41
CERT_ENROLL Messages 2-42
CERT_ENROLL-2 2-42
CERT_ENROLL-3 2-43
CERT_ENROLL-6 2-43
CFS Messages 2-43
CFS-2 2-43
CFS-3 2-45
CFS-4 2-47
CFS-6 2-47
CIMSRVPROV Messages 2-49
CIMSRVPROV-2 2-49
CIMSRVPROV-3 2-50
CIMSRVPROV-6 2-51
CLIS Messages 2-51
CLIS-5 2-51
CLK_MGR Messages 2-51
CLK_MGR-2 2-51
CLK_MGR-5 2-52
CLK_MGR-6 2-52
CLOUD Messages 2-52
OL-26589-01 iii
Contents
CLOUD-2 2-52
CLOUD-3 2-52
CLOUD-6 2-53
CLP_MAC Messages 2-53
CLP_MAC-6 2-53
CLUSTER Messages 2-54
CLUSTER-2 2-54
CMOND Messages 2-54
CMOND-2 2-54
CMPPROXY Messages 2-54
CMPPROXY-2 2-55
CMPPROXY-5 2-55
CMPPROXY-6 2-56
COPP Messages 2-56
COPP-1 2-56
COPP-2 2-56
COPP-3 2-57
COPP-4 2-58
COPP-5 2-58
COPP-6 2-58
COPP-7 2-59
CREDITMON Messages 2-59
CREDITMON-SLOT#-2 2-59
CTS Messages 2-60
CTS-2 2-60
CTS-3 2-63
CTS-5 2-63
CTS-6 2-63
DCEFIB Messages 2-65
DCEFIB-SLOT#-0 2-65
DCEFIB-SLOT#-2 2-66
DCEFIB-SLOT#-6 2-66
DEBUGPROXY Messages 2-67
DEBUGPROXY-6 2-67
DEVICE-ALIAS Messages 2-67
DEVICE-ALIAS-2 2-67
DEVICE-ALIAS-3 2-68
DEVICE-ALIAS-6 2-71
DEVICE_TEST Messages 2-73
DEVICE_TEST-2 2-73
iv OL-26589-01
Contents
DEVICE_TEST-3 2-76
DEVICE_TEST-4 2-76
DEVICE_TEST-5 2-77
DEVICE_TEST-6 2-77
DEV_LOG Messages 2-77
DEV_LOG-3 2-77
DEV_LOG-SLOT#-4 2-78
DFTM Messages 2-78
DFTM-SLOT#-2 2-78
DFTM-SLOT#-3 2-79
DHCP_SNOOP Messages 2-80
DHCP_SNOOP-2 2-81
DHCP_SNOOP-3 2-81
DHCP_SNOOP-4 2-83
DHCP_SNOOP-5 2-85
DHCP_SNOOP-6 2-86
DIAGCLIENT Messages 2-87
DIAGCLIENT-2 2-88
DIAGCLIENT-3 2-88
DIAGCLIENT-4 2-88
DIAGCLIENT-5 2-89
DIAGCLIENT-7 2-90
DIAGMGR Messages 2-90
DIAGMGR-2 2-90
DIAGMGR-3 2-91
DIAGMGR-4 2-91
DIAGMGR-5 2-92
DIAGMGR-6 2-93
DIAG_PORT_LB Messages 2-93
DIAG_PORT_LB-2 2-94
DIAG_PORT_LB-3 2-95
DIAG_PORT_LB-4 2-98
DIAG_PORT_LB-5 2-98
DMM Messages 2-99
DMM-SLOT#-5 2-99
DOT1X Messages 2-101
DOT1X-2 2-101
DOT1X-3 2-101
DOT1X-4 2-102
DOT1X-5 2-103
OL-26589-01 v
Contents
DOT1X-6 2-105
DPP_DEBUG Messages 2-105
DPP_DEBUG-2 2-105
DPVM Messages 2-105
DPVM-2 2-105
DPVM-3 2-106
DPVM-4 2-106
DPVM-6 2-107
DSTATS Messages 2-107
DSTATS-2 2-107
DSTATS-3 2-107
ELTMC Messages 2-109
ELTMC-SLOT#-2 2-109
ELTM Messages 2-112
ELTM-2 2-112
ELTM-3 2-113
ELTM-5 2-113
ELTM-6 2-113
EOU Messages 2-113
EOU-2 2-113
EOU-5 2-114
EOU-6 2-114
EOU-7 2-116
EPLD_UPGRADE Messages 2-116
EPLD_UPGRADE-2 2-116
EPP Messages 2-116
EPP-5 2-117
ETH-PORT-SEC Messages 2-117
ETH-PORT-SEC-3 2-117
ETH-PORT-SEC-5 2-118
ETHPORT Messages 2-119
ETHPORT-2 2-119
ETHPORT-3 2-120
ETHPORT-4 2-122
ETHPORT-5 2-122
ETH_PORT_CHANNEL Messages 2-133
ETH_PORT_CHANNEL-1 2-133
vi OL-26589-01
Contents
EUREKA_USD Messages 2-141
EUREKA_USD-3 2-141
EVMC Messages 2-141
EVMC-3 2-141
EVMC-4 2-141
EVMC-5 2-142
EVMS Messages 2-142
EVMS-2 2-142
EVMS-4 2-143
EVMS-6 2-143
EXCEPTIONLOG Messages 2-143
EXCEPTIONLOG-SLOT#-2 2-143
FABRICPATH Messages 2-143
FABRICPATH-2 2-143
FABRICPATH-4 2-144
FABRICPATH-6 2-144
FC-TUNNEL Messages 2-146
FC-TUNNEL-3 2-146
FC-TUNNEL-5 2-148
FCC_LC Messages 2-148
FCC_LC-2 2-148
FCC_LC-5 2-149
FCC_LC-6 2-149
FCC Messages 2-149
FCC-2 2-150
FCC-5 2-150
FCC-6 2-151
FCDDH Messages 2-151
FCDDH-SLOT#-3 2-151
FCDDH-SLOT#-4 2-151
FCDDH-SLOT#-5 2-151
FCDD Messages 2-152
FCDD-SLOT#-3 2-152
FCDD-SLOT#-4 2-152
FCDD-SLOT#-5 2-152
FCDD-SLOT#-7 2-153
FCDOMAIN Messages 2-153
OL-26589-01 vii
Contents
FCDOMAIN-2 2-153
FCDOMAIN-3 2-156
FCDOMAIN-4 2-159
FCDOMAIN-5 2-160
FCDOMAIN-6 2-161
FCDOMAIN-7 2-167
FCD Messages 2-169
FCD-7 2-169
FCFWD Messages 2-169
FCFWD-3 2-169
FCFWD-4 2-169
FCFWD-6 2-170
FCNS Messages 2-170
FCNS-2 2-170
FCNS-3 2-171
FCNS-4 2-172
FCNS-6 2-172
FCOE_MGR Messages 2-172
FCOE_MGR-2 2-172
FCOE_MGR-5 2-173
FCSP-MGR Messages 2-174
FCSP-MGR-2 2-174
FCS Messages 2-176
FCS-2 2-176
FCS-3 2-177
FCS-5 2-178
FCS-6 2-179
FDMI Messages 2-179
FDMI-2 2-179
FDMI-3 2-180
FDMI-4 2-181
FDMI-6 2-181
FEATURE-MGR Messages 2-182
FEATURE-MGR-2 2-182
FEATURE-MGR-6 2-185
FEX Messages 2-185
FEX-2 2-185
FEX-5 2-186
FICON Messages 2-187
FICON-2 2-187
viii OL-26589-01
Contents
FICON-3 2-188
FICON-5 2-189
FICON-6 2-189
FLOGI Messages 2-190
FLOGI-1 2-190
FLOGI-2 2-191
FLOGI-4 2-191
FLOGI-5 2-191
FS-DAEMON Messages 2-192
FS-DAEMON-2 2-192
FS-DAEMON-6 2-193
FSCM Messages 2-193
FSCM-2 2-193
FSPF Messages 2-194
FSPF-2 2-194
FSPF-2 2-194
FSPF-4 2-196
FSPF-5 2-197
FSPF-6 2-198
FSPF-7 2-199
GLBP Messages 2-199
GLBP-2 2-199
GLBP-3 2-199
GLBP-4 2-201
GLBP-5 2-203
HSRP_ENGINE Messages 2-205
HSRP_ENGINE-3 2-205
HSRP_ENGINE-4 2-206
HSRP_ENGINE-5 2-207
HSRP_ENGINE-6 2-209
IKE Messages 2-209
IKE-3 2-209
IKE-4 2-211
IKE-6 2-211
ILC-SPAN Messages 2-211
ILC-SPAN-3 2-212
ILC_HELPER Messages 2-212
ILC_HELPER-2 2-212
ILC_HELPER-3 2-212
ILC_HELPER-6 2-212
OL-26589-01 ix
Contents
IMAGE_DNLD Messages 2-213

IMAGE_DNLD-SLOT#-2 2-213
IMAGE_UPGRADE Messages 2-214
IMAGE_UPGRADE-SLOT#-2 2-214
IMAGE_UPGRADE-SLOT#-4 2-215
IM Messages 2-215
IM-3 2-215
IM-5 2-216
INTERFACE_VLAN Messages 2-216
INTERFACE_VLAN-4 2-216
INTERFACE_VLAN-5 2-217
IOA_LC Messages 2-219
IOA_LC-5 2-219
IPACL Messages 2-219
IPACL-0 2-219
IPACL-1 2-220
IPACL-2 2-220
IPACL-3 2-220
IPACL-4 2-220
IPACL-5 2-220
IPACL-6 2-221
IPFC Messages 2-221
IPFC-2 2-221
IPFC-3 2-221
IPFC-5 2-222
IPFC-6 2-222
IPQOSMGR Messages 2-222
IPQOSMGR-2 2-222
IPQOSMGR-3 2-223
IPQOSMGR-4 2-224
IPQOSMGR-6 2-225
IPSEC Messages 2-225
IPSEC-2 2-225
IPSEC-3 2-225
IPSEC-5 2-226
IPS_SB_MGR Messages 2-227
IPS_SB_MGR-SLOT#-2 2-228
x OL-26589-01
Contents
IPS Messages 2-229
IPS-2 2-230
IPS-3 2-230
IPS-4 2-235
IPS-5 2-236
IPS-6 2-245
IPS-7 2-245
IPV6 Messages 2-246
IPV6-2 2-246
IPV6-3 2-246
IPV6-4 2-247
IPV6-6 2-247
IP Messages 2-248
IP-1 2-248
IP-2 2-248
IP-3 2-248
IP-4 2-249
IP-6 2-249
ISAPI Messages 2-250
ISAPI-SLOT#-0 2-250
ISAPI-SLOT#-1 2-251
ISAPI-SLOT#-2 2-251
ISAPI-SLOT#-3 2-252
ISAPI-SLOT#-4 2-253
ISAPI-SLOT#-5 2-253
ISAPI-SLOT#-6 2-254
ISAPI-SLOT#-7 2-255
ISCM Messages 2-256
ISCM-2 2-256
ISCM-3 2-256
ISCM-4 2-257
ISCM-5 2-258
ISNS Messages 2-258
ISNS-2 2-258
IVR Messages 2-258
IVR-2 2-259
IVR-3 2-262
IVR-4 2-270
OL-26589-01 xi
Contents
IVR-5 2-271
IVR-6 2-274
IVR-7 2-275
L2FMC Messages 2-275
L2FMC-SLOT#-0 2-276
L2FMC-SLOT#-2 2-276
L2FMC-SLOT#-5 2-276
L2FMC-SLOT#-6 2-277
L2FM Messages 2-278
L2FM-0 2-278
L2FM-1 2-278
L2FM-2 2-280
L2FM-4 2-280
L2FM-5 2-281
L2FM-6 2-281
L2MCAST Messages 2-281
L2MCAST-SLOT#-0 2-281
L3VM Messages 2-283
L3VM-5 2-284
LACP Messages 2-284
LACP-3 2-284
LACP-5 2-285
LC-FCFWD Messages 2-287
LC-FCFWD-3 2-287
LC-SPAN Messages 2-287
LC-SPAN-3 2-287
LC_CFG Messages 2-287
LC_CFG-SLOT#-2 2-287
LC_PORT_CHANNEL Messages 2-288
LC_PORT_CHANNEL-SLOT#-0 2-288
LC_PORT_CHANNEL-SLOT#-3 2-288
LC_PORT_MGR Messages 2-288
LC_PORT_MGR-SLOT#-2 2-289
LC_RDL Messages 2-289
LC_RDL-3 2-289
LC_RDL-6 2-290
LDAP Messages 2-290
xii OL-26589-01
Contents
LDAP-2 2-291
LDAP-3 2-291
LDAP-5 2-291
LDAP-6 2-291
LDP Messages 2-292
LDP-5 2-292
LIBBASE_SVC Messages 2-292
LIBBASE_SVC-2 2-292
LIBBASE_SVC-4 2-292
LIBBASE_SVC-5 2-293
LIBGD Messages 2-293
LIBGD-2 2-293
LIBGD-3 2-294
LIBGD-5 2-294
LIBGD-6 2-294
LICMGR Messages 2-295
LICMGR-0 2-295
LICMGR-1 2-295
LICMGR-2 2-296
LICMGR-3 2-297
LICMGR-4 2-298
LICMGR-6 2-298
LLDP Messages 2-299
LLDP-3 2-299
LLDP-5 2-300
LLDP-6 2-300
MAC Messages 2-300
MAC-SLOT#-2 2-300
MCAST Messages 2-300
MCAST-2 2-301
MCAST-4 2-301
MCAST-5 2-301
MCECTEST Messages 2-301
MCECTEST-3 2-301
MCECTEST-5 2-302
MCECTEST-6 2-302
MCM Messages 2-302
MCM-2 2-303
MCM-5 2-303
MCM-6 2-303
OL-26589-01 xiii
Contents
MFDM Messages 2-304

MFDM-2 2-304
MODULE Messages 2-305
MODULE-2 2-305
MODULE-3 2-309
MODULE-4 2-310
MODULE-5 2-310
MODULE-6 2-312
MONITOR Messages 2-312
MONITOR-5 2-312
NFM Messages 2-313
NFM-2 2-313
NFM-3 2-314
NFM-4 2-315
NFM-5 2-316
NFM-6 2-316
NFM-7 2-317
NFP Messages 2-317
NFP-SLOT#-2 2-318
NFP-SLOT#-5 2-319
NPC Messages 2-319
NPC-SLOT#-3 2-319
NPC-SLOT#-4 2-319
NPC-SLOT#-5 2-319
NPV Messages 2-320
NPV-2 2-320
NPV-3 2-321
NPV-4 2-324
NPV-5 2-324
NPV-6 2-325
NPV-7 2-328
NTP Messages 2-329
NTP-2 2-329
NTP-3 2-329
NTP-6 2-330
NVP Messages 2-330
NVP-6 2-330
NVP-SLOT#-2 2-331
OC_USD Messages 2-331
OC_USD-2 2-331
xiv OL-26589-01
Contents
ORI_FWD Messages 2-331

ORI_FWD-2 2-331
ORI_FWD-6 2-332
ORI_MAC Messages 2-332
ORI_MAC-2 2-332
ORI_MAC-6 2-332
OTM Messages 2-332
OTM-2 2-332
OTM-3 2-333
OTM-5 2-333
OTM-6 2-333
PHY_USD Messages 2-334
PHY_USD-SLOT#-4 2-334
PIXM Messages 2-334
PIXM-2 2-334
PIXM-3 2-335
PIXM-4 2-335
PIXM-7 2-335
PLATFORM Messages 2-335
PLATFORM-0 2-335
PLATFORM-1 2-338
PLATFORM-2 2-339
PLATFORM-3 2-351
PLATFORM-4 2-353
PLATFORM-5 2-353
PLATFORM-6 2-355
PLATFORM-7 2-355
PLOG_SUP Messages 2-356
PLOG_SUP-4 2-356
PLOG Messages 2-356
PLOG-4 2-356
PONG Messages 2-356
PONG-5 2-356
PORT-CHANNEL Messages 2-357
PORT-CHANNEL-1 2-357
OL-26589-01 xv
Contents
PORT-PROFILE Messages 2-362
PORT-PROFILE-2 2-362
PORT-RESOURCES Messages 2-365
PORT-RESOURCES-3 2-365
PORT-RESOURCES-5 2-366
PORT-SECURITY Messages 2-366
PORT-SECURITY-2 2-366
PORT Messages 2-369
PORT-2 2-369
PORT-3 2-369
PORT-4 2-370
PORT-5 2-371
PRIVATE_VLAN Messages 2-391
PRIVATE_VLAN-2 2-392
PROC_MGR Messages 2-394
PROC_MGR-SLOT#-2 2-394
PSS Messages 2-397
PSS-0 2-397
PSS-1 2-399
PSS-2 2-399
PSS-4 2-400
PSS-5 2-400
PTPLC Messages 2-401
PTPLC-3 2-401
PTP Messages 2-401
PTP-5 2-401
PTP-6 2-402
QOS Messages 2-403
QOS-2 2-403
xvi OL-26589-01
Contents
QOS-3 2-404
QOS-4 2-406
QOS-6 2-406
RADIUS Messages 2-408
RADIUS-2 2-408
RADIUS-3 2-409
RADIUS-4 2-409
RADIUS-5 2-409
RADIUS-6 2-409
RDL Messages 2-410
RDL-2 2-410
RDL-3 2-410
RDL-6 2-411
RES_MGR Messages 2-412
RES_MGR-1 2-412
RES_MGR-2 2-412
RES_MGR-3 2-413
RES_MGR-4 2-413
RES_MGR-5 2-415
RES_MGR-6 2-415
RIB Messages 2-415
RIB-0 2-415
RIB-1 2-415
RIB-2 2-416
RIB-3 2-416
RIB-4 2-417
RIB-5 2-418
RIB-6 2-418
RLIR Messages 2-418
RLIR-2 2-418
RLIR-6 2-419
RM Messages 2-420
RM-6 2-420
RM-SLOT#-2 2-420
RM-SLOT#-4 2-421
RSCN Messages 2-421
RSCN-2 2-421
RSCN-4 2-422
RSCN-6 2-422
SAL Messages 2-423
OL-26589-01 xvii
Contents
SAL-5 2-423
SAN_EXT_TUNER Messages 2-423
SAN_EXT_TUNER-3 2-423
SCHEDULER Messages 2-423
SCHEDULER-2 2-424
SCHEDULER-3 2-424
SCHEDULER-4 2-425
SCHEDULER-6 2-425
SCM Messages 2-425
SCM-2 2-425
SCSI-TARGET Messages 2-425
SCSI-TARGET-2 2-426
SCSI-TARGET-3 2-426
SCSI-TARGET-7 2-428
SDV Messages 2-428
SDV-2 2-428
SDV-3 2-429
SDV-4 2-431
SDV-6 2-431
SDV-7 2-431
SECURITYD Messages 2-431
SECURITYD-2 2-431
SECURITYD-3 2-433
SECURITYD-6 2-433
SENSOR_USD Messages 2-434
SENSOR_USD-2 2-434
SENSOR_USD-3 2-435
SENSOR_USD-5 2-436
SENSOR_MGR Messages 2-436
SENSOR_MGR-2 2-436
SENSOR_MGR-3 2-436
SENSOR_MGR-4 2-437
SFC Messages 2-437
SFC-3 2-437
SFM Messages 2-437
SFM-2 2-437
SFM-6 2-437
SKSD Messages 2-438
SKSD-2 2-438
SKSD-3 2-438
xviii OL-26589-01
Contents
SKSD-4 2-438
SKSD-5 2-439
SKSD-6 2-440
SKT_USD Messages 2-440
SKT_USD-2 2-441
SKT_USD-6 2-441
SME_CPP Messages 2-441
SME_CPP-2 2-441
SME_CPP-3 2-442
SME_CPP-5 2-447
SME_CPP-SLOT#-2 2-452
SNMPD Messages 2-456
SNMPD-1 2-456
SNMPD-2 2-457
SNMPD-3 2-457
SNMPD-4 2-457
SNMPD-5 2-457
SNMPD-6 2-457
SNMPD-7 2-458
SPAN Messages 2-458
SPAN-2 2-458
SPAN-3 2-458
SPAN-5 2-459
SPAN-6 2-460
SPI Messages 2-460
SPI-SLOT#-2 2-460
STP Messages 2-460
STP-2 2-461
STP-3 2-468
STP-4 2-469
STP-6 2-470
SVC_BATTERY Messages 2-472
SVC_BATTERY-SLOT#-2 2-472
SVC Messages 2-475
SVC-0 2-475
SVC-1 2-475
OL-26589-01 xix
Contents
SVC-2 2-475
SVC-3 2-476
SVC-4 2-488
SVC-5 2-497
SVC-6 2-497
SVC-7 2-512
SYSMGR Messages 2-512
SYSMGR-2 2-513
SYSMGR-3 2-536
SYSMGR-4 2-545
SYSMGR-5 2-547
SYSMGR-6 2-552
SYSMGR-7 2-554
SYSTEMHEALTH Messages 2-556
SYSTEMHEALTH-2 2-556
TACACS Messages 2-568
TACACS-2 2-568
TACACS-3 2-568
TACACS-4 2-568
TACACS-5 2-569
TACACS-6 2-569
TBIRD_CMN_USD Messages 2-569
TBIRD_CMN_USD-6 2-570
TBIRD_FWD_USD Messages 2-570
TBIRD_FWD_USD-6 2-570
TBIRD_MAC_USD Messages 2-570
TBIRD_MAC_USD-3 2-570
TBIRD_MAC_USD-6 2-570
TBIRD_QUE_USD Messages 2-570
TBIRD_QUE_USD-6 2-571
TBIRD_XBAR_USD Messages 2-571
TBIRD_XBAR_USD-6 2-571
TCAP Messages 2-571
TCAP-2 2-571
TPC Messages 2-572
TPC-SLOT#-5 2-572
TTYD Messages 2-572
xx OL-26589-01
Contents
TTYD-2 2-573
TTYD-3 2-573
TTYD-6 2-573
TUNNEL Messages 2-573
TUNNEL-2 2-574
TUNNEL-3 2-574
TUNNEL-4 2-574
TUNNEL-5 2-575
TUNNEL-7 2-576
U2RIB Messages 2-576
U2RIB-2 2-576
U2RIB-3 2-577
U2RIB-5 2-577
U2RIB-6 2-577
UDLD Messages 2-577
UDLD-3 2-577
UDLD-4 2-578
UDLD-5 2-579
UFDM Messages 2-579
UFDM-2 2-579
VDC_MGR Messages 2-580
VDC_MGR-2 2-580
VDC_MGR-3 2-581
VDC_MGR-5 2-581
VEC Messages 2-582
VEC-SLOT#-3 2-583
VEC-SLOT#-4 2-583
VEC-SLOT#-5 2-583
VEDB_MGR Messages 2-586
VEDB_MGR-2 2-587
VEDB_MGR-6 2-587
VES Messages 2-587
VES-SLOT#-4 2-587
VES-SLOT#-5 2-588
VFC Messages 2-589
VFC-3 2-589
VFC-6 2-589
VLAN_MGR Messages 2-589
VLAN_MGR-2 2-589
VLAN_MGR-3 2-589
OL-26589-01 xxi
Contents
VLAN_MGR-4 2-590
VLAN_MGR-5 2-590
VLAN_MGR-6 2-590
VNI Messages 2-591
VNI-2 2-591
VNI-3 2-591
VNI-6 2-591
VPC Messages 2-592
VPC-2 2-592
VPC-3 2-595
VPC-4 2-596
VPC-5 2-598
VPC-6 2-601
VPM Messages 2-603
VPM-2 2-604
VPM-3 2-605
VPM-4 2-605
VPM-6 2-606
VPM-SLOT#-2 2-608
VRRP-CFG Messages 2-608
VRRP-CFG-2 2-608
VRRP-CFG-3 2-609
VRRP-CFG-5 2-609
VRRP-ENG Messages 2-609
VRRP-ENG-2 2-609
VRRP-ENG-3 2-610
VRRP-ENG-4 2-611
VRRP-ENG-5 2-611
VRRP-ENG-6 2-612
VSAN Messages 2-612
VSAN-2 2-612
VSAN-3 2-613
VSAN-6 2-613
VSD Messages 2-614
VSD-SLOT#-2 2-614
VSHD Messages 2-614
VSHD-2 2-615
VSHD-3 2-615
VSHD-4 2-616
VSHD-5 2-616
xxii OL-26589-01
Contents
VSHD-7 2-617
WWN Messages 2-617
WWN-1 2-617
WWN-2 2-618
WWN-3 2-619
WWN-4 2-620
WWN-5 2-621
WWN-6 2-621
WWN-7 2-623
XBAR_CLIENT Messages 2-623
XBAR_CLIENT-2 2-623
XBAR_CLIENT-3 2-624
XBAR_CLIENT-SLOT#-2 2-625
XBAR_CLIENT-SLOT#-3 2-626
XBAR Messages 2-626
XBAR-2 2-626
XBAR-3 2-627
XBAR-4 2-627
XBAR-5 2-628
XMLMA Messages 2-632
XMLMA-2 2-632
XMLMA-3 2-633
XMLMA-5 2-633
XMLMA-6 2-633
XMLSA Messages 2-634
XMLSA-2 2-634
XMLSA-5 2-634
XMLSA-6 2-635
ZBM Messages 2-635
ZBM-2 2-635
ZBM-4 2-637
ZBM-6 2-637
ZONE Messages 2-639
ZONE-2 2-639
ZONE-3 2-647
ZONE-4 2-648
ZONE-5 2-650
ZONE-6 2-651
OL-26589-01 xxiii
Contents
xxiv OL-26589-01
Preface
This document lists and describes the system messages for Cisco NX-OS software. The system software
sends these messages to the console (and, optionally, to a logging server on another system) during
operation. Not all messages indicate a problem with your system. Some messages are purely
informational, while others might help diagnose problems with links, internal hardware, or the system
software.
This document includes system messages for all CiscoNX-OS software releases.
This chapter includes the following sections:
• Audience, page xvii
• Organization, page xvii
• Document Conventions, page xviii
• Documentation Feedback, page xviii
• Obtaining Documentation and Submitting a Service Request, page xix
Audience
This guide is for system administrators who are responsible for managing Cisco NX-OS systems.
Organization
This guide is organized as follows:
Chapter Title Description

Chapter 1 Introduction to System Messages for Describes the structure of system messages and
Cisco NX-OS the format of system log files.
Chapter 2 System Messages and Recovery Lists the messages that may appear in log files,
Procedures for the Cisco MDS 9000 and indicates suggested remedies where
and Nexus 7000 Family applicable for the Cisco MDS and Nexus 7000
Family.
OL-26589-01 xvii
Preface
Document Conventions
Command descriptions use these conventions:
Convention Description
boldface font Commands and keywords are in boldface.
italic font Arguments for which you supply values are in italics.
[ ] Elements in square brackets are optional.
[x|y|z] Optional alternative keywords are grouped in brackets and separated by vertical
bars.
string A nonquoted set of characters. Do not use quotation marks around the string or
the string will include the quotation marks.
Screen examples use these conventions:
screen font Terminal sessions and information that the switch displays are in screen font.
boldface screen Information that you must enter is in boldface screen font.
font
italic screen font Arguments for which you supply values are in italic screen font.
< > Nonprinting characters, such as passwords, are in angle brackets.
[ ] Default responses to system prompts are in square brackets.
!, # An exclamation point (!) or a pound sign (#) at the beginning of a line of code
indicates a comment line.
This document uses the following conventions:
Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the
manual.
Caution Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, please send your
comments to nexus7k-docfeedback@cisco.com. We appreciate your feedback.
xviii OL-26589-01
Preface
Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS version 2.0.
OL-26589-01 xix
Preface
xx OL-26589-01
CH A P T E R 1
Introduction to System Messages for Cisco
NX-OS
This chapter describes system messages, as defined by the syslog protocol (RFC 3164). It describes how
to understand the syslog message format and how to capture system messages for review.
This chapter contains the following sections:
• System Log Message Format, page 1-1
• Capturing System Messages and History, page 1-5
System Log Message Format

System log messages begin with a percent sign (%) and are displayed in the following formats:
• Syslog Format On a Resident Switch, page 1-1
• Syslog Format On a Remote-Logging Server, page 1-3
Syslog Format On a Resident Switch

The format for a resident syslog is:
month dd hh:mm:ss switchname facility-severity-MNEMONIC description
or
month dd hh:mm:ss switchname facility-SLOTnumber-severity-MNEMONIC description
or
month dd hh:mm:ss switchname facility-STANDBY-severity-MNEMONIC description
For example:
Nov 1 14:07:58 excal-113 %MODULE-5-MOD_OK: Module 1 is online
Nov 1 14:07:58 excal-113 %PORT-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver for interface
fc1/13 is not supported
.
Table 1-1 System Log Message Format Description
Element Description
month dd The date and month of the error or event
hh:mm:ss The time of the error or event
OL-26589-01 1-1
Chapter 1 Introduction to System Messages for Cisco NX-OS
Table 1-1 System Log Message Format Description (continued)
Element Description
switchname The name of the switch
facility The facility of the error or event (daemon, kernel, VSHD, or other facility)
severity Single-digit code from 0 to 7 that indicates the severity of the message
MNEMONIC Text string that uniquely describes the system message
%$VDC #%$ An optional virtual device context (VDC) ID that appears in the description for
messages requiring VDC IDs
%$VRF #%$ An optional virtual routing and forwarding (VRF) ID that appears in the
description for messages requiring VRF IDs
description Text string containing detailed information about the event being reported
FACILITY is a code consisting of two or more uppercase letters that indicate the facility to which the
system message refers. A facility is a hardware device, a protocol, a feature, or a module of the system
software.
System message SEVERITY codes range from 0 to 7 and reflect the severity of the condition. The lower
the number, the more serious the situation. Table 1-2 lists the severity levels.
Table 1-2 System Message Severity Levels
Level Description
0 – emergency System unusable
1 – alert Immediate action needed
2 – critical Critical condition
3 – error Error condition
4 – warning Warning condition
5 – notification Normal but significant condition
6 – informational Informational message only
7 – debugging Appears during debugging only
MNEMONIC is a code that uniquely identifies the system message.

Message-text is a text string that describes the condition. This portion of the message might contain
detailed information about the event, including terminal port numbers, network addresses, or addresses
that correspond to locations in the system memory address space. Because the information in these
variable fields changes from message to message, it is represented here by short strings enclosed in
square brackets ([ ]). A decimal number, for example, is represented as [dec].
Table 1-3 lists the representations of variable fields and the type of information in the fields.
Table 1-3 Representation of Variable Fields in System Messages
Representation Type of Information

[dec] Decimal number
[hex] Hexadecimal number
1-2 OL-26589-01

[char] Single character
[chars] Character string
The following example system message shows how the variable field might be used:
%MODULE-5-MOD_MINORSWFAIL: Module [dec] reported a failure in service [chars]
In this example,
Facility code =MODULE (indicating that it is a module-specific error)
Severity =5 (notification)
Alarm/event code= MOD_MINORSWFAIL
Description of the problem= Module [dec] reported a failure in service [chars]
[dec] is the module slot number associated with this message.
[chars] is the service name that experienced this failure.
System log messages begin with a percent sign (%) and are displayed in the following format (see
Table 1-4).
Syslog Format On a Remote-Logging Server

The syslog format on a remote-logging server is:
month dd hh:mm:ss IP-addr-switch : year month day hh:mm:ss Timezone: facility-severity-MNEMONIC
description
or
month dd hh:mm:ss IP-addr-switch : year month day hh:mm:ssTimezone:
facility-SLOTnumber-severity-MNEMONIC description
or
month dd hh:mm:ss IP-addr-switch : year month day hh:mm:ss Timezone: facility-STANDBY-severity-MNEMONIC
description
For example:
sep 21 11:09:50 172.22.22.45 : 2005 Sep 04 18:18:22 UTC: %AUTHPRIV-3-SYSTEM_MSG: ttyS1:
togetattr: Input/output error - getty[28224]
switch resident syslog 2005 Sep 4 18:18:22 switch %AUTHPRIV-3-SYSTEM_MSG: ttyS1:
togetattr: Input/output error - getty[28224]
time on switch : 2005 Sep 4 18:18:22 time on Loggng Server : Sep 21 11:09:50
fc1/13 is not supported
.
Table 1-4 System Log Message Format Description
Element Description
month dd The date and month of the error or event
hh:mm:ss The time of the error or event
IP-addr-switch The IP address of the switch
facility The facility of the error or event (daemon, kernel, VSHD, or other facility)
severity Single-digit code from 0 to 3 that indicates the severity of the message
MNEMONIC Text string that uniquely describes the system message
OL-26589-01 1-3
Table 1-4 System Log Message Format Description (continued)
Element Description
%$VDC #%$ An optional virtual device context (VDC) ID that appears in the description for
messages requiring VDC IDs
%$VRF #%$ An optional virtual routing and forwarding (VRF) ID that appears in the
description for messages requiring VRF IDs
description Text string containing detailed information about the event being reported
FACILITY is a code consisting of two or more uppercase letters that indicate the facility to which the
system message refers. A facility is a hardware device, a protocol, a feature, or a module of the system
software.
System message SEVERITY codes range from 0 to 3 and reflect the severity of the condition. The lower
the number, the more serious the situation. Table 1-5 lists the severity levels.
Table 1-5 System Log Message Format description
Level Description
0 – emergency System unusable
1 – alert Immediate action needed
2 – critical Critical condition
3 – notification Normal but significant condition
MNEMONIC is a code that uniquely identifies the system message.

Message-text is a text string that describes the condition. This portion of the message might contain
detailed information about the event, including terminal port numbers, network addresses, or addresses
that correspond to locations in the system memory address space. Because the information in these
variable fields changes from message to message, it is represented here by short strings enclosed in
square brackets ([ ]). A decimal number, for example, is represented as [dec].
Table 1-6 lists the representations of variable fields and the type of information in the fields.

[dec] Decimal number
[hex] Hexadecimal number
[char] Single character
[chars] Character string
The following example system message shows how the variable field might be used:
%AUTHPRIV-3-SYSTEM_MSG: AUTHPRIV [dec] reported a failure in service [chars]
In this example,
Facility code =AUTHPRIV (indicating that it is a authpriv-specific error)
Severity =3 (notification)
1-4 OL-26589-01
Capturing System Messages and History
Alarm/event code= SYSTEM_MSG

Description of the problem= Authpriv [dec] reported a failure in service [chars]
[dec] is the module slot number associated with this message.
[chars] is the service name that experienced this failure.

The system messages are displayed instantly on the console, by default, or are redirected to an internal
log file, or a syslog server. System message severity levels correspond to the keywords assigned by the
logging global configuration commands. These keywords define where and at what level these messages
appear (see to the Cisco NX-OS System Management Configuration Guide). Only system messages that
correspond to the configured logging level or higher severity messages are logged. As an example, if
you set the logging level to 3 (error), then you get error, critical, alerts, and emergency system messages,
but you do not get warning, notification, informational, or debugging system messages.
For complete information about handling system messages, see the Cisco NX-OS System Management
Configuration Guide, Release 4.1.
Saving the System Messages Log

The logging logfile global configuration command enables copying of system messages to an internal
log file and optionally sets the size of the file. To display the messages that are logged in the file, use
the show logging EXEC command. The first message displayed is the oldest message in the buffer. To
clear the current contents of the buffer, use the clear debug-logfile command.
Logging System Messages to a Syslog Server

The logging host-name command identifies a syslog server host to receive logging messages. The
host-name argument is the name or Internet address of the host. By issuing this command more than
once, you build a list of syslog servers that receive logging messages. The no logging host-name
command deletes the syslog server with the specified address from the list of syslog servers.
OL-26589-01 1-5
1-6 OL-26589-01
CH A P T E R 2
System Messages and Recovery Procedures for
the Cisco MDS 9000 and Nexus 7000 Family
This chapter includes system messages for the Cisco NX-OS MDS 9000 and Nexus 7000 families of
switches. The messages are listed in alphabetical order by the system facility that produces them. Within
each system facility section, messages are listed alphabetically by severity and mnemonics. Each error
message is followed by an explanation and a recommended action.
AAA Messages
This section contains the AAA messages.
AAA-1
Error Message AAA-1-AAA_SESSION_LIMIT_REJECT: aaa request rejected as maximum aaa

sessions are in progress
Explanation Aaa request rejected as the limit for maximum concurrent aaa sessions is reached
Recommended Action Please contact the Cisco reseller through which you procured the product for
support. If you have purchased a Cisco support contract please call Cisco TAC for support.
AAA-2
Error Message AAA-2-AAA_NVRAM_UPGRADE_FAILURE: upgrading of accounting log failed.

[chars]
Explanation Upgrading of accounting log failed.
OL-26589-01 2-1
Chapter 2 System Messages and Recovery Procedures for the Cisco MDS 9000 and Nexus 7000 Family
Error Message AAA-2-AAA_PROGRAM_EXIT: aaa daemon exiting: [chars]
Explanation Aaa daemon is exiting.
AAA-3
Error Message AAA-3-AAA_NVRAMFAILURE: nvram failure
Explanation Nvram can not be read/written to. Hence accounting log can not be stored there
AAA-6
Error Message AAA-6-AAA_ACCOUNTING_MESSAGE: [chars]
Explanation Accounting Message
Recommended Action No action is required.
AAM Messages
This section contains the AAM messages.
AAM-2
Error Message AAM-2-ELS_FC2_GL_SINDEX_LOOKUP_FAILED: Failed to lookup global port

index for interface [[chars]]
Explanation Failed to lookup global port index for interface [chars]
AAM-3
Error Message AAM-3-ALLOC_FAILED: Failed in File:[chars] Line:[dec] for type [dec]

size [dec]
AAM process could not allocate heap memory in File:[chars], at line:[dec], for
Explanation
memory-type:[dec] of Size:[dec]
2-2 OL-26589-01
Error Message AAM-3-ASSERTION_FAILED: Failed in File:[chars] Line:[dec]
Explanation AAM Process assertion failed in File:[chars], at line:[dec]
ACLLOG Messages
This section contains the ACLLOG messages.
ACLLOG-4
Error Message ACLLOG-4-ACLLOG_MAXFLOW_REACHED: [chars]
Explanation Max flow reached in current interval: [chars]
Error Message ACLLOG-4-ACLLOG_THRESHOLD: [chars]
Explanation Threshold Reached for Flow: [chars]
ACLLOG-6
Error Message ACLLOG-6-ACLLOG_FLOW_INTERVAL: [chars]
Explanation Flow info in current alert interval: [chars]
Error Message ACLLOG-6-ACLLOG_NEW_FLOW: [chars]
Explanation New Acllog Flow: [chars]
ACLMGR Messages
This section contains the ACLMGR messages.
OL-26589-01 2-3
ACLMGR-2
Error Message ACLMGR-2-ACLMGR_COMMIT_FAIL: Commit failed: [chars]
Explanation The PPF commit failed
Error Message ACLMGR-2-ACLMGR_NO_ERRDISABLED: [chars] event on interface [chars]

([hex]) allowed to succeed in spite of access-list failure
Explanation Although an access-list operation failed during a port event, the port event still finished
successfully because errdisable is disallowed
Error Message ACLMGR-2-EXITING: Exit reason: [chars]
Explanation The ACLMGR service process has exited due to [char]. The process has probably been
restarted automatically.
Error Message ACLMGR-2-INITFAIL: ACLMGR Service Init failed: [chars]
Explanation ACLMGR Service initialization failed. [chars] explains the reason for the failure.
Error Message ACLMGR-2-MALLOC_ERROR: Size [dec] bytes
Explanation The ACLMGR service could not allocate memory.
Error Message ACLMGR-2-PSS_ERROR: [chars]: PSS ret. val=[dec]
Explanation The ACLMGR service encountered error while operating on a persistent storage
database.
2-4 OL-26589-01
ACLMGR-3
Error Message ACLMGR-3-ACLMGR_DB_LOCK_MSG: ACL database message, reason: [chars],

session 0x%llx, type: [chars]
Explanation ACL PPF database lock acquire/release related message.
Error Message ACLMGR-3-ACLMGR_GSYNC_ERROR: Error occured during global sync of ACL

runtime database to standby, reason: [chars] , [chars]
Explanation ACL snapshot to send the copy of runtime database to standby failed
Error Message ACLMGR-3-ACLMGR_PPF_ERROR: PPF error: [chars]
Explanation The PPF generated error
Error Message ACLMGR-3-ACLMGR_PSS_CORRUPTED: [chars] PSS found corrupted
Explanation The ACLMGR service has detected corruption in one of its persistent information
database. The database would be recreated.
Error Message ACLMGR-3-ACLMGR_STAT_CONSOLIDATION_FAILURE: ACL statistic parsing or

consolidation failed
Explanation A statistic update failed during the parsing or consolidation step; statistics may have
been lost
Error Message ACLMGR-3-ACLMGR_VACL_REDIRECTION_DISABLED_REMOVAL: VACL redirection

to interface [chars] ([hex]) disabled: the port has been removed
Explanation A VACL redirection to the port has been deactivated because the port has been removed
OL-26589-01 2-5
Error Message ACLMGR-3-ACLMGR_VERIFY_FAIL: Verify failed: [chars]
Explanation The PPF Verify failed
Error Message ACLMGR-3-ACLMGR_COMMIT_FAIL: Commit failed: [chars]
Explanation The PPF commit failed
Error Message ACLMGR-3-MTSERROR: [chars]
Explanation ACLMGR Service encountered an MTS error. [chars] specifies the context where the
error occured.
ACLMGR-4
Error Message ACLMGR-4-ACLMGR_PPF_WARNING: PPF warning: [chars]
Explanation The PPF generated warning
Error Message ACLMGR-4-ACLMGR_VACL_REDIRECTION_DISABLED_PCM: VACL redirection to

interface [chars] ([hex]) disabled: the port became a portchannel member
Explanation A VACL redirection to the port has been temporarily deactivated because it is now a
member in a port channel
Error Message ACLMGR-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec]
Explanation There was a version mismatch between the ACLMGR service and one of its persistent
storage databases. The persistent information has been translated to the new format.
2-6 OL-26589-01
ACLMGR-6
Error Message ACLMGR-6-ACLMGR_PPF_NOTIF: PPF notification: [chars]
Explanation The PPF generated notification
Error Message ACLMGR-6-BECAME_ACTIVE: Became ACTIVE from standby mode
Explanation The ACLMGR service on the standby supervisor became active and it is ready to serve
client requests.
Error Message ACLMGR-6-BECAME_STDBY: Became STANDBY from active mode
Explanation The ACLMGR service became standby from active mode.
Error Message ACLMGR-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system

manager: Reason=[chars]
Explanation The ACLMGR service was unable to send heartbeat to the system manger
Error Message ACLMGR-6-SERVICE_UP: Initialized [chars]
Explanation The ACLMGR service is up and ready The service was initialized in [char] mode.
Error Message ACLMGR-6-SRVEXIT: ACLMGR Service shutting down gracefully
Explanation ACLMGR Service is shutting down gracefully. This is an informational message.
Error Message ACLMGR-6-SWITCHOVER: Switching Over to other Sup.
Explanation The ACLMGR service has successfully switched over to the standby supervisor card.
OL-26589-01 2-7
ACLQOS Messages
This section contains the ACLQOS messages.
ACLQOS-SLOT#-2
Error Message ACLQOS-SLOT#-2-ACLQOS_FAILED: ACLQOS failure: [chars]
Explanation ACLQOS operation failed in the aclqos client
Recommended Action No DDTS.
Error Message ACLQOS-SLOT#-2-ACLQOS_INBAND_INTERFACE_FAILURE: Inband interface lif

lookup failed ([chars])
Explanation Inband interface lif lookup failed
Error Message ACLQOS-SLOT#-2-ACLQOS_MALLOC_FAILED: Memory allocation failed.

[chars]
Explanation Memory allocation failed. This is a critical failure
Error Message ACLQOS-SLOT#-2-ACLQOS_OOTR: Tcam resource exhausted: [chars]
Explanation Tcam resources to program acls exhausted
Error Message ACLQOS-SLOT#-2-PPF_FAILED: Database failure: [chars]
Explanation Database operation failed in the aclqos client
ACLQOS-SLOT#-3
Error Message ACLQOS-SLOT#-3-ACLQOS_CC_INVALID: Invalid Congestion Control

parameters: [chars]
Explanation Invalid Congestion Control parameters
2-8 OL-26589-01
Error Message ACLQOS-SLOT#-3-ACLQOS_MCM_ERROR: MCM Message Inconsistent. Please

collect MCM and ACLMgr Tech Support for all VDCs
Explanation MCM Message Inconsistent
Error Message ACLQOS-SLOT#-3-ACLQOS_PAUSE_INVALID: Invalid Pause parameters:

[chars]
Explanation Invalid Pause parameters
Error Message ACLQOS-SLOT#-3-ACLQOS_QUEUING_ERROR: ACL/QoS queuing error: [chars]
Explanation Internal error in ACL/QoS queuing config
ACLQOS-SLOT#-4
Error Message ACLQOS-SLOT#-4-ACLQOS_ATOMIC_ERR: [chars]
Explanation Tcam will be overused, please turn off atomic update
Error Message ACLQOS-SLOT#-4-ACLQOS_BC_OVER_THRESHOLD: Bank Chaining enabled: Inst

[dec]susagehasreacheditsthreshold'
Explanation Tcam is almost full
Error Message ACLQOS-SLOT#-4-ACLQOS_FC_WARNING: Found stale FCoE entry in instance

[dec]. VSAN: [dec], SID: [hex], DID: [hex], SI:[dec], SI_MASK:[dec], RW_VSAN:
[dec], RW_VSAN_FLAG: [dec], RW_SID: [hex], RW_SID_FLAG: [dec], RW_DID: [hex].
RW_DID_FLAG: [dec] Cleaning it up.
Explanation Found stale FCoE entry in instance [dec]. VSAN: [dec], SID: 0x[hex], DID: 0x[hex],
SI:[dec], SI_MASK:[dec], RW_VSAN:[dec], RW_VSAN_FLAG: [dec], RW_SID: 0x[hex],
RW_SID_FLAG:[dec], RW_DID: 0x[hex]. RW_DID_FLAG: [dec] Cleaning it up.
OL-26589-01 2-9
Error Message ACLQOS-SLOT#-4-ACLQOS_MATCH_ALL_MERGE_UPDATE: Warning (match_all

merging): [chars]
Explanation Warning (match_all merging)
Error Message ACLQOS-SLOT#-4-ACLQOS_OVER_THRESHOLD: Inst [dec] Tcam [dec] Bank

[dec]susagehasreacheditsthreshold'
Explanation Tcam is almost full
Error Message ACLQOS-SLOT#-4-ACLQOS_QUEUING_COS2Q_INVALID: ACL/QoS invalid queuing

policy because of cos map change: [chars] queue [chars], interface [chars]
Explanation Attemped to configure an invalid queuing policy
Error Message ACLQOS-SLOT#-4-ACLQOS_QUEUING_INVALID: ACL/QoS invalid queuing

policy: [chars]
Explanation Attemped to configure an invalid queuing policy
Error Message ACLQOS-SLOT#-4-ACLQOS_UNDER_THRESHOLD: Tcam [dec] Bank [dec]'s usage

is below the threshold now
Explanation Tcam's usage is below the threshold
Error Message ACLQOS-SLOT#-4-ACLQOS_WARNING: ACLQOS Warning: [chars]
Explanation ACLQOS Warnings
ACLQOS-SLOT#-5
Error Message ACLQOS-SLOT#-5-ACLQOS_DISRUPTIVE_IPv6_UPDATE: Disruptive update of

IPv6 compression entries
Explanation Disruptive IPv6 compression entries update
2-10 OL-26589-01
Error Message ACLQOS-SLOT#-5-ACLQOS_NON_ATOMIC: Non atomic ACL/QoS policy update

done for [chars]
Explanation Non atomic ACL/QoS policy update was done
ACLTCAM Messages
This section contains the ACLTCAM messages.
ACLTCAM-2
Error Message ACLTCAM-2-ACL_TCAM_ADJ_EXHAUSTED: ACLTCAM failed to program route for

VSAN: [dec], SID: [chars] DID: [chars], error: [chars].
Explanation ACLTCAM process experienced a failure while programming route for VSAN [dec]
SID [chars] DID [chars] due to resource exhaustion. [chars] is the error code.
Error Message ACLTCAM-2-ACL_TCAM_ALMOST_FULL: TCAM close to FULL. [chars] TCAM

Usage ([dec]/[dec]) exceeded [dec]% fwd-eng: [dec], [chars]
Explanation [chars] TCAM usage [dec]/[dec] exceeded [dec] percent on fwd-engine [dec], [chars]
Error Message ACLTCAM-2-ACL_TCAM_CONFIG_READ_FROM_DRIVER_FAILED: [chars] [dec],

Error: [hex].
Explanation Unable to read configuration from forwarding engine ASIC driver. [chars] [dec], Error:
0x[hex].
Error Message ACLTCAM-2-ACL_TCAM_CONFIG_WRITE_TO_DRIVER_FAILED: [chars] [dec],

Error: [hex].
Explanation Unable to write configuration to forwarding engine ASIC driver. [chars] [dec], Error:
0x[hex].
OL-26589-01 2-11
Error Message ACLTCAM-2-ACL_TCAM_FLOW_STATS_READ_FAILED: Hardware flow stats read

failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec], Error:
[chars]).
Explanation Hardware flow stats read failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num
Entries: [dec] Error: [chars]).
Error Message ACLTCAM-2-ACL_TCAM_INCONSISTENT_DATABASE: Database found

inconsistent.
Explanation Database found inconsistent.
Error Message ACLTCAM-2-ACL_TCAM_INCONSISTENT_TCAM_CONTENTS: TCAM contents found

inconsistent.
Explanation TCAM contents are found inconsistent.
Error Message ACLTCAM-2-ACL_TCAM_INIT_FAILED: Initialization failed for forwarding

engine ASIC: [dec], [chars] TCAM.
Explanation Initialization failed for forwarding engine ASIC [dec], in [chars] TCAM.
Error Message ACLTCAM-2-ACL_TCAM_INIT_REGIONS_FAILED: Initialization failed for

forwarding engine ASIC: [dec], [chars] TCAM, [chars] Region.
Explanation Initialization of regions failed for forwarding engine ASIC [dec], in [chars] TCAM, for
[chars] Region.
Error Message ACLTCAM-2-ACL_TCAM_MALLOC_FAILURE: Memory allocation failed for size

[dec].
Explanation Memory allocation is failed for size [dec] bytes.
Recommended Action Restart the process.
Error Message ACLTCAM-2-ACL_TCAM_MTS_FAILURE: MTS operation failed: [chars].
Explanation MTS operation failed. [chars] is the reason.
2-12 OL-26589-01
Error Message ACLTCAM-2-ACL_TCAM_MTS_Q_FULL: MTS queue for SAP [dec] is full
Explanation MTS queue for SAP [dec] is full
Error Message ACLTCAM-2-ACL_TCAM_MTS_REGISTRATION_FAILED: MTS registration failed

for opCode: [dec].
Explanation MTS registration failed for opCode: [dec].
Error Message ACLTCAM-2-ACL_TCAM_NO_ROUTE: ACLTCAM failed to get route for VSAN:

[dec], Rewrite: [chars] DID: [chars] DID MASK: [chars], error: [hex].
Explanation ACLTCAM process experienced a failure while getting route for VSAN [dec] Rewrite
[chars] DID [chars] DID Mask [chars]. [hex] is the error code.
Error Message ACLTCAM-2-ACL_TCAM_NO_TCAM_LEFT: ACLTCAM resource exhausted for

interface : [chars]
Explanation ACLTCAM hardware resource is completely used.
Error Message ACLTCAM-2-ACL_TCAM_PHY_TCAM_READ_FAILED: [chars] read from hardware

TCAM failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec], Error:
[chars]).
Explanation [chars] read from hardware TCAM failed(ASIC: [dec], [chars] TCAM, Address: [dec],
Num Entries: [dec] Error: [chars]).
Error Message ACLTCAM-2-ACL_TCAM_PHY_TCAM_READ_INVALID: Invalid([chars], value:

[dec]) TCAM entry read from hardware TCAM (FWD-Engine: [dec], [chars] TCAM,
Address: [dec]), Ignoring this entry.
Explanation Invalid([chars], value: [dec]) TCAM entry from hardware TCAM(FWD-Engine: [dec],
[chars] TCAM, Address: [dec]) Ignoring this entry
OL-26589-01 2-13
Error Message ACLTCAM-2-ACL_TCAM_PHY_TCAM_WRITE_FAILED: [chars] write to hardware

TCAM failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec], Error:
[chars]).
Explanation [chars] write to hardware TCAM failed(ASIC: [dec], [chars] TCAM, Address: [dec],
Num Entries: [dec] Error: [chars]).
Error Message ACLTCAM-2-ACL_TCAM_PSS_FAILURE: Failed to do PSS operation: [chars],

reason: [hex].
Explanation Failed to do PSS operation [chars]. [hex] is the reason.
Error Message ACLTCAM-2-PSS_OPEN_FAILED: PSS open failed - [hex].
Explanation Persistent database handle could not obtained for ACLTCAM. [hex] is the error.
Error Message ACLTCAM-2-RECONS_FAILED: Reconstruction of TCAM contents failed

during upgrade - [hex].
Explanation During non-disruptive upgrade, the ACLTCAM contents are not properly
reconstructed. [hex] is the error.
ACLTCAM-3
Error Message ACLTCAM-3-ACL_TCAM_INV_TCAM_SYNC_ATTEMPT: Attempt to write invalid

shadow entry: [dec] ([dec]/[dec]) to TCAM, fwd-engine: [dec] ([chars]),
change-array: [dec]/[dec], <MSG_EXPL
Explanation TL Port Manager initialization failed. [chars] explains the reason for the failure.
Error Message ACLTCAM-3-ACL_TCAM_MTS_Q_LEAK: Possible MTS buffer leak for SAP [dec]
Explanation Possible MTS buffer leak for SAP [dec]
2-14 OL-26589-01
Error Message ACLTCAM-3-ALLOCFAIL: Heap Memory allocation failed: [chars]
Explanation TL Port Manager is out of dynamic memory. [chars] specifies the context where the
failure occured.
Error Message ACLTCAM-3-FC2ERROR: [chars]
Explanation TL Port Manager encountered an FC2 error. [chars] specifies the context where the
error occured.
Error Message ACLTCAM-3-GENERROR: [chars]
Explanation TL Port Manager encountered a general error, one that does not fall in any of the above
categories. [chars] describes the error and its context.
Error Message ACLTCAM-3-MTSERROR: [chars]
Explanation TL Port Manager encountered an MTS error. [chars] specifies the context where the
error occured.
Error Message ACLTCAM-3-PSSERROR: [chars]
Explanation TL Port Manager encountered a PSS error. [chars] specifies the context where the
failure occured.
Error Message ACLTCAM-3-REGISTER_FAILED: Could not register to MTS opcode [chars] -

error [hex].
Explanation ACLTCAM process could not register to the notifications mentioned by [chars]. [hex]
is the error.
OL-26589-01 2-15
ACLTCAM-4
Error Message ACLTCAM-4-ACL_TCAM_BELOW_THRESHOLD: [chars] TCAM usage ([dec]/[dec])

fell below [dec]% fwd-eng: [dec], [chars]
Explanation [chars] TCAM usage [dec]/[dec] fell below [dec] percent on fwd-engine [dec], [chars]
Error Message ACLTCAM-4-ACL_TCAM_BEYOND_THRESHOLD: [chars] TCAM usage ([dec]/[dec])

exceeded [dec]% fwd-eng: [dec], [chars]
Explanation [chars] TCAM usage [dec]/[dec] exceeded [dec] percent on fwd-engine [dec], [chars]
Error Message ACLTCAM-4-ACL_TCAM_FLOW_COUNTER_INVALIDATED: Flow counter for flow:

vsan: [dec], sid: [hex], did: [hex] with statistics: frames = %llu & bytes = %llu
was invalidated due to: [chars]
Explanation ACLTCAM process invalidated the flow counter for flow VSAN [dec] SID [hex] DID
[hex] with collected stats of [dec] frames and [dev] bytes was invalidated because of reason
[[chars]].
Error Message ACLTCAM-4-ACL_TCAM_FLOW_COUNTER_VALIDATED: Flow counter for flow:

vsan: [dec], sid: [hex], did: [hex] is now valid
Explanation ACLTCAM process validated the flow counter for flow VSAN [dec] SID [hex] DID
[hex].
Error Message ACLTCAM-4-ACL_TCAM_MTS_Q_HIGH: MTS queue for SAP [dec] is close to full
Explanation MTS queue for SAP [dec] is close to full
Error Message ACLTCAM-4-TLPM_ALPA_CACHE_FULL: Translation Port ALPA cache is full.

Some new entries may not be cached
Explanation TL Port cache is currently fully populated with active entries. Hence, there is no
available cache space to be assigned any newly created alpa entry on a TL Port. This is an
informational message.
2-16 OL-26589-01
ACLTCAM-6
Error Message ACLTCAM-6-ACL_TCAM_STATUS: Status: [chars].
Explanation ACLTCAM status is reported as: [chars].
Error Message ACLTCAM-6-MGRCREATED: Translation Port Manager created.
Explanation TL Port Manager was created successfully and is up and running. This is an
Error Message ACLTCAM-6-MGREXIT: Translation Port Manager shutting down gracefully.
Explanation TL Port Manager is shutting down gracefully. This is an informational message.
Error Message ACLTCAM-6-PORTDOWN: Translation Port [chars] DOWN.
Explanation A port configured as TL Port is DOWN and out of operation. [chars] is the interface-id
string that identifies the TL Port. This is an informational message.
Error Message ACLTCAM-6-PORTUP: Translation Port [chars] UP.
Explanation A port configured as TL Port is UP and operational. [chars] is the interface-id string
that identifies the TL Port. This is an informational message.
ACL Messages
This section contains the ACL messages.
ACL-2
Error Message ACL-2-ACL_HA_FAILURE: Failed to do high availability operation:

[chars].
Explanation Failed to do high availability operation. [chars] is the reason.
OL-26589-01 2-17
Error Message ACL-2-ACL_INIT_FAILED: Initialization failed for ACL: [chars],

reason: [hex].
Explanation Initialization failed for ACL due to [chars], reason: [hex].
Error Message ACL-2-ACL_LINECARD_STATUS: Status from linecard: [dec], for module:

[chars](ID: [dec]), status : [dec], error_id: [hex], catastrophic: [chars],
restart count: [dec].
Explanation Status from linecard: [dec], for module: [chars](ID: [dec]), status : [dec], error_id:
[hex], catastrophic: [chars], restart count: [dec].
Error Message ACL-2-ACL_MTS_FAILURE: Failed to do MTS operation: [chars].
Explanation Failed to do MTS operation. [chars] is the reason.
Error Message ACL-2-ACL_MTS_Q_FULL: MTS queue for SAP [dec] is full
Explanation MTS queue for SAP [dec] is full
Error Message ACL-2-ACL_MTS_REGISTRATION_FAILED: MTS options setting to [hex] failed

for opCode: [dec].
Explanation MTS options setting to [hex] failed for opCode: [dec].
Error Message ACL-2-ACL_PENDING_MSG_ARR_FULL: ACL Upgrade Pending Messages Array is

Full with [dec] messages. Failing the MTS message with Opc: [dec], RR_TOKEN: [hex]
Explanation ACL Upgrade Pending Messages Array is Full with [dec] messages. Failing the MTS
message with Opc: [dec], RR_TOKEN: [hex]
Error Message ACL-2-ACL_PSS_FAILURE: Failed to do PSS operation: [chars], reason:

[hex].
2-18 OL-26589-01
Error Message ACL-2-ACL_PSS_VER_FAIL: PSS file [chars] has version

[dec].[dec].[dec], expected version [dec].[dec].[dec].
Explanation There was a mismatch in the PSS version. [chars] indicates the PSS service,
[dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version.
Error Message ACL-2-ACL_RUNTIME_FAILURE: [chars] [dec], Error: [hex]
Explanation ACL runtime failure is reported as [chars] [dec], reason: [hex].
Error Message ACL-2-ACL_TCAM_FAILURE: Failed to do TCAM operation: [chars].
Explanation Failed to do TCAM operation. [chars] is the reason.
ACL-3
Error Message ACL-3-ACL_MTS_Q_LEAK: Possible MTS buffer leak for SAP [dec]
Explanation Possible MTS buffer leak for SAP [dec]
ACL-4
Error Message ACL-4-ACL_MTS_Q_HIGH: MTS queue for SAP [dec] is close to full
Explanation MTS queue for SAP [dec] is close to full
Error Message ACL-4-ACL_WARNING: [chars] [dec]
Explanation ACL warning messages is reported as [chars] [dec].
OL-26589-01 2-19
ACL-5
Error Message ACL-5-ACL_ADJ_SHARING_STATUS: Successfully completed [chars] on

Generation 2 linecards.
Explanation Successfully completed the command \[chars]\ on Generation 2 linecards.
ACL-6
Error Message ACL-6-ACL_DIAG_EVENT_STATUS: [chars] [hex].
Explanation ACL system health management event status is reported as [chars] [hex].
Error Message ACL-6-ACL_E_PORT_EVENT_STATUS: [chars] [chars].
Explanation ACL xEport event status is reported as [chars] [chars].
Error Message ACL-6-ACL_FCC_EVENT_STATUS: [chars] [chars].
Explanation ACL FCC event status is reported as [chars] [chars].
Error Message ACL-6-ACL_LINECARD_EVENT_STATUS: [chars] [hex].
Explanation ACL linecard event status is reported as [chars] [dec].
Error Message ACL-6-ACL_MCAST_EVENT_STATUS: [chars] [chars].
Explanation ACL multicast event status is reported as [chars] [chars].
Error Message ACL-6-ACL_NX_PORT_EVENT_STATUS: [chars] [chars].
Explanation ACL Nx Port event status is reported as [chars] [chars].
2-20 OL-26589-01
Error Message ACL-6-ACL_PORT_MODE_EVENT_STATUS: [chars] [chars].
Explanation ACL portmode event status is reported as [chars] [chars].
Error Message ACL-6-ACL_RUNTIME_STATUS: [chars] [dec]
Explanation ACL runtime status is reported as [chars] [dec].
Error Message ACL-6-ACL_SPAN_DEST_CONFIG_STATUS: [chars] [chars].
Explanation ACL SPAN destination config event status is reported as [chars] [chars].
Error Message ACL-6-ACL_SPAN_SRC_CONFIG_STATUS: [chars] [chars].
Explanation ACL SPAN source config event status is reported as [chars] [chars].
Error Message ACL-6-ACL_STATUS: ACL Status: [chars].
Explanation ACL status is reported as [chars].
Error Message ACL-6-ACL_UPDATE_SSRAM_QOS_EVENT_STATUS: [chars] [chars].
Explanation ACL update SSRAM for QoS event status is reported as [chars] [chars].
AMM Messages
This section contains the AMM messages.
AMM-SLOT#-0
Error Message AMM-SLOT#-0-CLI_INIT_FAILED: CLI library initialization failed!
Explanation AMM failed to initialize CLI infrastructure\sbackendlibrary.Thisisafatalerror.'
OL-26589-01 2-21
Error Message AMM-SLOT#-0-TIMER_INIT_FAILED: Timer subsystem initialization failed!
Explanation AMM failed to initialize timer library. This is a fatal error.
AMM-SLOT#-2
Error Message AMM-SLOT#-2-AMM_MEM_ALLOC: Memory allocation failed. [chars]
Error Message AMM-SLOT#-2-AMM_RECOVERY_ERROR: Error in Recovery: [chars]
Explanation AMM failed to recover after a re-start. This is a fatal error.
AMM-SLOT#-6
Error Message AMM-SLOT#-6-INITIALIZED: Internal state created [chars]
Explanation AMM has created its internal state stateless/stateful [chars].
ASCII-CFG Messages
This section contains the ASCII-CFG messages.
ASCII-CFG-2
Error Message ASCII-CFG-2-ACFG_CONFIGURATION_APPLY_ERROR: Error encountered while

Ascii configuration was being applied. Please use show startup-config log to view
details
Explanation At least one command failed while Ascii configuration was being applied
2-22 OL-26589-01
Error Message ASCII-CFG-2-ACFG_LIB_INVOKE_ERR: Ascii config library invocation

error: [chars]
Explanation Error encountered while library function was being invoked to display Ascii
configuration
Error Message ASCII-CFG-2-ACFG_OPER_FAIL: Operation failed because of [chars]
Explanation Operation failed
Error Message ASCII-CFG-2-ACFG_ROLLBACK_FAILED: Rollback to checkpoint [chars]

Failed, Going to undo the changes (atomic option)
Explanation Rollback operation failed for atomic option
Error Message ASCII-CFG-2-ACFG_ROLLBACK_UNDO_FAILED: Undo failed for atomic

Rollback, Please correct the error manually and retry rollback
Explanation Undoing the rollback changes (for atomic behavior) Failed
Error Message ASCII-CFG-2-ACFG_SYSLOG_INIT_FAILED: Ascii config Syslog Init Error
Explanation Error encountered while Initializing Syslog for Ascii Config
Error Message ASCII-CFG-2-PSS_VER_FAIL: PSS file [chars] has version

[dec].[dec].[dec], expected version [dec].[dec].[dec]
[dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version
OL-26589-01 2-23
ASCII-CFG-3
Error Message ASCII-CFG-3-ACFG_MTSERROR: [chars]
Explanation Ascii-cfg-server (rollback process) encountered an MTS error. [chars] specifies the
context where the error occurred.
ASCII-CFG-6
Error Message ASCII-CFG-6-ACFG_CHECKPOINT_CLEAR_DATABASE: cleared all the

configuration checkpoints
Explanation Cleared all the configuration checkpoints
Error Message ASCII-CFG-6-ACFG_CHECKPOINT_CREATED: Created configuration

checkpoint [chars]
Explanation Created configuration checkpoint
Error Message ASCII-CFG-6-ACFG_CHECKPOINT_DELETED: Deleted configuration

checkpoint [chars]
Explanation Deleted configuration checkpoint
Error Message ASCII-CFG-6-ACFG_MAX_CHECKPOINTS: Maximum no of checpoints reached,

Removing the oldest checkpoint
Explanation Maximum no.of checkpoints reached, removing the oldest checkpoint
Error Message ASCII-CFG-6-ACFG_ROLLBACK_ATOMIC: Performing configuration rollback

to checkpoint [chars] (with atomic option)
Explanation Performing configuration rollback with atomic option
2-24 OL-26589-01
Error Message ASCII-CFG-6-ACFG_ROLLBACK_BEST: Performing configuration rollback to

checkpoint [chars] (with best-effort option)
Explanation Performing configuration rollback with best-effort option
Error Message ASCII-CFG-6-ACFG_ROLLBACK_FIRST_ERR: Performing configuration

rollback to checkpoint [chars] (with stop-at-first failure option)
Explanation Performing configuration rollback with stop-at-first-failure option
Error Message ASCII-CFG-6-INFORMATION: [chars]
Explanation An event happend that affects Acfg-Rollback. [chars] indicates the event
Error Message ASCII-CFG-6-PSS_ERR: [chars]
Explanation An error occurred during an Acfg PSS operation. [chars] indicates the PSS operation
that caused the error
ASSOC MGR Messages

This section contains the ASSOC MGR messages.
ASSOC MGR-0
Error Message ASSOC_MGR-0-EMERGENCY_MSG: [chars]
Explanation Association Manager Emergency Message
Recommended Action Please file the bug for Association Manager Component thro' CDETS
ASSOC MGR-1
Error Message ASSOC_MGR-1-ALERT_MSG: [chars]
Explanation Association Manager Alert Message
Recommended Action Association Manager Internal Operation Alert
OL-26589-01 2-25
ASSOC MGR-2
Error Message ASSOC_MGR-2-CRITICAL_MSG: [chars]
Explanation Association Manager Critical Message
ASSOC MGR-3
Error Message ASSOC_MGR-3-ERROR_MSG: [chars]
Explanation Association Manager Error Message
ASSOC MGR-4
Error Message ASSOC_MGR-4-WARN_MSG: [chars]
Explanation Association Manager Warning Message
ASSOC MGR-5
Error Message ASSOC_MGR-5-NOTIF_MSG: [chars]
Explanation Association Manager Notification Message
ASSOC MGR-6
Error Message ASSOC_MGR-6-ASSOC_ACTIVATED: Association Activated for vlan id:[dec]

<--> vsan id:[dec]
Explanation Association Activated
2-26 OL-26589-01
Error Message ASSOC_MGR-6-ASSOC_CREATED: Association Created for vlan id:[dec] <-->

vsan id:[dec]
Explanation Association Created
Error Message ASSOC_MGR-6-ASSOC_DEACTIVATED: Association Deactivated for vlan id:

[dec] <--> vsan id: [dec]
Explanation Association Deactivated
Error Message ASSOC_MGR-6-ASSOC_DELETED: Association Deleted for vlan id: [dec]

<--> vsan id: [dec]
Explanation Association Deleted
Error Message ASSOC_MGR-6-ASSOC_MGR_STATEFULL_RESTART: Association Manager

Statefull Restart
Explanation Association Manager Stateful Restart
Error Message ASSOC_MGR-6-ASSOC_MGR_STATELESS_RESTART: Association Manager

Stateless Restart
Explanation Association Manager Stateless Restart
Error Message ASSOC_MGR-6-ASSOC_OPER_STATUS_CHG: Association status for vlan id:

[dec] <--> vsan id: [dec] changed from [chars] to [chars]
Explanation Association Operational State Change
Error Message ASSOC_MGR-6-INFO_MSG: [chars]
Explanation ASSOC Manager Informational Message
OL-26589-01 2-27
ASSOC MGR-7
Error Message ASSOC_MGR-7-DEBUG_MSG: [chars]
Explanation Association Manager Debug Message
BFDC Messages
This section contains the BFDC messages.
BFDC-SLOT#-2
Error Message BFDC-SLOT#-2-BFDC_GENERAL_FAILURE: General failure. [chars]
Explanation General failure. This is a critical failure
Error Message BFDC-SLOT#-2-BFDC_MALLOC_FAILED: Memory allocation failed. [chars]
Error Message BFDC-SLOT#-2-BFDC_MTS_FAILURE: MTS failure. [chars]
Explanation MTS related failure. This is a critical failure
BFD Messages
This section contains the BFD messages.
BFD-3
Error Message BFD-3-REACHED_CAPACITY_LIMIT: BFD session [chars] creation on

interface [chars] failed due to capacity limit [dec]
Explanation BFD session [chars] creation on interface [chars] failed due to current capacity limit
[dec]
Recommended Action Please remove current bfd sessions to make room for new ones
2-28 OL-26589-01
Error Message BFD-3-SESSION_ACL_INSTALL_GAVE_UP: BFD session [chars] installation

failed due to ACL installation failure interface [chars]
Explanation BFD session [chars] installation failed due to ACL installation failure interface [chars
Recommended Action Maximum acl install retries exceeded. Please to free up acl resources
Error Message BFD-3-SESSION_ACL_REMOVE_GAVE_UP: BFD session [chars] removal failed

due to ACL removal failure interface [chars]
Explanation BFD session [chars] removal failed due to ACL removal failure interface [chars
Recommended Action Maximum acl removal retries exceeded. Please manually remove bfd sessions
Error Message BFD-3-SESSION_CREATE_FAIL: Failed to create BFD session to neighbor

[chars] over intertface [chars]. Reason [chars]
Explanation Failed to create BFD session to neighbor [chars] over intertface [chars] Reason [chars]
Recommended Action SYSLOGDPC_NO_ACTION
BFD-4
Error Message BFD-4-INVALID_NBR: Attempt to BFD session failed for application

[chars].
Explanation Attempt to BFD session failed for application [chars].
Error Message BFD-4-SESSION_DELETE_FAIL: Attempt to delete BFD session for neighbor

[chars] failed: Reason [chars] ([hex]).
Explanation Attempt to delete BFD session for neighbor [chars] failed: Reason [chars] (0x[hex]).
BFD-5
Error Message BFD-5-BFD_DISABLED: BFD Disabled
Explanation BFD Service Disabled
OL-26589-01 2-29
Error Message BFD-5-BFD_ENABLED: BFD Enabled
Explanation BFD Service enabled
Error Message BFD-5-SESSION_ACTIVE_PARAMS_CHANGE: Local parameter of BFD session

[hex] has changed [chars]
Explanation Local parameter of BFD session 0x[hex] has changed [chars]
Error Message BFD-5-SESSION_CREATED: BFD session to neighbor [chars] on interface

[chars] has been created
Explanation BFD session to neighbor [chars] on interface [chars]
Error Message BFD-5-SESSION_LOCAL_PARAMS_CHANGE: Local parameter of BFD session

[hex] has changed [chars]
Explanation Local parameter of BFD session 0x[hex] has changed [chars]
Error Message BFD-5-SESSION_MOVED: BFD session [hex]: [chars]
Explanation BFD session 0x[hex]: [chars]
Error Message BFD-5-SESSION_NO_RESOURCES: No resource for session to neighbor

[chars] on interface [chars]
Explanation The BFD session can not be created or modified due to lack of resources. [[[ It has
reached the maximum number of packets per second allowed on the linecard.]]] No resources for
session to neighbor [chars]
Recommended Action Remove other BFD sessions [[[ or reduce the Tx/Rx timers ]]] to free resources
for this session
Error Message BFD-5-SESSION_REMOVED: BFD session to neighbor [chars] on interface

[chars] has been removed
Explanation BFD session to neighbor [chars] on interface [chars]
2-30 OL-26589-01
Error Message BFD-5-SESSION_STATE_DOWN: BFD session [chars] to neighbor [chars] on

interface [chars] has gone down. Reason: [hex].
Explanation BFD session [chars] to neighbor [chars] on interface [chars] has gone down. Reason:
0x[hex]. This may be as a result of the forwarding path being down.
Error Message BFD-5-SESSION_STATE_UP: BFD session [chars] to neighbor [chars] on

interface [chars] is up.
Explanation BFD session [chars] to neighbor [chars] on interface [chars] is up.
BFD-6
Error Message BFD-6-SESSION_ACL_INSTALL_FAILED: BFD session [chars] failed due to

missing ACL resources for interface [chars]
Explanation BFD session [chars] failed due to missing ACL resources for interface [chars]
Error Message BFD-6-SESSION_ACL_REMOVE_FAILED: BFD session [chars] removal failed

due to missing ACL resources for interface [chars]
Explanation BFD session [chars] removal failed due to missing ACL resources for interface [chars]
BIOS DAEMON Messages

This section contains the BIOS DAEMON messages.
BIOS DAEMON-2
Error Message BIOS_DAEMON-2-BIOS_DAEMON_FLASH_WARNING: Flash chip not supported by

running image. Skipping bios upgrade.
Explanation BIOS CHIP NOT SUPPORTED
OL-26589-01 2-31
Error Message BIOS_DAEMON-2-BIOS_DAEMON_PRI_BOOT_FAIL: System booted from Alternate

BIOS Flash
Explanation Boot from Alternate
Recommended Action SYSLOGDOC_NOACTION
Error Message BIOS_DAEMON-2-BIOS_DAEMON_SUP_ERROR: BIOS Sector ([dec]) is write

protected
Explanation BIOS WRITE PROTECTED
BIOS DAEMON-5
Error Message BIOS_DAEMON-5-BIOS_DAEMON_PRI_BOOT: System booted from Primary BIOS

Flash
Explanation Boot from Primary
BIOS DAEMON-SLOT#-2
Error Message BIOS_DAEMON-SLOT#-2-BIOS_DAEMON_LC_ERROR: BIOS Sector ([dec]) is

write protected
Explanation BIOS WRITE PROTECTED
Error Message BIOS_DAEMON-SLOT#-2-BIOS_DAEMON_LC_PRI_BOOT_FAIL: System booted from

Alternate BIOS Flash
Explanation Boot from Alternate
2-32 OL-26589-01
BIOS DAEMON-SLOT#-5
Error Message BIOS_DAEMON-SLOT#-5-BIOS_DAEMON_LC_PRI_BOOT: System booted from

Primary BIOS Flash
Explanation Boot from Primary
BOOTUP TEST Messages

This section contains the BOOTUP TEST messages.
BOOTUP TEST-2
Error Message BOOTUP_TEST-2-EOBC_FAIL: Module [dec] has failed test [chars] on EOBC
due to error [chars]
Explanation Online diagnostics EOBC test has failed
Error Message BOOTUP_TEST-2-EOBC_SKIP: Module [dec] has failed test [chars] on EOBC
Explanation Online diagnostics ManagementPort test has failed
Error Message BOOTUP_TEST-2-MGMT_PORT_FAIL: Module [dec] has failed test [chars] on

Management Port due to error [chars]
Explanation Online diagnostics ManagementPort test has failed
Error Message BOOTUP_TEST-2-MGMT_PORT_SKIP: Module [dec] has skipped test [chars]

on Management Port due to error [chars]
Explanation Online diagnostics ManagementPort test is skipped
BOOTVAR Messages
This section contains the BOOTVAR messages.
OL-26589-01 2-33
BOOTVAR-2
Error Message BOOTVAR-2-ALLOC_MEMORY: Memory allocation failed
Explanation The service failed to allocate memory.
Recommended Action Check if the system is low on memory, if so reset the switch.
Error Message BOOTVAR-2-AUTOCOPY_FAILED: Autocopy of file [chars] to standby

failed. [chars] (Error-id: [hex])
Explanation The image deemed to be copied to standby via the auto-copy feature failed.
Recommended Action Check error id for specified reason.
Error Message BOOTVAR-2-AUTOSYNC_FAILED: Image autosync failed. Reason: [chars]

([hex])
Explanation Image synchronization failed.
Recommended Action Check that there is enough space on the flash, as well as system high
availability status.
Error Message BOOTVAR-2-CONFIG_ERROR: Failed to update boot configuration
Explanation An error has occurred during the update of the boot configuration files
Recommended Action Check that there is enough space on the flash, show boot to check the
configured image names, show loader internal configuration to compare them with the current
bootloader configuration, if they are not coherent do write erase and retry to save the configuration.
Error Message BOOTVAR-2-IMAGE_NOT_COMPATIBLE: Warning: image [chars] is not

compatible with the current platform in SUP [dec]
Explanation The input image name is not compatible with the current platform.
Recommended Action Make sure a right image is specified before reboot.
BOOTVAR-3
Error Message BOOTVAR-3-AUTOCOPY_FAILED_STANDBY_FULL: Autocopy of file [chars] to

standby failed due to not enough disk space on standby
Explanation There is not enough disk space on the standby for the file to be copied.
Recommended Action Clear space on the standby disk.
2-34 OL-26589-01
Error Message BOOTVAR-3-INIT_FAILED: Initialization failed: Component [chars]
Explanation The service failed to start The failure occurs during initialization of the component
[chars].
Recommended Action Show processes to check the status of the other processes, pay attention to the
specified component.
Error Message BOOTVAR-3-LOAD_VERIFY_LIB_FAILED: Fetching library [chars] failed,

reason=[chars]
Explanation Failed to load bootvar specified verification library.
Error Message BOOTVAR-3-MODULE_LOCK_FAIL: Unable to get module lock, please don't

reload <error-id:[hex]>
Explanation Unable to acquire modlock to prevent user to reload during auto-sync.
Error Message BOOTVAR-3-NEIGHBOR_REJECT_AUTOCOPY: auto-copy failed - not supported

by neighbor supervisor.
Explanation Standby supervisor does not support auto-copy, thus failed.
Error Message BOOTVAR-3-VERIFY_FAILED: Image [chars] for bootvar [chars]

verification failed, reason=[chars]
Explanation The image set for this bootvar has failed the verification process, this is just a warning.
Recommended Action Check reason to determine actions.
BOOTVAR-5
Error Message BOOTVAR-5-AUTOCOPY_SUCCEED: auto-copy of file [chars] to standby

supervisor succeed
Explanation Auto copy of the file succeed, image integrity verified by standby.
OL-26589-01 2-35
Error Message BOOTVAR-5-AUTOCOPY_VERIFY_SEND_FAILED: Unable to ask standby to

verify file [chars], error = [hex]
Explanation Upon copied the image to standby, failed to send message to ask standby to verify
integrity.
Recommended Action Turn auto-copy off and back on.
Error Message BOOTVAR-5-AUTOSYNC_DONE: Image autosync done
Explanation The image synchronization done successfully.
Error Message BOOTVAR-5-AUTOSYNC_REBOOT: Rebooting standby after successful

autosync
Explanation Image autosync has been successful, resetting the standby supervisor to load the new
image.
Recommended Action Check that the standby sup reloads correctly.
Error Message BOOTVAR-5-AUTOSYNC_START: Starting image autosync. Please wait until

completion...
Explanation The standby-sup has requested the sync of the current image.
Error Message BOOTVAR-5-IMAGE_NOTEXISTS: Warning: image [chars] doesn't exist on

sup[dec]
Explanation The input image name doesn't exist on the specified supervisor.
Recommended Action Check whether the input image name you entered exists and make sure that
you have the image on the flash before reboot.
Error Message BOOTVAR-5-NEIGHBOR_UPDATE_AUTOCOPY: auto-copy supported by neighbor

supervisor, starting...
Explanation Info log reporting standby's support of auto-copy. Auto-copy is being started.
2-36 OL-26589-01
BOOTVAR-6
Error Message BOOTVAR-6-ALREADY_IN_SYNC: Image already in sync
Explanation No need to update the image on the standby-sup.
Error Message BOOTVAR-6-AUTOCOPY_DID_NOT_START: Autocopy of file [chars] to standby

did not start. [chars] (Error-id: [hex])
Explanation Autocopy of the file did not start as the remote copy location does not exist
Error Message BOOTVAR-6-CONFIG_UPDATED: Boot configuration updated
Explanation The boot-loader configuration files have been successfully updated.
Error Message BOOTVAR-6-STARTING: Boot configuration initialized
Explanation The service has successfully started.
CALLHOME Messages
This section contains the CALLHOME messages.
CALLHOME-2
Error Message CALLHOME-2-EVENT: [chars]
Explanation Callhome event [chars] occurred.
Recommended Action If you have configured your email address to receive callhome notifications,
please check your email for more details about this callhome event. If callhome was not enabled,
please execute CLI commands relevant to the callhome event to get more information about the error
Error Message CALLHOME-2-PROGRAM_EXIT: callhome process ending: [chars]
Explanation Callhome process is exiting with reason [chars].
OL-26589-01 2-37
CALLHOME-3
Error Message CALLHOME-3-CALLHOME_CFS_MERGE_OPERATION_FAILED: [chars]
Explanation [chars1]
Recommended Action Please check the reason for the failure of the cfs operation and rectify the
problem
Error Message CALLHOME-3-CALLHOME_CFS_OPERATION_FAILED: [chars] : [chars]
Explanation [chars1] [chars2]
problem
Error Message CALLHOME-3-CALLHOME_MAX_ALERT_MSG: [chars]
Explanation [chars]
Recommended Action Please check the reason for the generation of the callhome messages and
rectify the problem
Error Message CALLHOME-3-EVENT_PROCESS_ERROR: error in processing callhome event

[chars] reason:[chars]
Explanation Error in processing callhome event [chars] reason:[chars]
Recommended Action Please check your callhome configuration for proper configuration. Please
check SMTP server address, email addresses for destination profiles and enable status of callhome.
Use "show callhome" commands for displaying configuration.
Error Message CALLHOME-3-MESSAGE_SIZE_EXCEED: message size for callhome

alert:[chars] exceeds maximum limit for destination profile:[chars]
Explanation Message size for callhome alert:[chars] exceeds maximum limit for destination
profile:[chars]
Recommended Action Please check the maximum message size for the destination profile under
question. Increase it if possible to match the maximum limit allowed by your email destinations.
2-38 OL-26589-01
CALLHOME-6
Error Message CALLHOME-6-NONCRIT_EVENT: [chars]
Explanation Non-critical Callhome event [chars] occurred.
Recommended Action If you have configured your email address to receive callhome notifications,
please check your email for more details about this callhome event. If callhome was not enabled,
please execute CLI commands relevant to the callhome event to get more information about the error
CDP Messages
This section contains the CDP messages.
CDP-2
Error Message CDP-2-INITFAIL: CDP Daemon Initialization failed: [chars]
Explanation CDP Daemon Initialization failed. [chars] explains the reason for the failure.
CDP-3
Error Message CDP-3-ALLOCFAIL: Heap Memory allocation failed: [chars]
Explanation CDP Daemon is out of dynamic memory. [chars] specifies the context where the failure
occurred.
Error Message CDP-3-GENERROR: [chars]
Explanation CDP Daemon encountered a general error, one that does not fall in any of the above
Error Message CDP-3-MCASTBINDFAIL: Failed to bind for CDP multicast address on

interface [hex] - [chars]
Explanation An attempt to register for packets destined to the CDP multicast address failed. [dec]
identifies the interface [char] identifies the reason.
OL-26589-01 2-39
Error Message CDP-3-MTSERROR: [chars]
Explanation CDP Daemon encountered an MTS error. [chars] specifies the context where the error
occurred.
Error Message CDP-3-PKTRECVFAIL: Failed to receive packet - [chars]
Explanation Failed to receive packet. [char] identifies the reason.
Error Message CDP-3-PKTSENDFAIL: Failed to send packet, interface [hex] - [chars]
Explanation Failed to send packet. [dec] identifies the interface [char] identifies the reason.
Error Message CDP-3-PSSERROR: [chars]
Explanation CDP Daemon encountered a PSS error. [chars] specifies the context where the failure
occurred.
Error Message CDP-3-SOCKBINDFAIL: Failed to bind to raw socket, interface [hex] -

[chars]
Explanation Failed to bind to raw socket. [dec] identifies the interface [char] identifies the reason.
Error Message CDP-3-SOCKOPENFAIL: Failed to open socket for receiving raw 802_2
packets - [chars]
Explanation An attempt to open a socket for receiving raw 802_2 packets failed. [char] identifies
the reason.
CDP-4
Error Message CDP-4-DUPLEX_MISMATCH: Duplex mismatch discovered on [chars], with

[chars]
Explanation Duplex mismatch discovered from the received cdp packet This is a warning message.
2-40 OL-26589-01
Error Message CDP-4-NATIVE_VLAN_MISMATCH: Native VLAN mismatch discovered on

[chars]([dec]), with [chars]([dec])
Explanation Native VLAN mismatch discovered This is a warning message.
CDP-5
Error Message CDP-5-DISABLED: CDP is disabled
Explanation CDP is disabled on the device.
Error Message CDP-5-ENABLED: CDP is enabled
Explanation CDP is enabled on the device.
Error Message CDP-5-NEIGHBOR_ADDED: Device [chars] discovered of type [chars] with

port [chars] on incoming port [chars] with ip addr [chars] and mgmt ip [chars]
Explanation Discovered a neighbor device. This is an informational message.
Error Message CDP-5-NEIGHBOR_REMOVED: CDP Neighbor [chars] on port [chars] has been
removed
Explanation Deleted a neighbor device. This is an informational message.
CDP-6
Error Message CDP-6-CDPDUP: CDP Daemon Up.
Explanation CDP Daemon was created successfully and is up and running. This is an informational
message.
OL-26589-01 2-41
Error Message CDP-6-CDPEXIT: CDP Daemon shutting down gracefully.
Explanation CDP Daemon is shutting down gracefully. This is an informational message.
Error Message CDP-6-PORTDISABLE: CDP disabled on port [chars]
Explanation CDP was disabled on a given port. [chars] is the interface-ID string that identifies the
port. This is an informational message.
Error Message CDP-6-PORTDOWN: A CDP enabled port [chars] went down.
Explanation A CDP enabled port became un-operational. [chars] is the interface-ID string that
identifies the port. This is an informational message.
Error Message CDP-6-PORTENABLE: CDP enabled on port [chars]
Explanation CDP was enabled on a given port. [chars] is the interface-ID string that identifies the
port. This is an informational message.
Error Message CDP-6-PORTUP: A CDP enabled port [chars] came up.
Explanation A CDP enabled port became operational. [chars] is the interface-ID string that
identifies the port. This is an informational message.
CERT_ENROLL Messages
This section contains the CERT_ENROLL messages.
CERT_ENROLL-2
Error Message CERT_ENROLL-2-CERT_EN_PROGRAM_EXIT: cert_enroll daemon exiting:

[chars]
Explanation Cert_enroll daemon is exiting.
2-42 OL-26589-01
CERT_ENROLL-3
Error Message CERT_ENROLL-3-CERT_EN_ERROR_MESSAGE: [chars]
Explanation CERT_ENROLL Error Message
Error Message CERT_ENROLL-3-CERT_EN_FIPS_MODE_INIT_ERROR: Could not initialize

FIPS mode : [chars]
Explanation FIPS mode initialization error
CERT_ENROLL-6
Error Message CERT_ENROLL-6-CERT_EN_MESSAGE: [chars]
Explanation CERT_ENROLL Message
CFS Messages
This section contains the CFS messages.
CFS-2
Error Message CFS-2-CFS_REJECT: CFS reject: [chars]: Switch WWN [chars], ip

[chars], reason [chars]
Explanation CFS reject: [chars] Switch WWN [chars], ip [chars], reason [chars]
Error Message CFS-2-EXITING: Exit reason: [chars]
Explanation The CFS service process has exited due to [char]. The process has probably been
OL-26589-01 2-43
Error Message CFS-2-GENERAL_ERROR: [chars]
Explanation The CFS service has encountered an critical error. The description of error is [str.]
Error Message CFS-2-INITFAIL: CFS Service Init failed: [chars]
Explanation CFS Service initialization failed. [chars] explains the reason for the failure.
Error Message CFS-2-LOCK_FAILED: lock failed for sap [dec] due to internal error.
Explanation Lock failed due to Unrestricted uncoordinated count is out of sync for sap [dec]
Recommended Action To recover from this state run command

cfsinternaldecrement-unrestricted<app-sap
Error Message CFS-2-MALLOC_ERROR: Size [dec] bytes
Explanation The CFS service could not allocate memory.
Error Message CFS-2-MTS_REJECT: Verification failed reject MTS message SAP

[dec]:RR-token [hex]
Explanation This MTS message could have been posted by the previous active running pre 3.x; MTS
structure has changed since then hence ignore the MTS message, Source SAP [dec]; RR-token [hex]
Error Message CFS-2-PSS_ERROR: [chars]: PSS ret. val=[dec]
Explanation The CFS service encountered error while operating on a persistent storage database.
Error Message CFS-2-VDC_MGR_FAIL: Failed to get a valid switch mac from VDC
Manager: [chars]
Explanation VDC manager did not respond with a proper MAC address. It could have been because
of a timeout in MTS received
2-44 OL-26589-01
CFS-3
Error Message CFS-3-ALLOCFAIL: Heap Memory allocation failed: [chars]
Explanation CFS Service is out of dynamic memory. [chars] specifies the context where the failure
occured
Error Message CFS-3-APP_MERGE_FAILED: Merge failed for app [chars], local switch
wwn [chars], remote switch wwn [chars].Please check
showcfsmergestatusname[chars]'formoreinformation'
Explanation The CFS service has detected a merge failure.
Error Message CFS-3-CFS_PSS_CORRUPTED: [chars] PSS found corrupted
Explanation The CFS service has detected corruption in one of its persistent information database.
The database would be recreated.
Error Message CFS-3-DBERROR: [chars]
Explanation CFS Service encountered a database error. [chars] specifies the context where the
failure occured.
Error Message CFS-3-FAILURE_RESPONSE: [chars] [hex]
Explanation CFS Service failed to get response [chars][hex] specify the context where the failure
occured.
Error Message CFS-3-FIPS_TEST_FAILED: FIPS compliance test failed
Explanation FIPS compliance test failed
OL-26589-01 2-45
Error Message CFS-3-GENERROR: [chars]
Explanation CFS Service encountered a general error, one that does not fall in any of the above
Error Message CFS-3-LICERR: [chars]
Explanation CFS Service failed to get license.
Error Message CFS-3-MERGE_FAILED: Merge failed for app [chars], local switch wwn
[chars],ip [chars], remote switch wwn [chars], ip [chars]
Explanation The CFS service has detected a merge failure.
Error Message CFS-3-MTSERROR: [chars]
Explanation CFS Service encountered an MTS error. [chars] specifies the context where the error
occured.
Error Message CFS-3-PSSERROR: [chars]
Explanation CFS Service encountered a PSS error. [chars] specifies the context where the failure
occured.
Error Message CFS-3-TIMEOUT_ERROR: [chars] [hex]
Explanation CFS Service encountered a timeout [chars][hex] specify the context where the failure
occured.
Error Message CFS-3-UNKNOWN_MSG: Recvd. from Node=[dec] SAP=[dec]
Explanation The CFS service has received an unknown message from [dec]].[dec]. This information
is for debugging only.
2-46 OL-26589-01
CFS-4
Error Message CFS-4-LICEXP: [chars]
Explanation CFS Service license is going to expire. [chars] gives the expected time of expiry
Error Message CFS-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec]
Explanation There was a version mismatch between the CFS service and one of its persistent storage
databases. The persistent information has been translated to the new format.
CFS-6
Error Message CFS-6-BECAME_ACTIVE: Became ACTIVE from standby mode
Explanation The CFS service on the standby supervisor became active and it is ready to serve client
requests.
Error Message CFS-6-BECAME_STDBY: Became STANDBY from active mode
Explanation The CFS service became standby from active mode.
Error Message CFS-6-EXCESSIVE_DELAY: [chars]
Explanation Excessive time taken for a processing event. The description of the event is [str.]
Error Message CFS-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system

Explanation The CFS service was unable to send heartbeat to the system manger
OL-26589-01 2-47
Error Message CFS-6-GENERAL_EVENT: [chars]
Explanation The CFS service has generated an important event. The description of the event is [str.]
Error Message CFS-6-INVALID_CHECKSUM: Received packet from peer on if-index([hex])

with corrupted checksum
Explanation This could be because of errors in the link
Error Message CFS-6-INVALID_IF_INDEX: Received packet on if-index([hex]) which is

not recognized by CFS
Explanation The if-index does not match with the if-index used in discovery or we might have
already recieved an adjacency cleanup message for this if-index. Check if the if-index is that of the
port-channel or a physical if-index
Error Message CFS-6-LOGICAL_DISTRIBUTION_INFO: vsan [dec], source wwn [chars], ip

[chars] app-id [dec], session-id [dec], user [chars], [chars]
Explanation Vsan [dec], source wwn [chars], ip [chars], app-id [dec], user [chars], event [chars]
Error Message CFS-6-PHY_DISTRIBUTION_INFO: source wwn [chars], ip [chars], app-id

[dec], session-id [dec], user [chars], [chars]
Explanation Source wwn [chars], ip [chars], app-id [dec], session-id [dec], user [chars], event
[chars]
Error Message CFS-6-PSS_CREATED: [chars] PSS Created
Explanation One of the persistent information database of CFS service has been recreated
Error Message CFS-6-PSS_DESTROYED: [chars] PSS Destroyed
Explanation One of the persistent information databases of CFS Service has been intentionally
destroyed and would be recreated.
2-48 OL-26589-01
Error Message CFS-6-REGION_CTX_REMOVED: Region info is deleted for [chars]
Explanation [chars] is in logical scope. Regions are supported only physical scope applications
Error Message CFS-6-SERVICE_UP: Initialized [chars]
Explanation The CFS service is up and ready to accept client requests The service was initialized in
[char] mode.
Error Message CFS-6-SRVCREATED: CFS Service created
Explanation CFS Service was created successfully and is up and running. This is an informational
message.
Error Message CFS-6-SRVEXIT: CFS Service shutting down gracefully
Explanation CFS Service is shutting down gracefully. This is an informational message.
Error Message CFS-6-SWITCHOVER: Switching Over to other Sup.
Explanation The CFS service has successfully switched over to the standby supervisor card.
CIMSRVPROV Messages
This section contains the CIMSRVPROV messages.
CIMSRVPROV-2
Error Message CIMSRVPROV-2-CIM_SYSLOG_EXIT: Message:[chars] errcode:[dec]
Explanation Exit due to critical error
OL-26589-01 2-49
Error Message CIMSRVPROV-2-CIM_SYSLOG_PSS_SNAPSHOT_ERR: Source URI:[chars]

Destination URI:[chars] errcode:[dec]
Explanation PSS snapshot error
Error Message CIMSRVPROV-2-CIM_SYSLOG_SDWRAP_ERR: Description:[chars]

errcode:[dec]
Explanation Debug infrastructure error
CIMSRVPROV-3
Error Message CIMSRVPROV-3-CIM_SYSLOG_COPY_CONFIG_ERR: Message:[chars]

URI:[chars] errcode:[dec]
Explanation Copy running startup error
Error Message CIMSRVPROV-3-CIM_SYSLOG_FILE_ERR: Purpose:[chars] Filename:[chars]

errcode:[dec]
Explanation File handling error
Error Message CIMSRVPROV-3-CIM_SYSLOG_MTS_ERR: message [chars]
Explanation MTS message handling error
Error Message CIMSRVPROV-3-CIM_SYSLOG_PSS_ERR: Purpose:[chars] URI:[chars]

errcode:[dec]
Explanation PSS handling error
2-50 OL-26589-01
CIMSRVPROV-6
Error Message CIMSRVPROV-6-LOG_CIM_CERTIFICATE_CLEARED: Cleared certificate

[chars]
Explanation Cleared a certificate named [chars].
Error Message CIMSRVPROV-6-LOG_CIM_CERTIFICATE_INSTALLED: Installed certificate

[chars]
Explanation Installed a certificate named [chars].
CLIS Messages
This section contains the CLIS messages.
CLIS-5
Error Message CLIS-5-CLIS_SYSLOG_CMD_REMOVED: Command deleted from the NVDB:

[chars]
Explanation Command removal due to configuration change
CLK_MGR Messages
This section contains the CLK_MGR messages.
CLK_MGR-2
Error Message CLK_MGR-2-CLK_MGR_FC2_CRIT: CLK_MGR critical error: [chars]
Explanation CLK_MGR fc2 clock synchronization critical error
OL-26589-01 2-51
CLK_MGR-5
Error Message CLK_MGR-5-CLK_MGR_CLI_CONFIG: CLK_MGR clock is synchronized by [chars]

from VDC [dec]
Explanation CLK_MGR clock is synchronized by [chars] from VDC
CLK_MGR-6
Error Message CLK_MGR-6-CLK_MGR_TSTAMP_CHKS_DISABLED: CLK_MGR timestamp checks

disabled: [chars]
Explanation CLK_MGR timestamp checks disabled
Error Message CLK_MGR-6-CLK_MGR_TSTAMP_CHKS_ENABLED: CLK_MGR timestamp checks

enabled
Explanation CLK_MGR timestamp checks enabled
CLOUD Messages
This section contains the CLOUD messages.
CLOUD-2
Error Message CLOUD-2-PROGRAM_EXIT: cloud-discovery process ending: [chars]
Explanation Cloud-discovery process is exiting with reason [chars].
CLOUD-3
Error Message CLOUD-3-CLOUD_CFS_MERGE_OPERATION_FAILED: [chars]
Explanation [chars1]
problem
2-52 OL-26589-01
Error Message CLOUD-3-CLOUD_CFS_OPERATION_FAILED: [chars] : [chars]
problem
Error Message CLOUD-3-CLOUD_FEATURE_MANAGER_ERROR: [chars] : [chars]
Recommended Action Please check the reason for error using feature manager and rectify the
problem
Error Message CLOUD-3-CLOUD_PSS_OPERATION_FAILED: [chars] : [chars]
Recommended Action Please check the reason for the failure of the pss operation and rectify the
problem
CLOUD-6
Error Message CLOUD-6-CLOUD_DISCOVERY_DONE: discovery over
Explanation Cloud-discovery started
Recommended Action Check cloud membership
Error Message CLOUD-6-CLOUD_DISCOVERY_STARTED: [chars] discovery started
Explanation Cloud-discovery started
Recommended Action Check cloud-discovery status after sometime
CLP_MAC Messages
This section contains the CLP_MAC messages.
CLP_MAC-6
Error Message CLP_MAC-6-CLM_DEBUG_MSG: [chars]
Explanation Debug log message
OL-26589-01 2-53
CLUSTER Messages
This section contains the CLUSTER messages.
CLUSTER-2
Error Message CLUSTER-2-CLUSTER_CAP_ADD_FAIL: Failed to add cluster capability

[dec]
Explanation Cluster capability addition failed
Error Message CLUSTER-2-CLUSTER_CAP_DEL_FAIL: Failed to delete cluster capability

[dec]
Explanation Cluster capability deletion failed
CMOND Messages
This section contains the CMOND messages.
CMOND-2
Error Message CMOND-2-CMOND_ALERT_MSG: [chars]
Explanation Alert message
Error Message CMOND-2-CMOND_ERROR_MSG: [chars]
Explanation Error message
CMPPROXY Messages
This section contains the CMPPROXY messages.
2-54 OL-26589-01
CMPPROXY-2
Error Message CMPPROXY-2-LOG_CMP_IS_NOT_UP: Connectivity Management processor (on

module [dec]) did not come up
Explanation Connectivity Management processor is not sending heartbeats on this module
Error Message CMPPROXY-2-LOG_CMP_UP: Connectivity Management processor(on module

[dec]) is now UP
Explanation Connectivity Management processor has come up and is exchanging heartbeats with
CP on this SUP slot
Error Message CMPPROXY-2-LOG_CMP_WENT_DOWN: Connectivity Management processor (on

module [dec]) went DOWN
Explanation Connectivity Management processor has either gone down or is not sending heartbeats
for a long time
CMPPROXY-5
Error Message CMPPROXY-5-LOG_CMP_AAA_FAILURE: Authentication failed for a login

from CMP (on module [dec])
Explanation A login attempt has been denied access from Connectivity management processor
(CMP) as authentication did not succeed
Error Message CMPPROXY-5-MALLOC_FAILURE: Memory allocation failure
Explanation Memory allocation in a call to malloc/calloc has failed.
OL-26589-01 2-55
CMPPROXY-6
Error Message CMPPROXY-6-LOG_CMP_AAA_SUCCESS: Authentication succeeded for a login

from CMP (on module [dec])
Explanation A login attempt has succeeded from Connectivity management processor (CMP) in
getting access as AAA succeeded
COPP Messages
This section contains the COPP messages.
COPP-1
Error Message COPP-1-COPP_DROPS1: CoPP drops exceed threshold in class: [chars],

check show policy-map interface control-plane for more info.
Explanation There are CoPP drops, [chars] tell which class has dropped packets.
COPP-2

Error Message COPP-2-COPP_INIT_FAIL: CoPP Initialization failed: [chars]
Explanation CoPP Initialization failed. [chars] explains the reason for the failure.
Error Message COPP-2-COPP_MTS_FAIL: Failed to do MTS operation: [chars]
Explanation Failed to do MTS operation. [chars] explains the reason for the failure.
2-56 OL-26589-01
Error Message COPP-2-COPP_NO_POLICY: Control-plane is unprotected.
Explanation There isntanypolicyconfiguredtoprotectcontrol-plane.'
Error Message COPP-2-COPP_POLICY: Control-Plane is protected with policy [chars].
Explanation There is a policy attached to the control-plane.
Error Message COPP-2-COPP_PROFILE_DIFF: CoPP Default Profile may have changed,

please check the diffs using show copp diff profile <profile-type
Explanation CoPP Default Profile may have changed, please check the diffs using show copp diff
profile <profile-type
COPP-3
Error Message COPP-3-COPP_ALLOC_FAIL: Memory allocation failure: [chars]
Explanation Failed to alloc required memory. [chars] explains the reason for the failure.

Error Message COPP-3-COPP_PPF_FAIL: Error during PPF operation: [chars]
Explanation Failed to do PPF operation. [chars] explains the reason for the failure.
Error Message COPP-3-COPP_PSS_FAIL: Error during PSS operation: [chars]
Explanation Failed to do PSS operation. [chars] explains the reason for the failure.
OL-26589-01 2-57
COPP-4

COPP-5
Error Message COPP-5-COPP_DISABLED: COPP Disabled
Explanation COPP Service Disabled

Error Message COPP-5-COPP_ENABLED: COPP Enabled
Explanation COPP Service nabled
Error Message COPP-5-COPP_INIT: COPP initialized
Explanation COPP Service Initialized
COPP-6

2-58 OL-26589-01
Error Message COPP-6-COPP_POLICY_ATTACHED: CoPP policy has been attached to control

plane interface.
Explanation CoPP policy has been attached to control plane interface.
Error Message COPP-6-COPP_POLICY_DETACHED: CoPP policy has been detached from

control plane interface.
Explanation CoPP policy has been detached from control plane interface.
COPP-7

Error Message CORE-DMON-2-MODULE_COREDUMP_DONE: kernel coredump completed on

module:[dec]
Explanation Kernel coredump finishing on a module
Error Message CORE-DMON-2-MODULE_COREDUMP_STARTED: kernel coredump started on

module:[dec]
Explanation Kernel coredump starting on a module
CREDITMON Messages
This section contains the CREDITMON messages.
CREDITMON-SLOT#-2
Error Message CREDITMON-SLOT#-2-SYSERR_CREDITMON_APP_EXITED: [chars]
Explanation Credit Monitor application exited
OL-26589-01 2-59
Error Message CREDITMON-SLOT#-2-SYSERR_CREDITMON_MTS_INIT_ERR: [chars]
Explanation Credit Monitor error binding to MTS
CTS Messages
This section contains the CTS messages.
CTS-2
Error Message CTS-2-CTS_AUTHENT_FAILURE: CTS Authentication failure on Port

[chars] (CTS Failure Reason: [chars] [chars])
Explanation Fibre-Channel Authentication failure on Port [chars].(Reason Code [chars] Detail

[chars]). Please check password configurations and ensure appropriate security modes on this port
as well as peer port
Error Message CTS-2-CTS_FIPS_BYPASS_TEST_FAILED: FIPS bypass test failed for

interface: [chars]
Explanation .
Error Message CTS-2-CTS_SAP_FAILED: SAP exchange failed on interface [chars].

(Reason: [chars])
Explanation .
Error Message CTS-2-CTS_SAP_REKEY_FAILED: SAP exchange failed on interface

[chars]. (Reason: [chars])
Explanation .
Error Message CTS-2-DBG_INIT_FAILED: Debug Infrastructure Initialization failed (

[chars] )
Explanation .
2-60 OL-26589-01
Error Message CTS-2-FC2_E_INIT_FAILED: Fibre-Channel Initialization of an E_Port

failed ( [chars] )
Explanation CTS Manager has been unable to initialize with the FC-2 E-Port infrastructure.
Error Message CTS-2-FC2_F_INIT_FAILED: Fibre-Channel Initialization of an F_Port

failed ( [chars] )
Explanation CTS Manager has been unable to initialize with the FC-2 F-Port infrastructure.
Error Message CTS-2-FC2_UNKNOWN_FRM_RECD_CRIT: Received an unexpected/unknown FC-2

frame on [chars]
Explanation .
Error Message CTS-2-FSMU_INIT_FAILED: State Machine Infrastructure Initialization

failed ( [chars] )
Explanation .
Error Message CTS-2-IPC_INIT_FAILED: IPC (Inter Process Communication)

Initialization failed ( [chars] )
Explanation CTS Manager has been unable to initialize with the IPC infrastructure.
Error Message CTS-2-LICENSE_UNAVAILABLE: License:[chars] unavailable, service

exiting
Explanation License of [chars] is unavailable. Service will exit now
Recommended Action Please install the license file to continue using the feature.
Error Message CTS-2-MEM_FAILED: Memory operations failed File: [chars] Line [dec]
for size [hex] bytes
Explanation .
OL-26589-01 2-61
Error Message CTS-2-POST_INIT_FAILED: Post-Initialization failed ( [chars] )
Explanation .
Error Message CTS-2-PSS_INIT_FAILED: PSS Infrastructure Initialization failed (

[chars] )
Explanation .
Error Message CTS-2-RBACL_ENFORCEMENT_FAILED: Failed to [chars] RBACL enforcement

on [chars] %lu
Explanation .
Error Message CTS-2-RBACL_LC_INSERT_FAILED: RBACL programming failed for inserted

module [dec]
Explanation .
Error Message CTS-2-RBACL_TCAM_SPACE_NOT_ENOUGH: Not enough free space left on TCAM
Explanation .
Error Message CTS-2-RBACL_UNABLE_PARSE_ACE: Unable to parse RBACL ACE substring:

[chars]
Explanation .
Error Message CTS-2-RBACL_UPDATE_FAILED: Failed to [chars] RBACL [chars]
Explanation .
2-62 OL-26589-01
CTS-3
Error Message CTS-3-DOT1X_AUTHC_FAILED: DOT1X authentication failed on port:

[chars]
Explanation DOT1X authentication failed on the port
CTS-5
Error Message CTS-5-CTS_IP_SGT_MAP_DELETE: IP-SGT mapping deleted for [chars] on

[chars] %lu
Explanation .
Error Message CTS-5-CTS_IP_SGT_MAP_UPDATE: [chars] assigned SGT [chars]
Explanation .
CTS-6
Error Message CTS-6-CTS_FIPS_BYPASS_TEST_PASSED: FIPS bypass test passed for

interface: [chars]
Explanation .
Error Message CTS-6-SXP_BIND_FAIL: CTS SXP socket bind failed for [chars]
Explanation .
Error Message CTS-6-SXP_CONFIG_MODE_MISMATCH: CTS SXP config mode mis-match with

peer [chars] during [chars]
Explanation .
OL-26589-01 2-63
Error Message CTS-6-SXP_CONFIG_VER_MISMATCH: CTS SXP config version mis-match with

peer [chars] during [chars]
Explanation .
Error Message CTS-6-SXP_CONN_PURGED: CTS SXP connection purged: vrf [dec], peer:
[chars]
Explanation .
Error Message CTS-6-SXP_CONN_STATE_CHG_OFF: CTS SXP connection state for peer

[chars] changed to off
Explanation .
Error Message CTS-6-SXP_DEFAULT_PASSWORD_RESET: CTS SXP default password reset
Explanation .
Error Message CTS-6-SXP_DEFAULT_PASSWORD_SET: CTS SXP default password set
Explanation .
Error Message CTS-6-SXP_DEFAULT_SRC_IP_RESET: CTS SXP default source IP address

reset to [chars]
Explanation .
Error Message CTS-6-SXP_DEFAULT_SRC_IP_SET: CTS SXP default source IP address set to

[chars]
Explanation .
2-64 OL-26589-01
Error Message CTS-6-SXP_INTERNAL_FAIL: CTS SXP internal failure
Explanation .
Error Message CTS-6-SXP_LISTEN_FAIL: CTS SXP socket listen failed
Explanation .
Error Message CTS-6-SXP_RX_UNKNOWN_MSG_TYPE: CTS SXP received unknown message type

[chars]
Explanation .
Error Message CTS-6-SXP_RX_UNKNOWN_OPC_TYPE: CTS SXP received unknown opcode type

[dec] for peer [chars]
Explanation .
Error Message CTS-6-SXP_STATE_CHANGE: CTS SXP [chars]
Explanation .
DCEFIB Messages
This section contains the DCEFIB messages.
DCEFIB-SLOT#-0
Error Message DCEFIB-SLOT#-0-CLI_INIT_FAILED: CLI library initialization failed!
Explanation L2mp unicast fib failed to initialize CLI infrastructure's backend library. This is a fatal
error.
OL-26589-01 2-65
Error Message DCEFIB-SLOT#-0-TIMER_INIT_FAILED: Timer subsystem initialization

failed!
Explanation L2mp unicast fib failed to initialize timer library. This is a fatal error.
DCEFIB-SLOT#-2
Error Message DCEFIB-SLOT#-2-DCEFIB_MEM_ALLOC: Memory allocation failed. [chars]
Error Message DCEFIB-SLOT#-2-DCEFIB_RECOVERY_ERROR: Error in Recovery: [chars]
Explanation L2mp unicast fib failed to recover after a re-start. This is a fatal error.
Error Message DCEFIB-SLOT#-2-U2FIB_ERR: [chars]
Explanation L2mp unicast fib encountered an error:
DCEFIB-SLOT#-6
Error Message DCEFIB-SLOT#-6-INITIALIZED: Internal state created [chars]
Explanation L2mp unicast fib has created its internal state stateless/stateful [chars].
Error Message DCEFIB-SLOT#-6-U2FIB_INFO: [chars]
Explanation L2mp unicast fib notice:
Error Message DCEFIB-SLOT#-6-VDC_CREATED: VDC [dec] created
Explanation Request to create VDC [dec] in l2mp unicsat fib was successful.
2-66 OL-26589-01
Error Message DCEFIB-SLOT#-6-VDC_REMOVED: VDC [dec] Removed
Explanation L2mp unicast fib has successfully removed VDC [dec] from its databases.
DEBUGPROXY Messages
This section contains the DEBUGPROXY messages.
DEBUGPROXY-6
Error Message DEBUGPROXY-6-SSM_DEBUG_PROXY_COMMON: SSM debug proxy [chars] [dec]
Explanation General SSM debug proxy information
DEVICE-ALIAS Messages
This section contains the DEVICE-ALIAS messages.
DEVICE-ALIAS-2
Error Message DEVICE-ALIAS-2-ALLOC_FAILED: Memory allocation failed for size:[dec]

type:[dec]
Explanation Memory allocation failed for size [dec] type [dec]
Error Message DEVICE-ALIAS-2-INIT_FAILED: [chars]
Explanation An error occurred during initialization. [chars] indicates the reason for failure.
OL-26589-01 2-67
DEVICE-ALIAS-3
Error Message DEVICE-ALIAS-3-CFS_OPER_FAILED: [chars]
Explanation An error occurred while performing a CFS operation. [chars] indicates the CFS
operation and the reason for failure.
Error Message DEVICE-ALIAS-3-CLEAR_FAILED: [chars]
Explanation An error occurred while clearing the session. [chars] indicates the reason for failure.
Error Message DEVICE-ALIAS-3-COMMIT_FAILED: [chars]
Explanation An error occurred while committing the database. [chars] indicates the reason for
failure.
Error Message DEVICE-ALIAS-3-COMMIT_REJECTED: [chars]
Explanation Commit request received from remote switch is rejected. [chars] indicates the reason
for failure.
Error Message DEVICE-ALIAS-3-LOCK_FAILED: [chars]
Explanation An error occurred while acquiring the lock. [chars] indicates the reason for failure.
Error Message DEVICE-ALIAS-3-LOCK_REJECTED: [chars]
Explanation Lock request received from remote switch is rejected. [chars] indicates the reason for
failure.
2-68 OL-26589-01
Error Message DEVICE-ALIAS-3-MERGE_ACTIVATION_FAILED: [chars]
Explanation An error occurred while activating the merged database. [chars] indicates the reason for
failure.
Error Message DEVICE-ALIAS-3-MERGE_ACTIVATION_REJECTED: [chars]
Explanation Merge activation request received from remote switch is rejected. [chars] indicates the
reason for failure.
Error Message DEVICE-ALIAS-3-MERGE_FAILED: [chars]
Explanation An error occurred during merge operation. [chars] indicates the reason for failure.
Recommended Action Compare device-alias configuration with the other switches in the fabric,
resolve the conflicts if any and commit the changes.
Error Message DEVICE-ALIAS-3-MERGE_MREQ_REJECTED: [chars]
Explanation MREQ received from remote switch is rejected. [chars] indicates the reason for failure.
Error Message DEVICE-ALIAS-3-MERGE_MRESP_REJECTED: [chars]
Explanation MRESP received from remote switch is rejected. [chars] indicates the reason for
failure.
Error Message DEVICE-ALIAS-3-MERGE_VALIDATION_FAILED: [chars]
Explanation An error occurred while validating the merged database. [chars] indicates the reason
for failure.
OL-26589-01 2-69
Error Message DEVICE-ALIAS-3-MERGE_VALIDATION_REJECTED: [chars]
Explanation Merge validation request received from remote switch is rejected. [chars] indicates the
reason for failure.
Error Message DEVICE-ALIAS-3-MTS_OPER_FAILED: [chars]
Explanation An error occurred during MTS operation. [chars] indicates the MTS operation and the
reason for failure.
Error Message DEVICE-ALIAS-3-PSS_OPER_FAILED: [chars]
Explanation An error occurred during PSS operation. [chars] indicates the PSS operation and the
reason for failure.
Error Message DEVICE-ALIAS-3-UNLOCK_FAILED: [chars]
Explanation An error occurred while releasing the lock. [chars] indicates the reason for failure.
Error Message DEVICE-ALIAS-3-UNLOCK_REJECTED: [chars]
Explanation Unlock request received from remote switch is rejected. [chars] indicates the reason for
failure.
Error Message DEVICE-ALIAS-3-VALIDATION_FAILED: [chars]
Explanation An error occurred while validating the database. [chars] indicates the reason for failure.
2-70 OL-26589-01
Error Message DEVICE-ALIAS-3-VALIDATION_REJECTED: [chars]
Explanation Validation request received from remote switch is rejected. [chars] indicates the reason
for failure.
DEVICE-ALIAS-6
Error Message DEVICE-ALIAS-6-CLEAR_FAILED_INFO: [chars]
Explanation An error occurred while clearing the session. [chars] indicates the additional
information regarding failure.
Error Message DEVICE-ALIAS-6-COMMIT_FAILED_INFO: [chars]
Explanation An error occurred while committing the database. [chars] indicates the additional
Error Message DEVICE-ALIAS-6-IMPORT_DEFINITION_CONFLICT: Fcalias [chars] could not

be imported due to definition conflict
Explanation Fcalias [chars] could not be imported due to definition conflict. Either there is already
a device-alias configuration present with the same definition OR another VSAN specified in the
import VSAN range has an fcalias with the same definition.
Recommended Action Resolve the conflict and issue the import command again.
Error Message DEVICE-ALIAS-6-IMPORT_MEMBER_TYPE_CONFLICT: Fcalias [chars] could

not be imported due to having unsupported member type
Explanation Fcalias [chars] could not be imported due to having unsupported member types. Fcalias
can be imported only if it has Port WWN based members..
Recommended Action Make sure that the fcalias has Port WWN based members and issue the import
command again.
OL-26589-01 2-71
Error Message DEVICE-ALIAS-6-IMPORT_NAME_CONFLICT: Fcalias [chars] could not be

imported due to name conflict
Explanation Fcalias [chars] could not be imported due to name conflict. Either there is already a
device-alias configuration present with the same name OR another VSAN specified in the import
VSAN range has an fcalias with the same name.
Recommended Action Resolve the conflict and issue the import command again.
Error Message DEVICE-ALIAS-6-IMPORT_NUM_MEMBERS_CONFLICT: Fcalias [chars] could

not be imported due to having unsupported number of members
Explanation Fcalias [chars] could not be imported due to having unsupported number of members.
Fcalias can be imported only if it has exactly one member..
Recommended Action Make sure that the fcalias has exactly one member and issue the import
command again.
Error Message DEVICE-ALIAS-6-LOCK_FAILED_INFO: [chars]
Explanation An error occurred while acquiring the lock. [chars] indicates the additional information
regarding failure.
Error Message DEVICE-ALIAS-6-MERGE_ACTIVATION_FAILED_INFO: [chars]
Explanation An error occurred while activating the merged database. [chars] indicates the additional
Error Message DEVICE-ALIAS-6-MERGE_VALIDATION_FAILED_BUSY: [chars]
Explanation Merged database could not be validated as some of the applications returned busy.
[chars] indicates information about the application returned busy. There is no user intervention
necessary. The validation would be automatically retried after some time.
Error Message DEVICE-ALIAS-6-MERGE_VALIDATION_REJECTED_BUSY: [chars]
Explanation Merged database received from the remote switch could not be validated as some of the
applications returned busy. [chars] indicates information about the application returned busy. There
is no user intervention necessary. The validation would be automatically retried after some time.
2-72 OL-26589-01
Error Message DEVICE-ALIAS-6-UNLOCK_FAILED_INFO: [chars]
Explanation An error occurred while releasing the lock. [chars] indicates the additional information
regarding failure.
Error Message DEVICE-ALIAS-6-VALIDATION_ABORTED: [chars]
Explanation Local validation is aborted. [chars] indicates the reason why validation is aborted.
DEVICE_TEST Messages
This section contains the DEVICE_TEST messages.
DEVICE_TEST-2
Error Message DEVICE_TEST-2-ASIC_REG_CHECK_FAIL: Module [dec] has failed test

[chars] [dec] times on device [chars] [chars] [dec] [chars] due to error [chars]
Explanation Online diagnostics ASICRegisterCheck test has failed
Error Message DEVICE_TEST-2-COMPACT_FLASH_FAIL: Module [dec] has failed test

[chars] [dec] times on device Compact Flash due to error [chars]
Explanation Online diagnostics CompactFlash test has failed
Error Message DEVICE_TEST-2-CRYPTO_DEVICE_FAIL: Module [dec] has failed test

[chars] [dec] times on Crypto device due to error [chars]
Explanation Online diagnostics CryptoDevice test has failed
Error Message DEVICE_TEST-2-EOBC_FAIL: Module [dec] has failed test [chars] on EOBC
Explanation Online diagnostics EOBC test has failed
OL-26589-01 2-73
Error Message DEVICE_TEST-2-FAN_MOD_FAIL: Module [dec] has failed test [chars]

[dec] times on System Mgmt Bus for chassis [chars] instance [dec] due to error
[chars] error number [hex]
Explanation Online diagnostics SystemMgmtBus test has failed
Error Message DEVICE_TEST-2-MALLOC_FAILURE: Memory allocation failed
Explanation Device Test process could not allocate memory
Error Message DEVICE_TEST-2-MGMT_PORT_SKIP: Module [dec] has skipped test [chars]

on Management Port due to error [chars]
Explanation Online diagnostics ManagementPort test is skipped
Error Message DEVICE_TEST-2-NVRAM_FAIL: Module [dec] has failed test [chars] [dec]
times on device NVRAM due to error [chars]
Explanation Online diagnostics NVRAM test has failed
Error Message DEVICE_TEST-2-OBFL_FAIL: Module [dec] has failed test [chars] [dec]
times on device OBFL due to error [chars]
Explanation Online diagnostics OBFL test has failed
Error Message DEVICE_TEST-2-POWER_SUPPLY_FAIL: Module [dec] has failed test

[chars] [dec] times on System Mgmt Bus for chassis [chars] instance [dec] due to
error [chars] error number [hex]
Explanation Online diagnostics SystemMgmtBus test has failed
Error Message DEVICE_TEST-2-PRIMARY_BOOTROM_FAIL: Module [dec] has failed test

[chars] [dec] times on device Primary BootROM due to error [chars]
Explanation Online diagnostics PrimaryBootROM test has failed
2-74 OL-26589-01
Error Message DEVICE_TEST-2-PWR_MGMT_BUS_FAIL: Module [dec] has failed test

[chars] [dec] times on device Power Mgmt Bus on slot [dec] due to error [chars]
error number [hex]
Explanation Online diagnostics PwrMgmtBus test has failed
Error Message DEVICE_TEST-2-RTC_FAIL: Module [dec] has failed test [chars] [dec]
times on device RealTimeClock due to error [chars]
Explanation Online diagnostics RealTimeClock test has failed
Error Message DEVICE_TEST-2-SECONDARY_BOOTROM_FAIL: Module [dec] has failed test

[chars] [dec] times on device Secondary BootROM due to error [chars]
Explanation Online diagnostics SecondaryBootROM test has failed
Error Message DEVICE_TEST-2-SPINE_CONTROL_BUS_FAIL: Module [dec] has failed test

[chars] [dec] times on device Spine Control Bus on slot [dec] due to error [chars]
error number [hex]
Explanation Online diagnostics SpineControlBus test has failed
Error Message DEVICE_TEST-2-STANDBY_LOOPBACK_TEST_FAIL: Module [dec] has failed

test [chars] [dec] times on [chars] [dec] due to error [chars]
Explanation Online diagnostics StandbyFabricLoopback test has failed
Error Message DEVICE_TEST-2-TWOWIRE_STW_FAIL: Module [dec] has failed test [chars]

[dec] times on Status Bus on slot [dec] due to error [chars]
Explanation Online diagnostics Status bus test has failed
Error Message DEVICE_TEST-2-USB_FAIL: Module [dec] has failed test [chars] [dec]
times on device USB due to error [chars]
Explanation Online diagnostics USB test has failed
OL-26589-01 2-75
DEVICE_TEST-3
Error Message DEVICE_TEST-3-STANDBY_TEST_GET_DIAG_VQI_FAIL: Standby test get diag

vqi failed due to error [hex]
Explanation Device Test StandbyLoopback Test failed get vqi
Error Message DEVICE_TEST-3-STANDBY_TEST_GET_SPINE_FAIL: Standby test get spines

failed due to error [hex]
Explanation Device Test StandbyFabricLoopback Test get spine failed
Error Message DEVICE_TEST-3-STANDBY_TEST_INIT_FAIL: Init for standby test failed

due to error [hex]
Explanation Device Test StandbyFabricLoopback Test failed init process
Error Message DEVICE_TEST-3-STANDBY_TEST_MTS_FAIL: Mts Init for standby test

failed due to error [hex]
Explanation Device Test StandbyFabricLoopback Test failed mts init
Error Message DEVICE_TEST-3-STANDBY_TEST_SOCKET_FAIL: Standby test socket error

[chars]: [hex]
Explanation Device Test StandbyFabricLoopback Test Socket error
DEVICE_TEST-4
Error Message DEVICE_TEST-4-THREAD_CREATE_FAIL: Thread creation failed
Explanation Device Test process could not create threads
2-76 OL-26589-01
Error Message DEVICE_TEST-4-TIMER_CREATE_FAIL: Timer creation failed
Explanation Device Test process could not create timer
Error Message DEVICE_TEST-4-TIMER_START_FAIL: Timer start failed
Explanation Device Test process could not start timer
DEVICE_TEST-5
Error Message DEVICE_TEST-5-NOTICE_TEST: Memory allocation failed notice
DEVICE_TEST-6
Error Message DEVICE_TEST-6-INFO_TEST: Memory allocation failed info
DEV_LOG Messages
This section contains the DEV_LOG messages.
DEV_LOG-3
Error Message DEV_LOG-3-ERROR: [chars]
Explanation Dev_log_lc encountered an error
OL-26589-01 2-77
DEV_LOG-SLOT#-4
Error Message DEV_LOG-SLOT#-4-DEV_LOG_LC_ERROR: [chars]
Explanation Dev_log_lc encountered an error
DFTM Messages
This section contains the DFTM messages.
DFTM-SLOT#-2
Error Message DFTM-SLOT#-2-DFTM_INTF_NOT_FOUND: Interface [chars] not found in

DFTM database [chars]
Explanation DFTM database doesnthavetheinterface.'
Error Message DFTM-SLOT#-2-DFTM_INVALID_FTAG_NUM: DFTM received invalid number of

FTags [dec] from M2RIB
Explanation DFTM recvd invalid number of FTags from M2RIB.
Error Message DFTM-SLOT#-2-DFTM_INVALID_INTF_NUM: DFTM has invalid number of

interfaces [dec] in the DB
Explanation DFTM has invalid number of interfaces in the DB.
Error Message DFTM-SLOT#-2-DFTM_PC_NUM_MEMB_INVALID: DFTM received invalid number of

PC members [dec] from ELTM
Explanation DFTM recvd invalid number of PC members from ELTM.
2-78 OL-26589-01
Error Message DFTM-SLOT#-2-DFTM_VLAN_NOT_FOUND: VLAN [dec] not found in DFTM

database [chars]
Explanation DFTM database doesnthavetheVLAN.'
DFTM-SLOT#-3
Error Message DFTM-SLOT#-3-DFTM_BDDB_PROG_FAILED: DFTM failed to program BDDB

Entry
Explanation DFTM failed to program BDDB Entry
Error Message DFTM-SLOT#-3-DFTM_BDT_PROG_FAILED: DFTM failed to program BD Table

Entry
Explanation DFTM failed to program BD Table Entry
Error Message DFTM-SLOT#-3-DFTM_IFIDX_INVALID_PORT_LAYER: Invalid Port Layer

Received for interface: [chars]
Explanation Invalid Port Layer Received for interface
Error Message DFTM-SLOT#-3-DFTM_IFIDX_INVALID_PORT_MODE: Invalid Port Mode

Explanation Invalid Port Mode Received for interface
Error Message DFTM-SLOT#-3-DFTM_IFIDX_INVALID_PORT_TYPE: Invalid Port Type

Explanation Invalid Port Type Received for interface
OL-26589-01 2-79
Error Message DFTM-SLOT#-3-DFTM_IFIDX_TYPE_ERROR: Failed to get type for

interface: [chars]
Explanation Failed to get type for the interface
Error Message DFTM-SLOT#-3-DFTM_INVALID_PRIM_SEC_VLAN_REQ: DFTM received prim-sec

request for a non-exiting sec vlan [dec] on primary [dec]
Explanation DFTM recvd prim-sec vlan mapping request for a non-existing sec vlan on prim vlan
Error Message DFTM-SLOT#-3-DFTM_L2L3CT_PROG_FAILED: DFTM failed to program L2L3

Consistency Table Entry
Explanation DFTM failed to program L2L3 Consistency Table Entry
Error Message DFTM-SLOT#-3-DFTM_MFT_PROG_FAILED: DFTM failed to program Multicast

FTag Table Entry
Explanation DFTM failed to program Multicast Ftag Table Entry
Error Message DFTM-SLOT#-3-DFTM_SDT_PROG_FAILED: DFTM failed to program SGT DGT

Table Entry
Explanation DFTM failed to program SGT DGT Table Entry
Error Message DFTM-SLOT#-3-DFTM_VTT_PROG_FAILED: DFTM failed to program VLAN

Translation Table Entry for vlan [dec], xlt_vlan [dec] on fe [dec]
Explanation DFTM failed to program VLAN Translation Table
DHCP_SNOOP Messages
This section contains the DHCP_SNOOP messages.
2-80 OL-26589-01
DHCP_SNOOP-2
Error Message DHCP_SNOOP-2-DHCP_SNOOP_PROGRAM_EXIT: [chars]
Explanation DHCP snoop process did an abnormal exit
Error Message DHCP_SNOOP-2-HWPGMFAILURE: Hardware programming has failed: [chars]
Explanation Hardware programming has failed. [chars] explains the reason for the failure.
Error Message DHCP_SNOOP-2-INITFAIL: DHCP Daemon Initialization failed: [chars]
Explanation DHCP Daemon Initialization failed. [chars] explains the reason for the failure.
Error Message DHCP_SNOOP-2-PSSERROR: [chars]
Explanation DHCP Daemon encountered a PSS error. [chars] specifies the context where the failure
occurred.
Error Message DHCP_SNOOP-2-REGPARTREE: Unable to register par tree: [chars]
Explanation Could not register par tree. [chars] explains the reason for the failure.
DHCP_SNOOP-3
Error Message DHCP_SNOOP-3-ALLOCFAIL: Heap Memory allocation failed: [chars]
Explanation DHCP Daemon is out of dynamic memory. [chars] specifies the context where the
failure occurred.
Error Message DHCP_SNOOP-3-ASSERTION_FAILED: [chars]:[dec]
Explanation DHCP Snoop process has hit an assert condition at file [chars] line number [dec]
OL-26589-01 2-81
Error Message DHCP_SNOOP-3-DHCPDENIEDARP: ARP frame denied due to DHCP snooping

binding on interface [chars] vlan [dec] sender mac [chars] sender ip [chars] target
mac [chars] target ip [chars].
Explanation [chars] identifies interface and [dec] identifies the vlan on which ARP packets have
been denied. [chars] identifies sender mac and [chars] identifies the sender ip. [chars] identifies the
target mac and [chars] identifies the target ip.
Error Message DHCP_SNOOP-3-DHCPRATELIMIT: Interface [chars] has been error

disabled due to excessive ingress rate [dec] of DHCP packets.
Explanation [chars] identifies the interface which has been error disabled due to excessive ingress
rate [dec].
Error Message DHCP_SNOOP-3-HWPGMFAILURE: Hardware programming has failed: [chars]
Explanation Hardware programming has failed. [chars] explains the reason for the failure.
Error Message DHCP_SNOOP-3-INVDHCPPKTS: Validation errors while processing DHCP

packet received on interface [chars] vlan [dec] Reason:[chars]. Dropping the
packet
Explanation Validation errors DHCP packet receieved on the interface [chars] vlan [[dec]].
Reason:[chars]
Error Message DHCP_SNOOP-3-MTSERROR: [chars]
Explanation DHCP Daemon encountered an MTS error. [chars] specifies the context where the error
occurred.
Error Message DHCP_SNOOP-3-PKTDROP: Packet dropped. Reason - [chars]
Explanation Dropping the packet. [char] identifies the reason.
2-82 OL-26589-01
Error Message DHCP_SNOOP-3-PKTRECVFAIL: Failed to receive packet - [chars]
Explanation Failed to receive packet. [char] identifies the reason.
Error Message DHCP_SNOOP-3-PKTSENDFAIL: Failed to send packet, - [chars]
Explanation Failed to send packet. [char] identifies the reason.
Error Message DHCP_SNOOP-3-SOCKBINDFAIL: Failed to bind to raw socket - [chars]
Explanation Failed to bind to socket. [char] identifies the reason.
Error Message DHCP_SNOOP-3-SOCKOPENFAIL: Failed to open socket for receiving DHCP

packets - [chars]
Explanation An attempt to open a socket for receiving DHCP packets failed. [char] identifies the
reason.
DHCP_SNOOP-4
Error Message DHCP_SNOOP-4-ACL_DENY: [dec] Invalid ARP messages ([chars]) on

[chars], vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]])
Explanation Packet-count [dec] Invalid ARPs (arp-type [chars]) on interface [chars], vlan [dec].
([sender-mac [chars]/sender-ip [chars]/ target-mac [chars]/target-ip [chars]/ time-of-day [chars]])
Error Message DHCP_SNOOP-4-DHCP_SNOOPING_DENY: [dec] Invalid ARP messages

([chars]) on [chars], vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]])
OL-26589-01 2-83
Error Message DHCP_SNOOP-4-ERROR_DISABLED: Interface [chars] has moved to error

disabled state due to excessive rate [dec] of ingress ARP packets
Explanation Interface [chars] has moved to error disabled state due to excessive rate [dec] of ingress
ARP packets
Error Message DHCP_SNOOP-4-INVALID_ARP: [dec] Invalid ARP messages ([chars]) on

Error Message DHCP_SNOOP-4-SMARTRELAYMAXIPADDR: Smart relay is supported only on

first [dec] IP addresses of the interface [chars].
Explanation There are more than SMARTRELAYMAXIPADDR addresses configured on the

interface. [dec] is the number of IP addresses with which smart relay supported [chars] identifies the
interface. This is an informational message.
Error Message DHCP_SNOOP-4-SMARTRELAYMAXLMT: Smart relay MAX limit [dec] reached.

All subsequent DHCP packets will be relayed with primary address of inbound
interface as relay agent address.
Explanation Smart relay MAX limit reached. [dec] is the number of smart relay bindings This is an
Error Message DHCP_SNOOP-4-SUBNETBCASTRELAYMAXIPADDR: subnet-broadcast relay is

supported only on first [dec] IP addresses of the interface [chars].
Explanation There are more than SUBNETBCASTRELAYMAXIPADDR addresses configured on

the interface. [dec] is the number of IP addresses with which subnet-broadcast relay supported
[chars] identifies the interface. This is an informational message.
2-84 OL-26589-01
DHCP_SNOOP-5
Error Message DHCP_SNOOP-5-ACL_PERMIT: [dec] ARP messages ([chars]) on [chars],

vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]])
Explanation Packet-count [dec] ARPs (arp-type [chars]) on interface [chars], vlan [dec].
Error Message DHCP_SNOOP-5-DHCPHOSTADD: A new Host is [chars] connected to

interface [chars] in VLAN [dec] and is allocated IP address [chars] for [dec] secs.
Explanation A Host identified by [chars] has been added. [chars] identifies the interface. [dec]
identifies the VLAN. [chars] identifies IP address. [dec] identifies the lease time in secs. This is an
Error Message DHCP_SNOOP-5-DHCPLEASEEXPIRE: Lease expired for host [chars] having

IP address [chars] connected to interface [chars] in VLAN [dec] for lease [dec]
secs.
Explanation The lease for host identified by [chars] with IP address [chars] connected to interface
[chars] in VLAN [dec] with lease [dec] has expired.
Error Message DHCP_SNOOP-5-DHCP_SNOOPING_PERMIT: [dec] ARP messages ([chars]) on

Explanation Packet-count [dec] ARPs (arp-type [chars]) on interface [chars], vlan [dec].
Error Message DHCP_SNOOP-5-VLANDISABLE: DHCP Snooping disabled on vlan [dec]
Explanation DHCP Snooping was disabled on a given vlan. [dec] is the VLAN-ID that identifies the
vlan. This is an informational message.
Error Message DHCP_SNOOP-5-VLANENABLE: DHCP Snooping enabled on vlan [dec]
Explanation DHCP Snooping was enabled on a given vlan. [dec] is the VLAN-ID that identifies the
vlan. This is an informational message.
OL-26589-01 2-85
DHCP_SNOOP-6
Error Message DHCP_SNOOP-6-DAIVLANDISABLE: DAI disabled on vlan [dec]
Explanation Dynamic ARP Inspection was disabled on a given vlan. [dec] is the VLAN-ID that
identifies the vlan. This is an informational message.
Error Message DHCP_SNOOP-6-DAIVLANENABLE: DAI enabled on vlan [dec]
Explanation Dynamic ARP Inspection was enabled on a given vlan. [dec] is the VLAN-ID that
identifies the vlan. This is an informational message.
Error Message DHCP_SNOOP-6-DHCPBINDSYNC: Binding entry with MAC [chars] interface

[chars] VLAN [dec] IP address [chars] and lease time [dec] secs is synced.
Explanation Binding entry identified by [chars] has been synced. [chars] identifies the interface.
[dec] identifies the VLAN. [chars] identifies IP address. [dec] identifies the lease time in secs. This
is an informational message.
Error Message DHCP_SNOOP-6-DHCPEXIT: DHCP Daemon shutting down gracefully.
Explanation DHCP Daemon is shutting down gracefully. This is an informational message.
Error Message DHCP_SNOOP-6-DHCPPERMITTEDARP: ARP frame permitted due to DHCP

snooping binding on interface [chars] vlan [dec] sender mac [chars] sender ip
[chars] target mac [chars] target ip [chars].
Explanation [chars] identifies interface and [dec] identifies the vlan on which ARP packets have
been permitted. [chars] identifies sender mac and [chars] identifies the sender ip. [chars] identifies
the target mac and [chars] identifies the target ip.
Error Message DHCP_SNOOP-6-DHCPPKTFWD: Gracefully forwarding DHCP packet. Reason:

[chars]
Explanation Gracefully forwarding DHCP packet. reason [chars]
2-86 OL-26589-01
Error Message DHCP_SNOOP-6-DHCPUP: DHCP Daemon Up.
Explanation DHCP Daemon was created successfully and is up and running. This is an
Error Message DHCP_SNOOP-6-INFO: [chars]
Explanation An event during switchover. [chars] explains the reason for the failure.
Error Message DHCP_SNOOP-6-INTFDISABLE: IP Src Guard disabled on intf [chars]
Explanation IP Src Guard was disabled on a given intf. [chars] is the intf-ID string that identifies
the intf. This is an informational message.
Error Message DHCP_SNOOP-6-INTFENABLE: IP Src Guard enabled on intf [chars]
Explanation IP Src Guard was enabled on a given intf. [chars] is the intf-ID string that identifies the
intf. This is an informational message.
Error Message DHCP_SNOOP-6-NONDHCPPKTFWD: Non DHCP packet with src port:[dec] dst
port:[dec] on intf:[chars] vlan:[dec]. Forwarding on [chars]
Explanation Non DHCP packet arrived with UDP src/dst ports [dec], [dec] on interface [chars], vlan
[dec]. Forwarding the packet on [chars]
Error Message DHCP_SNOOP-6-OPT82INSTFAIL: [chars] [chars]
Explanation Insertion of Option82 suboptions failed. [chars] tells the failure. [chars] explains the
reason for failure. This is an informational message.
DIAGCLIENT Messages
This section contains the DIAGCLIENT messages.
OL-26589-01 2-87
DIAGCLIENT-2
Error Message DIAGCLIENT-2-DIAG_BOOTUP_COMPLETE: Module <[dec]
Explanation Bootup Test completed
Recommended Action Nothing to be done if the test reports SUCCESS otherwise copy the error
message exactly as it appears on the console, gather the output of show tech-support, and contact
your Cisco technical support representative with the gathered information
Error Message DIAGCLIENT-2-EEM_ACTION_HM_SHUTDOWN: Test <[chars]
Explanation Informational Syslog
Error Message DIAGCLIENT-2-PSS_READ_FAILURE: Read from PSS failed on Module <[dec]
Explanation Read operation from PSS store failed
Error Message DIAGCLIENT-2-PSS_WRITE_FAILURE: Write to PSS failed on Module <[dec]
Explanation Write operation on PSS store failed
DIAGCLIENT-3
Error Message DIAGCLIENT-3-ONDEMAND_FAIL_EXCESS: Module <[dec]
Explanation Ondemand test has failed more than configured number of times
Recommended Action Copy the error message exactly as it appears on the console, gather the output
of show tech-support, and contact your Cisco technical support representative with the gathered
information
DIAGCLIENT-4
Error Message DIAGCLIENT-4-LC_OFFLINE_FOR_CURR_SLOT: Received LC offline event for

the current slot:[dec]. Ignoring it
2-88 OL-26589-01
Error Message DIAGCLIENT-4-MTS_SEND_FAILURE: MTS send failed, mts_opc: [chars],

dest slot: [dec], dest SAP: [dec], error-id: [hex]
Explanation MTS send reports failure
DIAGCLIENT-5
Error Message DIAGCLIENT-5-CALLOC_FAILURE: Memory allocation failed
Explanation DiagClient process could not allocate memory
Error Message DIAGCLIENT-5-DIAG_ONDEMAND_TEST_FINISH: Module [dec]: Ondemand test

[chars] finished
Error Message DIAGCLIENT-5-DIAG_ONDEMAND_TEST_START: Module [dec]: Ondemand test

[chars] started
Error Message DIAGCLIENT-5-DIAG_ONDEMAND_TEST_STOP: Module [dec]: Ondemand test

[chars] stopped
Error Message DIAGCLIENT-5-DIAG_SCHED_COMPLETE: Module <[dec]
Explanation A scheduled Test was completed
Error Message DIAGCLIENT-5-ONDEMAND_FAIL: Module <[dec]
Explanation The specified test has reported FAILURE in this Iteration
OL-26589-01 2-89
Error Message DIAGCLIENT-5-ONDEMAND_SUCCESS: Module <[dec]
Explanation The specified test has reported SUCCESS in this Iteration
DIAGCLIENT-7
Error Message DIAGCLIENT-7-DIAG_HM_FAIL: Module <[dec]
Explanation A Health Monitoring Test has reported failure
Recommended Action Ensure the line card is firmly in the slot, reseat if necessary, and attempt to run
the test again if the line card is not seated properly in the slot. If the line card was properly seated
in the slot, copy the error message exactly as it appears on the console, gather the output of show
tech-support, and contact your Cisco technical support representative with the gathered information.
Error Message DIAGCLIENT-7-PER_PORT_TEST_FAIL: Module <[dec]
Explanation Per Port Test has failed on the above all ports
DIAGMGR Messages
This section contains the DIAGMGR messages.
DIAGMGR-2
Error Message DIAGMGR-2-MTS_SEND_FAILURE: MTS send failed, mts_opc: [chars], dest

slot: [dec], dest SAP: [dec], error-id: [hex]
Explanation MTS send reports failure
Error Message DIAGMGR-2-PSS_DELETE_FAILURE: Read from PSS failed on Module <[dec]
Explanation Read operation from PSS store failed
Error Message DIAGMGR-2-PSS_WRITE_FAILURE: Write to PSS failed on Module <[dec]
Explanation Write operation on PSS store failed
2-90 OL-26589-01
DIAGMGR-3
Error Message DIAGMGR-3-DIAG_MAJOR_DEFECT: Module <[dec]
Explanation A major error was detected during diagnostic testing
Recommended Action Re-seat the card and retry the test. If the same result occurs after reseating the
card and retrying the test, copy the error message exactly as it appears on the screen and gather the
output of show tech-support and any other relevant information. Contact your technical support
representative with the gathered information.
Error Message DIAGMGR-3-DIAG_MINOR_DEFECT: Module <[dec]
Explanation A minor error was detected during diagnostic testing
Recommended Action Re-seat the card and retry the test. If the same result occurs after reseating the
card and retrying the test, copy the error message exactly as it appears on the screen and gather the
output of show tech-support and any other relevant information. Contact your technical support
representative with the gathered information
Error Message DIAGMGR-3-GET_CURR_SLOT_FAIL: Failed to get the current slot for the
process. Error:[chars]
Explanation The process initialization failed to get the current slot.
Recommended Action This is an informational message stating that a process initialization failure.
DIAGMGR-4
Error Message DIAGMGR-4-CURR_SLOT_OFFLINE: Recevied an LC offline event for the

current slot:[dec]. Ignoring it
Explanation The process received an offline event for the slot it is running. Ignoring it.
Recommended Action This is an informational message stating that an unexpected event has been
encountered.
Error Message DIAGMGR-4-DISRPT_TST_START: Starting Test <[chars]
Explanation Starting a Disruptive Test can disturb the systemsnormalfunctionality'
Recommended Action Reset target module
OL-26589-01 2-91
Error Message DIAGMGR-4-FIXED_INTRVL_CHANGED: The users are not allowed to change

monitoring interval of Test <[chars]
Explanation The specified health monitoring test interval is not user-configurable and therefore
cannot be changed
Recommended Action Nothing. The specific health monitoring interval is not user- configurable by
design so nothing can be done to change the interval
DIAGMGR-5
Error Message DIAGMGR-5-BOOTUP_CONF: Diagnostic Bootup Level: <[chars]
Explanation Current Diagnostic BootUp Level being configure or changed
Error Message DIAGMGR-5-CALLOC_FAILURE: Memory allocation failure
Explanation Memory allocation in a call to malloc/calloc has failed
Error Message DIAGMGR-5-CHANGE_ALWAYS_HM: Health Monitoring test <[chars]
Explanation The specified health monitoring test must be run and cannot be disabled
Recommended Action Nothing. The specific health monitoring test cannot be disabled by design. The
system is working properly.
Error Message DIAGMGR-5-HM_START: Health monitoring test <[chars]
Explanation Health Monitoring Test started
Error Message DIAGMGR-5-HM_STOP: Disabling health monitoring test <[chars]
Explanation Health Monitoring Test has been stopped It can be enabled through the diagnostic
monitor..... command
2-92 OL-26589-01
Error Message DIAGMGR-5-INTRVL_INCORRECT: Monitoring Interval is less than minimum

of [dec] seconds required for Module <[dec]
Explanation Health Monitoring cannot be enabled for the specified test because the interval for the
test has been incorrectly set
Recommended Action The system is working properly and no user action is required. If you want to
specify a smaller testing interval, the error message text provides the lowest possible configurable
interval for the specified monitoring interval
Error Message DIAGMGR-5-MODULE_MISSING: Diagnostic command issued on non-existing

Module <[dec]
Explanation A line card could not be located in a slot where a diagnostic action was requested
Recommended Action Ensure the targeted line card is properly seated in the specified slot. If the line
card is properly seated, ensure the correct slot was indicated in the command-line interface. If the
line card is well-seated and the correct slot was specified, copy the error message exactly as it
appears on the screen as well as the output of show tech-support and paste the output into a separate
file. Contact your technical support representative with the gathered information
Error Message DIAGMGR-5-NONHM_AS_HM: The Test <[chars]
Explanation Non-HM test cannot be scheduled to run as a Health Monitoring test
DIAGMGR-6
Error Message DIAGMGR-6-BOOTUP_DIAG_OK: Module <[dec]
Explanation The diagnostic tests did not detect any error on the card.
Recommended Action This is an informational message stating that the line card passed the
diagnostic tests.
Error Message DIAGMGR-6-BOOTUP_TEST_STARTED: Module <[dec]
Explanation Starting bootup testing for above module
DIAG_PORT_LB Messages
This section contains the DIAG_PORT_LB messages.
OL-26589-01 2-93
DIAG_PORT_LB-2
Error Message DIAG_PORT_LB-2-FIPS_RANDOM_ERROR: Random Number Generation Failure
Explanation Random Number genration failed in FIPS module
Error Message DIAG_PORT_LB-2-LCM_RESP_SEND_FAILURE: LC Inserted request response

send to Module Manager failed . Error:[chars]
Explanation Failed to send the response for LC insertion to Module Manager.
Error Message DIAG_PORT_LB-2-LIF_GET_ERROR: [chars]([dec]) [chars] Error:[chars]
Explanation Port Loopback test process failed to get Diagnostic LIF id
Error Message DIAG_PORT_LB-2-MALLOC_FAILURE: [chars]([dec]) Memory allocation

failed.
Explanation Port Loopback test process could not allocate memory
Error Message DIAG_PORT_LB-2-PORTLOOPBACK_TEST_FAIL: Module:[dec]

Test:PortLoopback failed [dec] consecutive times. Faulty module:[chars] [chars]
Error:[chars]
Explanation PortLoopback test failed on the module consecutively
Error Message DIAG_PORT_LB-2-PROC_INIT_FAILURE: [chars]([dec]) [chars]

Error:[chars]
Explanation Port Loopback test process failed in process initialization
2-94 OL-26589-01
Error Message DIAG_PORT_LB-2-REWRITE_ENGINE_LOOPBACK_TEST_FAIL: Module:[dec]

Test:RewriteEngine Loopback failed [dec] consecutive times. Faulty module:[chars]
[chars] Error:[chars]
Explanation Rewrite Engine Loopback test failed on the module consecutively
Error Message DIAG_PORT_LB-2-SNAKE_TEST_LOOPBACK_TEST_FAIL: Module:[dec]

Test:SnakeLoopback failed [dec] consecutive times. Faulty module:[chars] affected
ports:[chars] Error:[chars]
Explanation Snake test failed on the module consecutively
DIAG_PORT_LB-3
Error Message DIAG_PORT_LB-3-DIAG_FWD_PATH_SETUP_FAILURE: [chars]. Module:[dec]

Error:[chars].
Explanation Forwarding path setup for port loopback tests failed
Error Message DIAG_PORT_LB-3-DIAG_PKT_SEND_FAILURE: [chars]([dec]) [chars].

Error:[chars]
Explanation Port Loopback test process failed to send loopback packets.
Error Message DIAG_PORT_LB-3-FSM_LIB_ERROR: [chars]([dec]) [chars]. Error:[chars]
Explanation Port Loopback test process failed in MTS API.
Error Message DIAG_PORT_LB-3-GET_DIAG_BD_FAIL: [chars]([dec]) Failed to get the BD

for Diag VLAN:[dec]. Error:[chars].
Explanation Failed to get the BD corresponding to the Diag VLAN
OL-26589-01 2-95
Error Message DIAG_PORT_LB-3-IFINDEX_LIB_FAILURE: [chars]([dec]) [chars]

[chars]:[hex] [chars] [chars]
Explanation Port Loopback test process failed in if_index library API
Error Message DIAG_PORT_LB-3-INVALID_TEST_REQUEST: [chars]([dec]) [chars]:[dec]
Explanation Port Loopback test process failed to get test request info.
Error Message DIAG_PORT_LB-3-INVALID_TEST_RUN: [chars]([dec]) [chars]:[dec]
Explanation Port Loopback test process failed to get the current test run information
Error Message DIAG_PORT_LB-3-PDB_LIB_API_ERROR: Failed to [chars]. Error:[dec].
Explanation The port loopback test was not able to get chassis info
Error Message DIAG_PORT_LB-3-PIXM_LIB_ERROR: [chars]([dec]) Failed to convert

[chars]:[hex] to [chars]. Error:[chars]
Explanation Port Loopback test process failed to convert port ifindex <-
Error Message DIAG_PORT_LB-3-PORT_CLIENT_LIB_ERROR: [chars]([dec]) [chars].

Error:[chars]
Explanation Port Loopback test process failed in Port Client API.
Error Message DIAG_PORT_LB-3-RESULT_ADD_FAILURE: [chars]([dec]) [chars]:[dec]
Explanation Port Loopback test process failed to add the port test result
2-96 OL-26589-01
Error Message DIAG_PORT_LB-3-RESULT_SEND_FAILURE: [chars]([dec]) [chars]
Explanation Port Loopback test process failed to send the test results
Error Message DIAG_PORT_LB-3-RW_ENGINE_LOOPBACK_TEST_SPINE_PATH_FAIL:

Module:[dec] Test:RewriteEngine Loopback Spine path:[dec] failed [dec]
consecutive times. Error:[chars]
Explanation Rewrite Engine Loopback test failed on the spine path consecutively
Error Message DIAG_PORT_LB-3-SOCKET_ERROR: [chars]([dec]) [chars] Error:[chars]
Explanation Port Loopback test process failed in socket operations
Error Message DIAG_PORT_LB-3-STATS_LIB_ERROR: [chars]([dec]) [chars]:[dec]
Explanation Port Loopback test process failed in stats infra lib API.
Error Message DIAG_PORT_LB-3-TEST_RES_SEND_FAIL: Failed to send [chars] test

results back to Diagnostics Infrastucture. Error:[chars].
Explanation The port loopback test was not able to send the test results
Error Message DIAG_PORT_LB-3-TIMER_LIB_ERROR: [chars]([dec]) [chars]
Explanation Port Loopback test process timer handling failure.
Error Message DIAG_PORT_LB-3-VLAN_ERROR: [chars]([dec]) [chars] Error:[chars]
Explanation Port Loopback test process failed to get Diagnostic VLAN info
OL-26589-01 2-97
Error Message DIAG_PORT_LB-3-VQI_GET_FAIL: Failed to get the Diag VQi from XBM.
Error:[chars]
Explanation Rewrite Engine Loopback test failed to get the Diag VQi from XBAR Mgr
Error Message DIAG_PORT_LB-3-XBM_CFG_REQ_FAIL: Failed to conigure the XBAR mask

while running the RewriteEngineLoopback test. Error:[chars]. Module:[dec] could
have gone offline
Explanation Rewrite Engine Loopback test failed to set the XBAR mask while running the test. The
target module could have gone offline
DIAG_PORT_LB-4
Error Message DIAG_PORT_LB-4-MTS_LIB_ERROR: [chars]([dec]) [chars].

Warning:[chars]
Explanation Port Loopback test process failed in MTS API.
Error Message DIAG_PORT_LB-4-PORT_CFG_REQ_SEND: [chars]([dec]) Failed to send

request to configure port ifindex:[dec] for port loopback test
Explanation Failed to configure/restore the port to do/cleanup port loopback testing
DIAG_PORT_LB-5
Error Message DIAG_PORT_LB-5-DIAG_PORT_LB_DISABLED: DIAG_PORT_LB Disabled
Explanation DIAG_PORT_LB Service Disabled
Error Message DIAG_PORT_LB-5-DIAG_PORT_LB_ENABLED: DIAG_PORT_LB Enabled
Explanation DIAG_PORT_LB Service nabled
2-98 OL-26589-01
DMM Messages
This section contains the DMM messages.
DMM-SLOT#-5
Error Message DMM-SLOT#-5-LOG_ERR_DMM_NEW_NPORT_SRVR_ZONE: Job Id:%Ld VSAN :[dec]

New N-Port FCID :[hex] Server FCID:[hex] are in the same zone. ALERT!!
Explanation A New N-Port has come up which is zoned in the same zone as the Server
Error Message DMM-SLOT#-5-LOG_ERR_DMM_NEW_NPORT_STG_ZONE: Job Id:%Ld VSAN :[dec]

New N-Port FCID :[hex] Storage FCID:[hex] are in the same zone. ALERT!!
Explanation A New N-Port has come up which is zoned in the same zone as the Storage
Error Message DMM-SLOT#-5-LOG_ERR_DMM_SRVR_RSCN: Job Id:%Ld Server N-Port

pWWN:0x%Lx [chars]
Explanation An RSCN event was received for the Server associated with a Job
Error Message DMM-SLOT#-5-LOG_ERR_DMM_STG_RSCN: Job Id:%Ld N-Port pWWN:0x%Lx

Storage:[chars] [chars]
Explanation An RSCN event was received for the Storage associated with a Job
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_COMPLETE: Job Id:%Ld NumSession:[dec]
Explanation Event indicating the completion of a Data Migration Job
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_ERROR_LOST_SSM_PEER_CONNECTION: Job

Id:%Ld NumSession:[dec]
Explanation Event indicating the Suspension of Data Migration Job due to loss in ip connectivity to
peer ssm
OL-26589-01 2-99
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_ERROR: Job Id:%Ld NumSession:[dec]
Explanation Event indicating the Suspension of Data Migration Job
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_FINISH: Job Id:%Ld NumSession:[dec]
Explanation Event indicating Finish-request for a Method-2 Data Migration Job
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_START: Job Id:%Ld NumSession:[dec]
Explanation Event indicating the start of a Data Migration Job
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_STOP: Job Id:%Ld NumSession:[dec]
Explanation Event indicating that the Data Migration Job was stopped by Administrator
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_TCP_CONNECTION_DOWN: Job Id:%Ld lost

connection to peer [chars]. Job may be RESET
Explanation Event indicating IP Connectivity loss to peer SSM. Affected Job maybe be RESET
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_COMPLETE: Job Id:%Ld

NumSession:[dec]
Explanation Event indicating the completion of a Data Migration Job Verification
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_ERROR: Job Id:%Ld NumSession:[dec]
Explanation Event indicating the Suspension of Data Migration Job Verification due to an error
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_START: Job Id:%Ld NumSession:[dec]
Explanation Event indicating the start of a Data Migration Job Verification
2-100 OL-26589-01
Error Message DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_STOP: Job Id:%Ld NumSession:[dec]
Explanation Event indicating the Suspension of Data Migration Job Verification by the user
DOT1X Messages
This section contains the DOT1X messages.
DOT1X-2
Error Message DOT1X-2-DOT1X_INIT: Dot1x unable to start
Explanation The system failed to create the Dot1x process
DOT1X-3
Error Message DOT1X-3-DOT1X_ENABLE_STATIC_MAC_FOUND: Static mac found on an

interface [chars], dot1x enable failed in ethpm pre-cfg
Explanation Dot1x is not supported on an interface which is configured with static mac entries
Recommended Action Remove the static mac entry on the interface
Error Message DOT1X-3-ERR_SPANDST: It is configured as a SPAN Dest port.
Explanation Dot1x and SPAN Dest ports are mutually exclusive features.
Recommended Action Disable SPAN destination port configuration first before reconfiguring Dot1x
on the port.
Error Message DOT1X-3-INVALID_INPUT: Invalid on interface [chars].
Explanation The Dot1x interface parameter is out of the specified range or is invalid.
Recommended Action Refer to the CLI help documentation to determine the valid 802.1x parameters.
Error Message DOT1X-3-MEM_UNAVAIL: perform the 802.1X action.
Explanation Insufficient system memory is available to perform the Dot1x Authentication.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration.
OL-26589-01 2-101
Error Message DOT1X-3-NOT_DOT1X_CAPABLE: [chars].
Explanation Dot1x Authentication can only be enabled on physical Ethernet interfaces.
Recommended Action Enable Dot1x Authentication on physical Ethernet interfaces only.
Error Message DOT1X-3-SECURE_MAC_INSERT_FAILED: address [chars] could not be secured

on interface [chars]
Explanation The interface specified in the error message could not secured supplicant mac. The port
has been Error disabled.
Recommended Action Mac address could not be added into mac address table. Enter the <Cmd
Error Message DOT1X-3-SECURITY_VIOLATION: New MAC address [chars] is seen on

interface [chars] in [chars] mode
Explanation The port on the interface specified in the error message is configured in single host
mode. Any new host that is detected on the interface is treated as a security violation. The port has
been Error disabled.
Recommended Action Ensure that the port is configured to use only one host. Enter the <Cmd
Error Message DOT1X-3-SM_INIT: Internal error while initializing state machine

[chars], state [chars]: [chars]
Explanation An attempt was made to initialize an invalid state machine.
Recommended Action Initialize dot1x state machine
DOT1X-4
Error Message DOT1X-4-BADEVENT: Event [chars] is invalid for the current state
[chars]: [chars] [chars]
Explanation An attempt was made to post an event to a state machine that is invalid for the current
state.
Recommended Action Initialize dot1x state machine
Error Message DOT1X-4-MAB_DISABLED_ON_PCM: Interface [chars] is a member of

portchannel, MAB is not supported on this port
Explanation MAB is not supported on portchannel member port
Recommended Action To enable MAB make sure that port is not member of portchannel
2-102 OL-26589-01
Error Message DOT1X-4-MAB_DISABLED: Interface [chars] is in Trunk mode, MAB is not

supported on this port
Explanation MAB is not supported on Trunk port
Recommended Action To enable MAB make sure that port is not in trunk mode
Error Message DOT1X-4-MULTIHOST_ON_PCM: Interface [chars] is a member of

portchannel, dot1x host mode will be multi-host and changing it to single-host
mode wontbesupported'
Explanation Current Port is a member of portchannel, so dot1x host mode has to be in multi-host
mode.
Recommended Action To change host mode, ensure that port is not a member of portchannel
Error Message DOT1X-4-PSEC_ON_PCM: Interface [chars] is a member port or

portchannel interface with port security configration
Explanation Dot1x is not supported on member ports or port channel with port security
configuration
Recommended Action Remove port security configuration on the member port or port channel
interface
Error Message DOT1X-4-STOPPED: Event [chars] ignored because the state machine is
stopped: [chars] [chars]
Explanation An attempted was made to post an event to a state machine that has already been
stopped.
Recommended Action An internal error has occurred with the state machine. The traceback should
indicate the guilty party.
Error Message DOT1X-4-TO_MULTIHOST: Interface [chars] is in trunk mode, dot1x host

mode will be multi-host and changing it to single-host mode wontbesupported'
Explanation Current Port is in trunk mode, so dot1x host mode has to be in multi-host mode.
Recommended Action To change host mode, ensure that port is not in trunk mode
DOT1X-5
Error Message DOT1X-5-DOT1X_DISABLED: dot1x Disabled
Explanation Dot1x Service Disabled
OL-26589-01 2-103
Error Message DOT1X-5-DOT1X_ENABLED: dot1x Enabled
Explanation Dot1x Service Enabled
Error Message DOT1X-5-DOT1X_NOTIF: [chars]
Explanation Dot1x Notification
Error Message DOT1X-5-INVALID_MAC: broadcast or multicast mac address) [chars] is

trying to authenticate.
Authentication using 802.1x is not allowed for zero, broadcast, and multicast source
Explanation
MAC addresses.
Recommended Action Connect a Dot1x supported Host to the Dot1x enabled port.
Error Message DOT1X-5-PAC_STATUS: PAC provisioning for the server [chars] through
the vrf [chars] [chars]
Explanation PAC provisioning status
Error Message DOT1X-5-SESSION_CREATION: Dot1x authentication session initiated in

interface [chars] using authentication method [chars]
Explanation Dot1x authentication session has been created after successful authentication of
supplicant
Error Message DOT1X-5-SESSION_TERMINATION: Dot1x authentication session in

interface [chars] using authentication method [chars] is terminated because of
[chars] and port moved to [chars] state
Explanation Dot1x authentication session has been terminated
Error Message DOT1X-5-STATUS: Dot1x interface [chars] status changed from [chars]
to [chars]
Explanation Dot1x authenticator has changed its internal state
2-104 OL-26589-01
DOT1X-6
Error Message DOT1X-6-NOT_DOT1X_CAPABLE_SAT_FABRIC: [chars].
Explanation Dot1x Authentication can only be enabled on physical Ethernet interfaces.
Recommended Action Enable Dot1x Authentication on physical Ethernet interfaces only.
DPP_DEBUG Messages
This section contains the DPP_DEBUG messages.
DPP_DEBUG-2
Error Message DPP_DEBUG-2-DPP_CRIT: [DPP[dec]] [chars]
Explanation A DPP generated a critical message
DPVM Messages
This section contains the DPVM messages.
DPVM-2
Error Message DPVM-2-ALLOC_FAILED: Memory allocation failed for size:[dec] for

[chars]
Explanation Memory allocation failed for size [dec] for [chars]
Error Message DPVM-2-DPVM_DUPL_REJECT: [chars]
Explanation Rejected duplicate pwwn query
Recommended Action Dpvm overwrite-duplicate-pwwn
OL-26589-01 2-105
DPVM-3
Error Message DPVM-3-DB_ERR: [chars]
Explanation An error occured during an DPVM database operation. [chars] indicates the reason for
the error
Error Message DPVM-3-DDAS_MODE_INVALID: [chars]
Explanation DDAS mode Invalid. [chars]
Recommended Action Flip DDAS mode
Error Message DPVM-3-INIT_FAIL: [chars]
Explanation An error happened during DPVM Initialization. [chars] indicates the reason for failure
Error Message DPVM-3-MTS_ERR: [chars]
Explanation An error occured in processing of an MTS message. [chars] indicates the error that
occured
Error Message DPVM-3-PSS_ERR: [chars]
Explanation An error occured during an DPVM PSS operation. [chars] indicates the PSS operation
DPVM-4
Error Message DPVM-4-ACTIVATION_FAIL: [chars]
Explanation Activation of DPVM device mappings failed due to [chars]
Recommended Action Correct the error and reactivate database again
2-106 OL-26589-01
Error Message DPVM-4-FEATURE_DISABLED: [chars]
Explanation DPVM is unavailable and disabled now
DPVM-6
Error Message DPVM-6-FEATURE_ENABLED: [chars]
Explanation DPVM is available and enabled now
Error Message DPVM-6-INFO: [chars]
Explanation An event happened that affects DPVM. [chars] indicates the event
DSTATS Messages
This section contains the DSTATS messages.
DSTATS-2
Error Message DSTATS-2-PSS_INIT_FAIL: pss initialization failed due to error: [hex]
Explanation Dstats process pss initialization failure due to error [hex].
Recommended Action Collect more information using command

showflash'.Seepsssystemerrorcodesforreason.'
DSTATS-3
Error Message DSTATS-3-PSS_CREATE_FAIL: pss create runtime database failed due to

error: [hex]
Explanation Dstats process pss create runtime database failure due to error [hex].

OL-26589-01 2-107
Error Message DSTATS-3-PSS_DELETE_FAIL: pss delete runtime entry key:[hex] failed

due to error: [hex]
Explanation Dstats process pss delete runtime entry key [hex] failure due to error [hex].

Error Message DSTATS-3-PSS_MAX_KEY_FAIL: pss set runtime max key failed due to
error: [hex]
Explanation Dstats process pss set runtime max key failure due to error [hex].

Error Message DSTATS-3-PSS_MAX_VALUE_FAIL: pss set runtime max value failed due to
error: [hex]
Explanation Dstats process pss set runtime max value failure due to error [hex].

Error Message DSTATS-3-PSS_OPEN_FAIL: pss open runtime database failed due to

error: [hex]
Explanation Dstats process pss open runtime database failure due to error [hex].

Error Message DSTATS-3-PSS_RELOAD_FAIL: pss reload runtime database failed due to

error: [hex]
Explanation Dstats process pss reload runtime database failure due to error [hex].

Error Message DSTATS-3-PSS_SNAPSHOT_DEBUG_FAIL: pss snapshot runtime debug to

uri:[chars] failed due to error: [hex]
Explanation Dstats process pss snapshot of runtime debug to uri [string] failed due to error [hex].

2-108 OL-26589-01
Error Message DSTATS-3-PSS_SNAPSHOT_FAIL: pss snapshot runtime to uri:[chars]

failed due to error: [hex]
Explanation Dstats process pss snapshot of runtime to uri [string] failed due to error [hex].

Error Message DSTATS-3-PSS_STORE_FAIL: pss store runtime entry key:[hex] val:[hex]

Explanation Dstats process pss store runtime entry key [hex] value [hex] failure due to error [hex].

ELTMC Messages
This section contains the ELTMC messages.
ELTMC-SLOT#-2
Error Message ELTMC-SLOT#-2-ELTMC_GENERIC_DEBUG: [chars]
Explanation Logging some generic debugging info
Error Message ELTMC-SLOT#-2-ELTMC_INTERFACE_INTERNAL_ERROR: Internal error:

[chars]:[chars], collect output of show tech-support eltm
Explanation ELTM hit a internal error. Collect show tech-support eltm for futher analysis.
Error Message ELTMC-SLOT#-2-ELTMC_INTERNAL_ERROR: Internal error: [chars], collect

output of show tech-support eltm
Error Message ELTMC-SLOT#-2-ELTMC_INTF_NOT_FOUND: Interface [chars] not found in

ELTM database [chars]
Explanation ELTM database doesnthavetheinterface.'
OL-26589-01 2-109
Error Message ELTMC-SLOT#-2-ELTMC_INTF_NOT_SUPP: Interface [chars] not supported

by ELTM [chars]
Explanation ELTM doesntsupporttheinterfaceforthespecifiedoperation'
Error Message ELTMC-SLOT#-2-ELTMC_INTF_TO_LTL: Failed to get LTL for interface

[chars] return status [chars]
Explanation ELTM Failed to get LTL for interface. Packets received on this interface might not be
handled correctly by the forwarding engine
Error Message ELTMC-SLOT#-2-ELTMC_INTF_TO_SLOT: Failed to get slot for interface

[chars] return status [chars]
Explanation ELTM Failed to get Slot for interface. Port-channels and L2 Learning might be effected
Error Message ELTMC-SLOT#-2-ELTMC_LDB_REALLOC_FAIL: Failed to realloc LDB in

forwarding engine for interface [chars] for non-XL linecard
Explanation ELTM Failed to allocate L2 LIF entries in forwarding engine. ISSU failed for this VDC.
Shutdown the interfaces
Error Message ELTMC-SLOT#-2-ELTMC_LTL_ISSUE_EXT_COMP: Critical LTL clean-up issue

(either ETHPM/PIXM) [chars]
Explanation LTL didnt get cleaned-up either bcos of ETHPM not sending DELETE or PIXM issuing
a duplicate LTL
Error Message ELTMC-SLOT#-2-ELTMC_NONXL_LDB_REALLOC_FAIL: Failed to realloc LDB in

forwarding engine for certain interfaces for non-XL linecard
Shutdown the interfaces
2-110 OL-26589-01
Error Message ELTMC-SLOT#-2-ELTMC_L2_LIF_ALLOC_FAIL_INTF: Failed to allocate L2 LIF

entries in forwarding engine for interfac [chars]
Explanation ELTM Failed to allocate L2 LIF entries in forwarding engine. This will effect Layer 2
and Layer 3 forwarding for the interface
Error Message ELTMC-SLOT#-2-ELTMC_L2_LIF_ALLOC_FAIL_VDC: Failed to allocate L2 LIF

entries in forwarding engine
and Layer 3 forwarding in this VDC
Error Message ELTMC-SLOT#-2-ELTMC_L2_LIF_REALLOC_FAIL_INTF: Failed to realloc L2 LIF

entries in forwarding engine for interface [chars]
and Layer 3 forwarding for the interface. ISSU failed for certain interfaces
Error Message ELTMC-SLOT#-2-ELTMC_L3_INGRESS_LIF_ALLOC_FAIL_INTF: Failed to

allocate L3 Ingress LIF entries in forwarding engine for interfac [chars]
Explanation ELTM Failed to allocate L3 Ingress LIF entries in forwarding engine. This will effect
Layer 3 forwarding for the interface
Error Message ELTMC-SLOT#-2-ELTMC_RSVD_VLAN: Failed to get the reserved vlans.

Failed with error [chars]
Explanation ELTM Failed to get the reserved

vlans.ThiswilleffectmulticastforwardingonSVIinterfaces'
Error Message ELTMC-SLOT#-2-ELTMC_VDC_LIF_REALLOC_FAIL: Failed to realloc LDB in

forwarding engine for vdc [dec]. Reload VDC after config reduction
Remove the interfaces and then reload VDC
OL-26589-01 2-111
Error Message ELTMC-SLOT#-2-ELTMC_VLAN_INTERNAL_ERROR: Internal error: VLAN

[dec]:[chars], collect output of show tech-support eltm
ELTM Messages
This section contains the ELTM messages.
ELTM-2
Error Message ELTM-2-INTERFACE_INTERNAL_ERROR: Internal error: [chars]:[chars],

collect output of show tech-support eltm
Error Message ELTM-2-INTERNAL_ERROR: Internal error: [chars], collect output of

show tech-support eltm
Error Message ELTM-2-INTF_NOT_FOUND: Interface [chars] not found in ELTM database

[chars]
Explanation ELTM database doesnthavetheinterface.'
Error Message ELTM-2-INTF_NOT_SUPP: Interface [chars] not supported by ELTM [chars]
Explanation ELTM doesntsupporttheinterfaceforthespecifiedoperation'
Error Message ELTM-2-INTF_TO_LTL: Failed to get LTL for interface [chars] return
status [chars]
Explanation ELTM Failed to get LTL for interface. Packets received on this interface might not be
handled correctly by the forwarding engine
2-112 OL-26589-01
ELTM-3
Error Message ELTM-3-OTV_FEATURE_FAIL: Feature OTV failed : [chars]
Explanation Error in ELTM while handling feature OTV request from OIM
ELTM-5
Error Message ELTM-5-EXT_COMP_ERR: [chars] component error [chars]
Explanation Recently applied Multicast config on the interface was unsuccessful, so reverting to the
old state (before config)
ELTM-6
Error Message ELTM-6-ELTM_MTS_SEND_FAILED: Failed to send MTS message errno [hex]

opcode [dec]
Explanation No action is required.
Recommended Action Eltm
EOU Messages
This section contains the EOU messages.
EOU-2
Error Message EOU-2-PBACL_APPLICATION_FAILURE: [chars] of host [chars] to/from

pbacl group [chars] failed. Error : [chars]
Explanation Failure of host addition/deletion to/from pbacl group
Recommended Action Please verify the addition/deletion of the host using the cli "show
object-group". If it was a delete request that failed, manual deletion of the host from the group is
recommended
OL-26589-01 2-113
EOU-5
Error Message EOU-5-L2NAC_DISABLED: EOU Disabled
Explanation Service EOU Disabled
Error Message EOU-5-L2NAC_ENABLED: EOU Enabled
Explanation Service EOU enabled
EOU-6
Error Message EOU-6-AAA_DOWN: Default Policy ip: [chars]:retained
Explanation Policy retained
Error Message EOU-6-AUTHTYPE: Authtype: ip: [chars] Authtype:[chars]
Explanation Authentication type
Error Message EOU-6-BAD_PKT: Bad Packet: ip: [chars] Why: [chars]
Explanation Bad Packet because of reason specified
Error Message EOU-6-CTA: CTA: ip: [chars] status(detected/not detected): [chars]
Explanation CTA detected or not
Error Message EOU-6-IDENTITY_MATCH: Identity Match: ip: [chars] Policy: [chars]
Explanation Identity Matched or not
2-114 OL-26589-01
Error Message EOU-6-PBACL_APPLICATION_STATUS: [chars] of host [chars] to/from

pbacl group [chars] succeeded
Explanation Status of host addition/deletion to pbacl group
Error Message EOU-6-POLICY: Policy on ip: [chars]: [chars]: [chars]
Explanation Policy applied
Error Message EOU-6-POSTURE: Posture:ip: [chars] Status: [chars], Interface:

[chars]
Explanation Posture of host
Error Message EOU-6-SESSION: Session ip: [chars] Action:[chars] , Interface:

[chars]
Explanation Session detected
Error Message EOU-6-SOCKET: Service eou on port: [dec]
Explanation Eou using above port
Error Message EOU-6-SQ_EAP_MSG: Status Query: ip: [chars] status: [chars]
Explanation Status query state
Error Message EOU-6-UNKN_EVENT_ERR: Unknow Event Err: ip: [chars] Message: [chars]
Explanation Error due to unknown event
OL-26589-01 2-115
Error Message EOU-6-VERSION_MISMATCH: Eou version mismatch ip: [chars] and version
[dec]
Explanation Eou version mismatch
EOU-7
Error Message EOU-7-EOU_DISABLED_INTF: eou disabled on interface [chars]
Explanation Eou service disabled on interface
Error Message EOU-7-EOU_ENABLED_INTF: eou enabled on interface [chars]
Explanation Eou service enabled on interface
EPLD_UPGRADE Messages
This section contains the EPLD_UPGRADE messages.
EPLD_UPGRADE-2
Error Message EPLD_UPGRADE-2-ACTIVE_SINGLE_SUP_UPGRADE: install all epld does not

upgrade Active Supervisor module [dec].
Explanation Install all epld does not upgrade Active Supervisor in a switch with a single supervisor.
Error Message EPLD_UPGRADE-2-ACTIVE_SUP_UPGRADE: install all epld does not upgrade

Active Supervisor module [dec]. Please do a switchover and upgrade the EPLDs on
module [dec].
Explanation Install all epld did not upgrade Active Supervisor.
EPP Messages
This section contains the EPP messages.
2-116 OL-26589-01
EPP-5
Error Message EPP-5-EPP_FAILURE: Interface [chars] EPP Failure
Explanation Trunk protocol failed
Recommended Action showeppinternalevent-historyerr'willindicatetheerrorsencountered'
Error Message EPP-5-EPP_LOOPBACK: Interface [chars] is looped back to the same

switch
Explanation The interface is looped back to another interface on the same switch
Recommended Action Check the connectivity of this interface and ensure that it is connected to
another switch
Error Message EPP-5-EPP_TRUNK_PROTOCOL_STATUS: epp trunk protocol is [chars] on

switch
Explanation Epp trunk protocol enabled/disabled on the switch
ETH-PORT-SEC Messages
This section contains the ETH-PORT-SEC messages.
ETH-PORT-SEC-3
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_CONFIG_MAC_FAILED: Failed to configure

MACs
Explanation Failed to configure MACs
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_INVALID_VLAN: Invalid VLAN configuration
Explanation Invalid VLAN configuration
OL-26589-01 2-117
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_SECURITY_VIOLATION_ANOTHER_PORT: Host

[chars] bound to Port [chars] in Vlan [dec] is trying to access Port [chars] in
Vlan [dec]
Explanation Moved the port to violation state due to a mac address seen on one port being seen on
another
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_SECURITY_VIOLATION_MAX_MAC_VLAN: Port

[chars] moved to [chars] state as host [chars] is trying to access the port in
vlan [dec]
Explanation Moved the port to violation state due to exceeding address count
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_UNABLE_TO_DISABLE: Unable to disable

eth_port_sec [chars].
Explanation Unable to disable eth_port_sec Service
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_UNABLE_TO_ENABLE: Unable to enable

eth_port_sec [chars].
Explanation Unable to enable eth_port_sec Service
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_VIOL_UPDATE_FAILED: Failed to update

violation mode
Explanation Failed to update violation mode
ETH-PORT-SEC-5
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_AGE_TIME_EXPIRY: Age Time expired for

host [chars] in VLAN [dec] in port [chars]
Explanation Age time expired for host
2-118 OL-26589-01
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_DISABLED: eth_port_sec Disabled on

if_index:[hex]
Explanation Eth_port_sec Service Disabled
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_DYNAMIC_MAC_ADDRESS_CLEARED: Dynamic

MAC addresses for port [chars] cleared
Explanation Dynamic MAC address for port cleared
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_ENABLED: eth_port_sec Enabled on

if_index:[hex]
Explanation Eth_port_sec Service Enabled
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_HOST_ADDITION: A new Host [chars] learnt

on Port [chars] in Vlan [dec]
Explanation A new host is learnt on a port
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_HOST_DELETION: Host [chars] bound to

secure port [chars] in Vlan [dec] has been removed
Explanation A host has been removed
ETHPORT Messages
This section contains the ETHPORT messages.
ETHPORT-2
Error Message ETHPORT-2-IF_CRITICAL_FAILURE: (Debug syslog)Critical failure:

[chars], [chars]
Explanation There was a critical failure in the component.
Recommended Action Please follow instructions on the syslog.
OL-26589-01 2-119
Error Message ETHPORT-2-IF_DOWN_ERROR_DISABLED: Interface [chars] is down (Error

disabled. Reason:[chars])
Explanation The interface encountered an error while configuring it
Recommended Action Collect more information about failed interface using command
showportinternalallinterface[char]'.Inmostcases,youcanrecoverusinga'shutdown'followeda'noshutd
own'ontheinterfaceorremovingandre-insertingthefibreopticcable.'
Error Message ETHPORT-2-IF_SEQ_ERROR: Error ([chars]) communicating with [chars]

for opcode [chars] ([chars])
Explanation Some component returned system error as a response to one of the port event sequence.
Recommended Action None
Error Message ETHPORT-2-SEQ_TIMEOUT: Component [chars] timed out on response to

opcode [chars] ([chars])
Explanation Some component did not respond to a request in stipulated time.
Error Message ETHPORT-2-SYSLOG_ETHPM_CRITICAL: Critical failure: [chars]
Explanation There was a critical failure in the component.
Recommended Action Please collect system tech-support
ETHPORT-3
Error Message ETHPORT-3-IF_DOWN_CHANNEL_ERR_DISABLED: Interface [chars] is down

(Channel error disabled)
Explanation This interface belongs to a PortChannel and the PortChannel is error disabled
Recommended Action Perform shut'and'noshutdown'onthePortChannelinterfacethatitbelongsto'
Error Message ETHPORT-3-IF_ERROR_VLANS_REMOVED: VLANs [chars] on Interface [chars]

are removed from suspended state.
Explanation The VLANs on an interface are being removed from the suspended state
2-120 OL-26589-01
Error Message ETHPORT-3-IF_ERROR_VLANS_SUSPENDED: VLANs [chars] on Interface

[chars] are being suspended. (Reason: [chars])
Explanation The VLANs on an interface are being suspended due to some protocol action
Error Message ETHPORT-3-IF_SFP_ALARM: Interface [chars], [chars]
Explanation There was an alarm on the transceiver module
Recommended Action Please do show interface transceiver details to obtain more information
Error Message ETHPORT-3-IF_SFP_ERROR: Interface [chars], [chars]
Explanation There was an error on the transceiver module
Error Message ETHPORT-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver on interface

[chars] is not supported
Explanation The transceiver for the interface specified in the error message is not a Cisco supported
module
Recommended Action Replace the module with a compatible transceiver. If the transceiver was
purchased from Cisco, please contact Cisco TAC to get the transceiver replaced
Error Message ETHPORT-3-IF_XCVR_ALARM: Interface [chars], [chars]
Explanation There was an alarm on the transceiver module
Error Message ETHPORT-3-IF_XCVR_ERROR: Interface [chars], [chars]
Explanation There was an error on the transceiver module
OL-26589-01 2-121
ETHPORT-4
Error Message ETHPORT-4-IF_NON_QUALIFIED_TRANSCEIVER: Non-qualified transceiver on

interface [chars] was detected
Explanation The transceiver for the interface specified has not been qualified on this platform for
this software release
Recommended Action Replace the module with a supported transceiver. Contact Cisco TAC to get
platform transceiver qualification details
Error Message ETHPORT-4-IF_SFP_WARNING: Interface [chars], [chars]
Explanation There was an warning on the transceiver module
Error Message ETHPORT-4-IF_XCVR_WARNING: Interface [chars], [chars]
Explanation There was an warning on the transceiver module
ETHPORT-5
Error Message ETHPORT-5-IF_ADMIN_UP: Interface [chars] is admin up [chars]
Explanation Interface is admin up
Error Message ETHPORT-5-IF_BANDWIDTH_CHANGE: Interface [chars],bandwidth changed

to [chars] Kbit
Explanation Bandwidth of the interface (port channel) has changed and this change is updated
Error Message ETHPORT-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is down

(Administratively down)
Explanation Interface has been configured to be administratively down
Recommended Action Perform noshutdown''
2-122 OL-26589-01
Error Message ETHPORT-5-IF_DOWN_CFG_CHANGE: Interface [chars] is down(Config

change)
Explanation FCIP interface temporarily down due to reconfiguration
Error Message ETHPORT-5-IF_DOWN_CHANNEL_ADMIN_DOWN: Interface [chars] is down

(Channel admin down)
Explanation This interface belongs to a PortChannel and the PortChannel is configured to be

administratively down
Recommended Action Perform noshutdown'onthePortChannelinterfacethatitbelongsto'
Error Message ETHPORT-5-IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS: Interface

[chars] is down (Channel membership update in progress)
Explanation The interface belongs to a PortChannel and a configuration is being attempted on the
interface while there is a configuration in progress on the PortChannel
Recommended Action Retry the configuration again
Error Message ETHPORT-5-IF_DOWN_DOMAIN_ADDR_ASSIGN_FAILURE_ISOLATION: Interface

[chars] is down (Isolation due to domain id assignment failure)
Explanation Isolated due to a failure while assigning a domain
Error Message ETHPORT-5-IF_DOWN_DOMAIN_INVALID_RCF_RECEIVED: Interface [chars] is

down (Isolation due to invalid fabric reconfiguration)
Explanation Invalid RCF received
Error Message ETHPORT-5-IF_DOWN_DOMAIN_MANAGER_DISABLED: Interface [chars] is down

(Isolation due to domain manager disabled)
Explanation Isolated due to domain manager being disabled
Error Message ETHPORT-5-IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE: Interface

[chars] is down (Isolation due to domain manager other side not responding)
Explanation Remote end domain manager not responding
OL-26589-01 2-123
Error Message ETHPORT-5-IF_DOWN_DOMAIN_OTHER_SIDE_EPORT_ISOLATED: Interface

[chars] is down (Isolation due to domain other side eport isolated)
Explanation Isolating this interface due to the remote end being isolated
Error Message ETHPORT-5-IF_DOWN_DOMAIN_OVERLAP_ISOLATION: Interface [chars] is

down (Isolation due to domain overlap)
Explanation Isolated due to domain overlap
Error Message ETHPORT-5-IF_DOWN_ELP_FAILURE_ISOLATION: Interface [chars] is down

(Isolation due to ELP failure)
Explanation ELP failed on the interface
Recommended Action Check the output of showportinternalinfo'inthe'ELPfailurereason'field'
Error Message ETHPORT-5-IF_DOWN_EPP_FAILURE: Interface [chars] is down (Error

Disabled - EPP Failure)
Explanation Trunk protocol failed
Recommended Action
showportinternalevent-historymsgs'willindicatethetrunkprotocolexchangestodeterminewhyitfailed'
Error Message ETHPORT-5-IF_DOWN_ESC_FAILURE_ISOLATION: Interface [chars] is down

(Isolation due to ESC failure)
Explanation ESC failed on the interface
Recommended Action Check the output of

showportinternalevent-history'todeterminetheESCprotocolexchangestodeterminehowitfailed'
Error Message ETHPORT-5-IF_DOWN_ETH_IF_DOWN: Interface [chars] is down(Tunnel port

src interface down)
Explanation Ethernet link to which the FCIP interface is bound is down
Recommended Action Ensure that the ethernet cable is connected, the interface is administratively
enabled
2-124 OL-26589-01
Error Message ETHPORT-5-IF_DOWN_ETH_LINK_DOWN: Interface [chars] is down(Tunnel

port src interface link down)
Explanation Ethernet link to which the FCIP interface is bound is down
Recommended Action Ensure that the ethernet cable is connected and the remote end is also active
Error Message ETHPORT-5-IF_DOWN_FCOT_NOT_PRESENT: Interface [chars] is down (FCOT

not present)
Explanation The FCOT has been removed
Recommended Action Insert an FCOT
Error Message ETHPORT-5-IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED: Interface [chars] is

down (Error disabled - Fcot vendor not supported)
Explanation Fcot inserted is not a supported one
Recommended Action Please contact customer support for a list of authorized transceiver vendors
Error Message ETHPORT-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware

Failure)
Explanation The moduleshardwarehasfailed'
Recommended Action Collect more information about failed module using command
showmoduleinternalallmodule''
Error Message ETHPORT-5-IF_DOWN_INACTIVE: Interface [chars] is down (Inactive)
Explanation The port VSAN has been suspended or deleted
Recommended Action Assign a new active port VSAN to the interface
Error Message ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_MODE: Interface [chars] is down

(Error disabled - Incompatible admin port mode)
Explanation The configured mode is not supported on this interface
Recommended Action Perform a

showportinternalinfo'todeterminethelistofmodessupportedonthisinterface'
Error Message ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBBCREDIT: Interface [chars]

is down (Error disabled - Incompatible admin port rxbbcredit)
Explanation The configured receive B2B credit size is not supported
Recommended Action Get the allowed receive B2B credit size from showportinternalinfo''
OL-26589-01 2-125
Error Message ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBUFSIZE: Interface [chars] is

down (Error disabled - Incompatible admin port rxbufsize)
Explanation The configured receive buffer size is not supported
Recommended Action Get the allowed receive buffer size from showportinternalinfo''
Error Message ETHPORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_SPEED: Interface [chars] is

down (Error disabled - Incompatible admin port speed)
Explanation The configured speed is not supported on this interface

showportinternalinfo'todeterminetherangeofspeedsupportedonthisinterface'
Error Message ETHPORT-5-IF_DOWN_INITIALIZING: Interface [chars] is down

(Initializing)
Explanation The interface is in the process of coming up
Recommended Action If the interface is stuck in this state for a while, check the output of
showportinternalevent-history'todeterminewhatitiswaitingfor'
Error Message ETHPORT-5-IF_DOWN_INTERFACE_REMOVED: Interface [chars] is down

(Interface removed)
Explanation Interface removed
Error Message ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface [chars] is down (Link

failure)
Explanation The physical link has gone down
Recommended Action Ensure that the cable is connected and the remote end is not shut down
Error Message ETHPORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE: Interface [chars] is down

(Diag failure)
Explanation Diag failed on the interface
attachmodule'toconnecttomodule'
2-126 OL-26589-01
Error Message ETHPORT-5-IF_DOWN_LOOPBACK_ISOLATION: Interface [chars] is down

(Isolation due to port loopback to same switch)
Explanation The interface is looped back to another interface on the same switch
another switch
Error Message ETHPORT-5-IF_DOWN_MODULE_REMOVED: Interface [chars] is down (module

removed)
Explanation Interface is down because the module was removed
Error Message ETHPORT-5-IF_DOWN_NONE: Interface [chars] is down ([chars])
Explanation Interface is down with a possible reason.
Recommended Action Collect more information about port using command

showportinternalinfo/event-history'todeterminewhyitwentdown'
Error Message ETHPORT-5-IF_DOWN_NON_PARTICIPATING: Interface [chars] is down (Non

participating)
Explanation The loop port has been put into non participating mode
Error Message ETHPORT-5-IF_DOWN_OFFLINE: Interface [chars] is down (Offline)
Explanation The interface has been placed into the offline state
Error Message ETHPORT-5-IF_DOWN_PARENT_ADMIN_DOWN: Interface [chars] is down

(Parent interface down)
Explanation Parent interface is down
Error Message ETHPORT-5-IF_DOWN_PARENT_DOWN: Interface [chars] is down (Parent

interface is down)
Explanation The physical link on the parent interface has gone down
OL-26589-01 2-127
Error Message ETHPORT-5-IF_DOWN_PEER_CLOSE: Interface [chars] is down(TCP conn.

closed by peer)
Explanation The FCIP peer connected to this interface closed the TCP connection
Recommended Action This command will provide the peer IP address of this FCIP interface: show
interface. Check to see why the peer closed the TCP connection
Error Message ETHPORT-5-IF_DOWN_PEER_RESET: Interface [chars] is down(TCP conn.

reset by peer)
Explanation TCP connection to the FCIP peer got reset
Recommended Action The following commands will provide the IP address of the peer and the route
used connect to this FCIP peer: show interface, show ip route. Check to see why the peer reset the
TCP connection
Error Message ETHPORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface [chars] is

down (No operational members)
Explanation This is a PortChannel interface and all its members are operationally down
Recommended Action Enable at least one of the PortChannelsmembers'
Error Message ETHPORT-5-IF_DOWN_PORT_VSAN_MISMATCH_ISOLATION: Interface [chars] is

down (Isolation due to port vsan mismatch)
Explanation Isolated due to a mismatch in the configured port VSAN of the local and remote ends
Recommended Action Configure the port VSAN of the local and remote interfaces to be the same and
perform a shutdown'anda'noshutdown''
Error Message ETHPORT-5-IF_DOWN_RCF_IN_PROGRESS: Interface [chars] is down (RCF in

progress)
Explanation There is an RCF in progress
Error Message ETHPORT-5-IF_DOWN_SOFTWARE_FAILURE: Interface [chars] is down (Port

software failure)
Explanation The software servicing the data path on the port has failed
2-128 OL-26589-01
Error Message ETHPORT-5-IF_DOWN_SRC_MOD_NOT_ONLINE: Interface [chars] is

down(Tunnel source module not online)
Explanation Module that has the tunnel source port of this FCIP interface is not fully online
Recommended Action The module that has the tunnel src port is coming online. Please use show mod
to find module status
Error Message ETHPORT-5-IF_DOWN_SRC_PORT_NOT_BOUND: Interface [chars] is down

(Tunnel port src interface unbound)
Explanation Tunnel port source interface unbound
Error Message ETHPORT-5-IF_DOWN_SRC_PORT_REMOVED: Interface [chars] is down(Tunnel

src port removed)
Explanation Tunnel source port of this FCIP interface has been removed
Recommended Action The src interface with ip address that matches the ip address of the bound
entity is removed. This happens normally due to the module on which the src interface exists is
removed
Error Message ETHPORT-5-IF_DOWN_SUSPENDED_BY_MODE: Interface [chars] is down

(Suspended due to incompatible mode)
Explanation This interface belongs to a PortChannel and operational mode of the interface is
different from that of the PortChannel
Recommended Action Change the mode and the trunking mode of the PortChannel from
auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'
Error Message ETHPORT-5-IF_DOWN_SUSPENDED_BY_SPEED: Interface [chars] is down

(Suspended due to incompatible speed)
Explanation This interface belongs to a PortChannel and operational speedode of the interface is
Recommended Action Change the speed of the PortChannel from

Error Message ETHPORT-5-IF_DOWN_SUSPENDED_BY_WWN: Interface [chars] is down

(Suspended due to incompatible remote switch WWN)
Explanation This interface belongs to a PortChannel and remote switch WWN of the interface is
Recommended Action Ensure that this interface is connected to the same remote switch as all the
other interfaces in the PortChannel
OL-26589-01 2-129
Error Message ETHPORT-5-IF_DOWN_SUSPENDED: Interface [chars] is down (Suspended)
Explanation This interface belongs to a PortChannel and has been suspended due to an error while
bringing it up

shutdown'anda'noshutdown'.Ifthishappensagainobtainoutputof'showportinternalinfo/event-history'
ontheinterface'
Error Message ETHPORT-5-IF_DOWN_TCP_KEEP_ALIVE_EXPIRED: Interface [chars] is

down(TCP conn. closed - Keep alive expired)
Explanation TCP session to the FCIP peer got closed due to loss of TCP keep alive
Recommended Action This may be due to loss of IP connectivity. The following commands will
provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show
ip route. Please do a trace route to check the connectivity to the peer using command:traceroute
ipaddr
Error Message ETHPORT-5-IF_DOWN_TCP_MAX_RETRANSMIT: Interface [chars] is down(TCP

conn. closed - retransmit failure)
Explanation Interface is down due to maximum retransmission failure
ipaddr
Error Message ETHPORT-5-IF_DOWN_TCP_PERSIST_TIMER_EXPIRED: Interface [chars] is

down(TCP conn. closed - Persist timer expired)
Explanation TCP session to the FCIP peer closed because TCP persist timer expired
ipaddr
Error Message ETHPORT-5-IF_DOWN_UPGRADE_IN_PROGRESS: Interface [chars] is down

(Linecard upgrade in progress)
Explanation Upgrade of the linecard software is in progress
2-130 OL-26589-01
Error Message ETHPORT-5-IF_DOWN_VRF_UNUSABLE: Interface [chars] is down (Vrf down)
Explanation The vrf for which this interface is a member is removed
Error Message ETHPORT-5-IF_DOWN_VSAN_MISMATCH_ISOLATION: Interface [chars] is down

(Isolation due to vsan mismatch)
Explanation This is a trunking interface and the VSANs configured do not match with the VSANs
configured on the remote end
Recommended Action Check the VSANs configured on the local end with the remote end
Error Message ETHPORT-5-IF_DOWN_ZONE_MERGE_FAILURE_ISOLATION: Interface [chars] is

down (Isolation due to zone merge failure)
Explanation Isolated due to a failure during zone merge
Error Message ETHPORT-5-IF_DOWN_ZONE_REMOTE_NO_RESP_ISOLATION: Interface [chars]

is down (Isolation due to remote zone server not responding)
Explanation Isolated due to remote zone server not responding
Error Message ETHPORT-5-IF_DUPLEX: Interface [chars], operational duplex mode

changed to [chars]
Explanation Operational duplex mode has changed when link came up
Error Message ETHPORT-5-IF_ERRDIS_RECOVERY: Interface [chars] is being recovered

from error disabled state (Last Reason:[chars])
Explanation Interface is being recovered from error disabled state
Error Message ETHPORT-5-IF_HARDWARE: Interface [chars], hardware type changed to

[chars]
Explanation There was a change in the hardware characteristic of an interface, such as a transceiver
module plugged in or removed
OL-26589-01 2-131
Error Message ETHPORT-5-IF_L2MP_MODE: Interface [chars], l2mp-mode changed to

[chars]
Explanation The l2mp-mode on the port has changed
Error Message ETHPORT-5-IF_RX_FLOW_CONTROL: Interface [chars], operational Receive

Flow Control state changed to [chars]
Explanation Operational receive flow control has changed when link came up
Error Message ETHPORT-5-IF_TRUNK_DOWN: Interface [chars], vlan [chars] down
Explanation Interface [chars] is trunking, VLANs [chars] are down
Recommended Action The following commands will help determine why this VSAN is down on this
interface: show interface, show port internal info interface VSAN, show port internal event-history
interface vsan
Error Message ETHPORT-5-IF_TRUNK_UP: Interface [chars], vlan [chars] up
Explanation Interface [chars] is trunking, VLANs [chars] are up
Error Message ETHPORT-5-IF_TX_FLOW_CONTROL: Interface [chars], operational

Transmit Flow Control state changed to [chars]
Explanation Operational transmit flow control has changed when link came up
Error Message ETHPORT-5-IF_UP: Interface [chars] is up [chars]
Explanation Interface is up in mode specified, if applicable
Error Message ETHPORT-5-SPEED: Interface [chars], operational speed changed to

[chars]
Explanation Operational speed has changed when link came up
2-132 OL-26589-01
Error Message ETHPORT-5-STORM_CONTROL_ABOVE_THRESHOLD: Traffic in port [chars]

exceeds the configured threshold [chars]
Explanation Traffic on specified port is beyond the configured storm-control threshold, and the
excess traffic is being dropped
Recommended Action Identify source of traffic storm
Error Message ETHPORT-5-STORM_CONTROL_BELOW_THRESHOLD: Traffic in port [chars] has

fallen below the configured threshold [chars]
Explanation Traffic on specified port has returned to within configured storm-control threshold
ETH_PORT_CHANNEL Messages
This section contains the ETH_PORT_CHANNEL messages.
ETH_PORT_CHANNEL-1
Error Message ETH_PORT_CHANNEL-1-LC_CFG_FAILURE: configuring module [dec] failed

[[chars]]
Explanation Module configuration failed
Recommended Action Module will be automatically reset
Error Message ETH_PORT_CHANNEL-1-MALLOC_FAILED: cannot allocate memory (size

[dec])
Explanation No enough memory
Error Message ETH_PORT_CHANNEL-1-MAP_PARAM_FAILURE: mapping parameter failed for

[chars] [[chars]]
Explanation Parameter mapping failed
Recommended Action Specified service is misbehaving; check its status
OL-26589-01 2-133
Error Message ETH_PORT_CHANNEL-1-MCAST_SEND_FAILURE: failed to send multicast

[chars]: [chars]
Explanation Failed to send a multicast message to all modules, usually because some module went
down
Recommended Action Run show port-channel consistency to check consistency
ETH_PORT_CHANNEL-2
Error Message ETH_PORT_CHANNEL-2-RESET_MODULE: reset module [dec] for not

responding or returning error
Explanation A module is reset for not responding or returning error
ETH_PORT_CHANNEL-3
Error Message ETH_PORT_CHANNEL-3-ADD_REM_MEMBERS_FAILURE: [chars]
Explanation Some service(s) failed to add or remove ports to port-channel
Error Message ETH_PORT_CHANNEL-3-ALL_DROP_TIMEOUT: Some component(s) (sap:[chars])

timed out on dropping notif:[chars] (for:[chars]); Please collect <show system
internal mts buffers details
Error Message ETH_PORT_CHANNEL-3-COMPAT_CHECK_FAILURE: [chars] is not compatible
Explanation Compatibility check failed when adding ports to port-channel
Recommended Action Make sure the compatibility parameters are consistent while adding ports to
port-channel, or use force option
Error Message ETH_PORT_CHANNEL-3-GENERAL_ERROR: [chars]
Explanation General error
2-134 OL-26589-01
Error Message ETH_PORT_CHANNEL-3-MSG_SEND_FAILURE: failed to send [chars] to sap

[dec]: [chars]
Explanation Failed to send a message
Error Message ETH_PORT_CHANNEL-3-NUM_ACTIVE_PORTS_ERROR: Port-channel:[chars]

active_nports [dec]; No member is active; Please collect <show tech-support
port-channel/ethpm
Explanation Port-channel num active ports error
Error Message ETH_PORT_CHANNEL-3-PCM_HWCFG_FAIL_ERROR: Port-channel:[chars]

mbr:[chars] SAP [dec] returned error [chars] for opc [chars]; if lacp port-channel
please collect <show tech-support lacp all
Explanation Port-channel hwcfg fail error
Error Message ETH_PORT_CHANNEL-3-PCM_INTERNAL_ERROR: Port-channel:[chars]

mbr:[chars]; if lacp port-channel please collect <show tech-support lacp all
Explanation Port-channel internal error
Error Message ETH_PORT_CHANNEL-3-PCM_PORT_DEL_IN_PC_UP_ERROR:

Port-channel:[chars] mbr:[chars]; if lacp port-channel please collect <show
tech-support lacp all
Explanation Port-channel port del in pc_up. Shut resp recvd before bundle member down
Error Message ETH_PORT_CHANNEL-3-PCM_PORT_DOWN_IN_PC_UP_ERROR:

Port-channel:[chars] mbr:[chars]; if lacp port-channel please collect <show
tech-support lacp all
Explanation Port-channel port down in pc_up. No bundle member down
OL-26589-01 2-135
Error Message ETH_PORT_CHANNEL-3-PORT_CHANNEL_NOT_FOUND: [chars] is not found
Explanation Cannot find port-channel in its database, which indicates an inconsistency with an
external component
Error Message ETH_PORT_CHANNEL-3-RESOURCE_ALLOC_FAILED_PORT_CHANNEL_DELETED:

[chars] deleted
Explanation Port-channel deleted from running config
Recommended Action May need to re-configure the port-channel and its members
Error Message ETH_PORT_CHANNEL-3-RSP_TIMEOUT: Component [chars] timed out on

response to opcode:[chars] (for:[chars])
Error Message ETH_PORT_CHANNEL-3-TIMEOUT: timed out after [dec] seconds [type

[chars], state [chars]]
Explanation Some operation timed out
Recommended Action Run show port-channel consistency to check all module connectivity and
consistency
Error Message ETH_PORT_CHANNEL-3-SHADOW_MBR_CHANGE_FAILURE: [chars]
Explanation Some service failed shadow member change to port-channel
Error Message ETH_PORT_CHANNEL-3-SHADOW_PC_CREATE_FAILURE: [chars]
Explanation Some service failed shadow port-channel create
Error Message ETH_PORT_CHANNEL-3-SHADOW_PC_DELETE_FAILURE: [chars]
Explanation Some service failed shadow port-channel delete
2-136 OL-26589-01
ETH_PORT_CHANNEL-4
Error Message ETH_PORT_CHANNEL-4-PORT_CFG_DELETED: [chars] removed from [chars]

(different module inserted)
Explanation Port is removed from a port-channel because a different module was inserted to the
same slot
Recommended Action You lost some ports from port-channel, check if you want to add ports in the
new module to the same port-channel.
Error Message ETH_PORT_CHANNEL-4-PORT_INDIVIDUAL: port [chars] is operationally

individual
Explanation The port is operating as an individual link even though it is locally or remotely
configured to be part of a port channel
Recommended Action Check the configuration of the port locally and remotely to ensure that it can
operate as part of a port channel
Error Message ETH_PORT_CHANNEL-4-PORT_NOT_FOUND: port [chars] is not part of

port-channel
Explanation Cannot find the port in port-channel database, which indicates an inconsistency with an
external component
Error Message ETH_PORT_CHANNEL-4-RACE_WARN: [chars]
Explanation Warning of possible race condition
Error Message ETH_PORT_CHANNEL-4-UNEXPECTED_RESPONSE: unexpected response [chars]

from [chars]
Explanation Received an unexpected response and discarded
ETH_PORT_CHANNEL-5
Error Message ETH_PORT_CHANNEL-5-AUTO_CREATE_FAILURE: [chars] [chars]
Explanation Auto create process on the port failed
OL-26589-01 2-137
Error Message ETH_PORT_CHANNEL-5-CREATED: [chars] created
Explanation A port-channel is created
Error Message ETH_PORT_CHANNEL-5-DELETED: [chars] deleted
Explanation A port-channel is deleted
Error Message ETH_PORT_CHANNEL-5-FOP_CHANGED: [chars]: first operational port

changed from [chars] to [chars]
Explanation The first operational port in a port-channel is changed
Error Message ETH_PORT_CHANNEL-5-IF_DOWN_SUSPENDED_BY_MODE: Interface [chars] is

down (Suspended due to incompatible mode
Recommended Action Make sure the compatibility parameters are consistent between the ports and
the port-channel
Error Message ETH_PORT_CHANNEL-5-IF_DOWN_SUSPENDED_BY_SPEED: Interface [chars] is

down (Suspended due to incompatible speed
Explanation Operational compatibility check failed on the port in a port-channel
Recommended Action Make sure the compatibility parameters are consistent between the ports and
the port-channel
Error Message ETH_PORT_CHANNEL-5-MAX_CHANNEL_DISALLOWED: Module failed to come

online because port channel interface <port-channel number
Explanation The port-channel number configured on the switch is larger than 128
Recommended Action Delete the set of port channel interface <port-channel interface
Error Message ETH_PORT_CHANNEL-5-PORT_ADDED: [chars] added to [chars]
Explanation Ports are added to a port-channel
2-138 OL-26589-01
Error Message ETH_PORT_CHANNEL-5-PORT_DOWN: [chars]: [chars] is down
Explanation Port goes down in a port-channel
Error Message ETH_PORT_CHANNEL-5-PORT_HOT_STANDBY_DOWN: [chars]: hot-standby port

[chars] is down
Explanation Port-channel hot-standby member goes down
Error Message ETH_PORT_CHANNEL-5-PORT_HOT_STANDBY: [chars]: [chars] goes to

hot-standby
Explanation Port goes to hot-standby in a port-channel
Error Message ETH_PORT_CHANNEL-5-PORT_INDIVIDUAL_DOWN: individual port [chars] is

down
Explanation Port-channel member operating in individual mode goes down
Error Message ETH_PORT_CHANNEL-5-PORT_REMOVED: [chars] removed from [chars]
Explanation Ports are removed from a port-channel
Error Message ETH_PORT_CHANNEL-5-PORT_SUSPENDED: [chars]: [chars] is suspended
Explanation Port is suspended in a port-channel
Error Message ETH_PORT_CHANNEL-5-PORT_UP: [chars]: [chars] is up
Explanation Port comes up in a port-channel
OL-26589-01 2-139
Error Message ETH_PORT_CHANNEL-5-SUBGROUP_ID_CHANGE: Interface [chars] in

port-channel[dec] subgroup-id changed from [dec] to [dec]
Explanation The portssubgroup-idgotchanged'
ETH_PORT_CHANNEL-6
Error Message ETH_PORT_CHANNEL-6-RESYNC: resyncing [chars] with all modules
Explanation Resync modules with sup after an error or switchover
ETH_PORT_CHANNEL-7
Error Message ETH_PORT_CHANNEL-7-GSYNC_DONE: global synchronization is done
Explanation Port-channel manager finished global synchronization
Error Message ETH_PORT_CHANNEL-7-GSYNC_REQ: requesting global synchronization
Explanation Port-channel manager requested a global synchronization from active sup
Error Message ETH_PORT_CHANNEL-7-START_ACTIVE: started in active mode
Explanation Port-channel manager started in active mode
Error Message ETH_PORT_CHANNEL-7-START_DEFAULT: started with default configuration
Explanation Port-channel manager started with default configuration
Error Message ETH_PORT_CHANNEL-7-START_STANDBY: started in standby mode
Explanation Port-channel manager started in standby mode
2-140 OL-26589-01
Error Message ETH_PORT_CHANNEL-7-START_STATEFUL: started statefully
Explanation Port-channel manager started with running configuration
Error Message ETH_PORT_CHANNEL-7-START_STATELESS: started statelessly
Explanation Port-channel manager started with startup configuration
EUREKA_USD Messages
This section contains the EUREKA_USD messages.
EUREKA_USD-3
Error Message EUREKA_USD-3-MSG1: [chars]
Explanation Eureka log message
EVMC Messages
This section contains the EVMC messages.
EVMC-3
Error Message EVMC-3-MTS_OPERATION_FAILED: [chars]([dec]): [chars]
Explanation Internal IPC operation failed in Event Manager Client
EVMC-4
Error Message EVMC-4-ACTION_CFG_MONITOR_COLLECT: [chars]([dec]): Action

configuration disallowed for Monitor Collect Policy
Explanation Configuring Policy Action for Monitor Collect Policy isnot allowed and hence, has
been rejected
OL-26589-01 2-141
EVMC-5
Error Message EVMC-5-AVL_CREATE_FAIL: [chars]([dec]): AVL Tree creation failure
Explanation Event Manager could not initialize local policy store
Error Message EVMC-5-MALLOC_FAILURE: [chars]([dec]): Memory allocation failure
Explanation Event Manager Client process could not allocate memory
Error Message EVMC-5-RT_PSS_OP_FAILURE: [chars]([dec]): Failed to [chars].

Error:[chars]
Explanation Event Manager Client could not access HA store
EVMS Messages
This section contains the EVMS messages.
EVMS-2
Error Message EVMS-2-EVMS_PSS_DELETE_FAILURE: Delete from PSS failed
Explanation Delete from PSS failed
Error Message EVMS-2-EVMS_PSS_WRITE_FAILURE: Write to PSS failed
Explanation Write to PSS failed
Error Message EVMS-2-EVMS_SHOW_POLICY_ALLOC_FAILURE: Insufficient memory: policy

information shown will be incomplete
Explanation Memory allocation failed. so complete requested information is not being shown
2-142 OL-26589-01
EVMS-4
Error Message EVMS-4-EVMS_APPLET_NO_ACTION_DEFAULT: WARNING: The default system

policy actions are being skipped
Explanation The default system policy actions are being skipped
EVMS-6
Error Message EVMS-6-EVMS_LOGGING_NO_SPACE: logflash full, so deleting first event

archive file
Explanation As the logflash is full, first of the present event archive files is deleted
EXCEPTIONLOG Messages
This section contains the EXCEPTIONLOG messages.
EXCEPTIONLOG-SLOT#-2
Error Message EXCEPTIONLOG-SLOT#-2-LC_EXP_MSG: Linecard exception: [chars] is the

affected Port bit map. [dec] Additional information - [chars]
Explanation LC Exception event.
FABRICPATH Messages
FABRICPATH-2
Error Message FABRICPATH-2-FABRICPATH_LINK_BRINGUP_STALLED_STATIC: Link bringup

stalled due to conflicts
Explanation Interface is disabled due to conflicts
OL-26589-01 2-143
FABRICPATH-4
Error Message FABRICPATH-4-FABRICPATH_ES_REMOTE_CONFLICT: Remote ES Switch-id

collides with local/remote switch-id in database
Explanation Conflict between Remote ES switch-id and non ES switch-id in database
Error Message FABRICPATH-4-FABRICPATH_INVALID_FTAG: Invalid ftag [dec] received
Explanation Invalid ftag is received from remote
Error Message FABRICPATH-4-FABRICPATH_INVALID_SWITCH_ID: Invalid switch-id [dec]

received
Explanation Invalid switch-id is received from remote
Error Message FABRICPATH-4-FABRICPATH_LOCAL_SWID_UNKNOWN: Local Switch-id is not

known to Resource Allocation manager
Explanation Resource Allocation Manager was not able to recover the local switch-id
Error Message No action is required.
FABRICPATH-6
Error Message FABRICPATH-6-FABRICPATH_LINK_BRINGUP_RESOLVE_COLLISION: Resolving

Collision for switch-id [dec]
Explanation Resolving Collision for switch-id
Error Message FABRICPATH-6-FABRICPATH_LINK_BRINGUP_STALLED_CLEARED: LINK bringup

cleared for [chars] after collision resolution
Explanation Link bringup temporarily suspended due to conflicts
2-144 OL-26589-01
Error Message FABRICPATH-6-FABRICPATH_LINK_BRINGUP_STALLED: LINK bringup suspended

for [chars] due to conflicts
Explanation Link bringup temporarily suspended due to conflicts
Error Message FABRICPATH-6-FABRICPATH_NEW_ES_SWITCH_ID: New Emulated switch-id

[chars] received
Explanation New Emulated switch-id received
Error Message FABRICPATH-6-FABRICPATH_NEW_SWITCH_ID: New switch-id [chars]

received
Explanation New switch-id received
Error Message FABRICPATH-6-FABRICPATH_SWID_CHANGED: Switch-id [dec] is assigned

with [chars] state
Explanation Local switch-id is changed
Error Message FABRICPATH-6-FABRICPATH_SWID_CONFLICTS: Switch-id [dec] is in

conflict with device [chars]
Explanation Local switch-id collision with other device
Error Message FABRICPATH-6-FABRICPATH_SWID_PRI_SEC_CHANGED: Switch-id [dec] is

changed to [chars]
Explanation Local switch-id status changed
Error Message FABRICPATH-6-FABRICPATH_SWID_STATE_CHANGED: Switch-id [dec] status

changed to [chars]
Explanation Local switch-id status changed
OL-26589-01 2-145
FC-TUNNEL Messages
This section contains the FC-TUNNEL messages.
FC-TUNNEL-3
Error Message FC-TUNNEL-3-INTERNAL_ERROR: Internal error: [chars]
Explanation FCMPLS tunnel process encountered a general error, one that does not fall in any of
the categories. [chars] describes the error and its context.
Error Message FC-TUNNEL-3-IPFC_ERROR: IPFC API, [chars], failed with error [hex]
Explanation FCMPLS tunnel invoked IPFC API and received the error code. [chars] describes the
API and 0x[hex] specifies the error
Error Message FC-TUNNEL-3-MTS_ERROR: MTS message transmission failed with error

[dec]
Explanation FCMPLS tunnel process unsuccessfully tried to send a MTS message. MTS errro
number is specified in [dec]
Error Message FC-TUNNEL-3-NS_ERROR: FCNS API, [chars], failed with error [hex]
Explanation FCMPLS tunnel invoked FCNS API and received the error code. [chars] describes the
Error Message FC-TUNNEL-3-PM_ERROR: Port Manager API, [chars], failed with error
[hex]
Explanation FCMPLS tunnel invoked Port Manager API and received the error code. [chars]
describes the API and 0x[hex] specifies the error
2-146 OL-26589-01
Error Message FC-TUNNEL-3-PSS_CFG_RESTORE_ERROR: Configuration restoration for

[chars] failed with error [hex]
Explanation FCMPLS tunnel read the saved configuration and encountered an error while
rebuilding the runtime configuration. [chars] describes the configuration which the process tried to
restore and 0x[hex] is the system error code
Error Message FC-TUNNEL-3-PSS_ERROR: PSS operation [chars] returned error: [hex]
Explanation [chars] specifies the context where the failure occurred and 0x[hex] specifies the error
Error Message FC-TUNNEL-3-PSS_RTDB_RESTORE_ERROR: Runtime database restoration for

Explanation FCMPLS tunnel read the saved runtime database and encountered an error while
rebuilding the runtime database. [chars] describes the runtime database which the process tried to
restore and 0x[hex] is the system error code
Error Message FC-TUNNEL-3-RIB_ERROR: RIB API, [chars], failed with error [hex]
ExplanationFCMPLS tunnel invoked RIB API and received the error code. [chars] describes the
Error Message FC-TUNNEL-3-RSVP_PROTO_ERROR: RSVP protocol error: [chars]
Explanation RSVP-TE protocol error is encountered. [chars] describes the error and its context.
Error Message FC-TUNNEL-3-UNEXPECTED_MTS_MSG: Unexpected MTS message, opcode

[dec], is received
Explanation FCMPLS tunnel process received unexpected MTS event. MTS opcode is specified in
[dec]
OL-26589-01 2-147
FC-TUNNEL-5
Error Message FC-TUNNEL-5-MSG_INTERFACE_DOWN: Interface [chars] is down
Explanation The logical fc tunnel interface is down. This may be due to a reconfiguration on the fc
tunnel, or issues on the underlying physical interface
Recommended Action If this is not due to a known reconfiguration, you should verify connectivity
at the physical port level, and then on then on the fc tunnel interface. Furthermore, verify the
physical ports along the fc tunnel path operate in the TE mode
Error Message FC-TUNNEL-5-MSG_INTERFACE_UP: Interface [chars] is up
Explanation The fc interface is up
FCC_LC Messages
This section contains the FCC_LC messages.
FCC_LC-2
Error Message FCC_LC-2-ERROR_SENDING_HEART_BEAT: Error sending heart beat [dec]
Explanation FCC_LC has error sending heart beat
Error Message FCC_LC-2-EXITING: Exiting fcc_lc: [chars]
Explanation FCC_LC exiting
Error Message FCC_LC-2-HEART_BEAT_NOT_SENT: Heart beat not sent for [dec] millisecs
Explanation FCC_LC has not sent heart beat
Error Message FCC_LC-2-SHUTDOWN: Process shutting down: [chars]
Explanation FCC_LC Process is shutting down
2-148 OL-26589-01
Error Message FCC_LC-2-UNABLE_READ_DATA: Unable to read fcc data ([chars])
Explanation FCC is unable to read and process relevant FCC data
FCC_LC-5
Error Message FCC_LC-5-BAD_MSG: Received bad message: [chars]
Explanation FCC_LC has received a malformed/unrecognized message
Error Message FCC_LC-5-DISABLE: FCC_LC has been disabled
Explanation FCC_LC has been disabled
Error Message FCC_LC-5-ENABLE: FCC_LC has been enabled
Explanation FCC_LC has been enabled
Error Message FCC_LC-5-STARTING: FCC_LC process started
Explanation Process started successfully
FCC_LC-6
Error Message FCC_LC-6-PRIO_UPDATE: Updated enable priority to [dec]
Explanation FCC_LC is active for packets with priority <= [threshold]
FCC Messages
This section contains the FCC messages.
OL-26589-01 2-149
FCC-2
Error Message FCC-2-SHUTDOWN: Process shutting down: [chars]
Explanation FCC Process is shutting down
FCC-5
Error Message FCC-5-BAD_MSG: Received bad message: [chars]
Explanation FCC has received a malformed/unrecognized message
Error Message FCC-5-CONGESTION_STATE_CHANGE_NOTIF: Received Congestion State Change

notification to state: [dec]
Explanation FCC has received a Contestion State Change Notification
Error Message FCC-5-DISABLE: FCC has been disabled
Explanation FCC has been disabled
Error Message FCC-5-ENABLE: FCC has been enabled
Explanation FCC has been enabled
Error Message FCC-5-RATE_LIMIT_END_NOTIF: Received Rate Limit End notification
Explanation FCC has received a Rate Limit End Notification
Error Message FCC-5-RATE_LIMIT_START_NOTIF: Received Rate Limit Start notification
Explanation FCC has received a Rate Limit Start Notification
2-150 OL-26589-01
Error Message FCC-5-STARTING: FCC process started
Explanation Process started successfully
FCC-6
Error Message FCC-6-PRIO_UPDATE: Updated enable priority to [dec]
Explanation FCC is active for packets with priority <= [threshold]
FCDDH Messages
This section contains the FCDDH messages.
FCDDH-SLOT#-3
Error Message FCDDH-SLOT#-3-LOG_FCDDH_ERR: Nonrecoverable error - exiting: [chars]
Explanation Errors which cause program to exit occurred
FCDDH-SLOT#-4
Error Message FCDDH-SLOT#-4-LOG_FCDDH_WARNING: Serious error: [chars]
Explanation Serious errors which affect all normal operations occurred
FCDDH-SLOT#-5
Error Message FCDDH-SLOT#-5-LOG_FCDDH_DEBUG: Unexpected error: [chars]
Explanation Unexpected errors which affect some normal operations occurred
OL-26589-01 2-151
Error Message FCDDH-SLOT#-5-LOG_FCDDH_NOTICE: [chars]
Explanation Major configuration changes
FCDD Messages
This section contains the FCDD messages.
FCDD-SLOT#-3
Error Message FCDD-SLOT#-3-LOG_FCDD_ERR: Nonrecoverable error - exiting: [chars]
FCDD-SLOT#-4
Error Message FCDD-SLOT#-4-LOG_FCDD_WARNING: Warning!: [chars]
FCDD-SLOT#-5
Error Message FCDD-SLOT#-5-LOG_FCDD_GCONF_FSM: [chars]
Explanation Illegal event received in Global Configuration FSM
Error Message FCDD-SLOT#-5-LOG_FCDD_NOTICE: [chars]
Explanation Major configuration changes
Error Message FCDD-SLOT#-5-LOG_FCDD_RESCAN_FSM: [chars]
Explanation Illegal event received in Rescan FSM
2-152 OL-26589-01
Error Message FCDD-SLOT#-5-LOG_FCDD_TZONE_FSM: [chars]
Explanation Illegal event received in Twilight Zone Remover FSM
Error Message FCDD-SLOT#-5-LOG_FCDD_VCONF_FSM: [chars]
Explanation Illegal event received in VSAN Configuration FSM
Error Message FCDD-SLOT#-5-LOG_FCDD_VNO_FSM: [chars]
Explanation Illegal event received in VSAN Normal Operation FSM
FCDD-SLOT#-7
Error Message FCDD-SLOT#-7-LOG_FCDD_DEBUG: [chars]
FCDOMAIN Messages
This section contains the FCDOMAIN messages.
FCDOMAIN-2
Error Message FCDOMAIN-2-DOMS_CONFLICT: Conflict detected: ([dec]) domain ID [dec]

WWN [chars]
Explanation Conflict detected ([dec]) domain ID [dec] with WWN [chars].
Recommended Action Check which switches have the same WWN and change either one; then
change either's domain ID.
OL-26589-01 2-153
Error Message FCDOMAIN-2-EPORT_ISOLATED: Isolation of interface [chars] (reason:

[chars])
Explanation Fcdomain has isolated interface [chars] (reason: [chars].) Perform a show interface.
Based on the reason specified, you might have to ensure domains are adequate and unique in the
VSAN and perform a disruptive restart [fcdomain restart disruptive vsan <vsan-id>] or to
reinitialize the port.
Error Message FCDOMAIN-2-FC2BIND_FAILED: Bind to FC2 Service failed
Explanation Fcdomain has not been able to contact the FC2 module.
Error Message FCDOMAIN-2-FC2_INITIALIZATION_FAILED: FC initialization sequence

failed
Explanation The fcdomain has not been able to complete the initialization sequence with the Fibre
Channel subsystem. fcdomain depends on resources not available at the moment: the switch might
be short in memory or some other component might be unable to provide the necessary information
to fcdomain.
Error Message FCDOMAIN-2-FC2_SET_SOCKOPT_DM_SOCK_FAILED: set sockopt to FC2 Service

failed
Explanation Fcdomain has not been able to setsockopt to the FC2 module.
Error Message FCDOMAIN-2-FCID_PERSISTENT_TBL_COMPLETELY_FULL: FCID persistent

table is completely full
Explanation The FCID persistent table is full. Perform [show fcdomain fcid persistent vsan
<vsan-id>] to view the entries currently in the table. No more entries can be saved as persistent
FCIDs across reboots.
Recommended Action Purge stale entries [purge fcdomain fcid] to obtain more free entries OR
disable the feature on certain VSANs which are not critical enough [no fcdomain fcid persistent].
Error Message FCDOMAIN-2-HIGH_PRIORITY_MTSBIND_FAILED: Bind for high priority IPC

failed
Explanation Fcdomain has not been able to contact the Inter Process Communication (IPC) module
for its high priority queue.
2-154 OL-26589-01
Error Message FCDOMAIN-2-INITIALIZATION_FAILED: Initialization sequence failed
Explanation The fcdomain has not been able to complete the initialization sequence. fcdomain
depends on resources not available at the moment: the switch might be short in memory or some
other component might be unable to provide the necessary information to fcdomain.
Error Message FCDOMAIN-2-MTSBIND_FAILED: Bind to IPC failed
Explanation Fcdomain has not been able to contact the Inter Process Communication (IPC) module.
Error Message FCDOMAIN-2-MTSREGISTRATION_FAILED: Registration of opcodes with IPC

Service failed
Explanation Fcdomain has not been able to register its messages with the Inter Process
Communication (IPC) module.
Error Message FCDOMAIN-2-MTS_INITIALIZATION_FAILED: IPC initialization sequence

failed
Explanation The fcdomain has not been able to complete the initialization sequence with the IPC
(Inter Process Communication) subsystem. fcdomain depends on resources not available at the
moment: the switch might be short in memory or some other component might be unable to provide
the necessary information to fcdomain.
Error Message FCDOMAIN-2-MY_NON_VIRTUAL_DOM_CONFLICTS: During VSAN merge detected

that the local switch has the same domain ID [dec] and WWN [chars] of another
switch
Explanation It has been detected that the local switch has the same domain ID [dec] and WWN
[chars] of another switch.
Error Message FCDOMAIN-2-NON_VIRTUAL_DOMS_CONFLICTS: During VSAN merge detected

conflict between two switches having the same non-virtual domain ID [dec] and the
same WWN [chars]
Explanation It has been detected that two switches have the same non-virtual domain ID [dec] and
the same WWN [chars].
OL-26589-01 2-155
Error Message FCDOMAIN-2-PSSBIND_FAILED: Bind to Persistent Storage Service failed
Explanation Fcdomain has not been able to contact the Persistent Storage Service (PSS).
Error Message FCDOMAIN-2-RDIRJT: Rejected request for domain ID [dec], WWN requestor
[chars] (reason code [dec])
Explanation An invalid request for domain IDs has been rejected by fcdomain.
Recommended Action Perform [show fcdomain vsan <vsan-id>] for all the switches in the affected
VSAN; if a switch does not have a valid current domain ID, configure preferred domain ID zero,
then perform [fcdomain restart vsan <vsan-id>] in the affected VSAN.
Error Message FCDOMAIN-2-SYSBIND_FAILED: Bind to System Manager service failed
Explanation Fcdomain has not been able to contact the System Manager.
Error Message FCDOMAIN-2-SYSMGR_INITIALIZATION_FAILED: System Manager

initialization sequence failed
Explanation The fcdomain has not been able to complete the initialization sequence with the System
Manager. fcdomain depends on resources not available at the moment: the switch might be short in
memory or some other component might be unable to provide the necessary information to
fcdomain.
FCDOMAIN-3
Error Message FCDOMAIN-3-COMMITERRORLOCALINVALIDALLOWEDDOMS: A remote switch

attempted to locally apply an illicit allowed domains configuration
Explanation A remote switch attempted to locally apply an allowed domains configuration that
doesn't include all currently assigned domains or the locally configured domain.
2-156 OL-26589-01
Error Message FCDOMAIN-3-COMMITERRORREMOTEINVALIDALLOWEDDOMS: A remote switch

(domain ID [dec], WWN [chars]) refuses to locally apply the proposed allowed
domains
Explanation The remote switch with domain ID [dec] and WWN [chars] refuses to locally apply the
proposed allowed domains probably due to incompatibility with its local configured domain or the
domain ID list.
Recommended Action Check the configuration on the remote switch, and make sure that the proposed
allowed domains include it. Also, make sure that the the proposed allowed domains include all the
domains in the domain ID list.
Error Message FCDOMAIN-3-MTSOPENTRX_FAILED: IPC failure (opening of a transaction

failed)
Explanation Fcdomain was not able to open a transaction( HA Purposes.)
Error Message FCDOMAIN-3-MTSRECV_FAILED: IPC failure (receiving of a message

failed)
Explanation Fcdomain has not been able to receive a message from the Inter Process
Recommended Action Please perform fcdomain restart in the affected VSAN (non disruptive.)
Error Message FCDOMAIN-3-MTSRESP_FAILED: IPC failure replying to a request message

(error [hex])
Explanation Fcdomain has not been able to reply to a request coming from the Inter Process
Communication (IPC) module (error [hex]).
Recommended Action Please perform fcdomain restart in the affected VSAN (non disruptive).
Error Message FCDOMAIN-3-MTSSENDREQ_FAILED: IPC failure (sending of a request

failed)
Explanation Fcdomain was not able to send a request using the Inter Process Communication
module.
Recommended Action Please perform [fcdomain restart vsan <vsan-id>] in the affected VSAN (non
disruptive.)
OL-26589-01 2-157
Error Message FCDOMAIN-3-MTSSEND_FAILED: IPC failure (sending of a message (syserr

[hex], opc [dec], mtsq [dec], sap.node [hex], sap_addr [dec]) failed)
Explanation Fcdomain has not been able to send a message to the Message Transactional Service
(MTS).
Recommended Action Please perform [fcdomain restart vsan <vsan-id>] in the affected VSAN (non
disruptive).
Error Message FCDOMAIN-3-MTS_H_RECV_FAILED: IPC failure (receiving of a message

failed)
Explanation Fcdomain has not been able to receive a message from the Inter Process
Recommended Action Please perform fcdomain restart in the affected VSAN (non disruptive.)
Error Message FCDOMAIN-3-NVRAMFAILURE: NVRAM open failed
Explanation Reading the last assigned runtime domain IDs from Non Volatile RAM (NVRAM)
failed.
Recommended Action Fcdomain is able to continue without access to the Non Volatile RAM
(NVRAM.)
Error Message FCDOMAIN-3-PORT_SUSPENDED: Response (Cmd Code [hex]) for SWILS [hex]
intended for [chars] is received on [chars]
Explanation An FC2 response frame (Command Code [hex]) for SWILS [hex] that was intended for
interface [chars] has been received on [chars] instead.
Recommended Action Check the configuration of both interfaces on the local switch and the
interfaces on the other side of their corresponding links. In particular, check whether they should all
belong to the same port-channel.
Error Message FCDOMAIN-3-SDWRAPBIND_FAILED: Bind to debug server failed
Explanation Fcdomain feature has not been able to contact the debug service. Any problems
occurring in the fcdomain feature will not be logged.
Error Message FCDOMAIN-3-SDWRAPHISTINIT_FAILED: Initialization of history message

list failed.
Explanation Fcdomain feature has not been able to contact the debug history service. Any problems
occurring in the fcdomain feature will not be logged to this debug history.
2-158 OL-26589-01
Error Message FCDOMAIN-3-VSAN_MERGE_DETECTED: Merge detected with VSAN [dec]

(Common Fabric Name [chars])
Explanation The local VSAN and VSAN [dec] have the same principal switch [chars], hence are
connected in the same logical fabric.
FCDOMAIN-4
Error Message FCDOMAIN-4-DM_ALLOWED_DM_LIST_MOD_ON_SUBORDINATE: Allowed domain

list for vsan [dec] modified on subordinate switch with fcdomain distribution
enabled
Explanation When distribution is enabled, it is recommended to modify the allow domain list on the
principal switch only.
Recommended Action Abort the current session on the local switch and start a new one on the
principal switch.
Error Message FCDOMAIN-4-FABRICCONFSTARTRCF: Disruptive reconfiguration started
Explanation A disruptive reconfiguration (RCF phase) of the VSAN has started. This can happen
when two or more fabrics merge disruptively, or when the user manually triggers a diruptive
reconfiguration of the VSAN.
Error Message FCDOMAIN-4-FC2_CORRUPTED: Received malformed FC2 [chars] frame
Explanation Fcdomain received a malformed FC2-SWILS frame.
Error Message FCDOMAIN-4-FCID_PERSISTENT_TBL_ALMOST_FULL: FCID persistent table is

almost full
Explanation Fcdomain has 80% or more of the FCID persistent table full with entries. Perform
[show fcdomain fcid persistent vsan <vsan-id>] to view the entries currently in the table.
Recommended Action Purge stale entries [purge fcdomain fcid] to obtain more free entries.
OL-26589-01 2-159
FCDOMAIN-5
Error Message FCDOMAIN-5-DOMAIN_TYPE_IS_PREFERRED: The domain ID type is currently

configured as preferred in all the existing VSANs
Explanation All the currently existing VSANs have the domain ID type configured as preferred.
This means that with a low probability the domain ID of the local VSAN might change afer a
reconfiguration. A reconfiguration can happen when two or more VSANs are merged or a principal
link flaps. A principal link is either an upstream or a downstream link.
Recommended Action Type [fcdomain domain <dom-id> static vsan <vsan-id>] to configure as static
the domain ID type in an existing VSAN.
Error Message FCDOMAIN-5-FCIDP_DISABLED: FCID persistency feature is currently not

enabled in any of the existing VSANs
Explanation All the currently existing VSANs have the FCID persistency feature disabled.
Recommended Action Type [fcdomain fcid persistent vsan <vsan-id>] to enable FCID persistency in
an existing VSAN. Type [fcdomain fcid persistent global-enable] to automatically enable the FCID
persistency feature on all newly created VSANs.
Error Message FCDOMAIN-5-FCID_PERSISTENT_TBL_HALF_FULL: FCID persistent table is

half full
Explanation Fcdomain has 50% of the FCID persistent table full with entries. Perform [show
fcdomain fcid persistent vsan <vsan-id>] to view the entries currently in the table.
Recommended Action You may want to purge stale entries [purge fcdomain fcid] to obtain more free
entries.
Error Message FCDOMAIN-5-UNKNOWNDOMAININCFSDATAREQUEST: Received CFS Data request

from unknown domain [dec].
Explanation A CFS Data request from the unknown domain [dec] has been received.
Error Message FCDOMAIN-5-UNKNOWNDOMAININCFSLOCKREQUEST: Received CFS Lock request

Explanation A CFS Lock request from the unknown domain [dec] has been received.
2-160 OL-26589-01
Error Message FCDOMAIN-5-UNKNOWNDOMAININCFSRELEASEREQUEST: Received CFS Release

request from unknown domain [dec].
Explanation A CFS Release request from the unknown domain [dec] has been received.
Error Message FCDOMAIN-5-UNKNOWNDOMAININUNKNOWNCFSREQUEST: Received CFS request

Explanation A CFS request from the unknown domain [dec] has been received.
FCDOMAIN-6
Error Message FCDOMAIN-6-BF_STARTED: BF started by [chars]
Explanation Build Fabric has been started in this VSAN
Error Message FCDOMAIN-6-CANNOTFREESINGLEFCID: Impossible to free single FCIDs
Explanation Impossible to free single FCIDs.
Error Message FCDOMAIN-6-CLEARLOCKNOTIFICATIONRECEIVED: Implict lock release.
Explanation Lock has been implicitly released due to a clear session operation.
Error Message FCDOMAIN-6-DEVICEALREADYOWNSDIFFERENTFCIDS: The device already owns

different FCIDs
Explanation Requested different FCIDs without any freeing in between.
Error Message FCDOMAIN-6-DOMAINID_INVALID: Local domain ID invalid
Explanation The local domain ID is invalid.
OL-26589-01 2-161
Error Message FCDOMAIN-6-DOMAINID_VALID: Local domain ID [dec] available
Explanation The domain ID [dec] is available.
Error Message FCDOMAIN-6-DOWNSTREAM_SWITCHED: Downstream interface has been

fast-switched from [chars] to [chars]
Explanation Because of a link failure the downstream interface has been fast-switched from [dec]
to [dec].
Error Message FCDOMAIN-6-EPORT_ALREADY_CREATED: Interface [chars] already created
Explanation Interface [chars] already created.
Error Message FCDOMAIN-6-EPORT_ALREADY_DOWN: Interface [chars] is already down
Explanation Interface [chars] already down.
Error Message FCDOMAIN-6-EPORT_CLEANUP: Interface [chars] received cleanup request
Explanation Fcdomain on interface [chars] has received a cleanup request.
Error Message FCDOMAIN-6-EPORT_CREATED: Creation of interface [chars]
Explanation Fcdomain is going to create interface [chars].
Error Message FCDOMAIN-6-EPORT_DOWN: Interface [chars] is down
Explanation Fcdomain is going to remove interface [chars] from its database.
2-162 OL-26589-01
Error Message FCDOMAIN-6-FABRICCONFSTARTBF: Non disruptive reconfiguration started
Explanation A non disruptive reconfiguration (BF phase) of the VSAN has started. This can happen
when two or more fabrics merge, or when the user manually triggers a non diruptive reconfiguration
of the VSAN.
Error Message FCDOMAIN-6-FABRICNAME_INVALID: Fabric name not available
Explanation Fabric name not available.
Error Message FCDOMAIN-6-FABRICNAME_VALID: Fabric name [chars] available
Explanation Fabric name [chars] available.
Error Message FCDOMAIN-6-FCIDALREADYFREE: FCIDs already free
Explanation FCIDs already free.
Error Message FCDOMAIN-6-FCIDNOTSTORED: FCIDs not stored
Explanation FCIDs not stored.
Error Message FCDOMAIN-6-FCIDP_ENABLED_DOM_TYPE_PREFERRED: FCID persistency is

enabled, but the domain ID type is configured as preferred
Explanation The FCID persistency feature is enabled, but the domain ID type is configured as
preferred. This means that with a low probability the domain ID of the local VSAN might change
afer a reconfiguration. A reconfiguration can happen when two or more VSANs are merged or a
principal link flaps. A principal link is either an upstream or a downstream link. Should the domain
ID change, all the FCIDs associated with it would be invalidated.
Recommended Action Type [fcdomain domain <dom-id> static vsan <vsan-id>] to configure as static
the domain ID type in an existing VSAN.
Error Message FCDOMAIN-6-FCIDS_ASSIGNED: Assigned a sequence of 256 contiguous

FCIDs starting from FCID [hex]:[hex]:[hex]
Explanation Assigned a sequence of 256 contiguous FCIDs starting from FCID [hex]:[hex]:[hex].
OL-26589-01 2-163
Error Message FCDOMAIN-6-FCIDS_FREED: Freed a sequence of 256 contiguous FCIDs

starting from FCID [hex]:[hex]:[hex]
Explanation Freed a sequence of 256 contiguous FCIDs starting from FCID [hex]:[hex]:[hex].
Error Message FCDOMAIN-6-FCID_ASSIGNED: Assigned single FCID [hex]:[hex]:[hex]
Explanation Assigned single FCID [hex]:[hex]:[hex].
Error Message FCDOMAIN-6-FCID_FREED: Freed single FCID [hex]:[hex]:[hex]
Explanation Freed single FCID [hex]:[hex]:[hex].
Error Message FCDOMAIN-6-INCORRECTDOMAINRANGE: Requested FCIDs with domain field

not in expected range
Explanation Requested FCIDs with domain field not in expected range.
Error Message FCDOMAIN-6-INCORRECTDOMAIN: Requested FCIDs with domain field

different from local domain
Explanation Requested FCIDs with domain field different from local domain.
Error Message FCDOMAIN-6-INVALIDARG: Requested FCID of type 00.00.YY, but

specifying an entire area
Explanation Requested FCID of type 00.00.YY, but specifying an entire area.
Error Message FCDOMAIN-6-MY_SAME_WWN_DIFFERENT_DOMS_CONFLICTS: During VSAN merge

detected local WWN [chars] is already in use by another switch (the two switches
have different domain IDs: [dec] (local) and [dec])
Explanation It has been detected that the local switch has the same WWN [chars] of another switch,
and that they have different domain IDs: [dec] (local) and [dec].
Recommended Action Check which switches have the same WWN and change either one.
2-164 OL-26589-01
Error Message FCDOMAIN-6-NODOMAIN: Local domain not available
Explanation The local domain is not available yet.
Error Message FCDOMAIN-6-NOFREEFCID: No free FCIDs
Explanation No free FCIDs.
Error Message FCDOMAIN-6-NOTOWNER: Feature [dec] cannot free FCID [dec]:[dec]:[dec]

(feature [dec] is the actual owner)
Explanation Feature UUID [dec] cannot free FCID [dec]:[dec]:[dec] because it is not its owner
(UUID actual owner is [dec]).
Error Message FCDOMAIN-6-OTHER_SIDE_VIRTUAL_IVR_DOMS_OVERLAPPING: During VSAN

merge detected overlap with virtual IVR domain ID [dec] from across the link
Explanation It has been detected an overlap with the virtual IVR domain ID [dec] from across the
link during an attempt to merge the local VSAN.
Error Message FCDOMAIN-6-PSWSSTARTED: Principal Switch Selection started
Explanation Fcdomain started a principal switch selection phase to elect a principal switch in this
VSAN.
Error Message FCDOMAIN-6-RCF_STARTED: RCF started by [chars]
Explanation Reconfigure Fabric has been started in this VSAN
Error Message FCDOMAIN-6-REQSINGLEFCIDWITHINRESERVEDRANGE: Requested single FCIDs

in area [dec] within the reserved range
Explanation Requested single FCIDs in area [dec] within the reserved range.
OL-26589-01 2-165
Error Message FCDOMAIN-6-REQUESTEDFCIDNOTFREE: Requested FCIDs not free
Explanation Requested FCIDs not free.
Error Message FCDOMAIN-6-REQUESTEDFCIDRESERVED: Requested reserved FCIDs
Explanation Requested reserved FCIDs.
Error Message FCDOMAIN-6-REQUESTEDRESERVEDFCIDMISMATCH: Requested persistent

FCIDs, but there is a mismatch
Explanation Requested persistent FCIDs, but there is a mismatch.
Error Message FCDOMAIN-6-SAME_WWNS_DIFFERENT_DOMS_CONFLICTS: During VSAN merge

detected two switches with same WWN [chars] and different non-virtual domain IDs
[dec] and [dec]
Explanation It has been detected that two switches have the same WWN [chars], but different
non-virtual domain IDs: [dec] and [dec].
Recommended Action Check which switches have the same WWN and change either one.
Error Message FCDOMAIN-6-TIMER_UNKNOWN: fcdomain has received a notification for an

unknown timer expiration
Explanation A timer unknown to fcdomain has expired.
Error Message FCDOMAIN-6-UPSTREAM_SWITCHED: Upstream interface has been

fast-switched from [chars] to [chars]
Explanation Because of a link failure the upstream interface has been fast-switched from [dec] to
[dec].
Error Message FCDOMAIN-6-UUIDNOSPACEFOUND: No available space to store the identity

of the requestor the FCIDs
Explanation No available space to store the identity of the requestor the FCIDs.
2-166 OL-26589-01
Error Message FCDOMAIN-6-UUIDNOTFOUND: Universal Unique ID (UUID) not found
Explanation Universal Unique ID (UUID) not found.
Error Message FCDOMAIN-6-VIRTUAL_IVR_DOMS_OVERLAPPING: During VSAN merge detected

overlap with local virtual IVR domain ID [dec]
Explanation It has been detected an overlap with the local virtual IVR domain ID [dec] during an
attempt to merge the local VSAN.
FCDOMAIN-7
Error Message FCDOMAIN-7-EPORT_ALREADY_ISOLATED: Interface [chars] is already

isolated or down
Explanation Fcdomain was going to isolate interface [chars], but the interface is already isolated.
Error Message FCDOMAIN-7-FABRICCONFCOMPLETEDBF: Non disruptive reconfiguration

completed
Explanation A non disruptive reconfiguration (BF phase) completed. This can happen when two or
more fabrics merged, or when the user manually triggered a non diruptive reconfiguration of the
VSAN.
Error Message FCDOMAIN-7-FABRICCONFCOMPLETEDRCF: Disruptive reconfiguration

completed
Explanation A disruptive reconfiguration (RCF phase) of the VSAN has completed. This can
happen when two or more fabrics merged disruptively, or when the user manually triggered a
diruptive reconfiguration of the VSAN.
Error Message FCDOMAIN-7-FC2_RETRY: Retransmission of FC2 frame on interface

[chars] (Cmd Code: [hex])
Explanation Fcdomain is retrying an FC2 frame on interface [chars] due to loss/no response. The
Command Code of the frame is [hex].
OL-26589-01 2-167
Error Message FCDOMAIN-7-FCID_IN_USE_PURGING_FOR_FICON_MGR: FICON needs to purge

the persistent FCID table, but at least one FCID is still in use, preventing this
purge from completely remove all entries belonging to the VSAN.
Explanation There may be a problem in the sequence that shuts down all interfaces before fcdomain
receives a request from FICON Manager to purge the persistent FCID table.
Error Message FCDOMAIN-7-FSM_FAILED: FSM transition failed on interface [chars]

(current state [chars])
Explanation Fcdomain state machine generated an invalid event on interface [chars], for which no
proper action was defined (current state [chars].)
Error Message FCDOMAIN-7-FSM_FORBIDDEN_TRANSITION: fcdomain state machine has hit

a forbidden transition
Explanation Fcdomain state machine has tried to execute a forbidden transition.
Error Message FCDOMAIN-7-INTERFACERDY: Interface [chars] ready
Explanation Interface [chars] is ready.
Error Message FCDOMAIN-7-PREACTIONTYPE_UNKNOWN: fcdomain state machine has hit an

unknown pre-action type
Explanation An undefined pre-action type has been used.
Error Message FCDOMAIN-7-PSWSCOMPLETED: Principal Switch Selection completed
Explanation A Principal Switch Selection (PSwS phase) completed.
Error Message FCDOMAIN-7-RDIACC: Assigned domain ID [dec], WWN of requestor [chars]

(requested domain ID [dec])
Explanation Domain ID [dec] has been received by VSAN with WWN [chars] (requested domain
ID was [dec].)
2-168 OL-26589-01
FCD Messages
This section contains the FCD messages.
FCD-7
Error Message FCD-7-SB3_ABTS_EXCHANGE: sb3 aborted exchange [hex] from vsan:[dec]

ch:[hex] chi:[hex] ccw:[hex] token:[hex] cmd:[hex] reason:[chars]
state:[chars]:[dec]
Explanation SB3 aborted exchange due to reason given. Aborts are caused by either the channel or
control unit detecting a device protocol error. Recovery actions are performed to restore
communication. In certain circumstances aborts occur in normal operations.
Recommended Action No action is required if communication with CUP device is still operational.
Error Message FCD-7-SB3_UCS_PER_FILE_FN: VSAN:[dec] Unit Check for perform file

function, reason: [chars]
Explanation SB3 failed perform file function. Failure is caused by error in the file main frame sent
to director.
Recommended Action No action is required if communication with CUP device is still operational.
FCFWD Messages
This section contains the FCFWD messages.
FCFWD-3
Error Message FCFWD-3-ERROR: [chars]
Explanation Fcfwd encountered an error
FCFWD-4
Error Message FCFWD-4-WARNING: [chars]
Explanation Fcfwd is generating a relevant notification
OL-26589-01 2-169
FCFWD-6
Error Message FCFWD-6-INFO: [chars]
Explanation An fcfwd event occurred
FCNS Messages
This section contains the FCNS messages.
FCNS-2
Error Message FCNS-2-DB_FULL: the database; max entries [dec] exceeded
Explanation Name server database is full. The max number of entries, [dec], of ports is already
present in the database
Error Message FCNS-2-INIT_FAILURE: : [chars]
Explanation Fcns initialisation has failed due to [chars].
Error Message FCNS-2-NO_RESPONSE: for query [chars] from domain [dec]
Explanation No response for query [chars] from domain [dec].
Error Message FCNS-2-PSS_VERSION_MISMATCH: : for [chars]
Explanation Version mismatch for pss of type [chars].
Error Message FCNS-2-RELOAD_FAILURE: : [chars]
Explanation Failed to reload information from PSS: [chars].
2-170 OL-26589-01
FCNS-3
Error Message FCNS-3-BAD_FRAME: : [chars]
Explanation Received a bad frame from the network: [chars].
Error Message FCNS-3-CFG_FAILURE: : [chars]
Explanation A failure related to fcns configuration: [chars].
Error Message FCNS-3-CHUNK_FAILURE: : [chars]
Explanation Chunk memory failure: [chars].
Error Message FCNS-3-DB_FAILURE: : [chars]
Explanation A failure occured in fcns database: [chars].
Error Message FCNS-3-MALLOC_FAILURE: : [chars]
Explanation Malloc failed: [chars].
Error Message FCNS-3-MTS_FAILURE: : [chars] [chars]
Explanation Failure occured trying to do an MTS operation: [chars] [chars].
Error Message FCNS-3-PSS_FAILURE: : [chars]
Explanation Pss failure: [chars].
OL-26589-01 2-171
FCNS-4
Error Message FCNS-4-QUERY_NO_RESPONSE: for query [chars] from domain [dec]
Explanation No response for query [chars] from domain [dec].
FCNS-6
Error Message FCNS-6-DB_INFO: : [chars] [hex]
Explanation Database modification:[chars] for entry [hex].
Error Message FCNS-6-STATUS_INFO: : [chars]
Explanation A change in fcns status: [chars].
FCOE_MGR Messages
This section contains the FCOE_MGR messages.
FCOE_MGR-2
Error Message FCOE_MGR-2-FCOE_MGR_MODULE_NOT_LICENSED: FCoE Manager Module:[dec]

not licensed
Explanation FCOE_MGR Line Card not licensed
Error Message FCOE_MGR-2-FCOE_MGR_PSS_RESTORE_FAILED: FCoE Manager PSS Restore

operation failed, error: [chars]
Explanation FCoE Manager PSS Restore operation failed
2-172 OL-26589-01
FCOE_MGR-5
Error Message FCOE_MGR-5-FCOE_MGR_DISABLED: FCOE_MGR Disabled
Explanation FCOE_MGR Service Disabled
Error Message FCOE_MGR-5-FCOE_MGR_ENABLED: FCOE_MGR Enabled
Explanation FCOE_MGR Service nabled
Error Message FCOE_MGR-5-FCOE_MGR_INFO: [chars]
Explanation FCoE Manager general info
Error Message FCOE_MGR-5-FCOE_MGR_MODULE_LICENSE_CHECKIN: FCoE Manager License

Checkin:[dec]
Explanation FCOE_MGR Line Card license checked in
Error Message FCOE_MGR-5-FCOE_MGR_MODULE_LICENSE_CHECKOUT: FCoE Manager License

Checkout:[dec]
Explanation FCOE_MGR Line Card license checked out
Error Message FCOE_MGR-5-FCOE_MGR_SOLICITATION_FROM_SAME_MAC: FCoE Manager received

Mulicast Solication from same MAC: [chars]
Explanation FCoE Manager received Mulicast Solication from same MAC
OL-26589-01 2-173
Error Message FCOE_MGR-5-FCOE_MGR_VE_DUPLICATE_PEER_MAC: FCoE Manager has already

received unicast advertisement from MAC [chars] on a different VE link. Bringing
down this link
Explanation FCoE Manager has already received unicast advertisement from same MAC on a
different VE link
FCSP-MGR Messages
This section contains the FCSP-MGR messages.
FCSP-MGR-2
Error Message FCSP-MGR-2-DBG_INIT_FAILED: Debug Infrastructure Initialization

failed ( [chars] )
Explanation The system has detected an error.
Error Message FCSP-MGR-2-FC2_E_INIT_FAILED: Fibre-Channel Initialization of an

E_Port failed ( [chars] )
Explanation FC-SP Manager has been unable to initialize with the FC-2 E-Port infrastructure.
Error Message FCSP-MGR-2-FC2_F_INIT_FAILED: Fibre-Channel Initialization of an

F_Port failed ( [chars] )
Explanation FC-SP Manager has been unable to initialize with the FC-2 F-Port infrastructure.
Error Message FCSP-MGR-2-FC2_UNKNOWN_FRM_RECD_CRIT: Received an unexpected/unknown

FC-2 frame on [chars]
2-174 OL-26589-01
Error Message FCSP-MGR-2-FCSP_AUTHENT_FAILURE: FC-SP Authentication failure on Port

[chars] (FC-SP Failure Reason: [chars] [chars])
Explanation Fibre-Channel Authentication failure on Port [chars].(Reason Code [chars] Detail

[chars]). Please check password configurations and ensure appropriate security modes on this port
as well as peer port
Error Message FCSP-MGR-2-FCSP_ESP_MISMATCH: ESP parameters mismatch failure on Port

[chars] (reason:[chars])
Explanation Fibre-Channel ESP parameters mismatch with the peer on Port [chars].(Reason:
[chars]). Please check ESP configurations on both side of the link and ensure appropriate ESP mode
on this port as well as peer port
Error Message FCSP-MGR-2-FSMU_INIT_FAILED: State Machine Infrastructure

Error Message FCSP-MGR-2-IPC_INIT_FAILED: IPC (Inter Process Communication)

Explanation FC-SP Manager has been unable to initialize with the IPC infrastructure.
Error Message FCSP-MGR-2-LICENSE_UNAVAILABLE: License:[chars] unavailable, service

exiting
Explanation License of [chars] is unavailable. Service will exit now
Error Message FCSP-MGR-2-MEM_FAILED: Memory operations failed File: [chars] Line

[dec] for size [hex] bytes
OL-26589-01 2-175
Error Message FCSP-MGR-2-POST_INIT_FAILED: Post-Initialization failed ( [chars] )
Error Message FCSP-MGR-2-PSS_INIT_FAILED: PSS Infrastructure Initialization failed

( [chars] )
FCS Messages
This section contains the FCS messages.
FCS-2
Error Message FCS-2-ALLOC_FAILED: Memory allocation failed for size:[dec]
Explanation Memory allocation failed for size [dec]
Recommended Action Restart the process
Error Message FCS-2-CHUNK_ALLOC_FAILED: Chunk memory allocation failed for [chars]

chunk
Explanation Chunk memory allocation failed. [chars] indicates the chunk name
Recommended Action Restart the process
Error Message FCS-2-NO_RESPONSE: Retried maximum number of times for [chars] to

domain [dec] in VSAN [dec]
Explanation Maximum number of retires completed for [chars] form domain [dec] in VSAN [dec].
Error Message FCS-2-PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec],

expected version [dec].[dec].[dec]
2-176 OL-26589-01
Error Message FCS-2-RANDNUM_FAIL: [chars]
Explanation There was a critical error during random number generation. [chars] indicates details
of the error
FCS-3
Error Message FCS-3-DB_ERR: [chars]
Explanation An error occurred during an FCS database operation. [chars] indicates the reason for
the error
Error Message FCS-3-INIT_FAIL: [chars]
Explanation An error happened during FCS Initialization. [chars] indicates the reason for failure
Error Message FCS-3-MTS_API_ERR: [chars] : [chars]
Explanation An error occurred in send or receive of an MTS message. [chars] indicates the error that
occurred and [chars] indicates the error number
Error Message FCS-3-MTS_ERR: [chars]
Explanation An error occurred in processing of an MTS message. [chars] indicates the error that
occurred
Error Message FCS-3-NO_MTS_RESP: [chars]
Explanation There was no response to an MTS request. [chars] indicates details of the MTS message
OL-26589-01 2-177
Error Message FCS-3-NO_REMOTE_RESP: No response for request [chars] from domain

[dec] in VSAN [dec]
Explanation There was no response to an FC2 request. [chars] indicates FCS request [dec] indicates
the remote domain and [dec] the VSAN ID
Error Message FCS-3-OTHER_ERR: [chars]
Explanation An FCS generic error occurred. [chars] indicates the description of the error
Error Message FCS-3-PSS_ERR: [chars]
Explanation An error occurred during an FCS PSS operation. [chars] indicates the PSS operation
Error Message FCS-3-SOCK_ERR: sd: [dec], [chars]
Explanation An FC-2 Socket error occurred on socket-ID [dec]. [chars] indicates the reason for
failure
FCS-5
Error Message FCS-5-API_FAIL: [chars]: [chars]
Explanation An API called by FCS failed. [chars] indicates the API name failed and [chars] the
reason for failure
Recommended Action If this message is seen during a cold boot, it means that the queried module
came up after FCS and this case can be ignored
Error Message FCS-5-DB_NOTICE: [chars]
Explanation An error occurred during an FCS database operation. [chars] indicates the reason for
the error
2-178 OL-26589-01
FCS-6
Error Message FCS-6-BAD_CT_FRAME: Invalid FCS frame: [chars] received from [hex]
Explanation An invalid FCS FC-CT frame with [chars] received from FC-ID [hex].
Error Message FCS-6-INFORMATION: [chars]
Explanation An event happend that affects FCS. [chars] indicates the event
Error Message FCS-6-REXMIT_PKT: Retransmitting request [chars] to domain [dec] in

VSAN [dec]
Explanation There was a retransmission of an FC2 request. [chars] indicates FCS request [dec]
indicates the remote domain and [dec] the VSAN ID
FDMI Messages
This section contains the FDMI messages.
FDMI-2
Error Message FDMI-2-FDMI_INIT_FAILED: FDMI initialization failed : [chars]
Explanation Fdmi process encountered error while starting
Error Message FDMI-2-MTS_ERROR: MTS message transmission failed with error [dec]
Explanation Fdmi process unsuccessfully tried to send a MTS message. MTS errro number is
specified in [dec]
OL-26589-01 2-179
Error Message FDMI-2-PSS_CFG_RESTORE_ERROR: Configuration restoration for [chars]

failed with error [hex] for key type [dec]
Explanation Fdmi read the saved configuration and encountered an error while rebuilding the
runtime configuration. [chars] describes the configuration which the process tried to restore and
0x[hex] is the system err code
Error Message FDMI-2-PSS_RTDB_RESTORE_ERROR: Runtime database restoration for

Explanation Fdmi read the saved runtime database and encountered an error while rebuilding the
runtime database. [chars] describes the runtime database which the process tried to restore and
0x[hex] is the system err code
FDMI-3
Error Message FDMI-3-BAD_FRAME: Malformed frame received: [chars]
Explanation Fdmi process received malformed frame. [chars] describes the malformation
Error Message FDMI-3-BAD_RESPONSE: response with command code: [hex]
Explanation Fdmi process received bad payload in response
Error Message FDMI-3-INTERNAL_ERROR: Internal err: [chars]
Explanation Fdmi process encountered a general error, one that does not fall in any of the categories.
[chars] describes the error and its context.
Error Message FDMI-3-MTS_API_ERROR: API, [chars] returned [hex]
Explanation Fdmi invoked API [chars], received the error code specified in 0x[hex]
2-180 OL-26589-01
Error Message FDMI-3-MTS_FORMAT_ERROR: Unknown MTS message format in opcode [dec]

from module [chars]
Explanation Fdmi received message from module [chars] which contains unknown message format.
MTS opcode is specified in [dec]
Error Message FDMI-3-NO_RESPONSE: No response from switch whose domain id is [dec]
Explanation Fdmi process sents a inter-switch packets to switches and has not received the response
Error Message FDMI-3-PSS_ERROR: PSS operation [chars] returned err: [hex]
Explanation [chars] specifies the context where the failure occured and 0x[hex] specifies the err
Error Message FDMI-3-UNEXPECTED_MTS_MSG: Unexpected MTS message, opcode [dec], is

received
Explanation Fdmi process received unexpected MTS event. MTS opcode is specified in [dec]
FDMI-4
Error Message FDMI-4-SW_REJ_RESPONSE: Reject response [chars] from switch whose

domain id is [dec]
Explanation Fdmi process sents a inter-switch packets to switches and has received the reject
response with reason code in [chars]
FDMI-6
Error Message FDMI-6-DEBUG_INFO: [chars]
Explanation Fdmi process debug info
OL-26589-01 2-181
FEATURE-MGR Messages
This section contains the FEATURE-MGR messages.
FEATURE-MGR-2
Error Message FEATURE-MGR-2-FM_AUTOCKPT_FAILED: AutoCheckpoint [chars] failed to be

created for reason: [chars] ([hex])
Explanation AutoCheckpoint with the given name has been created successfully
Error Message FEATURE-MGR-2-FM_FEATURE_LICENSE_ERROR: the license operation for

feature failed [hex] [chars]
Explanation License operation was not successful, check license validity for the feature
Recommended Action Please contact FM team
Error Message FEATURE-MGR-2-FM_FEATURE_LICENSE_ERROR: license [chars] checkout

failure for [chars], error [hex] ([chars])
Explanation License operation was not successful, check license validity for the feature
Error Message FEATURE-MGR-2-FM_FEATURE_OP_TIMEOUT_ERROR: feature [chars] operation

failed on response timeout from service: [chars] with uuid ([hex])
Explanation The error seen at FM and service communication
Recommended Action Please contact service owner with given uuid and FM team
Error Message FEATURE-MGR-2-FM_FSET_ADD_CONFCHECK_ERROR: failed to add confcheck

[hex] ([chars]) at installing feature-set [chars]
Explanation Failed to add confcheck at enabling feature-set
Recommended Action Please contact FM/sysmgr team
Error Message FEATURE-MGR-2-FM_FSET_CFG_ALLOW_ERROR: Potential vdc_mgr issue: the

allow request failed [hex] ([chars])
Explanation Vdc_mgr failed to response the allow request
Recommended Action Please contact FM/vdc_mgr team
2-182 OL-26589-01
Error Message FEATURE-MGR-2-FM_FSET_CKPT_ERROR: Checkpoint issue: failed on

checkpoint with error [hex] ([chars]) at feature-set [chars]
Explanation Checkpoint did not response
Recommended Action Please contact FM/vdc_mgr and rollback team
Error Message FEATURE-MGR-2-FM_FSET_DISABLE_ERROR: Potential sysmgr issue: disable

feature-set [chars] on sup failed with error [hex] ([chars])
Explanation Some issues while disabling feature-set
Error Message FEATURE-MGR-2-FM_FSET_DISABLE_FEATURES_ERROR: features failed to

disable at feature-set [chars] with error [hex] ([chars])
Explanation Failed to disable feature at disabling feature-set
Error Message FEATURE-MGR-2-FM_FSET_DISABLE_FEATURES_TIMEOUT: Potential [chars]

issue: feature [chars] did not complete its disabling
Explanation Failed to disable feature at disabling feature-set
Recommended Action Please contact FM/sysmgr team and the feature owner
Error Message FEATURE-MGR-2-FM_FSET_INSTALL_ERROR: install feature-set [chars]

returns error 0X[hex] ([chars])
Explanation Somes issues during install feature-set
Error Message FEATURE-MGR-2-FM_FSET_LCS_DISABLE_ERROR: Potential sysmgr issue:

disable feature-set [chars] failed on module [dec] with error [hex] ([chars])
Explanation Some issues on the lc while disabling feature-set
Error Message FEATURE-MGR-2-FM_FSET_LCS_ENABLE_ERROR: enabling feature-set [chars]

on module [dec] returns error 0X[hex] ([chars])
Explanation Somes issue on the lc while enabling feature-set
OL-26589-01 2-183
Error Message FEATURE-MGR-2-FM_FSET_PRESEQ_REJECT: It rejects pre-sequence due to

a service with sap [dec]: [chars]
Explanation The message seen when an application rejects feature-set disable request
Error Message FEATURE-MGR-2-FM_FSET_SUP_ENABLE_ERROR: enabling feature-set [chars]

on sup returns error 0X[hex] ([chars])
Explanation Some issues during enabling feature-set
Error Message FEATURE-MGR-2-FM_FSET_UNGRACEFUL_DISABLE_ERROR: Potential sysmgr

issue: ungraceful disable feature-set [chars] failed with error [hex] ([chars])
Explanation Some issues while ungraceful disable feature-set
Error Message FEATURE-MGR-2-FM_FSET_UNGRACEFUL_UNINSTALL_ERROR: Potential sysmgr

issue: ungraceful uninstall feature-set [chars] failed with error [hex] ([chars])
Explanation Some issues while ungraceful uninstall feature-set
Error Message FEATURE-MGR-2-FM_FSET_UNINSTALL_ERROR: Potential sysmgr issue:

uninstall feature-set [chars] failed with error [hex] ([chars])
Explanation Some issues while uninstall feature-set
Error Message FEATURE-MGR-2-FM_FSET_VMM_OP_ERROR: [chars]
Explanation The error seen at FM and VMM interaction
Recommended Action Please contact FM/VMM team
Error Message FEATURE-MGR-2-MODULE_FM_DONE: feature manager completed
Explanation Feature manager completed
2-184 OL-26589-01
Error Message FEATURE-MGR-2-MODULE_FM_STARTED: feature manager started
Explanation Feature manager started
FEATURE-MGR-6
Error Message FEATURE-MGR-6-FM_AUTOCKPT_IN_PROGRESS: AutoCheckpoint

[chars]screationinprogress...'
Explanation AutoCheckpoint creation has been requested and it should be in progress
Error Message FEATURE-MGR-6-FM_AUTOCKPT_SUCCEEDED: AutoCheckpoint [chars] created

successfully
Explanation AutoCheckpoint with the given name has been created successfully
Error Message FEATURE-MGR-6-FM_FCOE_AUTOINSTALL_ON_NOT_ISOLA: auto-install

feature-set fcoe on non-isola
Explanation Auto-install feature-set fcoe could be done on isola only
Error Message FEATURE-MGR-6-FM_FSET_ENABLED_AT_UNINSTALL: Uninstall aborted because

feature set is still enabled in vdc [dec]
Explanation Feature set is in enabled state
FEX Messages
This section contains the FEX messages.
FEX-2
Error Message FEX-2-FEX_NOT_ONLINE_SUP_ISSU: FEX [dec] did not come online after
SUP ISSU
Explanation FEX did not come online after sup ISSU
OL-26589-01 2-185
Error Message FEX-2-FEX_OFFLINE: FEX [dec] has gone OFFLINE
Explanation FEX has gone OFFLINE
Error Message FEX-2-FEX_ONLINE: FEX [dec] has come ONLINE
Explanation FEX has come ONLINE
Error Message FEX-2-FEX_PORT_STATUS_CRIT: Uplink-ID [dec] of Fex [dec] that is

connected with [chars] changed its status from [chars] to [chars]
Explanation Fex [decimal-digit] changed port status
Error Message FEX-2-NOHMS_ENV_FEX_OFFLINE: [chars]
Explanation Fex off-line
Recommended Action Show inventory
Error Message FEX-2-NOHMS_ENV_FEX_ONLINE: [chars]
Explanation Fex on-line
Recommended Action Show inventory
FEX-5
Error Message FEX-5-FEX_DISABLED: FEX Disabled
Explanation FEX Service Disabled
Error Message FEX-5-FEX_ENABLED: FEX Enabled
Explanation FEX Service Enabled
2-186 OL-26589-01
Error Message FEX-5-FEX_PORT_STATUS_NOTI: Uplink-ID [dec] of Fex [dec] that is

connected with [chars] changed its status from [chars] to [chars]
Explanation Fex [decimal-digit] changed port status
Error Message FEX-5-PINNING_CHANGED: Fex [dec] pinning information is changed
Explanation Fex pinning information changed
Error Message FEX-5-SATMGR_DISABLE_FAILED: Disabling of feature FEX failed. Please

remove FEX related configs from interfaces
Explanation Disabling of FEX feature failed
FICON Messages
This section contains the FICON messages.
FICON-2
Error Message FICON-2-E_DUPLICATE_PN_BRINGUP_FAIL: [chars]
Explanation This port has the same port number assigned to other port in the same FICON VSAN.
No more than one port with duplicate port number can be up in each FICON VSAN
Recommended Action Avoid duplicate number assignment in each FICON VSAN
Error Message FICON-2-E_PN_PA_NOT_IN_BOUND: [chars]
Explanation Port number or port address in startup-configure is out of bound.
Recommended Action Change ficon port number assign configuration and save to startup-configure.
Error Message FICON-2-E_SAVE_FILE: [chars]
Explanation Failed to save file. Possibly due to asymmetric pdcm matrix. Look for retval for actual
reason.
Recommended Action Configure port prohibits in symmetrically.
OL-26589-01 2-187
Error Message FICON-2-SHUTDOWN: FICON Manager process shutting down: [chars]
Explanation FICON Manager shutting down
Recommended Action This is a severe error. Provide the reason given in the message.
FICON-3
Error Message FICON-3-E_ASSIGN_BINDING_PN_FAIL: [chars]
Explanation Port number has fcip or port channle binding can not be removed nor changed.
Recommended Action Remove port number binding of the logical interface first.
Error Message FICON-3-E_ASSIGN_INVALID_PN_PARAM: [chars]
Explanation Invalid port number parameters in command.
Recommended Action Check port numbers in the command.\n
Error Message FICON-3-E_ASSIGN_OVERLAP_PN_FAIL: [chars]
Explanation Port number assigned to physical and logical can not overlap.
Error Message FICON-3-E_ASSIGN_PN_NOT_DOWN_FAIL: [chars]
Explanation Only port number assigned to a port in down state can be removed or changed.
Recommended Action Bring down the port first.\n
Error Message FICON-3-E_ASSIGN_PROHIBIT_PN_FAIL: [chars]
Explanation Logical port address can not be prohibited.
Error Message FICON-3-E_DUPLICATE_PN_ASSIGN_WARNING: [chars]
Explanation This port has the same port number assigned to other port in the same FICON VSAN.
No more than one port should have the same port number in each FICON VSAN
Recommended Action Avoid duplicate number assignment in each FICON VSAN\n
2-188 OL-26589-01
Error Message FICON-3-E_INVALID_PA_BRINGUP_FAIL: [chars]
Explanation This port either has an invalid port address assigned or has no port address assigned.
Recommended Action Assign a valid ficon port number to the port.\n
Error Message FICON-3-E_PORT_PROHIBIT_BRINGUP_FAIL: [chars]
Explanation This port has been prohibited. Prohibiting E or TE ports is not allowed. This port can
not be configured in E mode or TE mode until the prohibit mask configuration is changed
Recommended Action Correct the prohibit mask (PDCM) for this port if you wish to bring it up as
an E or TE port in a FICON VSAN\n
Error Message FICON-3-E_UNASSIGN_NO_PN_FAIL: [chars]
Explanation Only port number already assigned can be removed.
Error Message FICON-3-PDCM_CHANGE_REJ_E_PORT: [chars]
Explanation The FICON Prohibit Dynamic Connectivity Mask(PDCM) change rejected because an
E or TE port is being prohibited. Prohibiting an E or TE port in not allowed
Recommended Action Correct the prohibit mask (PDCM) for this port if you wish to bring the port
up as an E or TE port in a FICON VSAN.
FICON-5
Error Message FICON-5-STARTING: FICON Manager process starting
Explanation FICON Manager process is being started
FICON-6
Error Message FICON-6-PDCM_CHANGE: VSAN [dec] port-address [dec] prohibit mask set
to [chars]
Explanation The FICON Prohibit Dynamic Connectivity Mask (PDCM) for this port has changed.
VSAN [dec], port address [dec] prohibit mask (PDCM) is now set to [chars]
OL-26589-01 2-189
Error Message FICON-6-PORT_SWAP: port number [dec] [dec] swapped
Explanation FICON portnumbers swapped
Error Message FICON-6-VSAN_DISABLED: FICON disabled on VSAN [dec]
Explanation FICON has been disabled on the given VSAN
Error Message FICON-6-VSAN_ENABLED: FICON enabled on VSAN [dec]
Explanation FICON has been enabled on the given VSAN
FLOGI Messages
This section contains the FLOGI messages.
FLOGI-1
Error Message FLOGI-1-MSG_FDISC_REJECT_TOO_MANY_LOGINS: [VSAN [dec], Interface

[chars]] FDISC rejected - this interface has reached the max num of N-Ports ([dec])
Explanation An FDISC was rejected because the F-Port has reached the maximum allowed number
of devices.
Recommended Action Check the configuration of the NPIV device connected to the port.
Error Message FLOGI-1-MSG_FLOGI_REJECT_FCID_ERROR: [VSAN [dec], Interface [chars]]

FLOGI rejected - FCID allocation failed.
Explanation An FLOGI was rejected because the FCID allocation failed.
Recommended Action Check the fcid-interop configuration, purge the persistency table and check the
output of show flogi database details and see if any of the A area FCID allocation entries can be
turned to single fcid allocation as per Configuration Guide
2-190 OL-26589-01
Error Message FLOGI-1-MSG_FLOGI_REJECT_TOO_MANY_LOGINS: [VSAN [dec], Interface

[chars]] FLOGI rejected - this interface has reached the max num of NL-Ports
([dec])
Explanation An FLOGI was rejected because the FL-Port has reached the maximum allowed
number of devices.
Recommended Action Reduce the number of devices on the loop
Error Message FLOGI-1-MSG_NPIV_NOT_SUPPORTED_WITH_TRUNKING: [VSAN [dec], Interface

[chars]] NPIV not supported - on this platform, NPIV is not supported on trunking
interfaces
Explanation The N_Port requested NPIV, but this platform does not support NPIV on trunking
F_Ports.
Recommended Action Disable NPIV, or move the N_Port to a switch that supports NPIV on trunking
F_Ports
FLOGI-2
Error Message FLOGI-2-MSG_FLOGI_REJECT_NO_ACL_TCAM_AVAILABLE: [VSAN [dec],

Interface [chars]] FLOGI rejected - ACLTCAM resource exausted
Explanation An FLOGI was rejected because the ACLTCAM hardware resource is completely used.
Recommended Action Reduce the number of nodes.
FLOGI-4
Error Message FLOGI-4-MSG_VF_FLOGI_FROM_NON_CISCO_OUI: [VSAN [dec], Interface

[chars]] FLOGI with VF bit set from OUI [hex]:[hex]:[hex] (nwwn: [chars])
Explanation This interface received an FLOGI with VF bit set from a non CISCO OUI; in this
release Virtual Fabrics are not supported on interfaces connected to third-party devices
Recommended Action Set the trunk mode of this interface to off
FLOGI-5
Error Message FLOGI-5-MSG_FLOGI_DROP_DUE_TO_SUSPENDED_VSAN: [VSAN [dec], Interface

[chars]] FLOGI (pwwn: [chars]) has been dropped because the VSAN is suspended on
this trunking interface
Explanation The switch received an FLOGI from a trunking interface on a VSAN which has been
suspended; the FLOGI frame has been dropped.
Recommended Action To bring up the VSAN again on the trunking port, remove it from the allowed
VSAN list and add it again
OL-26589-01 2-191
Error Message FLOGI-5-MSG_FLOGI_DUPLICATE_WWPN: [VSAN [dec], Interface [chars]]

FLOGI (pwwn: [chars]) has been dropped because the host has a duplicate WWPN
Explanation The switch received an FLOGI from the interface, which has a duplicate PWWN value.
Error Message FLOGI-5-MSG_IF_REINIT_ALPA_CONFLICT: [VSAN [dec], Interface [chars]]

FL/TL interface [chars] re-initialized as ALPA - PWWN map conflict occurred.
Explanation The FL/TL interface is re-initialized as ALPA used by device conflicts with an existing
FLOGI session after the Loop Initialization Protocol (LIP). All the devices will re-login with new
ALPA and PWWN mapping
Error Message FLOGI-5-MSG_PORT_LOGGED_IN: [VSAN [dec], Interface [chars]] Nx Port

[chars] with FCID [chars] logged IN.
Explanation Nx port logged in with the specified information.
Error Message FLOGI-5-MSG_PORT_LOGGED_OUT: [VSAN [dec], Interface [chars]] Nx Port

[chars] logged OUT.
Explanation Nx port logged out. The following commands will help determine why this Nx port
logged out: 'show interface, show VSAN, show module'
FS-DAEMON Messages
This section contains the FS-DAEMON messages.
FS-DAEMON-2
Error Message FS-DAEMON-2-FSD_ENOSPC_BOOTFLASH: Due to insufficient space, [chars]

image could not be copied to standby bootflash. [chars] image is not present on
standby. Please copy \[chars]\'manually.'
Explanation Move system images from RAM to bootflash to free up some memory
Recommended Action Please remove some unnecessary files on bootflash using

\delete\'CLIcommandandcopyimagesfromactivesupervisororfromremotelocation'
2-192 OL-26589-01
FS-DAEMON-6
Error Message FS-DAEMON-6-FSD_ENOSPC_LOGFLASH: System logflash usage has reached

[dec]%. You may delete some old files on logflash to free up space
Explanation System logflash space is almost full
Recommended Action Use 'clear core archived' or 'delete' CLI to free up space on logflash
Error Message FS-DAEMON-6-FSD_ENOSPC_ROOT: System root usage has reached [dec]%.

You may delete some old files from root or /var/log to free up space
Explanation System root space is almost full
Recommended Action Use 'clear core archived' or 'delete' CLI to free up space on root dir or /var/log
Error Message FS-DAEMON-6-FSD_ENOSPC_TMP: System temporary directory usage has

reached [dec]%.
Explanation System /tmp space usage.
Error Message FS-DAEMON-6-FSD_REEXPORT_NFS: Re-exported NFS mounts
Explanation Exported NFS mounts are not visible in kernel and had to be reexported
Recommended Action Please use showsysteminternalflash'tomakesuretherearenoStaleNFShandles'
FSCM Messages
This section contains the FSCM messages.
FSCM-2
Error Message FSCM-2-FABRIC_START_CFG_MGR_PROGRAM_EXIT: Fabric Start Cfg Mgr daemon

exiting: [chars]
Explanation FABRIC_START_CFG_MGR daemon is exiting.
OL-26589-01 2-193
FSPF Messages
This section contains the FSPF messages.
FSPF-2
Error Message FSPF-2-SHUTDOWN: Routing daemon shutting down : [chars]
Explanation FSPF routing daemon is shutting down because of [chars] reason.
Recommended Action This is a severe bug. Provide the reason provided and the log files for FSPF.
FSPF-2
Error Message FSPF-3-BAD_FC2_PKT: Received bad FC2 packet on interface [chars] :

[chars]
Explanation FSPF received a bad FC2 packet on [chars] interface , error description is [chars].
Recommended Action FSPF daemon has received a bad FC frame. Provide the output of 'debug fc2
pkt '.
Error Message FSPF-3-CHECKSUM_FAIL: Checksum test failed for LSR domain [dec]
Explanation Periodic database checksum test failed for LSR for domain [dec]
Recommended Action This indicates that the internal database got corrupted because of some
memory corruption bug. Provide output of 'show fspf database '. May need to power cycle the switch
Error Message FSPF-3-FC2_PROC_ERR: Error in processing [chars] packet on interface

[chars], Error = [chars]
Explanation An error occurred in processing a [chars] FC2 packet on [chars] interface. The internal
error code is [chars].
Recommended Action Turn on 'debug fspf error' to get more information. Make sure there is no
misconfiguration of FSPF parameters on the two ends of the interface. Provide output of 'show fspf
vsan x' 'show fspf vsan x interface' and 'debug fspf fc pkt ' for the specific interface
Error Message FSPF-3-FLOOD_ERR: Error in flooding the local LSR , Error = [chars]
Explanation FSPF had an error in flooding the local LSR , error description is [chars].
Recommended Action Provide output of 'debug fspf flood' , 'debug fspf error'. If error is reported in
transmitting packet check if interface is up and turn on 'debug fc2 error'
2-194 OL-26589-01
Error Message FSPF-3-HELLO_MISMATCH: Mismatch in [chars] in the Hello packet on

interface [chars]
Explanation There is a mismatch in the [chars] entry in the hello packet received on interface
[chars]. The packet will be dropped.
Recommended Action Check the configuration of hello or dead interval on the switches on the two
ends of the interface to see if there is a mismatch.
Error Message FSPF-3-INTF_TIMER_ERR: Error in processing interface timer event

[chars] for interface [chars] , error = [chars]
Explanation FSPF had an error in processing timer event for interface chars, error is [chars].
Recommended Action Provide output of 'debug fspf error'
Error Message FSPF-3-IPC_PROC_ERR: Error in processing IPC message : Opcode = [dec],

Error code = [hex]
Explanation FSPF had an error in processing message of [dec] opcode , the internal error code is
[dec].
Recommended Action Possibly some wrong IPC message is received by FSPF . Provide output of
'debug fspf mts pkt' and 'debug fspf error ' trace.
Error Message FSPF-3-LOCK_FAIL: FSPF failure in gaining lock
Explanation There is a software failure in gaining lock of the shared resource between FSPF threads.
Recommended Action Provide output of 'debug fspf all '
Error Message FSPF-3-MTS_MSG_BEFORE_GSYNC: FSPF in standby received MTS message

opcode = [hex] before GSYNC
Explanation FSPF in standby received an MTS message of opcode [dec] before receiving the
GSYNC message.
Recommended Action Provide output of 'debug fspf mts pkt '
Error Message FSPF-3-RIB_ERR: Error in RIB : [chars]
Explanation FSPF had an error in interacting with RIB, error description is [chars].
Recommended Action Check if rib application is running using 'show processes'. Provide output of
'debug fspf route' and RIB debug traces.
OL-26589-01 2-195
Error Message FSPF-3-ROUTE_COMPUTE_ERR: Error in computing or sending routes : Error

= [chars]
Explanation FSPF had an error in computing routes , error description is [chars].
Recommended Action Provide the error code and output of 'debug fspf error' and 'debug fspf route'
if problem is reproducible
Error Message FSPF-3-UNLOCK_FAIL: FSPF failure in releasing lock
Explanation There is a software failure in releasing lock of the shared resource between FSPF
threads.
Recommended Action Provide output of 'debug fspf all '
Error Message FSPF-3-VSAN_TIMER_ERR: Error in processing VSAN timer event [chars],

error description = [chars]
Explanation FSPF had an internal error in processing timer event , error description is [chars].
Recommended Action Provide output of 'debug fspf error'
FSPF-4
Error Message FSPF-4-FC2_DOWN_INTF: Received FC2 packet on DOWN interface [chars]
Explanation FSPF received a FC2 packet on inactive interface [chars] .
Recommended Action This message may be printed for the first FSPF packet when an interface is
brought up. If the message is seen continuously check if FSPF is disabled on one end for the
interface or the VSAN. Otherwise check 'show interface ' output to see if interface is physically up
only on one side. Also check if there is any error message printed for IPC_PROC_ERR
Error Message FSPF-4-FC2_DOWN_VSAN: Received FC2 packet on inactive vsan
Explanation FSPF received a FC2 packet on inactive vsan.
Recommended Action If message seen continuously check if FSPF is disabled on the VSAN
Investigate if VSAN is active and valid domain has been assigned on the switch Also check if
IPC_PROC_ERR message is printed in the syslog
2-196 OL-26589-01
Error Message FSPF-4-ILLEGAL_FSM_EVENT: Illegal FSM event for state [chars] in

interface [chars]
Explanation An illegal protocol event has occurred for the FSPF state machine. The old state was
[chars] for the interface [chars].
Recommended Action It is possible to get this message if some protocol packet gets dropped but the
it should recover and move back to FULL state. Do 'show fspf interface' to check the state of the
interface. If it is stuck in state other than FULL provide output of 'debug fspf event' and 'debug fspf
fc pkt ' for the interfaces involved.
Error Message FSPF-4-LSR_DROPPED: [chars], Dropping LSR [dec] received on interface

[chars]
Explanation A LSR packet is dropped due to [chars] reason. LSR belonged to domain [dec] and was
received on interface [chars].
Recommended Action Provide the reason given for dropping the LSR and output of 'debug fspf fc
pkt' If the reason is checksum failure investigate possible packet corruption or truncation
Error Message FSPF-4-LSR_MIN_LS_ARRIVAL: Packet arrived before MIN_LS_ARRIVAL,

Dropping LSR [dec] on interface [chars]
Explanation A LSR packet is dropped as it arrived before MIN_LS_ARRIVAL. LSR belonged to

domain [dec] and was received on interface [chars].
Recommended Action This can occur in transient situation and protocol recovers by retransmitting
the LSR. If the message is seen continuously provide output of 'debug fspf flood ' , 'debug fspf
retrans' and 'debug fspf error '. The message may be seen more often when interoperating with other
vendors
Error Message FSPF-4-LSU_RX_INIT: Dropping LSU received in state INIT on interface

[chars]
Explanation A LSU packet is dropped as interface [char] is in INIT state when it received the LSU.
Recommended Action This can occur in some transient situation. If the problem persists provide
output of 'show fspf vsan x interface' and 'debug fspf fc pkt ' and 'debug fspf event vsan x'
FSPF-5
Error Message FSPF-5-STARTING: Routing daemon started
Explanation FSPF routing daemon has been started.
OL-26589-01 2-197
FSPF-6
Error Message FSPF-6-ADD_LSR: New LSR added for domain [dec]
Explanation A new LSR is added to the database for domain [dec] .
Error Message FSPF-6-DELETE_LSR: LSR deleted for domain [dec]
Explanation The LSR for domain [dec] is deleted from the database.
Error Message FSPF-6-INTF_OPER_DOWN: Down on interface [chars]
Explanation FSPF has become operationally down on interface [chars].
Error Message FSPF-6-INTF_OPER_UP: Up on interface [chars]
Explanation FSPF has become operational on interface [chars].
Error Message FSPF-6-MAX_AGE: LSR [dec] reached Maxage
Explanation The LSR for domain [dec] reached the maximum age and will be deleted from all the
connected switches .
Error Message FSPF-6-ROLLOVER: Rolling over the incarnation number of Local LSR
Explanation The incarnation number of local LSR reached the maximum value and is rolling over.
Error Message FSPF-6-SELF_ORIGINATED: Received local LSR with higher incarnation

number
Explanation A LSR for the local domain was received with incarnation number higher than the one
in database. This situation should only occur initially on a topology change. If this situation persists
the domain assignment of switches may not be unique
Recommended Action If this message is received continuously check if domain assignment is unique
in the fabric.
2-198 OL-26589-01
Error Message FSPF-6-STATE_CREATED: Internal state created [chars]
Explanation FSPF has created its internal state stateless/stateful [chars].
Error Message FSPF-6-VSAN_OPER_DOWN: Down on vsan
Explanation FSPF has become operationally down on VSAN.
Error Message FSPF-6-VSAN_OPER_UP: Up with local domain [dec]
Explanation FSPF has started with local domain [dec].
FSPF-7
Error Message FSPF-7-ROUTE_THREAD_STARTED: Thread number [dec] started
Explanation Route computation thread number [dec] has been started for FSPF.
GLBP Messages
This section contains the GLBP messages.
GLBP-2
Error Message GLBP-2-GLBP_URIB_INIT_ERROR: [chars]
Explanation Unicast routing initialization failed and the GLBP process terminated
Recommended Action Please check syslog messages for URIB failures and rectify the problem
GLBP-3
Error Message GLBP-3-GLBP_ARP_ADD_FAILED: failed to add [chars]/[chars] in arp

table
Explanation The system was unable to add the GLBP vIP into the arp table
Recommended Action Please check syslog messages for ARP failures and rectify the problem
OL-26589-01 2-199
Error Message GLBP-3-GLBP_ARP_DEL_FAILED: failed to delete [chars]/[chars] in arp

table
Explanation The system was unable to delete the GLBP vIP from the arp table
Error Message GLBP-3-GLBP_FEATURE_MANAGER_ERROR: [chars]: [chars]
Explanation There was a problem in GLBP interaction with feature manager.
problem
Error Message GLBP-3-GLBP_IP_JOIN_GROUP_FAILED: [chars]: failed to join glbp

multicast address group
Explanation The system was unable to peform a join to start receiving GLBP protocol packets.
Recommended Action Please check syslog messages for IP failures and rectify the problem
Error Message GLBP-3-GLBP_IP_LEAVE_GROUP_FAILED: [chars]: failed to leave glbp

multicast address group
Explanation The system was unable to peform a leave to stop receiving GLBP protocol packets.
Recommended Action Please check syslog messages for IP failures and rectify the problem
Error Message GLBP-3-GLBP_MAC_ADD_FAILED: fwd [dec] failed to add [chars] in mac

table (error [hex])
Explanation The system was unable to add the GLBP mac address into the mac addresss table
Recommended Action Please check syslog messages for L2FM failures and rectify the problem
Error Message GLBP-3-GLBP_MAC_DEL_FAILED: fwd [dec] failed to delete [chars] in

mac table (error [hex])
Explanation The system was unable to delete the GLBP mac address from the mac addresss table
Recommended Action Please check syslog messages for L2FM failures and rectify the problem
Error Message GLBP-3-GLBP_ROUTE_ADD_FAILED: failed to add [chars] in routing table
Explanation The system was unable to add the GLBP vIP address into the unicast routing table
2-200 OL-26589-01
Error Message GLBP-3-GLBP_ROUTE_DEL_FAILED: failed to delete [chars] in routing

table
Explanation The system was unable to delete the GLBP vIP address from the unicast routing table
GLBP-4
Error Message GLBP-4-BADAUTH: Bad authentication received from [chars]
Explanation Two routers participating in a Gateway Load Balancing Protocol group have a valid
authentication string that does not match.
Recommended Action Use the glbp authentication interface command to repair the Gateway Load
Balancing Protocol authentication discrepancy between the local system and the one whose IP
address is reported
Error Message GLBP-4-BADVIP1: address [chars] is in the wrong subnet for this
interface
Explanation The Gateway Load Balancing Protocol virtual IP address is not within the subnet
configured on this interface.
Recommended Action Configure the virtual IP address of Gateway Load Balancing Protocol to be
within the subnet configured on this interface.
Error Message GLBP-4-BADVIP2: address [chars] in the wrong subnet for this
interface is not learned
Explanation The Gateway Load Balancing Protocol virtual IP address contained in the hello
message cannot be learned. It is not within the subnet configured on this interface.
Recommended Action Check the configuration on all Gateway Load Balancing Protocol routers.
Error Message GLBP-4-BADVIP3: address [chars] is the broadcast address for this
interface
Explanation The Gateway Load Balancing Protocol virtual IP address is a broadcast address for this
interface.
Recommended Action Configure the virtual IP address of Gateway Load Balancing Protocol to be a
non broadcast address.
OL-26589-01 2-201
Error Message GLBP-4-DIFFVIP1: active router virtual IP address [chars] is

different from the locally configured virtual IP address [chars]
Explanation The Gateway Load Balancing Protocol virtual IP address contained in the Hello
message from the Active router is different to that configured locally.
Recommended Action Check the configuration on all Gateway Load Balancing Protocol routers
Error Message GLBP-4-DUPADDR: Duplicate address on [chars]
Explanation The IP address in a Gateway Load Balancing Protocol message received on the
interface is the same as the IP address of its own router. This condition may be caused by a
misconfiguration or because of a malfunctioning switch.
Recommended Action Check the configurations on all the Gateway Load Balancing Protocol routers,
and ensure that any switches are functioning properly
Error Message GLBP-4-DUPVIP1: address [chars] already assigned to interface [chars]

grp [dec]
message cannot be learned. It is already assigned to a different Gateway Load Balancing Protocol
group.
Recommended Action Check the configuration on all Gateway Load Balancing Protocol routers
Error Message GLBP-4-DUPVIP2: address [chars] already assigned to this interface
message cannot be learned. It is already assigned to this interface.
Error Message GLBP-4-DUPVIP3: address [chars] already assigned to another interface

[chars]
message cannot be learned. It is already assigned to, or overlaps with, an address on another
interface or application.
Error Message GLBP-4-GLBP_ARP_RESP_FAILED: failed to send arp response

[chars]/[chars]
Explanation The system was unable to send the arp response for vIP
2-202 OL-26589-01
GLBP-5
Error Message GLBP-5-ACTIVE_CHANGE: Active gateway is [chars]
Explanation The Gateway Load Balancing Protocol has changed active gateway.
Recommended Action No action is required
Error Message GLBP-5-FWDSTATECHANGE: fwd [dec] state changed from [chars] to

[chars]
Explanation The Gateway Load Balancing Protocol forwarder has changed state.
Error Message GLBP-5-FWD_CREATE: fwd [dec] created
Explanation The Gateway Load Balancing Protocol forwarder has been created.
Error Message GLBP-5-FWD_DELETE: fwd [dec] deleted
Explanation The Gateway Load Balancing Protocol forwarder has been removed.
Error Message GLBP-5-FWD_OWNER: fwd [dec] owner mac is [chars]
Explanation The Gateway Load Balancing Protocol forwarder has changed the owner MAC address.
Error Message GLBP-5-FWD_VMAC: fwd [dec] virtual mac is [chars]
Explanation The Gateway Load Balancing Protocol forwarder has changed the virtual MAC
address.
Error Message GLBP-5-FWD_WEIGHTING: fwd [dec] weighting is [dec]
Explanation The Gateway Load Balancing Protocol forwarder has changed the weighting.
OL-26589-01 2-203
Error Message GLBP-5-GRPSTATECHANGE: state changed from [chars] to [chars]
Explanation The Gateway Load Balancing Protocol gateway has changed state.
Error Message GLBP-5-MEMBER_ADD: member [chars] [chars] added
Explanation The Gateway Load Balancing Protocol gateway has added a member.
Error Message GLBP-5-MEMBER_REMOVE: member [chars] [chars] removed
Explanation The Gateway Load Balancing Protocol gateway has removed a member.
Error Message GLBP-5-PRIORITY: [chars] gateway priority changed to [dec]
Explanation The Gateway Load Balancing Protocol gateway has changed priority.
Error Message GLBP-5-STANDBY_CHANGE: Standby gateway is [chars]
Explanation The Gateway Load Balancing Protocol has changed standby gateway.
Error Message GLBP-5-TIMER: [chars] timer changed to [chars]
Explanation The Gateway Load Balancing Protocol gateway has learnt timers.
Error Message GLBP-5-VIPLEARN: learnt virtual ip address [chars]
Explanation The Gateway Load Balancing Protocol gateway has learnt virtual IP address.
Error Message GLBP-5-VIPUNLEARN: unlearnt virtual ip address [chars]
Explanation The Gateway Load Balancing Protocol gateway has unlearnt virtual IP address.
2-204 OL-26589-01
Error Message GLBP-5-WEIGHTING: weighting changed to [dec]
Explanation The Gateway Load Balancing Protocol gateway has changed the weighting.
HSRP_ENGINE Messages
This section contains the HSRP_ENGINE messages.
HSRP_ENGINE-3
Error Message HSRP_ENGINE-3-BFD_GLOBAL_SESSION_REMOVAL_ERROR: Failed to remove all

the HSRP-BFD sessions([hex] [hex]), Refer logs
Explanation Refer logs for more details
Error Message HSRP_ENGINE-3-BFD_IF_SESSION_REMOVAL_ERROR: Failed to remove few

HSRP-BFD sessions([hex] [hex]), Refer logs
Explanation Refer logs for more details.
Error Message HSRP_ENGINE-3-BFD_SESSION_ADD_ERROR: Failed to add few HSRP-BFD

sessions([hex] [hex]), Refer logs
Explanation TRefer logs for more details.
Error Message HSRP_ENGINE-3-BFD_SESSION_CREATION_ERROR: Failed to create BFD

session information([hex] [hex]), Refer logs
Error Message HSRP_ENGINE-3-BFD_SESSION_REMOVAL_ERROR: Failed to remove few

HSRP-BFD sessions([hex] [hex]), Refer logs
OL-26589-01 2-205
Error Message HSRP_ENGINE-3-ERROR_IN_ADD_VIP_TO_U6RIB: Failed to Add VIP [chars]

to U6RIB (errno [hex]), Refer logs
Error Message HSRP_ENGINE-3-ERROR_IN_DEL_VIP_FROM_U6RIB: Failed to delete VIP

[chars] from U6RIB (errno [hex]), Refer logs
Error Message HSRP_ENGINE-3-NOSOCKET: Unable to open socket
Explanation The system was unable to initialize an IP connection for the Hot Standby protocol.
Recommended Action Make sure that there is at least one interface configured to run IP.
HSRP_ENGINE-4
Error Message HSRP_ENGINE-4-BADAUTH2: Bad authentication from [chars]
Explanation Two routers participating in HSRP disagree on the valid authentication string.
Recommended Action Use the HSRP authentication command to repair the HSRP authentication
discrepancy between the local system and the one whose IP address is reported.
Error Message HSRP_ENGINE-4-BADAUTH: Bad authentication from [chars], group [dec],

remote state [chars]
Explanation Two routers participating in HSRP disagree on the valid authentication string.
Recommended Action Use the HSRP authentication command to repair the HSRP authentication
discrepancy between the local system and the one whose IP address is reported.
Error Message HSRP_ENGINE-4-DIFFVIP1: [chars] Grp [dec] active routers virtual IP

address [chars] is different to the locally configured address [chars]
Explanation The HSRP virtual IP address contained in the Hello message from the Active router is
different to that configured locally.
Recommended Action Check the configuration on all HSRP routers.
2-206 OL-26589-01
Error Message HSRP_ENGINE-4-DUPADDR: Duplicate address %i on [chars], sourced by %e
Explanation The IP address in an HSRP message received on the interface is the same as the
routersownIPaddress.Thismaybebecauseofmisconfiugration,orbecauseofamalfunctioningswitch'
Recommended Action Check the configurations on all the HSRP routers, and make sure that any
switches you have are functioning properly.
Error Message HSRP_ENGINE-4-DUPVIP1: [chars] Grp [dec] address [chars] is already

assigned to a HSRP group on this interface
Explanation The HSRP virtual IP address contained in the Hello message cannot be learnt as it is
already assigned to a different HSRP group.

assigned on this interface
already assigned to this interface.

assigned to, or overlaps with, an address on another interface or application
already assigned to, or overlaps with, an address on another interface or application.
HSRP_ENGINE-5
Error Message HSRP_ENGINE-5-ACTIVEROUTERPRIORITY: Interface [chars] [chars] Grp

[dec] Active router priority changed to [dec]
Explanation The priority of the Active router for the group has changed.
Error Message HSRP_ENGINE-5-ACTIVE_CHANGE: Interface [chars] [chars] Grp [dec]

Active router is [chars]
Explanation The Active router for the group has changed.
OL-26589-01 2-207
Error Message HSRP_ENGINE-5-AUTOCONFIG_VIPLEARN: Interface [chars] grp [dec]

learnt autoconfig virtual ip address [chars]
Explanation The local router has generate virtual ip address
Error Message HSRP_ENGINE-5-GRPSTATECHANGE: Interface [chars] [chars] Grp [dec]

state changed from [chars] to [chars] reason [chars]
Explanation The HSRP router has changed state
Error Message HSRP_ENGINE-5-MACADDRESS_CHANGE: Interface [chars] [chars] Grp [dec]

mac-address changed to [chars]
Explanation The mac address of the group has changed.
Error Message HSRP_ENGINE-5-PRIORITY: Interface [chars] [chars] Grp [dec] priority

changed to [dec]
Explanation The current priority of the HSRP group has changed.
Error Message HSRP_ENGINE-5-STANDBYROUTERPRIORITYCHANGE: Interface [chars] [chars]

Grp [dec] Standby router priority changed to [dec]
Explanation The priority of the Standby router for the group has changed.
Error Message HSRP_ENGINE-5-STANDBY_CHANGE: Interface [chars] [chars] Grp [dec]

Standby router is [chars]
Explanation The Standby router for the group has changed.
Error Message HSRP_ENGINE-5-TIMER: Interface [chars] [chars] Grp [dec] [chars]

timer changed to [dec] [chars]
Explanation The hello/hold timer value for the HSRP group has changed
2-208 OL-26589-01
Error Message HSRP_ENGINE-5-VIPLEARN: Interface [chars] [chars] Grp [dec] learnt

virtual ip address [chars]
Explanation The local router has learnt virtual ip address from the incoming HSRP packet.
HSRP_ENGINE-6
Error Message HSRP_ENGINE-6-STATECHANGE2: [chars] [chars] Grp [dec] state moving

from [chars]
Explanation The router has changed state
Error Message HSRP_ENGINE-6-STATECHANGE: [chars] [chars] Grp [dec] state move to

[chars]
Explanation The router has changed state
IKE Messages
This section contains the IKE messages.
IKE-3
Error Message IKE-3-CRYPTO_INIT_ERROR: IKEv2 crypto init error: [chars]
Explanation Crypto initialization error
Error Message IKE-3-ENABLE_ERROR: Unable to store enable flag in configuration

(error-id [hex]).
Explanation Service failed to store the enable flag in configuration. As a result, it will exit
Error Message IKE-3-FIPS_MODE_ERROR: Could not set FIPS mode
Explanation The FIPS mode could not be set by IKE
OL-26589-01 2-209
Error Message IKE-3-IKE_PROGRAM_EXIT: [chars]
Explanation IKE process did an abnormal exit
Error Message IKE-3-MAX_HALF_CONN_LIMIT_REACHED: IKEv1 : Exceeded the limit for

number of half open Phase 1 connections
Explanation The number of half open connections has exceeded the maximum limit
Error Message IKE-3-PHASE1_NEGOTIATION_FAILED: IKEv1: Phase 1 negotiation failed

for peer [chars]
Explanation IKE policy negotiation failed for peer [chars].
Error Message IKE-3-PHASE1_PROPOSAL_MISMATCH: IKEv1: No matching phase 1 proposal

found for peer [chars]
Explanation There is a IKE policy mismatch for the peer.
Error Message IKE-3-PHASE2_NEGOTIATION_FAILED: IKEv1: Phase 2 negotiation failed

for peer [chars]
Explanation IPsec policy negotiation failed for peer [chars].
Error Message IKE-3-PHASE2_PROPOSAL_MISMATCH: IKEv1: No matching phase 2 proposal

found for peer [chars]
Explanation There is a IPsec policy mismatch for the peer.
Error Message IKE-3-UNSUPPORTED_EXCHANGE: IKEv1: Unsupported exchange [dec]

received from [chars]
Explanation A unsupported IKE exchange type [digits] was received from [chars]
2-210 OL-26589-01
IKE-4
Error Message IKE-4-INVALID_PAYLOAD_APPEAR: IKEv2 received message (from [chars])

with payload ([chars]) appeared in [chars]([chars])
Explanation Received a payload in an inappropriate exchange
Error Message IKE-4-MESSAGE_ERROR: IKEv2 message (from [chars]) message error:

[chars]
Explanation Received a malformed message which doesntadheretotheprotocol'
Error Message IKE-4-PARSING_ERROR: IKEv2 message (from [chars]) parsing error:

[chars]
Explanation Received a malformed message which can not be parsed appropriately
Error Message IKE-4-UNKNOWN_PAYLOAD: IKEv2 received message (from [chars]) with

un-recognized payload ([chars])
Explanation Received an invalid payload
Error Message IKE-4-UNSUPPORT: [chars] is not supported (message from [chars])
Explanation Received something unsupported
IKE-6
Error Message IKE-6-POLL_START_DONE: IKE is exiting since it is not enabled
Explanation IKE is exiting since it is not enabled in the configuration
ILC-SPAN Messages
This section contains the ILC-SPAN messages.
OL-26589-01 2-211
ILC-SPAN-3
Error Message ILC-SPAN-3-ERROR: [chars]
Explanation Ilc_span_mgr encountered an error
ILC_HELPER Messages
This section contains the ILC-HELPER messages.
ILC_HELPER-2
Error Message ILC_HELPER-2-NO_LICENSE_REBOOT: Linecard [dec] will reboot now.
Explanation SSE License has expired, hence the linecard will be rebooted.
Recommended Action Install appropriate SSE license to be able to use SSM features normally
ILC_HELPER-3
Error Message ILC_HELPER-3-INVALID_SSI: [chars]
Explanation The ssi boot variable is configured to an invalid image. So, the linecard will be bought
online in basic mode instead of advanced SSI mode
Recommended Action Configure a proper image for the ssi boot variable
ILC_HELPER-6
Error Message ILC_HELPER-6-LICENSE_VALID: A valid license for linecard [dec] has

been obtained
Explanation A valid license has been obtained for the SSM
Error Message ILC_HELPER-6-UPGRADE_DELAY: The SSI upgrade on slot [dec] is delayed

by [dec] secs.
Explanation The SSI upgrade is delayed due to the configured ssm upgrade delay command
2-212 OL-26589-01
IMAGE_DNLD Messages
This section contains the IMAGE_DNLD messages.
IMAGE_DNLD-SLOT#-2
Error Message IMAGE_DNLD-SLOT#-2-ADDON_IMG_DNLD_FAILED: Module image download

process failed. [chars]
Explanation Addon image download to module failed. This module is not operational until an addon
image has been successfully installed.
Recommended Action Verify the location and version of your module image. Use the install module
cli command to download a new module image.
Error Message IMAGE_DNLD-SLOT#-2-IMG_DNLD_COMPLETE: Module image download process.

[chars]
Explanation Image download completed. Module image is being installed.
Error Message IMAGE_DNLD-SLOT#-2-IMG_DNLD_FAILED: Module image download process.

[chars]
Explanation Image download failed. Module may be inoperable.
Recommended Action Use show module cli command to verify the state of this module. Retry image
download with install module cli command.
Error Message IMAGE_DNLD-SLOT#-2-IMG_DNLD_FILE_SYSTEM_CHECK_ERROR: File System

check failed: [chars]
Explanation File system consistency check failed
Recommended Action File-system repair is needed using fsck
Error Message IMAGE_DNLD-SLOT#-2-IMG_DNLD_STARTED: Module image download process.

[chars]
Explanation Image download started. Module image downloads are non-disruptive to module
operation.
OL-26589-01 2-213
IMAGE_DNLD-SLOT#-4
Error Message IMAGE_DNLD-SLOT#-4-IMG_DNLD_FILE_SYSTEM_RECREATION: [chars].

Partition was erased and successfully recreated.
Explanation File system checking and recreation if necessary for /images.
IMAGE_DNLD-SLOT#-5
Error Message IMAGE_DNLD-SLOT#-5-ADDON_IMG_DNLD_COMPLETE: Addon module image

download process completed. [chars]
Explanation Addon image download to module has completed.The module should now be installing
this new image.
Recommended Action This message is informational only.
Error Message IMAGE_DNLD-SLOT#-5-ADDON_IMG_DNLD_STARTED: Addon module image

download process started. [chars]
Explanation Addon image download to module has started. This is a disruptive download and this
module will be inoperable until this download process is complete.
Recommended Action This message is informational only.
Error Message IMAGE_DNLD-SLOT#-5-ADDON_IMG_DNLD_SUCCESSFUL: Addon module image

download and install process successful. [chars]
Explanation Addon image download and install to module is successful.
Recommended Action Use the show module cli command to verify the modulesoperationalstatus.'
IMAGE_UPGRADE Messages
This section contains the IMAGE_UPGRADE messages.
IMAGE_UPGRADE-SLOT#-2
Error Message IMAGE_UPGRADE-SLOT#-2-IMAGE_UPGRADE_ERROR: [chars]
Explanation Image Upgrade Error
2-214 OL-26589-01
IMAGE_UPGRADE-SLOT#-4
Error Message IMAGE_UPGRADE-SLOT#-4-IMAGE_UPGRADE_INFO: [chars]
Explanation Image Upgrade Info
IM Messages
This section contains the IM messages.
IM-3
Error Message IM-3-IM_IF_FEATURE_BIND_FAILURE: Interface feature bind failed

[chars]
Explanation Interface feature bind failed, so applications in that feature set may not behave
correctly.
Error Message IM-3-IM_LC_OFFLINE_ERROR: LC Offline could not be sent to vdc:[dec]
Explanation LC Offline was not relayed to some vdc, so applications may not behave correctly.
Error Message IM-3-IM_RESP_ERROR: Component [chars] opcode:[chars] in vdc:[dec]

returned error:[chars]
Explanation Some component returned an error.
Error Message IM-3-IM_SEQ_ERROR: Error ([chars]) while communicating with

component [chars] opcode:[chars] (for:[chars])
OL-26589-01 2-215
IM-5
Error Message IM-5-IM_DEMUX_ERROR: [chars]
Explanation Demux function returned error
Error Message IM-5-IM_INTERNAL_ERROR: [chars]
Explanation Internal error occurred
Error Message IM-5-IM_INTF_STATE: [chars] [chars] in vdc [dec]
Explanation Management interface state changed.
Error Message IM-5-IM_UNKNOWN_INTERFACE: [chars]
Explanation Interface is not supported or not found
INTERFACE_VLAN Messages
This section contains the INTERFACE_VLAN messages.
INTERFACE_VLAN-4
Error Message INTERFACE_VLAN-4-SVI_IF_CONFIG_DELETED_NOTIF_DELAYED_DROPPED:

Interface VLAN Delete Notification Not Processed on Time by SAP [dec] ([chars])
Explanation This SAP took long time in processing Interface VLAN delete notification and caused
timeout
Error Message INTERFACE_VLAN-4-SVI_IF_CONFIG_REMOVED_NOTIF_DELAYED_DROPPED:

Interface VLAN Remove Notification Not Processed on Time by SAP [dec] ([chars])
Explanation This SAP took long time in processing Interface VLAN remove notification and caused
timeout
2-216 OL-26589-01
Error Message INTERFACE_VLAN-4-SVI_VLAN_DOES_NOT_EXIST: Vlan [dec] does not exist
Explanation Vlan not created before assignment
Recommended Action Interface-vlan
Error Message INTERFACE_VLAN-4-SVI_WARN_SVI_UP_IN_NON_ROUTABLE_VDC: Interface

VLAN [dec] is being kept up in non-routable VDC. Reason: management configuration
enabled. Please disable all the routing protocols
Explanation Keeping Interface VLAN up in non-routable VDC may cause potenital traffic blackhole
INTERFACE_VLAN-5
Error Message INTERFACE_VLAN-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is

down(Administratively Down)
Explanation Interface has been configured to be administratively down
Error Message INTERFACE_VLAN-5-IF_DOWN_ERROR_DISABLED: Interface [chars] is down.

Reason [dec]
Explanation The interface encountered an error while configuring it
Error Message INTERFACE_VLAN-5-IF_DOWN_INACTIVE: Interface [chars] is down

(Inactive)
Explanation Interface VLAN has been suspended or deleted
Error Message INTERFACE_VLAN-5-SVI_DISABLED: SVI Disabled
Explanation SVI Service Disabled
Error Message INTERFACE_VLAN-5-SVI_ENABLED: SVI Enabled
Explanation SVI Service Enabled
OL-26589-01 2-217
Error Message INTERFACE_VLAN-5-SVI_GET_MAC_FAILED: Failed to acquire MAC address

for SVI [hex]
Explanation SVI failed to acquire MAC address
Error Message INTERFACE_VLAN-5-SVI_INIT: SVI intialization failed with error [hex]
Explanation SVI initialziation error
Error Message INTERFACE_VLAN-5-SVI_IOD_RELEASE_ERROR_RESPONSE: IM failed to

release SVI IOD error [hex]
Explanation IM failed to release SVI IOD
Error Message INTERFACE_VLAN-5-SVI_MTS_SEND_FAILURE: MTS send failure for opcode

[dec], error [hex]
Explanation SVI encountered an error in with MTS message
Error Message INTERFACE_VLAN-5-SVI_MTS_TIME_OUT: MTS send timed out
Explanation SVI did not recieve response for mts message
Error Message INTERFACE_VLAN-5-SVI_RSRVD_VLAN_FAILED: Failed to get list of

reserved vlans [hex]
Explanation SVI failed to get the list reserved vlans
Error Message INTERFACE_VLAN-5-SVI_SDB_UPDATE_FAILED: sdb update failed with

ret_val [dec]
Explanation SDB updated failed for SVI
2-218 OL-26589-01
Error Message INTERFACE_VLAN-5-SVI_SEC_VLAN_FAILED: Failed to get list of

secondary vlans [hex]
Explanation SVI failed to get the list of secondary vlans
Error Message INTERFACE_VLAN-5-UPDOWN: Line Protocol on Interface [chars], changed

state to [chars]
Explanation Line protocol status changed for an interface
IOA_LC Messages
This section contains the IOA_LC messages.
IOA_LC-5
Error Message IOA_LC-5-IOA_DISABLED: IOA Disabled
Explanation IOA Service Disabled
Error Message IOA_LC-5-IOA_ENABLED: IOA Enabled
Explanation IOA Service nabled
IPACL Messages
This section contains the IPACL messages.
IPACL-0
Error Message IPACL-0-EMERG: [chars]
Explanation Ipacl caused a system failure
OL-26589-01 2-219
IPACL-1
Error Message IPACL-1-ALERT: [chars]
Explanation Ipacl caused failures in other services
IPACL-2
Error Message IPACL-2-CRIT: [chars]
Explanation Ipacl encountered a catastrophic error
IPACL-3
Error Message IPACL-3-ERR: [chars]
Explanation Ipacl encountered an error
IPACL-4
Error Message IPACL-4-WARN: [chars]
Explanation Ipacl ignored the unexpected condition
Recommended Action Please perform

debugipaclall',thenrecreatetheoperationscenario,tofindoutmoredetails.'
IPACL-5
Error Message IPACL-5-NOTE: [chars]
Explanation Ipacl does not support this operation

debugipaclall',thenrecreatetheoperationscenario,tofindoutmoredetails.'
2-220 OL-26589-01
IPACL-6
Error Message IPACL-6-INFO: [chars]
Explanation Ipacl event occurred
IPFC Messages
This section contains the IPFC messages.
IPFC-2
Error Message IPFC-2-ALLOC_MEMORY: Memory allocation failed
Explanation The service failed to allocate a block of dynamic memory.
IPFC-3
Error Message IPFC-3-INIT_FAILED: Initialization failed. Component [chars]
Explanation The service failed to start. The failure occurred while initializing the component
[chars].
Recommended Action Show processes to check the status of the other processes, debug the specified
component.
Error Message IPFC-3-IOCTL_FAILED: IOCTL failed
Explanation An IOCTL to the character device failed.
Recommended Action Show IPFC internal interface VSAN <number
Error Message IPFC-3-PSSERROR: [chars]
Explanation IPFC manager encountered a PSS error.
OL-26589-01 2-221
IPFC-5
Error Message IPFC-5-CONFIG_EVENT: VSAN interface [dec] [chars]
Explanation The specified VSAN Interface has been successfully [chars].
Error Message IPFC-5-STATE_CHANGE: VSAN interface [dec] [chars]
Explanation The specified VSAN Interface is [chars].
IPFC-6
Error Message IPFC-6-STARTING: IP Over Fiber Channel service started
IPQOSMGR Messages
This section contains the IPQOSMGR messages.
IPQOSMGR-2
Error Message IPQOSMGR-2-QOSMGR_DCBXP_PFC_CMP_FAIL_MSG: [chars] - qos config

[chars] not compatible with the peer
Explanation Port_id [chars] has qos config [chars] which is incompatible with the peer.
Error Message IPQOSMGR-2-QOSMGR_HA_FAILURE: Failed to do high availability

operation: [chars].
2-222 OL-26589-01
Error Message IPQOSMGR-2-QOSMGR_INIT_FAILED: Initialization failed for QoS

Manager: [chars], reason: [hex].
Explanation Initialization failed for QoS Manager due to [chars], reason: [hex].
Error Message IPQOSMGR-2-QOSMGR_MTS_FAILURE: Failed to do MTS operation: [chars].
Error Message IPQOSMGR-2-QOSMGR_MTS_REGISTRATION_FAILED: MTS options setting to

[hex] failed for opCode: [dec].
Error Message IPQOSMGR-2-QOSMGR_NETWORK_QOS_POLICY_CHANGE: Policy [chars] is now

active
Explanation [chars] is the new active network-qos policy
Error Message IPQOSMGR-2-QOSMGR_PSS_FAILURE: Failed to do PSS operation: [chars],

reason: [hex].
Error Message IPQOSMGR-2-QOSMGR_PSS_VER_FAIL: PSS file [chars] has version

IPQOSMGR-3
Error Message IPQOSMGR-3-QOSMGR_CONFIG_ERROR: Configuration error: [chars].
Explanation Configuration error. [chars] is the reason.
OL-26589-01 2-223
Error Message IPQOSMGR-3-QOSMGR_NVDC_PFF_ERROR: PPF verify/commit failed in vdc

[dec] error: [hex] for global qos command
Explanation For global qos command, PPF verify/commit failed in vdc [dec] with reason [hex].
Error Message IPQOSMGR-3-QOSMGR_PPF_ERROR: PPF library error: [chars].
Explanation PPF library errors. [chars] is the reason.
IPQOSMGR-4
Error Message IPQOSMGR-4-QOSMGR_LC_ERROR_MSG: Linecard [dec] returned an error:

[chars]
Explanation Linecard [dec] returned an error message which is reported as [chars].
Error Message IPQOSMGR-4-QOSMGR_POLICIES_PRESENT_ON_DELETED_VLANS: Some VLANs (id:

[chars]) which are getting deleted now are still having qos service-policy
attached. These policies will be effective only when the VLANs get created again.
Explanation VLAN(s) [chars] is(are) getting deleted now. This is an informationsl message to notify
that qos service-policies are present when the vlan is deleted. If the service-policies are not needed,
please detach them from the vlans
Error Message IPQOSMGR-4-QOSMGR_PPF_WARNING: PPF library warning: [chars].
Explanation PPF library warning. [chars] is the reason.
Error Message IPQOSMGR-4-QOSMGR_WARNING_MSG: [chars] [dec]
Explanation QOSMGR warning messages is reported as [chars] [dec].
2-224 OL-26589-01
IPQOSMGR-6
Error Message IPQOSMGR-6-QOSMGR_DCBXP_CMP_FAIL_MSG: [chars] - qos config [chars] not

compatible with the peer
Explanation Dcbxp warning: Port_id [chars] has qos config [chars] which is incompatible with the
peer.
Error Message IPQOSMGR-6-QOSMGR_STATUS: QOSMGR Status: [chars].
Explanation QOSMGR status is reported as [chars].
IPSEC Messages
This section contains the IPSEC messages.
IPSEC-2
Error Message IPSEC-2-IPSEC_INIT: IPSec initialization of [chars] [chars]
Explanation IPSec initialization failed
Error Message IPSEC-2-IPSEC_SPD_OVERFLOW_DUE_TO_ACL: SPD Overflow on interface due

to IP ACL [chars] bound to crypto map [chars] [dec]
Explanation Modifying IP ACL caused Security Policy Database on the interface to overflow, IP
ACL filter not applied to security policy database
Recommended Action Undo IP ACL change
IPSEC-3
Error Message IPSEC-3-14_2_MODULE_PACKETS_DROPPED: [chars]: packets were dropped

in the module
Explanation Packets dropped in the 14/2 module. Please collect drop statistics using show ipsec
internal crypto-acc interface gigabit <slot/port
OL-26589-01 2-225
Error Message IPSEC-3-IPSEC_FIPS_TEST_FAILED: IPSEC FIPS compliance test failed
Explanation IPSEC FIPS compliance test failed
Error Message IPSEC-3-IPSEC_MSG_SEND_FAILURE: failed to send [chars] to sap [dec]:

[chars]
IPSEC-5
Error Message IPSEC-5-IPSEC_CMS_IF_ACL_UPDATED: IP ACL [chars] updated while

Crypto map [chars] [dec] bound to interface(s)
Explanation IP ACL updated while it is mapped to a crypto map that is bound to interface(s)
Error Message IPSEC-5-IPSEC_DISABLED_LIC_EXPIRED: IPSec Disabled due to License

Expiry
Explanation IPSec Disabled due to License Expiry
Error Message IPSEC-5-IPSEC_DISABLED: IPSec Disabled
Explanation IPSec Disabled
Error Message IPSEC-5-IPSEC_ENABLED: IPSec Enabled
Explanation IPSec Enabled
Error Message IPSEC-5-IPSEC_SA_CREATED: [chars]: IPSec SA created: local_ip:

[chars], peer_ip: [chars], [chars] SPI: [dec] ([hex])
Explanation IPSec SA created
2-226 OL-26589-01
Error Message IPSEC-5-IPSEC_SA_DELETED: [chars]: IPSec SA deleted: local_ip:

[chars], peer_ip: [chars], [chars] SPI: [dec] ([hex]), reason: [chars]
Explanation IPSec SA deleted
Error Message IPSEC-5-IPSEC_SA_REKEYED: [chars]: IPSec SA rekeyed: local_ip:

[chars], peer_ip: [chars], [chars] SPI: [dec] ([hex])
Explanation IPSec SA rekeyed
Error Message IPSEC-5-IPSEC_TUNNEL_CREATED: [chars]: IPSec tunnel created:

local_ip: [chars], peer_ip: [chars], id: [dec], protocol: [chars], traffic::
local: [chars]/[chars], port: [chars], remote: [chars]/[chars], ports: [chars]
Explanation IPSec tunnel created
Error Message IPSEC-5-IPSEC_TUNNEL_DELETED: [chars]: IPSec tunnel deleted:

local_ip: [chars], peer_ip: [chars], id: [dec], protocol: [chars], traffic::
local: [chars]/[chars], ports: [chars] remote: [chars]/[chars], ports: [chars]
Explanation IPSec tunnel deleted
Error Message IPSEC-5-IPSEC_TUNNEL_REKEYED: [chars]: IPSec tunnel rekeyed:

local_ip: [chars], peer_ip: [chars], id: [dec], protocol: [chars] traffic:: local:
[chars]/[chars], ports: [chars] remote: [chars]/[chars], ports: [chars]
Explanation IPSec tunnel rekeyed
IPS_SB_MGR Messages
This section contains the IP_SB_MGR messages.
OL-26589-01 2-227
IPS_SB_MGR-SLOT#-2
Error Message IPS_SB_MGR-SLOT#-2-NODE_CORE_NOT_RESPONDING: [Node [dec], Core

[dec]]: Not responding to heartbeats, state=[hex]
Explanation Node is not incrementing heartbeats periodically
Recommended Action Potential node software issue. Please contact your support representative
Error Message IPS_SB_MGR-SLOT#-2-NODE_NOT_RESPONDING: [Node [dec], Core [dec]] :

Not responding to heartbeats
Explanation Node manager is not receiving heartbeat responses from the node
Error Message IPS_SB_MGR-SLOT#-2-NODE_REIMAGE_PREPARE_FAIL: [Node [dec]]: Disk

formatting failed during node install
Explanation There was a problem during the partitioning of disk and creation of file systems during
node install.
Error Message IPS_SB_MGR-SLOT#-2-PORT_SOFTWARE_FAILURE: Port software failure,

module [dec] port [dec]
Explanation The software servicing the data path on the port has failed
IPS_SB_MGR-SLOT#-3
Error Message IPS_SB_MGR-SLOT#-3-COMP_FAILURE: Heartbeat failure in compression

engine (error [hex])
Explanation The compression engine did not respond to heartbeats, due to some failure. SAN-OS
will restart the compression engine to clear the problem.
Error Message IPS_SB_MGR-SLOT#-3-CRYPTO_FAILURE: Heartbeat failure in encryption

engine (error [hex])
Explanation The encryption engine did not respond to heartbeats, due to some failure. SAN-OS will
restart the encryption engine to clear the problem.
2-228 OL-26589-01
Error Message IPS_SB_MGR-SLOT#-3-FIPS_SELF_TEST_FAILURE: [chars] Restarting the

octeon...
Explanation FIPS self test failed for the algorithm. Restarting the octeon.
IPS_SB_MGR-SLOT#-4
Error Message IPS_SB_MGR-SLOT#-4-NODE_NOT_COMPAT_WITH_ADD_ON: svc-node[dec] image

is not compatible with svclc image
Explanation The svc image on the node is not compatible with the add on image running on the
linecard.
Recommended Action Please contact your support representative
Error Message IPS_SB_MGR-SLOT#-4-NODE_NOT_COMPAT_WITH_CURRENT: svc-node[dec]

image is not compatible with current node image
Explanation The new svc image is not compatible with the svc image currently running on the node
Error Message IPS_SB_MGR-SLOT#-4-NODE_NOT_COMPAT_WITH_SUP: svc-node[dec] image is

not compatible with system image
Explanation The svc image on the node is not compatible with the supervisor image.
IPS_SB_MGR-SLOT#-6
Error Message IPS_SB_MGR-SLOT#-6-SBMGR_EVENT: Sbmgr event: [chars]
Explanation This is an event log of sb_mgr relating to a port/node
IPS Messages
This section contains the IPS messages.
OL-26589-01 2-229
IPS-2
Error Message IPS-2-ISCSI_IPS_INIT: IPS initialization of [chars] [chars]
Explanation IPS initialization failed
IPS-3
Error Message IPS-3-DUP_IPV4_ADDR_DETECTED: duplicate IP address ([chars]) sent from

link address ([chars])
Explanation Duplicate IPv4 address is configured in the network
Error Message IPS-3-FCIP_FTA_ACCEL_CHAIN_ABORTED: Exch Aborted FC oxid [hex] My oxid

[hex] State [chars] Event [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI:
[hex] DA [hex] VSAN: [dec] (Internal [hex]:[hex])
Explanation FTA Exch being aborted
Recommended Action Informational no action required
Error Message IPS-3-FCIP_FTA_DATA_SENSE: Sense data with ERA [hex] sent to CH FCID:
[hex] CHI: [hex] from FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation Sense data with ERA sent
Recommended Action SYSLOGDOC_CONTACT_TAC
Error Message IPS-3-FCIP_FTA_ERA_35: ERA 0x35 presented to CH FCID: [hex] CHI: [hex]
from FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FCIP got an ERA 35
Error Message IPS-3-FCIP_FTA_ERA_38: ERA 0x38 received CH FCID: [hex] CHI: [hex] from
FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] at tape capacity: [dec] MB
Explanation FCIP got an ERA 38
2-230 OL-26589-01
Error Message IPS-3-FCIP_FTA_LOCATE_RBID_MISMATCH: Permanent Error due to Locate

RBID Mismatch, CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN:
[dec]
Explanation FCIP-FTA got a Permanent Error
Error Message IPS-3-FCIP_FTA_PERM_ERR: Permanent Error, ERA [hex] rcvd CH FCID:

[hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] sense_byte[2,6]:
[[hex], [hex]]
Explanation FCIP-FTA got a Permanent Error
Error Message IPS-3-FCIP_FTA_RETRY_ERROR: [chars] retries [dec] FC oxid [hex] My

oxid [hex] State [chars] Event [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex]
CUI: [hex] DA [hex] VSAN: [dec]
Explanation FTA Command timed out
Error Message IPS-3-FCIP_LINK_STAT_LOSS_OF_SYNC: [chars]: Loss of Sync ([chars])
Explanation FCIP Link Failed with Loss of Sync.
Error Message IPS-3-IPS_CRYPTO_FIPS_FAILED: IPS module [dec] has failed FIPS tests.
FIPS info - [chars]
Explanation FIPS error occurred in the IPS module.
Error Message IPS-3-IPS_EGRESS_PERR: Parity error on dma-bridge egress. Count:

[dec]
Explanation Parity error occured in dma-bridge egress direction.
OL-26589-01 2-231
Error Message IPS-3-IPS_FIPS_MODE_ERROR: IPS FIPS error: [chars]
Explanation IPS module FIPS mode error
Error Message IPS-3-IPS_FIPS_TEST_FAILED: IPS FIPS compliance test failed
Explanation IPS FIPS compliance test failed
Error Message IPS-3-IPS_INGRESS_PERR: Parity error on dma-bridge ingress. Count:

[dec]
Explanation Parity error occured in dma-bridge ingress direction.
Error Message IPS-3-ISLB_CFS_CLEAR_FAILED: [chars]
Explanation An error occurred while clearing the CFS lock. The reason for the failure : [chars]
Error Message IPS-3-ISLB_CFS_COMMIT_FAILED: [chars]; [chars]
Explanation An error occurred while commiting the cfs config data. The reason for the failure :
[chars]
Error Message IPS-3-ISLB_CFS_CONFIG_FAILED: [chars]; [chars]
Explanation An error occurred while distributing the CFS config data. The reason for the failure :
[chars]
Error Message IPS-3-ISLB_CFS_LOCK_FAILED: [chars]
Explanation An error occurred while acquiring the CFS lock. The reason for the failure : [chars]
2-232 OL-26589-01
Error Message IPS-3-ISLB_CFS_MERGE_ACTIVATION_FAILED: [chars]; [chars]
Explanation An error occurred while activating merged configuration. The reason for the failure :
[chars]
Error Message IPS-3-ISLB_CFS_MERGE_CLEARED: [chars]
Explanation Merge cleared, reason: [chars]
Error Message IPS-3-ISLB_CFS_MERGE_COMMIT_FAILED: [chars]; [chars]
Explanation An error occurred while commiting the cfs merge config data. The reason for the failure
: [chars]
Error Message IPS-3-ISLB_CFS_MERGE_CONFIG_FAILED: [chars]; [chars]
Explanation An error occurred while distributing the CFS merge config data. The reason for the
failure : [chars]
Error Message IPS-3-ISLB_CFS_MERGE_FAILED: [chars]; [chars]
Explanation An error occurred while merging the iSLB CFS fabrics. The reason for the failure :
[chars]
Error Message IPS-3-ISLB_CFS_MERGE_PRECOMMIT_FAILED: [chars]; [chars]
Explanation An error occurred while precommiting merge data. The reason for the failure : [chars]
OL-26589-01 2-233
Error Message IPS-3-ISLB_CFS_MERGE_REQ_REJECTED: [chars]
Explanation Merge requested rejected, reason: [chars]
Error Message IPS-3-ISLB_CFS_MERGING_CONFIG_DB_FAILED: [chars]; [chars]
Explanation An error occurred while merging the config data. The reason for the failure : [chars]
Error Message IPS-3-ISLB_CFS_PRECOMMIT_FAILED: [chars]; [chars]
Explanation An error occurred while precommiting data. The reason for the failure : [chars]
Error Message IPS-3-ISLB_CFS_PWWN_RESV_CLAIM_FAILED: [chars]
Explanation PWWN reservation claim failed. The reason for the failure : [chars]
Error Message IPS-3-ISLB_CFS_PWWN_RESV_RELEASE_FAILED: [chars]
Explanation PWWN reservation release failed. The reason for the failure : [chars]
Error Message IPS-3-ISLB_CFS_UNLOCK_FAILED: [chars]
Explanation An error occurred while releasing the CFS lock. The reason for the failure : [chars]
Error Message IPS-3-ISLB_CFS_VRRP_DIST_FAILED: [chars]
Explanation An error occurred while distributing the VRRP CFS runtime data. The reason for the
failure : [chars]
2-234 OL-26589-01
Error Message IPS-3-ISLB_ZONE_ACTIVATION_FAILED: iSLB zoneset activation returned

[hex] for VSAN [dec]
Explanation ISLB zoneset activation failed.
Error Message IPS-3-ISLB_ZONE_ACTIVATION_RETRY: iSLB zoneset activation returned

Explanation ISLB zoneset activation failed. Zone server busy.
Recommended Action Retry the iSLB zonest activation.
Error Message IPS-3-ISLB_ZONE_NO_ACTIVE_ZONESET: iSLB zoneset activation returned

Explanation ISLB zoneset activation failed. No active zoneset.
Recommended Action Activate a zoneset in the specified VSAN and retry
Error Message IPS-3-RED_PACKET_DROPS: Congestion detected on GigabitEthernet port

(buffer pool size: [dec])
Explanation Congestion detected on GigabitEthernet port due to RED threshold limit
IPS-4
Error Message IPS-4-FCIP_FTA_CFG_MISMATCH: [chars]: Mismatch in FCIP Ficon Tape

Acceleration configuration with peer
Explanation The FCIP Ficon Tape Acceleration configuration does not match with
peersconfiguration'
Recommended Action Fix the FCIP Ficon Tape Acceleration configuration to be consistent with the
peer
Error Message IPS-4-FCIP_FTA_VSAN_UPDATE_WARNING: FCIP FICON tape acceleration

VSAN update had an error ([chars]) on interface [chars] causing a flap of the
interface
Explanation The FCIP FICON tape acceleration VSAN configuration experienced an error when
disabling and enabling the VSAN over the FCIP tunnel. The FCIP tunnel was disabled and
re-enabled as a result of this error to ensure data integrity.
OL-26589-01 2-235
Error Message IPS-4-FCIP_LICENSE_BIND_FAILED: Bind failed for [chars] due to

[chars] for license failure; configuration accepted but bind failed
Explanation The FCIP configuration was accepted, but the FCIP interface did not bind to a physical
interface because the appropriate license was not available. If a license becomes available in the
future, this FCIP interface will bind to a physical interface automatically.
Recommended Action Check the license state with "show license usage" and acquire the necessary
FCIP license
Error Message IPS-4-FCIP_XRCE_LICENSE_FAILED: XRC Acceleration deactivated due to

license failure
Explanation The XRC Acceleration configuration was accepted, but will remain inactive until a
valid license is available. When the appropriate license is installed, XRC accelaration will be
activated.
Recommended Action Check the license state with "show license usage" and acquire the necessary
XRC_ACCL license
Error Message IPS-4-FCIP_XRCE_LICENSE_INSTALLED: XRC Acceleration activated due to

valid license
Explanation The XRC Acceleration configuration is activated as a valid license has been installed.
IPS-5
Error Message IPS-5-FCIP_BIND_FAILED: Bind failed for [chars] due to [chars] for
[chars]
Explanation FCIP/ISCSI Interface bind to Ethernet port failed
Error Message IPS-5-FCIP_BPORT_KEEPALIVES_NOT_SUPPORTED: Bport Keepalives not

supported for FCIP [chars]
Explanation Bport Keepalives not supported in this release
Error Message IPS-5-FCIP_BPORT_NOT_SUPPORTED: Bport not supported for FCIP [chars]
Explanation Bport not supported in this releas
2-236 OL-26589-01
Error Message IPS-5-FCIP_FTA_ALREADY_OFF: FTA Already Off, [chars] VSAN: [dec]
Explanation FTA Already Off
Error Message IPS-5-FCIP_FTA_ALREADY_ON: FTA Already ON, [chars] VSAN: [dec]
Explanation FTA Already ON
Error Message IPS-5-FCIP_FTA_CB_DOWN: FTA [chars] is DOWN
Explanation FTA is DOWN
Error Message IPS-5-FCIP_FTA_CB_UP: FTA [chars], is UP
Explanation FTA is UP
Error Message IPS-5-FCIP_FTA_DISBAND_GRP_CMD: Disband Group message processed

PGID: [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN:
[dec]
Explanation FCIP Disbanded a Group
Error Message IPS-5-FCIP_FTA_EST_GRP_CMD: Path Group establised for PGID: [chars]

CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FCIP established a Path Group
Error Message IPS-5-FCIP_FTA_NPORT_PATH_RSCN_CLNUP_PASS1: RSCN Cleanup Pass1

[chars] FCID1: [hex] FCID2: [hex] VSAN: [dec]
Explanation Doing RSCN Cleanup, Pass 1
OL-26589-01 2-237
Error Message IPS-5-FCIP_FTA_NPORT_PATH_RSCN_CLNUP_PASS2: RSCN Cleanup Pass2

[chars] FCID1: [hex] FCID2: [hex] VSAN: [dec]
Explanation Doing RSCN Cleanup, Pass 2
Error Message IPS-5-FCIP_FTA_RESIGN_GRP_CMD: Resign group processed for PGID:

[chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FCIP Resigned a Group
Error Message IPS-5-FCIP_FTA_RESP_3490: 3490 device discovered by FCIP CH FCID:

[hex] CHI: [hex] device at CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation Device type discovered is 3490
Error Message IPS-5-FCIP_FTA_RESP_3590: 3590 device discovered by FCIP CH FCID:

[hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation Device type discovered is 3590
Error Message IPS-5-FCIP_FTA_RESP_NOT_TAPE: Non-tape device discovered by FCIP CH

FCID: [hex] CHI: [hex] device at CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FCIP discovered a non-tape device
Error Message IPS-5-FCIP_FTA_TURN_OFF_LAST_VSAN: FTA turned off for the Last VSAN,
[chars] VSAN: [dec]
Explanation FTA turned off for the Last Vsan
Error Message IPS-5-FCIP_FTA_TURN_OFF_NONLAST_VSAN: FTA turned off for the

Non-Last VSAN, [chars] VSAN: [dec]
Explanation FTA turned off for the Non-Last Vsan
2-238 OL-26589-01
Error Message IPS-5-FCIP_FTA_TURN_ON: Turn ON FTA, [chars] VSAN: [dec]
Explanation FTA turned ON
Error Message IPS-5-FCIP_FTA_WARNING: FTA Warning :[chars]
Explanation Generic FTA Warning
Error Message IPS-5-FCIP_FTRA_CFG_MISMATCH: [chars]: Mismatch in FCIP FICON Tape

Read Accelerator configuration with peer
Explanation The FCIP FICON Tape Read Accelerator configuration does not match with
peersconfiguration'
Recommended Action Fix the FCIP FICON Tape Read Accelerator configuration to be consistent
with the peer
Error Message IPS-5-FCIP_IF_CR_DEL: Interface [chars] [chars]
Explanation FCIP Interface was Created or Deleted
Error Message IPS-5-FCIP_MODE1_CHANGED_TO_MODE2: Changing mode1 compression to mode2

for [chars], on a MSM/SSN-16 linecard
Explanation Change mode1 compression to mode2 on a MSM/SSN-16 linecard
Error Message IPS-5-FCIP_NUM_TCP_CONNS_MISMATCH: [chars]: configured for 2 tcp

connections but currently operating with 1 connection
Explanation Number of configured tcp connections dontmatchnumberofconnectionscurrentlyup'
Error Message IPS-5-FCIP_PEER_CAVIUM: Peer FCIP [chars] is a MSM/SSN-16 linecard
Explanation Peer linecard is a MSM/SSN-16
OL-26589-01 2-239
Error Message IPS-5-FCIP_PEER_NON_CAVIUM: Peer FCIP [chars] is a non MSM/SSN-16

linecard
Explanation Peer linecard is non MSM/SSN-16
Error Message IPS-5-FCIP_RA_CFG_MISMATCH: [chars]: Mismatch in FCIP Tape Read

Acceleration capability with peer
Explanation The FCIP Tape Read Acceleration capability does not match with peersconfiguration'
Recommended Action Fix the FCIP Tape Read Acceleration capability to be consistent with the peer
Error Message IPS-5-FCIP_SF_NOT_SUPPORTED: Special-Frame not supported for FCIP

[chars]
Explanation Spl-Frame not supported in this release
Error Message IPS-5-FCIP_TA_CFG_MISMATCH: [chars]: Mismatch in FCIP Tape

Explanation The FCIP Tape Acceleration configuration does not match with peersconfiguration'
Recommended Action Fix the FCIP Tape Acceleration configuration to be consistent with the peer
Error Message IPS-5-FCIP_TA_ITL_MISMATCH: [chars]: Mismatch in FCIP Write/Tape

Acceleration software capability with peer
Explanation The FCIP Write/Tape Acceleration software capability does not match with
peerssoftwarecapability'
Recommended Action Fix the FCIP software to be consistent with the peer
Error Message IPS-5-FCIP_TSTAMP_CHK_FAILED: [chars]: Timestamp check failed on

ingressing frames
Explanation Timestamp between local and remote side exceeds the configured tolerance
Error Message IPS-5-FCIP_UNBIND_FAILED: UNBIND failed for [chars] due to [chars]

for [chars]
Explanation FCIP/ISCSI Interface UNBIND from Ethernet port failed
2-240 OL-26589-01
Error Message IPS-5-FCIP_WA_CFG_MISMATCH: [chars]: Mismatch in FCIP Write

Explanation The FCIP Write Acceleration configuration does not match with peersconfiguration'
Recommended Action Fix the FCIP Write Acceleration configuration to be consistent with the peer
Error Message IPS-5-FCIP_WA_XFER_RDY_ERR: [chars]: FCIP Write Acceleration

received XFER-RDY after exhcange cleanup. Host [hex] Target [hex]
Explanation FCIP Write/Tape Acceleration received XFER-RDY after exchange cleanup
Error Message IPS-5-FCIP_XRCE_CFG_MISMATCH: [chars]: Mismatch in FCIP XRC Emulator

configuration with peer
Explanation The FCIP XRC Emulator configuration does not match with peersconfiguration'
Recommended Action Fix the FCIP XRC Emulator configuration to be consistent with the peer
Error Message IPS-5-IPS_IPACL_LOG_MSG: [chars]
Explanation Details of the packet dropped due to ACLs
Error Message IPS-5-IPS_MGR_FEATURE_ENABLE: ips:[dec] iscsi:[dec] fcip:[dec]

iscsi-intf-vsan:[dec] ips-lc:[dec]
Explanation IPS Manager feature enabled/disabled
Error Message IPS-5-IPS_TCP_PORT_IN_USE: Cannot bringup interface [chars], local

port already in use
Explanation FCIP and iSCSI interface are trying to use the same local port, please use different ports
Error Message IPS-5-ISCSI_BAD_DATA_DIGEST_CRC: iSCSI ingress data digest error

from initiator [chars] alias [chars] S_ID [hex] to D_ID [hex]
Explanation ISCSI Ingress Data Digest CRC failed
OL-26589-01 2-241
Error Message IPS-5-ISCSI_CONN_DOWN_BATCH: [chars]: [dec] iSCSI sessions failed in

last [chars], reason: [chars]
Explanation Number of iSCSI session down during the last time interval
Error Message IPS-5-ISCSI_CONN_DOWN: [chars]: iSCSI session down from initiator

[chars] alias [chars] ip [chars] to target [chars], reason: [chars]
Explanation ISCSI session goes down
Error Message IPS-5-ISCSI_CONN_UP: [chars]: iSCSI session up from initiator [chars]

alias [chars] ip [chars] to target [chars]
Explanation ISCSI session comes up and reaches Full-Feature phase
Error Message IPS-5-ISCSI_PORT_FAILOVER: [chars]: iSCSI initiator [chars] alias

[chars] ip [chars] target [chars]. FC session failed over to port [chars]
Explanation FC session for the iSCSI session failed over to newly active port
Error Message IPS-5-ISCSI_SB_GET_TGT: iSCSI SB get [dec] targets, initiator [chars]

alias [chars] ip [chars]
Explanation ISCSI FCNS query response
Error Message IPS-5-ISCSI_SESSION_CREATE_FAILURE: [chars]: iSCSI Session initiator

[chars] target [chars] create failed. [chars]
Explanation ISCSI Session Create failed
Error Message IPS-5-ISCSI_SESSION_CREATE_REDIRECT: [chars]: iSCSI Session

initiator [chars] target [chars] redirected to [chars]/[chars]
Explanation ISCSI Session Create redirected
2-242 OL-26589-01
Error Message IPS-5-ISCSI_SESSION_REDIRECT_TIMEOUT: iSCSI Session initiator

[chars] to [chars] redirected to [chars] timeout
Explanation ISCSI Session Redirect timeout
Error Message IPS-5-ISLB_CFS_SESSION_CLEARED: CFS Session Cleared
Explanation CFS Session Cleared by user
Error Message IPS-5-LRTP_HDR_FCID_MISMATCH: LRTP header s_id([hex]) d_id([hex]) do

not match Inner header s_id([hex]) d_id([hex]) Initiator ([chars]) Target([chars])
Explanation The s_id and/or the d_id field in the

framesLRTPheaderdoesnotmatchthes_idord_idfieldintheinnerheader'
Error Message IPS-5-PORT_IPCFG_FAILED: Cannot configure IP address for interface

[chars]
Explanation Cannot configure IPS port IP address
Error Message IPS-5-SB_MGR_CORE_FAILED: Ethernet Processing core [chars] failed

due to [chars]
Explanation Ethernet Processing Core failed
Error Message IPS-5-SFRAME_ENTITY_ID_MISMATCH: [chars]: special frame profile ID

mismatch
Explanation Special frame received and destination profile ID does not match local profile ID
Error Message IPS-5-SFRAME_FABRIC_WWN_MISMATCH: [chars]: special frame fabric wwn

mismatch
Explanation Special frame received and source/destination fabric wwn does not match local
destination/ source fabric wwn
OL-26589-01 2-243
Error Message IPS-5-SFRAME_IF_ADMIN_DOWN: [chars]: special frame received if down
Explanation Special frame received and interface is admin down
Error Message IPS-5-SFRAME_IF_NOT_ENABLED: [chars]: special frame not enabled
Explanation Special frame received and interface special frame configuration is disabled
Error Message IPS-5-SFRAME_INVALID_NONCE: [chars]: special frame response has

invalid nonce for FCIP
Explanation Special frame response has a different nonce than was originally sent in the special
frame
Error Message IPS-5-SFRAME_NOT_RECV: [chars]: special frame was not received by

passive-side FCIP
Explanation Special frame was not received by the passive-side of the FCIP TCP tunnel within
given time period
Error Message IPS-5-SFRAME_RESP_MISMATCH: [chars]: special frame response has byte

mismatch for FCIP
Explanation Special frame response has a mismiatch in one of the bytes from what was sent from
the FCIP special frame sender
Error Message IPS-5-SFRAME_RESP_NOT_RECV: [chars]: special frame response was not

received by active-side FCIP
Explanation Special frame response was not received by the active-side of the FCIP TCP tunnel
within given time period
2-244 OL-26589-01
IPS-6
Error Message IPS-6-FCIP_FTA_READ_ACCEL_STARTED: Read Acceleration started for CH

FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FCIP-FTA Read Acceleration started
Error Message IPS-6-FCIP_FTA_READ_ACCEL_STOPPED: Read Acceleration stopped for CH

FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] due to [chars]
after [dec] MB reads
Explanation FCIP-FTA Read Acceleration stopped
Error Message IPS-6-FCIP_FTA_WRITE_ACCEL_STARTED: Write Acceleration started for

CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]
Explanation FCIP-FTA Write Acceleration started
Error Message IPS-6-FCIP_FTA_WRITE_ACCEL_STOPPED: Write Acceleration stopped for

CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] due to
[chars] after [dec] MB writes
Explanation FCIP-FTA Write Acceleration stopped
IPS-7
Error Message IPS-7-ISCSI_FCNS_QUERY_REQ: return [hex], wait [dec], VSAN [dec],

Init: [chars]
Explanation ISCSI FCNS query
Error Message IPS-7-ISCSI_FCNS_QUERY_RESP: result [hex], [dec] targets, wait

[dec], Init: [chars]
OL-26589-01 2-245
Error Message IPS-7-ISCSI_NEW_FCNS_QUERY_REQ: return [hex], VSANs [chars], Init:

[chars]
Explanation ISCSI FCNS query
Error Message IPS-7-ISCSI_NEW_FCNS_QUERY_RESP: result [hex], [dec] entries, [dec]

targets, [dec] total targets Init: [chars]
Error Message IPS-7-ISNS_SVR_ERR_RESPONSE: iSNS server returned following error

code on iSNS request for interface [chars] : [dec]
Explanation ISNS server returned an error for register/deregister request. For select error codes
iSNS client would retry and re-register all target nodes corresponding to the interface
IPV6 Messages
This section contains the IPV6 messages.
IPV6-2
Error Message IPV6-2-ALLOC_MEMORY: Memory allocation failed
Explanation The IP Configuration Manager failed to allocate a block of dynamic memory.
IPV6-3
Error Message IPV6-3-FILE_WRITE_FAILED: Writing to file [chars] failed - error:

[chars]
Explanation Writing to a file failed probably due to no space.
Recommended Action Ipv6
2-246 OL-26589-01
Error Message IPV6-3-INIT_FAILED: Initialization failed. Component [chars]
[chars].
component.
IPV6-4
Error Message IPV6-4-DAD_FAILED_EVENT: Duplicate address detection failed for

[chars] on [chars]
Explanation Duplicate address detection for IP address failed.
Recommended Action Ipv6
IPV6-6
Error Message IPV6-6-CONFIG_EVENT: IP Configuration Msg: [chars]
Explanation Configuration message that needs to be logged.
Error Message IPV6-6-INTERFACE_DELETED: The interface [chars] has been deleted
Explanation The specified interface has been deleted. The service will delete all the configuration
on that interface.
Error Message IPV6-6-INTERFACE_EVENT: IP address [chars] [chars] on interface

[chars]
Explanation The IP address [chars] has been successfully [chars] on the interface [chars].
Error Message IPV6-6-ROUTE_NOT_ACTIVE: The [chars] is not active
Explanation The specified route is successfully configured but currently is not active.
Recommended Action Check that the route is correct and the outgoing interface is operationally up.
OL-26589-01 2-247
Error Message IPV6-6-STARTING: IP configuration Manager started
Explanation The IP Configuration Manager service has successfully started.
IP Messages
This section contains the IP messages.
IP-1
Error Message IP-1-DHCP_CLIENT_FAILED: dhcp-client failed to get the ip address
Explanation Dhcp-client failed to get the ip from server, probably due to server lease unavailability
or cable disconnectivity.
Recommended Action Ip
IP-2
Error Message IP-2-ALLOC_MEMORY: Memory allocation failed
Explanation The IP Configuration Manager failed to allocate a block of dynamic memory.
IP-3
Error Message IP-3-FILE_WRITE_FAILED: Writing to file [chars] failed - error:

[chars]
Explanation Writing to a file failed probably due to no space.
Error Message IP-3-INIT_FAILED: Initialization failed. Component [chars]
[chars].
component.
2-248 OL-26589-01
IP-4
Error Message IP-4-DAD_FAILED_EVENT: Duplicate address detected for [chars] on

[chars]
Explanation Duplicate address detected for IP address.
IP-6
Error Message IP-6-CONFIG_EVENT: IP Configuration Msg: [chars]
Explanation Configuration message that needs to be logged.
Error Message IP-6-DHCP_CLIENT_SUCCESS: dhcp_client got ip

address:[chars],netmask:[chars] for mgmt interface,got from server:[chars]
Explanation Dhcp-client is able to get the ip address from server,
Error Message IP-6-INTERFACE_DELETED: The interface [chars] has been deleted
Explanation The specified interface has been deleted. The service will delete all the configuration
on that interface.
Error Message IP-6-INTERFACE_EVENT: IP address [chars] [chars] on interface [chars]
Explanation The IP address [chars] has been successfully [chars] on the interface [chars].
Error Message IP-6-ROUTE_NOT_ACTIVE: The [chars] is not active
Explanation The specified route is successfully configured but currently is not active.
Recommended Action Check that the route is correct and the outgoing interface is operationally up.
OL-26589-01 2-249
Error Message IP-6-STARTING: IP configuration Manager started
Explanation The IP Configuration Manager service has successfully started.
ISAPI Messages
This section contains the ISAPI messages.
ISAPI-SLOT#-0
Error Message ISAPI-SLOT#-0-INVISTA_EMERG: [chars]
Explanation Isapi-invista software messages
Error Message ISAPI-SLOT#-0-MSM_EMERG: [chars]
Explanation Isapi software messages
Error Message ISAPI-SLOT#-0-NSP_EMERG: [chars]
Explanation Isapi-nsp software messages
Error Message ISAPI-SLOT#-0-SSM_EMERG: [chars]
Error Message ISAPI-SLOT#-0-SSN_EMERG: [chars]
2-250 OL-26589-01
ISAPI-SLOT#-1
Error Message ISAPI-SLOT#-1-INVISTA_ALERT: [chars]
Error Message ISAPI-SLOT#-1-MSM_ALERT: [chars]
Error Message ISAPI-SLOT#-1-NSP_ALERT: [chars]
Error Message ISAPI-SLOT#-1-SSM_ALERT: [chars]
Error Message ISAPI-SLOT#-1-SSN_ALERT: [chars]
ISAPI-SLOT#-2
Error Message ISAPI-SLOT#-2-INVISTA_CRIT: [chars]
Error Message ISAPI-SLOT#-2-MSM_CRIT: [chars]
OL-26589-01 2-251
Error Message ISAPI-SLOT#-2-NSP_CRIT: [chars]
Error Message ISAPI-SLOT#-2-SSM_CRIT: [chars]
Error Message ISAPI-SLOT#-2-SSN_CRIT: [chars]
ISAPI-SLOT#-3
Error Message ISAPI-SLOT#-3-INVISTA_ERROR: [chars]
Error Message ISAPI-SLOT#-3-MSM_ERROR: [chars]
Error Message ISAPI-SLOT#-3-NSP_ERROR: [chars]
Error Message ISAPI-SLOT#-3-SSM_ERROR: [chars]
2-252 OL-26589-01
Error Message ISAPI-SLOT#-3-SSN_ERROR: [chars]
ISAPI-SLOT#-4
Error Message ISAPI-SLOT#-4-INVISTA_WARN: [chars]
Error Message ISAPI-SLOT#-4-MSM_WARN: [chars]
Error Message ISAPI-SLOT#-4-NSP_WARN: [chars]
Error Message ISAPI-SLOT#-4-SSM_WARN: [chars]
Error Message ISAPI-SLOT#-4-SSN_WARN: [chars]
ISAPI-SLOT#-5
Error Message ISAPI-SLOT#-5-INVISTA_NOTICE: [chars]
OL-26589-01 2-253
Error Message ISAPI-SLOT#-5-MSM_NOTICE: [chars]
Error Message ISAPI-SLOT#-5-NSP_NOTICE: [chars]
Error Message ISAPI-SLOT#-5-SSM_NOTICE: [chars]
Error Message ISAPI-SLOT#-5-SSN_NOTICE: [chars]
ISAPI-SLOT#-6
Error Message ISAPI-SLOT#-6-INVISTA_INFO: [chars]
Error Message ISAPI-SLOT#-6-MSM_INFO: [chars]
Error Message ISAPI-SLOT#-6-NSP_INFO: [chars]
2-254 OL-26589-01
Error Message ISAPI-SLOT#-6-SSM_INFO: [chars]
Error Message ISAPI-SLOT#-6-SSN_INFO: [chars]
ISAPI-SLOT#-7
Error Message ISAPI-SLOT#-7-INVISTA_DEBUG: [chars]
Error Message ISAPI-SLOT#-7-MSM_DEBUG: [chars]
Error Message ISAPI-SLOT#-7-NSP_DEBUG: [chars]
Error Message ISAPI-SLOT#-7-SSM_DEBUG: [chars]
Error Message ISAPI-SLOT#-7-SSN_DEBUG: [chars]
OL-26589-01 2-255
ISCM Messages
ISCM-2
Error Message ISCM-2-APBR_CORRUPT: RISE APBR: in Corrupt State, RS IP: [chars],

port: [dec], Proto: [dec], nhop IP: [chars], slot ID: [dec], vlan: [dec]. Reason:
[chars].
Explanation RMAP
Recommended Action ACL cannot be completely deleted.
Error Message ISCM-2-LICENSE_EXPIRED: RISE License: LAN_ENTERPRISE_SERVICES_PKG

license has expired. RISE feature is being disabled.
Explanation License or grace-period has expired.
Recommended Action Take steps to renew license. Feature will be disabled.
Error Message ISCM-2-LICENSE_MISSING: RISE License: LAN_ENTERPRISE_SERVICES_PKG

does not exist.
Explanation License does not exist when attempting to enable RISE feature.
Recommended Action Acquire license or grace-period permission.
ISCM-3
Error Message ISCM-3-APBR_ACLMGR_ERROR: RISE APBR: ACL was not [chars], apbr
payload: [chars].
Explanation Acl was not created/deleted.
Recommended Action Check TCAM resource limit, and the sys admin.
Error Message ISCM-3-APBR_INGRESS_INT_NOT_FOUND: RISE APBR:

cantfindtheingressinterfaceforRSIP:[chars].'
Explanation 7K cannot find a route to the real server.
Recommended Action Check real server network reachablity in the current switch.
Error Message ISCM-3-APBR_PURGE_ERROR: RISE APBR: Purge failure, slot id: [dec].
Explanation PBR entriles for RISE cannot be deleted cleanly.
Recommended Action Manually delete pbr entries.
2-256 OL-26589-01
Error Message ISCM-3-APBR_RPM_ERROR: RISE APBR: RPM returns internal error, rpm
resp status: [dec], apbr payload: [chars].
Explanation Rmap step was not completed.
Recommended Action Check TCAM resource limit, or rmap collision on the same interface, and the
sys admin.
Error Message ISCM-3-RHI_ROUTE_ISSUE: RISE RHI: slot [dec] route [chars] cannot be
[chars]. Reason:[chars].
Explanation URIB dropped this RHI request. See reason string with the following possibilities: 1.
SVI for data vlan [dec] does not exist. 2. SVI for data vlan [dec] is down. 3. urib issues.
Recommended Action Take corrective action per the reason.
ISCM-4
Error Message ISCM-4-APBR_MAX_LIMIT: RISE APBR: Reached max apbr entries [dec] per
RISE. slot id: [dec].
Explanation PBR entriles for RISE cannot be deleted cleanly.
Recommended Action Manually delete pbr entries.
Error Message ISCM-4-APBR_PBR_DISABLED: RISE APBR: feature PBR Disabled.
Explanation APBR will not function correctly without pbr feature.
Recommended Action Manually enable pbr feature.
Error Message ISCM-4-DISCOVERY_CHANNEL_DOWN: RISE Channel down, slot id: [dec],

Reason: [chars]
Explanation See reason string in the error message with the following possibilities: 1. Error in
bootstrap/health-monitorying response. 2. Timed out while waiting for bootstrap/health-monitoring
response. 3. Failed to send bootstrap/health-monitorying message. 4. Control VLAN interface is not
operational. 5. RISE interface [chars] is not operational. 6. RISE interface [chars] does not have
control VLAN [dec] as trunk member. 7. Control VLAN ([dec]) interface does not have valid IP. 8.
RISE port channel po [dec] has no member ports. 9. Failed to send vlan-group. 10. RISE IP [chars]
is already assigned to another service, slot id [dec].
Recommended Action Take corrective action per the reason
Error Message ISCM-4-ISSU_PRE_UPGRADE_TIMEOUT: RISE ISSU: pre-upgrade timed out,

reason: [chars].
Explanation See the reason.
Recommended Action Try again with the upgrade.
OL-26589-01 2-257
Error Message ISCM-4-ISSU_UNEXPECTED_SLOT_MSG: RISE ISSU: unexpected msg from slot

[dec], opcode: [dec].
Explanation Application should not send msg during ISSU. iSCM will ignore.
Error Message ISCM-4-LICENSE_EXPIRING: RISE License: LAN_ENTERPRISE_SERVICES_PKG

license will expiry in [dec] days [dec] hours [chars]econds.
Explanation License or grace-period expiration warning.
Recommended Action Take steps to renew license. Prepare for feature disable.
ISCM-5
Error Message ISCM-5-TRANSPORT_ISSUE: RISE Transport: slot [dec] failed to send,

reason : [chars].
Explanation See the reason.
Recommended Action Check the network connectivity and the appliance status.
ISNS Messages
This section contains the ISNS messages.
ISNS-2
Error Message ISNS-2-ISNS_CFS_OPERATION_FAILED: iSNS CFS [chars] failed
Explanation ISNS CFS operation failed
Error Message ISNS-2-ISNS_INIT: iSNS initialization of [chars] [chars]
Explanation ISNS initialization failed
IVR Messages
This section contains the IVR messages.
2-258 OL-26589-01
IVR-2
Error Message IVR-2-AUTOLEARN_ACTION_FAIL: failure happens during constructing

virtual dynamic pfcid table
Explanation This can happen if failure happens during building, distributing or committing the
virtual dynamic pfcid table
Recommended Action Please 1. check the fabric connection or 2. check current virtual
user-configured pfcid entries and internally assigned virtual fcid entries for possible conflict
Error Message IVR-2-AUTOLEARN_FEATURE_NOT_SUPPORT: some switches:[chars]

dontsupportautolearn'
Explanation This can happen if some switches doesntsupportthevirtualpfcidautolearnfeature'
Recommended Action Please upgrade the unsupported switches
Error Message IVR-2-CFS_PEER_LOST_WITHIN_SESSION: CFS peer with switch wwn [chars]

was lost in the middle of an active CFS session. Abort the CFS session and re-enter
the configuration changes
Explanation Due to port flaps, link outages, switch restart etc. a CFS peer switch of IVR was lost.
The current configuration changes would not be applied to this peer until the peer merges with this
switch. The CFS merge may fail if the configuration at the lost peer conflicts with the changes made
in this session. Also, IVR auto topology could be out of sync. with this peer. It is recommended that
the user abort this CFS session using ivr abort command and then re-enter the configuration
changes.
Error Message IVR-2-DEVICE_FCID_REWRITE_FAILURE: Failure while programming FCID

rewrite entries for pWWN [chars] on incoming VSAN [dec]. Device may not be able
to communicate with its peer devices, failure reason code: [hex]
Explanation Failed to program FCID rewrite entries probably because the hardware ran out of FCID
rewrite entries. This can happen if there are too many devices in Inter-VSAN zone or too many local
VSANs in VSAN topology
Recommended Action Reduce the number of devices involved in IVR in the active IVR zoneset.
Also, reduce the number of redundant transit VSANs, if any
OL-26589-01 2-259
Error Message IVR-2-DEVICE_STATE_INCOMPATIBLE_WITH_NAT_MODE: State for device with

port WWN [chars] could not be restored because it was incompatible with the current
NAT mode([dec]). This probably happened because NAT mode was modified without
completely deactivating the active IVR zoneset
Explanation This probably happened because NAT mode was modified without completely
deactivating the active IVR zoneset
Recommended Action The switch needs to be rebooted
Error Message IVR-2-DEVICE_VSAN_REWRITE_FAILURE: Failure while programming VSAN

rewrite entries for pWWN [chars] on incoming VSAN [dec]. Device may not be able
to communicate with its peer devices
Explanation Failed to program VSAN rewrite entries probably because the hardware ran out of
VSAN rewrite entries. This can happen if there are too many devices in Inter-VSAN zone or too
many local VSANs in VSAN topology
Recommended Action Reduce the number of domains involved in IVR by moving the members of
active IVR zoneset to fewer switches. Also, reduce the number of redundant transit VSANs, if any
Error Message IVR-2-INTEROP_MODE_2_OR_3_BF_FAILED: [chars] VSAN [dec] Virtual

Domain [chars]
Explanation Build Fabric (BF) failed in VSAN [dec]. The BF was initiated in order to remove an
unused virtual domain [dec] from the fcdomain list in that VSAN. The virtual domain still remains
in the fcdomain list and hence it would not be available in that VSAN for assignment.
Recommended Action Perform a manual build fabric using

fcdomainsinterfaceifyouwouldliketoremovetheunusedvirtualdomain(s)fromthefcdomainlist.'
Error Message IVR-2-INTEROP_MODE_2_OR_3_RDI_FAILED: VSAN [dec], requested domain

[chars], received domain [chars] sWWN [chars]. Return Code [chars]
Explanation Request Domain Identifier (RDI) command to allocate virtual domain [dec] failed in
VSAN [dec]. Received another domain [chars] instead. IVR-members connected to third-party
switch may not participate in IVR communications. It is likely that the domain requested in the RDI
command is already in use.
Recommended Action Reassign the domains so that the domain requested via RDI does not overlap
with any existing domain in that VSAN.
Error Message IVR-2-IVR_DISABLE_FAILED: Inter-VSAN Routing disable failed for

reason: [chars]
Explanation Inter-VSAN Routing disable failed for reason: [chars]. Cleanup might not have
completed
Recommended Action Deactivate ivr zoneset and disable ivr again. If that fails, then the ivr process
would terminate itself in 5 minutes
2-260 OL-26589-01
Error Message IVR-2-IVZS_ACTIVATION_FAILED_RETRYING: Inter-VSAN zoneset activation

failed in VSAN [dec] : [chars]. retrying after [dec] seconds
Explanation Inter-VSAN zoneset activation failed in VSAN [dec] : [chars]. This could be an
intermittent regular zoneset activation error. The activation will be retried in [dec] seconds.
Error Message IVR-2-NO_LICENSE_SHUTDOWN: Inter-VSAN Routing is shutting down.
Explanation License required for continued IVR operation is not available. Hence IVR is shutting
down
Recommended Action Install appropriate license for IVR services and then enable IVR again.
Error Message IVR-2-NO_LICENSE_WARNING: Inter-VSAN Routing would shutdown in [dec]

seconds.
Explanation License required for continued IVR operation is not available. Unless the required
license is installed IVR would shutdown in [dec] seconds. IVR configurations would be lost.
Recommended Action Install appropriate license for IVR services to continute to operate
uninterrupted within [dec] seconds
Error Message IVR-2-PERSISTENT_VIRTUAL_FCID_CONFLICT_WITH_AUTOLEARN: Persistent

virtual fcid and dynamic pfcid entries
Explanation This can happen if conflict happens during persistent virtual domain, or virtual fcid
entry configuration.
Recommended Action Please assign a non-conflict persistent virtual domain or fcid entry with
current dynamic entries
Error Message IVR-2-PERSISTENT_VIRTUAL_FCID_UNAVAILABLE: to vsan [dec] because the

configured persistent virtual domain/fcid could not be assigned
Explanation This can happen if the virtual domain/fcid configured by the user is - a) Already in use
(either by IVR or a real switch) b) Not allowed due to interop mode or allowed domain list
Recommended Action Please make sure that the configured virtual domain/fcid is allowed and
available for use
OL-26589-01 2-261
Error Message IVR-2-VIRTUAL_DOMAIN_CONFLICT: In VSAN [dec] virtual domain [dec]

from native VSAN [dec] conflicts with native VSAN [dec] for the same virtual domain
Explanation Currently advertised virtual domain [dec] in VSAN [dec] is native to VSAN [dec]. This
switch has learned of a device that is member of active IVR zone and has the same domain ID, but
belongs to a different native VSAN. This device would not be advertised in that VSAN until the
domain conflict is resolved.
Error Message IVR-2-VIRTUAL_FCID_UNAVAILABLE: to vsan [dec] because the internally

generated FCID conflicts with fcid assigned to WWN [chars]. Please configure fcid
for WWN [chars] too
Explanation This can happen if the virtual domain/fcid internally configured is already in use by
another active device
Recommended Action Please assign a different persistent virtual fcid by CLI command
IVR-3
Error Message IVR-3-AAM_MODE_CANNOT_CHANGE: AAM mode cannot be changed. Might cause

the fabric NAT mode inconsistency
Explanation Could be caused by ivr NAT is not enable
Error Message IVR-3-AAM_MODE_DEREGISTERED_FAILED: Abstract ACL Manager (AAM) mode

deregister failed. Error code is [chars].
Explanation Abstract ACL Manager (AAM) mode deregister failed
Error Message IVR-3-AAM_MODE_REGISTERED_FAILED: Abstract ACL Manager (AAM)

register failed. Error code is [chars].
Explanation Abstract ACL Manager (AAM) register failed
Error Message IVR-3-ACL_ERROR: ACL API, [chars], failed with error [chars]
Explanation IVR invoked ACL API and received the error code. [chars] describes the API and
[chars] specifies the error.
2-262 OL-26589-01
Error Message IVR-3-ACL_PERMIT_ENTRY_ERROR: ACL permit entry update on interface

[chars] failed for reason: [chars]
Explanation ACL could not program permit entries for IVR traffic. [chars] describes the interface
named and [chars] describes the system error message from ACL. IVR traffic coming from the
interface may be dropped.
Recommended Action If the problem persists, please contact TAC, or your reseller for support.
Error Message IVR-3-ACL_PLOGI_ENTRY_ERROR: PLOGI capture entry update in slot [dec]

failed for reason: [chars]
Explanation ACL could not program IVR PLOGI could not be programmed. slot[dec] describes the
line card slot number and [chars] describes the system error message. PLOGI and its response may
be dropped because ivr process cannot capture those frames.
Error Message IVR-3-AFID_CONFLICT: [chars]
Explanation AFID configuration is different at different ivr-enabled switches in the same VSAN.
Change AFID configuration (auto mode) or vsan topology configuration (user mode) to make it
consistent
Error Message IVR-3-CFS_INVALID_PAYLOAD_RECEIVED: Inter-VSAN process received

invalid payload from CFS
Explanation Inter-VSAN process received invalid payload from CFS.
Error Message IVR-3-CLEAR_FAILED: [chars]
Explanation An error occurred while clearing the lock. The reason for the failure : [chars]
Error Message IVR-3-COMMIT_FAILED: [chars]
Explanation An error occurred while committing configuration. The reason for the failure : [chars]
OL-26589-01 2-263
Error Message IVR-3-COMMIT_PARTIALLY_FAILED: [chars]
Explanation An error occurred while committing configuration. Configuration could not be

committed on some switches. The reason for the failure : [chars]. Configuration can be inconsistent
in the fabric.
Error Message IVR-3-COMMIT_REJECTED: [chars]
Explanation Commit request received from remote switch is rejected. The reason for the failure:
[chars]
Error Message IVR-3-DDAS_LOCK_TIMER_EXPIRED: IVR database lock is released, as

device-alias commit/abort notification is not received in the expected time frame.
Explanation When device-alias sends the validation request, IVR database is locked and a timer is
started. For any reason, if device-alias commit/abort notification is not received within the expected
time frame, the lock timer gets expired and the lock is released. If device-alias commmit notification
is received after the lock is released, the changes are not applied and this could cause inconsistency
between IVR and device-alias.
Error Message IVR-3-DEVICE_NOT_PREENT_IN_FB_DB_FICON: Device with port WWN [chars]

could not be exported to VSANs [chars] because its native switch is not present
in the current active fabric binding database of those VSANs.
Explanation This happens if ficon is enabled on VSANs [chars] and native switch of device with
port WWN [chars] is not present in the current active fabric binding database of those VSANs. This
is a requirement for ficon compliance.
Error Message IVR-3-DEVICE_ON_WRONG_NATIVE_AFID_VSAN: Device with port WWN [chars]

(FCID:[chars], native VSAN [dec] native AFID [dec]) may not be exported to other
VSANs (for Inter-VSAN zoning) because it has come online in VSAN [dec] AFID [dec]
Explanation Device has come online on a AFID/VSAN different from the configured native
AFID/VSAN
2-264 OL-26589-01
Error Message IVR-3-DEVICE_ON_WRONG_NATIVE_VSAN: Device with port WWN [chars]

(FCID:[chars], native VSAN [dec]) may not be exported to other VSANs (for
Inter-VSAN zoning) because domain [hex] exists in VSAN [dec]
Explanation Device has come online on a VSAN different from the configured native VSAN or the
device does not satisfy unique domain criteria.
Error Message IVR-3-DM_ERROR: Domain Manager API, [chars], failed with error [hex]
Explanation IVR invoked DM API and received the error code. [chars] describes the API and
0x[hex] specifies the error.
Error Message IVR-3-DOMAIN_DISALLOWED_IN_INTEROP: Device with port WWN [chars] and

FCID [chars] may not be able to participate in Inter-VSAN zone since domain [dec]
is disallowed in the interop mode for VSAN [dec]
Explanation VSAN interop modes place restrictions on what domain ranges are allowed. This
domain is out of the range allowed for this interop mode. See the Cisco MDS 9000 Family
Configuration Guide for details on the domain range limitations.
Recommended Action Change the domain of the switch to which this IVR zone member is connected
to so that it is within the allowed domain list for the interop mode. The domain identifier can be
statically assigned using fcdomain interface. You can also configure a range of domains allowed in
a VSAN using the fcdomains'allowed-domains'interface.'
Error Message IVR-3-DOMAIN_UNAVAILABLE: Device with port WWN [chars] and FCID
[chars] may not be able to participate in Inter-VSAN zone since domain [dec] is
already assigned in VSAN [dec]
Explanation Device with port WWN [chars] and FCID [dec] may not be able to participate in
Inter-VSAN zone since domain [dec] is already assigned in VSAN [dec].
Error Message IVR-3-FC2_ERROR: FC2 API [chars] failed with error [hex] for [chars]
Explanation IVR invoked FC2 API for [chars] socket and received the error code. [chars] describes
the API and 0x[hex] specifies the error.
OL-26589-01 2-265
Error Message IVR-3-FCID_NAT_MODE_CANNOT_CHANGE: IVR NAT mode cannot be changed.

Might cause the fabric NAT mode inconsistency
Explanation Could be caused by active zoneset, pending activation /deactivation or non-empty

device list
Error Message IVR-3-FCID_REWRITE_REQUEST_TO_ACL_FAILED: fcid rewrite [chars]

request vsan [dec] did [chars] sid [chars] failed:[chars]([hex]).
Explanation This happens when either after IVR retried the request few times or ACL experienced
error while processing the request.
Error Message IVR-3-INTERNAL_ERROR: Internal error: [chars]
Explanation IVR process encountered a general error, one that does not fall in any of the categories.
Error Message IVR-3-INVALID_ZONE_MEMBER_PROP_INTEROP_MODE_2_3: unsupported

member/zone properties in interop mode 2 or 3 [chars]
Explanation Inter-VSAN member properties incompatible with interop mode vsan
Error Message IVR-3-IVR_NAT_OFF_IS_SAB: Fcid-nat must be enabled before IVR zoneset

activation for Sabre platform.
Explanation Fcid-nat must be enabled before IVR zoneset activation for Sabre platform.
Error Message IVR-3-IVZ_ACTIVATION_FAILED_VSAN: Inter-VSAN zoneset [chars]

activation failed in VSAN [dec]
Explanation Inter-VSAN zoneset activation failed failed in VSAN.
Error Message IVR-3-IVZ_ACTIVATION_FAILED: Inter-VSAN zoneset [chars] activation

failed
Explanation Inter-VSAN zoneset activation failed.
2-266 OL-26589-01
Error Message IVR-3-IVZ_DEACTIVATION_FAILED_VSAN: Inter-VSAN zoneset [chars]

deactivation failed in VSAN [dec]
Explanation Inter-VSAN zoneset deactivation failed in VSAN.
Error Message IVR-3-IVZ_DEACTIVATION_FAILED: Inter-VSAN zoneset [chars]

deactivation failed
Explanation Inter-VSAN zoneset deactivation failed.
Error Message IVR-3-LOCK_FAILED: [chars]
Explanation An error occurred while acquiring the lock. The reason for the failure : [chars]
Error Message IVR-3-MERGE_ACTIVATION_FAILED: [chars]
[chars]
Error Message IVR-3-MERGE_FAILED: reason is [chars]
Explanation An error occurred while merging configuration. The reason for the failure : [chars]
Error Message IVR-3-MTS_ERROR: MTS message transmission failed with error [dec]
Explanation IVR process unsuccessfully tried to send a MTS message. MTS error number is
specified in [dec].
Error Message IVR-3-NS_ERROR: FCNS API, [chars], failed with error [hex]
Explanation IVR invoked FCNS API and received the error code. [chars] describes the API and
OL-26589-01 2-267
Error Message IVR-3-PSS_CFG_RESTORE_ERROR: Configuration restoration for [chars]

failed with error [hex]
Explanation IVR read the saved configuration and encountered an error while rebuilding the runtime
configuration. [chars] describes the configuration which the process tried to restore and 0x[hex] is
the system err code.
Error Message IVR-3-PSS_ERROR: PSS operation [chars] returned error: [hex]
Explanation [chars] specifies the context where the failure occurred and 0x[hex] specifies the error.
Error Message IVR-3-PSS_RTDB_RESTORE_ERROR: Runtime database restoration for

Explanation IVR read the saved runtime database and encountered an error while rebuilding the
runtime database. [chars] describes the runtime database which the process tried to restore and
0x[hex] is the system error code.
Error Message IVR-3-QOS_IOD_UNDROP_REQUEST_TO_ACL_FAILED: qos iod undrop request

vsan [dec] did [chars] failed:[chars].
Error Message IVR-3-RIB_ERROR: RIB API, [chars], failed with error [hex]
Explanation IVR invoked RIB API and received the error code. [chars] describes the API and
Error Message IVR-3-ROUTE_REQUEST_TO_ACL_FAILED: route [chars] request vsan [dec]

domain [dec] failed:[chars].
2-268 OL-26589-01
Error Message IVR-3-TOPOLOGY_COMPUTATION_FAILED: Inter-VSAN Topology computation

has failed due to: [chars]
Explanation Inter-VSAN Topology has failed due to [chars]. Possible reasons are (a) Number of
AFID/VSAN combination is more than te maximum supported value of 128, or (b) Number of
ivr-enabled switches is more than the maximum supported value of 128
Error Message IVR-3-UNEXPECTED_MTS_MSG: Unexpected MTS message, opcode [dec], is

received
Explanation IVR process received unexpected MTS event. MTS opcode is specified in [dec].
Error Message IVR-3-UNLOCK_FAILED: [chars]
Explanation An error occurred while releasing the lock. The reason for the failure : [chars]
Error Message IVR-3-VSAN_SEGMENTED: [chars]
ExplanationVSAN is segmented. VSAN is removed from the topology graph and hence no
Inter-VSAN traffic can flow through this VSAN.
Error Message IVR-3-ZS_POLICY_IS_DENY_NO_ACTIVE_ZS: Default zone behavior policy

is deny on VSAN [dec] and there is no active zoneset
Explanation Default zone behavior is deny and there is no active zoneset. Inter-VSAN zone
members may not be able communicate in this VSAN.
Error Message IVR-3-ZS_POLICY_IS_PERMIT_NO_FORCE: Default zone behavior policy is

permit on VSAN [dec] and the force option is off
Explanation Default zone behavior is permit and the force option is off. Inter-VSAN zoneset
activation on this VSAN has failed.
OL-26589-01 2-269
Error Message IVR-3-ZS_POLICY_IS_PERMIT_ZS_DEACTIVATED: Default zone behavior

policy is permit on VSAN [dec] and regular zoneset deactivated
Explanation Default zone behavior is permit and regular zoneset is deactivated. Inter-VSAN zone
members may not be able to communicate.
IVR-4
Error Message IVR-4-AUTO_TOPOLOGY_UPDATE_DISCARDED: [chars]
Explanation Received auto topology update is discarded due to conflicts
Error Message IVR-4-FCID_REWRITE_REQUEST_TO_ACL_FAILED_AND_RETRYING: fcid rewrite

[chars] request vsan [dec] did [chars] sid [chars] failed:[chars]([hex]). Retrying
the request again.
Explanation This happens when either any of the linecards being upgraded or ACL experienced
Error Message IVR-4-PERSISTENT_VIRTUAL_DOMAIN_MERGE_CONFLICT: [chars]
Explanation Merge failed due to conflict in the persistent virtual domain configuration
Error Message IVR-4-IVR_VDC_FORCEFUL_CLEANUP: IVR was removed with VDC

delete/reload/suspend, Forceful cleanup was triggered.
Explanation IVR was removed from an N7K switch via VDC delete/reload, which triggered a
forceful cleanup.
Error Message IVR-4-IVR_REMOVED_PENDING_CFG: IVR was removed while there were still
pending IVR configurations. Forceful cleanup was triggered and the pending
configurations were not saved.
Explanation IVR was removed from an N7K switch via VDC delete/reload, which triggered a
forceful cleanup. The pending IVR configurations were not saved.
2-270 OL-26589-01
Error Message IVR-4-PERSISTENT_VIRTUAL_FCID_MERGE_CONFLICT: [chars]
Explanation Merge failed due to conflict in the persistent virtual fcid configuration
Error Message IVR-4-QOS_IOD_UNDROP_REQUEST_TO_ACL_FAILED_AND_RETRYING: qos iod

undrop request vsan [dec] did [chars] failed:[chars]. Retrying the request again.
Error Message IVR-4-ROUTE_REQUEST_TO_ACL_FAILED_AND_RETRYING: route [chars]

request vsan [dec] domain [dec] failed:[chars]. Retrying the request again.
Error Message IVR-4-UNKNOWN_NATIVE_VSAN: Unknown native VSAN for the virtual domain
[dec] in VSAN [dec] local native VSAN for the same virtual domain is [dec]
Explanation Could not determine native VSAN of the currently advertised virtual domain [dec] in
VSAN [dec]. This switch has learned of a device that is member of active IVR zone has the same
domain ID, and belongs to native VSAN [dec]. This device would not be advertised in that VSAN
until the native VSAN information is resolved.
IVR-5
Error Message IVR-5-AAM_MODE_DEREGISTERED: Abstract ACL Manager (AAM) mode has been
deregistered
Explanation Abstract ACL Manager (AAM) mode has been deregistered
Error Message IVR-5-AAM_MODE_REGISTERED: Abstract ACL Manager (AAM) mode has been
registered
Explanation Abstract ACL Manager (AAM) mode has been registered
OL-26589-01 2-271
Error Message IVR-5-FCID_NAT_MODE_ACTIVATED: FCID network address translation

(NAT) mode has been activated
Explanation FCID network address translation (NAT) mode has been activated
Error Message IVR-5-FCID_NAT_MODE_DEACTIVATED: FCID network address translation

(NAT) mode has been deactivated
Explanation FCID network address translation (NAT) mode has been deactivated
Error Message IVR-5-IVR_ASSERTION_FAILED: Unexpected assertion failure in File

[chars] at Line [dec]
Explanation An assertion failed in IVR code
Error Message IVR-5-IVZS_ACTIVATION_RETRYING: Inter-VSAN zoneset activation did

not go through because of [chars], retrying in VSAN [dec] after [dec] seconds
Explanation Inter-VSAN zoneset activation failed because of [chars] in VSAN [dec]. This could be
an intermittent regular zoneset activation error. The activation will be retried in [dec] seconds.
Error Message IVR-5-IVZS_WAITING_FOR_LOWEST_SWWN: Waiting for lowest switch WWN

Inter-VSAN enabled switch in VSAN [dec]
Explanation Only lowest switch WWN Inter-VSAN enabled switch adds the Inter-VSAN zones to
the regular active zoneset in a VSAN. This local switch is not the lowest sWWN switch in VSAN
[dec]
Error Message IVR-5-IVZ_ACTIVATED_VSAN: Inter-VSAN zoneset [chars] activated in

VSAN [dec]
Explanation Inter-VSAN zoneset activated in VSAN[dec].
Error Message IVR-5-IVZ_ACTIVATED: Inter-VSAN zoneset [chars] activated
Explanation Inter-VSAN zoneset activated[dec].
2-272 OL-26589-01
Error Message IVR-5-IVZ_CLEANUP_DONE_BY_TIMER: Inter-VSAN clean-up is not done

after waiting for 5 minutes
Explanation Inter-VSAN related configuration might not be cleaned up before the ivr process is
terminated
Recommended Action If the problem persists, you may have to reboot your switch to clean up the old
IVR configuration
Error Message IVR-5-IVZ_CLEANUP_DONE: Inter-VSAN clean-up is done
Explanation Inter-VSAN related configuration is cleaned up before exiting.
Error Message IVR-5-IVZ_DEACTIVATED_VSAN: Inter-VSAN zoneset [chars] deactivated

in VSAN [dec]
Explanation Inter-VSAN zoneset deactivated in VSAN[dec].
Error Message IVR-5-IVZ_DEACTIVATED: Inter-VSAN zoneset [chars] deactivated
Explanation Inter-VSAN zoneset deactivated[dec].
Error Message IVR-5-IVZ_PARTIALLY_ACTIVATED: Inter-VSAN zoneset [chars] partially

activated
Explanation Inter-VSAN zoneset activated[dec].
Recommended Action Check if it is successful in all VSANs by doing show IVR zoneset status.
Error Message IVR-5-IVZ_PARTIALLY_DEACTIVATED: Inter-VSAN zoneset [chars]

partially deactivated
Explanation Inter-VSAN zoneset deactivated[dec].
Recommended Action Check if it is successful in all VSANs by doing show IVR zoneset status.
Error Message IVR-5-LICENSE_CHECKIN_FAILED: Failed to checkin [chars] license:

Err=[chars]
Explanation Failed to checkin [chars] license
OL-26589-01 2-273
Error Message IVR-5-SERVICE_GROUP_ACTIVATED: Inter-VSAN Service Group has been

activated
Explanation Inter-VSAN Service Group has been activated.
Error Message IVR-5-SERVICE_GROUP_DEACTIVATED: Inter-VSAN Service Group has been

deactivated
Explanation Inter-VSAN Service Group has been deactivated.
Error Message IVR-5-VSAN_NO_LONGER_SEGMENTED: [chars]
Explanation VSAN is no longer segmented. VSAN is added back to the topology graph and hence
Inter-VSAN traffic can now flow through this VSAN.
Error Message IVR-5-VSAN_TOPOLOGY_ACTIVATED: Inter-VSAN Topology has been

activated
Explanation Inter-VSAN Topology has been activated.
IVR-6
Error Message IVR-6-DRAV_ASYNC_DOMAIN_RELEASE: [chars]
Explanation DRAV FSM has unconditionally released a domain due to conflict after a fabric merge.
The details are in [chars]
Error Message IVR-6-DRAV_CRITICAL_RETRY_EXCEED: [chars]
Explanation DRAV FSM frames are attempted to be resent. The details are in [chars]
2-274 OL-26589-01
Error Message IVR-6-DRAV_DOMAIN_ALLOC: Virtual domain [dec] for Native AFID: [dec]
Native VSAN [dec]
Explanation A virtual domain indicated by [dec] has been reserved for a device with native AFID
[dec] and native VSAN [dec]
Error Message IVR-6-DRAV_DOMAIN_RELEASE: Virtual domain [dec] for Native AFID:

[dec] Native VSAN [dec]
Explanation A virtual domain indicated by [dec] has been released used by devices with native
AFID [dec] and native VSAN [dec]
Error Message IVR-6-DRAV_TOPO_UPDATE: [chars]
Explanation DRAV FSM Topology has been updated as indicated by [chars]
Error Message IVR-6-LICENSE_VALID: A valid license for Inter-VSAN Routing has been
obtained
Explanation A valid license for Inter-VSAN Routing has been obtained
IVR-7
Error Message IVR-7-CFS_REQ_RCVD: [chars]
Explanation CFS request is received. The WWN of the switch originated this request and the
rr-token of the request are provided in the syslog message.
Error Message IVR-7-CFS_RESP_SENT: [chars]
Explanation CFS response is sent. The rr-token of the corresponding request and the status are
provided in the syslog message
L2FMC Messages
This section contains the L2FMC messages.
OL-26589-01 2-275
L2FMC-SLOT#-0
Error Message L2FMC-SLOT#-0-L2FMC_CLI_INIT_FAILED: CLI library initialization

failed!
Explanation L2FMC failed to initialize CLI infrastructure's backend library. This is a fatal error.
Error Message L2FMC-SLOT#-0-L2FMC_TIMER_INIT_FAILED: Timer subsystem

initialization failed!
Explanation L2FMC failed to initialize timer library. This is a fatal error.
L2FMC-SLOT#-2
Error Message L2FMC-SLOT#-2-L2FMC_MEM_ALLOC: Memory allocation failed. [chars]
Error Message L2FMC-SLOT#-2-L2FMC_VLAN_NOT_FOUND: VLAN [dec] not found in L2FMC

database!
Explanation L2FMC failed to find VLAN [dec] in its database. L2 MAC learning & aging on VLAN
[dec] may be affected.
L2FMC-SLOT#-5
Error Message L2FMC-SLOT#-5-L2FMC_GLBL_AGE_CONFIG_FAIL: Global age value

configuration to [dec] seconds failed!
Explanation L2FMC failed to configure global default age to [dec] seconds.
Error Message L2FMC-SLOT#-5-L2FMC_VLAN_AGE_CONFIG_FAIL: VLAN Age configuration to

[dec] seconds failed!
Explanation L2FMC failed to configure age for VLAN [dec] to [dec] seconds.
2-276 OL-26589-01
L2FMC-SLOT#-6
Error Message L2FMC-SLOT#-6-L2FMC_GLBL_AGE_CONFIGURED: Global age value configured

to [dec] seconds.
Explanation L2FMC has successfully configured global default age to [dec] seconds.
Error Message L2FMC-SLOT#-6-L2FMC_INITIALIZED: Internal state created [chars]
Explanation L2FMC has created its internal state stateless/stateful [chars].
Error Message L2FMC-SLOT#-6-L2FMC_VDC_CREATED: VDC [dec] created
Explanation Request to create VDC [dec] in L2FMC was successful.
Error Message L2FMC-SLOT#-6-L2FMC_VDC_REMOVED: VDC [dec] Removed
Explanation L2FMC has successfully removed VDC [dec] from its databases.
Error Message L2FMC-SLOT#-6-L2FMC_VDC_VLAN_CREATED: VLAN [dec] created
Explanation L2FMC has added VLAN [dec].
Error Message L2FMC-SLOT#-6-L2FMC_VDC_VLAN_REMOVED: VLAN [dec] removed from VDC

[dec]
Explanation L2FMC has successfully removed VLAN [dec] from VDC [dec].
Error Message L2FMC-SLOT#-6-L2FMC_VLAN_AGE_CONFIGURED: Age configured for VLAN

[dec] to [dec] seconds.
Explanation L2FMC has successfully configured age for VLAN [dec] to [dec] seconds.
OL-26589-01 2-277
L2FM Messages
This section contains the L2FM messages.
L2FM-0
Error Message L2FM-0-L2FM_CLI_INITIALIZATION_FAILED: CLI library initialization

failed!
Explanation Failed to initialize CLI infrastructure's backend library. This is a fatal error.
Error Message L2FM-0-L2FM_VDC_GWMAC_GET_FAILED: Failed to get gwmac for VDC
Explanation Failed to get gwmac for VDC.
Error Message L2FM-0-L2FM_WRITE_TO_PSS_FAILED_IN_PREVIOUS_INCARNATION: PSS Write

Failed in pervious incarnation. Stateful restart not possible
Explanation PSS Write Failed in pervious incarnation. Stateful restart not possible
L2FM-1
Error Message L2FM-1-L2FM_CRDCFG_ERROR: L2fm queried Card config for slot info and
it has returned error. The slot may not have been added correctly
Recommended Action L2fm
Error Message L2FM-1-L2FM_LINE_FULL_CONDITION_STRING: Unable to insert the MAC as

hardware lines are full
2-278 OL-26589-01
Error Message L2FM-1-L2FM_LINE_FULL_CONDITION: Unable to insert the MAC as hardware

lines are full
Error Message L2FM-1-L2FM_ORIB_SENDS_INCORRECT_IFIDX: Incorrect ifidx received

from Orib. Please check mac [chars] vlan [dec]
Explanation L2fm has received a mac insert/delete from Orib with incorrect ifidx. Please check otv
mac entries
Error Message L2FM-1-L2FM_OWNER_NOT_FOUND: Error : fe owner not found for mac entry
[chars] in age notif sent from slot = [dec], fe = [dec]
Explanation L2fm has received an age notification from the linecard but does not have the mac
owner in its database
Error Message L2FM-1-L2FM_SDB_NOT_FLUSHED: Error : [dec] mac entries have not

flushed from l2fm sdb
Explanation Due to an internal error l2fm has not written mac entries to its sdb
Error Message L2FM-1-L2FM_SMAC_DUP_FOUND: Duplicate static mac found in secondary

vlan. P-VLAN:[dec] S-VLAN:[dec] MAC:[chars]
Explanation Duplicate static mac found in secondary vlan. P-VLAN:[dec] S-VLAN:[dec]

MAC:[chars]
Error Message L2FM-1-L2FM_WRITE_TO_PSS_FAILED: Failed to write to PSS err [chars]
Explanation Failed to write to PSS err [chars]
OL-26589-01 2-279
L2FM-2
Error Message L2FM-2-L2FM_AGING_TIME_SET_FAILED: Failed to set age time [dec] for

vlan [dec]
Explanation Failed to set age time [dec] for vlan [dec].
Error Message L2FM-2-L2FM_CFS_OUT_OF_ORDER: Error: Received Message for STATIC MAC

INSERT/DELETE as Out Of Order from vpc peer due to congestion. Please check mac
programming for Router macs.Flap interface-vlans if necessary to correct the
programming
Explanation Messages over peer-link could be received out of order due to congestion
Error Message L2FM-2-L2FM_GLBL_AGING_TIME_SET_FAILED: Failed to set global age time

[dec]
Explanation Failed to set global age time [dec]
Error Message L2FM-2-L2FM_SMAC_INS_FAILED: Failed to insert static mac for

VLAN:[dec] MAC:[chars] IfIndex:[hex] Slot:[dec]
Error Message L2FM-2-L2FM_UPDATE_LOST_HINTS: mac

[hex]:[hex]:[hex]:[hex]:[hex]:[hex] updated by slot [dec] fe_index [dec], from
[hex] to [hex], with [hex] new hints and loosing %08 old_hints. stack trace:
[chars]
Explanation An update from MTM looks inconsistent with the previous state
L2FM-4
Error Message L2FM-4-L2FM_MAC_MOVE: Mac [chars] in vlan [dec] has moved from [chars]
to [chars]
Explanation Mac [string] in vlan [dec] has moved from [string] to [string]
2-280 OL-26589-01
L2FM-5
Error Message L2FM-5-L2FM_VLAN_MODE_CHANGE_TO_NON_CONV: Vlan [dec] has been

internally changed to non conversational mode on SVI CREATE
Explanation Change vlan learning mode to non conversational mode on SVI CREATE
Error Message L2FM-5-L2FM_VLAN_MODE_REVERTED_BACK: Vlan [dec] has been internally

changed to user configured learning mode on SVI DELETE. Mac entries installed
non-optimally due to SVI up will get removed from all FEs once ages out
Explanation Change vlan learning mode to user configured value on SVI DELETE
L2FM-6
Error Message L2FM-6-L2FM_DYN_MAC_INS_FAILED: Dynamic mac insertion

failure!fail_cnt: [dec] Slot:[dec]
Explanation Failed to insert dynamic macs fail_cnt:[dec] for Slot:[Slot]
Error Message L2FM-6-L2FM_MTS_SEND_FAILED: Failed to send MTS message errno [hex]

opcode [dec]
L2MCAST Messages
This section contains the L2MCAST messages.
L2MCAST-SLOT#-0
Error Message L2MCAST-SLOT#-0-L2MCAST_CLI_INIT_FAILED: CLI library initialization

failed!
Explanation L2MCAST failed to initialize CLI infrastructure's backend library. This is a fatal error.
OL-26589-01 2-281
Error Message L2MCAST-SLOT#-0-L2MCAST_TIMER_INIT_FAILED: Timer subsystem

initialization failed!
Explanation L2MCAST failed to initialize timer library. This is a fatal error.
L2MCAST-SLOT#-2
Error Message L2MCAST-SLOT#-2-L2MCAST_MAC_FULL_LC: Failed to insert entry in MAC

table for FE [dec] swidx [dec] ([hex]) with err ([chars]). To avoid possible
multicast traffic loss, disable OMF. Use the configuration CLI: "no ip igmp
snooping optimise-multicast-flood"
Explanation Failed to program the MAC table. MAC table line full for this entry
Error Message L2MCAST-SLOT#-2-L2MCAST_VLAN_NOT_FOUND: VLAN [dec] not found in

L2MCAST database!
L2MCAST failed to find VLAN [dec] in its database. L2 MAC learning & aging on
Explanation
VLAN [dec] may be affected.
Error Message L2MCAST-SLOT#-2-L2MCAST: Memory allocation failed. [chars]
L2MCAST-SLOT#-3
Error Message L2MCAST-SLOT#-3-L2MCAST_HW_INSTALL_FAIL: Hw install failed for vlan

[dec] ([dec], [chars], [chars]) entry!
Explanation L2MCAST failed to insert bd, g, s entry in hardware. Igmp snooping may not be
effective on vlan for that group and source
2-282 OL-26589-01
L2MCAST-SLOT#-6
Error Message L2MCAST-SLOT#-6-L2MCAST_HW_INSTALL_FAIL: Hw install failed for vlan

[dec] ([dec], [chars], [chars]) entry!
Explanation L2MCAST failed to insert bd, g, s entry in hardware. Igmp snooping may not be
effective on vlan for that group and source
Error Message L2MCAST-SLOT#-6-L2MCAST_INITIALIZED: Internal state created [chars]
Explanation L2MCAST has created its internal state stateless/stateful [chars].
Error Message L2MCAST-SLOT#-6-L2MCAST_VDC_CREATED: VDC [dec] created
Explanation Request to create VDC [dec] in L2MCAST was successful.
Error Message L2MCAST-SLOT#-6-L2MCAST_VDC_REMOVED: VDC [dec] Removed
Explanation L2MCAST has successfully removed VDC [dec] from its databases.
Error Message L2MCAST-SLOT#-6-L2MCAST_VDC_VLAN_CREATED: VLAN [dec] created
Explanation L2MCAST has added VLAN [dec].
Error Message L2MCAST-SLOT#-6-L2MCAST_VDC_VLAN_REMOVED: VLAN [dec] removed from

VDC [dec]
Explanation L2MCAST has successfully removed VLAN [dec] from VDC [dec].
L3VM Messages
This section contains the L3VM messages.
OL-26589-01 2-283
L3VM-5
Error Message L3VM-5-FP_TPG_CREATE: Fabricpath topology [dec] created
Explanation FP-Topology created
Error Message L3VM-5-FP_TPG_DELETE: Fabricpath topology [dec] deleted
Explanation FP-Topology deleted
Error Message L3VM-5-FP_TPG_INTF_DOWN: Interface [chars] down in fabricpath

topology [dec] [chars]
Explanation Interface in a FP-Topology went down
Error Message L3VM-5-FP_TPG_INTF_UP: Interface [chars] up in fabricpath topology

[dec]
Explanation Interface in a FP-Topology is up
LACP Messages
This section contains the LACP messages.
LACP-3
Error Message LACP-3-GENERAL_ERROR: [chars]
Error Message LACP-3-LACP_SUSPEND_HALF_DUPLEX_PORT: Port [chars] is in half duplex

mode. suspend port
Explanation LACP is not supported in half duplex mode. Suspend port
2-284 OL-26589-01
Error Message LACP-3-LACP_SUSPEND_MINLINK: LACP port [chars] of port-channel

[chars] is suspended as min-link requirement not met.
Explanation LACP suspend ports due to min-link
Error Message LACP-3-LACP_UPGRADE_READY_FAILED: Upgrade ready failed.
Explanation Upgrade ready event failed because atleast one port channel member is in intermediate
state.
Error Message LACP-3-PACKET_TRANSMIT_ERR: [chars]: Could not send LACP packet

err=[dec]
Explanation There was an error in sending LACP packet
Error Message LACP-3-SYN_COLL_DIS_EN: [chars] [[chars]]: SYNC, COLLECT and

DISTRIBUTE flags enabled too early by partner
Explanation Potential interop issue. Partner system seems to have enabled sync as well collecting
or distributing flags too early even before actor has selected an aggregator
Error Message LACP-3-SYSTEM_MAC_ERR: [chars]: Could not get system mac[[chars]]
Explanation There was an error in acquiring system mac from VDC Mgr
LACP-5
Error Message LACP-5-LACP_DISABLED: LACP Disabled
Explanation LACP Service Disabled
Error Message LACP-5-LACP_DOES_NOT_MEET_MINLINK_REQ: LACP port-channel [chars] is

brought down as min-link requirement not met.
Explanation LACP port-channel down as min-link requirement not met
OL-26589-01 2-285
Error Message LACP-5-LACP_ENABLED: LACP Enabled
Explanation LACP Service Enabled
Error Message LACP-5-LACP_MEETS_MINLINK_REQ: LACP port-channel [chars] meets

min-link requirement. Reint port-channel
Explanation LACP port-channel meets min-link requirement
Error Message LACP-5-LACP_REMOTE_NOTIFY_SUCCESS: Remote notify event.
Explanation Remote notify event was successful.
Error Message LACP-5-LACP_SUSPEND_INDIVIDUAL: LACP port [chars] of port-channel

[chars] not receiving any LACP BPDUs suspending (individual) port
Explanation LACP suspend individual ports
Error Message LACP-5-LACP_UPGRADE_READY_SUCCESS: Upgrade ready successful.
Explanation Upgrade ready event is successful as all port channel members are in steady state.
Error Message LACP-5-PORT_PRIORITY_CHANGED: [chars]: LACP port priority changed from

[dec] to [dec]
Explanation LACP port priority has been changed
Error Message LACP-5-SYSTEM_PRIORITY_CHANGED: LACP system priority changed from

[hex] to [hex]
Explanation LACP system priority has been changed
2-286 OL-26589-01
LC-FCFWD Messages
This section contains the LC-FCFWD messages.
LC-FCFWD-3
Error Message LC-FCFWD-3-ERROR: [chars]
Explanation Lc_fcfwd encountered an error
LC-SPAN Messages
This section contains the LC-SPAN messages.
LC-SPAN-3
Error Message LC-SPAN-3-ERROR: [chars]
Explanation Lc_span_mgr encountered an error
LC_CFG Messages
This section contains the L2_CFG messages.
LC_CFG-SLOT#-2
Error Message LC_CFG-SLOT#-2-LC2_CPU_ERRORS: [chars], Total IC [dec], DC [dec],

Tag [dec], MBit [dec], SBit [dec], I30 [dec]
Explanation LC CPU Cache errors.
Error Message LC_CFG-SLOT#-2-LC_CFG_ABORT: registration aborted with code [dec]
Explanation Process lc_cfg_mgr aborted registration
OL-26589-01 2-287
Error Message LC_CFG-SLOT#-2-LC_CFG_EXITED: exited with code [dec]
Explanation Process lc_cfg_mgr exited
LC_PORT_CHANNEL Messages
This section contains the LC_PORT_CHANNEL messages.
LC_PORT_CHANNEL-SLOT#-0
Error Message LC_PORT_CHANNEL-SLOT#-0-HW_FAILURE: fatal error in configureing

[chars]: [chars]
Explanation Fatal hardware error in port-channel configuration
Recommended Action Reset the module
Error Message LC_PORT_CHANNEL-SLOT#-0-IDX_FULL: D_IDX table full (current [dec],

new [dec], total [dec])
Explanation Programming error in port-channel configuration
Recommended Action Reset the module
LC_PORT_CHANNEL-SLOT#-3
Error Message LC_PORT_CHANNEL-SLOT#-3-LC_PORT_CHANNEL_ERROR: [chars]
Error Message LC_PORT_CHANNEL-SLOT#-3-LC_PORT_CHANNEL_IDXMAP_FAILURE: could not

lookup port index for interface [chars]
Explanation Could not look up port index
LC_PORT_MGR Messages
This section contains the LC_PORT_MGR messages.
2-288 OL-26589-01
LC_PORT_MGR-SLOT#-2
Error Message LC_PORT_MGR-SLOT#-2-LC_MTS_ERROR: An MTS error has occurred in

([chars]) with the following conditions: opc=[dec] ssap=[hex] dsap=[hex]
syserr=[hex]
Explanation This is a software error in message communication between two applications.
LC_RDL Messages
This section contains the LC_RDL messages.
LC_RDL-3
Error Message LC_RDL-3-SYSLOG_ALLOC_FAIL: : [chars]
Explanation RDL malloc failed : [chars]
Error Message LC_RDL-3-SYSLOG_CONTEXT_ERR: : [chars] [dec]
Explanation RDL context error: [chars] [dec]
Error Message LC_RDL-3-SYSLOG_ERR: : [chars]
Explanation RDL syslog errors : [chars]
Error Message LC_RDL-3-SYSLOG_EXIT: : [chars]
Explanation RDL exiting on errors : [chars]
Error Message LC_RDL-3-SYSLOG_INIT_FAIL: : [chars] [chars]
Explanation RDL Init Failed: [chars] [chars]
OL-26589-01 2-289
Error Message LC_RDL-3-SYSLOG_MTS_ERR: : [chars]
Explanation RDL MTS errors : [chars]
Error Message LC_RDL-3-SYSLOG_MTS_REG_FAILED: : [dec] [dec]
Explanation RDL context error: [dec] [dec]
LC_RDL-6
Error Message LC_RDL-6-SYSLOG_DEBUG_1: : [chars] [hex]
Explanation RDL Debug logs: [chars] [dec]
Error Message LC_RDL-6-SYSLOG_DEBUG_2: : [chars] [hex]
Explanation RDL Debug logs: [chars] [dec]
Error Message LC_RDL-6-SYSLOG_INFO: : [chars]
Explanation RDL Debug logs: [chars]
Error Message LC_RDL-6-SYSLOG_RESP_RCVD: : [chars] [dec]
Explanation RDL context error: [chars] [dec]
LDAP Messages
This section contains the LDAP messages.
2-290 OL-26589-01
LDAP-2
Error Message LDAP-2-LDAP_PROGRAM_EXIT: LDAP daemon exiting: [chars]
Explanation LDAP daemon is exiting.
LDAP-3
Error Message LDAP-3-LDAP_ERROR_MESSAGE: [chars]
Explanation LDAP Error Message
LDAP-5
Error Message LDAP-5-LDAP_MONITOR_STATUS: [chars] [chars]
Explanation Notifying Ldap server monitor status change
Error Message LDAP-5-LDAP_SERVER_STATUS: [chars] server [chars] with port [dec]

status has changed from [chars] to [chars]. Server was in previous-state for
[chars], and total dead time of the server is [chars]
Explanation Notifying Ldap server status change
LDAP-6
Error Message LDAP-6-LDAP_MESSAGE: [chars]
Explanation LDAP Message
OL-26589-01 2-291
LDP Messages
LDP-5
Error Message LDP-5-LDP_DISABLED: LDP Disabled
Explanation MPLS_LDP Service Disabled
Error Message LDP-5-LDP_ENABLED: LDP Enabled
Explanation MPLS_LDP Service nabled
LIBBASE_SVC Messages
This section contains the LIBBASE_SVC messages.
LIBBASE_SVC-2
Error Message LIBBASE_SVC-2-IT_NEXUS_MAX_INTERFACE_LIMIT_REACHED: [chars] cannot

be bound for site [chars], as the interfaces reached the maximum flow limit
Explanation IT Load Balancing failed
Error Message LIBBASE_SVC-2-LOG_ERR_BASE_SVC_TOM_ABORTED: SME Cluster [chars]

Message Id: [hex] aborted
Explanation An SME Cluster Message was aborted by the Cluster process
LIBBASE_SVC-4
Error Message LIBBASE_SVC-4-FCR_VER2_NOT_ENABLED: FCR Version2 is not enabled. May

affect flows. Please enable fc-redirect version2
Explanation FCR Version2 not enabled
2-292 OL-26589-01
LIBBASE_SVC-5
Error Message LIBBASE_SVC-5-FLOW_NOT_ALLOWED: Flow [chars] <-
Explanation Flow creation failed
Error Message LIBBASE_SVC-5-IT_NEXUS_FAILURE: [chars]. [chars] bind failure.

Reason: [chars]: [hex]
Explanation IT Nexus bind failed
Error Message LIBBASE_SVC-5-IT_NEXUS_OPTIMUM_INTERFACE_LIMIT_REACHED: Interface

[chars] exceeded the optimum flow limit
Explanation Iterface Flow Limit
LIBGD Messages
This section contains the LIBGD messages.
LIBGD-2
Error Message LIBGD-2-GD_ACCESS_FAILED: Guardian Failed to access reg for [chars]
Explanation Guardian Access failed
Error Message LIBGD-2-GD_CATASTROPHIC: Guardian catastrophic failure: [chars]
Explanation Guardian catastrophic error
Error Message LIBGD-2-GD_INTR: Guardian Interrupt occurred: [chars]
Explanation Interrupt occurred on the Guardian
OL-26589-01 2-293
Error Message LIBGD-2-SHUTDOWN: Guardian software process exiting: [chars]
Explanation Guardian shutting down
LIBGD-3
Error Message LIBGD-3-EN_DATA_FAILED: Guardian enable port failed for inst:[dec]

port:[dec]
Explanation Guardian Enable port failed for the guardian
LIBGD-5
Error Message LIBGD-5-STARTING: Guardian process starting
Explanation Guardian process is being started
LIBGD-6
Error Message LIBGD-6-DIS_DATA: Guardian disable port done for inst:[dec]

port:[dec]
Explanation Disabled port successfully for guardian
Error Message LIBGD-6-EN_PORT: Guardian enable port done for inst:[dec] port:[dec]
Explanation Enabled port for the Guardian
Error Message LIBGD-6-HW_INIT: GuardianHW initialization has been done for inst:
[dec] port: [dec]
Explanation Guardian HW initializtion has been called[dec]
2-294 OL-26589-01
LICMGR Messages
This section contains the LICMGR messages.
LICMGR-0
Error Message LICMGR-0-LOG_LIC_GRACE_EXPIRED: Grace period expired for feature

[chars].
Explanation Unlicensed feature [chars] has exceeded

itsgracetimeperiod.Applicationsusingwillbeshutdownimmediately.'
LICMGR-1
Error Message LICMGR-1-LOG_LIC_LICENSE_EXPIRED: Evaluation license expired for

feature [chars].
Explanation The named feature has exceeded

itsevaluationtimeperiod.Applicationsusingthelicensewillbeshutdownafteragraceperiod.'
Error Message LICMGR-1-LOG_LIC_LICENSE_EXPIRY_WARNING_ALERT: Evaluation license

for feature [chars] will expire in [dec] days.
Explanation Feature [chars] has very limited time for expiry. Feature will expire in [dec] days and
will be shut down.
Error Message LICMGR-1-LOG_LIC_NO_LIC_ALERT: No license(s) present for feature

[chars]. Application(s) running in grace-period and will be shut down in [dec]
days.
Explanation Feature [chars] has not been licensed. The feature will work for a grace period of [dec]
days after which application(s) using the feature will be shut down.
OL-26589-01 2-295
LICMGR-2
Error Message LICMGR-2-LOG_LICAPP_EXPIRY_WARNING: Application [chars] evaluation

license [chars] expiry in [dec] days.
Explanation Application [chars1] will exceed

itsevaluationtimeperiodin[dec]daysandwillbeshutdownafteragraceperiodunlessapermanentlicensef
orfeature[chars2]isinstalled.'
Error Message LICMGR-2-LOG_LICAPP_NO_LIC: Application [chars] running without

[chars] license, shut down in [dec] days.
Explanation Application [chars1] has not been licensed. The application will work for a grace period
of [dec] days after which it will be shut down unless a license file for feature [chars2] is installed.
Error Message LICMGR-2-LOG_LIC_EXIT: License manager exiting: [chars]
Explanation License manager exiting.
Error Message LICMGR-2-LOG_LIC_INVALID_SERVER_LINE: License file [chars] contains

invalid "SERVER" line. Contact TAC
Explanation Invalid SERVER line in license file.
Error Message LICMGR-2-LOG_LIC_NO_LIC: No license(s) present for feature [chars].

Application(s) shut down in [dec] days.
Explanation Feature [chars] has not been licensed. The feature will work for a grace period of [dec]
days after which application(s) using the feature will be shut down.
2-296 OL-26589-01
Error Message LICMGR-2-LOG_LIC_NVRAM_DISABLED: Licensing NVRAM is not available.

Grace period will be disabled: [chars]
Explanation The Supervisor NVRAM block may have a hardware problem and may need to be
replaced
Error Message LICMGR-2-LOG_LIC_VENDOR_DOWN: License file contains invalid "SERVER"

line. Vendor daemon down
Explanation Vendor daemon is down
Recommended Action Licensing
LICMGR-3
Error Message LICMGR-3-LOG_LIC_FILE_MISSING: License file(s) missing for feature

[chars].
Explanation One or more license files for feature [chars] are missing and must be reinstalled.
Error Message LICMGR-3-LOG_LIC_INVALID_HOSTID: Invalid license hostid VDH=[chars]

for feature [chars].
Explanation Feature [chars2] has a license with an invalid license hostid VDH=[chars1]. This can
occur if a supervisor card with licensed features for one switch is installed on another switch.
Error Message LICMGR-3-LOG_LIC_MESSAGE_ERROR: could not handle message: [chars] of

type [dec] from addr [dec]:[dec].
Explanation Could not handle a IPC message [chars] of type [dec1] sent by a component running on
node [dec2] with sap [dec3].
Error Message LICMGR-3-LOG_LIC_SERVER_DOWN: License Server Down [dec]
Explanation A connection to the license server was lost.
OL-26589-01 2-297
Error Message LICMGR-3-LOG_LIC_SPROM_LIC: Feature [chars] issued [dec] licenses

without a valid license file.
Explanation Feature [chars] has been licensed [dec] times without a valid license file. This means
one or more license files are missing for feature [chars] and must be reinstalled.
Error Message LICMGR-3-LOG_LIC_TOO_MANY_LIC: Only [dec] licenses are supported for

[chars] feature, where as [dec] licenses are installed.
Explanation More licenses are installed than allowed.
LICMGR-4
Error Message LICMGR-4-LOG_LIC_LICENSE_EXPIRY_WARNING: Evaluation license for

feature [chars] will expire in [dec] days.
Explanation Feature [chars] will exceed itsevaluationtimeperiodin[dec]daysandwillbeshutdown.'
LICMGR-6
Error Message LICMGR-6-LOG_CHECKPOINT_CREATED: created during license expiry.
Explanation When a license expires, auto checkpoint is created to prevent configuration loss.
Recommended Action Rollback can be done to the created checkpoint when a new license is installed.
Error Message LICMGR-6-LOG_LIC_FEATURE_CLEARED: Cleared [dec] license(s) for

feature [chars].
Explanation Uninstalled [dec] license(s) for feature [chars].
Recommended Action Use the showlicenseusage'commandtoverifythislicensefeatureremoval.'
Error Message LICMGR-6-LOG_LIC_FEATURE_INSTALLED: Installed [dec] license(s) for

feature [chars].
Explanation Installed [dec] license(s) for feature [chars].
Recommended Action Use the showlicenseusage'commandtoverifythislicensefeatureinstallation.'
2-298 OL-26589-01
Error Message LICMGR-6-LOG_LIC_LICENSE_CLEARED_ALL: Cleared all licenses.
Explanation Cleared all license files.
Error Message LICMGR-6-LOG_LIC_LICENSE_CLEARED: Cleared license file [chars].
Explanation Uninstalled the named license file.
Recommended Action Use the showlicense'commandtoverifythislicenseremoval.'
Error Message LICMGR-6-LOG_LIC_LICENSE_INSTALLED: Installed license file [chars].
Explanation Installed the named license file.
Recommended Action Use the showlicense'commandtoverifythislicenseinstallation.'
LLDP Messages
This section contains the LLDP messages.
LLDP-3
Error Message LLDP-3-DETECT_MULTIPLE_PEERS: Multiple peers detected on [chars]
Explanation Multiple peers detected on an interface
Error Message LLDP-3-INVALID_DCBXP_RECEIVED: Received an invalid DCBXP on [chars]
Explanation Received an invalid DCBXP on an interface
Error Message LLDP-3-INVALID_LLDP_RECEIVED: Received an invalid LLDP on [chars]
Explanation Received an invalid LLDP on an interface
Error Message LLDP-3-LLDP_INTERNAL_ERROR: LLDP internal error: [chars]
Explanation Internal error is encountered
OL-26589-01 2-299
LLDP-5
Error Message LDP-5-LDP_DISABLED: LDP Disabled
Explanation MPLS_LDP Service Disabled
Error Message LDP-5-LDP_ENABLED: LDP Enabled
Explanation MPLS_LDP Service nabled
LLDP-6
Error Message LLDP-6-DETECT_REMOTE_CHANGE: Remote change detected on [chars]
Explanation Remote change detected on an interface
Error Message LLDP-6-DETECT_REMOTE_DCBXP_CHANGE: Remote DCBXP change detected on

[chars]
Explanation Remote DCBXP change detected on an interface
MAC Messages
This section contains the MAC messages.
MAC-SLOT#-2
Error Message MAC-SLOT#-2-MAC_INFO: [chars]
Explanation MAC Informational message
MCAST Messages
This section contains the MCAST messages.
2-300 OL-26589-01
MCAST-2
Error Message MCAST-2-SHUTDOWN: Process shutting down: [chars]
Explanation Mcast is shutting down
Recommended Action The action depends on the situation. The multicast process can shut down
gracefully because of a system restart (in which case no action needs to take place) or because of a
failure. The message associated with the syslog should be self explanatory to understand the reason
for the shutdown. If the process is able to restart properly, there is no immediate harm for the system
stability and the suggested action is to report the syslog event together with an explanation of the
operations most recently performed on the system.
MCAST-4
Error Message MCAST-4-ERROR: [chars]
Explanation Mcast encountered a generic error
MCAST-5
Error Message MCAST-5-BAD_MSG: Received bad message: [chars]
Explanation Mcast has received a malformed/unrecognized message
Error Message MCAST-5-START: Process has been started
Explanation Mcast has been started
MCECTEST Messages
This section contains the MCECTEST messages.
MCECTEST-3
Error Message MCECTEST-3-ASSERTION_FAILED: [chars]
Explanation MCECTEST has hit an assert condition at file [chars]
OL-26589-01 2-301
Error Message MCECTEST-3-INIT_FAIL: [chars]
Explanation MCECTEST Initialization failed. due to [chars]
Error Message MCECTEST-3-INTERNAL_ERR: [chars]
Explanation MCECTEST encountered an internal error due to [chars]
Error Message MCECTEST-3-MTS_ERR: [chars]
Explanation MCECTEST encountered an MTS error due to [chars]
MCECTEST-5
Error Message MCECTEST-5-MCECTEST_DISABLED: MCECTEST Disabled
Explanation MCECTEST Service Disabled
Error Message MCECTEST-5-MCECTEST_ENABLED: MCECTEST Enabled
Explanation MCECTEST Service enabled
MCECTEST-6
Error Message MCECTEST-6-INTERNAL_INFO: [chars]
Explanation MCECTEST got an internal info [chars]
MCM Messages
This section contains the MCM messages.
2-302 OL-26589-01
MCM-2
Error Message MCM-2-MCM_CRITICAL_ERROR: Internal Critical Error
Explanation Some critical error
Error Message MCM-2-MCM_REPLICATION_DISABLED: Proxy layer-3 modules are not

available for replication. Proxy layer-3 multicast replication is disabled.
Explanation Replication is disabled
Error Message No action is required.MCM-2-MCM_REQ_RESP_ERROR: Error ([hex]: [chars])

while communicating with component :[chars], opcode: [chars] (for: [chars])
Explanation Error in request-response handshake
Error Message MCM-2-MCM_ROUTING_DISABLED: Proxy layer-3 modules are not available

for routing. Proxy layer-3 forwarding is disabled.
Explanation Routing is disabled
MCM-5
Error Message MCM-5-MCM_SDB_UPDATE_FAILED: sdb update failed with ret_val [dec]
Explanation SDB updated failed for MCM
MCM-6
Error Message MCM-6-MCM_REPLICATION_ENABLED: Proxy layer-3 modules are UP and

available for replication. Proxy layer-3 multicast replication is enabled.
Explanation Replication is enabled
OL-26589-01 2-303
Error Message MCM-6-MCM_ROUTING_ENABLED: Proxy layer-3 modules are UP and available

for routing. Proxy layer-3 forwarding is enabled.
Explanation Routing is enabled
MFDM Messages
This section contains the MFDM messages.
MFDM-2
Error Message MFDM-2-DI_REUSE: LTL node exists with DI [dec] oiflist_index [dec] type
[dec] and same DI returned for oiflist_index [dec] type [dec] Please collect show
tech-support forwarding distribution l2/l3 multicast and show tech-support pixm.
Explanation PIXM returned duplicate DI.
Error Message MFDM-2-DOWNLOAD_TIMEOUT: Download of L2/L3 route databases timed out

: download_in_progress_slots [hex] for database [chars] [chars] [chars]
Explanation Download of L2/L3 route databases timed out. Download triggered by VMM insert
request.
Error Message MFDM-2-INTERNAL_ERROR: MFDM-[chars] Internal error : show system

internal mfdm errors for more information
Explanation MFDM PD hit a internal error. show system internal mfdm errors for futher analysis.
Error Message MFDM-2-REF_OUTOFSYNC: In Decrement ltl_node ref_count: [dec] is less

than count: [dec] passed in for DI: [hex], oiflist_index: [dec], type: [dec].
Possible PI/PD refcount out-of-sync. Please collect show tech-support forwarding
distribution l2/l3 multicast and show tech-support pixm.
Explanation MFDM PI/PD refcount out-of-sync
2-304 OL-26589-01
Error Message MFDM-2-XID_TAMPERED: Correcting xid in resp - rrtoken:[hex],

req(xid:[dec], rt_cnt:[dec], msg_len:[dec], flag:[dec]), resp(xid:[dec],
rt_cnt:[dec], msg_len:[dec], flag:[dec])
Explanation MFDM tampered xid in OTV response payload
MODULE Messages
This section contains the MODULE messages.
MODULE-2
Error Message MODULE-2-LCM_PRE_UPGRADE_GENERAL_FAIL: Pre upgrade message fails seq

[dec]
Explanation Pre upgrade message failed.
Error Message MODULE-2-LCM_UPGRADE_DONE_GENERAL_FAIL: Upgrade done message fails SAP

[chars]
Explanation Upgrade ready message failed.
Recommended Action Recommended Action No action is required.
Error Message MODULE-2-LCM_UPGRADE_OVER_FAIL: Upgrade over message returned [dec]

[hex] for SAP [dec]
Explanation Upgrade done message failed.
Error Message MODULE-2-LCM_UPGRADE_READY_FAIL: Upgrade ready message returned [dec]

[hex] for SAP [dec]
Error Message MODULE-2-LCM_UPGRADE_READY_GENERAL_FAIL: Upgrade ready message fails

SAP [chars]
OL-26589-01 2-305
Error Message MODULE-2-MOD_DIAG_FAIL: Module [dec] (Serial number: [chars]) reported

failure [chars] due to [chars] in device [chars] (device error [hex])
Explanation The module in slot [decimal digit] reported a failure in the runtime diagnostic. Module
manager is going to power cycle the module.
Recommended Action Collect information about the module by issuing the command 'show module
internal all module [decimal digit]'.
Error Message MODULE-2-MOD_DNLD_FAIL: Image download failed for module [dec] (Serial
number: [chars])
Explanation Module [decimal digit] failed to download a new image from the supervisor.
Error Message MODULE-2-MOD_FAILURE: Re-initializing module [dec] (Serial number:

[chars]) failed. Received lc_failed from sap [hex] failure reason [hex]
Explanation Module [decimal digit] reported a failure during the initialization phase and will be
rebooted.
Recommended Action Collect information about the module by issuing the commands 'show
module_internal all module '.
Error Message MODULE-2-MOD_FAILURE: Re-initializing module [dec] (Serial number:

rebooted.
Recommended Action Collect information about the module by issuing the commands
showmodule_internalallmodule<modulenumber
Error Message MODULE-2-MOD_FAIL: Initialization of module [dec] (Serial number:

[chars]) failed
powered down.
module_internal all module '.
2-306 OL-26589-01
Error Message MODULE-2-MOD_MAJORSWFAIL: Module [dec] (Serial number: [chars])

reported a critical failure in service [chars]
Explanation A critical failure in service [string] happened at module [decimal digit] is going to reset
the module [decimal digit].
Error Message MODULE-2-MOD_MINORSWFAIL: Module [dec] (Serial number: [chars])

reported a failure in service [chars]
Explanation A non-critical failure in service [string] happened at module [decimal digit] is not going
to reset the module [decimal digit].
Error Message MODULE-2-MOD_NOT_ALIVE: Module [dec] not responding... resetting

(Serial number: [chars])
Explanation Module [decimal digit] is not replying to the hello message: module manager is then
going to reset the module.
Error Message MODULE-2-MOD_REGFAILED: Registration failed for module [dec]
Explanation Module [decimal digit] sent the registration message notifying a failure.
Recommended Action Collect module internal information by issuing the command 'show module
Error Message MODULE-2-MOD_SOMEPORTS_FAILED: Module [dec] (Serial number: [chars])

reported failure on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in
device [chars] (error [hex])
Explanation Module [decimal digit] reported a failure in the runtime diagnostic due to failure in
some of the ports.
Error Message MODULE-2-MOD_UNKNOWN: Module type [[dec]] in slot [dec] is not

supported
Explanation The software card id of module [decimal digit] is not supported by the supervisor.
Recommended Action Collect information about the module by issuing the commands 'show module
internal all module [decimal digit]'
OL-26589-01 2-307
Error Message MODULE-2-XBAR_DIAG_FAIL: Xbar [dec] (Serial number: [chars]) reported

failure [chars] due to [chars] in device [chars] (device error [hex])
Explanation The xbar in slot [decimal digit] reported a failure in the runtime diagnostic. Module
manager is going to power cycle the module.
internal all xbar [decimal digit]'.
Error Message MODULE-2-XBAR_FAILURE: Re-initializing xbar [dec] (Serial number:

Explanation Xbar [decimal digit] reported a failure during the initialization phase and will be
rebooted.
module_internal all xbar '.
Error Message MODULE-2-XBAR_FAILURE: Re-initializing xbar [dec] (Serial number:

rebooted.
showmodule_internalallxbar<modulenumber
Error Message MODULE-2-XBAR_FAIL: Initialization of xbar [dec] (Serial number:

[chars]) failed
powered down.
module_internal all xbar '.
Error Message MODULE-2-XBAR_SOMEPORTS_FAILED: Xbar [dec] (Serial number: [chars])

Explanation Xbar [decimal digit] reported a failure in the runtime diagnostic due to failure in some
of the ports.
internal all xbar [decimal digit]'.
2-308 OL-26589-01
Error Message MODULE-2-XBAR_SOMEPORTS_FAILED: Xbar [dec] (Serial number: [chars])

Explanation Xbar [decimal digit] reported a failure in the runtime diagnostic due to failure in some
of the ports.
Recommended Action Collect information about the module by issuing the command
showmoduleinternalallxbar[decimaldigit]'.'
Error Message MODULE-2-XBAR_UNKNOWN: Xbar type [[dec]] in slot [dec] is not supported
Explanation The software card id of xbar [decimal digit] is not supported by the supervisor.
Recommended Action Collect information about the module by issuing the commands 'show module
internal all xbar [decimal digit]''
MODULE-3
Error Message MODULE-3-LCM_SEQ_ERROR: Error ([chars]) for slot:[dec] while

communicating with component [chars] opcode:[chars] (for:[dec])
Explanation LCM encountered an error while executing a sequence for a module.
Error Message MODULE-3-LCM_SYSLOG_ERR: [chars]
Explanation LCM encountered an error while processing a message for module.
Recommended Action No action is required. '
Error Message MODULE-3-MOD_SRG_NOT_COMPATIBLE: Module [dec] (Serial number: [chars])

firmware is not compatible with supervisor, downloading new image
Explanation The software version of module [decimal digit] is not supported by the supervisor.
showmoduleinternalallmodule[decimaldigit]'.'
OL-26589-01 2-309
MODULE-4
Error Message MODULE-4-MOD_WARNING: Module [dec] (Serial number: [chars]) reported

warning [chars] due to [chars] in device [chars] (device error [hex])
Explanation Module [decimal digit] reported a warning in the runtime diagnostic due to failure in
some of the ports.
showmoduleinternalallmodule[decimaldigit]'.'
Error Message MODULE-4-XBAR_WARNING: Xbar [dec] (Serial number: [chars]) reported

warning [chars] due to [chars] in device [chars] (device error [hex])
Explanation Xbar [decimal digit] reported a warning in the runtime diagnostic due to failure in some
of the ports.
showmoduleinternalallxbar[decimaldigit]'.'
MODULE-5
Error Message MODULE-5-ACTIVE_SUP_OK: Supervisor [dec] is active (Serial number:

[chars])
Explanation Module [decimal digit] is ready to be configured and be able to switch traffic.
Error Message MODULE-5-LCM_MODULE_UPGRADE_END: Upgrade of module [dec] ended
Explanation Upgrade of the module has ended.
Error Message MODULE-5-LCM_MODULE_UPGRADE_START: Upgrade of module [dec] started
Explanation Upgrade of the module has been started by installer
Error Message MODULE-5-MOD_OK: Module [dec] is online (Serial number: [chars])
2-310 OL-26589-01
Error Message MODULE-5-MOD_REINIT: Re-initializing module [dec] (Serial number:

[chars])
rebooted.
showmodule_internalallmodule<modulenumber
Error Message MODULE-5-MOD_RESTART: Module [dec] is restarting after image download
Explanation Module [decimal digit] completed image download and is restarting.
Error Message MODULE-5-MOD_STARTUP_CFG_MISMATCH: The startup configuration cannot be

applied to a different module type for module [dec] (Serial number: [chars]).
[chars] module is replacing [chars].
Explanation The startup configuration for module [decimal digit] contains information about a
different type of module instead of containing information about the current one.
Error Message MODULE-5-STANDBY_SUP_OK: Supervisor [dec] is standby
Error Message MODULE-5-XBAR_OK: Xbar [dec] is online (Serial number: [chars])
Explanation Xbar [decimal digit] is ready to be configured and be able to switch traffic.
Error Message MODULE-5-XBAR_REINIT: Re-initializing xbar [dec] (Serial number:

[chars])
rebooted.
showmodule_internalallxbar<modulenumber
OL-26589-01 2-311
MODULE-6
Error Message MODULE-6-MOD_PURGE_CONFIG: Purging the configuration for module

[dec]
Explanation Notification is being sent to remove the module configurations.
Error Message MODULE-6-MOD_REG_OK: Registration succeeded for module [dec]
Explanation Module [decimal digit] sent a successful registration message.
MONITOR Messages
This section contains the MONITOR messages.
MONITOR-5
Error Message MONITOR-5-ETH_SPAN_SESSION_CREATED: Session [dec] created
Explanation A new span session has been created.
Error Message MONITOR-5-ETH_SPAN_SESSION_DELETED: Session [dec] deleted
Explanation Session has been deleted.
Error Message MONITOR-5-ETH_SPAN_SESSION_DOWN: Session [dec] is down. Reason

"[chars]"
Explanation Session is down, no further traffic will be spanned.
Error Message MONITOR-5-ETH_SPAN_SESSION_ERROR: Session [dec] is having error.

Reason "[chars]"
Explanation The session is experiencing a problem.
Recommended Action Delete the session and try to reconfigure it
2-312 OL-26589-01
Error Message MONITOR-5-ETH_SPAN_SESSION_UP: Session [dec] is up.
Explanation Session is up now. You can monitor Spanned traffic at the destination ports
NFM Messages
This section contains the NFM messages.
NFM-2
Error Message NFM-2-COMMIT_FAIL: Commit failed: client [hex], [chars]
Explanation The DDB commit failed
Error Message NFM-2-DDB_FAILURE: DDB failure: [chars]
Explanation A DDB generated failure
Error Message NFM-2-EXITING: Exit reason: [chars]
Explanation The NFM service process has exited due to [char]. The process has probably been
Error Message NFM-2-INIT_FAIL: NFM Service Init failed: [chars]
Explanation NFM Service initialization failed. [chars] explains the reason for the failure.
Error Message NFM-2-MALLOC_ERROR: Function [chars]: Size [dec] bytes
Explanation The NFM service could not allocate memory.
OL-26589-01 2-313
Error Message NFM-2-PSS_ERROR: [chars]: PSS ret. val=[dec]
Explanation The NFM service encountered error while operating on a persistent storage database.
Error Message NFM-2-VERIFY_FAIL: Verify failed - Client [hex], Reason: [chars],

Interface: [chars]
Explanation The DDB Verify failed
NFM-3
Error Message NFM-3-DDB_ERROR: DDB error: [chars]
Explanation The DDB generated error
Error Message NFM-3-FEATURE_MANAGER_ERROR: [chars]: An error occurred processing

a Feature Manager msg - error [chars]
Explanation An error occurred while processing a message from FEATURE Manager
Error Message NFM-3-HANDLE_IN_USE: [chars]: name: [chars]
Explanation The NFM service encountered a handle that was in use while reading a persistent
storage database.
Error Message NFM-3-INVALID_HANDLE: [chars]: handle =[hex]
Explanation The NFM service encountered an invalid handle in a persistent storage database.
Error Message NFM-3-MONITOR_NOT_FOUND: Monitor with handle [hex] from source [hex]
Explanation An Export Msg from a Linecard contained an invalid Monitor handle
2-314 OL-26589-01
Error Message NFM-3-MTS_ERROR: NFM encountered the following MTS error: [chars]
Explanation NFM Service encountered an MTS error. [chars] specifies the context where the error
occurred.
Error Message NFM-3-NFM_CONFIG_ERROR: [chars]
Explanation L2 Netflow config is applied on Port-channel with F1 Line Cards only - error
Error Message NFM-3-NFM_DDB_ERROR: DDB error: [chars]
Explanation The DDB generated error
Error Message NFM-3-PSS_CORRUPTED: [chars] PSS found corrupted
Explanation The NFM service has detected corruption in one of its persistent information database.
Error Message NFM-3-VLAN_PARSE_ERROR: [chars]: An error occurred processing a VLAN

Mgr Parse msg [hex]
Explanation An error occurred while processing a message from VLAN Manager
NFM-4
Error Message NFM-4-DDB_WARNING: DDB warning: [chars]
Explanation The DDB generated warning
Error Message NFM-4-LICENSE_EXPIRED: The License has expired.
Explanation The NFM service requires a License to run and exits when the License expires.
OL-26589-01 2-315
Error Message NFM-4-NFM_DDB_WARNING: DDB warning: [chars]
Explanation The DDB generated warning
Error Message NFM-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec]
Explanation There was a version mismatch between the NFM service and one of its persistent
NFM-5
Error Message NFM-5-FEATURE_DISABLED: NetFlow Disabled.
Explanation NetFlow Feature Disabled.
Error Message NFM-5-FEATURE_ENABLED: NetFlow Enabled.
Explanation NetFlow Feature Enabled.
NFM-6
Error Message NFM-6-BECAME_ACTIVE: Became ACTIVE from standby mode
Explanation The NFM service on the standby supervisor became active and it is ready to serve client
requests.
Error Message NFM-6-BECAME_STDBY: Became STANDBY from active mode
Explanation The NFM service became standby from active mode.
Error Message NFM-6-DDB_NOTIF: DDB notification: [chars]
Explanation The DDB generated notification
2-316 OL-26589-01
Error Message NFM-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system

Explanation The NFM service was unable to send heartbeat to the system manger
Error Message NFM-6-NFM_DDB_NOTIF: DDB notification: [chars]
Explanation The DDB generated notification
Error Message NFM-6-SERVICE_UP: Initialized [chars]
Explanation The NFM service is up and ready The service was initialized in [char] mode.
Error Message NFM-6-SRV_EXIT: NFM Service shutting down gracefully
Explanation NFM Service is shutting down gracefully. This is an informational message.
Error Message NFM-6-SWITCH_OVER: Switching Over to other Sup.
Explanation The NFM service has successfully switched over to the standby supervisor card.
NFM-7
Error Message NFM-7-DEBUG: [chars]
Explanation Debug information is being sent to syslog
NFP Messages
This section contains the NFP messages.
OL-26589-01 2-317
NFP-SLOT#-2
Error Message NFP-SLOT#-2-NF_ACL_ERR: [chars]([dec]): acl error. [chars]
Explanation Acl error
Error Message NFP-SLOT#-2-NF_DDB_ERR: [chars]([dec]): ddb error. [chars]
Explanation Ddb error
Error Message NFP-SLOT#-2-NF_ERR: [chars]([dec]): nfp error. [chars]
Explanation Nfp error occured
Error Message NFP-SLOT#-2-NF_FIB_ERR: [chars]([dec]): fib error. [chars]
Explanation Fib error
Error Message NFP-SLOT#-2-NF_NDE_ERR: [chars]([dec]): nde error. [chars]
Explanation Nde error
Error Message NFP-SLOT#-2-NF_NFM_ERR: [chars]([dec]): nfm error. [chars]
Explanation Nfm error
Error Message NFP-SLOT#-2-NF_QOS_ERR: [chars]([dec]): qos error. [chars]
Explanation Qos error
2-318 OL-26589-01
NFP-SLOT#-5
Error Message NFP-SLOT#-5-NF_INFO: [chars]
Explanation Info
NPC Messages
This section contains the NPC messages.
NPC-SLOT#-3
Error Message NPC-SLOT#-3-LOG_NPC_ERR: Nonrecoverable error: [chars]
NPC-SLOT#-4
Error Message NPC-SLOT#-4-LOG_NPC_WARNING: Serious error: [chars]
NPC-SLOT#-5
Error Message NPC-SLOT#-5-LOG_NPC_DEBUG: Unexpected error: [chars]
Error Message NPC-SLOT#-5-LOG_NPC_NVP_FSM: Illegal event received: [chars]
Explanation Illegal event received in NPC_NVP FSM
OL-26589-01 2-319
Error Message NPC-SLOT#-5-LOG_NPC_VSAN_FSM: Illegal event received: [chars]
Explanation Illegal event received in NPC_VSAN FSM
NPV Messages
This section contains the NPV messages.
NPV-2
Error Message NPV-2-CFS_PEER_LOST_WITHIN_SESSION: CFS peer with switch wwn [chars]

was lost in the middle of an active CFS session. Abort the CFS session and re-enter
the configuration changes
Explanation Due to port flaps, link outages, switch restart etc. a CFS peer switch of NPV was lost.
The current configuration changes would not be applied to this peer until the peer merges with this
switch. The CFS merge may fail if the configuration at the lost peer conflicts with the changes made
in this session. It is recommended that the user abort this CFS session using ivr abort command and
then re-enter the configuration changes.
Error Message NPV-2-NPV_DISABLE_FAILED: NPV could not disabled : [chars] [chars]
Explanation NPM could not disabled due to the reason specified. Please try again.
Error Message NPV-2-NPV_ENABLE_FAILED: NPV could not enabled : [chars] [chars]
Explanation NPM could not enabled due to the reason specified. Please try again.
Error Message NPV-2-NPV_EXITED: NPV process exited in file [chars] at Line

[chars]:[chars]
Explanation NPM process encountered a critical error as specified, and so NPV process cannot
continue.
2-320 OL-26589-01
NPV-3
Error Message NPV-3-ACL_UPDATE_FAILED: [chars]
Explanation ACL update request initiated by the NPV process has failed
Error Message NPV-3-CFS_INVALID_PAYLOAD_RECEIVED: NPV received invalid payload

from CFS
Explanation NPV process received invalid payload from CFS.
Error Message NPV-3-CLEAR_FAILED: [chars]
Explanation An error occurred while clearing the lock. The reason for the failure : [chars]
Error Message NPV-3-COMMIT_FAILED: [chars]
Explanation An error occurred while committing configuration. The reason for the failure : [chars]
Error Message NPV-3-COMMIT_PARTIALLY_FAILED: [chars]
Explanation An error occurred while committing configuration. Configuration could not be

committed on some switches. The reason for the failure : [chars]. Configuration can be inconsistent
in the fabric.
Error Message NPV-3-COMMIT_REJECTED: [chars]
Explanation Commit request received from remote switch is rejected. The reason for the failure:
[chars]
OL-26589-01 2-321
Error Message NPV-3-FC2_SEND_FAILED: [chars]
Explanation NPV process could send an FC2 message.
Error Message NPV-3-F_RJT_SENT: [chars]
Explanation NPV process sent an F_RJT frame.
Error Message NPV-3-INTERNAL_ERROR: Internal error: [chars]
Explanation NPV process encountered a general error, one that does not fall in any of the categories.
Error Message NPV-3-LCP_PROGRAMMING_FAILED: [chars]
Explanation LCP programming request initiated by the NPV process has failed
Error Message NPV-3-LOCK_FAILED: [chars]
Error Message NPV-3-LS_RJT_RCVD: [chars]
Explanation NPV process received an LS_RJT frame.
Error Message NPV-3-LS_RJT_SENT: [chars]
Explanation NPV process sent an LS_RJT frame.
Error Message NPV-3-MALLOC_FAILED: [chars]
Explanation NPV process could not allocate memory
2-322 OL-26589-01
Error Message NPV-3-MERGE_ACTIVATION_FAILED: [chars]
[chars]
Error Message NPV-3-MERGE_FAILED: [chars]
Explanation An error occurred while merging configuration. The reason for the failure : [chars]
Error Message NPV-3-MTS_SEND_FAILED: [chars]
Explanation NPV process could not send an MTS message.
Error Message NPV-3-NPIV_DISABLE_FAILED: [chars]
Explanation NPIV feature could not be disabled.
Error Message NPV-3-NPV_CFS_IPV4_ENABLE_FAILED: CFS IPv4 distribution enable

failed because [chars]
Explanation NPV CFS distribution might not work. Try enabling it again on the command line.
Make sure cfs distribution is enabled.
Error Message NPV-3-PORT_BRINGUP_FAILED: [chars]
Explanation NPV process has failed to bringup the port
Error Message NPV-3-PORT_REINIT_FAILED: [chars]
Explanation Port reinit request initiated by the NPV process has failed
OL-26589-01 2-323
Error Message NPV-3-UNLOCK_FAILED: [chars]
Explanation An error occurred while releasing the lock. The reason for the failure : [chars]
NPV-4
Error Message NPV-4-NPV_NPIV_NOT_ENABLED_ON_UPSTREAM_SWITCH: [chars]
Explanation This syslog is printed when the external interface fails to come up due to NPIV feature
not enabled on the upstream switch.
Recommended Action Verify and enable NPIV feature in upstream switch.
Error Message NPV-4-NPV_PORT_VSAN_MISMATCH_ON_UPSTREAM_LINK: [chars]
Explanation This syslog is printed when the external interface fails to come up due to upstream port
VSAN mis-match with the upstream switch.
Recommended Action Make sure port VSAN is same on both sides of this external link
NPV-5
Error Message NPV-5-ASSERTION_FAILED: Unexpected assertion failure in File [chars]

at Line [dec]
Explanation An assertion failed in NPV code
Error Message NPV-5-FLEXATTACH_VPWWN_AUTO_ASSIGNED: A virtual port WWN [chars] has

been automatically assigned to interface [chars]
Explanation The virtual port WWN will be used as port WWN for devices logging in on this
interface.
Error Message NPV-5-FLEXATTACH_VPWWN_MANUALLY_ASSIGNED: A virtual port WWN [chars]

has been manually assigned to interface [chars]
Explanation The virtual port WWN will be used as port WWN for devices logging in on this
interface.
2-324 OL-26589-01
Error Message NPV-5-FLEXATTACH_VPWWN_UNASSIGNED: The virtual port WWN has been

unassigned from interface [chars]
Explanation The physical port WWN will be used as port WWN for devices logging in on this
interface.
Error Message NPV-5-FRAME_DISCARDED: [chars]
Explanation NPV process discarded an FC2 frame.
Error Message NPV-5-NPV_LOAD_BALANCE_REINIT: Server ports reinitialized : [chars]
Explanation Server ports are reinitialized to balance the loads on the external interfaces.
Error Message NPV-5-UNEXPECTED_EVENT: [chars]
Explanation NPV process has received an unexpected event in the current state.
NPV-6
Error Message NPV-6-ABTS_SENT: [chars]
Explanation NPV process sent an ABTS frame.
Error Message NPV-6-ELS_CMD_SENT_TO_CORE: [chars]
Explanation NPV process sent an ELS frame to the core switch.
Error Message NPV-6-ELS_CMD_SENT_TO_SRV: [chars]
Explanation NPV process sent an ELS frame to the server.
OL-26589-01 2-325
Error Message NPV-6-EXT_IF_SELECTED: [chars]
Explanation NPV process has selected an external interface to forward either all frames received on
a server interface or frames received from a specific port WWN.
Error Message NPV-6-FABRIC_PROXY_LOGO_SENT: [chars]
Explanation NPV process sent a LOGO frame to the device as the corresponding external interface
went down.
Error Message NPV-6-FDISC_RCVD: [chars]
Explanation NPV process received an FDISC frame.
Error Message NPV-6-FDISC_SENT: [chars]
Explanation NPV process sent an FDISC frame to the core switch.
Error Message NPV-6-FLOGI_RCVD: [chars]
Explanation NPV process received an FLOGI frame.
Error Message NPV-6-INTERNAL_FLOGI_SENT: [chars]
Explanation NPV process sent an internal FLOGI frame to the core switch on an external interface.
Error Message NPV-6-LOGO_RCVD: [chars]
Explanation NPV process received a LOGO frame.
Error Message NPV-6-LOGO_SENT: [chars]
Explanation NPV process sent a LOGO frame.
2-326 OL-26589-01
Error Message NPV-6-LS_ACC_RCVD: [chars]
Explanation NPV process received an LS_ACC frame.
Error Message NPV-6-LS_ACC_SENT: [chars]
Explanation NPV process sent an LS_ACC frame.
Error Message NPV-6-MTS_NOTIF_RCVD: [chars]
Explanation NPV process received an MTS notification.
Error Message NPV-6-MTS_NOTIF_SENT: [chars]
Explanation NPV process sent an MTS notification.
Error Message NPV-6-MTS_REQ_RCVD: [chars]
Explanation NPV process received an MTS request.
Error Message NPV-6-MTS_REQ_SENT: [chars]
Explanation NPV process sent an MTS request.
Error Message NPV-6-MTS_RESP_RCVD: [chars]
Explanation NPV process received an MTS response.
Error Message NPV-6-MTS_RESP_SENT: [chars]
Explanation NPV process sent an MTS response.
OL-26589-01 2-327
Error Message NPV-6-NPIV_DISABLED: [chars]
Explanation NPIV feature has been disabled.
Error Message NPV-6-NPIV_ENABLED: [chars]
Explanation NPIV feature has been enabled.
Error Message NPV-6-NPV_ENABLE_DISABLE_IN_PROGRESS: [chars]
Explanation NPV feature enable/disable is in progress. This syslog is printed at the beginning of
various significant phases.
Error Message NPV-6-NPV_LOAD_BALANCE_TIMER_START: (Re)starting automatic load

balancing timer for [dec] seconds
Explanation Timer started for upon external interface up or server interface down. When the timer
goes off some of the server interfaces may be reinitialized to evenly distribute the server interfaces
amongst the eligible external interfaces.
Error Message NPV-6-SERVER_PROXY_LOGO_SENT: [chars]
Explanation NPV process sent a LOGO frame to the core switch as the server interface went down.
NPV-7
Error Message NPV-7-CFS_REQ_RCVD: [chars]
Explanation CFS request is received. The WWN of the switch originated this request and the
rr-token of the request are provided in the syslog message.
Error Message NPV-7-CFS_RESP_SENT: [chars]
Explanation CFS response is sent. The rr-token of the corresponding request and the status are
provided in the syslog message
2-328 OL-26589-01
NTP Messages
This section contains the NTP messages.
NTP-2
Error Message NTP-2-NTP_SYSLOG_CRIT_ERR: : [chars]
Explanation NTP syslog Critial Error : [chars].
Error Message NTP-2-NTP_SYSLOG_INIT_FAIL: : [chars] [chars]
Explanation NTP Initialization Failed: [chars] [chars].
Error Message NTP-2-NTP_SYSLOG_NO_RESP_FROM_LC: from LC[dec] for [chars]
Explanation NTP did not receive response from the linecard for the request sent.
NTP-3
Error Message NTP-3-NTP_SYSLOG_ALLOC_FAIL: : [chars]
Explanation NTP syslog allocation failed : [chars].
Error Message NTP-3-NTP_SYSLOG_ERR_EXT: : [chars] [chars]
Explanation NTP syslog Error Exit : [chars] [dec].
Error Message NTP-3-NTP_SYSLOG_ERR: : [chars]
Explanation NTP syslog Error : [chars].
OL-26589-01 2-329
Error Message NTP-3-NTP_SYSLOG_MTS_ERR: : [chars]
Explanation NTP MTS Error : [chars].
NTP-6
Error Message NTP-6-NTP_SYSLOG_CREATED: : [chars]; Slot No: [dec]
Explanation NTP syslog created : [chars] [chars].
Error Message NTP-6-NTP_SYSLOG_EXIT: : [chars]
Explanation NTP syslog Exit : [chars].
Error Message NTP-6-NTP_SYSLOG_LOGGING: : [chars]
Explanation NTP logging : [chars].
Error Message NTP-6-NTP_SYSLOG_WARN: : [chars]
Explanation NTP syslog Warning : [chars].
NVP Messages
This section contains the NVP messages.
NVP-6
Error Message NVP-6-NVP_INFO: [chars]
Explanation NVP daemon informational message
2-330 OL-26589-01
Error Message NVP-6-STARTING: deamon started
Explanation The NVP daemon successfully started
NVP-SLOT#-2
Error Message NVP-SLOT#-2-CPP_CATASTROPHIC_ERROR: ERROR: Component ([chars])

caused critical error please reboot SSM
Explanation Component caused critical error
Recommended Action Restart the linecard
OC_USD Messages
This section contains the OC_USD messages.
OC_USD-2
Error Message OC_USD-2-RF_CRC: [chars]
Explanation Octopus received packets with CRC error from fabric
ORI_FWD Messages
This section contains the ORI_FWD messages.
ORI_FWD-2
Error Message ORI_FWD-2-CRIT_MSG: [chars]
OL-26589-01 2-331
ORI_FWD-6
Error Message ORI_FWD-6-ORF_DEBUG_MSG: [chars]
ORI_MAC Messages
This section contains the ORI_MAC messages.
ORI_MAC-2
Error Message ORI_MAC-2-ORI_MAC_CRIT_MSG: [chars]
ORI_MAC-6
Error Message ORI_MAC-6-ORI_MAC_DEBUG_MSG: [chars]
OTM Messages
This section contains the OTM messages.
OTM-2
Error Message OTM-2-OTM_EEM_FAIL: OTM failed to register with EEM
Explanation OTM process failed to register with eem, exiting now
2-332 OL-26589-01
OTM-3
Error Message OTM-3-OTM_ERROR: [chars] [chars]
Explanation [chars1][chars2]
OTM-5
Error Message OTM-5-OTM_OBJECT_STATUS: Status of tracking object [dec] changed to

[chars]
Explanation Status of tracking object [dec] changed to [chars]
Error Message OTM-5-OTM_OBJ_ADD: : Tracking object [dec] configured, status of the

object [chars]
Explanation Tracking Object [dec] configured, status of the object [chars]
OTM-6
Error Message OTM-6-OTM_EXITED: OTM process exited
Explanation OTM process is terminated
Error Message OTM-6-OTM_OBJ_REM: : Tracking object [dec] removed
Explanation Tracking Object [dec] removed
Error Message OTM-6-OTM_STARTED: OTM process started
Explanation OTM process is up and running
OL-26589-01 2-333
Error Message OTM-6-OTM_TRACK_START: Client started tracking object [dec]
Explanation Client has started tracking object [dec]
Error Message OTM-6-OTM_TRACK_STOP: Client stopped tracking object [dec]
Explanation Client has stopped tracking object [dec]
Recommended Action
PHY_USD Messages
This section contains the PHY_USD messages.
PHY_USD-SLOT#-4
Error Message PHY_USD-SLOT#-4-LOG_PHY_ISSU_LINK_ST_CHNG: Port [dec]: link state

during ISSU
Explanation Port Link status changed while perfoming an In Service System Upgrade. Disabling the
port.
PIXM Messages
This section contains the PIXM messages.
PIXM-2
Error Message PIXM-2-PIXM_SYSLOG_MESSAGE_TYPE_CRIT: [chars]
Explanation PIXM has encountered a critical error
Recommended Action Please collect PIXM tech support using

showtechpixm'and'showtechpixmc-all''
2-334 OL-26589-01
PIXM-3
Error Message PIXM-3-PIXM_SYSLOG_MESSAGE_TYPE_ERR: [chars]
Explanation PIXM has encountered a error

PIXM-4
Error Message PIXM-4-PIXM_SYSLOG_MESSAGE_TYPE_WARNING: [chars]
Explanation PIXM has encountered a warning-level error

PIXM-7
Error Message PIXM-7-PIXM_SYSLOG_MESSAGE_TYPE_DEBUG: [chars]
Explanation This is a debug output from PIXM

PLATFORM Messages
This section contains the PLATFORM messages.
PLATFORM-0
Error Message PLATFORM-0-CHASSIS_CLKSWITCH: Hardware clock switched to redundant

clock-[dec]
Explanation Clock module on chassis deteted a failure and switched to redundant clock module.
Recommended Action Please perform a showplatforminternalinfo'tocollectmoreinformation.'
Error Message PLATFORM-0-CHASSIS_CLKSWRESET: Switch reset due to clock switch
Explanation Chassis clock source has failed and system will be reset. System will automatically start
using redundant clock module.
Recommended Action Please refer to the platform document on clock modules.
OL-26589-01 2-335
Error Message PLATFORM-0-CHASSIS_CLKSW_MODULE_RESET: Modules reset due to clock

switch
Explanation Chassis clock source has switched and all Vegas line cards will be reset. System will
automatically continue using redundant clock module.
Recommended Action Please refer to the platform document on clock modules.
Error Message PLATFORM-0-FAIL_REMOVED: Fan module removed. Fan[dec] has been absent
for [dec] seconds
Explanation Fan module is removed. This could lead to temperature alarms.
Recommended Action Replace the fan module ASAP.
Error Message PLATFORM-0-MOD_TEMPMAJALRM: [chars] reported Major temperature

alarm. Sensor=[dec] Temperature=[dec] MajThreshold=[dec]
Explanation Module in slot [decimal digit] exceeded major temperature threshold.
Recommended Action Please perform a showenvtemperature'tocollectmoreinformation.'
Error Message PLATFORM-0-MOD_TEMPSHUTDOWN: [chars] powered down due to major

temperature alarm for Sensor [dec].
Explanation Module in slot [decimal digit] shutdown due to temperature exceeding major threshold.
Error Message PLATFORM-0-MOD_TEMPWARMALRM: [chars] reported Warm temperature

alarm. Sensor=[dec] Temperature=[dec] WarmThreshold=[dec]
Explanation Module in slot [decimal digit] exceeded warm temperature threshold.
Error Message PLATFORM-0-PFM_EMERGENCY: [chars]
Explanation Platform Emergency
Error Message PLATFORM-0-SUP_SPROM_ERROR: Unable to read SPROM for Sup in slot

[dec]
Explanation The supervisor in slot [decimal digit] was not able to read its SPROM.
2-336 OL-26589-01
Error Message PLATFORM-0-SUP_WRONGSLOTNUM: Supervisor powered up in WRONG

SLOT:[dec] (Serial number [chars])
Explanation The supervisor is comming up in wrong slot [decimal digit].
Error Message PLATFORM-0-SYS_LC_DRIVER_LOAD_FAILED: Failed to load linecard module

drivers
Explanation Failed to load drivers.
Recommended Action Image is possibly corrupt. Try to load a different image.
Error Message PLATFORM-0-SYS_RESET: [chars] System shutdown in [dec] seconds
Explanation System shutdown in [decimal digit] seconds.
Error Message PLATFORM-0-SYS_SHUTDOWN_FAN_REMOVAL: System shutdown in [dec]

seconds due to fan removal
Explanation System shutdown in [decimal digit] seconds due to removal of fan module.
Recommended Action Please perform a showenvfan'tocollectmoreinformation.'
Error Message PLATFORM-0-SYS_SHUTDOWN_MDS9124_FAN_FAIL: System shutdown in [dec]

seconds due to less than 4 fans operating.
Explanation System shutdown in [decimal digit] seconds due to less than 4 fans operating.
Recommended Action Please perform a showenvfan'tocollectmoreinformation.'
Error Message PLATFORM-0-SYS_SHUTDOWN: System shutdown in [dec] seconds due to

major temperature alarm
Explanation System shutdown in [decimal digit] seconds due to temperature exceeding major
threshold.
Error Message PLATFORM-0-SYS_SUP_DRIVER_LOAD_FAILED: Failed to load supervisor

module drivers
Explanation Failed to load drivers.
Recommended Action Image is possibly corrupt. Try to load a different image
OL-26589-01 2-337
Error Message PLATFORM-0-XBAR_CARD_CLK_FAIL: Xbar card in slot:[dec] (Serial

number [chars]) encountered clock failure
Explanation The xbar in slot [decimal digit] encountered clock failure.
Error Message PLATFORM-0-XBAR_CARD_INCOMPAT_CHASSIS: Xbar card in slot:[dec] (Part

number [chars]) Incompatible with backplane chassis Part Num:[chars]
Explanation The xbar in slot [decimal digit] is incompatible with backplane chassis.
Error Message PLATFORM-0-XBAR_WRONGSLOTNUM: Xbar powered up in WRONG SLOT:[dec]

(Serial number [chars])
Explanation The xbar in slot [decimal digit] powered up in wrong slot.
PLATFORM-1
Error Message PLATFORM-1-FABRIC_SWITCH_FAN_FAIL: Less than 4 required fans

operating.
Explanation Fan module has failed leaving less than 4 total fans operating. Fan needs to be replaced.
This can lead to overheating and temperature alarms.
Error Message PLATFORM-1-FAN_FAIL: Fan module Failed
Explanation Fan module has failed and needs to be replaced. This can lead to overheating and
temperature alarms.
Error Message PLATFORM-1-PFM_ALERT: [chars]
Explanation Platform Alert
2-338 OL-26589-01
Error Message PLATFORM-1-PS_SINGLE_INPUT: Both power inputs are connected for Power
supplies, remove single-input configuration for optimal power usage
Explanation Current power supply redundancy mode may not be optimal
Recommended Action Please perform a

showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.'
Error Message PLATFORM-1-XBAR_PWRDENY: Xbar [dec] can not be powered up due to

insufficient power (Serial number [chars])
Explanation Available power in power supplies is not sufficient to power up the xbar
Recommended Action You can verify available power and current usage using command
showenvpower'.Pleaserefertopowersupplydocumentonhowtoincreasepowersupplycapacity.'
PLATFORM-2
Error Message PLATFORM-2-9134_FAN_FAIL: Fan module [dec] Failed
temperature alarms.
Error Message PLATFORM-2-9134_FAN_OK: Fan module [dec] ok
Explanation Fan module is ok
Error Message PLATFORM-2-CASA_FAN_FAIL: Fan module [dec] Failed
temperature alarms.
Error Message PLATFORM-2-CASA_FAN_OK: Fan module [dec] ok
Error Message PLATFORM-2-CHASSIS_CLKMODFAULTY: Chassis clock module [dec] faulty
Explanation Clock module on chassis is faulty or has been removed.
OL-26589-01 2-339
Error Message PLATFORM-2-CHASSIS_CLKMODOK: Chassis clock module [dec] ok
Explanation Clock module on chassis is functioning properly.
Error Message PLATFORM-2-CHASSIS_CLKSRC: Current chassis clock source is

clock-[dec]
Explanation The current chassis clock source is [decimal digit].
Error Message PLATFORM-2-FANLET_FAN_FAIL: Failed Fanlets for Fan [dec] ([chars]

fan) : [chars]
Explanation The specified fanlets have failed. This can lead to overheating and temperature alarms.
Error Message PLATFORM-2-FANMOD_FAN_FAIL: Fan module [dec] ([chars] fan)

Failed/Removed
temperature alarms.
Error Message PLATFORM-2-FANMOD_FAN_OK: Fan module [dec] ([chars] fan) ok
Error Message PLATFORM-2-FAN_OK: Fan module ok
Error Message PLATFORM-2-FAN_REMOVED: Fan module [dec] (Serial number [chars])

[chars] removed
Explanation Fan module is removed
2-340 OL-26589-01
Error Message PLATFORM-2-INSUFFICIENT_MAC: program management port on all the

non-default VDCs
Explanation Could not program the mac address for the management port of all the VDCs
Error Message PLATFORM-2-MEMORY_ALERT_RECOVERED: Memory Status Alert : [chars]
Explanation Memory alert event received
Error Message PLATFORM-2-MEMORY_ALERT: Memory Status Alert : [chars]. Usage

[chars]% of Available Memory
Explanation Memory alert event received
Error Message PLATFORM-2-MOD_ALL_PWRDN_NOXBAR: All modules powered down due to

non-availability of xbar modules
Explanation All modules in switch are powered down because all xbar modules are offline

showmodule','showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[de
cimaldigit]'tocollectmoreinformationifyoususpectmodulehasbeenpowereddownduetoerrors.Atleast
onexbarmodulehastobeformodulestofunction'
Error Message PLATFORM-2-MOD_DETECT: Module [dec] detected (Serial number [chars])

Module-Type [chars] Model [chars]
Explanation A new module in slot [decimal digit] is detected.
Error Message PLATFORM-2-MOD_PWRDENY: Module [dec] can not be powered up due to

insufficient power (Serial number [chars])
Explanation Available power in power supplies is not sufficient to power up the module
Recommended Action You can verify available power and current usage using command
showenvpower'.Pleaserefertopowersupplydocumentonhowtoincreasepowersupplycapacity.'
OL-26589-01 2-341
Error Message PLATFORM-2-MOD_PWRDN: Module [dec] powered down (Serial number

[chars])
Explanation The module in slot [decimal digit] is powered down.

showmodule','showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[de
cimaldigit]'tocollectmoreinformationifyoususpectmodulehasbeenpowereddownduetoerrors.'
Error Message PLATFORM-2-MOD_PWRFAIL_EJECTORS_OPEN: All ejectors open, Module [dec]

will not be powered up (Serial number [chars])
Explanation The module can not be powered up because all the ejectors are open

showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh
owspromxbar[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.'
Error Message PLATFORM-2-MOD_PWRFAIL: Module [dec] failed to power up (Serial

number [chars])
Explanation The module in slot [decimal digit] failed to power up

showplatforminternalallmodule[decimaldigit]'andtocollectmoreinformation.'
Error Message PLATFORM-2-MOD_PWRIDPROMFAIL: Module [dec] failed to power up due to

IDPROM read error
Explanation The module can not be powered up due to IDPROM read error

owsprommodule[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.'
Error Message PLATFORM-2-MOD_PWRIDPROM_SW_CARD_ID_UNKNOWN: Module [dec] failed to

power up. (Unknown card. Could not get software-card-id)
Explanation The module can not be powered up due to missing SWID in core-plugin for this
CARDID

owsprommodule[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.'
Error Message PLATFORM-2-MOD_PWRUP_XBAR: Modules powered up due to xbar

availability
Explanation Modules powered up because atleast one xbar module is online
Recommended Action No action needed
2-342 OL-26589-01
Error Message PLATFORM-2-MOD_PWRUP: Module [dec] powered up (Serial number [chars])
Explanation The module in slot [decimal digit] is powered up.
Error Message PLATFORM-2-MOD_REMOVE: Module [dec] removed (Serial number [chars])
Explanation The module in slot [decimal digit] has been removed.
Error Message PLATFORM-2-MOD_TEMPMAJOR2WARM: [chars] recovered from minor

temperature alarm. Warm alarm pending. Sensor=[dec] Temperature=[dec]
MajTheshold=[dec] WarmThreshold=[dec]
Explanation Module in slot [decimal digit] warm temperature threshold.
Error Message PLATFORM-2-MOD_TEMPMAJOR_OK: [chars] recovered from major

temperature alarm. Sensor=[dec] Temperature=[dec] MajThreshold=[dec]
Explanation Module in slot [decimal digit] major temperature threshold.
Error Message PLATFORM-2-MOD_TEMPMINALRM: [chars] reported minor temperature

alarm. Sensor=[dec] Temperature=[dec] MinThreshold=[dec]
Explanation Module in slot [decimal digit] has exceeded minor temperature threshold.
Error Message PLATFORM-2-MOD_TEMPMINOR2WARM: [chars] recovered from minor

temperature alarm. Warm alarm pending. Sensor=[dec] Temperature=[dec]
MinTheshold=[dec] WarmThreshold=[dec]
Error Message PLATFORM-2-MOD_TEMPOK: [chars] recovered from minor temperature

alarm. Sensor=[dec] Temperature=[dec] MinThreshold=[dec]
Explanation Module in slot [decimal digit] minor temperature threshold.
OL-26589-01 2-343
Error Message PLATFORM-2-MOD_TEMPRECOVER: [chars] recovered from major temperature

alarm. Minor temperature alarm pending. Sensor=[dec] Temperature=[dec]
MajThreshold=[dec] MinThresh=[dec]
Explanation Module in slot [decimal digit] recovered from major temperature threshold. Minor
threshold still exceeded.
Error Message PLATFORM-2-MOD_TEMPWARM_OK: [chars] recovered from warm temperature

alarm. Sensor=[dec] Temperature=[dec] WarmThreshold=[dec]
Error Message PLATFORM-2-PFM_CRITICAL: [chars]
Explanation Platform Critical
Error Message PLATFORM-2-PFM_FATW_BUS_SWITCH_FAIL: Backplane two wire [chars] bus

connection fault detected but failed to perform bus switchover(BUS_A to BUS_B)
Explanation Could not access some modules using BUS_A, but can access using BUS_B
Recommended Action Please perform a showplatforminternalerr''
Error Message PLATFORM-2-PFM_FATW_BUS_SWITCH: Backplane two wire [chars] bus

connection or device fault caused bus switchover(BUS_A to BUS_B)
Explanation Could not access some modules using BUS_A, but can access using BUS_B
Recommended Action Please perform a showplatforminternalerr''
Error Message PLATFORM-2-PFM_IMG_CMPT_FAIL: Image version is not supported in this

chassis.
Explanation This image version is not supported in this chassis.
Recommended Action Sup-platform
Error Message PLATFORM-2-PFM_LC_BOOT_DEV_ABSENT: No bootflash found in Module

[dec]
Explanation No bootflash found.
Recommended Action Try to put in a bootflash in the module and try again.
2-344 OL-26589-01
Error Message PLATFORM-2-PFM_LC_BOOT_DEV_FAIL: Bootflash access error in Module

[dec]
Explanation Bad bootflash/corrupted filesystem.
Recommended Action Try to put in a known good bootflash in the module and try again.
Error Message PLATFORM-2-PFM_LC_MOD_POWERED_DOWN: Module [dec] Powered Down.

Module is not supported in this chassis. (Chassis Incompatible card)
Explanation Module Powered Down, because Module is not supported in this chassis. (Chassis
Incompatible card)
Recommended Action Please perform a showmodule'toseethePowerDownreason.'
Error Message PLATFORM-2-PFM_LC_NETBOOT_FAIL: Netboot for Module [dec] failed
Explanation Netboot failed.
Recommended Action Try to replace the BIOS in the module.
Error Message PLATFORM-2-PFM_LC_REGISTRATION_FAIL: Could not register with Module

[dec]
Explanation Module registration failed.
Recommended Action Try to replace the module.
Error Message PLATFORM-2-PFM_LC_STATUS: Module [dec] powered up with [dec] status
Explanation Status for the module that failed registration.
Recommended Action Try to replace the module.
Error Message PLATFORM-2-PFM_LOW_MEMORY_CONDITION: Module [dec] is running low on

memory. %ld percent used
Explanation Supervisor is running low on memory
Recommended Action Switchover
Error Message PLATFORM-2-PFM_MODULE_POWER_OFF_TRIGGER: Power-off [chars] due to

[chars] policy trigger
Explanation Policy trigger initiated a module poweroff
OL-26589-01 2-345
Error Message PLATFORM-2-PFM_MODULE_POWER_OFF: Manual power-off of [chars] from

Command Line Interface
Explanation User initiated a module power-off from the CLI
Error Message PLATFORM-2-PFM_MODULE_POWER_ON: Manual power-on of [chars] from

Explanation User initiated a module power-on from the CLI
Error Message PLATFORM-2-PFM_MODULE_RESET: Manual restart of Module [dec] from

Explanation User initiated a module reload from the CLI
Error Message PLATFORM-2-PFM_NETBOOT_DISABLE: Netboot for supervisor module in

slot [dec] is disabled due to incompatible platform
Explanation Standby supervisor failed to powerup.
Recommended Action Try to replace the standby supervisor.
Error Message PLATFORM-2-PFM_PREP_DEEP_SLEEP: Supervisor module in slot [dec]

preparing to enter deep sleep mode
Explanation Deep sleep mode initiated by the Connectivity Management Processor (CMP) for this
supervisor
Error Message PLATFORM-2-PFM_PWR_MGMT_EPLD_VER_MISMATCH: Module [dec] Pwr Mgmt

Epld (Version-[dec]) needs to be upgraded
Explanation Using a wrong version of Epld version can result in unexplainable behaviour
Recommended Action Upgrade Power Managment EPLD
Error Message PLATFORM-2-PFM_STDBY_POWERUP_FAIL: standby supervisor failed to

powerup
Explanation Standby supervisor failed to powerup.
Recommended Action Try to replace the standby supervisor.
2-346 OL-26589-01
Error Message PLATFORM-2-PFM_SYSTEM_RESET_TRIGGER: System restart due to [chars]

policy trigger
Explanation Policy/trigger initiated a system reload
Error Message PLATFORM-2-PFM_SYSTEM_RESET: Manual system restart from Command Line

Interface
Explanation User initiated a system reload from the CLI
Error Message PLATFORM-2-PFM_SYSTEM_SHUTDOWN_TRIGGER: System shutdown due to

[chars] policy trigger
Explanation Policy/trigger initiated a system shutdown
Error Message PLATFORM-2-PFM_XBAR_RESET: Manual restart of Xbar [dec] from Command

Line Interface
Explanation User initiated a xbar reload from the CLI
Error Message PLATFORM-2-PLUGIN_ABSENT: Module in slot[dec] (sw_card_id=[dec]) has

missing plugin
Explanation Plugin not loaded, The LC cannot be poweredup
Recommended Action Load the associated plugin
Error Message PLATFORM-2-PS_ABSENT: Power supply [dec] is absent/shutdown,

ps-redundancy might be affected
Explanation Power Supply is absent.
Error Message PLATFORM-2-PS_CAPACITY_CHANGE: Power supply PS[dec] changed its

capacity. possibly due to power cable removal/insertion (Serial number [chars])
Explanation Detected power supply capacity change.
Recommended Action Please refer to power supply document on increasing decreasing power supply
capacity, configuring power supplies, etc. Please perform
OL-26589-01 2-347
Error Message PLATFORM-2-PS_CAPACITY_DIFFER: Detected power supplies with

differing capacity. It is recommended to have same capacity for both powersupplies
otherwise it may cause service disruptions
Explanation Detected a power supply that has differing capacity than an the otherpower supply.
Error Message PLATFORM-2-PS_DETECT: Power supply [dec] detected but shutdown

Explanation Power Supply is detected but shutdown.

Error Message PLATFORM-2-PS_FAIL: Power supply [dec] failed or shut down (Serial
number [chars])
Explanation Power Supply has failed or has been shutdown

showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.Pleaserefertopow
ersupplydocumentonincreasingdecreasingpowersupplycapacity,configuringpowersupplies,etc.'
Error Message PLATFORM-2-PS_FANFAIL: Fan in Power supply [dec] failed
Explanation Fan module in the Power Supply has failed

Error Message PLATFORM-2-PS_FANOK: Fan in Power supply [dec] ok
Explanation Fan module in the Power Supply is ok.
Error Message PLATFORM-2-PS_MISMATCH: Detected power supply [chars]. This reduces

the redundant power available to the system and can cause service disruptions
Explanation Detected a new power supply that has reduced capacity than an existing power supply.
2-348 OL-26589-01
Error Message PLATFORM-2-PS_OK: Power supply [dec] ok (Serial number [chars])
Explanation Power Supply is ok.
Error Message PLATFORM-2-PS_PWR_INPUT_MISSING: Power supply [dec] present but all

AC/DC inputs are not connected, power redundancy might be affected
Explanation Power Supply is present but not at full capacity.
Error Message PLATFORM-2-PS_RED_MODE_CHG: Power supply redundancy mode changed to

[chars]
Explanation Power supply redundancy mode changed notification

Error Message PLATFORM-2-PS_RED_MODE_RESTORED: Power redundancy operational mode

changed to configured mode
Explanation Power Supply redundancy mode changes.
Error Message PLATFORM-2-PS_REMOVE_LAST: Unexpected removal of last power supply

[dec]. (Serial number [chars])
Explanation Unexpected removal the only power supply in the system.
Recommended Action Power supply unit may be faulty. Contact CISCO to replace the unit.
Error Message PLATFORM-2-PS_REMOVE: Power supply [dec] removed (Serial number

[chars])
Explanation Power Supply is removed.
Error Message PLATFORM-2-PS_UNKNOWN: Detected an unknown power supply [dec] for

CISCO Multilayer Switch (Serial number [chars])
Explanation Unable to determine power supply type. Default power supply types will be assumed.
capacity, configuring power supplies, etc.
OL-26589-01 2-349
Error Message PLATFORM-2-PS_UNSUPPORTED: Detected an unsupported power supply

[dec] [chars] for CISCO Multilayer Switch (Serial number [chars])
Explanation This power supply is not supported for the CISCO Multilayer Switches.
capacity, configuring power supplies, etc.
Error Message PLATFORM-2-SYS_IDPROMBAD_RECOVER_FAIL: Chassis IDPROM [dec] data

re-initialization Un-successful. Data is invalid
Explanation Chassis IDPROM [decimal digit] re-initialization was unsuccessful. Data is invalid.

showsprommodule[decimaldigit]1'toreadmoduleIDPROMcontentsandcollectmoreinformation.'
Error Message PLATFORM-2-SYS_IDPROMBAD_RECOVER_PASS: Chassis IDPROM [dec] data

re-initialized successfully
Explanation Chassis IDPROM [decimal digit] invalid data was succesfully re-initialized to valid.

showsprommodule[decimaldigit]1'toreadmoduleIDPROMcontentsandverifytheinformation.'
Error Message PLATFORM-2-SYS_IDPROMBAD: Chassis IDPROM [dec] data invalid
Explanation Chassis IDPROM [decimal digit] contains invalid data.

showsprommodule[decimaldigit]1'toreadmoduleIDPROMcontentsandcollectmoreinformation.'
Error Message PLATFORM-2-XBAR_DETECT: Xbar [dec] detected (Serial number [chars])
Explanation A new xbar in slot [decimal digit] is detected.
Error Message PLATFORM-2-XBAR_PWRFAIL_EJECTORS_OPEN: All ejectors open, Xbar [dec]

will not be powered up (Serial number [chars])
Explanation The xbar can not be powered up because all the ejectors are open

owspromxbar[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.''
2-350 OL-26589-01
Error Message PLATFORM-2-XBAR_REMOVE: Xbar [dec] removed (Serial number [chars])
Explanation The xbar in slot [decimal digit] has been removed.
PLATFORM-3
Error Message PLATFORM-3-EJECTOR_STAT_CHANGED:

Ejectorsstatusinslot[dec]haschanged,[chars]Ejectoris[chars],[chars]Ejectoris[cha
rs]'
Explanation Ejector status has changed
Error Message PLATFORM-3-MOD_BRINGUP_MULTI_LIMIT: Giving up after multiple

attempts were made to bring up the Module [dec], (Serial number [chars])
Explanation The module can not be powered up even after three attempts

Error Message PLATFORM-3-MOD_PWRFAIL_MULTI: Module [dec] failed to power up

multiple times (Serial number [chars])

Error Message PLATFORM-3-PFM_ERROR: [chars]
Explanation Platform Error
Error Message PLATFORM-3-SINGLE_EJECTOR_STAT_CHANGED:

Ejectorsstatusinslot[dec]haschanged,Ejectoris[chars]'
Explanation Ejector status has changed
OL-26589-01 2-351
Error Message PLATFORM-3-XBAR_BRINGUP_MULTI_LIMIT: Giving up after multiple attempts

were made to bring up the Xbar [dec], (Serial number [chars])

owspromxbar[dec][dec]'toreadmoduleIDPROMcontXBAentstocollectmoreinformation.'
Error Message PLATFORM-3-XBAR_PWRFAIL_MULTI: Xbar [dec] failed to power up multiple

times (Serial number [chars])
Explanation The xbar can not be powered up even after three attempts

Error Message PLATFORM-3-XBAR_PWRFAIL: Xbar [dec] failed to power up (Serial number

[chars])
Explanation The xbar in slot [decimal digit] failed to power up

showplatforminternalallmodule[decimaldigit]'andtocollectmoreinformation.'
Error Message PLATFORM-3-XBAR_PWRIDPROMFAIL: Xbar [dec] failed to power up due to

IDPROM read error
Explanation The xbar can not be powered up due to IDPROM read error

Error Message PLATFORM-3-XBAR_PWRIDPROM_SW_CARD_ID_UNKNOWN: Xbar [dec] failed to

power up. (Unknown card. Could not get software-card-id)
Explanation The xbar can not be powered up due to missing SWID in core-plugin for this CARDID

2-352 OL-26589-01
PLATFORM-4
Error Message PLATFORM-4-MOD_TEMPACCESSFAIL: [chars] temperature sensor [dec]

access failed
Explanation Module in slot [decimal digit] unable to access temperature sensor.
Error Message PLATFORM-4-MOD_TEMPFAIL: [chars] temperature sensor [dec] failed
Explanation Module in slot [decimal digit] contains a faulty temperature sensor.
Error Message PLATFORM-4-PFM_FAN_FLTR_STATUS: Fan Filter status: [chars]
Explanation Fan Filter status: Present/Absent
Recommended Action Please perform a showplatforminternalinfo.'
Error Message PLATFORM-4-PFM_PS_RED_MODE_CHG: Power redundancy mode changed to

[chars]
Explanation Power redundancy mode changed
Recommended Action Please perform a showplatforminternalinfo.'
Error Message PLATFORM-4-PFM_WARNING: [chars]
Explanation Platform Warning
PLATFORM-5
Error Message PLATFORM-5-FAN_DETECT: Fan module [dec] (Serial number [chars])

[chars] detected
Explanation Fan module is detected
OL-26589-01 2-353
Error Message PLATFORM-5-FAN_STATUS: Fan module [dec] (Serial number [chars])

[chars] current-status is [chars]
Explanation Fan module changed status
Error Message PLATFORM-5-FEX_FAN_DETECT: Fex [dec] Fan Module [dec] detected
Explanation Fex Fan module is detected
Error Message PLATFORM-5-FEX_FAN_REMOVE: Fex [dec] Fan Module [dec] removed
Explanation Fex Fan module is removed
Error Message PLATFORM-5-FEX_PS_FOUND: Fex [dec] Power Supply [dec] found (Serial
number [chars])
Explanation Fex power supply is found
Error Message PLATFORM-5-FEX_PS_REMOVE: Fex [dec] Power Supply [dec] removed

Explanation Fex power supply is removed
Error Message PLATFORM-5-MOD_STATUS: [chars] current-status is [chars]
Explanation Module in slot [decimal digit] changed status.
Error Message PLATFORM-5-PFM_NOTICE: [chars]
Explanation Platform Notice
2-354 OL-26589-01
Error Message PLATFORM-5-PS_FOUND: Power supply [dec] found (Serial number [chars])
Explanation Power Supply is detected.
Error Message PLATFORM-5-PS_STATUS: PowerSupply [dec] current-status is [chars]

[chars]
Explanation Module in slot [decimal digit] changed status.
Error Message PLATFORM-5-XBAR_PWRDN: Xbar [dec] powered down (Serial number

[chars])
Explanation The xbar in slot [decimal digit] is powered down.

showmodulexbar','showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodul
e[decimaldigit]'tocollectmoreinformationifyoususpectmodulehasbeenpowereddownduetoerrors.'
Error Message PLATFORM-5-XBAR_PWRUP: Xbar [dec] powered up (Serial number [chars])
Explanation The xbar in slot [decimal digit] is powered up.
PLATFORM-6
Error Message PLATFORM-6-PFM_INFO: [chars]
Explanation Platform Info
PLATFORM-7
Error Message PLATFORM-7-PFM_CLOCK_UPD_FAIL: Clock update failed due to

context-switch delay of [dec] msec
Explanation System shutdown in [decimal digit] seconds.
OL-26589-01 2-355
PLOG_SUP Messages
This section contains the PLOG_SUP messages.
PLOG_SUP-4
Error Message PLOG_SUP-4-PLOG_SUP_EXIT: Persistent Logger encountered an error

[dec].
Explanation Persistent Logger encountered an error
PLOG Messages
This section contains the PLOG messages.
PLOG-4
Error Message PLOG-4-PLOG_LC_EXIT: Persistent Logger encountered an error [dec]
Explanation Persistent Logger encountered an error
PONG Messages
This section contains the PONG messages.
PONG-5
Error Message PONG-5-PONG_DISABLED: Pong Manager disabled
Explanation Pong Service Enabled
Error Message PONG-5-PONG_ENABLED: Pong Manager enabled
Explanation Pong Service Enabled
2-356 OL-26589-01
Error Message PONG-5-PONG_INJECTED: Pong packet injected
Explanation Pong packet injected
PORT-CHANNEL Messages
This section contains the PORT-CHANNEL messages.
PORT-CHANNEL-1
Error Message PORT-CHANNEL-1-LC_CFG_FAILURE: configuring module [dec] failed

[[chars]]
Explanation Module configuration failed
Recommended Action Module will be automatically reset
Error Message PORT-CHANNEL-1-MALLOC_FAILED: cannot allocate memory (size [dec])
Explanation No enough memory
Error Message PORT-CHANNEL-1-MAP_PARAM_FAILURE: mapping parameter failed for

[chars] [[chars]]
Explanation Parameter mapping failed
Recommended Action Specified service is misbehaving; check its status
Error Message PORT-CHANNEL-1-MCAST_SEND_FAILURE: failed to send multicast [chars]:

[chars]
Explanation Failed to send a multicast message to all modules, usually because some module went
down
Recommended Action Run show port-channel consistency to check consistency
PORT-CHANNEL-2
Error Message PORT-CHANNEL-2-AUTO_CREATE_DISABLED: [chars] has been deprecated;

[chars] [chars]
Explanation Auto create port-channel is deprecated and disabled
Recommended Action Convert the auto created channel to presistent by doing port-channel <n
OL-26589-01 2-357
Error Message PORT-CHANNEL-2-RESET_MODULE: reset module [dec] for not responding

or returning error
Explanation A module is reset for not responding or returning error
PORT-CHANNEL-3
Error Message PORT-CHANNEL-3-COMPAT_CHECK_FAILURE: [chars] is not compatible
Recommended Action Make sure the compatibility parameters are consistent while adding ports to
port-channel, or use force option
Error Message PORT-CHANNEL-3-GENERAL_ERROR: [chars]
Error Message PORT-CHANNEL-3-LC_CFG_TIMEOUT_ENTRY_PORT_ERR_DISABLE: Failed to send

LC config due to timeout, Port [chars] Err disabled
Explanation Failed to send a lc_config message
Error Message PORT-CHANNEL-3-LC_CFG_UCAST_FAILED_PORT_ERR_DISABLE: Failed to send

LC config unicast msg, Port [chars] Err disabled
Explanation Failed to send a lc_config unicast message
Error Message PORT-CHANNEL-3-LC_CFG_UCAST_SEND_FAILURE: Failed to send LC config

Unicast msg to slot [dec] node [hex] sap [dec]: [chars]. Resetting LineCard
Explanation Failed to send a lc_config unicast message
Error Message PORT-CHANNEL-3-MSG_SEND_FAILURE: failed to send [chars] to sap [dec]:

[chars]
2-358 OL-26589-01
Error Message PORT-CHANNEL-3-PORT_CHANNEL_NOT_FOUND: [chars] is not found
Explanation Cannot find port-channel in its database, which indicates an inconsistency with an
external component
Error Message PORT-CHANNEL-3-TIMEOUT: timed out after [dec] seconds [type [chars],
state [chars]]
Explanation Some operation timed out
Recommended Action Run show port-channel consistency to check all module connectivity and
consistency
PORT-CHANNEL-4
Error Message PORT-CHANNEL-4-PORT_CFG_DELETED: [chars] removed from [chars]
Explanation Port is removed from a port-channel because different module was inserted or module
config purged
Recommended Action You lost some ports from port-channel, check if you want to add ports in the
new module to the same port-channel.
Error Message PORT-CHANNEL-4-PORT_INDIVIDUAL: port [chars] is operationally

individual
Explanation The port is operating as an individual link even though it is locally or remotely
configured to be part of a port channel
Recommended Action Check the configuration of the port locally and remotely to ensure that it can
operate as part of a port channel
Error Message PORT-CHANNEL-4-PORT_NOT_FOUND: port [chars] is not part of

port-channel
Explanation Cannot find the port in port-channel database, which indicates an inconsistency with an
external component
Error Message PORT-CHANNEL-4-RACE_WARN: [chars]
Explanation Warning of possible race condition
OL-26589-01 2-359
Error Message PORT-CHANNEL-4-UNEXPECTED_RESPONSE: unexpected response [chars] from

[chars]
Explanation Received an unexpected response and discarded
PORT-CHANNEL-5
Error Message PORT-CHANNEL-5-AUTO_CREATE_FAILURE: [chars] [chars]
Explanation Auto create process on the port failed
Error Message PORT-CHANNEL-5-CREATED: [chars] created
Explanation A port-channel is created
Error Message PORT-CHANNEL-5-DELETED: [chars] deleted
Explanation A port-channel is deleted
Error Message PORT-CHANNEL-5-FOP_CHANGED: [chars]: first operational port changed

from [chars] to [chars]
Explanation The first operational port in a port-channel is changed
Error Message PORT-CHANNEL-5-MAX_CHANNEL_DISALLOWED: Module failed to come online

because port channel interface <port-channel number
Explanation The port-channel number configured on the switch is larger than 128
Recommended Action Delete the set of port channel interface <port-channel interface
Error Message PORT-CHANNEL-5-PORT_ADDED: [chars] added to [chars]
Explanation Ports are added to a port-channel
2-360 OL-26589-01
Error Message PORT-CHANNEL-5-PORT_DOWN: [chars]: [chars] is down
Explanation Port goes down in a port-channel
Error Message PORT-CHANNEL-5-PORT_REMOVED: [chars] removed from [chars]
Explanation Ports are removed from a port-channel
Error Message PORT-CHANNEL-5-PORT_UP: [chars]: [chars] is up
Explanation Port comes up in a port-channel
PORT-CHANNEL-6
Error Message PORT-CHANNEL-6-RESYNC: resyncing [chars] with all modules
Explanation Resync modules with sup after an error or switchover
PORT-CHANNEL-7
Error Message PORT-CHANNEL-7-GSYNC_DONE: global synchronization is done
Explanation Port-channel manager finished global synchronization
Error Message PORT-CHANNEL-7-GSYNC_REQ: requesting global synchronization
Explanation Port-channel manager requested a global synchronization from active sup
Error Message PORT-CHANNEL-7-START_ACTIVE: started in active mode
Explanation Port-channel manager started in active mode
OL-26589-01 2-361
Error Message PORT-CHANNEL-7-START_DEFAULT: started with default configuration
Explanation Port-channel manager started with default configuration
Error Message PORT-CHANNEL-7-START_STANDBY: started in standby mode
Explanation Port-channel manager started in standby mode
Error Message PORT-CHANNEL-7-START_STATEFUL: started statefully
Explanation Port-channel manager started with running configuration
Error Message PORT-CHANNEL-7-START_STATELESS: started statelessly
Explanation Port-channel manager started with startup configuration
PORT-PROFILE Messages
This section contains the PORT-PROFILE messages.
PORT-PROFILE-2
Error Message PORT-PROFILE-2-IF_REFRESH_FAILED: Interface Database Refresh failed

for [chars]
Explanation Interface Database Refresh failed
PORT-PROFILE-3
Error Message PORT-PROFILE-3-ALLOC_FAILED: Failed in File:[chars] Line:[dec] for

type [dec] size [dec]
Explanation SDM process could not allocate heap memory in File:[chars], at line:[dec], for
2-362 OL-26589-01
Error Message PORT-PROFILE-3-ASSERTION_FAILED: Failed in File:[chars] Line:[dec]
Explanation PPM Process assertion failed in File:[chars], at line:[dec]
Error Message PORT-PROFILE-3-CREATE_IF_FAILED: Running-config collection Failed

for intf range [chars]
Explanation Running-config collection failed for :[chars]
Error Message PORT-PROFILE-3-IF_APPLY_FAILED: Config Apply Failed
Explanation Config Apply Failed
Error Message PORT-PROFILE-3-INTERFACE_NO_SHUTDOWN_FAILED: Interface no shutdown

failed for [chars] after profile re-inherit
Explanation Interface could not be unshut after profile re-inherit
Error Message PORT-PROFILE-3-INTERFACE_SHUTDOWN_FAILED: Interface shutdown failed

for [chars] after failure to apply commands
Explanation Interface could not be shutdown after failure to apply commands
Error Message PORT-PROFILE-3-PROFILE_CREATE_FAILED: Port-profile [chars] creattion

failed with error "[chars]"
Explanation Port-profile:[chars] creation failed with [:chars]
Error Message PORT-PROFILE-3-PROFILE_DEINHERIT_FAILED: Port-profile [chars]

de-inherit failed with error [chars] on [chars]
Explanation Port-profile:[chars] de-inherit failed with [:chars] on [:chars]
OL-26589-01 2-363
Error Message PORT-PROFILE-3-PROFILE_DELETE_FAILED: Port-profile [chars] is

deletion failed with error "[chars]"
Explanation Port-profile:[chars] deletion failed with [:chars]
Error Message PORT-PROFILE-3-PROFILE_DISABLE_FAILED: Port-profile [chars] disable

Explanation Port-profile:[chars] disable failed with [:chars]
Error Message PORT-PROFILE-3-PROFILE_ENABLE_FAILED: Port-profile [chars] enable

Explanation Port-profile:[chars] enable failed with [:chars]
Error Message PORT-PROFILE-3-PROFILE_INHERIT_FAILED: Port-profile [chars] inherit

failed with error [chars] on [chars]
Explanation Port-profile:[chars] inherit failed with [:chars] on [:chars]
PORT-PROFILE-6
Error Message PORT-PROFILE-6-PROFILE_CREATED: Port-profile [chars] is created

successfully
Explanation Port-profile:[chars] is created
Error Message PORT-PROFILE-6-PROFILE_DEINHERITED: Port-profile [chars] is

de-inherited successfully on [chars]
Explanation Port-profile:[chars] is de-inherited on [:chars]
2-364 OL-26589-01
Error Message PORT-PROFILE-6-PROFILE_DELETED: Port-profile [chars] is deleted

successfully
Explanation Port-profile:[chars] is deleted
Error Message PORT-PROFILE-6-PROFILE_DISABLED: Port-profile [chars] is disabled

successfully
Explanation Port-profile:[chars] is disabled
Error Message PORT-PROFILE-6-PROFILE_ENABLED: Port-profile [chars] is enabled

successfully
Explanation Port-profile:[chars] is enabled
Error Message PORT-PROFILE-6-PROFILE_INHERITED: Port-profile [chars] is inherited

successfully on [chars]
Explanation Port-profile:[chars] is inherited on [:chars]
PORT-RESOURCES Messages
This section contains the PORT-RESOURCES messages.
PORT-RESOURCES-3
Error Message PORT-RESOURCES-3-PRM_MSG_SEND_FAILURE: failed to send [chars] to sap

[dec]: [chars]
OL-26589-01 2-365
PORT-RESOURCES-5
Error Message PORT-RESOURCES-5-INVALID_PORT_ACTIV_PKG_LICENSE_FILE_INSTALLED:

Invalid on demand port activation license file is installed for module [dec]
(number of port licenses = [dec])
Explanation Interfaces may not acquire port activation licenes during installation
Recommended Action Install a valid port activation license file
PORT-SECURITY Messages
This section contains the PORT-SECURITY messages.
PORT-SECURITY-2
Error Message PORT-SECURITY-2-ALLOC_FAILED: Memory allocation failed for size:[dec]

for [chars]
Explanation Memory allocation failed for size [dec] for [chars]
Error Message PORT-SECURITY-2-FEATURE_DISABLED: Feature [chars] disabled due to

[chars]
Explanation Feature [chars] is unavailable and will be disabled now
Recommended Action Please install the correct license and reenable
PORT-SECURITY-3
Error Message PORT-SECURITY-3-BINDING_CONFLICT: [chars]
Explanation An already logged in device is in conflict with the PSM active binding configurations.
[chars] indicates the WWN of the login entity, interface
Recommended Action For port-security, the auto-learn feature can be used with activation to prevent
this. This violating device or switch will be logged out
2-366 OL-26589-01
Error Message PORT-SECURITY-3-BINDING_VIOLATION: [chars]
Explanation A login happend that violates PSM binding configurations [chars] indicates the WWN
of the login entity
Recommended Action Only entries in the activated database of PSM can login. Change the config
and activate it again
Error Message PORT-SECURITY-3-CFS_NOTIF_ERR: [chars]
Explanation An error occurred during the processing of a CFS notification. [chars] indicates the
actual cause for the error
Error Message PORT-SECURITY-3-DB_ERR: [chars]
Explanation An error occurred during an PSM database operation. [chars] indicates the reason for
the error
Error Message PORT-SECURITY-3-EFMD_FC2_OPER_FAILED: [chars]
Explanation EFMD fc2 operation failed
Error Message PORT-SECURITY-3-EFMD_INIT_FAILED: [chars]
Explanation EFMD init failed
Error Message PORT-SECURITY-3-EFMD_MERGE_UNKNOWN_FORMAT: [chars]
Explanation Received a corrupted EFMD Request Packet
OL-26589-01 2-367
Error Message PORT-SECURITY-3-INIT_FAIL: [chars]
Explanation An error happened during PSM Initialization. [chars] indicates the reason for failure
Error Message PORT-SECURITY-3-LEARNT_BINDING_CONFLICT: [chars]
Explanation An already logged in device that is learnt during activation is in conflict with the PSM
active binding configurations. [chars] indicates the WWN of the login entity, interface
Recommended Action Copy the active-db to config-db and reactivate. Not doing so could result in
unexpected login rejects later on that interface.
Error Message PORT-SECURITY-3-MTS_ERR: [chars]
Explanation An error occurred in processing of an MTS message. [chars] indicates the error that
occurred
Error Message PORT-SECURITY-3-PSS_ERR: [chars]
Explanation An error occurred during an PSM PSS operation. [chars] indicates the PSS operation
Error Message PORT-SECURITY-3-PSS_VER_FAIL: PSS file [chars] has version

[dec].[dec].[dec], expected version [dec].[dec].[dec]
PORT-SECURITY-4
Error Message PORT-SECURITY-4-ACTIVATION_FAIL: [chars]
Explanation Activation of bindings failed due to [chars]
Recommended Action Correct the error and reactivate it again
2-368 OL-26589-01
PORT-SECURITY-6
Error Message PORT-SECURITY-6-INFO: [chars]
Explanation An event happend that affects PSM. [chars] indicates the event
PORT Messages
This section contains the PORT messages.
PORT-2
Error Message PORT-2-IF_DOWN_ERROR_DISABLED: Interface [chars] is down (Error

disabled) [chars] [chars]
Explanation The interface encountered an error while configuring it. [optionally if the port belongs
to port-channel, the port-channel number to which the port belongs will be displayed and if interface
description is configured, the interface description is displayed]
showportinternalallinterface[char]'.Inmostcases,youcanrecoverusingfollowingcommands'configter
minal','interface[char]','shutdown','noshutdown'ontheinterfaceorremovingandre-insertingthefibreo
pticcable'
Error Message PORT-2-IF_DOWN_LINK_FAILURE_CRIT: Interface [chars] is down (Link

failure)
Explanation The physical link has gone down
PORT-3
Error Message PORT-3-IF_SFP_ALARM: Interface [chars], [chars] [chars] [chars]
Explanation There was an alarm on the transceiver module. [optionally if the port belongs to
port-channel, the port-channel number to which the port belongs will be displayed and if interface
OL-26589-01 2-369
Error Message PORT-3-IF_TRANSCEIVER_READ_ERROR: Transceiver read error for

interface [chars] [chars] [chars]
Explanation Transceiver eeprom read failed. [optionally if the port belongs to port-channel, the
port-channel number to which the port belongs will be displayed and if interface description is
configured, the interface description is displayed]
Recommended Action Remove and insert the SFP back again. If the problem persists check if the
transceiver is supported using the command: show interface transceiver. Please contact customer
support to resolve the condition
Error Message PORT-3-IF_UNSUPPORTED_TRANSCEIVER: Transceiver for interface [chars]

is not supported
Explanation Transceiver is not from an authorized vendor
Recommended Action This command will determine the transceiver being used: show interface
transceiver. Please contact customer support for a list of authorized transceiver vendors
PORT-4
Error Message PORT-4-IF_NON_QUALIFIED_TRANSCEIVER: Non-qualified transceiver on

interface [chars] was detected
Explanation The transceiver for the interface specified has not been qualified on this platform for
this software release
Recommended Action Replace the module with a supported transceiver. Contact Cisco TAC to get
platform transceiver qualification details
Error Message PORT-4-IF_SFP_CLK_RATE_ERROR: SFP clock rate error for interface

[chars] [chars] [chars]
Explanation SFP clock rate mismatch/failed. [optionally if the port belongs to port-channel, the
Recommended Action Remove the SFP and insert a new one with a different frequency type. If the
problem persists check if the transceiver is supported using the command: show interface
transceiver. Please contact customer support to resolve the condition
Error Message PORT-4-IF_SFP_WARNING: Interface [chars], [chars] [chars] [chars]
Explanation There was an warning on the transceiver module. [optionally if the port belongs to
2-370 OL-26589-01
Error Message PORT-4-IF_TRUSTSEC_VIOLATION: Interface [chars] encountered port

security violation [chars] [chars]
Explanation The port has detected port security violation. [optionally if the port belongs to
Recommended Action Check port security configs on interface
PORT-5
Error Message PORT-5-EC_DISABLED_AS_LICENSE_NOT_PRESENT: Extended credit feature

has been disabled as Enterprise Package license could not be checked out
Explanation The Enterprise Package license is not available, so the extened credit feature has been
disabled even though it was present in startup config
Recommended Action Install the Enterprise Package license and re-enable the extended credit feature
Error Message PORT-5-IF_BRINGUP_ALLOWED_FCOT_CHECKSUM_ERR: Interface [chars] is

allowed to come up even with SFP checksum error [chars] [chars]
Explanation SFP checksum on this interface failed. [optionally if the port belongs to port-channel,
the port-channel number to which the port belongs will be displayed and if interface description is
Recommended Action Try to replace the SFP on this interface
Error Message PORT-5-IF_BRINGUP_FAILED_ALL_ZERO_PEER_WWN_RCVD: Interface [chars],

is not allowed to come up (received as all zeros wwn from peer [chars] [chars]
Explanation Check peer interface configuration. [optionally if the port belongs to port-channel, the
Error Message PORT-5-IF_BRINGUP_NOT_ALLOWED_PORT_CONFIG_FAILURE: Interface

[chars] is not allowed to be operational due to port config failure for reason:
[chars] ([hex]) [chars] [chars]
Explanation Check interface configuration. [optionally if the port belongs to port-channel, the
Recommended Action Try to change the configuration on the interface with the current available
hardware capability
OL-26589-01 2-371
Error Message PORT-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is down

(Administratively down) [chars] [chars]
Explanation Interface has been configured to be administratively down. [optionally if the port
belongs to port-channel, the port-channel number to which the port belongs will be displayed and if
interface description is configured, the interface description is displayed]
Recommended Action Perform the following commands to bring up the interface:

configterminal','interface[char]','noshutdown''
Error Message PORT-5-IF_DOWN_BIT_ERR_RT_THRES_EXCEEDED: Interface [chars] is down

(Error disabled - bit error rate too high) [chars] [chars]
Explanation The port has detected too high bit error rate in frames received from attached device.
[optionally if the port belongs to port-channel, the port-channel number to which the port belongs
will be displayed and if interface description is configured, the interface description is displayed]
Recommended Action Check the attached device; replace it if needed
Error Message PORT-5-IF_DOWN_BUNDLE_MISCFG: Interface [chars] is down (Isolation

due to channel mis-configuration on local or remote switch) [chars] [chars]
Explanation One port across a link is part of a PortChannel while the other is not. [optionally if the
port belongs to port-channel, the port-channel number to which the port belongs will be displayed
and if interface description is configured, the interface description is displayed]
Recommended Action While adding or deleting a member port from a PortChannel, both ports across
the link should be added/deleted. No operation should be performed on either ports until they are
both added/deleted.
Error Message PORT-5-IF_DOWN_CFG_CHANGE: Interface [chars] is down(Config change)

[chars] [chars]
Explanation FCIP interface temporarily down due to reconfiguration. [optionally if the port belongs
Error Message PORT-5-IF_DOWN_CHANNEL_ADMIN_DOWN: Interface [chars] is down

(Channel admin down) [chars] [chars]
Explanation This interface belongs to a PortChannel and the PortChannel is configured to be

administratively down. [optionally if the port belongs to port-channel, the port-channel number to
which the port belongs will be displayed and if interface description is configured, the interface
description is displayed]
Recommended Action Perform the following commands on the PortChannel interface to which it
belongs to bring the interface up: configterminal','interface[char]','shutdown','noshutdown''
2-372 OL-26589-01
Error Message PORT-5-IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS: Interface

[chars] is down (Channel membership update in progress) [chars] [chars]
Explanation The interface belongs to a PortChannel and a configuration is being attempted on the
interface while there is a configuration in progress on the PortChannel. [optionally if the port
Recommended Action Retry the configuration again
Error Message PORT-5-IF_DOWN_DENIED_DUE_TO_PORT_BINDING: Interface [chars] is

down(Suspended due to port binding) [chars] [chars]
Explanation The F port is suspended due to being denied by port binding. [optionally if the port
Recommended Action Please check the port binding database to allow the host port to log in.
Error Message PORT-5-IF_DOWN_DOMAIN_ADDR_ASSIGN_FAILURE_ISOLATION: Interface

[chars] is down (Isolation due to domain id assignment failure) [chars] [chars]
Explanation Isolated due to a failure while assigning a domain. [optionally if the port belongs to
Error Message PORT-5-IF_DOWN_DOMAIN_ID_MISMATCH_ISOLATION: Interface [chars] is

isolated (configured fcdomain ID is different from runtime config) [chars] [chars]
Explanation The runtime fcdomain ID does not equal the static configured fcdomain ID. [optionally
if the port belongs to port-channel, the port-channel number to which the port belongs will be
displayed and if interface description is configured, the interface description is displayed]
Recommended Action Ensure that the fcdomain ID configuration matches the runtime config.
Error Message PORT-5-IF_DOWN_DOMAIN_INVALID_RCF_RECEIVED: Interface [chars] is

down (Isolation due to invalid fabric reconfiguration) [chars] [chars]
Explanation Invalid RCF received. [optionally if the port belongs to port-channel, the port-channel
number to which the port belongs will be displayed and if interface description is configured, the
interface description is displayed]
OL-26589-01 2-373
Error Message PORT-5-IF_DOWN_DOMAIN_MANAGER_DISABLED: Interface [chars] is down

(Isolation due to domain manager disabled) [chars] [chars]
Explanation Isolated due to domain manager being disabled. [optionally if the port belongs to
Error Message PORT-5-IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE: Interface [chars]

is down (Isolation due to domain manager other side not responding) [chars] [chars]
Explanation Remote end domain manager not responding. [optionally if the port belongs to
Error Message PORT-5-IF_DOWN_DOMAIN_NOT_ALLOWED_ISOLATION: Interface [chars] is

isolated (domain not allowed) [chars] [chars]
Explanation There
arentenoughalloweddomainstomergetheVSANsacrossthelink.[optionallyiftheportbelongstoport-ch
annel,theport-channelnumbertowhichtheportbelongswillbedisplayedandifinterfacedescriptioniscon
figured,theinterfacedescriptionisdisplayed]'
Recommended Action Ensure that all assigned domain

idsareintheconfiguredalloweddomainsonbothsidesofthelink.'
Error Message PORT-5-IF_DOWN_DOMAIN_OTHER_SIDE_EPORT_ISOLATED: Interface [chars]

is down (Isolation due to domain other side eport isolated) [chars] [chars]
Explanation Isolating this interface due to the remote end being isolated. [optionally if the port
Error Message PORT-5-IF_DOWN_DOMAIN_OVERLAP_ISOLATION: Interface [chars] is down

(Isolation due to domain overlap) [chars] [chars]
Explanation Isolated due to domain overlap. [optionally if the port belongs to port-channel, the
2-374 OL-26589-01
Error Message PORT-5-IF_DOWN_DPVM_VSAN_NOT_FOUND: Interface [chars] is down

(dynamic vsan not present) [chars] [chars]
Explanation The specified dynamic vsan is not configured on this switch. [optionally if the port
Recommended Action Configure the dynamic vsan.
Error Message PORT-5-IF_DOWN_DPVM_VSAN_SUSPENDED: Interface [chars] is down

(dynamic vsan in suspended state) [chars] [chars]
Explanation The specified dynamic vsan is in suspended state. [optionally if the port belongs to
Recommended Action Un-suspend the dynamic vsan.
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_CLASSF_PARAM_ERR: Interface

[chars] is down (Isolation due to ELP failure: class F param error) [chars] [chars]
Explanation ELP failed on the interface due to class F param error. [optionally if the port belongs
Recommended Action Configure the attached switchport correctly and try again
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_CLASSN_PARAM_ERR: Interface

[chars] is down (Isolation due to ELP failure: class N param error) [chars] [chars]
Explanation ELP failed on the interface due to class N param error. [optionally if the port belongs
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_PAYLOAD_SIZE:

Interface [chars] is down (Isolation due to ELP failure: invalid payload size)
Explanation ELP failed on the interface due to invalid payload size
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_PORT_NAME: Interface

[chars] is down (Isolation due to ELP failure: invalid port name) [chars] [chars]
Explanation ELP failed on the interface due to invalid port name. [optionally if the port belongs to
OL-26589-01 2-375
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_SWITCH_NAME: Interface

[chars] is down (Isolation due to ELP failure: invalid switch name) [chars] [chars]
Explanation ELP failed on the interface due to invalid switch name. [optionally if the port belongs
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_TX_BBCREDIT: Interface

[chars] is down (Isolation due to ELP failure: loopback detected) [chars] [chars]
Explanation ELP failed on the interface due to loopback connection detected. [optionally if the port
Recommended Action Connect to a port on another switch and try again
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_LOOPBACK_DETECTED: Interface

[chars] is down (Isolation due to ELP failure: invalid transmit B2B credit) [chars]
[chars]
Explanation ELP failed on the interface due to invalid transmit B2B credit. [optionally if the port
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_RATOV_EDTOV_MISMATCH:

Interface [chars] is down (Isolation due to ELP failure: R_A_TOV or E_D_TOV
mismatch) [chars] [chars]
Explanation ELP failed on the interface due to R_A_TOV or E_D_TOV mismatch. [optionally if
the port belongs to port-channel, the port-channel number to which the port belongs will be
Recommended Action Configure R_A_TOV and E_D_TOV values correctly and try again
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_REVISION_MISMATCH: Interface

[chars] is down (Isolation due to ELP failure: revision mismatch) [chars] [chars]
Explanation ELP failed on the interface due to revision mismatch. [optionally if the port belongs to
2-376 OL-26589-01
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_UNKNOWN_FLOW_CTL_CODE:

Interface [chars] is down (Isolation due to ELP failure: invalid flow control code)
[chars] [chars]
Explanation ELP failed on the interface due to invalid flow control code. [optionally if the port
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION_UNKNOWN_FLOW_CTL_PARAM:

Interface [chars] is down (Isolation due to ELP failure: invalid flow control
param) [chars] [chars]
Explanation ELP failed on the interface due to invalid flow control param. [optionally if the port
Error Message PORT-5-IF_DOWN_ELP_FAILURE_ISOLATION: Interface [chars] is down

(Isolation due to ELP failure) [chars] [chars]
Explanation ELP failed on the interface. [optionally if the port belongs to port-channel, the
Recommended Action Check the output of showportinternalinfo'inthe'ELPfailurereason'field'
Error Message PORT-5-IF_DOWN_EPP_FAILURE: Interface [chars] is down (Error

Disabled - EPP Failure) [chars] [chars]
Explanation Trunk protocol failed. [optionally if the port belongs to port-channel, the port-channel
Recommended Action
showportinternalevent-historymsgs'willindicatethetrunkprotocolexchangestodeterminewhyitfailed'
Error Message PORT-5-IF_DOWN_ESC_FAILURE_ISOLATION: Interface [chars] is down

(Isolation due to ESC failure) [chars] [chars]
Explanation ESC failed on the interface. [optionally if the port belongs to port-channel, the
Recommended Action Check the output of

showportinternalevent-history'todeterminetheESCprotocolexchangestodeterminehowitfailed'
OL-26589-01 2-377
Error Message PORT-5-IF_DOWN_ETH_IF_DOWN: Interface [chars] is down(Tunnel port

src interface down) [chars] [chars]
Explanation Ethernet link to which the FCIP interface is bound is down. [optionally if the port
Recommended Action Ensure that the ethernet cable is connected, the interface is administratively
enabled
Error Message PORT-5-IF_DOWN_ETH_LINK_DOWN: Interface [chars] is down(Tunnel port

src interface link down) [chars] [chars]
Explanation Ethernet link to which the FCIP interface is bound is down. [optionally if the port
Recommended Action Ensure that the ethernet cable is connected and the remote end is also active
Error Message PORT-5-IF_DOWN_FABRIC_BIND_FAILURE: Interface [chars] is

down(Isolation due to fabric bind failure) [chars] [chars]
Explanation Fabric binding failed on this port. [optionally if the port belongs to port-channel, the
Recommended Action Please check the fabric binding database to ensure that the remote port is
allowed to connect to this port
Error Message PORT-5-IF_DOWN_FCOT_NOT_PRESENT: Interface [chars] is down (FCOT not

present) [chars] [chars]
Explanation The FCOT has been removed. [optionally if the port belongs to port-channel, the
Error Message PORT-5-IF_DOWN_FCOT_REMOVED: Interface [chars] is down (FCOT has been

removed) [chars] [chars]
Explanation The FCOT has been removed. [optionally if the port belongs to port-channel, the
2-378 OL-26589-01
Error Message PORT-5-IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED: Interface [chars] is down

(Error disabled - FCOT vendor not supported) [chars] [chars]
Explanation FCOT inserted is not a supported one. [optionally if the port belongs to port-channel,
Recommended Action Please contact customer support for a list of authorized transceiver vendors
Error Message PORT-5-IF_DOWN_FCSP_AUTHENT_FAILURE: Interface [chars] is down

(FC-SP authentication failure) [chars] [chars]
Explanation The port failed FC-SP authentication with its peer. [optionally if the port belongs to
Recommended Action Please check the FC-SP configuration.
Error Message PORT-5-IF_DOWN_FICON_BEING_ENABLED: Interface [chars] is down(FICON

being enabled) [chars] [chars]
Explanation FICON is being enabled on the port. [optionally if the port belongs to port-channel, the
Recommended Action Please wait. This might take a while
Error Message PORT-5-IF_DOWN_FICON_NOT_ENABLED: Interface [chars] is down(Error

disabled - FICON not enabled) [chars] [chars]
Explanation FICON not enabled on port. [optionally if the port belongs to port-channel, the
Recommended Action Please enable FICON on port
Error Message PORT-5-IF_DOWN_FICON_VSAN_DOWN: Interface [chars] is down(FICON vsan

down) [chars] [chars]
Explanation FICON is being enabled on the port VSAN of this port. [optionally if the port belongs
Recommended Action This is an intermediary state, whereby the port VSAN of the port is being
enabled to be a FICON VSAN.
OL-26589-01 2-379
Error Message PORT-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware

Failure) [chars] [chars]
Explanation The
moduleshardwarehasfailed.[optionallyiftheportbelongstoport-channel,theport-channelnumbertowh
ichtheportbelongswillbedisplayedandifinterfacedescriptionisconfigured,theinterfacedescriptionisdi
splayed]'
Recommended Action Collect more information about failed module using command
showmoduleinternalallmodule''
Error Message PORT-5-IF_DOWN_INACTIVE: Interface [chars] is down (Inactive)

[chars] [chars]
Explanation The port VSAN has been suspended or deleted. [optionally if the port belongs to
Recommended Action Assign a new active port VSAN to the interface
Error Message PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_MODE: Interface [chars] is down

(Error disabled - Incompatible admin port mode) [chars] [chars]
Explanation The configured mode is not supported on this interface. [optionally if the port belongs

showportinternalinfo'todeterminethelistofmodessupportedonthisinterface'
Error Message PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBBCREDIT: Interface [chars] is

down (Error disabled - Incompatible admin port rxbbcredit) [chars] [chars]
Explanation The configured receive B2B credit size is not supported. [optionally if the port belongs
Recommended Action Get the allowed receive B2B credit size from showportinternalinfo''
Error Message PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_RXBUFSIZE: Interface [chars] is

down (Error disabled - Incompatible admin port rxbufsize) [chars] [chars]
Explanation The configured receive buffer size is not supported. [optionally if the port belongs to
Recommended Action Get the allowed receive buffer size from showportinternalinfo''
2-380 OL-26589-01
Error Message PORT-5-IF_DOWN_INCOMPATIBLE_ADMIN_SPEED: Interface [chars] is down

(Error disabled - Incompatible admin port speed) [chars] [chars]
Explanation The configured speed is not supported on this interface. [optionally if the port belongs

showportinternalinfo'todeterminetherangeofspeedsupportedonthisinterface'
Error Message PORT-5-IF_DOWN_INITIALIZING: Interface [chars] is down

(Initializing) [chars] [chars]
Explanation The interface is in the process of coming up. [optionally if the port belongs to
Recommended Action If the interface is stuck in this state for a while, check the output of
showportinternalevent-history'todeterminewhatitiswaitingfor'
Error Message PORT-5-IF_DOWN_INTERFACE_REMOVED: Interface [chars] is down

(Interface removed) [chars] [chars]
Explanation Interface removed. [optionally if the port belongs to port-channel, the port-channel
Error Message PORT-5-IF_DOWN_INVALID_ATTACHMENT: Interface [chars] is down(Invalid

attachment) [chars] [chars]
Explanation The peer port does not have the compatible security attributes. [optionally if the port
Recommended Action Please ensure that the peer port has compatible security attributes as the local
port.
Error Message PORT-5-IF_DOWN_INVALID_CONFIG: Interface [chars] is down(Error

disabled - Possible PortChannel misconfiguration) [chars] [chars]
Explanation The local and peer port have a PortChannel membership misconfiguration. [optionally
Recommended Action Ensure that both the local and peer ports are either both members of the same
PortChannel or are not both part of PortChannel
OL-26589-01 2-381
Error Message PORT-5-IF_DOWN_INVALID_FABRIC_BINDING: Interface [chars] is

down(Invalid fabric binding exchange) [chars] [chars]
Explanation Fabric binding failed. [optionally if the port belongs to port-channel, the port-channel
Recommended Action Please check fabric binding database
Error Message PORT-5-IF_DOWN_LINK_FAILURE: Interface [chars] is down (Link failure

[chars]) [chars] [chars]
Explanation The physical link has gone down. [optionally if the port belongs to port-channel, the
Error Message PORT-5-IF_DOWN_LOCALLY_DISRUPTIVE_RECONFIGURATION: Interface [chars]

is down (fcdomain applied a locally disruptive reconfiguration) [chars] [chars]
Explanation Fcdomain applied a locally disruptive reconfiguration (local domain became invalid.
Error Message PORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE: Interface [chars] is down

(Diag failure) [chars] [chars]
Explanation Diag failed on the interface. [optionally if the port belongs to port-channel, the
attachmodule'toconnecttomodule'
Error Message PORT-5-IF_DOWN_LOOPBACK_ISOLATION: Interface [chars] is down

(Isolation due to port loopback to same switch) [chars] [chars]
Explanation The interface is looped back to another interface on the same switch. [optionally if the
another switch
2-382 OL-26589-01
Error Message PORT-5-IF_DOWN_MODULE_REMOVED: Interface [chars] is down (module

removed) [chars] [chars]
Explanation Interface is down because the module was removed. [optionally if the port belongs to
Error Message PORT-5-IF_DOWN_NONE: Interface [chars] is down (None) [chars] [chars]
Explanation There is no apparent reason the interface is down. [optionally if the port belongs to
Recommended Action Collect more information about port using command

showportinternalallinterface[char]'todeterminewhyitwentdown'
Error Message PORT-5-IF_DOWN_NON_PARTICIPATING: Interface [chars] is down (Non

participating) [chars] [chars]
Explanation The loop port has been put into non participating mode. [optionally if the port belongs
Error Message PORT-5-IF_DOWN_NOS_RCVD: Interface [chars] is down (NOS received)

[chars] [chars]
Error Message PORT-5-IF_DOWN_NO_TRUNK_OPER_VSANS_ISOLATION: Interface [chars] is

down(Isolation due to no common vsans with peer on trunk) [chars] [chars]
Explanation The trunk port is isolated as there are no common VSANs to be brought up with the
peer port. [optionally if the port belongs to port-channel, the port-channel number to which the port
belongs will be displayed and if interface description is configured, the interface description is
displayed]
Recommended Action Please check that there are common VSANs configured and allowed to come
up between the ports.
OL-26589-01 2-383
Error Message PORT-5-IF_DOWN_OFFLINE: Interface [chars] is down (Offline) [chars]

[chars]
Explanation The interface has been placed into the offline state. [optionally if the port belongs to
Error Message PORT-5-IF_DOWN_OHMS_EXTERNAL_LB_TEST: Interface [chars] is

down(Loopback test) [chars] [chars]
Explanation Loopback tests. [optionally if the port belongs to port-channel, the port-channel
Recommended Action Please wait. This might take a while
Error Message PORT-5-IF_DOWN_OLS_RCVD: Interface [chars] is down (OLS received)

[chars] [chars]
Error Message PORT-5-IF_DOWN_PARENT_ADMIN_DOWN: Interface [chars] is down (Parent

interface down) [chars] [chars]
Explanation Parent interface is down. [optionally if the port belongs to port-channel, the
Error Message PORT-5-IF_DOWN_PEER_CLOSE: Interface [chars] is down(TCP conn.

closed by peer) [chars] [chars]
Explanation The FCIP peer connected to this interface closed the TCP connection. [optionally if the
Recommended Action This command will provide the peer IP address of this FCIP interface: show
interface. Check to see why the peer closed the TCP connection
2-384 OL-26589-01
Error Message PORT-5-IF_DOWN_PEER_RESET: Interface [chars] is down(TCP conn. reset

by peer) [chars] [chars]
Explanation TCP connection to the FCIP peer got reset. [optionally if the port belongs to
Recommended Action The following commands will provide the IP address of the peer and the route
used connect to this FCIP peer: show interface, show ip route. Check to see why the peer reset the
TCP connection
Error Message PORT-5-IF_DOWN_PORT_ACT_LICENSE_NOT_AVAILABLE: Interface [chars] is

not allowed to come up (port activation license not available [chars] [chars]
Explanation Assign a port activation license to this port or install additional port activation licenses
as needed. [optionally if the port belongs to port-channel, the port-channel number to which the port
belongs will be displayed and if interface description is configured, the interface description is
displayed]
Error Message PORT-5-IF_DOWN_PORT_BIND_FAILURE: Interface [chars] is

down(Isolation due to port bind failure) [chars] [chars]
Explanation Port binding failed on this port. [optionally if the port belongs to port-channel, the
Recommended Action Please check the port binding database to ensure that the remote port is
allowed to connect to this port
Error Message PORT-5-IF_DOWN_PORT_BLOCKED: Interface [chars] is down(Port blocked

due to FICON) [chars] [chars]
Explanation The port has been blocked by FICON configuration. [optionally if the port belongs to
Recommended Action Please unblock the port in FICON configuration.
Error Message PORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: Interface [chars] is down

(No operational members) [chars] [chars]
Explanation This is a PortChannel interface and all its members are operationally down. [optionally
Recommended Action Enable at least one of the PortChannelsmembers'
OL-26589-01 2-385
Error Message PORT-5-IF_DOWN_PORT_VSAN_MISMATCH_ISOLATION: Interface [chars] is

down (Isolation due to port VSAN mismatch) [chars] [chars]
Explanation Isolated due to a mismatch in the configured port VSAN of the local and remote ends.
Recommended Action Configure the port VSAN of the local and remote interfaces to be the same and
perform a shutdown'anda'noshutdown''
Error Message PORT-5-IF_DOWN_RCF_IN_PROGRESS: Interface [chars] is down (RCF in

progress) [chars] [chars]
Explanation There is an RCF in progress. [optionally if the port belongs to port-channel, the
Error Message PORT-5-IF_DOWN_SOFTWARE_FAILURE: Interface [chars] is down (Port

software failure) [chars] [chars]
Explanation The software servicing the data path on the port has failed. [optionally if the port
Error Message PORT-5-IF_DOWN_SRC_MOD_NOT_ONLINE: Interface [chars] is down(Tunnel

source module not online) [chars] [chars]
Explanation Module that has the tunnel source port of this FCIP interface is not fully online.
Recommended Action The module that has the tunnel src port is coming online. Please use show mod
to find module status
Error Message PORT-5-IF_DOWN_SRC_PORT_NOT_BOUND: Interface [chars] is down (Tunnel

port src interface unbound) [chars] [chars]
Explanation Tunnel port source interface unbound. [optionally if the port belongs to port-channel,
2-386 OL-26589-01
Error Message PORT-5-IF_DOWN_SRC_PORT_REMOVED: Interface [chars] is down(Tunnel

src port removed) [chars] [chars]
Explanation Tunnel source port of this FCIP interface has been removed. [optionally if the port
Recommended Action The src interface with ip address that matches the ip address of the bound
entity is removed. This happens normally due to the module on which the src interface exists is
removed
Error Message PORT-5-IF_DOWN_SUSPENDED_BY_MODE: Interface [chars] is down

(Suspended due to incompatible mode) [chars] [chars]
Explanation This interface belongs to a PortChannel and operational mode of the interface is
different from that of the PortChannel. [optionally if the port belongs to port-channel, the
Recommended Action Change the mode and the trunking mode of the PortChannel from
Error Message PORT-5-IF_DOWN_SUSPENDED_BY_SPEED: Interface [chars] is down

(Suspended due to incompatible speed) [chars] [chars]
Explanation This interface belongs to a PortChannel and operational speedode of the interface is
Recommended Action Change the speed of the PortChannel from

Error Message PORT-5-IF_DOWN_SUSPENDED_BY_WWN: Interface [chars] is down

(Suspended due to incompatible remote switch WWN) [chars] [chars]
Explanation This interface belongs to a PortChannel and remote switch WWN of the interface is
Recommended Action Ensure that this interface is connected to the same remote switch as all the
other interfaces in the PortChannel
OL-26589-01 2-387
Error Message PORT-5-IF_DOWN_SUSPENDED: Interface [chars] is down (Suspended)

[chars] [chars]
Explanation This interface belongs to a PortChannel and has been suspended to to an error while
bringing it up. [optionally if the port belongs to port-channel, the port-channel number to which the
port belongs will be displayed and if interface description is configured, the interface description is
displayed]
Recommended Action In most cases, you can recover using following commands
configterminal','interface[char]','shutdown','noshutdown'ontheinterface.Ifthishappensagainobtaino
utputof'showportinternalallinterface[char]'ontheinterface'
Error Message PORT-5-IF_DOWN_TCP_KEEP_ALIVE_EXPIRED: Interface [chars] is down(TCP

conn. closed - Keep alive expired) [chars] [chars]
Explanation TCP session to the FCIP peer got closed due to loss of TCP keep alive. [optionally if
ipaddr
Error Message PORT-5-IF_DOWN_TCP_MAX_RETRANSMIT: Interface [chars] is down(TCP

conn. closed - retransmit failure) [chars] [chars]
Explanation Interface is down due to maximum retransmission failure. [optionally if the port
ipaddr
Error Message PORT-5-IF_DOWN_TCP_PERSIST_TIMER_EXPIRED: Interface [chars] is

down(TCP conn. closed - Persist timer expired) [chars] [chars]
Explanation TCP session to the FCIP peer closed because TCP persist timer expired. [optionally if
ipaddr
2-388 OL-26589-01
Error Message PORT-5-IF_DOWN_TOO_MANY_INTR: Interface [chars] is down (Error

disabled - too many interrupts) [chars] [chars]
Explanation The port has received too many interrupts in the hardware. [optionally if the port
Recommended Action Check the attached device; replace it if needed
Error Message PORT-5-IF_DOWN_TOO_MANY_INVALID_FLOGIS: Interface [chars] is

down(Suspended due to too many invalid flogis [chars] [chars]
Explanation The port is suspended due to receiving a large number of invalid

FLOGIs.[optionallyiftheportbelongstoport-channel,theport-channelnumbertowhichtheportbelongs
willbedisplayedandifinterfacedescriptionisconfigured,theinterfacedescriptionisdisplayed]'
Recommended Action Please check the HBA and perform a shut, followed by no shut on the port.
Error Message PORT-5-IF_DOWN_UPGRADE_IN_PROGRESS: Interface [chars] is down

(Linecard upgrade in progress) [chars] [chars]
Explanation Upgrade of the linecard software is in progress. [optionally if the port belongs to
Error Message PORT-5-IF_DOWN_VIRTUAL_IVR_DOMAIN_OVERLAP_ISOLATION: Interface

[chars] is down (Isolation due to virtual IVR domain overlap) [chars] [chars]
Explanation Isolated due to virtual IVR domain overlap. [optionally if the port belongs to
Error Message PORT-5-IF_DOWN_VSAN_MISMATCH_ISOLATION: Interface [chars] is down

(Isolation due to vsan mismatch) [chars] [chars]
Explanation This is a trunking interface and the VSANs configured do not match with the VSANs
configured on the remote end. [optionally if the port belongs to port-channel, the port-channel
Recommended Action Check the VSANs configured on the local end with the remote end
OL-26589-01 2-389
Error Message PORT-5-IF_DOWN_ZONE_MERGE_FAILURE_ISOLATION: Interface [chars] is

down (Isolation due to zone merge failure) [chars] [chars]
Explanation Isolated due to a failure during zone merge. [optionally if the port belongs to
Error Message PORT-5-IF_DOWN_ZONE_REMOTE_NO_RESP_ISOLATION: Interface [chars] is

down (Isolation due to remote zone server not responding) [chars] [chars]
Explanation Isolated due to remote zone server not responding. [optionally if the port belongs to
Error Message PORT-5-IF_PORT_GUARD_DOWN: Interface [chars] is down ([chars])

[chars] [chars]
Explanation The interface is down due to port guard configuration. [optionally if the port belongs
Recommended Action Perform a shut followed by no shut to bring up the interface
Error Message PORT-5-IF_PORT_QUIESCE_FAILED: Interface [chars] port quiesce failed

due to failure reason: [chars] ([hex])
Explanation There may be few packet drops due to this failure
Error Message PORT-5-IF_PSS_DUPLICATE_KEY: Duplicate key found for Interface

[chars]
Explanation Duplicate pss key detected
Error Message PORT-5-IF_TRUNK_DOWN: Interface [chars], vsan [chars] is down

([chars]) [chars] [chars]
Explanation Interface [chars] is trunking, VSAN [chars] is down with reason in (). [optionally if the
Recommended Action The following commands will help determine why this VSAN is down on this
interface: show interface, show port internal info interface VSAN, show port internal event-history
interface VSAN
2-390 OL-26589-01
Error Message PORT-5-IF_TRUNK_UP: Interface [chars], vsan [chars] is up [chars]

[chars]
Explanation Interface [chars] is trunking, VSAN [chars] is up. [optionally if the port belongs to
Error Message PORT-5-IF_UP: Interface [chars] is up [chars] [chars] [chars]
Explanation Interface is up in mode specified, if applicable. [optionally if the port belongs to

Error Message PORT-5-MODULE_BRINGUP_NOT_ALLOWED: Not allowing module [dec] to come

up for reason: [chars] ([hex])
Explanation Module is not allowed to be operational due to the current system state
Recommended Action Use command "show module <x
Error Message PORT-5-MODULE_INDEX_RESTORE_ERROR: Error in restoring indices for

module [dec]: reason [chars] ([hex])
Explanation Restore of module index may fail due to overlap of indices
Error Message PORT-5-MODULE_UNLIMITED_OSM_SEQ_FAILED: Enable/Disable of unlimited

oversubscription failed for module [dec]
Explanation Interfaces of the module may be in indeterminate state
Recommended Action Reload the module
PRIVATE_VLAN Messages
This section contains the PRIVATE_VLAN messages.
OL-26589-01 2-391
PRIVATE_VLAN-2
Error Message PRIVATE_VLAN-2-PVLAN_ASSOC_DOWN_FAILED: Failed to bring down the

association between [dec] & [dec]
Explanation Association bringdown failed
Error Message PRIVATE_VLAN-2-PVLAN_ASSOC_UP_FAILED: Failed to bring up the

association between [dec] & [dec]
Explanation Association bringup failed
Error Message PRIVATE_VLAN-2-PVLAN_ELTM_MTS_SEND_FAILED: MTS send failed while

communicating with ELTM.
Explanation ELTM MTS send failed
Error Message PRIVATE_VLAN-2-PVLAN_ELTM_TIMED_OUT: ELTM timed out while

configuring hardware.
Explanation ELTM timed out
Error Message PRIVATE_VLAN-2-PVLAN_ETHPM_TIMED_OUT: ETHPM timed out while

configuring/unconfiguring hardware
Explanation ETHPM timed out
Error Message PRIVATE_VLAN-2-PVLAN_HW_ERROR: Error [hex] occurred for ifindex

[hex] while programming hardware: [chars]
Explanation Hardware Configuration Error
2-392 OL-26589-01
Error Message PRIVATE_VLAN-2-PVLAN_PIXM_MTS_SEND_FAILED: MTS send failed while

communicating with PIXM
Explanation PIXM MTS send failed
Error Message PRIVATE_VLAN-2-PVLAN_PIXM_TIMED_OUT: PIXM timed out while

configuring hardware.
Explanation PIXM timed out
PRIVATE_VLAN-3
Error Message PRIVATE_VLAN-3-PVLAN_ASSOC_SDB_UPDATE_FAILED: Failed to update SDB

while [chars] association for vlan [dec]
Explanation SDB Update failed
Error Message PRIVATE_VLAN-3-PVLAN_IN_USE: PVLAN [dec] in use by interface [chars],

please do "no switchport access vlan" or "no switchport private-vlan
host-association"
Explanation PVLAN in use
Error Message PRIVATE_VLAN-3-PVLAN_VLANMGR_FAILURE: Cannot restore association

operational state. Failed to communicate with VLAN manager
Explanation Restoring association operational status failed
PRIVATE_VLAN-5
Error Message PRIVATE_VLAN-5-PVLAN_DISABLED: PVLAN Disabled
Explanation PVLAN Service Disabled
OL-26589-01 2-393
Error Message PRIVATE_VLAN-5-PVLAN_DISABLE_FAILED: Disabling of private-vlan

failed. Either shutdown these ports or remove them from private-vlan mode: [chars]
Explanation Disabling of private-vlan failed
Error Message PRIVATE_VLAN-5-PVLAN_ENABLED: PVLAN Enabled
Explanation PVLAN Service Enabled
PROC_MGR Messages
PROC_MGR-SLOT#-2
Error Message PROC_MGR-SLOT#-2-ERR_MSG: [chars]
Explanation Process manager error.
Error Message PROC_MGR-SLOT#-2-MESG: [chars]
Explanation Process manager information.
Recommended Action Process manager information.
Error Message PROC_MGR-SLOT#-2-PROC_MGR_APP_CRIT_ERROR: ERROR: Critical error

determined for app ([chars]) status=[dec] signal=[dec]
Explanation Application caused critical error.
Recommended Action Restart the linecard.
Error Message PROC_MGR-SLOT#-2-PROC_MGR_APP_EXITED: ERROR: Application ([chars])

exited with status=[dec] signal=[dec]
Explanation Application exited.
Recommended Action Check the application.
2-394 OL-26589-01
Error Message PROC_MGR-SLOT#-2-PROC_MGR_COMP_CATASTROPHIC_ERROR: ERROR: Component

([chars]) caused critical error and linecard will be rebooted
Explanation Component caused critical error.
Error Message PROC_MGR-SLOT#-2-PROC_MGR_COMP_CRIT_ERROR: ERROR: Critical error

determined for component ([chars]) errno=[dec]
Explanation Critical error for component.
Error Message PROC_MGR-SLOT#-2-PROC_MGR_COMP_DEP_FAIL: ERROR: Dependency failure

- Component ([chars]) depends on ([chars])
Explanation Component dependency failure.
Recommended Action Check whether the component exists.
Error Message PROC_MGR-SLOT#-2-PROC_MGR_COMP_NOT_INSTALLED: ERROR: Component

([chars]) could not be installed errno=[dec]
Explanation Component not installed.
Recommended Action Check whether the component exists.
Error Message PROC_MGR-SLOT#-2-PROC_MGR_COMP_TIMEOUT: ERROR: Component ([chars])

did not exit and time out occurred
Explanation Component initialization timed out.
Recommended Action Check the component.
Error Message PROC_MGR-SLOT#-2-PROC_MGR_MTS_CORE_CLIENT_FAIL: ERROR: MTS message

to core_client FAILED errno=[dec]
Explanation Message to core client failed.
Error Message PROC_MGR-SLOT#-2-PROC_MGR_QUIT: Process manager quitting because:

[chars]
Explanation Process manager quitting.
OL-26589-01 2-395
Error Message PROC_MGR-SLOT#-2-PROC_MGR_RM_KLM_SCRIPT: Removed: KLM/Script

[[chars]] in [dec] sec [dec] usec ...
Explanation Removed KLM/Script.
Error Message PROC_MGR-SLOT#-2-PROC_MGR_STOP_PROC: Process [[chars]] exited in

[dec] sec [dec] usec ...
Explanation Process stopped.
Error Message PROC_MGR-SLOT#-2-PROC_MGR_TERM_TIME: * Termination took [dec] sec

[dec] usec *
Explanation Process manager termination time.
Error Message PROC_MGR-SLOT#-2-PROC_MGR_UT_PEEK_FAIL: ERROR: Unable to peek on

utaker queue
Explanation Peek at utaker queue failed.
Error Message PROC_MGR-SLOT#-2-PROC_MGR_UT_SEM_ALLOC_FAIL: ERROR:Failed to

allocate utaker semaphore: [dec]
Explanation Utaker semaphore allocation failed.
Error Message PROC_MGR-SLOT#-2-PROC_MGR_UT_SEM_GET_FAIL: ERROR:[chars] [dec]:

Failed to get utaker semaphore: [dec]
Explanation Utaker semaphore get failed.
Error Message PROC_MGR-SLOT#-2-PROC_MGR_UT_SEM_GIVE_FAIL: ERROR:[chars] [dec]:

Failed to give utaker semaphore: [dec]
Explanation Utaker semaphore give failed.
2-396 OL-26589-01
Error Message PROC_MGR-SLOT#-2-PROC_MGR_UT_SEM_TAKE_FAIL: ERROR:[chars] [dec]:

Failed to take utaker semaphore: [dec]
Explanation Utaker semaphore take failed.
PROC_MGR-SLOT#-3
Error Message PROC_MGR-SLOT#-3-PROC_MGR_ERROR_MSG: [chars]
Explanation Process manager error message
PROC_MGR-SLOT#-4
Error Message PROC_MGR-SLOT#-4-PROC_MGR_APP_NOT_RESP: ERROR: Process ([chars]) is

not responding, it will be terminated
Explanation Application not sending heartbeat.
Recommended Action Check the application.
PROC_MGR-SLOT#-6
Error Message PROC_MGR-SLOT#-6-PROC_MGR_INFO_MSG: [chars]
Explanation Process manager info message
PSS Messages
This section contains the PSS messages.
PSS-0
Error Message PSS-0-PSS_NO_MORE_PAGES: [chars]: needs more working pages
Explanation Service needs more working page buffers
OL-26589-01 2-397
Error Message PSS-0-PSS_READ_DATA_FAILURE: [chars]: failed to read data to [chars]

block [dec]: [chars]
Explanation PSS cannot read data
Error Message PSS-0-PSS_SYNC_DATA_FAILURE: [chars]: failed to sync data to [chars]:

[chars]
Explanation PSS cannot sync data due to filesystem or disk error
Error Message PSS-0-PSS_SYNC_LOG_FAILURE: [chars]: failed to sync log: [chars]
Explanation PSS cannot sync log due to filesystem or disk error
Error Message PSS-0-PSS_UNKNOWN_LOG: [chars]: unknown log type [hex] at offset

[dec]
Explanation Unknown logging entry found
Error Message PSS-0-PSS_WRITE_DATA_FAILURE: [chars]: failed to write data to

[chars] block [dec]: [chars]
Explanation PSS cannot write data due to filesystem or disk error
Error Message PSS-0-PSS_WRITE_FAILURE: [chars]: failed to write data: [chars]
Explanation PSS cannot write data due to filesystem or disk error
Error Message PSS-0-PSS_WRITE_LOG_FAILURE: [chars]: failed to write log: [chars]
Explanation PSS cannot write log due to filesystem or disk error
2-398 OL-26589-01
PSS-1
Error Message PSS-1-PSS_INVALID_MAGIC: [chars]: database [chars] has invalid magic

number [hex]
Explanation PSS found a corrupted database with invalid magic number
Error Message PSS-1-PSS_META_READ_ERROR: [chars]: cannot read meta page from

[chars]: [chars]
Explanation PSS cannot read meta page of a database
Error Message PSS-1-PSS_STAT_ERROR: [chars]: cannot stat [chars]: [chars]
Explanation PSS cannot do fstat on a database
Error Message PSS-1-PSS_VERSION_MISMATCH: [chars]: found version mismatch in

[chars]
Explanation PSS found a database whose format it cannot interpret due to version mismatch
Recommended Action The image upgrade was not done properly; write erase should cure it as a last
step
PSS-2
Error Message PSS-2-PSS_INFRACONVERT: [chars]
Explanation Error in libinfraconvert during pss conversion
Error Message PSS-2-PSS_INVALID_SIZE: [chars]: database [chars] ([chars]) has

invalid size %ld (block size [dec])
Explanation PSS found a database with invalid size - probably due to a crash
OL-26589-01 2-399
Error Message PSS-2-PSS_MISSING_FILE: [chars]: database [chars] missing [chars]

file
Explanation PSS database is incomplete; probably due to a crash
Error Message PSS-2-PSS_RECOVERY_FAILED: [chars]: failed to recover [chars]
Explanation PSS recovery failed
PSS-4
Error Message PSS-4-PSS_CLEANUP: [chars]: cleaning up [chars]
Explanation PSS removed a leftover or corrupted file
Error Message PSS-4-PSS_RECOVERY_ENDED: [chars]: recovered [chars] successfully
Explanation PSS recovery finished
Error Message PSS-4-PSS_RECOVERY_STARTED: [chars]: recovering [chars]: [dec] valid

transactional records
Explanation PSS started recovery of previous aborted transaction
PSS-5
Error Message PSS-5-PSS_CONVERT_FORMAT: [chars]: converting pss format: [chars]
Explanation PSS format is being converted
Error Message PSS-5-PSS_CONVERT_LAYOUT: [chars]: converting pss layout: [chars]

(params [dec]/[dec]/[dec] -
Explanation PSS layout is being converted
2-400 OL-26589-01
Error Message PSS-5-PSS_SHRINK: [chars]: shrinking pss: [chars]
Explanation PSS is being shrunk to remove free space
Error Message PSS-5-SDB_CLOSED_AT_COMMIT: [chars]: sdb [chars] is closed: token

[dec] is not committed
Explanation Publisher received SDB commit but sdb was already closed
PTPLC Messages
PTPLC-3
Error Message PTPLC-3-PTPLC_PORT_CFG_FAILED: Configuration failed on port [hex],

[chars]: [hex], [chars]
Explanation PTP interface configuration error
Error Message PTPLC-3-PTPLC_PTP_INTF_CONFIG_ERROR: Failed to configure PTP/PONG on

port [dec]: [hex], [chars]
Explanation PTP interface configuration error
PTP Messages
This section contains the PTP messages.
PTP-5
Error Message PTP-5-PTP_DISABLED: PTP disabled
Explanation PTP Service Enabled
OL-26589-01 2-401
Error Message PTP-5-PTP_DOMAIN_CHANGE: PTP domain changed to [dec]
Explanation PTP domain changed
Error Message PTP-5-PTP_ENABLED: PTP enabled
Explanation PTP Service Enabled
PTP-6
Error Message PTP-6-PTP_ANNOUNCE_INTERVAL_CHANGE: PTP announce interval for [hex]

changed to [dec]
Explanation PTP announce interval for [chars] changed
Error Message PTP-6-PTP_ANNOUNCE_TIMEOUT_CHANGE: PTP announce timeout interval for

[hex] changed to [dec]
Explanation PTP announce timeout interval for [chars] changed
Error Message PTP-6-PTP_DELAY_REQ_INTERVAL_CHANGE: PTP delay-req interval for

[hex] changed to [dec]
Explanation PTP delay-req interval for [chars] changed
Error Message PTP-6-PTP_PRIORITY1_CHANGE: PTP priority1 changed to [dec]
Explanation PTP priority1 changed
Error Message PTP-6-PTP_PRIORITY2_CHANGE: PTP priority2 changed to [dec]
Explanation PTP priority2 changed
2-402 OL-26589-01
Error Message PTP-6-PTP_SYNC_INTERVAL_CHANGE: PTP sync interval for [hex] changed

to [dec]
Explanation PTP sync interval for [chars] changed
Error Message PTP-6-PTP_VLAN_CHANGE: PTP vlan for [hex] changed to [dec]
Explanation PTP vlan for [chars] changed
QOS Messages
This section contains the QOS messages.
QOS-2
Error Message QOS-2-EXITING: Exit reason: [chars]
Explanation The QOS Manager process has exited due to [char]. The process has probably been
Error Message QOS-2-GENERAL_ERROR: [chars]
Explanation The QOS Manager has encountered an critical error. The description of error is [str.].
Error Message QOS-2-INITFAIL: QoS Manager Initialization failed: [chars]
Explanation QoS Manager initialization failed. [chars] explains the reason for the failure.
Error Message QOS-2-MALLOC_ERROR: Size [dec] bytes
Explanation The QOS Manager could not allocate memory.
OL-26589-01 2-403
Error Message QOS-2-PSS_ERROR: [chars]: PSS returned value=[dec]
Explanation The QOS Manager encountered error while operating on a persistent storage database.
Error Message QOS-2-STDOUT_ROTATE_FAILURE: Failed to rotate stdout file: [chars]
Explanation The QOS Manager has failed to rotate its current stdout file with filename [str.]. The
file size could grow beyond its maximum limit.
QOS-3
Error Message QOS-3-ALLOCFAIL: Heap Memory allocation failed: [chars]
Explanation QoS Manager is out of dynamic memory. [chars] specifies the context where the failure
occurred.
Error Message QOS-3-DBERROR: [chars]
Explanation QoS Manager encountered a database error. [chars] specifies the context where the
failure occurred.
Error Message QOS-3-E_PORT_ACL_FAILURE: Failed to [chars] QOS ACL for interface

[chars] (ACL return code=[hex])
Explanation The QOS Manager has failed to program or erase QoS related ACL when an E-Port
came up or went down for interface [str.]. The error code returned by ACL module is [int.].
Error Message QOS-3-FAILURE_RESPONSE: [chars] [hex]
Explanation QoS Manager failed to get response [chars][hex] specify the context where the failure
occurred.
2-404 OL-26589-01
Error Message QOS-3-GENERROR: [chars]
Explanation QoS Manager encountered a general error, one that does not fall in any of the above
Error Message QOS-3-LICERR: [chars]
Explanation QoS Manager failed to get license.
Error Message QOS-3-MTSERROR: [chars]
Explanation QoS Manager encountered an MTS error. [chars] specifies the context where the error
occurred.
Error Message QOS-3-PSSERROR: [chars]
Explanation QoS Manager encountered a PSS error. [chars] specifies the context where the failure
occurred.
Error Message QOS-3-QOS_PSS_CORRUPTED: [chars] PSS found corrupted
Explanation The QOS Manager has detected corruption in one of its persistent information database.
Error Message QOS-3-TIMEOUT_ERROR: [chars] [hex]
Explanation QoS Manager encountered a timeout [chars][hex] specify the context where the failure
occurred.
Error Message QOS-3-UNKNOWN_MSG: Received from Node=[dec] SAP=[dec]
Explanation The QOS Manager has received an unknown message from [dec]].[dec]. This
information is for debugging only.
OL-26589-01 2-405
QOS-4
Error Message QOS-4-LICEXP: [chars]
Explanation QoS Manager license is going to expire. [chars] gives the expected time of expiry.
Error Message QOS-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec]
Explanation There was a version mismatch between the QOS Manager and one of its persistent
QOS-6
Error Message QOS-6-BECAME_ACTIVE: Became ACTIVE from standby mode.
Explanation The QOS Manager on the standby supervisor became active and it is ready to serve
client requests.
Error Message QOS-6-BECAME_STDBY: Became STANDBY from active mode.
Explanation The QOS Manager became standby from active mode.
Error Message QOS-6-DISABLED_UP_MARKING: [chars]
Explanation The QoS Manager has disabled marking of time-critical control traffic as high-priority
traffic. Priority of such traffic is now not altered by QoS Manager.
Error Message QOS-6-ENABLED_UP_MARKING: [chars]
Explanation The QoS Manager has enabled marking of time-critical control traffic as high-priority
traffic.
2-406 OL-26589-01
Error Message QOS-6-EXCESSIVE_DELAY: [chars]
Explanation Excessive time taken for a processing event. The description of the event is [str.].
Error Message QOS-6-E_PORT_ACL_SUCCESS: Successfully [chars] QOS ACL for interface

[chars]
Explanation The QOS Manager has successfully programmed or erased QoS related ACL when an
E-Port came up or went down for interface [str.].
Error Message QOS-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system

Explanation The QOS Manager was unable to send heartbeat to the system manager.
Error Message QOS-6-GENERAL_EVENT: [chars]
Explanation The QOS Manager has generated an important event. The description of the event is
[str.].
Error Message QOS-6-MGRCREATED: QoS Manager created
Explanation QoS Manager was created successfully and is up and running. This is an informational
message.
Error Message QOS-6-MGREXIT: QoS Manager shutting down gracefully
Explanation QoS Manager is shutting down gracefully. This is an informational message.
Error Message QOS-6-PSS_CREATED: [chars] PSS Created
Explanation One of the persistent information database of QOS Manager has been recreated.
OL-26589-01 2-407
Error Message QOS-6-PSS_DESTROYED: [chars] PSS Destroyed
Explanation One of the persistent information databases of QoS Manager has been intentionally
Error Message QOS-6-SERVICE_UP: Initialized [chars]
Explanation The QOS Manager is up and ready to accept client requests The service was initialized
in [char] mode.
Error Message QOS-6-SWITCHOVER: Switching Over to other Supervisor.
Explanation The QOS Manager has successfully switched over to the standby supervisor card.
Error Message QOS-6-UNKNOWNMTS: QoS Manager received an unexpected message
Explanation QoS Manager received an unexpected message.
RADIUS Messages
This section contains the RADIUS messages.
RADIUS-2
Error Message RADIUS-2-RADIUS_NO_AUTHEN_INFO: ASCII authentication not supported
Explanation ASCII authentication not supported.
Error Message RADIUS-2-RADIUS_PROGRAM_EXIT: RADIUS daemon exiting: [chars]
Explanation RADIUS daemon is exiting.
2-408 OL-26589-01
RADIUS-3
Error Message RADIUS-3-RADIUS_ERROR_MESSAGE: [chars]
Explanation RADIUS Error Message
RADIUS-4
Error Message RADIUS-4-RADIUS_WARNING: [chars]
Explanation RADIUS Warning
RADIUS-5
Error Message RADIUS-5-RADIUS_MONITOR_STATUS: [chars] [chars]
Explanation Notifying Radius server monitor status change
Error Message RADIUS-5-RADIUS_NOTIFICATION: [chars]
Explanation RADIUS Notification
Error Message RADIUS-5-RADIUS_SERVER_STATUS: [chars] server [chars] with auth-port

[dec] and acct-port [dec] status has changed from [chars] to [chars]. Server was
in previous-state for [chars], and total dead time of the server is [chars]
Explanation Notifying Radius server status change
RADIUS-6
Error Message RADIUS-6-RADIUS_ACCOUNTING_MESSAGE: [chars]
OL-26589-01 2-409
Error Message RADIUS-6-RADIUS_MESSAGE: [chars]
Explanation RADIUS Message
RDL Messages
This section contains the RDL messages.
RDL-2
Error Message RDL-2-PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec],

expected version [dec].[dec].[dec]
RDL-3
Error Message RDL-3-SYSLOG_ALLOC_FAIL: : [chars]
Explanation RDL memory allocation failed : [chars].
Error Message RDL-3-SYSLOG_CONTEXT_ERR: : [chars] [dec]
Explanation RDL context error: [chars] [dec].
Error Message RDL-3-SYSLOG_ERR: : [chars]
Explanation RDL syslog errors : [chars].
Error Message RDL-3-SYSLOG_EXIT: : [chars]
Explanation RDL exiting on errors : [chars].
2-410 OL-26589-01
Error Message RDL-3-SYSLOG_INIT_FAIL: : [chars] [chars]
Explanation RDL Initialization Failed: [chars] [chars].
Error Message RDL-3-SYSLOG_MTS_ERR: : [chars]
Explanation RDL MTS errors : [chars].
RDL-6
Error Message RDL-6-INFORMATION: [chars]
Explanation An event happend that affects RDL. [chars] indicates the event
Error Message RDL-6-PSS_ERR: [chars]
Explanation An error occurred during an RDL PSS operation. [chars] indicates the PSS operation
Error Message RDL-6-SYSLOG_DEBUG_1: : [chars] [hex]
Explanation RDL Debug logs: [chars] [dec].
Error Message RDL-6-SYSLOG_DEBUG_2: : [chars] [hex]
Explanation RDL Debug logs: [chars] [dec].
Error Message RDL-6-SYSLOG_INFO: : [chars]
Explanation RDL Debug logs: [chars].
OL-26589-01 2-411
Error Message RDL-6-SYSLOG_RESP_RCVD: : [chars] [dec]
Explanation RDL context error: [chars] [dec].
RES_MGR Messages
This section contains the RES_MGR messages.
RES_MGR-1
Error Message RES_MGR-1-RES_MGR_HA_ERR: HA sync message received for resource [dec]

which does not exist
Explanation RES_MGR Received HA msg for resource which does not exist Please check standby
status and restart standby to recover
RES_MGR-2
Error Message RES_MGR-2-RES_MGR_CONFLICTING_RESOURCE_KEYS: The [chars] resource

key [dec] from node [dec] is conflicting with other nodes.
Explanation The user should try and release the conflicting resource.
Error Message RES_MGR-2-RES_MGR_CRIT: RES_MGR Critical: [chars]
Explanation RES_MGR generic critical condition
Error Message RES_MGR-2-RES_MGR_HA_PSS_ERR: HA sync message received for resource

[dec] with wrong pss type [dec]
Explanation RES_MGR Received HA msg for resource which does not exist Please check standby
status and restart standby to recover
2-412 OL-26589-01
RES_MGR-3
Error Message RES_MGR-3-RES_MGR_RES_ALREADY_EXCEEDED: The VDC [dec] is currently

already using more [chars] resources (total: [dec]) than the desired new maximum
limit ([dec])
Explanation A limit-resource command was issued such that a VDC would be a forbidden state if
we obeyed, having already allocated more resources than the new maximum limit
Error Message RES_MGR-3-RES_MGR_RES_MAX_LOWER_THAN_MIN: The maximum limit for

[chars] resources is not allowed to be less than the minimum limit
Explanation A limit-resource command was issued such that the desired maximum limit was lower
than the desired minimum limit
Error Message RES_MGR-3-RES_MGR_RES_TOO_HIGH: Limits for [chars] resources are not

allowed to be set as high
Explanation A limit-resource command was issued such that a desired limit

couldntbesatisfiedbecauseofstaticpolicies'
Error Message RES_MGR-3-RES_MGR_RES_UNAVAIL: Missing [dec] [chars] resources

currently available to satisfy the minimum limit requested for vdc [dec]
Explanation A limit-resource command was issued such that the desired minimum limit
couldntbesatisfiedwiththecurrentlyavailableresources'
RES_MGR-4
Error Message RES_MGR-4-RES_MGR_MAX_ALLOWED_VDCS_HAS_DECREASED: The maximum number

of allowed VDCs has decreased from [dec] to [dec] since binary config was saved.
Explanation When startup config was saved, more VDCs were allowed in the system.
OL-26589-01 2-413
Error Message RES_MGR-4-RES_MGR_RES_ALREADY_EXCEEDED_BUT_NOT_ENFORCED: The VDC

[dec] is currently already using more [chars] resources (total: [dec]) than the
desired new maximum limit ([dec]) You may experience some route loss upon
switchover, when the new limits will actually take effect.
Explanation A limit-resource command was issued such that a VDC may not have enough memory
for holding the current amount of routing entries when the new limits will be enforced upon
switchover
Error Message RES_MGR-4-RES_MGR_SC_PSS_PCW_NETADMIN: Performing partial config

write for resource [chars] in vdc [dec]
Explanation A copy running-config startup-config command was issued from a local admin
resource limits for the specified resource in the specified vdc had to be saved as a side-effect of it
Error Message RES_MGR-4-RES_MGR_SC_PSS_PCW: Performing partial config write for

resource [chars]
Explanation A copy running-config startup-config command was issued from another VDC
resource limits for the specified resource had to be saved as part of it
Error Message RES_MGR-4-RES_MGR_UNEXPECTED_MSG_LEN: The size of this message was

expected to be [dec] ([dec] keys of [dec] size with a [dec] bytes header) and
instead was [dec].
Explanation A message of unexpected length was received.
Error Message RES_MGR-4-RES_MGR_VLAN_RESERVED_RANGE_UNAVAILABLE: System is running

with limited functionality due to restricted reserved vlan range 3968-4047 should
be 3968-4096.
Explanation User should delete VLANS in range 4048-4093 and use following command: system
vlan 3968 reserve
2-414 OL-26589-01
RES_MGR-5
Error Message RES_MGR-5-RES_MGR_DISABLED: RES_MGR Disabled
Explanation RES_MGR Service Disabled
Error Message RES_MGR-5-RES_MGR_ENABLED: RES_MGR Enabled
Explanation RES_MGR Service Enabled
RES_MGR-6
Error Message RES_MGR-6-RES_MGR_CONDITION_VERIFIED: error [hex] [[chars]] during

sysmgrcb_vdc_handshake_done() for vdc [dec]
Explanation RES_MGR is spotting some issue when VDC got created
RIB Messages
This section contains the RIB messages.
RIB-0
Error Message RIB-0-EMERG: [chars]
Explanation Rib caused a system failure
RIB-1
Error Message RIB-1-ALERT: [chars]
Explanation Rib caused failures in other services
OL-26589-01 2-415
Error Message RIB-1-LCM_FIB_ERR: RIB failed LC insertion
Explanation RIB stopped linecard from coming online due to error received from FIB during merge
operation
Recommended Action Check RIB error logs to see error received from FIB
RIB-2
Error Message RIB-2-CRIT: [chars]
Explanation Rib encountered a catastrophic error
RIB-3
Error Message RIB-3-ERR: [chars]
Explanation Rib encountered an error
Error Message RIB-3-FIB_EXIT: fib exited
Explanation Fib had exited and may not continue operation
Error Message RIB-3-MISS_APPS: Missing response from service
Explanation Service not responding to rib

debugriberror',thenrecreatetheoperationscenario,tofindoutmoredetails.'
Error Message RIB-3-NO_MEM: Out of memory
Explanation Rib does not have enough memory to continue proper operation.
2-416 OL-26589-01
Error Message RIB-3-SEND_FIB: Cannot talk to fib
Explanation Rib to fib IPC failure
Error Message RIB-3-SEND_SNMP: Cannot respond to snmp
Explanation Rib to snmp IPC failure
Error Message RIB-3-SEND_STANDBY: Cannot talk to standby rib
Explanation Lost a rib-fib transaction log due to IPC failure
RIB-4
Error Message RIB-4-CPU_HOG: Inactive or busy
Explanation Either rib was not scheduled to run, or rib was busy, and rib did not service the message
or timer queue for an extended period.

Error Message RIB-4-DUP_FIB: Duplicate response from fib
Explanation Rib ignored duplicate response from fib

Error Message RIB-4-LATE_FIB: Late response from fib
Explanation Rib ignored late response from fib

OL-26589-01 2-417
Error Message RIB-4-PC_LIMIT: PC number greater than 128 (ignored by RIB)
Explanation Rib ignored pc
Recommended Action Please use PC number < 128
Error Message RIB-4-WARN: [chars]
Explanation Rib ignored the unexpected condition

debugriball',thenrecreatetheoperationscenario,tofindoutmoredetails.'
RIB-5
Error Message RIB-5-NOTE: [chars]
Explanation Rib does not support this operation

debugriball',thenrecreatetheoperationscenario,tofindoutmoredetails.'
RIB-6
Error Message RIB-6-INFO: [chars]
Explanation Rib event occurred
RLIR Messages
This section contains the RLIR messages.
RLIR-2
Error Message RLIR-2-DRLIR_REJECT: DRLIR rejected: [chars]: fcid [chars], reason

code [dec]
Explanation DRLIR rejected: [chars] fcid [chars] reason code [dec]
2-418 OL-26589-01
Error Message RLIR-2-FC2_FAILED: RLIR FC2 operation failed: [chars]: [chars]
Explanation RLIR FC2 operation failed: [chars] [chars]
Error Message RLIR-2-INIT_FAILED: RLIR Init failed: [chars]
Explanation RLIR Init failed: [chars]
Error Message RLIR-2-LINK_INCIDENT: Interface [chars] [Port [hex]], Link Status:

[chars], Link Status Reason: [chars]
Explanation RLIR module detected an unintentional Link Incident
Error Message RLIR-2-MALLOC_FAILED: RLIR Malloc failed: [chars]
Explanation RLIR Malloc failed: [chars]
Error Message RLIR-2-MTS_FAILED: RLIR MTS operation failed: [chars]: [chars]
Explanation RLIR MTS operation failed: [chars] [chars]
Error Message RLIR-2-PSS_FAILED: RLIR PSS operation failed: [chars]: [chars]
Explanation RLIR PSS operation failed: [chars] [chars]
RLIR-6
Error Message RLIR-6-SYSLOG_INFO: RLIR Syslog info: [chars]
Explanation RLIR Syslog info: [chars]
OL-26589-01 2-419
Error Message RLIR-6-SYSLOG_STATUS: RLIR Syslog status: [chars]: [chars]
Explanation RLIR Syslog status: [chars] [chars]
RM Messages
This section contains the RM messages.
RM-6
Error Message RM-6-RMGR_INFO: [chars]
Explanation RMGR daemon informational message
Error Message RM-6-STARTING: deamon started
Explanation The RMGR daemon successfully started
RM-SLOT#-2
Error Message RM-SLOT#-2-CPP_CATASTROPHIC_ERROR: ERROR: Component ([chars]) caused

critical error. Service Module will be reloaded
Error Message RM-SLOT#-2-RM_CPP_RELOAD_TMOUT: ERROR: Component ([chars]) timed out

for critical error response. Service Module will be reloaded
Explanation Component critical error timeout
Error Message RM-SLOT#-2-RM_CRITICAL_ALERT: [chars]
Explanation Critical Alert
2-420 OL-26589-01
Error Message RM-SLOT#-2-RM_PROCESS_FAILED: ERROR: [chars] failed
Explanation Process failed
Error Message RM-SLOT#-2-RM_PROCESS_TMOUT: ERROR: [chars] did not complete.

Reloading Service Module
Explanation Component critical error timeout
Error Message RM-SLOT#-2-RM_VICPP_RECREATE_ERROR: All the fast path resources are

down VICPP connectivity lost
RM-SLOT#-4
Error Message RM-SLOT#-4-RM_WARNING: [chars]
Explanation Warning
RSCN Messages
This section contains the RSCN messages.
RSCN-2
Error Message RSCN-2-FC2_FAILED: RSCN FC2 operation failed: [chars]: [chars]
Explanation RSCN FC2 operation failed: [chars] [chars]
Error Message RSCN-2-INIT_FAILED: RSCN Init failed: [chars]
Explanation RSCN Init failed: [chars]
OL-26589-01 2-421
Error Message RSCN-2-MALLOC_FAILED: RSCN Malloc failed: [chars]
Explanation RSCN Malloc failed: [chars]
Error Message RSCN-2-MTS_FAILED: RSCN MTS operation failed: [chars]: [chars]
Explanation RSCN MTS operation failed: [chars] [chars]
Error Message RSCN-2-PSS_FAILED: RSCN PSS operation failed: [chars]: [chars]
Explanation RSCN PSS operation failed: [chars] [chars]
Error Message RSCN-2-SCR_REJECT: SCR rejected: [chars]: fcid [chars], Reason

code-[chars], Reason code expl-[chars]
Explanation SCR rejected: [chars] fcid [chars] Reason code [chars] Reason code expl [chars]
RSCN-4
Error Message RSCN-4-RSCN_REJECT: RSCN rejected: [chars]: fcid [chars], Reason

code-[chars], Reason code expl-[chars]
Explanation RSCN rejected: [chars] fcid [chars] Reason code [chars] Reason code expl [chars]
Error Message RSCN-4-SWRSCN_REJECT: SW-RSCN rejected: [chars]: fcid [chars],

Reason code-[chars], Reason code expl-[chars]
Explanation SW-RSCN rejected: [chars] fcid [chars] Reason code [chars] Reason code expl [chars]
RSCN-6
Error Message RSCN-6-SYSLOG_INFO: RSCN Syslog info: [chars]
Explanation RSCN Syslog info: [chars]
2-422 OL-26589-01
Error Message RSCN-6-SYSLOG_STATUS: RSCN Syslog status: [chars]: [chars]
Explanation RSCN Syslog status: [chars] [chars]
Recommended Action
SAL Messages
This section contains the SAL messages.
SAL-5
Error Message SAL-5-SAL_DISABLED: SAL Disabled
Explanation SAL Service Disabled
Error Message SAL-5-SAL_ENABLED: SAL Enabled
Explanation SAL Service nabled
SAN_EXT_TUNER Messages
This section contains the SAN_EXT_TUNER messages.
SAN_EXT_TUNER-3
Error Message SAN_EXT_TUNER-3-SAN_EXT_TUNER_LICENSE_EXPIRED: SAN Extension Licence

expired - Disabling SAN Extension Tuner
Explanation SAN Extension Licence expired/not present - Disabling SAN Extension Tuner
SCHEDULER Messages
This section contains the SCHEDULER messages.
OL-26589-01 2-423
SCHEDULER-2
Error Message SCHEDULER-2-SCH_SYSLOG_MALLOC_ERR: Out of memory: [chars]
Explanation Process memory exhausted. Possible memory leak.
Recommended Action Contact TAC
Error Message SCHEDULER-2-SCH_SYSLOG_MTS_ERR: MTS error: [chars]
Explanation MTS operation failure
Error Message SCHEDULER-2-SCH_SYSLOG_PSS_SNAPSHOT_ERR: Source URI:[chars]

Destination URI:[chars] errcode:[dec]
Explanation Error while performing snapshot I/O to PSS
Error Message SCHEDULER-2-SCH_SYSLOG_SDWRAP_ERR: Debug infrastructure

initialization failed: [chars]
Explanation Debug infrastructure failed to initialize
SCHEDULER-3
Error Message SCHEDULER-3-SCH_ERR: [chars]
Explanation Scheduler error
Error Message SCHEDULER-3-SCH_SYSLOG_FILE_ERR: [chars] Error:[chars]
2-424 OL-26589-01
Error Message SCHEDULER-3-SCH_SYSLOG_PSS_ERR: Purpose:[chars] URI:[chars]

Error:[dec]
Explanation Error while performing I/O to PSS
Error Message SCHEDULER-3-SCH_SYSLOG_USER_ERR: Description: Failed to execute job

for user id [chars] Error:[dec]
Explanation Error while attempting to execute job for user. Possibly, the user is removed from the
system.
Recommended Action Ensure the user exists. Make sure he is not a remotely authenticated user.
SCHEDULER-4
Error Message SCHEDULER-4-SCH_WARN: [chars]
Explanation Scheduler warning
SCHEDULER-6
Error Message SCHEDULER-6-SCH_MSG: [chars]
Explanation Scheduler Message
SCM Messages
SCM-2
Error Message SCM-2-SCMLCINSERTFAIL: [chars]
Explanation SCSI-TARGET
Recommended Action NONE
SCSI-TARGET Messages
This section contains the SCSI-TARGET messages.
OL-26589-01 2-425
SCSI-TARGET-2
Error Message SCSI-TARGET-2-PROC_OPEN_VHBA_DEVICE_FAIL: Failed to communicate with

SCSI-target driver error: [hex]
Explanation SCSI-target process failed to communicate with

itspeerkerneldriver[hex].NoSCSIdiscoverycanbeperformed.'
Recommended Action Collect more information using command showscsi-targetinternaldriver'.'
Error Message SCSI-TARGET-2-PROC_SET_SCSI_INDEX_FAIL: Failed to set SCSI index

SCSI-target driver error: [hex]
Explanation SCSI-target process failed to set SCSI index with

itspeerkerneldriver[hex].NoSCSIdiscoverycanbeperformed.'
Recommended Action Collect more information using command showscsi-targetinternaldriver'.'
Error Message SCSI-TARGET-2-PROC_WWNM_GET_WWN_FAIL: Failed to get local controller

pwwn from WWN Manager error: [hex] response: [hex]
Explanation SCSI-target process used wwnm_bwt_get_local_controller_wwn() api for the port

wwn and it failed due to error [hex], response code [hex]. No SCSI discovery can be performed.
Recommended Action Collect more information using commands

showprocesscpu'and'showsysteminternalsysmgrserviceall'.SeeWWNManagersystemerrorcodesforr
eason.'
Error Message SCSI-TARGET-2-PSS_INIT_FAIL: pss initialization failed due to error:

[hex]
Explanation SCSI-target process pss initialization failure due to error [hex]. No SCSI discovery can
be performed.

SCSI-TARGET-3
Error Message SCSI-TARGET-3-PROC_VSAN_GET_RATOV_FAIL: Failed to get vsan attribute

RATOV from VSAN Manager, error: [hex]
Explanation SCSI-target process used the vsan_get_global_value() api for RATOV and it failed due
to error [hex].
Recommended Action This is a non-fatal error. The default value for RATOV is used. Collect more
information using commands
showprocesscpu'and'showsysteminternalsysmgrserviceall'.SeeVsanManagersystemerrorcodesforre
ason.'
2-426 OL-26589-01
Error Message SCSI-TARGET-3-PSS_CREATE_FAIL: pss create runtime database failed

due to error: [hex]
Explanation SCSI-target process pss create runtime database failure due to error [hex]. No SCSI
discovery can be performed.

Error Message SCSI-TARGET-3-PSS_DELETE_FAIL: pss delete runtime entry key:[hex]

Explanation SCSI-target process pss delete runtime entry key [hex] failure due to error [hex].

Error Message SCSI-TARGET-3-PSS_MAX_KEY_FAIL: pss set runtime max key failed due
to error: [hex]
Explanation SCSI-target process pss set runtime max key failure due to error [hex]. No SCSI

Error Message SCSI-TARGET-3-PSS_MAX_VALUE_FAIL: pss set runtime max value failed

due to error: [hex]
Explanation SCSI-target process pss set runtime max value failure due to error [hex]. No SCSI

Error Message SCSI-TARGET-3-PSS_OPEN_FAIL: pss open runtime database failed due to

error: [hex]
Explanation SCSI-target process pss open runtime database failure due to error [hex]. No SCSI

Error Message SCSI-TARGET-3-PSS_RELOAD_FAIL: pss reload runtime database failed

due to error: [hex]
Explanation SCSI-target process pss reload runtime database failure due to error [hex].

OL-26589-01 2-427
Error Message SCSI-TARGET-3-PSS_SNAPSHOT_DEBUG_FAIL: pss snapshot runtime debug to

uri:[chars] failed due to error: [hex]
Explanation SCSI-target process pss snapshot of runtime debug to uri [string] failed due to error
[hex].

Error Message SCSI-TARGET-3-PSS_SNAPSHOT_FAIL: pss snapshot runtime to uri:[chars]

Explanation SCSI-target process pss snapshot of runtime to uri [string] failed due to error [hex].

Error Message SCSI-TARGET-3-PSS_STORE_FAIL: pss store runtime entry key:[hex]

val:[hex] failed due to error: [hex]
Explanation SCSI-target process pss store runtime entry key [hex] value [hex] failure due to error
[hex].

SCSI-TARGET-7
Error Message SCSI-TARGET-7-SCSI_TARGET_DISCOVERED: SCSI-target discovered

VSAN:[dec] FCID:[hex] prlisparm:[hex]
Explanation SCSI-target process discovered VSAN [dec] FCID [hex] prli service parameter [hex].
SDV Messages
This section contains the SDV messages.
SDV-2
Error Message SDV-2-RANDNUM_FAIL: Random number generation failed
Explanation Random number generation failed. Process has to exit due to FIPS compliance
2-428 OL-26589-01
SDV-3
Error Message SDV-3-ACL_CACHE_ERROR: ACL CACHE ERR, Trying to prog with no

interface list
Explanation A Null interface list was generated for a ACL entry
Error Message SDV-3-ACL_ERROR: ACL API, [chars], failed with error [hex]
Explanation SDV invoked ACL API and received the error code. [chars] describes the API and
Error Message SDV-3-ALLOC_FAILED: Failed for type [dec] size [dec]
Explanation SDM process could not allocate heap memory. [dec] is the memory type and [dec] is
the size of memory
Error Message SDV-3-ASSERTION_FAILED: [chars]:[dec]
Explanation SDM process has hit an assert condition at file [chars] line number [dec]
Error Message SDV-3-AUTO_FAILOVER_ERROR: [chars]
Explanation SDV Virtual-device failed to auto-failover due to [chars]
Error Message SDV-3-BCAST_NOT_SUPPORTED: Broadcast attribute will be ignored for

SDV devices
Explanation Broadcast attribute will be ignored for SDV devices
Error Message SDV-3-ENQUEUE_EVENT_FAIL: Unable to enqueue event into state machine
Explanation Unable to enqueue event into state machine
OL-26589-01 2-429
Error Message SDV-3-FCID_REWRITE_REQUEST_TO_ACL_FAILED: fcid rewrite [chars]

request vsan [dec] vdev_id [dec] failed:[chars].
Explanation This happens when either after SDV retried the request few times or ACL experienced
Error Message SDV-3-INIT_FAIL: [chars]
Explanation SDM process init has failed due to [chars]
Error Message SDV-3-INTERNAL_ERR: [chars]
Explanation SDM process encountered an internal error due to [chars]
Error Message SDV-3-LOCK_FAILED: [chars]
Error Message SDV-3-MERGE_ACTIVATION_FAILED: [chars]
Explanation Error while activating the merged SDV database due to [chars]
Error Message SDV-3-MERGE_CAP_FAILED: [chars]
Explanation SDV fabric merge failed because of incomaptible capabilities [chars]
Recommended Action Compare SDV configuration in both fabrics and resolve the conflicts if any
and commit the changes.
Error Message SDV-3-MERGE_FAILED: [chars]
Explanation SDV fabric merge failed due to [chars]
Recommended Action Check the error using "show sdv merge staus vsan <vsan-id
2-430 OL-26589-01
Error Message SDV-3-MTS_ERR: [chars]
Explanation SDM process encountered an MTS error due to [chars]
SDV-4
Error Message SDV-4-FCID_REWRITE_REQUEST_TO_ACL_FAILED_AND_RETRYING:

failed:[chars]. Retrying the request again.
SDV-6
Error Message SDV-6-INTERNAL_ERR_INFO: [chars]
Explanation SDM process encountered ignorable error due to [chars]
SDV-7
Error Message SDV-7-SRVCREATED: SDM Process started
Explanation SDM process has started
SECURITYD Messages
This section contains the SECURITYD messages.
SECURITYD-2
Error Message SECURITYD-2-FIPS_BYPASS_SELF_TEST_STATUS: FIPS Bypass self-test

status : [chars]
Explanation Status of FIPS self-test [chars]
OL-26589-01 2-431
Error Message SECURITYD-2-FIPS_CRNG_SELF_TEST_STATUS: FIPS CRNG self-test status

: [chars]
Explanation Status of FIPS self-test [chars]
Error Message SECURITYD-2-FIPS_CRYPTO_SELF_TEST_STATUS: FIPS [chars] Crypto

self-test status : [chars]
Explanation Status of FIPS [chars] self-test [chars]
Error Message SECURITYD-2-FIPS_IMAGE_INTEGRITY_SELF_TEST_STATUS: FIPS Image

Integrity self-test status : [chars]
Explanation Status of FIPS [chars] self-test [chars]
Error Message SECURITYD-2-FIPS_POST_ERROR_MSG: [chars]
Explanation Fips post Error Message
Error Message SECURITYD-2-FIPS_POST_MAINTENANCE: FIPS Test failed. Moving to

maintenance mode
Explanation FIPS Test failed. Moving to maintenance mode
Error Message SECURITYD-2-FIPS_POST_TEST_FAILED: FIPS crypto-test failure : [dec]
Explanation FIPS crytpo-test failed [chars]
Error Message SECURITYD-2-FIPS_POWERUP_SELF_TESTS_STATUS: FIPS power-up self-test

status: [chars]
Explanation Status FIPS self-test [chars]
2-432 OL-26589-01
Error Message SECURITYD-2-FIPS_POWERUP_SELF_TEST_STATUS: FIPS [chars] power-up

self-test status : [chars]
Explanation Status of FIPS [chars] power-up self-test [chars]
Error Message SECURITYD-2-FIPS_SELF_TEST_FAILED: FIPS self-test failure : [chars]

: [chars]
Explanation FIPS self-test failed [chars] for service [chars]
Error Message SECURITYD-2-PROGRAM_EXIT: security/accounting daemon exiting:

[chars]
Explanation Security/accounting daemon is exiting.
SECURITYD-3
Error Message SECURITYD-3-NVRAMFAILURE: nvram failure
Explanation Nvram can not be read/written to. Hence accounting log can not be stored there
SECURITYD-6
Error Message SECURITYD-6-ACCOUNTING_MESSAGE: [chars]
Error Message SECURITYD-6-CHANGE_PASSWD: changing passwd for [chars]
Explanation Changing passwd for [chars]
OL-26589-01 2-433
Error Message SECURITYD-6-DELETE_STALE_USER_ACCOUNT: deleting expired user

account:[chars]
Explanation Deleting expired user account of [chars]
Error Message SECURITYD-6-FIPS_MODE_SET_FAILED: Error when setting FIPS mode :

[chars]
Explanation FIPS mode failed [chars]
Error Message SECURITYD-6-FIPS_MODE_SET: FIPS mode is [chars] for service [chars]
Explanation FIPS mode is changed [chars] [chars]
Error Message SECURITYD-6-FIPS_POST_INFO_MSG: [chars]
Explanation Fips post Information Message
SENSOR_USD Messages
This section contains the SENSOR_USD messages.
SENSOR_USD-2
Error Message SENSOR_USD-2-SNSM_SYSLOG_INIT_FAILED: Sensor Mgr Initialization

failed. Component [chars]
Explanation Sensor Manager syslog message
Error Message SENSOR_USD-2-SNSM_SYSLOG_SHUTDOWN: Sensor Mgr process shutting down:

[chars]
2-434 OL-26589-01
Error Message SENSOR_USD-2-SNSM_SYSYLOG_ALLOC_MEMORY: Sensor Mgr Memory allocation

failed
SENSOR_USD-3
Error Message SENSOR_USD-3-MSG_SNSM_SYS_MEM_ALOC_FAILURE: Sensor Mgr Error in

allocing mem: [dec], Error code = [dec]
Error Message SENSOR_USD-3-SNSM_API_CALL_FAILURE: Sensor Mgr Error in [chars] call

errno=[dec]
Error Message SENSOR_USD-3-SNSM_SYSLOG_BAD_MTS_MSG: Sensor Mgr Received bad MTS

message: [dec]
Error Message SENSOR_USD-3-SNSM_SYSLOG_MTS_PROCESS_ERROR: Sensor Mgr Error in

processing MTS message: [dec], Error code = [hex]
Error Message SENSOR_USD-3-SNSM_SYS_DEQUE_PENDING_QUE_FAILURE: Sensor Mgr Error in

Dequing pend Que: %p, Error code = [hex]
OL-26589-01 2-435
Error Message SENSOR_USD-3-SNSM_SYS_ENQUE_PENDING_QUE_FAILED: Sensor Mgr Error in

queuing to pending queue: %p, Error code = [hex]
Error Message SENSOR_USD-3-SNSM_SYS_MTS_RECV_FAILURE: Sensor Mgr Error in receving

MTS mesg
SENSOR_USD-5
Error Message SENSOR_USD-5-SNSM_SYSLOG_STARTING: Sensor Mgr process started
SENSOR_MGR Messages
This section contains the SENSOR_MGR messages.
SENSOR_MGR-2
Error Message SESSION-MGR-2-DB_UNLOCK_FAILED: Failed to unlock the database for

session:[chars]
Explanation Session-Manager failed to unlock the database for session: [chars]
SENSOR_MGR-3
Error Message SESSION-MGR-3-ALLOC_FAILED: Failed in File:[chars] Line:[dec] for

type [dec] size [dec]
Explanation Session-mgr process could not allocate heap memory in File:[chars], at line:[dec], for
2-436 OL-26589-01
SENSOR_MGR-4
Error Message SESSION-MGR-4-ISSU_FAILED: [chars] :[hex]
Explanation Session manager failed ISSU because of:[string] and error: [hex]
SFC Messages
This section contains the SFC messages.
SFC-3
Error Message SFC-3-ERROR: [chars]
Explanation SCSI Flow Client encountered an error
SFM Messages
This section contains the SFM messages.
SFM-2
Error Message SFM-2-NO_LICENSE_WARNING: SCSI Flow Manager is shutting down as no

license is available.
Explanation License required for continued SCSI Flow Manager operation is not available.
SFM-6
Error Message SFM-6-LICENSE_VALID: A valid license for SCSI FLow Manager has been
obtained
Explanation A valid license for SCSI Flow Manager has been obtained
OL-26589-01 2-437
SKSD Messages
This section contains the SKSD messages.
SKSD-2
Error Message SKSD-2-SKSD_CRYPT_SERVICE_CRIT: Encryption-Service: [chars]
Explanation Encryption Service critical errors.
SKSD-3
Error Message SKSD-3-SKSD_CRYPT_SERVICE_ERR: Encryption-Service: [chars]
Explanation Encryption Service errors.
Error Message SKSD-3-SKSD_FIPS_MODE_INIT_ERROR: Could not initialize FIPS mode :

[chars]
Explanation FIPS mode initialization error
Error Message SKSD-3-SKSD_FIPS_MODE_SELFTEST: FIPS POST for [chars] [chars]
Explanation FIPS Selftest Result
SKSD-4
Error Message SKSD-4-SKSD_CRYPT_SERVICE_WARN: Encryption-Service: [chars]
Explanation Encryption Service warnings.
2-438 OL-26589-01
SKSD-5
Error Message SKSD-5-SKSD_CRYPT_SERVICE_NOTICE: Encryption Service: [chars]
Explanation Encryption Service updates.
Error Message SKSD-5-SKSD_EXIT: Keystore Application Exiting: [chars]
Explanation Keystore Program exiting
Error Message SKSD-5-SKSD_FUNC: Keystore Operation: [chars]
Explanation Keystore Event upon a receiving a request
Error Message SKSD-5-SKSD_HW_INIT: Hardware Keystore Init done
Explanation Hardware Keystore Init completed
Error Message SKSD-5-SKSD_HW_RESET: Hardware Reset :[chars]
Explanation Hardware Reset
Error Message SKSD-5-SKSD_HW: Smartcard :[chars]
Explanation Smartcard Presence
Error Message SKSD-5-SKSD_INIT: Keystore Application Init: [chars]
Explanation Keystore Program Init
OL-26589-01 2-439
Error Message SKSD-5-SKSD_KEY_ADD: Key added
Explanation Key added to keystore
Error Message SKSD-5-SKSD_KEY_DELETE: Key deleted
Explanation Key deleted from keystore
Error Message SKSD-5-SKSD_MKEY_INSTALL: Installing a Master Key on the smartcard(s)
Explanation Installing a new Master Key on the smartcard(s)
Error Message SKSD-5-SKSD_SUP_STATE: Supervisor card new state: [dec]
Explanation Supervisor state change
Error Message SKSD-5-SKSD_SW_INIT: Software Keystore Init done
Explanation Software Keystore Init completed
SKSD-6
Error Message SKSD-6-SKSD_CRYPT_SERVICE_INFO: Encryption Service: [chars]
Explanation Encryption Service informational updates.
SKT_USD Messages
This section contains the SKT_USD messages.
2-440 OL-26589-01
SKT_USD-2
Error Message SKT_USD-2-SKT_RF_CRC_ERR: [chars]
Explanation Skytrain received packet(s) from fabric with CRC error
SKT_USD-6
Error Message SKT_USD-6-SKT_DEBUG_MSG: [chars]
SME_CPP Messages
This section contains the SME_CPP messages.
SME_CPP-2
Error Message SME_CPP-2-IT_NEXUS_MAX_INTERFACE_LIMIT_REACHED: [chars] cannot be

bound as the interfaces reached the maximum IT Nexus limit
Explanation IT Load Balancing failed
Error Message SME_CPP-2-LOG_ERR_SME_CTRL_LUN_PATH_MISCONFIG: Control LUN [chars]

behind Host PWWN [chars] Tgt PWWN [chars] LUN Id [chars] has some lun paths that
are not configured.
Explanation A single lun with multiple paths has some non configured paths. Please configure all
lun paths.
Error Message SME_CPP-2-LOG_ERR_SME_DIFF_LUN_MISCONFIG: Lun [chars] and [chars]

behind Host PWWN [chars] Tgt PWWN [chars] LUN Id [chars] configured as one device.
Explanation Two different luns configured as one device. Please fix configuration.
OL-26589-01 2-441
Error Message SME_CPP-2-LOG_ERR_SME_LICENSE_EXPIRED: SME License expired -

Disabling [chars]
Explanation SAN Media Encryption License expired/not present - Disabling SME
Error Message SME_CPP-2-LOG_ERR_SME_TAPE_LUN_PATH_MISCONFIG: Tape Drive [chars]

behind Host PWWN [chars] Tgt PWWN [chars] LUN Id [chars] has some lun paths that
are not configured.
Explanation A single lun with multiple paths has some non configured paths. Please configure all
lun paths.
Error Message SME_CPP-2-LOG_ERR_SME_TOM_ABORTED: SME Cluster [chars] Message Id:

[hex] aborted
Explanation An SME Cluster Message was aborted by the Cluster process
Error Message SME_CPP-2-LOG_WARN_SME_LICENSE_GRACE: No SME License. Feature will

be shut down after a grace period of approximately [dec] days
Explanation SAN Media Encryption feature on grace period. Please acquire actual license.
Error Message SME_CPP-2-SME_INIT_FAILED: Initialization failed for SME: [chars],

Reason: [hex]
Explanation Initialization failed for SME
SME_CPP-3
Error Message SME_CPP-3-LOG_ERR_SME_DBSYBC_REJECT: SME Database Synchronization

[chars] for a New Cluster (Id 0x%llx) Rejected; Reason - [chars].
Explanation A switch can be part of only one SME cluster
2-442 OL-26589-01
Error Message ME_CPP-3-LOG_ERR_SME_DISK_DP_CNODE_NOT_FOUND: crypto disk data

preparation for (DG: [chars] CD NAME: [chars]) could not find cnode ([chars]
if_index: [hex])
Explanation The data preparation failed since crypto node assigned for data prepration is not found
Error Message SME_CPP-3-LOG_ERR_SME_DISK_DP_CNODE_OVERLOAD: crypto disk data

preparation for (DG: [chars] CD NAME: [chars]) could not be assgined a crypto node
([chars] if_index: [hex]) due to max limit. current active sessions: [dec]
Explanation The data preparation failed since crypto node is already handling maximum number of
data preparation sessions
Error Message SME_CPP-3-LOG_ERR_SME_DISK_KMC_NAME_MISMATCH: The KMC DG: [chars] and

CD NAME: [chars] corresponding to VID: [chars] PID: [chars] DID: [chars] doesnt
match cdisk DG: [chars] and CD NAME: [chars]
Explanation The discovered vendor id information not match the cryptodisk
Error Message SME_CPP-3-LOG_ERR_SME_DISK_KMC_VPD_FIXED: The VPD of cdisk DG: [chars]

CD NAME: [chars] has been changed to VPD in KMC VID: [chars] PID: [chars] DID:
[chars] and old VPD of disk has been removed
Explanation The vendor id information has been modified to be consistent with KMC
Error Message SME_CPP-3-LOG_ERR_SME_DISK_KMC_VPD_MISMATCH: The VID:[chars]

PID:[chars] DID: [chars] of cdisk DG: [chars] CD NAME: [chars] does not match VPD
in KMC VPD: [chars] PID: [chars] DID: [chars]
Explanation The discovered vendor id information not match the cryptodisk
Error Message SME_CPP-3-LOG_ERR_SME_DISK_LUN_PATH_AUTH_FAIL1: ITL HPWWN: [chars]

TPWWN: [chars] LUN Id: [chars] VPD mismatch disk. Disk VPD VID: [chars] PID:
[chars] DID: [chars] ITL VID: [chars] PID: [chars] DID: [chars]
Explanation The given path does not belong to the configured disk
OL-26589-01 2-443
Error Message SME_CPP-3-LOG_ERR_SME_DISK_LUN_PATH_AUTH_FAIL2: ITL HPWWN: [chars]

TPWWN: [chars] LUN Id: [chars] VID: [chars] PID: [chars] DID: [chars] belongs to
a different cdisk DG: [chars] CD NAME: [chars]
Explanation The given path does not belong to the configured disk
Error Message SME_CPP-3-LOG_ERR_SME_DISK_LUN_PATH_AUTH_FAIL3: CFG ITL HPWWN:

[chars] TPWWN: [chars] LUN Id: [chars] VID: [chars] PID: [chars] DID: [chars]
doesnt belong to DG: [chars] CD NAME: [chars] whose VID: [chars] PID: [chars] DID:
[chars]
Explanation The given path does not belong to the disk
Error Message SME_CPP-3-LOG_ERR_SME_DISK_LUN_PATH_AUTH_FAIL4: CFG ITL HPWWN:

[chars] TPWWN: [chars] LUN Id: [chars] of DG: [chars] CD: [chars] has VID: [chars]
PID: [chars] DID: [chars] belonging to DG: [chars] CD NAME: [chars]
Explanation The given path does not belong to the disk
Error Message SME_CPP-3-LOG_ERR_SME_INTF_MISMATCH_CLUSTER_PARAMS: SME interface

[chars] part of cluster [chars] with ID [chars] and security mode [dec], but the
DPP has state from a previous instance of a cluster [chars] with ID [chars] and
security mode [dec].
Explanation DPP has persistent state about a previous cluster membership incarnation, but the
interface is part of a different cluster.
Error Message SME_CPP-3-LOG_ERR_SME_INTF_MISMATCH_CRYPTO_NODE_CERTIFICATE2: but

the DPP has a different certificate (len [dec] fingerprint [chars]).
Explanation DPP has persistent state about a previous cluster membership with a different crypto
node identity.
Error Message SME_CPP-3-LOG_ERR_SME_INTF_MISMATCH_CRYPTO_NODE_CERTIFICATE: SME

interface [chars] part of cluster [chars] with ID [chars] as a crypto node [chars]
with certificate (len [dec] fingerprint [chars]), ..
Explanation DPP has persistent state about a previous cluster membership with a different crypto
node identity.
2-444 OL-26589-01
Error Message SME_CPP-3-LOG_ERR_SME_INTF_MISMATCH_CRYPTO_NODE_PARAMS: SME

interface [chars] part of cluster [chars] with ID [chars] as a crypto node [chars],
but the DPP is identified as [chars].
Explanation DPP has persistent state about a previous cluster membershipon a different switch or
module.
Error Message SME_CPP-3-LOG_ERR_SME_IT_NEX_USED_FOR_DP: IT CL: [chars] H: [chars] T:

[chars] VSAN: [dec] has PATH lunid: [chars] for disk (dg: [chars] cd: [chars]) so
rediscover not issued
Explanation The IT nexus is currently in use by data preparation so rediscover not permitted since
it disrupts data preparation. Please stop data preparation first
Error Message SME_CPP-3-LOG_SME_CDISK_DP_FAILED: SME cdisk ([chars]) data

preparation failed ([chars]), disk-group ([chars]), cluster (name [chars], id
%llx)
Explanation SME cdisk data preperation failed
Error Message SME_CPP-3-LOG_SME_DISK_ASL_FAILED: [chars]
Explanation SME KMC disk asl token generation failed for the given device discovery info
Error Message SME_CPP-3-LOG_SME_KEY_CREATE_FAILED: Key creation ([chars]) failed

with error ([chars]), SME cluster (name [chars], id %llx)
Explanation SME key creation failed
Error Message SME_CPP-3-LOG_SME_KMC_DELETE_ALL_KEYS_FAILED: Delete all keys in

cluster failed to KMC server failed with error ([chars]), SME cluster (name
[chars], id %llx)
Explanation SME KMC delete keys failed
OL-26589-01 2-445
Error Message SME_CPP-3-LOG_SME_KMC_DELETE_KEYS_FAILED: Delete keys for [chars]

failed to KMC server failed with error ([chars]), SME cluster (name [chars], id
%llx)
Explanation SME KMC delete keys failed
Error Message SME_CPP-3-LOG_SME_KMC_KEEPALIVE_FAILED: Keepalive to KMC server

failed with error ([chars]), SME cluster (name [chars], id %llx)
Explanation SME KMC keepalive failed
Error Message SME_CPP-3-LOG_SME_KMC_KEY_ENTITY_LOOKUP_FAILED: Key ([chars]) lookup

from KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)
Explanation SME KMC key lookup failed
Error Message SME_CPP-3-LOG_SME_KMC_KEY_LOOKUP_FAILED: Key ([chars]) lookup from KMC

server failed with error ([chars]), SME cluster (name [chars], id %llx)
Explanation SME KMC key lookup failed
Error Message SME_CPP-3-LOG_SME_KMC_KEY_UPDATE_FAILED: Key updates ([chars]) to

KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)
Explanation SME KMC key updates failed
Error Message SME_CPP-3-LOG_SME_KMC_MODIFY_DISK_STATUS_FAILED: Key ([chars]) update

disk status in KMC server failed with error ([chars]), SME cluster (name [chars],
id %llx)
Explanation SME KMC disk status update failed
2-446 OL-26589-01
Error Message SME_CPP-3-LOG_SME_REPLACE_SMARTCARD_ABORT: Replace smartcard process

(type [chars]) aborted [chars] with reason ([chars]) in SME cluster (name [chars],
id %llx)
Explanation SME KMC connection up
Error Message SME_CPP-3-SME_FIPS_MODE_ERROR: SME FIPS error: [chars]
Explanation SME module FIPS mode error
Error Message SME_CPP-3-SME_MAX_CLUSTERS_LIMIT_EXCEEDED: SME maximum clusters limit

of [dec] exceeded
Explanation The maximum sme clusters limit exceeded
SME_CPP-5
Error Message SME_CPP-5-IT_NEXUS_OPTIMUM_INTERFACE_LIMIT_REACHED: Interface

[chars] exceeded the optimum IT Nexus limit
Explanation Iterface Flow Limit
Error Message SME_CPP-5-LOG_ERR_SME_INTF_MISMATCH_NOT_PART_OF_ANY_CLUSTER: SME

interface [chars] not part of any cluster, but the DPP has state from a previous
instance of a cluster [chars] with ID [chars].
interface is not part of any cluster.
Error Message SME_CPP-5-LOG_ERR_SME_INTF_MISMATCH_NOT_PROVISIONED: SME is not

provisioned on slot [dec], but the DPP has state from a previous instance as a
crypto node [chars] of a cluster [chars] with ID [chars].
switch has not provisioned the interface for SME.
OL-26589-01 2-447
Error Message SME_CPP-5-LOG_SME_CDISK_DP_SUCCESS: SME cdisk ([chars]) data

preparation succeeded, disk-group ([chars]), cluster (name [chars], id %llx)
Explanation SME cdisk data preperation succeeded
Error Message SME_CPP-5-LOG_SME_CLUSTER_INTF_ADDED: SME interface now part of

cluster [chars] with ID [chars] as a crypto node [chars] and certificate (len [dec]
fingerprint [chars]).
Explanation Interface added to cluster successfully
Error Message SME_CPP-5-LOG_SME_CLUSTER_INTF_REMOVED: SME interface now removed

from cluster [chars] with ID [chars] as a crypto node [chars] and certificate (len
[dec] fingerprint [chars]).
Explanation Interface removed from cluster successfully
Error Message SME_CPP-5-LOG_SME_INTERFACE_DOWN: SME Interface ([chars]) DOWN
Explanation SAN Interface was brought down
Error Message SME_CPP-5-LOG_SME_INTERFACE_UP: SME Interface ([chars]) is UP
Explanation SAN Interface was brought up
Error Message SME_CPP-5-LOG_SME_IT_NEXUS_FAILURE: [chars]. [chars] bind failure.

Reason: [chars]: [hex]
Explanation SME IT Nexus bind failed
Error Message SME_CPP-5-LOG_SME_KEY_CREATE_SUCCESS: Key created ([chars])

successfully in SME cluster (name [chars], id %llx)
Explanation SME key creation succeeded
2-448 OL-26589-01
Error Message SME_CPP-5-LOG_SME_KMC_CONNECTION_DOWN: Connection to KMC server

[chars] is down with reason ([chars]) from local switch in SME cluster (name
[chars], id %llx)
Explanation SME KMC connection down
Error Message SME_CPP-5-LOG_SME_KMC_CONNECTION_INIT_FAIL: Connection

initialization to KMC server [chars] from local switch in SME cluster (name
[chars], id %llx) failed with error ([chars])
Explanation SME KMC connection initialization failed
Error Message SME_CPP-5-LOG_SME_KMC_CONNECTION_INIT_PASS: Connection

initialization to KMC server [chars] from local switch in SME cluster (name
[chars], id %llx) succeeded
Explanation SME KMC connection initialization succeeded
Error Message SME_CPP-5-LOG_SME_KMC_CONNECTION_UP: Connection to KMC server

[chars] is up from local switch in SME cluster (name [chars], id %llx)
Error Message SME_CPP-5-LOG_SME_KMC_DELETE_ALL_KEYS_SUCCESS: Delete all keys in

cluster to KMC server succeeded, SME cluster (name [chars], id %llx)
Explanation SME KMC delete keys succeeded
Error Message SME_CPP-5-LOG_SME_KMC_DELETE_KEYS_SUCCESS: Delete keys for [chars]

to KMC server succeeded, SME cluster (name [chars], id %llx)
Explanation SME KMC delete keys succeeded
OL-26589-01 2-449
Error Message SME_CPP-5-LOG_SME_KMC_KEY_ENTITY_LOOKUP_NOKEY: Key ([chars]) lookup

from KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)
Explanation SME KMC key lookup resulted in no key
Error Message SME_CPP-5-LOG_SME_KMC_KEY_ENTITY_LOOKUP_SUCCESS: Key ([chars]) lookup

from KMC server succeeded, SME cluster (name [chars], id %llx)
Explanation SME KMC key lookup succeeded
Error Message SME_CPP-5-LOG_SME_KMC_KEY_LOOKUP_SUCCESS: Key ([chars]) lookup from

KMC server succeeded, SME cluster (name [chars], id %llx)
Explanation SME KMC key lookup succeeded
Error Message SME_CPP-5-LOG_SME_KMC_KEY_UPDATE_SUCCESS: Key updates ([chars]) to

KMC server succeeded, SME cluster (name [chars], id %llx)
Explanation SME KMC key updates succeeded
Error Message SME_CPP-5-LOG_SME_KMC_MODIFY_DISK_STATUS_SUCCESS: Key ([chars])

update disk status in KMC server succeeded, SME cluster (name [chars], id %llx)
Explanation SME KMC disk status update succeeded
Error Message SME_CPP-5-LOG_SME_MASTER_KEY_REKEYED: Master Key rekeyed successfully

in SME cluster (name [chars], id %llx)
Explanation SME Master Key rekeyed
Error Message SME_CPP-5-LOG_SME_REPLACE_SMARTCARD_COMMIT: Replace smartcard

process (type [chars]) committed [chars] in SME cluster (name [chars], id %llx)
2-450 OL-26589-01
Error Message SME_CPP-5-LOG_SME_REPLACE_SMARTCARD_START: Replace smartcard process

(type [chars]) initiated [chars] in SME cluster (name [chars], id %llx)
Error Message SME_CPP-5-LOG_SME_TAPE_VOLUME_GROUP_REKEYED: Tape volume group

([chars]) rekeyed successfully in SME cluster (name [chars], id %llx)
Explanation SME Master Key rekeyed
Error Message SME_CPP-5-SME_DISABLED: SME Disabled
Explanation SME Service Disabled
Error Message SME_CPP-5-SME_DISK_DP_WAIT_KMC: crypto disk data preparation (DG:

[chars] CD NAME: [chars]) is waiting KMC validation of VPD
Explanation The data preparation is waiting for validation of VPD with KMC
Error Message SME_CPP-5-SME_DISK_DP_WAIT_PATH_ADD: crypto disk data preparation (DG:

[chars] CD NAME: [chars]) is waiting paths to be added
Explanation The data preparation is waiting for paths to be added to the crypto disk
Error Message SME_CPP-5-SME_DISK_DP_WAIT_PATH_CFG: crypto disk data preparation (DG:

[chars] CD NAME: [chars]) is waiting for the path (fabric: [chars] hwwn: 0x%Lx
twwn: 0x%Lx vsan: [dec] lun_id: [chars]) to be added
Explanation The data preparation is waiting for discovered path to be added
Error Message SME_CPP-5-SME_DISK_DP_WAIT_PATH_DISC: (DG: [chars] CD NAME: [chars])

is waiting for configured path (fabric: [chars] hwwn: 0x%Lx twwn: 0x%Lx vsan: [dec]
lun_id: [chars]) to be discovered
Explanation The data preparation is waiting for configured path to be discovered
OL-26589-01 2-451
Error Message SME_CPP-5-SME_ENABLED: SME Enabled
Explanation SME Service nabled
SME_CPP-SLOT#-2
Error Message SME_CPP-SLOT#-2-LOG_ERR_SME_DEVICE_MISCONFIG: Different configured

Devices under same physical LUN - Old Cluster Name:[chars] New Cluster
Name:[chars] Old Group Name:[chars] New Group Name:[chars] Old Device Name:[chars]
New Device Name:[chars]
Explanation Different configured devices under same physical LUN
Error Message SME_CPP-SLOT#-2-LOG_ERR_SME_ITL_MISCONFIG: Different physical LUNs

under same Tape Device - Device Name:[chars] Host PWWN:[chars] Tgt PWWN:[chars]
LUN Id:[chars] Serial Num:[chars] Serial Num:[chars]
Explanation Different physical LUNs under same Tape Device
Error Message SME_CPP-SLOT#-2-LOG_ERR_SME_LUN_MISCONFIG: Different physical LUNs

under same ITL - Old Serial Num:[chars] New Serial Num:[chars]
Explanation Different physical LUNs under same ITL
Error Message SME_CPP-SLOT#-2-LOG_ERR_SME_TAPE_BYPASS_ENC: Bypassing encryption

for partly written tape - Cluster:[chars] Tape Device:[chars] Serial Num:[chars]
Explanation This tape is currently not being encrypted
Error Message SME_CPP-SLOT#-2-LOG_ERR_SME_TAPE_CTH_FAIL: Bypassing encryption for

current tape on failed CTH verification - Cluster:[chars] Tape Device:[chars]
Serial Num:[chars]
Explanation This tape is currently not being encrypted because CTH verification has failed in DPP
2-452 OL-26589-01
Error Message SME_CPP-SLOT#-2-LOG_ERR_SME_TAPE_KEY_ERR: Getting tape keys from SUP

failed - Cluster:[chars] Tape Device:[chars] Serial Num:[chars]
Explanation There was a failure retrieving keys from SUP for this tape
SME_CPP-SLOT#-3
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISC_TIMEOUT: Module:[dec]

Host-Target:[chars]
Explanation Discovery on this IT Nexus is taking too long, please check status
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_CAP_CHANGED: capacity changed for

lun VID: [chars] PID: [chars] DID: [chars] previous max_lba: 0x%Lx blk_sz: [dec]
discovered max_lba: [hex] blk_sz: [dec] on ITL Host PWWN:[chars] Tgt PWWN:[chars]
LUN Id:0x%Lx
Explanation The capacity of the disk seems to have changed
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_CPP_ITL_MISCONFIG: Disk ITL Host

PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx has been misconfigured under a non disk
lun
Explanation Disk ITL has been misconfigured under non disk lun
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_CPP_IT_MISCONFIG: Tape device has

been misconfigured under disk IT nexus [chars] hence skipping discovery of ITLs
under this IT nexus
Explanation Remove misconfigured disk path under the tape device
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_CRYPTO_UPDATE_ITL_AUTH_FAIL: ITL

Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx with discovered VID: [chars] PID:
[chars] DID: [chars] marked by SUP as failed authentication
Explanation SUP detected authentication failure on path
OL-26589-01 2-453
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_ENTITY_INVALID: disk entity index

invalid from KMC (cluster: [chars] DG: [chars] CD NAME: [chars] VID: [chars] PID:
[chars] DID: [chars]
Explanation KMC returned an invalid disk entity index
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_INVALID_CAPACITY: Disk capacity not

supported.IT nexus:[chars] LUN Id:0x%Lx VID: [chars] PID : [chars] max_lba=[hex]
max_lba64=0x%Lx
Explanation The reported disk capacity is zero
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_ITL_CREATE_VPD_MISMATCH: ITL Host

PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx VID: [chars] PID: [chars] DID: [chars]
doesnt match cdisk DG: [chars] CD NAME: [chars] VID: [chars] PID: [chars] DID:
[chars]
Explanation The configured path does not belong to this disk
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_ITL_MISCONFIG: ITL Host PWWN:[chars]

Tgt PWWN:[chars] LUN Id:0x%Lx part of DG: [chars] CD NAME: [chars] is misconfigured
as the ITL VPD VID: [chars] PID: [chars] DID: [chars] belongs to a different cdisk
DG: [chars] CD NAME: [chars]
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_KEY_INVALID: (CLUSTER: [chars] DG:

[chars] CD NAME: [chars] keytype: [dec] keyguid: [chars] invalid
Explanation KMC returned an invalid disk key
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_KMC_VERIFY_PENDING: cluster: [chars]

DG: [chars] CD NAME: [chars] VID: [chars] PID: [chars] DID: [chars]
Explanation Vpd of the discovered path pending verification with KMC
2-454 OL-26589-01
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_MISCONFIG: A disk device

misconfiguration under disk config - Device Name:[chars] Host PWWN:[chars] Tgt
PWWN:[chars] LUN Id:%Lx
Explanation A disk device misconfigured under disk config
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_PHYENCRYPT_FAILED: CL: [chars] DG:

[chars] CD: [chars] VID: [chars] PID: [chars] DID: [chars] ISAPI_PhyCopyEncrypt()
failed isapi status: [dec] copy status: [hex] scsi status: [hex] data preparation
failed
Explanation ISAPI_PhyCopyEncrypt() failed causing data preparation to fail
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_VPD_CHANGED: VID, PID and DID changed

on ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx previous VID: [chars] PID
: [chars] DID: [chars] current VID: [chars] PID: [chars] DID: [chars]
Explanation The VPD of the disk seems to have changed
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DISK_VPD_MISMATCH: ITL Host PWWN:[chars]

Tgt PWWN:[chars] LUN Id:0x%Lx failed authentication DISK VPD(VID id: [chars] PID:
[chars] DID: [chars]) ITL(VID: [chars] PID: [chars] DID: [chars])
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_DP_TEST_IO_ERR: IT nexus [chars] lun

[chars] isapi [hex] scsi [hex] sense/asc/ascq [hex]/[hex]/[hex]
Explanation ITL DP TEST IO failure, please check status
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_ITL_CPP_ERR: Module:[dec] Host-Target

[chars] LunID:[chars]
Explanation ITL failure seen on CPP, please check status
OL-26589-01 2-455
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_IT_NEXUS_UNSUPPORTED: IT nexus [chars]

has both disks and tapes which is an unsupported configuration
Explanation IT nexus has an unsupported mix of tape and disk devices
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_NON_DISK_MISCONFIG: A non-disk device

misconfigured under disk config - Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:%Lx
Explanation A non disk device misconfigured under disk config
Error Message SME_CPP-SLOT#-3-LOG_ERR_SME_NON_TAPE_MISCONFIG: A non-tape device

misconfigured under tape config - Device Name:[chars] Host PWWN:[chars] Tgt
PWWN:[chars] LUN Id:%Ld
Explanation A disk misconfigured under tape config
SME_CPP-SLOT#-4
Error Message SME_CPP-SLOT#-4-LOG_WARN_SME_MAX_BLOCK_LEN: Maximum block length

[dec] of tape drive is 256K or less - [chars] LunID:[chars] VendorID:[chars]
ProdID:[chars] Serial Num:[chars] Cluster:[chars] Tape Device:[chars]
Explanation This tape drive may not operate correctly with SME
SNMPD Messages
This section contains the SNMPD messages.
SNMPD-1
Error Message SNMPD-1-ALERT: SNMP log alert : [chars]
Explanation SNMP log alert message.
2-456 OL-26589-01
SNMPD-2
Error Message SNMPD-2-CRITICAL: SNMP log critical : [chars]
Explanation SNMP log critical message.
SNMPD-3
Error Message SNMPD-3-ERROR: SNMP log error : [chars]
Explanation SNMP log error message.
SNMPD-4
Error Message SNMPD-4-WARNING: SNMP log warning : [chars]
Explanation SNMP log warning message.
SNMPD-5
Error Message SNMPD-5-NOTIFICATION: SNMP log notification : [chars]
Explanation SNMP log notification message.
SNMPD-6
Error Message SNMPD-6-INFO: SNMP log informational : [chars]
Explanation SNMP log info message.
OL-26589-01 2-457
SNMPD-7
Error Message SNMPD-7-DEBUG: SNMP log debugging : [chars]
Explanation SNMP log debug message.
SPAN Messages
This section contains the SPAN messages.
SPAN-2
Error Message SPAN-2-MEM_FULL: Memory allocation failed
Explanation Memory allocation failed
SPAN-3
Error Message SPAN-3-IPC_FAIL: IPC Error
Explanation Internal IPC error
Error Message SPAN-3-SYSINFO_TIMEOUT: Span timed out waiting for response from port
manager for sys info
Explanation Span request for critical system information from port manager timed out. So, span on
the new active is exiting and system manager will restart Span.
2-458 OL-26589-01
SPAN-5
Error Message SPAN-5-ATL_VSAN_DEFAULT_ALL: Default to all VSANs for SPAN egress

session
Explanation Generation 2 fabric switches support only one VSAN filter for egress SPAN session. If
no or more than one VSANs are specified, SPAN will default to use all VSANs for the egress SPAN
session
Error Message SPAN-5-SPAN_CFG_REJECT_SRC_VSAN_FILTER_NOT_SUPPORTED: Source

interface [[chars]] in dir [[chars]] removed from session [[dec]].
Explanation Interface level VSAN filters is not supported
Error Message SPAN-5-SPAN_CFG_REJECT_VSAN_SRC_PRESENT: Source VSAN [[dec]] removed

from session [[dec]].
Explanation Source VSANs are removed from the session as mixing of interface and VSANs is not
supported.
Error Message SPAN-5-SPAN_PSS_CORRUPTION: Span is starting stateless due to PSS

corruption
Explanation Due to unrecoverable PSS corruption error, SPAN starts stateless without any
configuration
Error Message SPAN-5-STATELESS_RESTART_ON_ACTIVE: Span is restarting as Span on

active sup was restarted stateless.
Explanation Due to unrecoverable error, Span on active supervisor was restarted stateless. So, the
standby Span restarts to get in sync with the stateless Span on active.
Error Message SPAN-5-STATELESS_RESTART: Span is restarting stateless.
Explanation Due to unrecoverable error, Span is starting stateless. The currently active sessions will
not be preserved. The user will have to reenter all the configuration.
OL-26589-01 2-459
SPAN-6
Error Message SPAN-6-SESSION_DOWN: Session [dec] is inactive ([chars])
Explanation Session [dec] is inactive now. Traffic for this session is no longer spanned
Recommended Action Check the reason for session inactive using command
showspansession'andtakecorrespondingaction.'
Error Message SPAN-6-SESSION_UP: Session [dec] is active, destination SD port

[chars]
Explanation Session [dec] is active now. You can monitor Spanned traffic at the destination SD port
Error Message SPAN-6-STATELESS_SWITCHOVER: Span is starting stateless after

switchover.
Explanation Active sessions are not preserved across switchover. Span is starting stateless and the
configuration will be reapplied to get back the active configuration.
SPI Messages
This section contains the SPI messages.
SPI-SLOT#-2
Error Message SPI-SLOT#-2-SPI_INFO: [chars]
Explanation SPI Informational message
STP Messages
This section contains the STP messages.
2-460 OL-26589-01
STP-2
Error Message STP-2-BLOCK_BPDUGUARD: Received BPDU on port [chars] with BPDU Guard
enabled. Disabling port.
Explanation A BPDU was received in the interface specified in the error message that has the
spanning tree BPDU Guard feature enabled. As a result, the interface was administratively shut
down.
Recommended Action Either remove the device sending BPDUs or disable the BPDU Guard feature.
The BPDU Guard feature can be locally configured on the interface or globally configured on all
ports that have portfast enabled. After the conflict has been resolved, re-enable the interface by
entering the <CmdBold
Error Message STP-2-BLOCK_DETECTED_PVST_PEER: Blocking port [chars] [PVST peer

detected].
Explanation The listed interface received SSTP BPDU indicating that peer is running PVST and will
be held in spanning tree blocking state until the interface stops receiving SSTP BPDUs
Recommended Action Either enable PVST simulation configuration for the interface or make sure
the port peer is not PVST switch
Error Message STP-2-BLOCK_PVID_LOCAL: Blocking [chars] on [chars]. Inconsistent

local vlan.
Explanation The spanning tree port associate with the listed spanning tree instance and interface will
be held in spanning tree blocking state until the Port VLAN ID (PVID) inconsistency is resolved.
The listed spanning tree instance is that of the native VLAN id of the listed interface.
Recommended Action Verify that the configuration of the native VLAN id is consistent on the
interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree will
automatically unblock the interfaces as appropriate.
Error Message STP-2-BLOCK_PVID_PEER: Blocking [chars] on [chars]. Inconsistent

peer vlan.
Explanation The spanning tree port associate with the listed spanning tree instance and interface will
be held in spanning tree blocking state until the port VLAN Id (PVID) inconsistency is resolved.
The listed spanning tree instance is that of the native VLAN id of interface on the peer switch to
which the listed interface is connected.
OL-26589-01 2-461
Error Message STP-2-BRIDGE_ASSURANCE_BLOCK: Bridge Assurance blocking port [chars]

[chars].
Explanation BPDUs were not received from a neighboring switch on the interface that has spanning
tree Bridge Assurance configured. As a result, the interface was moved to the spanning tree
Blocking state
Recommended Action LOG_STD_NO_ACTION
Error Message STP-2-BRIDGE_ASSURANCE_UNBLOCK: Bridge Assurance unblocking port

[chars] [chars].
Explanation The interface listed in the message has been restored to normal spanning tree state after
receiving BPDUs from the neighboring L2 switch/bridge
Error Message STP-2-DISPUTE_CLEARED: Dispute resolved for port [chars] on [chars].
Explanation The listed interface has stopped receiving Inferior BPDUs with designated role and
state as learning and/or forwarding. The Dispute has been resolved and if the port is still designated,
it will be taken out of the blocking state as and when appropriate.
Error Message STP-2-DISPUTE_DETECTED: Dispute detected on port [chars] on [chars].
Explanation The spanning tree has detected a Dispute on this interface. The BPDU received from
the peer is Inferior with designated role and state as learning and/or forwarding. Since this condition
could be caused by an unidirectional link failure, the interface is put into blocking state and marked
as disputed in order to prevent possible loops from being created
Recommended Action Issue the <CmdBold
Error Message STP-2-IPC_PROCESSING_ERR: Error in processing IPC message : Opcode

= [dec], Error code = [hex]
Explanation STP encountered an error in processing an MTS message. The error and message are
specified in the error message
2-462 OL-26589-01
Error Message STP-2-L2GW_BACKBONE_BLOCK: L2 Gateway Backbone port inconsistency

blocking port [chars] on [chars].
Explanation A BPDU was received on the listed interface which advertises a superior spanning tree
root bridge to that currently in use. The interface is put into blocking state and marked as L2
Gateway Backbone port inconsistent in order to prevent a suboptimal spanning tree topology to
form.
Error Message STP-2-L2GW_BACKBONE_UNBLOCK: L2 Gateway Backbone port inconsistency

cleared unblocking port [chars] on [chars].
Explanation The listed interface is no longer receiving BPDUs advertizing a superior root bridge.
The L2 Gateway Backbone port inconsistency is cleared for the interface and then it is taken out of
the blocking state if appropriate.
Error Message STP-2-LOOPGUARD_BLOCK: Loop guard blocking port [chars] on [chars].
Explanation The spanning tree message age timer has expired because and no BPDUs were received
from the designated bridge. Since this condition could be caused by an unidirectional link failure,
the interface is put into blocking state and marked as loop guard inconsistent in order to prevent
possible loops from being created
Error Message STP-2-LOOPGUARD_CONFIG_CHANGE: Loop guard [chars] on port [chars].
Explanation The spanning tree loopguard configuration for the listed interface has been changed. If
enabled, the interface will be put into blocking state and marked as loopguard inconsistent when the
message age timer expires because no BPDU were received from the designated bridge. This feature
is mainly used to detect unidirectional links
Recommended Action Verify that this is the desired configuration for the listed interface. Correct it
if this is not the desired configuration otherwise no further action is required.
Error Message STP-2-LOOPGUARD_UNBLOCK: Loop guard unblocking port [chars] on

[chars].
Explanation The listed interface has received a BPDU and therefore if the inconsistency was due to
an unidirectional link failure, now the problem is not there anymore. The loop guard inconsistency
is cleared for the interface which is taken out of the blocking state if appropriate.
OL-26589-01 2-463
Error Message STP-2-PVSTSIM_FAIL: Blocking [chars] port [chars]: Inconsistent

[chars] PVST BPDU received on VLAN [dec], claiming root [chars]
Explanation When a MST switch is connected to a PVST+ switch, the CIST (MST00) information
on the port of the MST switch must be consistently better than all the PVST+ messages if the port
is designated or consistently worse than all the PVST+ messages if the port is root. If this constraint
is not respected, the port on the MST switch is blocked in order to prevent a potential bridging loop
Recommended Action When STP is converging after a new switch, or switch port is added to the
topology, this condition may happen transiently. The port unblocks automatically in such cases. If
the port remains blocked, identify the root bridge as reported in the message, and configure a worse
or better priority for the VLAN spanning tree consistent with the CIST role on the port of the MST
switch. There could be more inconsistencies than the message indicates, and the port will not
recover until all such inconsistencies are cleared. If you cannot determine which other VLANs have
inconsistencies, disable and reenable the port. This message will appear again and specify another
VLAN with inconsistencies to be fixed. Repeat this process until all inconsistencies on all VLANs
are cleared.
Error Message STP-2-PVSTSIM_OK: PVST Simulation inconsistency cleared on port

[chars].
Explanation The listed interface is no longer receiving PVST BPDUs advertising an information
inconsistent with the CIST port information. The PVST Simulation Inconsistency is cleared and the
interface returns to normal operation
Error Message STP-2-RANDNUM_FAIL: [chars]
Explanation There was a critical error during random number generation. [chars] indicates details
of the error
Error Message STP-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on [chars]
[chars].
Explanation The list interface received a SSTP BPDU that was missing the VLAN id tag. The BPDU
is discarded.
2-464 OL-26589-01
Error Message STP-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id

[dec] on [chars] [chars].
Explanation The listed interface received a SSTP BPDU that is tagged with a VLAN id that does
not match the VLAN id on which the BPDU was received. This occurs when the native VLAN is
not consistently configured on both ends of a 802.1Q trunk.
Error Message STP-2-ROOTGUARD_BLOCK: Root guard blocking port [chars] on [chars].
Explanation A BPDU was received on the listed interface which advertizes a superior spanning tree
root bridge to that currently in use. The interface is put into blocking state and marked as root guard
inconsistent in order to prevent a suboptimal spanning tree topology to form.
Error Message STP-2-ROOTGUARD_CONFIG_CHANGE: Root guard [chars] on port [chars].
Explanation The spanning tree root guard configuration for the listed interface has been changed. If
enabled, any BPDU received on ths interface which advertizes a superior spanning tree root bridge
to that already in use will cause the interface to be put into blocking state and marked as root guard
inconsistent.
Recommended Action Verify that this is the desired configuration for the listed interface. Correct it
if this is not the desired configuration otherwise no further action is required.
Error Message STP-2-ROOTGUARD_UNBLOCK: Root guard unblocking port [chars] on

[chars].
Explanation The listed interface is no longer receiving BPDUs advertizing a superior root bridge.
The root guard inconsistency is cleared for the interface and then it is taken out of the blocking state
if appropriate.
Error Message STP-2-SET_PORT_STATE_FAIL: Port state change req to PIXM failed,

status = [hex] [[chars]] vdc [dec], tree id [dec], num ports [dec], ports [chars]
state [chars], opcode [chars], msg id ([dec]), rr_token [hex]
Explanation The port set port state has failed. check port
OL-26589-01 2-465
Error Message STP-2-SET_PORT_STATE_TIMEOUT: Port state change req to PIXM timedout

after [dec] sec. vdc [dec], tree id [dec], num ports [dec], ports [chars] state
[chars], opcode [chars], msg id ([dec]), rr_token [hex]
Explanation The port set port state has timedout. check port
Error Message STP-2-STP_INIT: STP initialization of [chars] [chars]
Explanation STP initialization failed
Error Message STP-2-STP_ISSU_LC_RESET: STP resetting LC[dec] to prevent Loops

during ISSU caused by a topology change in the network. Peer on [chars] [chars]
could not be Disputed
Explanation This can happen as a result of a topology change in the network while the Linecard was
undergoing ISSU. Since STP cannot change the port state to blocking on the Linecard undergoing
ISSU, it will first try to prevent the Loop by causing a Dispute on the peer ports forcing them into
blocking state. But if the peer does not support Dispute mechanism, and STP detects a potential
Loop, it will reset the Linecard to prevent the Loop
Error Message STP-2-UNBLOCK_CONSIST_PORT: Unblocking port [chars] on [chars]. Port

consistency restored.
Explanation The Port VLAN ID and/or Port Type inconsistencies have been resolved and spanning
tree will now unblock the listed interface of the listed spanning tree instance as appropriate.
Error Message STP-2-UNBLOCK_DETECTED_PVST_PEER: Unblocking port [chars] [PVST peer

detected].
Explanation The listed interface has stopped receiving SSTP BPDUs and so will be restored to
normal spanning tree state
2-466 OL-26589-01
Error Message STP-2-VLAN_PORT_LIMIT_EXCEEDED: The number of vlan-port instances

exceeded [[chars] mode] recommended limit of [dec]
Explanation The total number of individual VLAN ports, in the spanning tree mode specified in the
error message, has exceeded the limit specified in the error message. VLANs can be counted more
than once; if VLAN 1 is carried on 10 interfaces, it will count as 10 VLAN ports. Note that bundling
is ignored for purposes of this count; if 8 interfaces on the same module are in one bundle, and the
port channel is carrying VLAN 1, it will count as 1 VLAN ports.
Recommended Action Reduce the number of trunks and VLANs configured in the switch. Keep the
VLAN port count below the recommended limit specified in the configuration documentation. Enter
the <CmdBold
Error Message STP-2-VPC_PEERSWITCH_CONFIG_DISABLED: vPC peer-switch configuration

is disabled. Please make sure to change spanning tree bridge priority as per the
recommended guidelines.
Explanation The vPC peer-switch configuration has been changed. If enabled, please make sure to
configure spanning tree bridge priority as per the recommended guidelines. If disabled, please make
sure to change spanning tree bridge priority as per the recommended guidelines.
Recommended Action Verify that this is the desired configuration and follow the vPC peer-switch
Error Message STP-2-VPC_PEERSWITCH_CONFIG_ENABLED: vPC peer-switch configuration

is enabled. Please make sure to configure spanning tree bridge priority as per
recommended guidelines to make vPC peer-switch operational.
Explanation The vPC peer-switch configuration has been changed. If enabled, please make sure to
configure spanning tree bridge priority as per the recommended guidelines. If disabled, please make
sure to change spanning tree bridge priority as per the recommended guidelines.
Recommended Action Verify that this is the desired configuration and follow the vPC peer-switch
Error Message STP-2-VPC_PEER_LINK_INCONSIST_BLOCK: vPC peer-link detected [chars]

blocking [chars] [chars].
Explanation VPC Peer-link detected the STP inconsistency mentioned in the message. This will
impact the STP topology for vPCs and can cause frame duplications. As a result, the interface was
moved to the spanning tree Blocking state
OL-26589-01 2-467
Error Message STP-2-VPC_PEER_LINK_INCONSIST_ERRDISABLE: vPC Peer-link detected

[chars]. Disabling [chars].
Explanation VPC Peer-link detected the STP inconsistency mentioned in the message. This will
impact the STP topology for vPCs and can cause frame duplications. As a result, the vPC Peer-link
was administatively shut down.
Recommended Action Please resolve the inconsistency reported in this message on the vPC Peer link.
After the conflict has been resolved, re-enable the interface by entering the <CmdBold
Error Message STP-2-VPC_PEER_LINK_INCONSIST_UNBLOCK: vPC peer-link inconsistency

cleared unblocking [chars] [chars].
Explanation VPC Peer-link inconsistency is cleared and the vPC interface listed in the message has
been restored to normal spanning tree state.
STP-3
Error Message STP-3-BLOCK_PORT_TYPE: Blocking [chars] on [chars]. Inconsistent

port type.
Explanation The listed interface is being held in spanning tree blocking state until the port type
inconsistency is resolved.
Recommended Action Verify that the configuration and operational state of the listed interface and
that of the interface to which it is connected have the same mode (access vs trunk). If mode is trunk,
verify the same encapsulation (ISL, 802.1Q). Once these parameters are consistent, spanning tree
will automatically unblock the interfaces as appropriate.
Error Message STP-3-PORT_SELF_LOOPED: Received BPDU src mac same as that of port.
Port self loopback detected. Port [chars] being disabled
Explanation The source MAC address contained in a BPDU received on the listed interface matches
the MAC address assigned to that interface This indicates the possibility that a port is looped back
to itself, possibly due to a diagnostic cable being plugged in. The interface will be administratively
shutdown.
Recommended Action Check the interface configuration and any cable plugged into the interface.
Once problem resolved, re-enable interface by doing a no shutdown in the interface configuration.
Copy the error message as it is printed and also copy the output of a show interface for the interace
listed in the error message.
2-468 OL-26589-01
Error Message STP-3-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk [chars]

[chars].
Explanation A SSTP BPDU was received on the listed interface that was not operationally a trunk.
Recommended Action Verify that the configuration and operational state of the listed interface and
that of the interface to which it is connected have the same mode (access vs trunk). If mode is trunk,
verify the same encapsulation (none, ISL, 802.1Q). Once these parameters are consistent, spanning
tree will automatically unblock the interfaces as appropriate.
STP-4
Error Message STP-4-FORWARDTIME_CONFIG_CHANGE: Forward Delay time change to [dec]

seconds for instance [chars] is not recommended as it can cause STP data loops
during High Availability Dual-Supervisor Switchover and In-Service Software
Upgrade
Explanation It is stongly recommended to avoid changing forward delay time value to less than the
default value of 15 seconds since it can cause STP data loops during High Availability
Dual-Supervisor Switchover and also during In-Service Software Upgrade. Please read the release
notes.
Recommended Action Please change the forward delay time to be greater than or equal to the default
value of 15 seconds
Error Message STP-4-HELLOTIME_CONFIG_CHANGE: Hello time change to [dec] seconds

for instance [chars] is not recommended as it can trigger STP Topology Changes
during High Availability Dual-Supervisor Switchover and In-Service Software
Upgrade
Explanation It is stongly recommended to avoid changing Hello time value to less than the default
value of 2 seconds since it can trigger STP Topology change during High Availability
Dual-Supervisor Switchover and also during In-Service Software Upgrade. Please read the release
notes.
Recommended Action Please change the hello time to be greater than or equal to the default value of
2 seconds.
Error Message STP-4-MAC_ADDR_FLUSH_REQ_TIMEOUT: MAC Address Flush req to L2FM

timedout after [dec] sec. vdc [dec], tree id [dec], num ports [dec], ports [chars],
opcode [chars], msg id ([dec]), rr_token [hex]
Explanation The MAC Address Flush Request to L2FM has timedout. check port
OL-26589-01 2-469
STP-6
Error Message STP-6-FIRST_BPDU_TX: First BPDU transmitted
Explanation First BPDU transmitted.
Error Message STP-6-MST_DIGEST: MST digest changed to [chars], pre-std digest

changed to [chars]
Explanation MST Region configuration has changed
Error Message STP-6-MST_PORT_BOUNDARY: Port [chars] [chars] as MST Boundary port
Explanation MST Boundary port status of the specified port is changed
Error Message STP-6-MST_PORT_PRE_STANDARD: Port [chars] [chars] as MST

Pre-standard port.
Explanation MST pre-standard status of the specified port is changed
Error Message STP-6-PORT_ADDED: Interface [chars], added to [chars] with role

[chars], state [chars], cost [dec], priority [dec], link-type [chars]
Explanation This spanning tree port has been added
Error Message STP-6-PORT_COST: Port [chars] instance [chars] cost changed to [dec]
Explanation The spanning tree port cost has changed for the specified port
Error Message STP-6-PORT_DELETED: Interface [chars], removed from [chars]
Explanation This spanning tree port has been deleted
2-470 OL-26589-01
Error Message STP-6-PORT_LINK_TYPE: Port [chars] instance [chars] link changed to

[chars]
Explanation The spanning tree port link type has changed for the specified port
Error Message STP-6-PORT_PRIORITY: Port [chars] instance [chars] priority changed

to [dec]
Explanation The spanning tree port priority has changed for the specified port
Error Message STP-6-PORT_RANGE_ADDED: Interface [chars] added to [chars] with cost

[dec], priority [dec], link-type [chars]
Explanation This spanning tree port has been added
Error Message STP-6-PORT_RANGE_DELETED: Interface [chars] removed from [chars]
Explanation This range spanning tree logical ports has been deleted
Error Message STP-6-PORT_RANGE_ROLE: new_role=[chars] interface=[chars] [chars]
Explanation The role of the range of spanning tree logical ports has changed
Error Message STP-6-PORT_RANGE_STATE: new_state=[chars] interface=[chars] [chars]
Explanation The range of Spanning-Tree logical ports have changed state.
Error Message STP-6-PORT_ROLE: Port [chars] instance [chars] role changed to

[chars]
Explanation The spanning tree port role has changed for the specified port
OL-26589-01 2-471
Error Message STP-6-PORT_STATE: Port [chars] instance [chars] moving from [chars]
to [chars]
Explanation The Spanning-Tree port has changed state.
Error Message STP-6-PRESTD_NEIGH: This switch has received a pre-standard MST BPDU
on port [chars]: Invoking pre-standard MST BPDU transmission on this port.
Explanation The switch has received a pre-standard MST BPDU on a port. The switch will
automatically adjust its mode of operation on this port and will start sending pre-standard BPDUs.
Error Message STP-6-ROOT: Root bridge for [chars] changed to [chars]
Explanation The spanning tree root bridge has changed
Error Message STP-6-SERVICE_UP: Initialized [chars]
Explanation STP line 2.
Error Message STP-6-STATE_CREATED: Internal state created [chars]
Explanation STP has created its internal state stateless/stateful [chars].
SVC_BATTERY Messages
This section contains the SVC_BATTERY messages.
SVC_BATTERY-SLOT#-2
Error Message SVC_BATTERY-SLOT#-2-BATTERY_NOT_OPERATIONAL: Battery [dec]

temperature [dec] C is outside the operational range (-10C to 65C).
Explanation The battery temperature is outside the operational range (-10C to 65C).
Recommended Action Verify fan operation with [show environment fan], and take action to cool
down the switch.
2-472 OL-26589-01
Error Message SVC_BATTERY-SLOT#-2-BATTERY_NOT_PRESENT: Battery [dec] is not

present.
Explanation The line card does not have sufficient number of batteries. Two batteries are needed.
Recommended Action Remove the line card and plug in batteries in the battery slots that are empty.
Error Message SVC_BATTERY-SLOT#-2-CHARGING_DISABLED: Temperature outside permitted

range for battery charging (5C-40C).
Explanation The temperature of the linecard is not within the range to permit battery charging.
Recommended Action Make sure the temperature of the linecard is between 5C and 40C
Error Message SVC_BATTERY-SLOT#-2-CHARGING_FAILURE: Charging failure in battery

[dec] ([hex]).
Explanation The module encountered failures while charging a battery.
Recommended Action Replace the battery.
Error Message SVC_BATTERY-SLOT#-2-CLOCK_INCORRECT: System clock is running behind,

battery conditioning will be affected.
Explanation The Vegas system clock is running behind the actual time. This will affect the battery
conditioning.
Recommended Action Use clock set CLI command to set the correct time
Error Message SVC_BATTERY-SLOT#-2-COMMUNICATION_FAILURE: Communication failure

with battery [dec].
Explanation The module encountered failures while communicating with a battery.
Error Message SVC_BATTERY-SLOT#-2-CONDITIONING_DISABLED: Temperature outside

permitted range for battery conditioning (5C-40C).
Explanation The temperature of the linecard is not within the range to permit battery conditioning.
Error Message SVC_BATTERY-SLOT#-2-DISCHARGING_FAILURE: Discharging failure in

battery [dec] ([hex]).
Explanation The module encountered failures while discharging a battery.
OL-26589-01 2-473
SVC_BATTERY-SLOT#-4
Error Message SVC_BATTERY-SLOT#-4-BATTERY_CAPACITY_LOW: Battery capacity is below

the required threshold.
Explanation The battery is lower than the required threshold.
Recommended Action Make sure the temperature is within the range to allow charging.
SVC_BATTERY-SLOT#-6
Error Message SVC_BATTERY-SLOT#-6-BATTERY_CAPACITY_OK: Battery capacity is above

the required threshold.
Explanation The battery is above the required threshold.
Error Message SVC_BATTERY-SLOT#-6-CONDITIONING_CANCELLED: Temperature outside

permitted range for battery conditioning (5C-40C). Battery [dec] conditioning
cancelled.
Explanation The temperature of the linecard is not within the range to permit battery conditioning.
Error Message SVC_BATTERY-SLOT#-6-CONDITIONING_COMPLETED: Conditioning of battery

[dec] completed successfully.
Explanation Conditioning process started for a battery is completed successfully.
Error Message SVC_BATTERY-SLOT#-6-CONDITIONING_RESUMED: Conditioning of battery

[dec] resumed.
Explanation Conditioning process for a battery is resumed.
Error Message SVC_BATTERY-SLOT#-6-CONDITIONING_STARTED: Conditioning of battery

[dec] started.
Explanation Conditioning process started for a battery
2-474 OL-26589-01
SVC Messages
This section contains the SVC messages.
SVC-0
Error Message SVC-0-NODE_EMERG_MSG: [chars]
Explanation Syslog message from a SVC interface node
SVC-1
Error Message SVC-1-NODE_ALERT_MSG: [chars]
SVC-2
Error Message SVC-2-NODE_CRIT_MSG: [chars]
Error Message SVC-2-SVC_SYSLOG_INIT_FAILED: Initialization failed for SVC:

[chars], Reason: [hex]
Explanation Initialization failed for SVC
Error Message SVC-2-SVC_SYSLOG_NO_PORT_CHAN: Too many PortChannels allocated by

user for interface [chars]
Explanation SVC interface needs PortChannels to operate. Too many PortChannels have been
allocated by the user for the interface to operate correctly.
Recommended Action Please delete unneeded user configured PortChannels and shutdown the SVC
interface. Once complete, please bring the SVC interface back up.
OL-26589-01 2-475
Error Message SVC-2-SVC_SYSLOG_PATH_FAILURE: System health detected SVC packet

path failure for [chars].
Explanation The CSM has been brought down by the System Health monitor. System Health has
detected a failure in the packet path between the SVC interface on the CSM and the backplane. This
System Health test is run periodically.
Recommended Action Issue a "no shutdown" on the SVC interface to bring the node back online. If
a subsequent packet path failure occurs, the CSM module should be replaced.
Error Message SVC-2-SVC_SYSLOG_URIFS_FAILURE: [chars] is unreachable for reason:

[chars]
Explanation SVC interface modflash is not accessable. Modflash is the name of the filesystem local
to the SVC interface, and is typically used for coredumps and temporary file transfers.
Recommended Action Please shutdown and bring up the SVC interface in question to regain access
to the modflash filesystem.
SVC-3
Error Message SVC-3-NODE_ERR_MSG: [chars]
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec]

SS_EID_EC_ER_ACTIVATE_CLUSTER_IP_FAILED ) Activate cluster IP failed [chars]
Explanation Unable to activate the cluster IP for the config node. It will not be possible to execute
configuration commands.
Recommended Action 1. Shutting the interfaces of the node will force this node out of the cluster and
cause another node to become the config node, which should restore the ability to execute
configuration commands. 2. If the error persists, re-install the code on the node. The node will then
have to be removed and re-added back to the cluster. 3. Ensure that the software is at the latest level
on the cluster. If not, upgrade the cluster and if necessary repeat step 2 with the latest level of code.
4. If the error continues, ask IBM Product Support for assistance.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_BATT_FAILURE )

Battery Failed [chars]
Explanation The battery module on the Caching Services Module has failed. The nodes on the CSM
will have shutdown. Other log entries may accompany this error.
Recommended Action Reload the Caching Services Module. If the error persists, replace the Caching
Services Module.
2-476 OL-26589-01
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_DISK_FAILURE )

Internal Disk Drive Failed [chars]
Explanation The internal disk drive for the node on the Caching Services Module has failed. The
node will have shutdown. Other log entries may accompany this error.
Recommended Action Reload the Caching Services Module. If the error persists, replace the Caching
Services Module.

SS_EID_EC_ER_DUMP_RESTORE_FAILED ) Restore of hardened data failed [chars]
Explanation Restore of customer data failed. This error will be accompanied by other log entries.
Recommended Action Examine the log for other error entries and follow the actions recommended.
If no other entries are found: 1. Re-install the code on the node. The node will have to be removed
and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If
not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error
continues, ask IBM Product Support for assistance. It may be necessary to replace the Caching
Services Module.

SS_EID_EC_ER_INVALID_BATT_CAPACITY ) Get battery capacity failed [chars]
Explanation The process was unable to get the battery capacity. Possibly due to communication
failures with the CPP processor in the line card. Node was rebooted due to this error.
Recommended Action If this error is repeated continously, 1. Re-install the code on the line card. The
node(s) will then have to be removed and re-added back to the cluster. 2. Ensure that the software
is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the
latest level of code. 3. If the error persists, replace the Caching Services Module.

SS_EID_EC_ER_OPEN_COMMITTED_FILE_FAILED ) Error attempting to open file [chars]
Explanation Process was unable to open the committed file. Node was rebooted due to this error.
Recommended Action If this error is repeated continously, 1. Re-install the code on the node. The
node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at
the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest
level of code. 3. If the error continues, ask IBM Product Support for assistance.
OL-26589-01 2-477

SS_EID_EC_ER_SET_BATT_THRESHOLD_FAILED ) Set battery threshold failed [chars]
Explanation The process was unable to set the battery threshold. Possibly due to fatal
communication failures with the power management module in the line card or the power
management module has crashed. Node was rebooted due to this error.
Recommended Action If this error is repeated continously, 1. Re-install the code on the line card. The
node(s) will then have to be removed and re-added back to the cluster. 2. Ensure that the software
is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the
latest level of code. 3. If the error persists, replace the Caching Services Module.

SS_EID_IC_EV_NODE_DISENFRANCHISED ) Node missing [chars]
Explanation A node is missing from the cluster.
Recommended Action 1. If it is not obvious which node in the cluster has failed, check the status of
the nodes and find the node with a status of offline. 2. Repair the failing node. 3. When the repair
has been completed, this error will automatically be marked as fixed. 4. Check the node status. If all
the nodes in the cluster are now online, but the error in the log has not been marked as fixed,
manually mark the error as fixed.

SS_EID_PL_ER_CLUSTER_PATH_FAILURE ) Cluster path failure [chars]
Explanation A cluster path has failed. The node is unable communicate with all the other nodes in
the cluster.
Recommended Action 1. Repair the fibre-channel network fabric. 2. Check the status of the node port.
If the status of the port shows as online, mark the error you have just repaired as fixed.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_CPU_QUANTITY )

Processor change detected [chars]
Explanation The Caching Services Module is failing.
Recommended Action 1. Replace the Caching Services Module. 2. Check node status. If all nodes
show a status of online, mark the error you have just repaired fixed.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_DISK_FULL ) Node

hard disk full [chars]
Explanation The error that is logged in the cluster error log indicates a software problem in the
cluster.
Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Delete files
from the /dumps directory. 3. Run a configuration dump and a logged data dump. Save the dump
data. 4. Ask IBM Product Support for assistance. 5. Mark the error you have just repaired as fixed.
2-478 OL-26589-01
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_FC_ADAP_FAIL )

Logical Fibre Channel port reported failed [chars]
Explanation No active/functioning logical FC port was detected by the software.
Recommended Action Reload the node. If the problem persists, replace the Caching Services Module.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_FC_ADAP_QUANTITY

) Logical Fibre Channel port missing [chars]
Explanation No active/functioning FC port was detected by the software.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_FC_PORT_QUANTITY

) Logical Fibre Channel port reported not operational [chars]
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_NODE_WARMSTART )

Node warmstarted due to software error [chars]
cluster.
Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Run a
configuration dump and a logged data dump. Save the dump data. 3. Ask IBM Product Support for
assistance. 4. Mark the error you have just repaired as fixed.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_POWER_DOMAIN )

Power domain error [chars]
Explanation The two nodes in an IO group are on the same Caching Services Module.
Recommended Action Determine what the configuration should be. Remove one of the nodes and add
a node to the IO group which is not on the same Caching Services Module.

SS_EID_VG_ER_MDISK_GROUP_OFFLINE ) A Managed Disk group is offline [chars]
Explanation An Mdisk group is offline.
Recommended Action 1. Repair the enclosure or disk controller. 2. Start a cluster discovery
operation. 3. Check managed disk status. If all managed disks show a status of online, mark the error
you have just repaired as fixed.
OL-26589-01 2-479
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VG_ER_MED_ERRS_TOO_HIGH

) Media errors on back-end Managed Disk [chars]
Explanation Media errors on backend managed disk.
Recommended Action 1. Repair the enclosure or disk controller. 2. Include the managed disk into
the cluster. 3. Check managed disk status. If all managed disks show a status of online, mark the
error you have just repaired as fixed.

SS_EID_VL_ER_BASE_EVENT_RESOURCE_RAN_OUT ) Software error [chars]
cluster.
Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Run a
configuration dump and a logged data dump. Save the dump data. 3. Ask IBM Product Support for
assistance. 4. Mark the error you have just repaired as fixed.

SS_EID_VL_ER_CONTROLLER_CONFIG_INVALID ) Incorrect controller configuration
[chars]
Explanation Incorrect disk controller configuration.
Recommended Action 1. Using service documentation for the disk controller, check that the correct
configuration is set up for the disk controller. See also the IBM TotalStorage SAN Volume
Controller for Cisco MDS 9000: Configuration Guide. 2. Mark the error you have just repaired as
fixed. 3. Start a cluster discovery operation.

SS_EID_VL_ER_DEVICE_PORT_LOGIN_LOSS ) Number of controller logins reduced [chars]
Explanation The number of controller logins has been reduced. One possible cause is that the user
intentionally reconfigured the system.
Recommended Action 1. Check whether the controller has regained connectivity. If it has not, check
the cable connection to the remote-device port. 2. If all logins to a remote-device port have failed
and you cannot solve the problem by changing cables, check the condition of the remote-device port
and the condition of the remote device. 3. Start a cluster discovery operation. 4. Check the status of
the disk controller. If all disk controllers show a good status, mark the error you have just repaired
as fixed.
2-480 OL-26589-01

SS_EID_VL_ER_DEVICE_RESOURCE_RAN_OUT ) Too many controllers were presented to the
cluster [chars]
Explanation The configuration is not valid. Too many devices have been presented to the cluster or
node.
Recommended Action 1. Remove unwanted devices from the fibre-channel network fabric. 2. Start a
cluster discovery operation to find devices. 3. List all connected managed disks. Check with the
customer that the configuration is as expected. Mark the error you have just repaired fixed.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_ERP ) Error

Recovery Procedure occurred [chars]
Explanation A managed disk error recovery procedure (ERP) has occurred. This error has been
reported because a large number of disk error recovery procedures have been performed by the disk
controller. The problem is probably caused by a failure of some other component on the SAN.
Recommended Action 1. View the error log entry and determine the managed disk that was being
accessed when the problem was detected. (Note that the sense data from the disk controller is
recorded in the cluster error log and can be accessed there. This data is not available in the switch
system log.) 2. Perform the disk controller problem determination and repair procedures for the
mdisk determined in step 1. 3. Perform fibre channel switch problem determination and repair
procedures for the fibre channel switches containing the node, and connected to the disk controller
that is managing the mdisk, and any fibre channel switches in the fibre channel path between those
switches. 4. If any problems are found and resolved in steps 2 and 3, mark this error as fixed. 5. If
no switch or disk controller failures were found in steps 2 and 3, take an error log dump. Call your
hardware support center.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_ERROR ) Managed

Disk I/O error [chars]
Explanation A managed disk or managed disk controller port has been excluded because of
excessive errors or unusual behavior.
Recommended Action 1. Repair the enclosure or disk controller. 2. Check the managed disk status.
If any managed disks show a status of online, mark the error you have just repaired as fixed. If any
managed disks show a status of excluded, included the managed disks and then mark the error as
fixed.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_THRESHOLD )

Managed Disk error count threshold exceeded [chars]
If any managed disks show a status of online, mark the error you have just repaired as fixed. If any
fixed.
OL-26589-01 2-481
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_IO_TIMEOUT_OVERALL

) Timeout due to excessive processing time [chars]
Explanation A managed disk has timed out. This error has been reported because a large number of
disk timeout conditions have been detected. The problem is probably caused by a failure of some
other component on the SAN.
Recommended Action 1. Repair problems on all disk controllers and switches on the same SAN as
this cluster. 2. If problems are found, mark this error as fixed. 3. If no switch or disk controller
failures can be found, take an error log dump and call your hardware support center.

SS_EID_VL_ER_LOCAL_PORT_EXCLUDED ) Local FC port excluded [chars]
Explanation A local fibre-channel port has been excluded.
Recommended Action 1. Repair the fibre-channel network fabric. 2. Check the status of the disk
controller. If all disk controllers 3. show good status, mark the error you have just repaired fixed. 4.
If the error persists and no other cause can be determined, replace the Caching Services Module.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_LOGIN_EXCLUDED )

Login excluded [chars]
Explanation Login has been excluded.
Recommended Action 1. In the sequence shown, exchange the FRUs for new FRUs: Fibre Channel
cable, switch to remote port. 2. Start a cluster discovery operation to recover the login. 3. Check the
status of the disk controller. If all disk controllers show a good status, mark the error you have just
repaired fixed. 4. If the error persists and no other cause can be determined, replace the Caching
Services Module.

SS_EID_VL_ER_LUN_RESOURCE_RAN_OUT ) Too many LUNs were presented to a node [chars]
node.

SS_EID_VL_ER_MDISK_ACCESS_INVALID ) Access beyond end of disk, or Managed Disk
missing [chars]
Explanation The error that is logged in the cluster error log indicates a software problem either in
the cluster, or in a disk enclosure or disk controller that is connected to the node.
Recommended Action 1. Ensure that the software is at the latest level on the cluster and on the disk
controllers. 2. Run a configuration dump and a logged data dump. Save the dump data. 3. Ask IBM
Product Support for assistance. 4. Mark the error you have just repaired as fixed.
2-482 OL-26589-01

SS_EID_VL_ER_MDISK_DEVICE_PORT_EXCLUDED ) Remote Port excluded for a specific
Managed Disk and Node [chars]
Explanation A remote fibre-channel port has been excluded.
Recommended Action 1. View the error log. Note the mdisk ID associated with the error code. 2.
Using the mdisk ID, determine the failing disk controller. 3. Refer to the service documentation for
the disk enclosure or disk controller and the fibre-channel network fabric to resolve the reported
problem. 4. Start a cluster discovery operation to recover the excluded fibre-channel port. 5. Include
the managed disk that you noted in step 1. 6. Check the status of the disk controller. If all disk
controllers show a good status, mark the error you have just repaired fixed. 7. If all disk controllers
do not show a good status, contact the IBM support center to resolve the problem with the disk
controller.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_MDISK_EXCLUDED )

Managed Disk excluded due to excessive errors, or all device ports excluded [chars]
If any managed disks show a status of online, mark the error you have just repaired as fixed. If all
fixed.

SS_EID_VL_ER_MDISK_INITIALISE_INVALID ) Invalid blocksize, capacity or LUN
identity has changed during Managed Disk initialisation [chars]
Explanation Access beyond end of disk. The initialization of the managed disk has failed.
Recommended Action 1. Check the status of the managed disk and of the managed-disk group. 2.
Include the managed disk into the cluster. 3. Check the managed disk status. If all managed disks
show a status of online, mark the error you have just repaired as fixed. 4. If not all managed disks
show a status of online, check the status of the disk controller.

SS_EID_VL_ER_MDISK_RESOURCE_RAN_OUT ) Too many Managed Disks were presented to the
cluster [chars]
node.
OL-26589-01 2-483

SS_EID_VL_ER_QUORUM_DISK_CREATION_FAILURE ) A suitable Managed Disk for use as a
Quorum Disk was not found [chars]
Explanation No Mdisk is suitable for use as a quorum disk. When a cluster is created three disks are
automatically selected as quorum disks. A quorum disk is needed to enable a tie-break when some
cluster members are missing. To become a quorum disk: The Mdisk must be accessible by all nodes
in the cluster and the Mdisk must have free extents. This error code is produced when at least one
quorum disk is not accessible by all nodes in the cluster. A quorum disk might not be available
because of a fibre-channel network failure or because of a fibre-channel switch zoning problem.
Recommended Action 1. Resolve any known fibre-channel network problems. 2. Ask the customer
to confirm that Mdisks have been created and that those mdisks have free extents. 3. List the manage
disks. If at least one managed disk shows a mode of managed, mark the error you have just repaired
as fixed. 4. If the customer is unable to make the appropriate changes, ask IBM Software Support
for assistance.

SS_EID_VL_ER_QUORUM_DISK_NOT_AVAILABLE ) Quorum Disk not available [chars]
Explanation One or more quorum disks were not discovered by the node.
Recommended Action 1. Resolve any known fibre-channel network problems. 2. Check managed
disk status. If any managed disks are offline or excluded perform the disk controller problem
determination and repair procedures for the managed disks. 3. Start a cluster discovery operation. 4.
Check managed disk status. If all managed disks show a status of online, mark the error you have
just repaired as fixed.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ALL_SSH_KEYS_REMOVED

) Attempt to delete SSH keys (no effect) [chars]
Explanation
svctaskrmallsshkeys'commandhasbeeninvoked.ThiscommandhasnoeffectinSANVolumeControllerf
orCiscoMDS9000,butisretainedforcompatibility.'

SS_ERR_CFG_REMOTE_CREATEPARTNERSHIP ) Remote Copy partnership created [chars]
Explanation svctaskmkpartnership'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'

SS_ERR_CFG_REMOTE_DELETEPARTNERSHIP ) Remote Copy partnership deleted [chars]
Explanation svctaskrmpartnership'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
2-484 OL-26589-01

SS_ERR_CFG_REMOTE_MODIFYPARTNERSHIP ) Remote Copy partnership modified [chars]
Explanation svctaskchpartnership'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_SSH_KEY_ADDED )

Attempt to add SSH key (no effect) [chars]
Explanation
svctaskaddsshkey'commandhasbeeninvoked.ThiscommandhasnoeffectinSANVolumeControllerfor
CiscoMDS9000,butisretainedforcompatibility.'
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_SSH_KEY_REMOVED )

Attempt to delete SSH key (no effect) [chars]
Explanation
svctaskrmsshkey'commandhasbeeninvoked.ThiscommandhasnoeffectinSANVolumeControllerforC
iscoMDS9000,butisretainedforcompatibility.'
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_CR_START ) Cluster

recovery required [chars]
Explanation The node has detected that cluster recovery is required and is waiting for for human
intervention to continue.
Recommended Action Contact IBM Product support for assistance.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_DATA_CORRUPT ) Node

data corrupted - node rejected from cluster [chars]
Explanation Node data is readable but corrupted. The node has been rejected from the cluster.
Recommended Action 1. Re-install the code on the node. The node will have to be removed and
re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not,
upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error
Services Module.
OL-26589-01 2-485
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_DATA_UNREADABLE )

Node data unreadable - node rejected from cluster [chars]
Explanation Node data could not be read. The node has been rejected from the the from cluster.
Recommended Action 1. Re-install the code on the node. The node will have to be removed and
re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not,
upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error
Services Module.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_HDW_CONFIG )

Processor not valid [chars]
Explanation The node has detected unexpected differences in the processor vital data.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_MEM_SIZE ) Memory

size error [chars]
Explanation The detected memory size does not match the expected memory size for the cluster.
Recommended Action A memory module on the Cisco MDS 9000 Caching Services Module is
probably faulty. Reload the node. If the error persists, replace the Caching Services Module.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_MISSING_RES ) Unable

to form a cluster due to lack of cluster resources [chars]
Explanation The node is unable to locate sufficient other nodes in the cluster and/or the quorum
disk controller needed in order to form a cluster.
Recommended Action Check the status of the quorum disk controller and the other nodes in the
cluster. If the quorum disk has failed, perform the problem determination procedures for the disk
controller. Otherwise perform problem determination on the missing nodes and network.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_NO_FABRIC ) The node

is unable to see the FC fabric [chars]
2-486 OL-26589-01
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_PWR_DMN_ERR ) Power

domain error [chars]
Explanation The two nodes in an IO group are on the same Caching Services Module.
Recommended Action Determine if both nodes on the Caching Services Module are in fact in the
same IO group. If so, determine what the configuration should be. Remove one of the nodes and add
a node to the IO group which is not on the same Caching Services Module. If not, ask IBM Product
Support for assistance.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_REPEATED_ASSERTS )

Node repeatedly crashing due to a software fault [chars]
Explanation The number of software faults has exceeded the maximum allowed for the time period.
Recommended Action 1. Delete the node from the cluster. 2. Try to add the node back into the cluster.
3. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster with the
latest level of code. 4. If the error continues, ask IBM Product Support for assistance.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_NODERR_RESET_AND_REJECT )

Node data not found - node rejected from cluster [chars]
Explanation Node data was not found. The node has been rejected from the the from cluster.
Recommended Action Examine error logs to determine if another recorded error caused the loss of
the node data and, if so, follow the actions for that error. If no other error was recorded, the node
may have lost power without saving data or been reset. Attempt to determine the cause of the power
loss or reset. If no cause can be determined, then: 1. Re-install the code on the node. The node will
have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level
on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code.
3. If the error continues, ask IBM Product Support for assistance. It may be necessary to replace the
Caching Services Module.
Error Message SVC-3-SVC_SYSLOG_IF_INTERNAL_ERROR: Interface [chars] internal

error: [chars]
Explanation SVC interface internal error
Error Message SVC-3-SVC_SYSLOG_LC_INTERNAL_ERROR: Unable to send MTS to linecard

in slot [dec]: [chars]
Explanation Linecard MTS failure
OL-26589-01 2-487
Error Message SVC-3-SVC_SYSLOG_NPORT_INTERNAL_ERROR: [chars] N-port for Interface

[chars], vsan [dec] internal error: [chars]
Explanation N-port internal error
SVC-4
Error Message SVC-4-NODE_WARNING_MSG: [chars]
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec]

SS_EID_CA_EV_FIRST_DATA_PINNED ) Customer data pinned [chars]
Explanation There is now pinned customer data. This warning is given when data is pinned and there
wasntalreadypinneddata.Errorlogentrieswillexistfortheunderlyingcauseofthepinneddata.'
Recommended Action Perform problem determintation on the error log to determine the cause of the
pinned data and correct.

SS_EID_CA_EV_HWS_TO_SYNCHRONOUS ) Cache in write through mode due to pinned data
[chars]
Explanation The cache must now operate in write through mode because of the amount of pinned
data.
Recommended Action Perform problem determintation on the error log to determine the cause of the
pinned data and correct.

SS_EID_EC_ER_BATT_BELOW_CAPACITY ) Battery is below threshold capacity [chars]
Explanation Battery capacity is below threshold. The node will remain offline until the battery
charge is sufficient to come up.
Recommended Action Wait for the battery to recharge. This may take many hours. If after several
hours have passed and the node has not yet come up: 1. Reload the node. 2. If the error persists,
re-install the code on the line card. The node(s) will then have to be removed and re-added back to
the cluster. 3. If the error persists, replace the Caching Services Module.
2-488 OL-26589-01

SS_EID_EC_ER_CANNOT_OPEN_IO_PROCESS_Q ) Internal error - IO process queue [chars]
Explanation The process was unable to open the needed message queue. Node was rebooted due to
this error.

SS_EID_EC_ER_DEACTIVATE_CLUSTER_IP_FAILED ) Deactivate cluster IP failed [chars]
Explanation Unable to deactivate the cluster IP for the config node. The cluster IP should be
deactivated by other checks. If that is not the case it may not be possible to execute configuration
commands.
Recommended Action If there is a problem executing configuration commands: 1. Shutting the

interfaces of the node will force this node out of the cluster and should cause the switch to deactivate
the IP address associated with this node which should restore the ability to execute configuration
commands. 2. If the error persists, re-install the code on the node. The node will then have to be
removed and re-added back to the cluster. 3. Ensure that the software is at the latest level on the
cluster. If not, upgrade the cluster and if necessary repeat step 2 with the latest level of code. 4. If
the error continues, ask IBM Product Support for assistance.

SS_EID_EC_ER_DUMP_METADATA_FAILED ) Node assert dump failed [chars]
Explanation A failure occurred writting out a node assert dump. Other log entries may accompany
this error.
Recommended Action An initial error will have caused the node assert dump. Examine the log for
that error and follow the recommended actions for that error. In addition examine the log for errors
related to the internal disk drive. If found, follow the recommended actions. If no entries explain the
failure to write the dump: 1. Re-install the code on the node. The node will then have to be removed
and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If
not, upgrade the cluster with the latest level of code. 3. If the error continues, ask IBM Product
Support for assistance. It may be necessary to replace the Caching Services Module.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_EXECVE_FAILED

) Internal error - program launch [chars]
Explanation The process was unable to launch the IO program. Node was rebooted due to this error.
OL-26589-01 2-489
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_FORK_FAILED )

Internal error - fork failed [chars]
Explanation The process was unable to launch the IO program. Node was rebooted due to this error.

SS_EID_EC_ER_INTERNAL_EXIT_LOGIC_ERR ) Internal error - bad exit code [chars]
Explanation Node was warmstarted due to internal logic error.
Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Ask IBM
Product Support for assistance.

SS_EID_EC_ER_INTERNAL_UNKNOWN_EXEC_MODE ) Internal error - run mode [chars]
Explanation Node was rebooted due to internal logic error.

SS_EID_EC_ER_IOP_EXITED_DUE_TO_SIGNAL ) Internal error - signal caused exit
[chars]
Explanation The IO process exited because of a signal which was not caught. Node was warmstarted
due to this error.

SS_EID_EC_ER_IOP_STOPPED_DUE_TO_SIGNAL ) Internal error - signal caused stop
[chars]
Explanation The IO process stopped because of a signal received. Node was warmstarted due to this
error.
2-490 OL-26589-01

SS_EID_EC_ER_IOP_TERMINATED_ABNORMALLY ) Internal error - abnormal exit [chars]
Explanation The IO process exited abnormally. Node was warmstarted due to this error.

SS_EID_EC_ER_OPEN_MSG_QUEUE_FAILED ) Internal error - message queue [chars]
Explanation The process was unable to open the needed message queue. Node was rebooted due to
this error.

SS_EID_EC_ER_PTHREAD_CREATE_FAILED ) Internal error - threads [chars]
Explanation The process was unable to create the needed threads. Node was rebooted due to this
error.

SS_EID_EC_ER_UNKNOWN_MESSAGE_TYPE ) Internal error - message type [chars]
Explanation Node was rebooted due to internal logic error.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_WAITPID_FAILED

) Internal error - waitpid failed [chars]
Explanation The process was unable to launch the IO program properly. Node was warmstarted due
to this error.
Recommended Action If this error is repeated continously, 1. Reload the node. 2. If the error persists,
re-install the code on the node. The node will then have to be removed and re-added back to the
cluster. 3. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and
if necessary repeat step 2 with the latest level of code. 4. If the error continues, ask IBM Product
Support for assistance.
OL-26589-01 2-491

SS_EID_EC_ER_WARMSTART_MEMORY_FAILED ) Internal error - warmstart memory device
[chars]
Explanation The process was unable to warmstart the memory device. Node was rebooted due to
this error.

SS_EID_FC_ER_MAPPING_STOPPED ) FlashCopy has been stopped [chars]
Explanation A Flash Copy mapping task has been stopped because of an error. A stopped flash copy
may affect the status of other VDisks in the same I/O group. Preparing the stopped flash copies as
soon as possible is advised.
Recommended Action 1. Correct higher priority errors. Then, ask the customer to prepare and start
the Flash Copy task again. 2. Mark the error you have just repaired as fixed.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_FC_ER_PREPARE_FAILED

) FlashCopy prepare failed due to cache flush failure [chars]
Explanation A Flash Copy prepare task has failed because a cache flush has failed.
Recommended Action 1. Correct higher priority errors, then retry the prepare tasks. 2. Mark the error
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_FC_ER_STOP_COMPLETED

) Flash Copy Stopped [chars]
Explanation The Flash Copy mapping or consistency group has entered the STOPPED state as a
result of a user request to stop.

SS_EID_IC_ER_DIRECTORY_LIST_FAILED ) Failed to obtain directory listing from
remote node [chars]
Explanation An attempt to clean or retrieve files from /dumps directory has failed because of a
failure to get listing of the directory from the remote node.
Recommended Action Determine if the remote node is still online. If not, perform problem
determination on the remote node. If it is, retry the command. If it still fails contact the IBM Support
Center for assistance. Cisco CLI commands may be used to access the node directly as an
alternative.
2-492 OL-26589-01

SS_EID_IC_ER_FEATURISATION_VIOLATION ) Featurisation violation [chars]
Explanation The user has allocated more virtualized storage than licensed for or established a Flash
Copy mapping or Remote Copy relationship when these have not been licensed.
Recommended Action Look in the featurisation log for log entries of type
Error'todeterminethetypeofviolation.Theuserthenshouldtheneitherreducevirtualizedstorage,remove
theFlashCopymappingorRemoteCopyrelationship,soastobeincompliancewiththeirlicense;orupdatet
helicenseinformationifthatisincorrect;orarrangewiththeirIBMrepresentativetopurchasealicenseforth
edesiredfeatures.'

SS_EID_IC_ER_TRANSFER_FILE_FAILED ) Failed to transfer file from remote node
[chars]
Explanation An attempt to retrieve a file from /dumps directory has failed.
Recommended Action Determine if the remote node is still online. If not, perform problem
determination on the remote node. If it is, retry the command. If it still fails contact the IBM Support
Center for assistance. Cisco CLI commands may be used to access the node directly as an
alternative.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_IOGRP_NONE_OK

) Both nodes in the IO group are not available [chars]
Explanation Following node remove by the user, there are no nodes left in the IO group.

SS_EID_IC_EV_UPGRADE_NODE_PENDED ) Software upgrade process failed [chars]
Explanation A software upgrade has failed. This might be because of a hardware error or it might
be because of a failure in the new version of the software. An automatic software downgrade is
performed to restore the nodes to their previous software version. This will be indicated in the log
by a
Softwaredowngradecomplete'entry.Ifthedowngradeoperationfailstodowngradeanode,forexamplebe
causeitisoffline,thedownloadoperationwillstopandwaitfortheofflineSANVolumeControllertoberepa
iredordeletedfromthecluster.Whilethedowngradeoperationisinprogress,configurationcommandssen
ttotheclusterwillfailwithamessageindicatingthatasoftwareupgradeoperationisstillinprogress.Thedo
wngradeoperationmighttakeuptothreehours.'
Recommended Action 1. Display the status of the nodes on the cluster. 2. If any node is offline, delete
the offline node from the cluster. If the delete fails with a message indicating that a software upgrade
is in progress, this means that the downgrade process is still active. Wait for this operation to either
complete or stop on the offline node and then retry the delete. If the downgrade operation had
stopped, it will now continue. 3. Solve all logged hardware problems 4. Ask the user to retry the
software install. 5. If the installation fails again, report the problem to your software support center.
6. Mark the error you have just repaired as fixed.
OL-26589-01 2-493

SS_EID_IC_EV_UPGRADE_PCK_DELIVERY_FAILED ) Software install package cannot be
delivered to all nodes [chars]
Explanation An error occured while sending the software package to the nodes.
Recommended Action 1. Display the status of the nodes on the cluster. 2. If any node is offline,
perform problem determination on the node and bring the node back online. Or, alternatively, delete
the offline node from the cluster. 3. Retry the software retry the delete. If the downgrade operation
had stopped, it will now continue. 3. Solve upgrade command. 4. If the installation fails again, report
the problem to your software support center.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_PLIC_LINK )

Connection to a configured remote cluster has been lost [chars]
Explanation This cluster is no longer able to communicate with the remote copy partner cluster.
Recommended Action Perform problem determination on the network and the other cluster.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_LSYNC ) Remote

Copy suffered loss of synchronization [chars]
Explanation In a remote-copy operation, the relationship has stopped and lost synchronization, for
a reason other than a continuous I/O error.
Recommended Action 1. Correct higher priority errors, then restart the remote copy. 2. Mark the error
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_PERS ) Remote

Copy suffered persistent error [chars]
Explanation A Remote Copy relationship has been stopped because of a continuous I/O error.
Recommended Action 1. Correct the higher priority errors, then retry the Remote Copy task. 2. Mark
the error you have just repaired as fixed.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_TIMEOUT )

Remote Copy retry timeout [chars]
Explanation Remote Copy was unable to find a path to the device in the remote cluster within the
timeout period.
Recommended Action Perform problem determination on the network and remote cluster: Ensure that
all nodes in both clusters are configured in the inter-cluster SAN or VSAN. Ensure that all virtual
disks in the remote cluster are online.
2-494 OL-26589-01

SS_EID_VG_ER_COPIED_MEDIUM_ERROR ) I/O media error copied [chars]
Explanation During a copy or a migrate process a media error was copied to the destination disk.

SS_EID_VG_ER_INSUFFICIENT_VIRTUAL_EXTENTS ) Insufficient extents to create
Virtual Disk [chars]
Explanation There are not enough extents contained within the managed disk group to create the
required virtual disk. This error can be logged if a migration is started and then a virtual disk is
created which uses the extents that were to be used for the migration.
Recommended Action Add additional managed disks to the managed disk group or reduce the size of
virtual disk to be created.

SS_EID_VG_ER_MIGRATE_STOPPED ) Migration stopped [chars]
Explanation The specific migration has been stopped due to errors occurring during migration, these
errors have been logged.
Recommended Action Analyze the error log. Perform problem determination and correct any errors
which have occurred. Migrate any specific extents which were not migrated due to the errors.

SS_EID_VG_ER_MIGRATE_SUSPENDED ) Migration suspended [chars]
Explanation Migration suspended.
Recommended Action 1. Ensure that all error codes of a higher priority have already been fixed. 2.
Ask the customer to ensure that all mdisk groups that are the destination of suspended migrate
operations have free extents available. 3. Mark this error as fixed. This will cause the migrate
operation to be restarted. If the restart fails a new error will be logged.

SS_EID_VL_ER_IO_MEDIUM_ERROR ) A media error has occurred during I/O to a Managed
Disk [chars]
Explanation A disk I/O medium error has occurred.
Recommended Action 1. Ask the customer to rewrite the bad data to the block LBA reported in the
host systems SCSI sense data. Note: If this error has occurred during a migration, the host system
will notice the error until the target device is accessed. 2. Check managed disk status. If all managed
disks show a status of online, mark the error you have just repaired as fixed.
OL-26589-01 2-495

SS_EID_VL_ER_IO_THRESHOLD_WARNING ) Managed Disk error count warning threshold met
[chars]
Explanation IOs to the managed disk have experienced sufficient errors to generate this warning. If
the managed disk continues to experience IO errors, the managed disk may be excluded.
Recommended Action Perform problem determination on the affected managed disk.

SS_EID_VL_ER_LUN_DISCOVERY_FAILED ) Discovery of LUN failed [chars]
Explanation The cluster has a connection to the device on the SAN through this node, but the device
has not responded to the node in a manner consistent with a functional device LUN.
Recommended Action If there are device LUNs that should have been discovered by the node: 1)
Perform a manual discovery. 2) Perform problem determination on the device.

SS_EID_VL_ER_MDISK_PORT_PREFERENCE_IGNORED ) Preferred port is not being used for
Managed Disk access [chars]
Explanation The preferred port designated by the back end controller is not being used for Managed
Disk access. A port error or excluded port has prevented the use of the preferred port.
Recommended Action Perform problem determination on the controller and network to determine the
cause of the port error or exclusion.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_NODERR_CR_FAILED )

Cluster recovery failed [chars]
Explanation Cluster recovery has failed and a software dump has been created.
Recommended Action Contact IBM Product support for assistance.
Error Message SVC-4-SVC_SYSLOG_IF_INTERNAL_WARN: Interface [chars] internal

warning: [chars]
Explanation SVC interface internal warning
Error Message SVC-4-SVC_SYSLOG_NPORT_INTERNAL_WARN: [chars] N-port for Interface

[chars], vsan [dec] internal warning: [chars]
Explanation SVC interface internal warning
2-496 OL-26589-01
SVC-5
Error Message SVC-5-NODE_NOTICE_MSG: [chars]
Error Message SVC-5-SVC_SYSLOG_IF_CONFIG_DELETED: Interface [chars] configuration

was deleted[chars]
Explanation SVC interface configuration was deleted
Error Message SVC-5-SVC_SYSLOG_IF_DOWN: Interface [chars] is down
Explanation SVC interface is down
Error Message SVC-5-SVC_SYSLOG_IF_UP: Interface [chars] is up
Explanation SVC interface is up
SVC-6
Error Message SVC-6-NODE_INFO_MSG: [chars]
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_CA_EV_ALL_DATA_UNPINNED

) All data now unpinned [chars]
Explanation All the customer data in the IO group is now unpinned.
OL-26589-01 2-497
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec]

SS_EID_CA_EV_HWS_TO_ASYNCHRONOUS ) Pinned data reduced; cache can operate normally
[chars]
Explanation Enough customer data has been unpinned that the cache is no longer required to operate
in write through mode because of the pinned data. (Note that the cache may still operate in write
through mode for other reasons.)
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_BATT_OK ) Battery

recharged [chars]
Explanation Battery capacity has been restored to above threshold. The node will now come online.
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_BATT_POWER_DOWN

) Poweroff or power failure detected [chars]
Explanation The process has received a poweroff or power failure indication. The node is shutting
down.
Recommended Action Restore power. If power was not removed and this occurs: 1. Reload the node.
2. If the error persists, re-install the code on the line card. The node(s) will then have to be removed
and re-added back to the cluster. 3. If the error persists, replace the Caching Services Module.
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_PWR_BUTTON )

Power withdrawn [chars]
Explanation Node software was notified that AC power was being shut off or the Caching Services
Module was being reset.
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_FC_ER_COPY_COMPLETED )

Flash Copy Copied [chars]
Explanation The Flash Copy mapping or consistency group has entered the IDLE_COPIED state.
The target disk now contains a complete copy and is no longer dependent on the source.
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_FC_ER_PREPARE_COMPLETED

) Flash Copy Prepared [chars]
Explanation The Flash Copy mapping or consistency group has entered the PREPARED state. It is
now possible to Start or Stop the mapping/group.
2-498 OL-26589-01

SS_EID_IC_EV_CLUSTER_RECOVERY_COMPLETE ) Cluster recovery completed [chars]
Explanation Cluster recovery has completed successfully.
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_IOGRP_ONE_OK )

One node in the IO group is not available [chars]
Explanation Following node remove by the user, there is only one node left in the IO group.

SS_EID_IC_EV_SECURE_DELETE_COMPLETE ) Virtual Disk format completed [chars]
Explanation The formatting (writing all zeros) to new extents of the Virtual Disk has completed.
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_COLDSTART ) Node

software started [chars]
Explanation The node software has been started (cold start).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_COPY_COMP )

Remote Copy complete [chars]
Explanation Background copy complete. The standalone relationship or consistency group has
transitioned from
InconsistentCopying'to'ConsistentSynchronized'.ThiswillonlybeloggedontheclusterofthePrimaryVi
trualDisk(s).'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_RC_ER_READY_TO_START )

Remote Copy ready to start [chars]
Explanation The remote copy relationship or consistency group, whic had been previously been
stopped due to an error, is ready to be restarted. All resources are now online.
Recommended Action Restart the relationship or consistency group.
OL-26589-01 2-499
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_VG_EV_MIGRATE_COMPLETE

) Migration complete [chars]
Explanation Migration has completed.

SS_EID_VL_ER_CLUSTER_FABRIC_VIEW_CHANGE ) Cluster fabric view has been updated.
[chars]
Explanation The node is in the process of discoverying devices on the fabric.
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ADD_MAPPING )

Virtual Disk to Host SCSI mapping created [chars]
Explanation svctaskmkvdiskhostmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ADD_WWPN ) Port

added to a Host [chars]
Explanation svctaskaddhostport'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CHANGE_CLUSTER_TIME

) Attempt to change cluster time (no effect) [chars]
Explanation
svctasksetclustertime'commandhasbeeninvoked.ThiscommandhasnoeffectinSANVolumeController
forCiscoMDS9000,butisretainedforcompatibility.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CHANGE_TIMEZONE )

Attempt to change time zone (no effect) [chars]
Explanation
svctasksettimezone'commandhasbeeninvoked.ThiscommandhasnoeffectinSANVolumeControllerfo
rCiscoMDS9000,butisretainedforcompatibility.'
2-500 OL-26589-01
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_DISCOVERY

) Manual Managed Disk discovery invoked [chars]
Explanation svctaskdetectmdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_DUMP_CONFIG

) Cluster config dumped to file [chars]
Explanation svctaskdumpconfig'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_MODIFY )

Cluster attributes modified [chars]
Explanation svctaskchcluster'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_SHUTDOWN )

Node or Cluster shutdown [chars]
Explanation svctaskstopcluster'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CREATE_FC_MAPPING

) Flash Copy mapping created [chars]
Explanation svctaskmkfcmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CREATE_HOST ) Host

created [chars]
Explanation svctaskmkhost'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_FC_MAPPING

) Flash Copy mapping deleted [chars]
Explanation svctaskrmfcmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
OL-26589-01 2-501
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_HOST ) Hosts

deleted [chars]
Explanation svctaskrmhost'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_MAPPING )

Virtual Disk to Host SCSI mapping deleted [chars]
Explanation svctaskrmvdiskhostmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'

SS_ERR_CFG_DELETE_PORT_HOST_LIST ) Ports deleted from a Host [chars]
Explanation svctaskrmhostport'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_WWPN ) Port

deleted from a Host [chars]
Explanation svctaskrmhostport'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DEVICE_SET_NAME )

Controller attributes modified [chars]
Explanation svctaskchcontroller'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_ANALYSE )

Error log analyzed [chars]
Explanation svctaskfinderr'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_CLEARLOG

) Error log cleared [chars]
Explanation svctaskclearerrlog'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
2-502 OL-26589-01
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_DUMPLOG )

Error log dumped [chars]
Explanation svctaskdumperrlog'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_FIX )

Error log entry marked fixed [chars]
Explanation svctaskcherrstate'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'

SS_ERR_CFG_FC_CONSIST_GRP_SET_NAME ) Flash Copy consistency group name modified
[chars]
Explanation svctaskchfcconsistgrp-name'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'

SS_ERR_CFG_FC_CREATE_CONSIST_GRP ) Flash Copy consistency group created [chars]
Explanation svctaskmkfcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'

SS_ERR_CFG_FC_DELETE_CONSIST_GRP ) Flash Copy consistency group deleted [chars]
Explanation svctaskrmconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FC_SET_NAME ) Flash

Copy mapping name modified [chars]
Explanation svctaskchfcmap-name'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'

SS_ERR_CFG_FEATURISATION_CHANGED ) Licensed settings modified [chars]
Explanation svctaskchlicense'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
OL-26589-01 2-503
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FLASH_PREPARE_CG )

Flash Copy consistency group prepared [chars]
Explanation svctaskprestartfcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FLASH_START_CG )

Flash Copy consistency group started [chars]
Explanation svctaskstartfcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FLASH_STOP_CG )

Flash Copy consistency group stopped [chars]
Explanation svctaskstopfcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_HOST_DELETE ) Host

deleted [chars]
Explanation svctaskrmhost'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_HOST_SET_NAME )

Host attributes modified [chars]
Explanation svctaskchhost'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_HWS_SET_NAME ) IO

Group name modified [chars]
Explanation svctaskchiogrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_IO_TRACE_FINISHED

) IO Tracing stopped [chars]
Explanation
svctaskstoptrace'orequivalentGUI/CiscoCLIcommandhasbeeninvoked,orthetriggeroccurredforagiv
enManagedDisk,automaticallystoppingthetrace.'
Recommended Action Analyse the traces.
2-504 OL-26589-01
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_ADD_MDISK

) Managed Disk added to Managed Disk group [chars]
Explanation svctaskaddmdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_CREATE )

Managed Disk Group created [chars]
Explanation svctaskmkmdiskgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_DELETE )

Managed Disk Group deleted [chars]
Explanation svctaskrmmdiskgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'

SS_ERR_CFG_MDISK_GRP_DELETE_MDISK ) Managed Disk deleted from Managed Disk group
[chars]
Explanation svctaskrmmdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_SET_NAME

) Managed Disk Group attributes modified [chars]
Explanation svctaskchmdiskgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_SET_NAME )

Managed Disk attributes modified [chars]
Explanation svctaskchmdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_UNSLANDER )

Managed Disk online [chars]
Explanation The managed disk which was excluded is now online.
OL-26589-01 2-505
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MIGRATE ) Virtual

Disk migration to new Managed Disk group started [chars]
Explanation svctaskmigratevdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MODIFY_FC_MAPPING

) Flash Copy mapping modified [chars]
Explanation svctaskchfcmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_ADD ) Node

added [chars]
Explanation svctaskaddnode'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_CREATE_CLUSTER

) Cluster created [chars]
Explanation clusteradd'orequivalentGUIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_DELETE ) Node

deleted from cluster [chars]
Explanation svctaskrmnode'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_PEND ) Node

Pend [chars]
Explanation The node has gone into the pending state. It will shortly go into the online or offline
state.
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_REMOVE ) Node

leaving cluster (expected) [chars]
Explanation The node has gone offline as expected due to shutdown, upgrade or deletion.
2-506 OL-26589-01
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_SET_NAME )

Node attributes modified [chars]
Explanation svctaskchnode'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_SHUTDOWN )

Node shutdown [chars]
Explanation svctaskstopcluster-node'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_UNPEND ) Node

Unpend [chars]
Explanation The node has gone online.
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_PLANAR_SN_CHANGE )

Attempt to change the Planar Serial Number (no effect) [chars]
Explanation
svctaskwritesernum'commandhasbeeninvoked.ThiscommandhasnoeffectinSANVolumeControllerf
orCiscoMDS9000,butisretainedforcompatibility.'

SS_ERR_CFG_PRETRIGGER_FC_MAPPING ) Flash Copy mapping prepared [chars]
Explanation svctaskprestartfcmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_QUORUM_CREATE )

Quorum disk set [chars]
Explanation svctasksetquorum'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'

SS_ERR_CFG_REMOTE_CREATECONSTGRP ) Remote Copy consistency group created [chars]
Explanation svctaskmkrcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
OL-26589-01 2-507
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_CREATEREL )

Remote Copy relationship created [chars]
Explanation svctaskmkrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'

SS_ERR_CFG_REMOTE_DELETECONSTGRP ) Remote Copy consistency group deleted [chars]
Explanation svctaskrmconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_DELETEREL )

Remote Copy relationship deleted [chars]
Explanation svctaskrmrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'

SS_ERR_CFG_REMOTE_MODIFYCONSTGRP ) Remote Copy consistency group modified [chars]
Explanation svctaskchrcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_MODIFYREL )

Remote Copy relationship modified [chars]
Explanation svctaskchrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_START )

Remote Copy relationship started [chars]
Explanation svctaskstartrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_START_CG )

Remote Copy consistency group started [chars]
Explanation svctaskstartrcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
2-508 OL-26589-01
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_STOP )

Remote Copy relationship stopped [chars]
Explanation svctaskstoprcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_STOP_CG )

Remote Copy consistency group stopped [chars]
Explanation svctaskstoprcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_SWITCH )

Remote Copy relationship switched [chars]
Explanation svctaskswitchrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_SWITCH_CG )

Remote Copy consistency group switched [chars]
Explanation svctaskswitchrcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'

SS_ERR_CFG_SERVICE_APPLY_SOFTWARE ) Software upgrade command accepted [chars]
Explanation
clusterupgradesvc-system'orequivalentGUIcommandhasbeeninvoked.Thecommandhasbeenaccepte
d.Additionallogentrieswilltracktheprogressoftheupgrade.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_STOP_FC_MAPPING )

Flash Copy mapping stopped [chars]
Explanation svctaskstopfcmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_TRIGGER_FC_MAPPING

) Flash Copy mapping started [chars]
Explanation svctaskstartfcmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
OL-26589-01 2-509
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_UPGRADE_BACKED_OFF

) Software downgrade complete [chars]
Explanation The software upgrade process failed and all nodes have been restored to the previous
level of code.
Recommended Action Perform problem determination on the cause of the upgrade failure and take
corrective action before retrying the upgrade.
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_UPGRADE_COMPLETED

) Software upgrade complete [chars]
Explanation All nodes have successfully moved to the new code level, which will now be
committed.
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_UPGRADE_STARTED )

Software upgrade started [chars]
Explanation The software upgrade process has started (the first node is about to be upgraded).
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_CREATE )

Virtual Disk created [chars]
Explanation svctaskmkvdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_DELETE )

Virtual Disk deleted [chars]
Explanation svctaskrmvdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_EXPAND )

Virtual Disk expanded [chars]
Explanation svctaskexpandvdisksize'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
2-510 OL-26589-01

SS_ERR_CFG_VDISK_EXPAND_SINGLE_EXT ) Virtual Disk expanded by single extent
[chars]
Explanation svctaskaddvdiskext'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'

SS_ERR_CFG_VDISK_MIGRATE_EXTENT ) Extent migration started [chars]
Explanation svctaskmigrateexts'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'

SS_ERR_CFG_VDISK_MIGRATE_EXTENTS ) Extent migration started [chars]
Explanation svctaskmigrateexts'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_MODIFY_GOVERN

) Virtual Disk throttling rate modified [chars]
Explanation svctaskchvdisk-rate'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_MOVE_HWS )

Virtual Disk IO Group changed [chars]
Explanation svctaskchvdisk-iogrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_SET_NAME )

Virtual Disk name modified [chars]
Explanation svctaskchvdisk-name'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_SHRINK )

Virtual Disk shrunk [chars]
Explanation svctaskshrinkvdisksize'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'
OL-26589-01 2-511
Error Message SVC-6-SVC_SYSLOG_CL_CONFIG: Node [chars] has become config node of

cluster [chars]
Explanation SVC interface has because cluster config node
Error Message SVC-6-SVC_SYSLOG_CL_JOIN: Node [chars] has joined cluster [chars]
Explanation SVC interface has joined cluster
Error Message SVC-6-SVC_SYSLOG_CL_UNJOIN: Node [chars] has left cluster [chars]
Explanation SVC interface has left cluster
Error Message SVC-6-SVC_SYSLOG_LC_WWN_PURGE: All WWNs for module [dec] have been
purged[chars]
Explanation SVC linecard has purged all WWNs
Error Message SVC-6-SVC_SYSLOG_VSAN_INACTIVE: Vsan [dec] suspended
Explanation Vsan was suspended; can cause warnings
SVC-7
Error Message SVC-7-NODE_DEBUG_MSG: [chars]
SYSMGR Messages
This section contains the SYSMGR messages.
2-512 OL-26589-01
SYSMGR-2
Error Message SYSMGR-2-ACTIVE_LOWER_MEM_THAN_STANDBY: Active supervisor in slot

[dec] is running with less memory than standby supervisor in slot [dec].
Explanation Supervisor memory mismatch
Error Message SYSMGR-2-BOOTSCOPE_HANDSHAKE: Service [chars] is in the boot scope,

but tried a regular handshake. Discarding request.
Explanation A service is trying to take actions that belong to a different class of services.
Error Message SYSMGR-2-CFGERASE_ABORTED: Write erase aborted.
Explanation Write erase has failed.
Recommended Action Please verify the other syslog messages printed correct the problem, and try
again.
Error Message SYSMGR-2-CFGSNAPSHOT_ABORTED_DIR: Unable to open the configuration

directory. Aborting configuration snapshot.
Explanation The destination location for the snapshot-config could not be found.
Recommended Action If the problem persists, please use the vshboot command
initsystem'toinitializetheconfigurationpartition.'
Error Message SYSMGR-2-CFGSNAPSHOT_ABORTED_INIT: Unable to initialize the

configuration directory (error-id [hex]). Aborting configuration snapshot.
Explanation An attempt to copy the startup-config to snapshot-config has failed because the old data
could not be removed.
Error Message SYSMGR-2-CFGSNAPSHOT_ABORTED: Configuration snapshot aborted.
Explanation An attempt to save a snapshot of the startup-config has failed.
again.
OL-26589-01 2-513
Error Message SYSMGR-2-CFGSYNC_FAILURE: Syncing of the configuration to the standby

failed.
Explanation Syncing of the configuration to the standby failed.
again.
Error Message SYSMGR-2-CFGWRITE_ABORTED_DIR: Unable to open the configuration

directory. Aborting configuration copy.
Explanation The destination location for the startup-config could not be found.
Error Message SYSMGR-2-CFGWRITE_ABORTED_INIT: Unable to initialize the

configuration directory (error-id [hex]). Aborting configuration copy.
Explanation An attempt to copy the running-config to startup-config has failed because the old data
could not be removed.
Error Message SYSMGR-2-CFGWRITE_ABORTED_LABEL: Unable to label the new

configuration (error-id [hex]). Aborting configuration copy.
Explanation An attempt to copy the running-config to startup-config has failed because the new
startup-config could not be stamped.
Error Message SYSMGR-2-CFGWRITE_ABORTED_LOCK: Unable to lock the configuration

(error-id [hex]). Aborting configuration copy.
Explanation An attempt to copy the running-config to startup-config has failed because the system
could not lock the required configuration items.
Error Message SYSMGR-2-CFGWRITE_ABORTED_LOG: Unable to open a log file for the new
configuration: [chars] (error-id [hex]). Aborting configuration copy.
Explanation An attempt to copy the running-config to startup-config has failed because a log file
could not be created.
2-514 OL-26589-01
Error Message SYSMGR-2-CFGWRITE_ABORTED: Configuration copy aborted.
Explanation A configuration copy has failed.
again.
Error Message SYSMGR-2-CFGWRITE_TIMEOUT_ABORT: Configuration copy aborted by

timeout.
Explanation A service failed to store its configuration in the timeout period. The operation has been
aborted.
Error Message SYSMGR-2-CFGWRITE_USER_ABORT: Configuration copy aborted by the

user.
Explanation The user typed CTRL+C while the configuration was being saved, and the operation
has been aborted.
Error Message SYSMGR-2-CONVERT_FUNC_FAILED: Conversion function failed for service

"[chars]" (error-id [hex]).
Explanation This message indicates that the conversion function failed for this service.
Error Message SYSMGR-2-CONVERT_FUNC_NOTFOUND: Conversion function not found for

service "[chars]".
Explanation This message indicates that the system could not find appropriate conversion function
for this service.
Error Message SYSMGR-2-CONVERT_LIB_NOTFOUND: Conversion library not found for

service "[chars]".
Explanation This message indicates that the system could not find conversion library for this
service.
OL-26589-01 2-515
Error Message SYSMGR-2-CONVERT_STARTUP_ABORTED: Conversion of startup-config

failed.
Explanation This message indicates that the conversion of startup configuration was aborted.
Error Message SYSMGR-2-CONVERT_ZIPPING_FAILED: Failed to zip the converted startup

configuration.
Explanation This message indicates that conversion of the startup configuration failed when system
was trying to zip the converted configuration.
Error Message SYSMGR-2-CORE_SAVE_FAILED: [chars]: PID [dec] with message [chars].
Explanation
Error Message SYSMGR-2-CREATE_DONEFILE_FAILED: Creating /var/run/sysmgr.initdone

failed with return value: ([dec]).
Explanation The initialization of the system could not complete.
Error Message SYSMGR-2-DELETE_BINARY_STARTUP_FAILED: Deletion of binary startup

config failed during boot (error-id [hex]).
Explanation This message indicates that the deletion of the binary startup configuration failed
during boot.
Error Message SYSMGR-2-FEATURE_SET_NOT_DISABLED_SRVS: vdc [dec]: feature-set

0x%llx: Following services did not cleanup: [chars]
Explanation
2-516 OL-26589-01
Error Message SYSMGR-2-FEATURE_SET_SRVTIMEOUT: vdc [dec]: feature-set 0x%llx

[chars]: Following services did not respond in time: [chars]
Explanation The services did not handshake with sysmgr in time
Error Message SYSMGR-2-FEATURE_SET_UNGRACEFUL_DISABLE_FAILED_SRVS: vdc [dec]:

feature-set 0x%llx: Following services did not exit even after SIGKILL: [chars]
Explanation
Error Message SYSMGR-2-FORMAT_FAILURE_SUP_RESET: Failure to format a partition

successfully causing sup to reset.
Explanation The partition used to store non-volatile pss files could not be formatted successfully.
The supervisor will be reset.
Recommended Action If the problem persists, please contact customer support.
Error Message SYSMGR-2-GSYNC_ABORT: Global sync aborted by signal.
Explanation The initial synchronization of the services has been aborted. The synchronization will
be attempted again later.
Recommended Action Use the command reloadmodule<mod
Error Message SYSMGR-2-GSYNC_GET_TIMEOUT: Request for global sync for UUID [hex]
not completed in specified time.
Explanation Service failed to complete global sync in specified time. The standby will no longer act
as a HA standby.
Error Message SYSMGR-2-GSYNC_READY_SRVFAILED: Service "[chars]" on standby

supervisor failed to restore its snapshot (error-id [hex]).
Explanation The initial synchronization of service [chars] has failed.
OL-26589-01 2-517
Error Message SYSMGR-2-GSYNC_SNAPSHOT_SRVFAILED: Service "[chars]" on active

supervisor failed to store its snapshot (error-id [hex]).
Explanation The initial synchronization of service [chars] has failed.
Error Message SYSMGR-2-HANDSHAKE_FAILED: Handshake with service "[chars]" in vdc

[dec] failed since send failed: [chars] (error-id [hex]).
Explanation Handshake with a service failed since system manager could not send handshake
response to it.
Error Message SYSMGR-2-HASWITCHOVER_PRE_START: This supervisor is becoming active

(pre-start phase).
Explanation A cold switchover has started (pre-start phase).
Recommended Action When the other supervisor is back online, use the command
showsystemreset-reason'toknowwhatcausedtheswitchover.'
Error Message SYSMGR-2-HASWITCHOVER_START: Supervisor [dec] is becoming active.
Explanation A cold switchover has started.
Error Message SYSMGR-2-HEARTBEAT_FAILED: Sysmgr heartbeat failed at %lu. [chars].

[chars] ([dec])
Explanation System manager had failure while trying to heartbeat with KLM
Error Message SYSMGR-2-INBAND_START_FAILED: Failure while bringing up inband after

ISSU reboot, errno: [dec].
Explanation Sysmgr tried to bring up inband after ISSU reboot, but the call returned error.
2-518 OL-26589-01
Error Message SYSMGR-2-INVALID_HANDSHAKE: Invalid secret ([dec]) received from

service [chars]. Expected [dec].
Explanation A service cantbestarted.'
Error Message SYSMGR-2-INVALID_SYSMGRCONF: [chars]: invalid configuration file

"[chars]": [chars] (error-id [hex]).
Explanation The system image contains an inconsistent list of services. The initialization of the
system cantproceedfurther.'
Error Message SYSMGR-2-INVALID_VERSIONMSG: The remote System Manager ([chars])

declares itself in the same state as this System Manager ([chars]).
Explanation The redundancy state negotiation between the two supervisors failed.
Error Message SYSMGR-2-ISSU_FAILED: The ISSU has failed: [chars] (error-id [hex])
Explanation The ISSU has failed and the switch need to be rebooted.
Error Message SYSMGR-2-LAST_CORE_BASIC_TRACE: [chars]: PID [dec] with message

[chars].
Explanation
Error Message SYSMGR-2-MSG_SEND_FAILURE_STANDBY_RESET: Failure in sending message

to standby causing standby to reset.
Explanation We will be resetting the standby since mts on the active is unable to send a message to
standby.
OL-26589-01 2-519
Error Message SYSMGR-2-MTS_FLUSH_SYNC_QUEUE_FAILURE: flush mts sync queue failed

with [chars] (errno [dec])
Explanation Calling mts_flush_sync_queue to guarante no outstanding messages. the failure might

affect HA
Error Message SYSMGR-2-NON_VOLATILE_DB_FULL: System non-volatile storage usage is

unexpectedly high at [dec]%.
Explanation System non-volatile storage space is almost full.
Recommended Action Please run the command clearprocesseslogpid<pid
Error Message SYSMGR-2-NON_VOLATILE_DB_INODE_FULL: System non-volatile inode

storage usage is unexpectedly high at [dec]%.
Explanation System non-volatile inode storage space is almost full.
Recommended Action Please run the command clearprocesseslogpid<pid
Error Message SYSMGR-2-ONBOARD_FAILURE_LOGGING_FULL: Onboard failure logging usage

is unexpectedly high at [dec]%.
Explanation Onboard failure logging space is almost full.
Recommended Action Please run the command

clearloggingonboard'.Ifthismessagecontinuestopersist,pleasecontactTAC.'
Error Message SYSMGR-2-PARSEERR_DEPENDCYCLE: Dependency cycle found among [chars].
Error Message SYSMGR-2-PARSEERR_DUPLICATEDCONFIG: [chars]: duplicated definition

for service config. Previous definition in [chars].
2-520 OL-26589-01
Error Message SYSMGR-2-PARSEERR_DUPLICATEDDEPEND: [chars]: duplicated dependency

from [chars] for service [chars]. Previous use in [chars].
Error Message SYSMGR-2-PARSEERR_DUPLICATEDNAME: [chars]: short name [chars] used

by service [chars] is also used by service "[chars]" in [chars].
Error Message SYSMGR-2-PARSEERR_DUPLICATEDOPTION: [chars]: duplicated definition

for option [chars]-
Error Message SYSMGR-2-PARSEERR_DUPLICATEDSERVICE: [chars]: duplicated definition

for service [chars]. Previous definition in [chars].
Error Message SYSMGR-2-PARSEERR_DUPLICATEDVERDB: [chars]: duplicated definition

for service version_db. Previous definition in [chars].
OL-26589-01 2-521
Error Message SYSMGR-2-PARSEERR_DUP_UGRPENTRY: [chars]: service [chars] duplicated

in the current upgrade group. Previous use in [chars].
Error Message SYSMGR-2-PARSEERR_FT_SET_ID_PARSEERR: [chars]: ft_set_id ([dec]) out

of bound for "[chars]".
Error Message SYSMGR-2-PARSEERR_INCONSISTENTOPT: [chars]: option "[chars]=[chars]"

not consistent with "[chars]=[chars]" for service "[chars]"
Error Message SYSMGR-2-PARSEERR_INVALIDCOMPCONDDEPEND: [chars] (in dependency list

of compulsory conditional service [chars]): optional conditional service "[chars]"
not allowed.
Error Message SYSMGR-2-PARSEERR_INVALIDCONDDEPEND: [chars] (in dependency list of

ASAP service [chars]): conditional service "[chars]" not allowed.
2-522 OL-26589-01
Error Message SYSMGR-2-PARSEERR_INVALIDDEPEND: [chars] (in dependency list of

service [chars]): service [chars] not defined for scope "[chars]".
Error Message SYSMGR-2-PARSEERR_INVALIDEXEC: [chars]: invalid executable [chars]

for service [chars]: [chars] ([dec]).
Error Message SYSMGR-2-PARSEERR_INVALIDHANDSHAKEDEPEND: [chars] (in handshake

dependency list of service [chars]): service "[chars]" is MTS unaware or not
defined for scope "[chars]".
Error Message SYSMGR-2-PARSEERR_INVALIDIDENT: [chars]: [chars] "[chars]" not found

for service "[chars]".
Error Message SYSMGR-2-PARSEERR_INVALIDOPTION: [chars]: option [chars]-
OL-26589-01 2-523
Error Message SYSMGR-2-PARSEERR_INVALIDSTDBYDEPEND: [chars]: service [chars]

cannot be dependent on service [chars] due to the standby mode wait for that
service.
Error Message SYSMGR-2-PARSEERR_INVALIDVDCDEPEND: [chars] (in dependency list of

service [chars]): service [chars] is a [chars] service.
Error Message SYSMGR-2-PARSEERR_INVALID_CLEANUP_ARGUMENTS: [chars]:

cleanup_arguments = "[chars]": only conditional services that are scripts can
specify cleanup arguments
Error Message SYSMGR-2-PARSEERR_INVALID_COND_SRV_MODE: [chars]: service [chars]

not defined for scope "control" or not mts aware.
Error Message SYSMGR-2-PARSEERR_INVALID_DIR: [chars]: "[chars]" is not a valid

[chars]: [chars] ([dec]).
2-524 OL-26589-01
Error Message SYSMGR-2-PARSEERR_INVALID_GLOBAL_SYNC: [chars]: mts unaware service

may not request for a global sync.
Error Message SYSMGR-2-PARSEERR_INVALID_HB: [chars]: "[dec]" is not a valid

heartbeat timeout.
Error Message SYSMGR-2-PARSEERR_INVALID_MAX_INSTANCE: [chars]: [dec] is not a

valid max_instance.
Error Message SYSMGR-2-PARSEERR_INVALID_SHELLTREE: [chars]: invalid shell parser

tree [chars] for service [chars]: [chars] ([dec]).
Error Message SYSMGR-2-PARSEERR_INVALID_STANDBY_MODE_GLOBAL_SYNC: [chars]:

service with standby mode wait cannot request for a global sync.
OL-26589-01 2-525
Error Message SYSMGR-2-PARSEERR_INVALID_STANDBY_MODE: [chars]: standby_mode should

be run.
Error Message SYSMGR-2-PARSEERR_INVALID_STARTUP_MODE_DEPENDENCY: [chars]: Invalid

dependency. Service
[chars]sstartupmode('[chars]')doesnotmatchdependentservice"[chars]"'sstartupmode
('[chars]').'
Error Message SYSMGR-2-PARSEERR_INVALID_TRANSL: [chars]: invalid translator

[chars] for service [chars]: [chars] ([dec]).
Error Message SYSMGR-2-PARSEERR_INVALID_UGRPENTRY: [chars]: service "[chars]" is

not defined.
Error Message SYSMGR-2-PARSEERR_MISSINGOPTION: [chars]: option [chars]-
2-526 OL-26589-01
Error Message SYSMGR-2-PARSEERR_MTSUNAWARE_HANDSHAKEDEPEND: [chars]: service

[chars] is MTS unaware and cannot have handshake dependencies.
Error Message SYSMGR-2-PARSEERR_NORESTART: [chars]: option [chars]-
Error Message SYSMGR-2-PARSEERR_NOTCONFIG: [chars]: [chars] implemented only for

service config.
Error Message SYSMGR-2-PARSEERR_REPARSE_CANNOT_ADD_SRV: Service "[chars]" cannot

be added
Error Message SYSMGR-2-PARSEERR_REPARSE_CANNOT_DELETE_SRV: Service "[chars]"

cannot be removed
OL-26589-01 2-527
Error Message SYSMGR-2-PARSEERR_REPARSE_CANNOT_MODIFY_PARAM: Cannot modify

parameter [chars] for the service "[chars]", old value = [chars], new value =
[chars]
Error Message SYSMGR-2-PARSEERR_REPARSE_CANNOT_MODIFY_SRV: Configuration for

service "[chars]" cannot be modified, param modified = [chars], old_value =
[chars], new_value = [chars]
Error Message SYSMGR-2-PARSEERR_REP_UGRPENTRY: [chars]: service [chars] is used in

more than one upgrade group. First use in [chars].
Error Message SYSMGR-2-PARSEERR_TOOMANYDEPENDS_MULTIPLE_INST: [chars]: too many

multiple instance dependencies ([dec]) for service "[chars]".
Error Message SYSMGR-2-PARSEERR_TOOMANYDEPENDS: [chars]: too many dependencies

([dec]) for service "[chars]".
2-528 OL-26589-01
Error Message SYSMGR-2-PARSEERR_UGRPDUPLICATEDNAME: [chars]: upgrade group name

"[chars]" already used in [chars].
Error Message SYSMGR-2-PARSEERR_UGRPNAMEREDEFINED: [chars]: the upgrade group is

already called "[chars]".
Error Message SYSMGR-2-PARTIAL_CFGWRITE_ABORTED: Partial configuration copy

aborted.
Explanation A partial configuration copy has failed.
again. If problem persists, please run the command copyrunning-configstartup-config'andtryagain.'
Error Message SYSMGR-2-PLUGIN_BOOTUP_FAILURE: The bootup of the supervisor has

failed due to plugin load: [chars] (error-id [hex])
Explanation The bootup of the supervisor has failed due to plugin load.
Error Message SYSMGR-2-PSS2FILE_CONVERT_FAILED: Conversion of file [chars] failed.
Explanation Conversion of internal data format failed.
Error Message SYSMGR-2-PSS2_VOLATILE_DB_FULL: Volatile database usage in kernel is

Explanation System volatile database in kernel space is almost full.

systemsysteminternalpsskernelmemstats'.Ifthismessagecontinuestopersist,pleasecontactTAC.'
OL-26589-01 2-529
Error Message SYSMGR-2-REDSTATE_GETFAILED: Failed to request redundancy state:

[chars] (error-id [hex]).
Explanation The local supervisor is unable to get the redundancy state.
Error Message SYSMGR-2-REDSTATE_SETFAILED: Failed to set redundancy state: ret_val

([dec]).
Explanation The local supervisor is unable to get the redundancy state.
Error Message SYSMGR-2-REDUNDANCY_CHANNEL_FAILURE: Remote sup will be rebooted

since its coming up as active when local sup is still active.
Explanation Remote sup is becoming active although local sup is still active. As a result, local sup
will cause the remote sup to reset itself.
Error Message SYSMGR-2-REDUNDANCY_HEARTBEAT_FAILURE: Heartbeat between active and

standby on the redundancy channel not working for last [dec] minutes.
Explanation This supervisor is not receiving heartbeat on the redundancy channel from the other
supervisor. This can result in problems during switchover and switchover may even fail.
Error Message SYSMGR-2-RESTART_SYSTEM_LOG: We will be restarting system soon for

vdc [dec].
Explanation We will be restarting system since we were trying to do a hot switchover before all the
state could have been transferred to this supervisor. So we will be doing a cold switchover now.
Error Message SYSMGR-2-RESTORE_RUNTIME_DB_FAILED: Restoring of runtime database

for fabric switch upgrade failed during boot (error-id [hex]).
Explanation This message indicates that the runtime database could not be restored during boot for
the fabric switch upgrade.
2-530 OL-26589-01
Error Message SYSMGR-2-SAVE_RUNTIME_DB_FAILED: Saving of runtime database for

fabric switch upgrade failed (error-id [hex]).
Explanation This message indicates that the runtime database could not be saved for the fabric
switch upgrade.
Error Message SYSMGR-2-SERVICE_CRASHED: Service "[chars]" (PID [dec])

hasntcaughtsignal[dec][chars]'
Explanation A service has terminated its execution abnormally. The service might be restarted,
depending on the HA policies implemented for the service.
Recommended Action Please use the command showprocess'toverifythattheservicehasbeenrestarted.'
Error Message SYSMGR-2-SHUTDOWN_FAILURE: Unable to set signal handler for graceful

shutdown: [chars] (error-id [hex]).
Explanation This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).
Error Message SYSMGR-2-SHUTDOWN_REJECT: The System Manager is busy saving the

configuration. Please try again later.
Error Message SYSMGR-2-SHUTDOWN_SYSTEM_LOG: vdc [dec] will shut down soon.
Explanation We are shutting down system the vdc
Error Message SYSMGR-2-SIGKILL_FAILURE: Service "[chars]" failure to respond to

SIGKILL causing supervisor to reset. Last heartbeat %.2f secs ago.
Explanation We will be resetting the supervisor since service failed to respond to SIGKILL sent to
it by System Manager.
OL-26589-01 2-531
Error Message SYSMGR-2-SOCKET_ERROR: Failed to open socket connection, errno:

[dec].
Explanation Call to open socket connection failed.
Error Message SYSMGR-2-SRV_CLEAR_MEMORY_ALERT: service "[chars]" clear memory

alert ([dec]%)
Explanation Clean Memory Alert Event received
Error Message SYSMGR-2-SRV_MAJOR_MEMORY_ALERT: service "[chars]" major memory

alert ([dec]%)
Explanation Major Memory Alert Event received
Error Message SYSMGR-2-SRV_MINOR_MEMORY_ALERT: service "[chars]" minor memory

alert ([dec]%)
Explanation Minor Memory Alert Event received
Error Message SYSMGR-2-SRV_SPAWN_FAILED: Spawning of service "[chars]" in vdc [dec]

failed : [chars] (error-id [hex]).
Explanation Failed to spawn a service
Error Message SYSMGR-2-STANDBY_BOOT_FAILED: Standby supervisor failed to boot up.
Explanation This message is printed if the standby supervisor

doesntcompleteitsbootprocedure(i.e.itdoesn'treachtheloginpromptonthelocalconsole)3to6minutesaf
tertheloaderhasbeenloadedbytheBIOS.Thismessageisusuallycausedbybootvariablesnotproperlysetf
orthestandbysupervisor.Thismessagecanalsobecausedbyauserintentionallyinterruptingthebootproce
dureattheloaderprompt(bymeansofpressingESC).'
Recommended Action Connect to the local console of the standby supervisor. If the supervisor is at
the loader prompt, try to use the
boot'commandtocontinuethebootprocedure.Otherwise,issuea'reload'commandforthestandbysupervi
sorfromavshsessionontheactivesupervisor,specifyingthe'force-dnld'option.Oncethestandbyisonline,
fixtheproblembysettingthebootvariablesappropriately.'
2-532 OL-26589-01
Error Message SYSMGR-2-STARTUP_CONVERSION_FAILED: Startup config conversion failed

during boot (error-id [hex]).
Explanation This message indicates that the conversion of startup configuration failed during boot.
Error Message SYSMGR-2-START_SCRIPT_FAILED: Start script (/isan/etc/rc.sysmgr

start) failed with return value: ([dec]).
Explanation The initialization of the system could not complete.
Error Message SYSMGR-2-SUBPROC_SPAWN_FAILED: Spawning of sub-process "[chars]" in

vdc [dec] failed : [chars] (error-id [hex]).
Explanation Failed to spawn a sub-process
Error Message SYSMGR-2-SUP_POWERDOWN: Supervisor in slot [dec] is running with less

memory than active supervisor in slot [dec]
Explanation Supervisor memory mismatch
Error Message SYSMGR-2-SWITCHOVER_OVER: Switchover completed.
Explanation The switchover is completed.
Error Message SYSMGR-2-SWITCHOVER_SRVCRASHED: Service "[chars]" (PID [dec])

crashed during switchover - hasntcaughtsignal[dec].Corewillnotbecollected.'
Explanation The switchover failed because a service crashed during switchover.
Error Message SYSMGR-2-SWITCHOVER_SRVFAILED: Service "[chars]" failed in

performing its switchover actions (error-id [hex]).
Explanation The switchover failed because a service could not transition to the active state.
OL-26589-01 2-533
Error Message SYSMGR-2-SWITCHOVER_SRVTERMINATED: Service "[chars]" (PID [dec])

terminated during switchover with error code [dec] .
Explanation The switchover failed because a service terminated during switchover.
Error Message SYSMGR-2-SWITCHOVER_THRESHOLD_EXCEEDED: Switchover threshold

exceeded ([dec] switchovers happened within [dec] seconds). Powering down all
linecards.
Explanation Switchover threshold exceeded
Error Message SYSMGR-2-SWITCHOVER_TIMEOUT: Service "[chars]" (vdc [dec]) did not

respond to switchover message in [dec] seconds
Explanation The switchover timeout because a service failed to response
Error Message SYSMGR-2-SYNC_FAILURE_MSG_PAYLOAD: vdc [dec]: [chars]
Explanation Dump out the msg to know what causes sync failure
Error Message SYSMGR-2-SYNC_FAILURE_STANDBY_RESET: Failure in syncing messages to

standby for vdc [dec] causing standby to reset.
Explanation We will be resetting the standby since mts on the active is unable to sync messages to
standby.
Error Message SYSMGR-2-SYSMGR_AUTOCOLLECT_TECH_SUPPORT_LOG: This supervisor will

temporarily remain online in order to collect show tech-support. This behavior is
configurable via system[no]auto-collecttech-support'.'
Explanation Supervisor is automatically collecting logs
2-534 OL-26589-01
Error Message SYSMGR-2-TMP_DIR_FULL: System temporary directory usage is

Explanation System /tmp space is almost full.
Error Message SYSMGR-2-VDC_CREATE_DELETE_SRVCRASHED: Global vdc-aware service

"[chars]" (PID [dec]) crashed during vdc create/delete on standby -
hasntcaughtsignal[dec].'
Explanation The creation/deletion of vdc on standby failed because a global vdc-aware service
crashed on standby.
Error Message SYSMGR-2-VDC_CREATE_DELETE_SRVTERMINATED: Global vdc-aware service

[chars] (PID [dec]) terminated during vdc create/delete on standby with error code
[dec] .
Explanation The creation/deletion of vdc on standby failed because a global vdc-aware service
terminated on standby.
Error Message SYSMGR-2-VDC_DELETE_FAILURE: The vdc delete has failed: [chars]

(error-id [hex])
Explanation The vdc delete has failed
Error Message SYSMGR-2-VDC_NOT_CLEANEDUP_SRVS: vdc [dec]: [chars]
Explanation
Error Message SYSMGR-2-VOLATILE_DB_FULL: System volatile database usage is

Explanation System volatile database space is almost full.

systempssshrink'.Ifthismessagecontinuestopersist,pleasecontactTAC.'
OL-26589-01 2-535
Error Message SYSMGR-2-WARMSWITCHOVER_START: This supervisor is becoming active.
Explanation A cold switchover has started.
Error Message SYSMGR-2-WDT_KGDB: System watchdog kgdb has been [chars] for slot
[dec].
Explanation System watchdog kgdb has been [chars]. If the command has been enabled, the system
will go into kgdb if there is a watchdog timeout.
SYSMGR-3
Error Message SYSMGR-3-BASIC_TRACE: [chars]: PID [dec] with message [chars].
Explanation
Error Message SYSMGR-3-CAPABILITY_REDUN_CHANGE: Redundancy mode changed to [chars]

due to configuration change.
Explanation Some configuration changes have occurred causing administrative redundancy mode to
change.
Error Message SYSMGR-3-CFGCTRL_ABORT: signal to abort cfgctrl as super changes to

the unstable state
Explanation When super state changes to unstable, cfgctrl should be terminated
Error Message SYSMGR-3-CFGERASE_FAILED: Configuration erase failed (error-id

[hex]).
Explanation The requested configuration erase has failed. [dec] is the error-ID representing the
failure reason.
2-536 OL-26589-01
Error Message SYSMGR-3-CFGSNAPSHOT_FAILED: Configuration snapshot failed (error-id

[hex]).
Explanation The requested configuration snapshot has failed. [dec] is the error-id representing the
failure reason.
Error Message SYSMGR-3-CFGWRITE_FAILED: Configuration copy failed (error-id

[hex]).
Explanation The requested configuration copy has failed. [dec] is the error-id representing the
failure reason.
Error Message SYSMGR-3-CFGWRITE_REJECT: Discarding request for configuration

[chars]: configuration action already in progress.
Explanation Another instance of the command copyrunning-configstartup-config'isinprogress.'
Recommended Action Please wait for the other instance to complete.
Error Message SYSMGR-3-CFGWRITE_SRVCRASHED: Service [chars] crashed with signal

([dec]) while configuration was being saved
Explanation A required service has crashed while configuration was being saved. The overall
configuration copy is considered failed.
Error Message SYSMGR-3-CFGWRITE_SRVFAILED: Service "[chars]" failed to store its

configuration (error-id [hex]).
Explanation A required service has failed to store its own configuration into the startup-config. The
overall configuration copy is considered failed.
Recommended Action Use the

showprocess'commandtoverifythatthesystemisrunningproperlyandtheservice[chars]isbehavingcorr
ectly.Thentryagain.'
Error Message SYSMGR-3-CFGWRITE_SRVTERMINATED: Service [chars] terminated with

error code ([dec]) while configuration was being saved
Explanation A required service has terminated while configuration was being saved. The overall
OL-26589-01 2-537
Error Message SYSMGR-3-CFGWRITE_SRVTIMEOUT: Service [chars] failed to store its

configuration in the timeout period
Explanation A required service has failed to send a response after receving a request to store its
configuration into the startup-config. The overall configuration copy is considered failed.
Error Message SYSMGR-3-CFGWRITE_VDCSRVCRASHED: Service [chars] in vdc [dec]

crashed with signal ([dec]) while configuration was being saved
Explanation A required service has crashed while configuration was being saved. The overall
Error Message SYSMGR-3-CFGWRITE_VDCSRVFAILED: Service "[chars]" in vdc [dec]

failed to store its configuration (error-id [hex]).
Explanation A required service has failed to store its own configuration into the startup-config. The
overall configuration copy is considered failed.

showprocess'commandtoverifythatthesystemisrunningproperlyandtheservice[chars]isbehavingcorr
ectly.Thentryagain.'
Error Message SYSMGR-3-CFGWRITE_VDCSRVTERMINATED: Service [chars] in vdc [dec]

terminated with error code ([dec]) while configuration was being saved
Explanation A required service has terminated while configuration was being saved. The overall
Error Message SYSMGR-3-CFGWRITE_VDCSRVTIMEOUT: Service [chars] in vdc [dec] failed

to store its configuration in the timeout period
Explanation A required service has failed to send a response after receving a request to store its
configuration into the startup-config. The overall configuration copy is considered failed.
2-538 OL-26589-01
Error Message SYSMGR-3-COPY_CORES_FAILED: Copying cores failed ([dec]).
Explanation Copying cores to the destination failed because of an error specified in the log.
Error Message SYSMGR-3-COREDUMP_TIMEOUT: Failed to store the core in the specified

time. Resetting ....
Explanation Failed to store the core in the specified time. Resetting ...
Error Message SYSMGR-3-CORE_CLIENT_INIT_FAILED: Core client will not be started

due to some internal error.
Explanation Core client will not be started due to some internal error.
Error Message SYSMGR-3-CORE_OP_FAILED: Core operation failed: [chars]
Explanation Mainly use to display failure on core operation in general
Error Message SYSMGR-3-CORE_SERVER_INIT_FAILED: Core server will not be started

due to some internal error.
Explanation Core server will not be started due to some internal error.
Error Message SYSMGR-3-DAEMONIZE_FAILED: Unable to daemonize service "[chars]":

[chars] ([dec]).
Explanation A service could not be spawned.
Error Message SYSMGR-3-FAILED_PFM_HANDSHAKE: PFM-handshake from service "[chars]"

failed (error-id [hex]).
Explanation The Platform Manager handshake has failed. The system

cantproceedwiththeinitialization.'
OL-26589-01 2-539
Error Message SYSMGR-3-GSYNC_TIMEOUT_FAILED: Failed to set timeout for global sync

for an application ([dec]).
Explanation Failed to set timeout for global sync for an application. This can result in global sync
to be stuck forever if application never complete global sync.
Error Message SYSMGR-3-HEARTBEAT_FAILURE: Service "[chars]" sent SIGABRT for not

setting heartbeat for last [dec] periods. Last heartbeat %.2f secs ago.
Explanation A service is not setting proper heartbeats to System Manager So it will kill this service
and if this service has restartability set to TRUE, the service will restart.
Error Message SYSMGR-3-INVALID_BOOT_HANDSHAKE: Boot-scope-handshake received from

service [chars], that is in scope [dec] (not the boot scope).
Explanation A service is trying to take actions that belong to a different class of services.
Error Message SYSMGR-3-INVALID_GSYNC_GET: Service "[chars]" vdc [dec] requesting

gsync without setting proper flag in its conf file.
Explanation Service is requesting global sync without setting proper flag in its conf file.
Error Message SYSMGR-3-INVALID_PFM_HANDSHAKE: PFM-handshake received from service

[chars], that is in scope [dec] (not the boot scope).
Explanation A service is trying to take actions that belong to the Platform Manager service.
Error Message SYSMGR-3-INVALID_TRANSITION: Transition from state [chars] to state

[chars] is not allowed.
Explanation Unexpected transition in the System Manager state machine.
2-540 OL-26589-01
Error Message SYSMGR-3-INVALID_UUID: Service [chars] is configured with UUID [hex],

but uses UUID [hex].
Explanation The identity of a service is inconsistent in the image file
Error Message SYSMGR-3-ISSU_BEGIN_FAILED: ISSU cannot proceed (error-id [hex]).
Explanation This message indicates that some service has blocked the ISSU.
Error Message SYSMGR-3-LC_IMAGE_UPGRADE_FAILURE: Linecard image upgrade request

failed(error-id [hex]).
Explanation Linecard image upgrade request failed
Error Message SYSMGR-3-LC_RESET: Resetting linecard
Explanation Linecard is being reset
Error Message SYSMGR-3-LC_SAVE_STATES_FAILURE: Save states request for the

linecard failed(error-id [hex]).
Explanation Save state request for the linecard failed
Error Message SYSMGR-3-LC_STOP_ASYNC_FAILURE: Stop async notification request

failed(error-id [hex]).
Explanation Stop async notification request for the linecard failed
OL-26589-01 2-541
Error Message SYSMGR-3-LC_UPG_ERROR: LC ERROR: [chars]
Explanation Linecard upgrade error message
Error Message SYSMGR-3-MISSING_OPTIONAL_CAPABILITY: Incomplete support for the

current running-config on standby supervisor.
Explanation Loose config incompatibilities exist between active and standby sup. Operational
redundancy mode is still set to HA.
Error Message SYSMGR-3-MODULE_LOCK_FAILED: Failed to lock the local module to avoid

reset (error-id [hex]).
Explanation Locking the local module has failed. Reloading the local module can now result in
switchover to fail.
Error Message SYSMGR-3-ND_UPGD_RECOVERY_SRVFAILED: Service "[chars]" in vdc [dec]

failed in non-disruptive upgrade recovery (error-id [hex]).
Explanation The non-disruptive upgrade failed because a service could not recover its state.
Error Message SYSMGR-3-OPERATIONAL_MODE_WARM: Operational redundancy mode set to

warm (error-id [hex]).
Explanation Operational redundancy mode will be set to warm. [dec] is the error-ID representing
the reason.
Error Message SYSMGR-3-PARTIAL_CFGWRITE_FAILED: Partial configuration copy failed

(error-id [hex]).
Explanation The requested configuration copy has failed. [dec] is the error-ID representing the
failure reason.
2-542 OL-26589-01
Error Message SYSMGR-3-PARTIAL_CFGWRITE_VER_MISMATCH: Startup-config version not

same as current software version.
Explanation Startup-config version not same as current software version.
Recommended Action Please do a copy running startup, and try again.
Error Message SYSMGR-3-RTDBCTRL_BUILD_UPG_TBL_FAILED: Failed to prepare upgrade

version table during pre-upgrade
Explanation A required sequence in the preupgrade sequence has failed. The version table could not
be built correctly
Error Message SYSMGR-3-RTDBCTRL_SRVFAILURE: Service "[chars]" responded with a

failure
Explanation A service responded with a failure to the request
Error Message SYSMGR-3-RTDBCTRL_SRVTIMEOUT: Service [chars] failed to respond back

to System Manager in the specified timeout period
Explanation A required service has failed to send a response after receiving a request for the fabric
switch upgrade.
Error Message SYSMGR-3-RTDBCTRL_SRV_RECV_FAILED: Failed to receive response from

Service "[chars]"
Explanation A required service has failed to send a response after receiving a request for the fabric
switch upgrade.
Error Message SYSMGR-3-RTDBCTRL_SRV_SEND_FAILED: Failed to send upgrade request to

Service "[chars]"
Explanation Failed to send upgrade request to a required service
OL-26589-01 2-543
Error Message SYSMGR-3-SERVICE_TERMINATED: Service [chars] (PID [dec]) has

finished with error code [chars] ([dec]).
Explanation A service has terminated its execution normally. Depending on the value of [dec2] and
the HA policies implemented for the service, the service might be restarted automatically.
Error Message SYSMGR-3-SHUTDOWN_OVER: The System Manager is shutting down now.
Error Message SYSMGR-3-SHUTDOWN_START: The System Manager has started the shutdown
procedure.
Error Message SYSMGR-3-STANDBY_UNSTABLE_FTSET_OPERATION: Restarting standby since

it is not in hot standby state while feature-set operation was in progress in vdc
[dec].
Explanation Standby unstable during feature-set operation
Error Message SYSMGR-3-STANDBY_VDC_RESTART_FAILURE: vdc [dec] on standby failed to

restart. error: [chars] ([hex])
Explanation
Error Message SYSMGR-3-SYSMGR_CRASHED: Sysmgr (PID [dec]) [chars]
Explanation Sysmgr has terminated abnormally.
Recommended Action Please use the command showprocess'toverifythatsysmgrhasbeenrestarted.'
Error Message SYSMGR-3-TFTP_CORES_FAILED: TFTPing cores failed ([chars]).
Explanation TFTPing cores to the destination failed because of an error specified in the log.
2-544 OL-26589-01
Error Message SYSMGR-3-UNACCEPTABLE_WAIT: Service [chars], no response from System

Manager after [dec] seconds. Terminating.
Explanation A spawned service

couldnthandshakewiththeSystemManagerandit'sabouttobeterminated.'
Error Message SYSMGR-3-UNLINK_RELINK_CONF_FILES_FAILED: [chars] of conf files

failed. plugin_id [dec]
Explanation Unlink and/or Relink of configuration files failed.
Error Message SYSMGR-3-URIFS_APPLY_FAILED: Applying URI filesystem database failed

(error-id [hex]).
Explanation The application of URI filesystem database has failed. [dec] is the error-ID representing
the failure reason.
SYSMGR-4
Error Message SYSMGR-4-BASIC_TRACE_WARNING: [chars]: PID [dec] with message

[chars].
Explanation
Error Message SYSMGR-4-CFGWRITE_PARTIALFORCED: Some services are missing; partial

configuration write forced.
Explanation The system is not fully operational, but a configuration copy has been forced. The
services that are not running
wontsavetheirconfiguration,andthenexttimetheywillrestartwithadefaultconfiguration.'

showprocess'commandtofindoutwhichrequiredservicesarenotrunning.'
Error Message SYSMGR-4-ON_DEMAND_STOP_UID_KNOWN: On-demand service "[chars]"

stopped by uid ([dec]).
Explanation The service start type is specified as type on-demand in its configuration file and an
external request requested to abort it.
OL-26589-01 2-545
Error Message SYSMGR-4-ON_DEMAND_STOP: On-demand service "[chars]" stopped.
Explanation The service start type is specified as type on-demand in its configuration file and an
external request requested to abort it.
Error Message SYSMGR-4-PARSEWARN_INVALID_CFGFILE: [chars]: unable to find

"[chars]": [chars] ([dec]).
Explanation This message is for Cisco TAC debugging. This is not a problem or malfunction.
Error Message SYSMGR-4-PARSEWARN_RESTART_CNT_TOO_BIG: Service "[chars]": [chars]

restart count of [dec] too big, needs to be set to [dec].
Error Message SYSMGR-4-PARSEWARN_VALUE_TOO_SMALL: [chars]: [chars] is too small,

replaced with [dec].
Error Message SYSMGR-4-READCONF_REJECT: Discarding configuration update request:

[chars].
Error Message SYSMGR-4-READCONF_STARTED: Configuration update started (PID [dec]).
Error Message SYSMGR-4-SRVSCOPE_DELAYED: Waiting for redundancy state; termination

delayed for scope [chars].
2-546 OL-26589-01
Error Message SYSMGR-4-SYSMGR_CORE_TRUNCATED: Core seems to be truncated on

generation. [dec] / [dec] KB. PID: [dec]
Explanation Core likely truncated
Error Message SYSMGR-4-SYSMGR_PLUGIN_FAILURE: Received failure response [hex] from

Plugin Manager
Explanation Failure response from plugin mgr
Error Message SYSMGR-4-SYSMGR_VDC_CORE_DELETION: Cores in VDC [dec] will be deleted

as part of VDC deletion
Explanation VDC cores deleted
Error Message SYSMGR-4-UGRP_ALL_COMPLETED: Upgrade completed for all the groups.
Error Message SYSMGR-4-VAR_SYSMGR_FULL: System core file storage usage is

unexpectedly high at [dec]%. This may cause corruption of core files
Explanation System core file storage space is almost full.
Recommended Action Please copy cores off the supervisor and run clearcores'tofreesomespace'
SYSMGR-5
Error Message SYSMGR-5-CFGERASE_DONE: Configuration erase successful.
Explanation The requested configuration erase has completed successfully.
Error Message SYSMGR-5-CFGERASE_STARTED: Configuration erase started (PID [dec]).
Explanation The requested configuration erase has started. [dec] is the Process-ID of the process
servicing the request.
OL-26589-01 2-547
Error Message SYSMGR-5-CFGINIT_STARTED: Initialization of the startup

configuration started (PID [dec]).
Explanation The requested initialization of the startup configuration has started. [dec] is the
Process-ID of the process servicing the request.
Error Message SYSMGR-5-CFGSNAPSHOT_DONE: Configuration snapshot successful.
Explanation The requested configuration snapshot has completed successfully.
Error Message SYSMGR-5-CFGSNAPSHOT_STARTED: Configuration snapshot started (PID

[dec]).
Explanation The requested configuration snapshot has started. [dec] is the Process-ID of the process
servicing the request.
Error Message SYSMGR-5-CFGWRITE_DONE: Configuration copy successful.
Explanation The requested configuration copy has completed successfully.
Error Message SYSMGR-5-CFGWRITE_STARTED: Configuration copy started (PID [dec]).
Explanation On the active supervisor, this message indicates that the system has started to service a
copyrunning-configstartup-config'requestedbytheuser.Onthestandbysupervisor,thismessageindicat
esthatthesystemissynchronizingthestartup-configfromtheactivesupervisor.[dec]istheProcess-IDofth
eprocessservicingtherequest.'
Error Message SYSMGR-5-CONVERT_STARTUP_STARTED: Configuration conversion started

(PID [dec]).
Explanation This message indicates that the system has started conversion of startup configuration.
This happens either on system boot or during the course of an upgrade.
2-548 OL-26589-01
Error Message SYSMGR-5-DELETE_BINARY_STARTUP_STARTED: Deletion of binary startup

configuration started (PID [dec]).
Explanation This message indicates that the system will be deleting the binary startup configuration,
due to an error in the conversion of the startup conversion.
Error Message SYSMGR-5-FSM_STATE_TRANS: System Manager NESTED state transition

from [chars] to [chars].
Explanation
Error Message SYSMGR-5-IMPROPER_CLEANUP: Service "[chars]" exited without replying

to switchover request.
Explanation A conditional service exited without replying to switchover request. This message is
for logging purposes only and does not affect the functionality of the system
Error Message SYSMGR-5-ISSU_ABORT: Notifying services of aborted ISSU (PID [dec]).
Explanation This message indicates that the ISSU has been aborted and the services have been asked
to rollback any changes.
Error Message SYSMGR-5-ISSU_BEGIN_STARTED: Notifying services of ISSU (PID [dec]).
Explanation This message indicates that the system has started notifying services for the ISSU.
Services can block the upgrade at this point.
Error Message SYSMGR-5-LC_UPGRADE_REBOOT: Rebooting linecard as a part of upgrade
Explanation Linecard is being rebooted as a part of upgrade
OL-26589-01 2-549
Error Message SYSMGR-5-LC_UPGRADE_START: Starting linecard upgrade
Explanation Linecard upgrade is starting
Error Message SYSMGR-5-MODULE_ONLINE: System Manager has received notification of

local module becoming online.
Explanation System Manager has received notification of local module becoming online.
Error Message SYSMGR-5-PARTIAL_CFGWRITE_ASCII_CONFIG: Startup-config version not

present.
Explanation Startup-config version not present.
Recommended Action Startup-config version is not present. Ascii configuration will be applied.
Error Message SYSMGR-5-PARTIAL_CFGWRITE_DONE: Partial configuration copy

successful.
Explanation The requested configuration copy has completed successfully.
Error Message SYSMGR-5-PARTIAL_CFGWRITE_STARTED: Partial configuration copy

started by UUID [hex] (PID [dec]).
Explanation This message is printed only on active supervisor, and indicates that service with
mentioned UUID has requested a partial write mem. [dec] is the Process-ID of the process servicing
the request.
Error Message SYSMGR-5-RECOVERY_FAILED: Stateful recovery failed, system manager

will now start stateless.
Explanation Stateful recovery failed, system manager will now restart system and start stateless.
2-550 OL-26589-01
Error Message SYSMGR-5-RUNTIME_DB_RESTORE_STARTED: Runtime database controller

started (PID [dec]).
Explanation This message indicates that the system has started the restoration of the runtime
database. This happens during the non-disruptive fabric switch upgrade.
Error Message SYSMGR-5-RUNTIME_DB_RESTORE_SUCCESS: Runtime database successfully

restored.
Explanation This message indicates that the runtime database has been successfully restored for the
non-disruptive fabric switch upgrade.
Error Message SYSMGR-5-RUNTIME_DB_SAVE_STARTED: Runtime database save has started

(PID [dec]).
Explanation This message indicates that the system has started the saving of the runtime database.
This happens during the non-disruptive fabric switch upgrade.
Error Message SYSMGR-5-SERVICE_DELETED: Service [chars] has been removed from the
System Manager database.
Error Message SYSMGR-5-STATEFUL_STATE: System Manager is in state [chars] after

stateful restart.
Explanation System Manager has been restarted stateful after an error that resulted in System
Manager exiting.
Error Message SYSMGR-5-SUBPROC_KILLED: "[chars]" (PID [dec])

hasntcaughtsignal[dec][chars]'
OL-26589-01 2-551
Error Message SYSMGR-5-SUBPROC_TERMINATED: "[chars]" (PID [dec]) has finished with

error code [chars] ([dec]).
Error Message SYSMGR-5-UGRP_COMPLETED: Upgrade completed for group [dec].
SYSMGR-6
Error Message SYSMGR-6-ALL_SCOPES_STARTED: System services have completely started

at this time.
Explanation System services have completely started at this time.
Error Message SYSMGR-6-HANDSHAKE_DONE: Handshake with service "[chars]"

successfully performed.
Error Message SYSMGR-6-HANDSHAKE_VERIFYING_DONE: Handshake verification done from

service "[chars]".
Explanation
Error Message SYSMGR-6-LC_UPG_DEBUG: LC DEBUG: [chars]
Explanation Linecard upgrade debug message
Error Message SYSMGR-6-RLIMIT_INFO: rlimit of service "[chars]"([dec]) = %llu
Explanation
2-552 OL-26589-01
Error Message SYSMGR-6-SERVICE_STARTED: Service "[chars]" in vdc [dec] started with

PID([dec]).
Explanation The System Manager is starting a service. This message is for debugging purposes only.
Error Message SYSMGR-6-SERVICE_SUCCESS_EXIT: Service [chars] (PID [dec]) has

successfully exited with exit code [chars] ([dec]).
Explanation A service has successfully exited its execution.
Error Message SYSMGR-6-SRVSCOPE_COMPLETED: Completed execution for scope [chars].
Error Message SYSMGR-6-SRVSCOPE_STARTED: Started execution for scope [chars].
Error Message SYSMGR-6-SRVSTATE_CHANGED: State for service "[chars]" changed from

[chars] to [chars] in vdc [dec].
Error Message SYSMGR-6-SRV_ENQUEUED_FOR_START: Conditional service "[chars]"

started by sap "[dec]" has been enqueued for start.
Explanation
Error Message SYSMGR-6-STATE_CHANGED: System Manager state changed from [chars] to

[chars] for vdc [dec].
Explanation
OL-26589-01 2-553
Error Message SYSMGR-6-SUBPROC_SUCCESS_EXIT: [chars] (PID [dec]) has successfully

exited with exit code [chars] ([dec]).
Error Message SYSMGR-6-SUPERSTATE_CHANGED: System Manager super state changed from

[chars] to [chars] for vdc [dec].
Explanation
Error Message SYSMGR-6-UNEXPECTED_GSYNC_RESTART_STANDBY: Sending a message to

restart system on standby on vdc [dec].
Explanation Activity occurred on active supervisor that is incompatible with state of standby.
System will be restarted on standby.
SYSMGR-7
Error Message SYSMGR-7-CFGWRITE_UNEXPECTEDRSP: Discarding unexpected response from

service "[chars]".
Explanation
Error Message SYSMGR-7-DUPLICATED_PFM_HANDSHAKE: PFM-handshake received from

service [chars], but information already available.
Error Message SYSMGR-7-LIBCDB_FAILURE: Conversion for service "[chars]" failed in

libcdb.
Explanation This message indicates that either the system could not find conversion tarball or there
is no conversion library needed for this service.
2-554 OL-26589-01
Error Message SYSMGR-7-LIBVDB_FAILURE: Conversion for service "[chars]" failed in

libvdb.
Explanation This message indicates that the system could not find package information for this
service in the version database.
Error Message SYSMGR-7-ND_UPGD_RECOVERY_SRVSUCCEEDED: Service "[chars]" recovered

its state during non-disruptive upgrade.
Explanation
Error Message SYSMGR-7-NO_STARTUP_CONFIG: No startup-config to convert.
Explanation This message indicates that the system tried to convert startup configuration but it
found no configuration to convert.
Error Message SYSMGR-7-SWITCHOVER_SRVSUCCEDED: Service "[chars]" completed its

switchover actions.
Error Message SYSMGR-7-UNEXPECTEDMSG: Opcode [dec] not expected at this time from
service "[chars]" ([chars]).
Error Message SYSMGR-7-UNKNOWNADDR: Opcode [dec] received from unknown source

[chars]. Discarding.
Error Message SYSMGR-7-UNKNOWNMSG: Unknown opcode [dec] received from [chars].
Explanation The System Manager has received an unrecognized message with the specified opcode.
[chars] is the source of the message. This message is for debugging purposes only.
OL-26589-01 2-555
Error Message SYSMGR-7-UNKNOWNPID: Opcode [dec] received from [chars] with unknown
PID [dec]. Discarding.
Explanation The System Manager has received a message from an unknown process. [chars] is the
source of the message. This message is for debugging purposes only.
Error Message SYSMGR-7-UNKNOWNUUID: Opcode [dec] received from [chars] with unknown
UUID [dec]. Discarding.
Explanation The System Manager has received an unrecognized message from the specified UUID.
[chars] is the source of the message. This message is for debugging purposes only.
SYSTEMHEALTH Messages
This section contains the SYSTEMHEALTH messages.
SYSTEMHEALTH-2
Error Message SYSTEMHEALTH-2-OHMS_BATTERY_FAILED: Battery [dec] failed for module

[dec]. Reason: [chars].
Explanation Battery failed.
Error Message SYSTEMHEALTH-2-OHMS_BOOTFLASH_FAILED_RESET_DAY: Bootflash hard

resets for module [dec] has reached threshold limit in 24 hours.
Explanation Bootflash hard resets reached threshold limit in 24 hours.
Error Message SYSTEMHEALTH-2-OHMS_BOOTFLASH_FAILED_RESET_LIFE: Bootflash hard

resets for module [dec] has reached the maximum threshold limit.
Explanation Bootflash hard resets reached maximum threshold limit.
2-556 OL-26589-01
Error Message SYSTEMHEALTH-2-OHMS_BOOTFLASH_FAILED: Bootflash test maximum

failures reached for module [dec] Reason: ([chars]).
Explanation Bootflash failed.
Error Message SYSTEMHEALTH-2-OHMS_CACHE_DISK_FAILED: Cache disk [dec] failed for

module [dec].
Explanation Cache disk failed.
Error Message SYSTEMHEALTH-2-OHMS_EMGMT_FAILED: Management port failed for module

[dec].
Explanation Ethernet management port failed.
Error Message SYSTEMHEALTH-2-OHMS_EOBC_FAILED: EOBC test failed for module [dec].
Explanation EOBC test failed for module.
Error Message SYSTEMHEALTH-2-OHMS_FIPS_FAILURE: FIPS compliance error during

random number generation.
Explanation FIPS compliance error.
Error Message SYSTEMHEALTH-2-OHMS_FREE_DISK_FAILED: Free Disk Space on partition

[chars] is below [chars] threshold for module [dec].
Explanation System Health Free Disk Space below threshold.
Recommended Action Force a switch over if a standby supervisor is available, or reboot the switch
to recover
Error Message SYSTEMHEALTH-2-OHMS_FREE_DISK_RUNNING: Free Disk Space on partition

[chars] have increased and is above [chars] threshold for module [dec].
Explanation System Health Free Disk Space above threshold.
OL-26589-01 2-557
Error Message SYSTEMHEALTH-2-OHMS_INBAND_FAILED: Inband test maximum failures

reached for module [dec].
Explanation Inband failed.
Error Message SYSTEMHEALTH-2-OHMS_MOD_PORT_LB_TEST_FAILED: Module [dec] Port [dec]

has failed loop back tests.
Explanation Port loop-back test failure.
Error Message SYSTEMHEALTH-2-OHMS_MOD_RELOAD_REQ: Module [dec] reload being

requested due to errors found by [chars] test.
Explanation System Health Module Reload Request.
Error Message SYSTEMHEALTH-2-OHMS_MOD_SNAKE_TEST_FAILED: Module [dec] has failed

snake loopback tests.
Explanation Snake test failure.
Error Message SYSTEMHEALTH-2-OHMS_NVRAM_FAILED: Nvram test maximum failures

reached for module [dec] for blocks 0x%llx.
Explanation Nvram failed.
Error Message SYSTEMHEALTH-2-OHMS_SUP_CF_CRC_FAILED: Compact Flash firmware CRC

checksum on module [dec] is corrupted.
Explanation Compact flash firmware has been corrupted.
Recommended Action Replace the compact flash on this module.
Error Message SYSTEMHEALTH-2-OHMS_SUP_CF_CRC_INIT_ERRORS: Compact Flash firmware

CRC checksum procedure encountered an error during initialization on module [dec],
reason:([chars]).
Explanation Compact flash CRC checksum initializations failed.
Recommended Action Check the compact flash on the board and any relevant system
(mis)configurations.
2-558 OL-26589-01
Error Message SYSTEMHEALTH-2-OHMS_SUP_CF_REFLASH_FAILED: Compact Flash firmware

refresh procedure failed, replace the compact flash on module [dec]. Reason [dec]
Explanation Compact flash firmware has been corrupted is corrupted.
Recommended Action Replace the compact flash on this module.
Error Message SYSTEMHEALTH-2-OHMS_SWITCHOVER_REQ: Supervisor switch over being

requested due to errors found [chars] test.
Explanation System Health Switch Over Request.
Error Message SYSTEMHEALTH-2-OHMS_SWITCH_RELOAD_REQ: Switch reload request due to

errors found [chars] test.
Explanation System Health Switch Reload Request.
Error Message SYSTEMHEALTH-2-OHMS_TCAM_PARITY_FAILED: TCAM test failed for module

[dec].
Explanation TCAM test failed for module as uncorrectable parity errors were detected.
Recommended Action Please schedule a downtime and replace the module.
Error Message SYSTEMHEALTH-2-OHMS_TCAM_PARITY_OFLOW: Too many TCAM Parity errors

detected on module [dec]
Explanation More parity errors than that can be corrected were detected on the affected module
Recommended Action Please schedule a downtime and reload the module. If these errors continue to
happen even after module reload, please replace the module
SYSTEMHEALTH-4
Error Message SYSTEMHEALTH-4-OHMS_BATTERY_ERRORS: Battery test on module [dec] has

been suspended due to internal errors.
Explanation Battery test internal errors.
OL-26589-01 2-559
Error Message SYSTEMHEALTH-4-OHMS_BOOTFLASH_TEST_ERRORS: Bootflash test cannot

proceed due to internal errors on module [dec].
Explanation Compact flash test internal errors.
Error Message SYSTEMHEALTH-4-OHMS_CACHE_DISK_ERRORS: Cache disk test on module

[dec] dpp [dec] has been suspended due to internal errors.
Explanation Cache disk test internal errors.
Error Message SYSTEMHEALTH-4-OHMS_CF_CRC_PASSED: Compact Flash firmware on module

[dec] is healthy at this time.
Explanation The Compact Flash model has data retention issues and need to be replaced.
Recommended Action Please schedule a downtime and replace the compact flash on this module.
Error Message SYSTEMHEALTH-4-OHMS_CF_REFLASH_PASSED: Compact Flash firmware was

successfully refreshed on module [dec].
Explanation The Compact Flash model has data retention issues and need to be replaced.
Error Message SYSTEMHEALTH-4-OHMS_EMGMT_ERRORS: Management port test cannot

proceed due to internal errors on module [dec].
Explanation Ethernet management port internal errors.
Error Message SYSTEMHEALTH-4-OHMS_EOBC_ERRORS: EOBC test on module [dec] has been

suspended due to internal errors.
Explanation EOBC test internal errors.
Error Message SYSTEMHEALTH-4-OHMS_EOBC_HALTED: EOBC Test Halted for module [dec].

Module needs EPLD Upgrade
Explanation Module does not have the minimum required EPLD version to run EOBC test.
Recommended Action Please upgrade the module with the latest EPLDs.'
2-560 OL-26589-01
Error Message SYSTEMHEALTH-4-OHMS_EXIT: Online System Health exiting due to

internal errors. Reason [dec].
Explanation Online System Health exiting due to internal errors.
Error Message SYSTEMHEALTH-4-OHMS_FAIL_ACTION_NOTICE: Failure action not taken,

failure action is disabled.
Explanation System Health SERDES test failure.
Error Message SYSTEMHEALTH-4-OHMS_FREE_DISK_ERRORS: Too many errors on module

[dec] while running the Free Disk Space test for partition [chars].
Explanation System Health Free Disk Space test has too many errors while running.
Error Message SYSTEMHEALTH-4-OHMS_FREE_DISK_FAILING: Free Disk Space on partition

[chars] is starting to go below threshold for module [dec]
Explanation System Health Free Disk Space going below threshold.
Recommended Action Force a switch over if a standby supervisor is available, or reboot the switch
to recover
Error Message SYSTEMHEALTH-4-OHMS_INBAND_FAILING1: Inband test failed [dec] times

for module [dec].
Explanation Inband Failing.
Error Message SYSTEMHEALTH-4-OHMS_INBAND_TEST_ERRORS: Too many errors while

running the inband test.
Explanation Inband test has had too many errors while running.
Error Message SYSTEMHEALTH-4-OHMS_LC_DAEMON_EXITED: System Health process running

on module [dec] exited due to internal errors. Will attempt to restart.
Explanation System Heath line card daemon exited.
OL-26589-01 2-561
Error Message SYSTEMHEALTH-4-OHMS_LC_DAEMON_FAILED: System Health process running

on module [dec] failed due to fatal errors.
Explanation System Heath line card daemon failed.
Error Message SYSTEMHEALTH-4-OHMS_LC_DAEMON_RESTARTED: System Health process

running on module [dec] restarted.
Explanation System Heath line card daemon restarted.
Error Message SYSTEMHEALTH-4-OHMS_MOD_SNAKE_PATH_FAILURE: Snake Loopback data path

failure on module [dec].
Explanation Snake data path only error.
Error Message SYSTEMHEALTH-4-OHMS_MOD_SNAKE_TEST_ERRORS: Snake Loopback test

cannot proceed due to internal errors for module [dec].
Explanation Snake test internal errors.
Error Message SYSTEMHEALTH-4-OHMS_NVRAM_ERRORS: Too many errors on module [dec]

while running the Nvram test.
Explanation Nvram test has had too many errors while running.
Error Message SYSTEMHEALTH-4-OHMS_SERDES_FAILED: SERDES loopback test on interface

fc[dec]/[dec] failed.
Explanation System Health SERDES Test Failure.
Error Message SYSTEMHEALTH-4-OHMS_SUP_BOOTFLASH_ERRORS: Bootflash test has

encountered an error on module [dec] Reason:([chars]).
Explanation Compact flash test errors on supervisor.
2-562 OL-26589-01
Error Message SYSTEMHEALTH-4-OHMS_SUP_CF_CRC_INTERN_ERRORS: Compact flash firmware

CRC checksum procedure cannot proceed due to internal errors on module [dec].
Explanation Compact flash firmware CRC checksum procedure ended up in errors.
Recommended Action Try restarting the cf-crc-check using system health clear-errors module <x
Error Message SYSTEMHEALTH-4-OHMS_SUP_CF_CRC_PROCESS_ERRORS: Compact flash

firmware CRC checksum procedure failed on module [dec]. Reason [dec]
Explanation Compact flash firmware CRC checksum procedure failed.
Recommended Action Try restarting the cf-crc-check using system health clear-errors module <x
Error Message SYSTEMHEALTH-4-OHMS_SUP_CF_CRC_TEST_FAILING: Compact flash firmware

CRC checksum validation starting to fail on module [dec].
Explanation Compact flash firmware CRC checksum might be bad on this module.
Recommended Action Schedule a downtime and replace the compact flash on the affected module.
Do not attempt any hitless up/downgrades.
Error Message SYSTEMHEALTH-4-OHMS_SUP_CF_RECALLED: Compact Flash on module [dec]

was recalled.
Explanation The Compact flash model has data retention issues and need to be replaced.
Error Message SYSTEMHEALTH-4-OHMS_SUP_CF_REFLASH_INTERN_ERRORS: Compact Flash

firmware re-flash procedure cannot proceed due to internal errors on module [dec].
Explanation Compact flash firmware re-flash procedure ended up in errors.
Recommended Action Try restarting the test using system health clear-errors module <x
Error Message SYSTEMHEALTH-4-OHMS_SUP_CF_REFLASH_TEST_FAILING: Compact flash

firmware refresh procedure starting to fail on module [dec].
Explanation Compact flash might be dead on this module.
Error Message SYSTEMHEALTH-4-OHMS_SUP_CF_UNRESPONSIVE: Recalled Compact Flash on

module [dec] is unresponsive.
Explanation The Compact flash model has data retention issues and need to be replaced.
OL-26589-01 2-563
Error Message SYSTEMHEALTH-4-OHMS_SVC_DAEMON_FAILED: System Health process running

on module [dec] SVC node [dec] exited due to errors.
Explanation OHMS SVC daemon exited.
Error Message SYSTEMHEALTH-4-OHMS_TCAM_PARITY_ACL_FIB_TIMEOUT: TCAM test timeout

waiting for ACL/FIB to update TCAM on module [dec]
Explanation System health TCAM test timeout occured while waiting for response from ACL/FIB
Recommended Action If significant packet drops are encountered in the forwarding engine, please
schedule a downtime and reload the module
Error Message SYSTEMHEALTH-4-OHMS_TCAM_PARITY_ACL_FIB_UPDATE_FAILING: Tcam test

failed as ACL/FIB failed to update TCAM on module [dec]
Explanation ACL/FIB failed to update TCAM after soft parity errors were encountered.
Recommended Action If significant packet drops are encountered in the forwarding engine, please
schedule a downtime and reload the module
Error Message SYSTEMHEALTH-4-OHMS_TCAM_PARITY_ERRORS: TCAM test on module [dec]

has been suspended due to internal errors.
Explanation TCAM test internal errors.
SYSTEMHEALTH-5
Error Message SYSTEMHEALTH-5-OHMS_BATTERY_FAILING: Battery [dec] starting to fail

on module [dec]. Reason: [chars].
Explanation System Health battery failing.
Error Message SYSTEMHEALTH-5-OHMS_BOOTFLASH_FAILING: Bootflash starting to fail on

module [dec].
Explanation System Health bootflash failing.
2-564 OL-26589-01
Error Message SYSTEMHEALTH-5-OHMS_CDISK_FAILING: Cache disk [dec] starting to fail

on module [dec].
Explanation System Health cache disk failing.
Error Message SYSTEMHEALTH-5-OHMS_EMGMT_FAILING: Management port on module [dec]

starting to show signs of failures.
Explanation System Health emgmt failing.
Error Message SYSTEMHEALTH-5-OHMS_EOBC_FAILING: EOBC starting to fail on module

[dec].
Explanation System Health eobc failing.
Error Message SYSTEMHEALTH-5-OHMS_INBAND_FAILING: Inband starting to fail on

module [dec].
Explanation System Health inband failing.
Error Message SYSTEMHEALTH-5-OHMS_NVRAM_FAILING: Nvram starting to fail on module

[dec].
Explanation System Health Nvram failing.
Error Message SYSTEMHEALTH-5-OHMS_SUP_CF_ERRORS_CLEARED: Compact flash failing

conditions on module [dec] has been cleared.
Explanation Compact flash might be dead on this module.
Error Message SYSTEMHEALTH-5-OHMS_TCAM_PARITY_CLEARED: Failing conditions for TCAM

on module [dec] have been cleared.
Explanation System Health TCAM failures cleared.
OL-26589-01 2-565
Error Message SYSTEMHEALTH-5-OHMS_TCAM_PARITY_FAILING: TCAM starting to fail on

module [dec].
Explanation System Health Tcam failing.
Error Message SYSTEMHEALTH-5-OHMS_TEST_FAILING: [chars] test starting to fail on

module [dec].
Explanation System Health test failing.
SYSTEMHEALTH-6
Error Message SYSTEMHEALTH-6-OHMS_ASIC_FAILURE_INFO: Module [dec] Asic [chars]

instance [dec] probable cause of failure.
Explanation HW failure analysis findings.
Error Message SYSTEMHEALTH-6-OHMS_BATTERY_CLEARED: Failing conditions for battery

[dec] on module [dec] have been cleared.
Explanation System Health battery failure cleared.
Error Message SYSTEMHEALTH-6-OHMS_BOOTFLASH_CLEARED: Failing conditions for

bootflash on module [dec] have been cleared.
Explanation System Health bootflash failures cleared.
Error Message SYSTEMHEALTH-6-OHMS_CDISK_CLEARED: Failing conditions for cache disk

[dec] on module [dec] have been cleared.
Explanation System Health cache disk failure cleared.
2-566 OL-26589-01
Error Message SYSTEMHEALTH-6-OHMS_EMGMT_CLEARED: Failing conditions for management

port on module [dec] have been cleared.
Explanation System Health emgmt failure cleared.
Error Message SYSTEMHEALTH-6-OHMS_EOBC_CLEARED: Failing conditions for EOBC on

module [dec] have been cleared.
Explanation System Health eobc failures cleared.
Error Message SYSTEMHEALTH-6-OHMS_FAILURE_CLEARED: Failing conditions for test

[chars] have been cleared on module [dec].
Explanation System Health failure cleared.
Error Message SYSTEMHEALTH-6-OHMS_INBAND_CLEARED: Failing conditions for inband on

Explanation System Health inband failures cleared.
Error Message SYSTEMHEALTH-6-OHMS_INBAND_DROP: Inband Dropping frames from module

[dec] due to unknown reasons.
Explanation System Health Inband non-timeout drop.
Error Message SYSTEMHEALTH-6-OHMS_INBAND_TO_ERR: Inband Dropping frames from

module [dec] due to timeout errors.
Explanation System Health Inband timeout drop.
Error Message SYSTEMHEALTH-6-OHMS_INBAND_TX_CONGESTION: Inband Unable to transmit

due to TX path congestion on module [dec].
Explanation System Health Inband TX congestion.
OL-26589-01 2-567
Error Message SYSTEMHEALTH-6-OHMS_NVRAM_CLEARED: Failing conditions for Nvram on

Explanation System Health Nvram failures cleared.
Error Message SYSTEMHEALTH-6-OHMS_STARTED: Online System Health started.
Explanation Online System Health started.
TACACS Messages
This section contains the TACACS messages.
TACACS-2
Error Message TACACS-2-TACACS_PROGRAM_EXIT: TACACS+ daemon exiting: [chars]
Explanation TACACS+ daemon is exiting.
TACACS-3
Error Message TACACS-3-TACACS_ERROR_MESSAGE: [chars]
Explanation TACACS+ Error Message
TACACS-4
Error Message TACACS-4-TACACS_WARNING: [chars]
Explanation TACACS+ warning
2-568 OL-26589-01
TACACS-5
Error Message TACACS-5-TACACS_MONITOR_STATUS: [chars] [chars]
Explanation Notifying Tacacs+ server monitor status change
Error Message TACACS-5-TACACS_NOTIFICATION: [chars]
Explanation TACACS+ notification
Error Message TACACS-5-TACACS_SERVER_STATUS: [chars] server [chars] with auth-port

[dec] and acct-port [dec] status has changed from [chars] to [chars]. Server was
in previous-state for [chars], and total dead time of the server is [chars]
Explanation Notifying Tacacs+ server status change
TACACS-6
Error Message TACACS-6-TACACS_ACCOUNTING_MESSAGE: [chars]
Error Message TACACS-6-TACACS_MESSAGE: [chars]
Explanation TACACS+ Message
TBIRD_CMN_USD Messages
This section contains the TBIRD_CMN_USD messages.
OL-26589-01 2-569
TBIRD_CMN_USD-6
Error Message TBIRD_CMN_USD-6-TBIRD_CMN_DEBUG_MSG: [chars]
TBIRD_FWD_USD Messages
This section contains the TBIRD_FWD_USD messages.
TBIRD_FWD_USD-6
Error Message TBIRD_FWD_USD-6-TBIRD_FWD_DEBUG_MSG: [chars]
TBIRD_MAC_USD Messages
This section contains the TBIRD_MAC_USD messages.
TBIRD_MAC_USD-3
Error Message TBIRD_MAC_USD-3-FCMAC_ERR_MSG: [chars]
Explanation Error log message
TBIRD_MAC_USD-6
Error Message TBIRD_MAC_USD-6-FCMAC_DEBUG_MSG: [chars]
TBIRD_QUE_USD Messages
This section contains the TBIRD_QUE_USD messages.
2-570 OL-26589-01
TBIRD_QUE_USD-6
Error Message TBIRD_QUE_USD-6-TBIRD_QUE_DEBUG_MSG: [chars]
TBIRD_XBAR_USD Messages
This section contains the TBIRD_XBAR_USD messages.
TBIRD_XBAR_USD-6
Error Message TBIRD_XBAR_USD-6-TBIRD_XBAR_DEBUG_MSG: [chars]
TCAP Messages
This section contains the TCAP messages.
TCAP-2
Error Message TCAP-2-MEM_FULL: Memory allocation failed.
Explanation TCAP process has failed to allocate memory.
Recommended Action Please perform a showtcapevent-history'tocollectmoreinformation.'
Error Message TCAP-2-PROC_DN: Process is shutting down: [chars]
Explanation TCAP process is exiting.
Error Message TCAP-2-PROC_INITFAIL: Process initialization failed due to [chars].
Explanation TCAP process has failed initialization.
OL-26589-01 2-571
TPC Messages
This section contains the TPC messages.
TPC-SLOT#-5
Error Message TPC-SLOT#-5-LOG_ERR_TPC_DPP_DEAD: VSAN :[dec] VT pWWN :[chars] DPP

died
Explanation The DPP associated with the Virtual Target has crashed
Error Message TPC-SLOT#-5-LOG_ERR_TPC_VT_ACT_FAILED: VSAN :[dec] VT pWWN :[chars]

VT Activate failed
Explanation The activate step for a Virtual Target has failed
Error Message TPC-SLOT#-5-LOG_ERR_TPC_VT_CREATE_FAIL: VSAN :[dec] VT pWWN :[chars]

VT and NPort creation FAILED !!!
Explanation The Virtual Target and nport creation failed
Error Message TPC-SLOT#-5-LOG_ERR_TPC_VT_DESTROYED: VSAN :[dec] Virtual Target :

[chars] Deleted
Explanation The Virtual Target in the associated VSAN is being destroyed
Error Message TPC-SLOT#-5-LOG_ERR_TPC_VT_VSAN_DOWN: VSAN :[dec] VT pWWN :[chars]

VSAN down
Explanation The VSAN where the Virtual Target is configured is down
TTYD Messages
This section contains the TTYD messages.
2-572 OL-26589-01
TTYD-2
Error Message TTYD-2-TTYD_ERROR: TTYD Error [chars]
Explanation Critical TTY daemon error.
Error Message TTYD-2-TTYD_MTS: TTYD Message queue [dec] [chars]
Explanation TTY daemon message error.
Error Message TTYD-2-TTYD_SDWRAP: TTYD Debug Facility error [dec] [chars]
Explanation TTY daemon Debug Facility failed.
TTYD-3
Error Message TTYD-3-TTYD_MISC_ERROR: Error [chars] with error [chars]([hex])
Explanation TTY daemon errors.
TTYD-6
Error Message TTYD-6-TTYD_MISC: TTYD [chars]
Explanation The tty daemon miscellaneous message.
Error Message TTYD-6-TTYD_PSS: TTYD Store error:[hex] [chars]
Explanation Failed to store configuration for TTY service.
TUNNEL Messages
This section contains the TUNNEL messages.
OL-26589-01 2-573
TUNNEL-2
Error Message TUNNEL-2-FEATURE_ENABLE_FAILED: failed to enable feature tunnel,

reason [chars] ([hex])
Explanation Failed to enable feature tunnel, reason [char] ([int])
Recommended Action Check the failure reason and take appropriate action to fix the failure. if unable
to fix, please capture "show tech-support tunnel"
Error Message TUNNEL-2-TM_F2_ONLY_VDC: Tunnel feature is not supported in F2 only VDC
Explanation Tunnel feature is not supported in F2 only VDC
Error Message Disable the Tunnel feature by the CLI "no feature tunnel"
TUNNEL-3
Error Message TUNNEL-3-HW_PROGRAMMING_FAILED: for [chars], reason [chars]
Explanation Hardware programming failed for tunnel [num] interface
Recommended Action Try

shutdown'and'noshutdown'undertunnelinterfacesubmodeaftersometime.ifstilltunnelinterfacedoesn't
comeupcaptureshowtech-supporttunneltoidentifytheissue'
TUNNEL-4
Error Message TUNNEL-4-TM_DF_PROGRAMMING_FAILED: [chars] DF(dont fragment)

programming failed! status [hex]
Explanation [chars] DF programming failed! status [int]
Recommended Action Capture "show tech-support tunnel " to identify why df flag programing failed
Error Message TUNNEL-4-TM_DF_PROGRAMMING: Programming [chars] DF(dont fragment)

df.sel [dec] df.val [dec]
Explanation Programming [chars] DF df.sel [int] df.val [int]
2-574 OL-26589-01
Error Message TUNNEL-4-TM_MTU_PROGRAMMING_FAILED: [chars] mtu [dec] programming

failed! status [hex]
Explanation [chars] mtu [int] programming failed! status [int]
Recommended Action Capture show "tech-support tunnel" to identify why MTU programming as
failed. tunnel interface will used default mtu value
Error Message TUNNEL-4-TM_MTU_PROGRAMMING: Programming [chars] mtu [dec]...
Explanation Programming [chars] mtu [int]
TUNNEL-5
Error Message TUNNEL-5-IF_CLEAR_COUNTER: Interface [chars] counters is cleared
Explanation Interface [char] counters is cleared
Error Message TUNNEL-5-IF_CREATED: Interface [chars] is created
Explanation Interface [char] is created
Error Message TUNNEL-5-IF_CREATE_FAILED: Interface [chars] creation failed due to

[[hex]] [chars]
Explanation Interface [char] is creation failed due to [int] [char]
Error Message TUNNEL-5-IF_DELETED: Interface [chars] is deleted
Explanation Interface [char] is deleted
Error Message TUNNEL-5-IF_STATE_UPDATE: Interface [chars] is [chars] reason

[chars]
Explanation Interface [char] is [char] reason [char]
OL-26589-01 2-575
Error Message TUNNEL-5-PPF_SESSION_FAILED: session id %llx type [chars] for [chars]

failed error [hex] [chars]
Explanation Session id [int] type [char] for [char] failed error [int] [char]
Error Message TUNNEL-5-TM_DISABLED: Tunnel Disabled
Explanation Tunnel Service Disabled
Error Message TUNNEL-5-TM_ENABLED: Tunnel Enabled
Explanation Tunnel Service Enabled
TUNNEL-7
Error Message TUNNEL-7-TM_INFO: [chars]
Explanation Tunnel Service info
U2RIB Messages
This section contains the U2RIB messages.
U2RIB-2
Error Message U2RIB-2-IPC_PROCESSING_ERR: Error in processing IPC message : Opcode

= [dec], Error code = [hex]
Explanation U2RIB encountered an error in processing an MTS message. The error and message are
specified in the error message
Error Message U2RIB-2-U2RIB_INIT: U2RIB initialization of [chars] [chars]
Explanation U2RIB initialization failed
2-576 OL-26589-01
U2RIB-3
Error Message U2RIB-3-U2RIB_LD_BLNCE_ERROR: Error in config. lb parameters using

the DCEFIB Library, error code = [hex], [chars]
Explanation Error while communicating with the dcefib library
U2RIB-5
Error Message U2RIB-5-U2RIB_DISABLED: U2RIB Disabled
Explanation U2RIB Service Disabled
Error Message U2RIB-5-U2RIB_ENABLED: U2RIB Enabled
Explanation U2RIB Service enabled
U2RIB-6
Error Message U2RIB-6-STATE_CREATED: Internal state created [chars]
Explanation U2RIB has created its internal state stateless/stateful [chars].
UDLD Messages
This section contains the UDLD messages.
UDLD-3
Error Message UDLD-3-IDB_ERROR: UDLD error handling [chars] interface: [chars]
Explanation A softare error occurred in UDLD processing associated with a specific interface.
Recommended Action LOG_STD_SH_TECH_ACTION
OL-26589-01 2-577
Error Message UDLD-3-MSG_SEND_FAILURE: failed to send [chars] to sap [dec]: [chars]
Error Message UDLD-3-UDLD_INTERNAL_ERROR: UDLD internal error: [chars]
Explanation A softare sanity check failed in the course of UDLD processing.
Error Message UDLD-3-UDLD_INTERNAL_IF_ERROR: UDLD internal error, interface

[chars]: [chars]
Explanation A softare sanity check failed in the course of UDLD processing.
UDLD-4
Error Message UDLD-4-UDLD_GWRAP_COUNT: UDLD gwrap count is %lu, please log a 'show
tech udld' for detail info.
Explanation UDLD gwrap count reached high level, show tech udld is needed to debug it.
Error Message UDLD-4-UDLD_NEIGHBOR_MISMATCH: UDLD neighbor mismatch detected, exp:

[chars], rec [chars]. Please collect debug info using:
http://zed.cisco.com/confluence/display/KGP/UDLD+debug
Explanation An interface will be disabled because UDLD protocol detected a nieghbor mismatch
condition on the interface indicated. Cause is likely due to bad interface hardware or cable
misconfiguration. User should investigate.
Error Message UDLD-4-UDLD_PORT_DISABLED: Interface [chars], link error detected:

[chars]. Please collect debug info using:
http://zed.cisco.com/confluence/display/KGP/UDLD+debug
Explanation An interface was disabled because UDLD protocol detected the cause on the interface
indicated. Cause is likely due to bad interface hardware or cable misconfiguration. User should
investigate.
2-578 OL-26589-01
Error Message UDLD-4-UDLD_PORT_RESET: UDLD reset interface [chars]
Explanation A port which had been disabled for UDLD has been reset.
UDLD-5
Error Message UDLD-5-UDLD_AGGRESSIVE: UDLD Aggressive
Explanation UDLD Service Aggressive
Error Message UDLD-5-UDLD_DISABLED: UDLD Disabled
Explanation UDLD Service Disabled
Error Message UDLD-5-UDLD_ENABLED: UDLD Enabled
Explanation UDLD Service Enabled
UFDM Messages
This section contains the UFDM messages.
UFDM-2
Error Message UFDM-2-DNLD_TIMEDOUT: Download timer expired: [chars]
Explanation UFDM download timer expired. Collect show tech-support forwarding l3 unicast for
futher analysis.
Error Message UFDM-2-FIB_ROUTE_UPDATE_ERR: Route update error from slot [dec] FIB
Explanation FIB returned route update error. Collect show tech-support forwarding l3 unicast for
futher analysis.
OL-26589-01 2-579
Error Message UFDM-2-INTERNAL_ERROR: Internal error: [chars], collect output of

show tech-support fowarding l3 unicast... command
Explanation UFDM hit a internal error. Collect show tech-support forwarding l3 unicast for futher
analysis.
VDC_MGR Messages
This section contains the VDC_MGR messages.
VDC_MGR-2
Error Message VDC_MGR-2-VDC_CRITICAL: vdc_mgr has hit a critical error: [chars]
Explanation Vdc_mgr has hit a critical error
Recommended Action A critical error has been hit within vdc_mgr. Please check show vdc to
determine the state of the vdcs
Error Message VDC_MGR-2-VDC_LIC_WARN_EXP: WARNING License for vdcs is about to

expire! VDCs will be deleted if license is allowed to expire
Explanation VDC license is close to expire
Recommended Action Please contact your sales representative to obtain a license
Error Message VDC_MGR-2-VDC_LIC_WARN: Service using grace period will be shutdown

in [dec] day(s)
Explanation The license for vdcs is not installed and currently running in the grace period
Recommended Action Vdcs will continue to work within the grace period, but obtaining a license is
reccomended
Error Message VDC_MGR-2-VDC_OFFLINE: vdc [dec] is now offline
Explanation The vdc has been shut down. Either it has been deleted or has just completed ungraceful
cleanup
Recommended Action If the vdc was deleted, no action is necessary. Otherwise vdc_mgr may attempt
to recreate it according to the ha-policy that has been set
2-580 OL-26589-01
Error Message VDC_MGR-2-VDC_ONLINE: vdc [dec] has come online
Explanation Vdc_mgr has finished creating a vdc and it is ready to use
Error Message VDC_MGR-2-VDC_UNALLOCATED: Module [dec] is unsupported by the current

vdc and some of its ports have been placed in the unallocated pool.
Explanation The module is of a type unsupported by the current vdc. You can see port membership
by 'show vdc membership' and check the current vdc's configuration via 'show vdc'
Recommended Action Allocate interfaces to a vdc that supports this module type or change the
current vdc to support this module type via the 'limit-resource module-type' command
Error Message VDC_MGR-2-VDC_UNGRACEFUL: vdc_mgr: Ungraceful cleanup request

recieved for vdc [dec], restart count for this vdc is [dec] restarts within the
last 5 minutes
Explanation Vdc_mgr has begun ungraceful cleanup for a vdc
Recommended Action There has been a failure within the vdc and vdc_mgr has begun the cleanup
process. Use show vdc to determine its state
VDC_MGR-3
Error Message VDC_MGR-3-VDC_ERROR: vdc_mgr: [chars]
Explanation Vdc_mgr has recieved bad data but will try to continue
Recommended Action Vdc_mgr will attempt to correct the error at hand
VDC_MGR-5
Error Message VDC_MGR-5-VDC_FEATURESET_ALLOW: vdc_mgr: Feature-set [chars] can now

be used in this vdc
Explanation Allowed feature-set config has changed
Error Message VDC_MGR-5-VDC_FEATURESET_DISALLOW: vdc_mgr: Feature-set [chars] is

now disallowed in this vdc
Explanation Allowed feature-set config has changed
OL-26589-01 2-581
Error Message VDC_MGR-5-VDC_HOSTNAME_CHANGE: vdc [dec] hostname changed to [chars]
Explanation Host name for a vdc has changed.
Error Message VDC_MGR-5-VDC_MEMBERSHIP_ADD: vdc_mgr: Interface [chars] has been

added to this vdc
Explanation A new interface has been added to this vdc
Error Message VDC_MGR-5-VDC_MEMBERSHIP_DELETE: vdc_mgr: Interface [chars] has been

removed from this vdc
Explanation A new interface has been removed from this vdc
Error Message VDC_MGR-5-VDC_MODULETYPE: vdc_mgr: Module type changed to [chars]
Explanation This vdc has been changed to support only the the type of modules listed
Error Message VDC_MGR-5-VDC_STATE_CHANGE: vdc [dec] state changed to [chars]
Explanation A vdc state change has happened. This is most likely due to a configuration change.
Error Message VDC_MGR-5-VDC_SWMODULETYPE: vdc_mgr: System Module type changed to

[chars]
Explanation This switch has been changed to support only the the type of modules listed
VEC Messages
This section contains the VEC messages.
2-582 OL-26589-01
VEC-SLOT#-3
Error Message VEC-SLOT#-3-LOG_DPP_EXCEPTION: DPP Exception DPP [dec]
Recommended Action Vec
Error Message VEC-SLOT#-3-LOG_GUID_MISMATCH: GUID Mismatch DPP [dec] PWWN [chars]

lun [chars] Expected [chars] Read [chars]
Explanation The disk GUID verification performed by the DPP failed. Access to the disk is denied.
VEC-SLOT#-4
Error Message VEC-SLOT#-4-LOG_DPP_REBOOTED: DPP [dec] Rebooted
VEC-SLOT#-5
Error Message VEC-SLOT#-5-LOG_ERR_VEC_DISK: SCSI STATUS([hex]) [chars]

SENSE_KEY([hex]) [chars] ASC([hex]) ASCQ([hex]) [chars]
Error Message VEC-SLOT#-5-LOG_ERR_VEC_DPP_MON_FSM: Illegal Event [chars] in State

[chars] FSM [chars]
Explanation An Event is received for a State in the VEC DPP Monitor FSM which should not have
occured
Error Message VEC-SLOT#-5-LOG_ERR_VEC_DPRLI_FSM: Illegal Event [chars] in State

[chars] FSM [chars]
Explanation An Event is received for a State in the VEC DPRLI FSM which should not have occured
OL-26589-01 2-583
Error Message VEC-SLOT#-5-LOG_ERR_VEC_GID_FSM: Illegal Event [chars] in State

[chars] FSM [chars]
Explanation An Event is received for a State in the VEC Guid ID FSM which should not have
occured
Error Message VEC-SLOT#-5-LOG_ERR_VEC_HOST_LMAP_FSM: Illegal Event [chars] in

State [chars] Host VSAN :[dec] Host pWWN :[chars] VEP pWWN :[chars]
Explanation An Event is received for a State in the VEC HOST LMAP XP FSM which should not
have occured
Error Message VEC-SLOT#-5-LOG_ERR_VEC_HOST_LOGO: Logging out Host [VSAN :[dec]

pWWN :[chars]] logged in to VEP [pWWN :[chars]]. Reason : Host not responding
Explanation The Host HBA is logged out from the VEP as it is not responding to ADISCs initiated
from the VEP
Error Message VEC-SLOT#-5-LOG_ERR_VEC_HOST_XP_FSM: Illegal Event [chars] in State

[chars] Host VSAN :[dec] Host pWWN :[chars] VEP pWWN :[chars]
Explanation An Event is received for a State in the VEC HOST XP FSM which should not have
occured
Error Message VEC-SLOT#-5-LOG_ERR_VEC_HOST: Host VSAN :[dec] Host pWWN :[chars]

access denied to VEP pWWN :[chars] due to licensing
Explanation The Host HBA is denied access to the VEP due to licensing
Error Message VEC-SLOT#-5-LOG_ERR_VEC_NPORT_FSM: Illegal Event [chars] in State

[chars] FSM [chars]
Explanation An Event is received for a State in the VEC NPORT FSM which should not have
occured
2-584 OL-26589-01
Error Message VEC-SLOT#-5-LOG_ERR_VEC_PID_FSM: Illegal Event [chars] in State

[chars] FSM [chars]
Explanation An Event is received for a State in the VEC PID FSM which should not have occured
Error Message VEC-SLOT#-5-LOG_ERR_VEC_TARGET_FSM: Illegal Event [chars] in State

[chars] FSM [chars]
Explanation An Event is received for a State in the VEC TARGET FSM which should not have
occured
Error Message VEC-SLOT#-5-LOG_ERR_VEC_TCAM_MON_FSM: Illegal Event [chars] in State

[chars] DPP :[dec]
Explanation An Event is received for a State in the VEC TCAM MON FSM which should not have
occured
Error Message VEC-SLOT#-5-LOG_ERR_VEC_TP_FSM: Illegal Event [chars] in State

[chars] Host VSAN :[dec] TP nWWN :[chars] TP pWWN :[chars]
Explanation An Event is received for a State in the VEC TP FSM which should not have occured
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VEP_FSM: Illegal Event [chars] in State

[chars] Host VSAN :[dec] VEP nWWN :[chars] VEP pWWN :[chars]
Explanation An Event is received for a State in the VEC VEP FSM which should not have occured
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VEP_ILC_LIMIT: VEP [VSAN :[dec] pWWN

:[chars]] could not be created. Reason : ILC VEP limit [dec] reached
Explanation The VEP could not be created as the per ILC limit of VEPs has been reached
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VLUN_FSM: Illegal Event [chars] in State

[chars] FSM [chars]
Explanation An Event is received for a State in the VEC VLUN FSM which should not have occured
OL-26589-01 2-585
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VO_FSM: Illegal Event [chars] in State

[chars] FSM [chars]
Explanation An Event is received for a State in the VEC VO FSM which should not have occured
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VSAN_FSM: Illegal Event [chars] in State

[chars] VSAN [dec]
Explanation An Event is received for a State in the VEC VSAN FSM which should not have occured
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VSAN_XCHG_FSM: Illegal Event [chars] in

State [chars] VES IP Addr [chars]
Explanation An Event is received for a State in the VEC VSAN XCHG FSM which should not have
occured
Error Message VEC-SLOT#-5-LOG_NOTICE_VEC_SLEEP_THRESH: VEC not scheduled for [dec]

seconds
Explanation The VEC process sleep threshold was exceeded which should not have occured.
Recovery will be preformed if appropriate.
Error Message VEC-SLOT#-5-LOG_NOTICE_VEC_WORK_THRESH: VEC did not yeild the cpu

for [dec] seconds
Explanation The VEC process work threshold was exceeded which should not have occured.
VEDB_MGR Messages
This section contains the VEDB_MGR messages.
2-586 OL-26589-01
VEDB_MGR-2
Error Message VEDB_MGR-2-MALLOC_ERROR: Size [dec] bytes
Explanation The VEDB library could not allocate memory.
VEDB_MGR-6
Error Message VEDB_MGR-6-EXITING: Exited due to [chars]
Explanation The VEDB library has exited due to [char]. The process has probably been restarted
automatically.
Error Message VEDB_MGR-6-SERVICE_UP: Initialized [chars]
Explanation The VEDB library is up and ready to accept client requests The service was initialized
in [char] mode.
VES Messages
This section contains the VES messages.
VES-SLOT#-4
Error Message VES-SLOT#-4-LOG_WARNING_VES_CONFIG_TOO_BIG: Volume [chars]

configuration too large to virtualize
Explanation The VES maximum volume configuration was exceeded. Volume will be virtualized by
the cpp.
OL-26589-01 2-587
VES-SLOT#-5
Error Message VES-SLOT#-5-LOG_ERR_VES_PATH_FSM: disk guids dont match - received

verify_mismatch for pid [dec] from vec [dec]
Explanation An VERIFY MISMATCH Event is received for a State in the VES PATH FSM which
should not have occured
Error Message VES-SLOT#-5-LOG_ERR_VES_VEP_FSM: Illegal Event [chars] in State

[chars] Host VSAN :[dec] VEP pWWN :[chars]
Explanation An Event is received for a State in the VES VEP FSM which should not have occured
Error Message VES-SLOT#-5-LOG_ERR_VES_VSAN_FSM: Illegal Event [chars] in State

[chars] VSAN [dec]
Explanation An Event is received for a State in the VES VSAN FSM which should not have occured
Error Message VES-SLOT#-5-LOG_ERR_VES_VSAN_XCHG_FSM: Illegal Event [chars] in

State [chars] VEC IP Addr [chars]
Explanation An Event is received for a State in the VES VSAN XCHG FSM which should not have
occured
Error Message VES-SLOT#-5-LOG_NOTICE_VES_SLEEP_THRESH: VES not scheduled for [dec]

seconds
ExplanationThe VES process sleep threshold was exceeded which should not have occured.
Error Message VES-SLOT#-5-LOG_NOTICE_VES_WORK_THRESH: VES did not yeild the cpu

for [dec] seconds
Explanation The VES process work threshold was exceeded which should not have occured.
2-588 OL-26589-01
VFC Messages
This section contains the VFC messages.
VFC-3
Error Message VFC-3-VFC_MEM_ERROR: Memory consistency problem
Explanation Miscellaneous target error
Error Message VFC-3-VFC_TGT_ERROR: Target error:[chars] 0x%llx
Explanation Miscellaneous target error
VFC-6
Error Message VFC-6-STARTING: deamon started
Explanation The VFC daemon successfully started
VLAN_MGR Messages
This section contains the VLAN_MGR messages.
VLAN_MGR-2
Error Message VLAN_MGR-2-CRITICAL_MSG: [chars]
Explanation VLAN Manager Critical Message
VLAN_MGR-3
Error Message VLAN_MGR-3-ERROR_MSG: [chars]
Explanation VLAN manager error
OL-26589-01 2-589
VLAN_MGR-4
Error Message VLAN_MGR-4-WARN_MSG: [chars]
Explanation VLAN manager warning
VLAN_MGR-5
Error Message VLAN_MGR-5-NOTIF_MSG: [chars]
Explanation VLAN Manager Notification Message
Error Message VLAN_MGR-5-RESERVED_VLAN_RANGE_CHANGED: New Reserved VLAN Range

Configured From VLAN [dec] to VLAN [dec]
Explanation VLAN Manager Reserved VLAN Reconfiguration Message
VLAN_MGR-6
Error Message VLAN_MGR-6-INFO_MSG: [chars]
Explanation VLAN manager info
Error Message VLAN_MGR-6-VLAN_CREATED: VLAN [dec], created
Explanation VLAN created
Error Message VLAN_MGR-6-VLAN_MGR_STATEFULL_RESTART: VLAN Manager statefull

restart
Explanation VLAN Manager statefull restart
2-590 OL-26589-01
Error Message VLAN_MGR-6-VLAN_MGR_STATELESS_RESTART: VLAN Manager stateless

restart
Explanation VLAN Manager stateless restart
Error Message VLAN_MGR-6-VLAN_OPER_STATUS_CHG: VLAN [dec], status changed to

[chars]
Explanation VLAN operational state change
VNI Messages
This section contains the VNI messages.
VNI-2
Error Message VNI-2-ALLOC_MEMORY: Memory allocation failed
VNI-3
Error Message VNI-3-INIT_FAILED: Initialization failed. Component [chars]
[chars].
component.
VNI-6
Error Message VNI-6-INTERFACE_EVENT: VSAN interface [chars] [chars]
Explanation The specified VSAN Interface has been successfully [chars].
OL-26589-01 2-591
Error Message VNI-6-STARTING: Virtual Network Interface Manager started
Error Message VNI-6-VSAN_DELETED: VSAN [dec] has been deleted
Explanation The specified VSAN has been deleted. The service will delete all the configuration on
that VSAN.
VPC Messages
This section contains the VPC messages.
VPC-2
Error Message VPC-2-PEER_KEEP_ALIVE_RECV_FAIL: In domain [dec], VPC peer

keep-alive receive has failed
Explanation Peer keep-alive receive failed
Error Message VPC-2-PEER_KEEP_ALIVE_SEND_FAIL: In domain [dec], VPC peer

keep-alive send has failed
Explanation Peer keep-alive send failed
Error Message VPC-2-PEER_VPC_RESP_TIMEDOUT: Failed to receive response from peer

for vPC: [dec]
Explanation VPC bringup failed
Error Message VPC-2-TRACK_INTFS_DOWN: In domain [dec], vPC tracked interfaces down,

suspending all vPCs and keep-alive
Explanation VPC tracked object down
2-592 OL-26589-01
Error Message VPC-2-VPC_ADD_L3_BKUP_VLAN_TO_PEER_GW_EXCLUDE_LIST: Exclude L3 backup

routing VLAN from vpc peer-gateway config.
Explanation Triggered when peer-link is F1 and peer-gateway is configured without exclude-vlan

list.
Error Message VPC-2-VPC_CORE_PORT_FPATH_BUP_FAILED: Failed to bring up vPC+ peer

link port [chars] in Fabric Path Port Mode - vPC+ Fabric Path switch ID not
configured
Explanation VPC+ Failed to bringup peer-link - switch-ID not configured
Error Message VPC-2-VPC_ES_FAILED_LID_ALLOC: Failed to negotiate common LID

between vPC peers.
Explanation Failed to find common lid.
Error Message VPC-2-VPC_ES_FAILED_PEERLINK_DOWN: vPC+ operations failed. Bringing

down peer-link.
Explanation Triggered in mcecm_em_es_failed. Bring down peer-link.
Error Message VPC-2-VPC_ES_PEER_LINK_OPERATION_FAILED: Peer-link operation failed

due to SAP [dec].
Explanation Triggered in mcecm_cfg_es_failed when peer-link bringup fails.
Error Message VPC-2-VPC_GRACEFUL_SUSP_ALL_VPC: Operational graceful type-1 check

configuration changed, reiniting all vPCs
Explanation Graceful configuration change,reinit vPCs
Error Message VPC-2-VPC_ISSU_END: Peer vPC switch ISSU end, unlocking configuration
Explanation Peer vPC switch issu end
OL-26589-01 2-593
Error Message VPC-2-VPC_ISSU_START: Peer vPC switch ISSU start, locking

configuration
Explanation Peer vPC switch issu start
Error Message VPC-2-VPC_LC_FAIL: LC [dec] does not support required hardware for
vPC; run showvdcmembershipstatus'forportstatus'
Explanation Lc insertion failed
Error Message VPC-2-VPC_NON_DEF_LID: vPC+ negotiated non-default local id.

Flapping orphan edge ports recommended.
Explanation Triggered in mcecm_em_es_failed. Bring down peer-link.
Error Message VPC-2-VPC_PEER_LINK_FPATH_BUP_FAILED: Failed to bring up vPC+ peer

link port [chars] - port [chars] is not configured as a Fabric Path port
Explanation VPC+ Failed to bringup Peer-link - not in Fabric Path mode
Error Message VPC-2-VPC_PSS_ERROR: [chars], 0x([hex]) present in VPC DB but not is

IM DB
Explanation Triggered when vpc DB and IM SDB are inconsistent
Error Message VPC-2-VPC_SUSP_ALL_VPC: Peer-link going down, suspending all vPCs on

secondary
Explanation Peer link down suspend vPCs
Error Message VPC-2-VPC_SVI_EXCLUDE: vPC [dec] has up vlans [chars] which are
excluded from suspension on dual-active
Explanation VPC track object deconfigured
2-594 OL-26589-01
VPC-3
Error Message VPC-3-GLOBAL_CONSISTENCY_FAILED: In domain [dec], global

configuration is not consistent ([chars])
Explanation Global compat-check failed
Error Message VPC-3-INTF_CONSISTENCY_FAILED: In domain [dec], VPC [dec]

configuration is not consistent ([chars])
Explanation MCEC compat-check failed
Error Message VPC-3-PEER_UNREACHABLE: Remote Switch Unreachable
Explanation Peer unreachable
Error Message VPC-3-PEER_VPC_BRINGUP_FAILED: Peer vPC [dec] bringup failed

([chars])
Explanation Peer vPC bringup failed
Error Message VPC-3-VPCM_ASSERTION_FAILED: [chars]
Explanation VPCM has hit an assert condition at file [chars]
Error Message VPC-3-VPCM_INIT_FAIL: vPC Manager Initialization Failed ([chars])
Explanation VPCM Initialization failed. due to [chars]
Error Message VPC-3-VPCM_INTERNAL_ERR: [chars]
Explanation VPCM encountered an internal error due to [chars]
OL-26589-01 2-595
Error Message VPC-3-VPCM_MTS_ERR: [chars]
Explanation VPCM encountered an MTS error due to [chars]
Error Message VPC-3-VPC_BRINGUP_FAILED: vPC [dec] bringup failed ([chars])
Explanation VPC bringup failed
Error Message VPC-3-VPC_PEER_LINK_BRINGUP_FAILED: vPC peer-link bringup failed

([chars])
Explanation VPC Peer-link bringup failed
Error Message VPC-3-VPC_PEER_LINK_DOWN: VPC Peer-link is down
Explanation VPC Peer link is down
VPC-4
Error Message VPC-4-PEER_VPC_DELETED: Peer vPC [dec] deleted
Explanation Peer vPC configuration deleted
Error Message VPC-4-VPC_CONSISTENCY_NEW_VLAN_FAIL: Global Consistency check for vPC

failed for new vlans
Explanation Global Consistency check for vPC failed for new vlans
Error Message VPC-4-VPC_DELETED: vPC [dec] is deleted
Explanation VPC configuration deleted
2-596 OL-26589-01
Error Message VPC-4-VPC_DISABLE_IP_REDIRECTS: peer-gateway enabled. Disabling IP

redirects on all interface-vlans of this vPC domain for correct operation of this
feature.
Explanation Peer-gateway enabled, hence IP redirects on SVIs are disabled
Error Message VPC-4-VPC_LC_UPG_OVER_DELIVERY_FAIL: Failed to deliver LC upgrade to

vPC peer
Explanation Failed to deliver LC upgrade to peer
Error Message VPC-4-VPC_PEER_LINK_DELETED: vPC Peer-link deleted. This will

bringdown all vPC interfaces
Explanation VPC Peer-link configuration removed
Error Message VPC-4-VPC_PEER_ROLE_CHANGE: In domain [dec], VPC peer role status

has changed to [chars]
Explanation VPC Peer role status changed to (Primary/Secondary
Error Message VPC-4-VPC_PER_VLAN_NO_SUPPORT: image that does not support per-vlan

type-1 check will not bring down/up any vlan (i.e. nothing will happen) until next
compat-check.
Explanation Triggered when ISSU/ISSD to an image which does not support per-vlan compat-check
Error Message VPC-4-VPC_PER_VLAN_CONSISTENCY_FAILED: Global consistency check for

vPC failed for few vlans
Explanation Global Consistency check for vPC failed for few vlans
Error Message VPC-4-VPC_REINITIALIZED: Reinitializing vpcs assuming peer dead
Explanation Initializing vpcs assuming peer dead
OL-26589-01 2-597
Error Message VPC-4-VPC_ROLE_CHANGE: In domain [dec], VPC role status has changed
to [chars]
Explanation VPC role status changed to (Primary/Secondary
VPC-5
Error Message VPC-5-GLOBAL_CONSISTENCY_SUCCESS: In domain [dec], global

configuration is consistent
Explanation Global compat-check passed
Error Message VPC-5-INTF_CONSISTENCY_SUCCESS: In domain [dec], vPC [dec]

configuration is consistent
Explanation VPC configuration is consistent
Error Message VPC-5-PEER_KEEP_ALIVE_RECV_INT_LATEST: In domain [dec], VPC

peer-keepalive received on interface [chars]
Explanation VPC peer-keepalive receive interface changed
Error Message VPC-5-PEER_KEEP_ALIVE_RECV_SUCCESS: In domain [dec], vPC peer

keep-alive receive is successful
Explanation Peer keep-alive receive successful
Error Message VPC-5-PEER_KEEP_ALIVE_SEND_INT_LATEST: In domain [dec], VPC

peer-keepalive sent on interface [chars]
Explanation VPC peer-keepalive send interface changed
2-598 OL-26589-01
Error Message VPC-5-PEER_KEEP_ALIVE_SEND_SUCCESS: In domain [dec], vPC peer

keep-alive send is successful
Explanation Peer keep-alive send successful
Error Message VPC-5-PEER_KEEP_ALIVE_STATUS: In domain [dec], peer keep-alive status

changed to [chars]
Explanation Peer keep-alive (oob) status is changed to <peer-alive
Recommended Action Peer-not-alive
Error Message VPC-5-ROLE_PRIORITY_CFGD: In domain [dec], vPC role priority changed

to [dec]
Explanation Role priority configured
Error Message VPC-5-SYSTEM_MAC_CFGD: In domain [dec], vPC system-mac changed to

[chars]
Explanation System mac configured
Error Message VPC-5-SYSTEM_PRIO_CFGD: In domain [dec], vPC system priority changed

to [dec]
Explanation System priority changed
Error Message VPC-5-VPCM_DISABLED: vPC Manager disabled
Explanation VPCM Service Disabled
Error Message VPC-5-VPCM_ENABLED: vPC Manager enabled
Explanation VPCM Service Enabled
OL-26589-01 2-599
Error Message VPC-5-VPC_DELAY_SVI_BUP_TIMER_EXPIRED: vPC restore, delay

interface-vlan bringup timer expired, reiniting interface-vlans
Explanation VPC delay interface-vlan restore timer expired
Error Message VPC-5-VPC_DELAY_SVI_BUP_TIMER_START: vPC restore, delay

interface-vlan bringup timer started
Explanation VPC delay interface-vlan restore timer start
Error Message VPC-5-VPC_DOWN: vPC [dec] is down ([chars])
Explanation VPC is down (reason)
Error Message VPC-5-VPC_PEER_LINK_UP: vPC Peer-link is up
Explanation VPC Peer-link is up
Error Message VPC-5-VPC_RESTORE_TIMER_EXPIRED: vPC restore timer expired, reiniting

vPCs
Explanation VPC restore timer expired
Error Message VPC-5-VPC_RESTORE_TIMER_START: vPC restore timer started to reinit

vPCs
Explanation VPC restore timer start
Error Message VPC-5-VPC_ROLE_PREMPT: In domain [dec], vPC role pre-emption

triggered
Explanation VPC preemption triggered
2-600 OL-26589-01
Error Message VPC-5-VPC_UP: vPC [dec] is up
Explanation MCEC is UP
VPC-6
Error Message VPC-6-PEER_LOCK_FAILED: Locking failed on peer switch - Aborting

upgrade!!
Explanation Locking failed on peer switch
Error Message VPC-6-PEER_VPC_CFGD_VLANS_CHANGED: Peer vPC [dec] configured vlans

changed
Explanation Remote MCEC configured vlans Changed
Error Message VPC-6-PEER_VPC_CFGD: peer vPC [dec] is configured
Explanation VPC is configured
Error Message VPC-6-PEER_VPC_DOWN: Peer vPC [dec] is down ([chars])
Explanation Peer vPC is down
Error Message VPC-6-PEER_VPC_UP: Peer vPC [dec] is up
Explanation Peer vPC is up
Error Message VPC-6-STATS_CLEARED: vPC Statistics Cleared
Explanation VPC statistics cleared
OL-26589-01 2-601
Error Message VPC-6-TRACK_OBJ_CONFIGURED: In domain [dec], track object configured

[dec]
Explanation VPC track object configured
Error Message VPC-6-TRACK_OBJ_DELETED: In domain [dec], track object deleted
Explanation VPC track object deconfigured
Error Message VPC-6-TYPE1_PARAM_CHANGED: TYPE-1 parameters changed: [chars]
Explanation Type-1 Parameters Changed
Error Message VPC-6-VPCM_INTERNAL_INFO: [chars]
Explanation VPCM got an internal info [chars]
Error Message VPC-6-VPC_ALLOWED_VLAN_CHANGED: vPC [dec] operational vlans changed
Explanation Operational vlans changed on vPC
Error Message VPC-6-VPC_CFGD: vPC [dec] is configured
Explanation VPC is configured
Error Message VPC-6-VPC_CONSISTENCY_CHECK_BYPASS: Bypassing consistency check for

vPC: [dec]
Explanation Bypassing consistency check for vpcs
2-602 OL-26589-01
Error Message VPC-6-VPC_CONSISTENCY_NEW_VLAN_PASS: Global Consistency check for vPC

passed for new vlans
Explanation Global Consistency check for vPC passed for new vlans
Error Message VPC-6-VPC_DOMAIN_ID_CFGD: vPC domain-id configured to [dec]
Explanation VPC domain-id configured
Error Message VPC-6-VPC_ES_EGRESS_DF_STATE_CHANGED: Egress designated forwarder

state changed from [chars] to [chars] for vPC [dec].
Explanation DF state changed for some vPC.
Error Message VPC-6-VPC_ES_ID_CFGD: Fabricpath switch ID [dec] configured
Explanation Fabricpath switch ID configured
Error Message VPC-6-VPC_ES_ID_REMOVED: Fabricpath switch ID [dec] removed
Explanation Fabricpath switch ID removed
Error Message VPC-6-VPC_PEER_LINK_CFGD: vPC peer-link is configured
Explanation VPC Peer-link is configured
Error Message VPC-6-VPC_PER_VLAN_CONSISTENCY_PASSED: Global Consistency check for

vPC passed for all vlans
Explanation Global Consistency check for vPC passed for all vlans
VPM Messages
This section contains the VPM messages.
OL-26589-01 2-603
VPM-2
Error Message VPM-2-GENERAL_ERROR: [chars]
Explanation The VP Manager has encountered an critical error. The description of error is [str.]
Error Message VPM-2-MALLOC_ERROR: Size [dec] bytes
Explanation The VP Manager could not allocate memory.
Error Message VPM-2-PSS_ERROR: [chars]
Explanation The VP Manager encountered error while operating on a persistent storage database.
Error Message VPM-2-VPMON_CRIT: [chars] [dec]
Explanation VPMON daemon critical message
Error Message VPM-2-VPMON_DPP_DOWNLOAD: HB failure, Restarting the DPP [dec]
Explanation VPMON daemon redownloading DPP(s)
Recommended Action ISAPI API users need to re-download config data to fast path
Error Message VPM-2-VPMON_DPP_RELOAD_FORCE: Force reload of DPP(s) [chars]:

[chars]
Explanation VPMON daemon critical action message
2-604 OL-26589-01
VPM-3
Error Message VPM-3-PSS_SYNC_TO_STNDBY_FAILED: PSS TYPE=[chars] KEY=[chars]
Explanation Could not send PSS Sync. notification to Standby Supervisor. PSS Type=[str.]
Operation=[.str] Key=[Str.]
Error Message VPM-3-SEND_TO_ILC_FAILED: [chars]
Explanation The VP Manager could not send to ILC for DG=[chars], at slot=[dec] processor=[dec]
and SAP=[dec].
Error Message VPM-3-SEND_TO_SNMP_AGENT_FAILED: [chars]
Explanation The VP Manager could not send to SNMP Agent for DG=[chars].
Error Message VPM-3-UNKNOWN_MSG: Recvd. from Node=[dec] SAP=[dec]
Explanation The VP Manager has received an unknown message from [dec]].[dec]. This
information is for debugging only.
Error Message VPM-3-VPM_PSS_CORRUPTED: [chars] PSS found corrupted
Explanation The VP Manager has detected corruption in one of its persistent information database.
VPM-4
Error Message VPM-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec]
Explanation There was a version mismatch between the VP Manager and one of its persistent
OL-26589-01 2-605
VPM-6
Error Message VPM-6-BECAME_ACTIVE: Became ACTIVE from standby mode
Explanation The VP Manager on the standby supervisor became active and it is ready to serve client
requests.
Error Message VPM-6-BECAME_STDBY: Became STANDBY from active mode
Explanation The VP Manager became standby from active mode.
Error Message VPM-6-DG_DEREGISTERED: [chars]
Explanation The VP Manager has deregistered DG [chars] at slot=[dec] processor=[dec] and

SAP=[dec].
Error Message VPM-6-DG_REGISTERED: [chars]
Explanation The VP Manager has registered DG [chars] from slot=[dec] processor=[dec] and
SAP=[dec].
Error Message VPM-6-EXITING: Exited due to [chars]
Explanation The VP Manager process has exited due to [char]. The process has probably been
Error Message VPM-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system

Explanation The VP Manager was unable to send heartbeat to the system manger
Error Message VPM-6-GENERAL_EVENT: [chars]
Explanation The VP Manager has generated an important event. The description of the event is [str.]
2-606 OL-26589-01
Error Message VPM-6-PSS_CREATED: [chars] PSS Created
Explanation One of the persistent information database of VP Manager has been recreated
Error Message VPM-6-PSS_DESTROYED: [chars] PSS Destroyed
Explanation One of the persistent information databases of Vp Manager has been intentionally
Error Message VPM-6-SERVICE_UP: Initialized [chars]
Explanation The VP Manager is up and ready to accept client requests The service was initialized
in [char] mode.
Error Message VPM-6-SWITCHOVER: Switching Over to other Sup.
Explanation The VP Manager has successfully switched over to the standby supervisor card.
Error Message VPM-6-VPMON_INFO: [chars]
Explanation VPMON daemon informational message
Error Message VPM-6-VPMON_STARTING: deamon started
Explanation The VPMON daemon successfully started
Error Message VPM-6-VPM_MDS_LICENSE_GRACE: MDS LICENSE in grace period for feature

: [chars]
Explanation MDS license is in grace period. Please retrieve a new MDS license
OL-26589-01 2-607
Error Message VPM-6-VPM_MDS_LICENSE_REVOKED: MDS LICENSE REVOKED for feature :

[chars]
Explanation MDS license is revoked. Please retrieve a new MDS license
Error Message VPM-6-VPM_MDS_TIMED_LICENSE: Timed MDS LICENSE for feature : [chars]
Explanation Timed MDS license
VPM-SLOT#-2
Error Message VPM-SLOT#-2-CPP_CATASTROPHIC_ERROR: ERROR: Component ([chars])

VRRP-CFG Messages
This section contains the VRRP-CFG messages.
VRRP-CFG-2
Error Message VRRP-CFG-2-ALLOC_MEMORY: Memory allocation failed
Error Message VRRP-CFG-2-VSH_REGISTER_FAIL: VSH registration failed returning

[dec]
Explanation VRRPsparsetreeregistrationwithVSHfailed'
2-608 OL-26589-01
VRRP-CFG-3
Error Message VRRP-CFG-3-INIT_FAILED: Initialization failed. Component [chars]
[chars].
component.
Error Message VRRP-CFG-3-VRRP_FEATURE_MANAGER_ERROR: Error in feature manager

operation
Explanation The feature manager operation did not go through fine
problem
VRRP-CFG-5
Error Message VRRP-CFG-5-STARTING: VRRP Manager service started
Explanation The service successfully started.
VRRP-ENG Messages
This section contains the VRRP-ENG messages.
VRRP-ENG-2
Error Message VRRP-ENG-2-ALLOC_MEMORY: Memory allocation failed
Error Message VRRP-ENG-2-VR_FAILURE: Error in VR[chars] [dec] interface [chars].

Going to init state
Explanation The VR [dec] on the interface [chars] is in init state for an internal error.
Recommended Action Show interface to check the status of the interface, show configuration, status
and statistics of the specified virtual router, enable the vrrp debug and shut/ no shut the specified
virtual router.
OL-26589-01 2-609
VRRP-ENG-3
Error Message VRRP-ENG-3-ARP_INIT_ERROR: Failed to init ARP, ret [hex], errno [dec]
Explanation VRRP-ARP interaction failed.
Error Message VRRP-ENG-3-BFD_IF_SESSION_REMOVAL_ERROR: Failed to remove interface

level VRRP-BFD sessions ([hex] [hex]), Refer logs
Explanation Plz refer internal error history for more details.
Error Message VRRP-ENG-3-BFD_SESSION_ADD_ERROR: Failed to add a few VRRP-BFD

sessions([hex] [hex]), Refer logs
Error Message VRRP-ENG-3-BFD_SESSION_CREATION_ERROR: Failed to create BFD session

information([hex] [hex]), Refer logs
Error Message VRRP-ENG-3-BFD_SESSION_REMOVAL_ERROR: Failed to remove a few

VRRP-BFD sessions([hex] [hex]), Refer logs
Error Message VRRP-ENG-3-INIT_FAILED: Initialization failed. Component [chars]
[chars].
component.
2-610 OL-26589-01
Error Message VRRP-ENG-3-IP_INIT_ERROR: Failed to init IP, ret [hex], errno [dec]
Explanation VRRP-IP interaction failed.
Error Message VRRP-ENG-3-L3VM_INIT_ERROR: Failed to init L3VM, ret [hex], errno

[dec]
Explanation VRRP-L3VM interaction failed.
Error Message VRRP-ENG-3-URIB_INIT_ERROR: Failed to init URIB, ret [hex], errno

[dec]
Explanation VRRP-URIB interaction failed.
VRRP-ENG-4
Error Message VRRP-ENG-4-BAD_ADV: VR[chars] ID [dec] on interface [chars] bad

advertisement received: reason [chars]
Explanation The virtual router specified has received an invalid advertisement.
Recommended Action Check that all VRRP nodes have the same configuration.
VRRP-ENG-5
Error Message VRRP-ENG-5-INTERFACE_DOWN: Cannot start the VR[chars] [dec] since

the interface [chars] is down
Explanation The specified VR is enabled but

cantchangestatefrominit.Thespecifiedinterfaceisdownordoesn'thaveaprimaryIPaddressconfigured.'
Error Message VRRP-ENG-5-INTERFACE_STATE_CHANGE: Interface [chars] state changed

to [chars]
Explanation The interface specified has changed state This could have triggered a VRRP status
change.
OL-26589-01 2-611
Error Message VRRP-ENG-5-INVALID_CONFIG: Cannot start the VR[chars] [dec] on the

interface [chars]. Invalid IP configuration. Reason: [chars]
Explanation The specified VR on interface [chars] is enabled but the IP configuration is not valid
because of [chars].
Recommended Action Show interface to check that the IP address of the interface is configured and
it is in the same subnet of the virtual router address.
Error Message VRRP-ENG-5-STARTING: VRRP Engine service started
Explanation The service successfully started.
Error Message VRRP-ENG-5-VR_STATE_CHANGE: VR[chars] ID [dec] on interface [chars]

state changed to [chars], event [chars]
Explanation The status of the specified virtual router has changed to [chars].
VRRP-ENG-6
Error Message VRRP-ENG-6-VSHA_RESULT: VR ID [dec] on interface [chars] state change

request result [chars]
Explanation The result of the request for status change on the virtual router (with VSHA extension)
specified is [chars].
VSAN Messages
This section contains the VSAN messages.
VSAN-2
Error Message VSAN-2-PROGRAM_EXIT: process exiting with reason: [chars]
Explanation VSAN manager process is exiting with reason [chars].
2-612 OL-26589-01
VSAN-3
Error Message VSAN-3-CFS_OPERATION_FAILED: cfs [chars] operation failed : [chars]
Explanation Cfs operation [chars1] has failed. [chars2]
problem
Error Message VSAN-3-MEM_ALLOC_FAILED: alloc failed for size:[dec]
Explanation Memory allocation of size [dec] failed.
Recommended Action Do "show process memory" command to see memory usage of processes.
Error Message VSAN-3-MESSAGE_ERROR: could not handle message:[chars] of type [dec]

sent by addr [dec]:[dec]
Explanation Got an IPC message [chars] of type [dec1] sent by a component running on node [dec2]
with sap [dec3].
VSAN-6
Error Message VSAN-6-ACTIVATED: VSAN:[dec] changing from suspended to active
Explanation Making VSAN with ID [dec] active from suspended state.
Error Message VSAN-6-CFS_MERGE_NOT_SUPPORTED: merging of fctimer configuration

data is not supported
Explanation Merging of fctimer configuration data using cfs is not supported
Error Message VSAN-6-CREATED: Created VSAN:[dec] with name:[chars]
Explanation Created VSAN with ID [dec] and name [chars].
OL-26589-01 2-613
Error Message VSAN-6-MEMBERSHIP_UPDATE: Updated membership for interface:[chars]

with VSAN:[dec]
Explanation Updating membership for interface [chars] with VSAN [dec].
Error Message VSAN-6-REMOVED: Removed VSAN:[dec]
Explanation Removed VSAN with ID [dec].
Error Message VSAN-6-SUSPENDED: VSAN:[dec] changing from active to suspended
Explanation Suspending VSAN with ID [dec] from active state.
Error Message VSAN-6-TRUNKING_MEMBERSHIP_UPDATE: trunking membership updated for

interface:[chars] with VSAN bitmap:[chars]
Explanation Updated trunking membership for interface [chars1] with allowed VSAN list [chars2].
VSD Messages
This section contains the VSD messages.
VSD-SLOT#-2
Error Message VSD-SLOT#-2-CPP_CATASTROPHIC_ERROR: ERROR: Component ([chars])

VSHD Messages
This section contains the VSHD messages.
2-614 OL-26589-01
VSHD-2
Error Message VSHD-2-VSHD_SYSLOG_EOL_ERR: EOL function [chars] from library

[chars] exited due to Signal [dec]
Explanation Error in CLI EOL function
Error Message VSHD-2-VSHD_SYSLOG_PSS_SNAPSHOT_ERR: Source URI:[chars] Destination

URI:[chars] errcode:[dec]
Explanation PSS snapshot error
Error Message VSHD-2-VSHD_SYSLOG_SDWRAP_ERR: Description:[chars] errcode:[dec]
Explanation Debug infrastructure error
VSHD-3
Error Message VSHD-3-VSHD_ROLE_DISTRIBUTE_FAILURE: Role distribution operation

([chars]) failed with error id [hex]
Explanation This is probably occurring due to unstable fabric
Recommended Action Please retry operation when fabric is stable
Error Message VSHD-3-VSHD_SYSLOG_FILE_ERR: Purpose:[chars] Filename:[chars]

errcode:[dec]
Error Message VSHD-3-VSHD_SYSLOG_MTS_ERR: message [chars]
Explanation MTS message handling error
OL-26589-01 2-615
Error Message VSHD-3-VSHD_SYSLOG_PARSE_TREE_ERR: [chars]
Explanation Error while updating parse tree in shell
Error Message VSHD-3-VSHD_SYSLOG_PSS_ERR: Purpose:[chars] URI:[chars]

errcode:[dec]
Explanation PSS handling error
VSHD-4
Error Message VSHD-4-VSHD_LICENSE_EXPIRY_WARNING: License [chars] expires on

[chars]. Vsan policy will be set to default (deny) for all roles when license
expires
Explanation Vsan policy would be set default (deny) for all roles when license expires
Error Message VSHD-4-VSHD_ROLE_DATABASE_OUT_OF_SYNC: Role configuration database

found to be different between the switches during merge
Explanation Role configuration database is recommended to be identical among all switches in the
fabric.
Recommended Action Edit the configuration on one of the switches to obtain the desired role
configuration database and then commit it
Error Message VSHD-4-VSHD_ROLE_DATABASE_VERSION_NOT_UNDERSTOOD: This switch does

not understand the version of role configuration database received during merge
Explanation This is probably occurring due to different versions of system image on switches in the
fabric
Recommended Action Please make sure all switches are running the same version of the system
image
VSHD-5
Error Message VSHD-5-VSHD_SYSLOG_CONFIG_CHANGE: VDC=[chars], VTY=[chars],

user=[chars], CMD="[chars]"
Explanation Configuration change notification
2-616 OL-26589-01
Error Message VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by [chars] on

[chars]
Explanation CLI Configuration mode was exited
Error Message VSHD-5-VSHD_SYSLOG_ROLE_CREATED: New cli role [chars] created
Explanation New cli role created
VSHD-7
Error Message VSHD-7-VSHD_SYSLOG_PARSE_TREE_UPDATE: Parse tree [chars]
Explanation Parse tree updated in shell
WWN Messages
This section contains the WWN messages.
WWN-1
Error Message WWN-1-TYPE1_ALERT: [dec] (< [dec] %) Remain
Explanation The WWN Manager has run out of WWNs. No new dynamically allocated WWNs are
available. However, statically assigned WWNs such as switch WWN, port WWN, etc. are still
available.
Recommended Action Please add additional WWNs by programming a new Secondary MAC address
and its range.
Error Message WWN-1-TYPES2_5_ALERT: Only [dec] (< [dec] %) Type 2 & 5 WWNs Remain
Explanation The WWN Manager has run out of WWNs of NAA Types 2 and 5
and its range.
OL-26589-01 2-617
WWN-2
Error Message WWN-2-BKPLN_PROM_CANT_READ: Can not read backplane PROM
Explanation The WWN Manager has failed to read chassis information. No dynamic WWNs could
be allocated.
Error Message WWN-2-EXITING: Exited due to [chars]
Explanation The WWN Manager process has exited due to [char]. The process has probably been
Error Message WWN-2-GENERAL_ERROR: [chars]
Explanation The WWN Manager has encountered an critical error. The description of error is [str.].
Error Message WWN-2-MALLOC_ERROR: Size [dec] bytes
Explanation The WWN Manager could not allocate memory.
Error Message WWN-2-PSS_BKP_PSS_MISMATCH: Block [dec]: PSS: Not Free; BKPLN PROM:
Free
Explanation This WWN Manager detected a discrepancy between the information on the chassis and
that in its persistent information databases. The persistent information database has been updated
with the information on the chassis.
Error Message WWN-2-PSS_ERROR: [chars]
Explanation The WWN Manager encountered error while operating on a persistent storage database.
2-618 OL-26589-01
Error Message WWN-2-STDOUT_ROTATE_FAILURE: Failed to rotate stdout file: [chars]
Explanation The WWN Manager has failed to rotate its current stdout file with filename [str.]. The
filesize could grow beyond its maximum limit.
Error Message WWN-2-TYPE1_CRIT: [dec] (< [dec] %) Remain
Explanation The WWN Manager has only [dec] or less than [dec]-percent WWNs remaining.
and its range.
Error Message WWN-2-TYPES2_5_CRIT: [dec] (< [dec] %) Remain
Explanation The WWN Manager has only [dec] or less than [dec]-percent WWNs of NAA Types 2
and 5 remaining.
and its range.
WWN-3
Error Message WWN-3-PSS_SYNC_TO_STNDBY_FAILED: PSS TYPE=[chars] KEY=[chars]
Explanation Could not send PSS Sync. notification to Standby Supervisor. PSS Type=[str.]
Operation=[.str] Key=[Str.].
Error Message WWN-3-RELEASE_ERR_UNKNOWN: Unknown WWN [chars] [chars]
Explanation WWN Manager received a request to release a WWN [char] that could not have been
allocated by this WWN Manager due to [char].
Error Message WWN-3-RELEASE_ERR: Cant Rel. WWN [chars]
Explanation WWN Manager received a request to release a WWN that cannot be released.
OL-26589-01 2-619
Error Message WWN-3-STARTUP_COPY_TO_RUNNING_FAILED: [chars]
Explanation Could not snapshot Startup-Config PSS to Running-Config. The description of error is
[str.].
Error Message WWN-3-TOOMANY_REQ_REL: WWNs [chars] = [dec]
Explanation The WWN Manager received a request to allocate [dec] WWN, which is more than the
maximum number of WWNs that can be allocated/released in a single request.
Error Message WWN-3-UNKNOWN_MSG: Received from Node=[dec] SAP=[dec] Opcode=[dec]
Explanation The WWN Manager has received an unknown message from [dec]].[dec] with opcode
[dec]. This information is for debugging only.
Error Message WWN-3-WWN_PSS_CORRUPTED: [chars] PSS found corrupted
Explanation The WWN Manager has detected corruption in one of its persistent information
database. The database would be recreated.
WWN-4
Error Message WWN-4-PSS_SUP_CNT_MISMATCH: PSS [dec] Bkpln [dec]
Explanation The WWN Manager has detected that some other supervisor card was plugged in earlier
on this chassis. This WWN Manager is making sure that new WWNs allocate do not conflict with
WWNs that could have been allocated by the previous supervisor card.
Error Message WWN-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec]
Explanation There was a version mismatch between the WWN Manager and one of its persistent
2-620 OL-26589-01
Error Message WWN-4-TYPE1_WARN: [dec] (< [dec] %) Remain
Explanation The WWN Manager has only [dec] or less than [dec]-percent WWNs remaining for
allocation.
Error Message WWN-4-TYPES2_5_WARN: [dec] (< [dec] %) Remain
Explanation The WWN Manager has only [dec] or less than [dec]-percent WWNs of NAA Types 2
and 5 remaining.
and its range.
WWN-5
Error Message WWN-5-VSAN_WWN_CHANGE: [chars]
Explanation VSAN-WWN created or deleted. The description of error is [str.].
WWN-6
Error Message WWN-6-ALLOCATED_BLOCK: Block number [dec]
Explanation The WWN Manager has allocated a new block, block number [dec], of 256 WWNs for
internal use.
Error Message WWN-6-BECAME_ACTIVE: Became ACTIVE from standby mode
Explanation The WWN Manager on the standby supervisor became active and it is ready to serve
client requests for WWNs.
Error Message WWN-6-BECAME_STDBY: Became STANDBY from active mode
Explanation The WWN Manager became standby from active mode.
OL-26589-01 2-621
Error Message WWN-6-EXCESSIVE_DELAY: [chars]
Explanation Excessive time taken for a processing event. The description of the event is [str.].
Error Message WWN-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system

Explanation The WWN Manager was unable to send heartbeat to the system manager.
Error Message WWN-6-GENERAL_EVENT: [chars]
Explanation The WWN Manager has generated an important event. The description of the event is
[str.].
Error Message WWN-6-PSS_CREATED: [chars] PSS Created
Explanation One of the persistent information database of the WWN Manager has been recreated.
Error Message WWN-6-PSS_DESTROYED: [chars] PSS Destroyed
Explanation One of the persistent information databases has been intentionally destroyed and would
be recreated.
Error Message WWN-6-RELEASED_BLOCK: Block number [dec]
Explanation The WWN Manager has released a block, block number [dec], of 256 WWNs.
Error Message WWN-6-SEC_MAC_UPDATED: MAC=[chars] Range=[dec]
Explanation The WWN Manager had updated the Secondary MAC address with MAC address
[char] and range [dec]. This update was initiated from a management entity.
2-622 OL-26589-01
Error Message WWN-6-SERVICE_UP: Initialized [chars]
Explanation The WWN Manager is up and ready to accept client requests for WWNs. The service
was initialized in [char] mode.
Error Message WWN-6-SWITCHOVER: Switching Over to other Supervisor
Explanation The WWN Manager has successfully switched over to the standby supervisor card.
WWN-7
Error Message WWN-7-RELEASE_ERR_FREE: Already free WWN [chars]
Explanation A client of WWN Manager attempted to release WWN [char] which is already free.
This information is for debugging only.
XBAR_CLIENT Messages
This section contains the XBAR_CLIENT messages.
XBAR_CLIENT-2
Error Message XBAR_CLIENT-2-CROSS_LINK_SYNC_LOSS: XBAR-[chars].
Explanation Cross links lost sync and hence xbar is brought down.
Recommended Action Please reload the xbar using reloadxbar<xbar-num
Error Message XBAR_CLIENT-2-MEM_FULL: Memory allocation failed.
Explanation XBAR_CLIENT process has failed to allocate memory.
Recommended Action Please perform a showxbar-clientevent-history'tocollectmoreinformation.'
Error Message XBAR_CLIENT-2-MEM_FULL: memory allocation failed
Explanation Process xbar_client failed to allocate memory
Recommended Action Please examine the xbar-client event-history for more information.
OL-26589-01 2-623
Error Message XBAR_CLIENT-2-PROC_DN: Process is shutting down: [chars].
Explanation XBAR_CLIENT process is exiting.
Error Message XBAR_CLIENT-2-PROC_DN: exiting: [chars].
Explanation Process xbar_client is exiting
Error Message XBAR_CLIENT-2-PROC_INITFAIL: Process initialization failed due to

[chars].
Explanation XBAR_CLIENT process has failed initialization.
Error Message XBAR_CLIENT-2-PROC_INITFAIL: Process initialization failed due to

[chars].
Explanation XBAR_CLIENT process has failed initialization.
Error Message XBAR_CLIENT-2-PROC_INITFAIL: initialization failed due to [chars]
Explanation Process xbar_client failed initialization
XBAR_CLIENT-3
Error Message XBAR_CLIENT-3-IPC_MSGERR: Error in processing IPC message: [dec],

Error code = [dec].
Explanation XBAR_CLIENT process has encountered an error in processing message.
Error Message XBAR_CLIENT-3-IPC_MSGERR: failure processing IPC message [dec],

error code = [dec]
Explanation Process xbar_client failed to process IPC message
2-624 OL-26589-01
Error Message XBAR_CLIENT-3-IPC_MSGUNKN: Received unexpected IPC message: [dec].
Explanation XBAR_CLIENT process has received an unknown message.
Error Message XBAR_CLIENT-3-IPC_MSGUNKN: unknown IPC message received: [dec]
Explanation Process xbar_client has received an unknown IPC message.
Error Message XBAR_CLIENT-3-SUP2_XBC_MOD_INIT_FAIL: [chars], errcode - [hex]
Explanation The module initialiazation failed

showprocessxbar-clientevent-history'tocollectmoreinformation'
XBAR_CLIENT-SLOT#-2
Error Message XBAR_CLIENT-SLOT#-2-VEGAS2_XBC_MEM_FULL: memory allocation failed in

routine [chars]
Explanation Process xbar_client failed to allocate memory

Error Message XBAR_CLIENT-SLOT#-2-VEGAS2_XBC_PROC_DN: terminating due to signal

[dec]
Explanation Process xbar_client is exiting

Error Message XBAR_CLIENT-SLOT#-2-VEGAS2_XBC_PROC_INITFAIL: initialization

failed: [chars], errno [dec]
Explanation Process xbar_client failed initialization

OL-26589-01 2-625
XBAR_CLIENT-SLOT#-3
Error Message XBAR_CLIENT-SLOT#-3-VEGAS2_XBC_IPC_MSGUNKN: unknown IPC message

received: opcode [dec]
Explanation Process xbar_client hass received an unknown IPC message

Error Message XBAR_CLIENT-SLOT#-3-VEGAS2_XBC_MOD_INIT_FAIL: [chars], errcode -

[hex]
Explanation The module initialiazation failed

XBAR Messages
This section contains the XBAR messages.
XBAR-2
Error Message XBAR-2-ARB_INIT_FAIL: Arbiter Initialization failed return_code

[hex] ([chars]).
Explanation The supervisor has experienced an arbiter setup failure .
Error Message XBAR-2-INCOMPATIBLE_CONFIG: [chars] [dec] [chars].
Explanation This module is not compatible with the current fabric mode. It will be powered down.
Error Message XBAR-2-XBAR_INSUFFICIENT_XBAR_BANDWIDTH: Module in slot [dec] has

insufficient xbar-bandwidth.
Explanation To track insufficient xbar-bandwidth.
2-626 OL-26589-01
Error Message XBAR-2-XBAR_MIXED_SPINES_POLICY_MATCHED: [chars]
Explanation Fabric could not be brought online due to policy match:
Error Message XBAR-2-XBAR_SUFFICIENT_XBAR_BANDWIDTH: Module in slot [dec] has

sufficient xbar-bandwidth.
Explanation To track recovery from insufficient xbar-bandwidth.
Error Message XBAR-2-XBM_EEM_FABRIC_ACTION: Fabric [chars] has been reloaded by

xbar-manager because of an eem-policy triggered action [chars] %i
Explanation Xbar-manager has removed the fabric because an eem policy has been met This means
that the fabric has hit the maximum number of recoverable sync-losses with multiple line-cards
within a time-window.
Error Message XBAR-2-XBM_EEM_MODULE_ACTION: Module [chars] has been reloaded by

xbar-manager because of an eem-policy triggered action [chars] %i
Explanation Xbar-manager has removed the linecard because an eem policy has been met This
means that the module has hit the maximum number of recoverable sync-losses with fabric card(s)
within a time-window.
XBAR-3
Error Message XBAR-3-MEM_FULL: Memory allocation failed. [chars] %i
Explanation
XBAR-4
Error Message XBAR-4-XBAR_MIXED_SPINES_IN_CHASSIS: [chars]
Explanation There are both FAB-1 and FAB-2 type spines in the Chassis. Please replace the FAB-1
spines with FAB-2 Spines.
OL-26589-01 2-627
XBAR-5
Error Message XBAR-5-ARBITER_INIT_FAILURE: Re-initializing Arbiter. [chars]

[chars] module %i
Error Message XBAR-5-ARB_CLEAR_PORT_FAIL: Arbiter reported failure to de-register

port [dec] in group [dec] return_code [hex] ([chars]).
Error Message XBAR-5-ARB_INIT_MOD_DIS_INTR_FAIL: Arbiter reported failure to

disable interrupt for module [dec] return_code [hex] ([chars]).
Error Message XBAR-5-ARB_INIT_MOD_INSERT_CHECK_FAIL: Arbiter reported failure to

recognize module [dec] return_code [hex] ([chars]).
Error Message XBAR-5-ARB_INIT_MOD_INSERT_FAIL: Arbiter reported failure to init

module [dec] return_code [hex] ([chars]).
Error Message XBAR-5-ARB_INIT_MOD_INTR_FAIL: Arbiter reported failure to enable

interrupt for module [dec] return_code [hex] ([chars]).
2-628 OL-26589-01
Error Message XBAR-5-ARB_INIT_MOD_REMOVE_FAIL: Arbiter reported failure to remove

module [dec] return_code [hex] ([chars]).
Error Message XBAR-5-ARB_INIT_PORT_FAIL: Arbiter reported failure to register port

[dec] in group [dec] return_code [hex] ([chars]).
Error Message XBAR-5-MOD_CONNECTION_REATTEMPT: Re-attempting XBAR connection with

module [dec]
Explanation The module has experienced a setup failure on connecting the module to the fabric.
Recommended Action Collect more informations about XBAR component Use command
showxbarinternalevent-historymodule<moduleid
Error Message XBAR-5-SYNC_THRESHOLD_FAILURE: Module resync threshold exceeded

[chars] [chars] module %i
Explanation This module has exceeded the number of resync attempts in a day. Module will be
reloaded
Error Message XBAR-5-XBAR_ENABLE_FPOE_DB_FAILURE: XBAR [chars] enabling FPOE-DB

mode failed
Explanation The supervisor failed to enable FPOE-DB mode in fabric. The supervisor is going to
reboot. In case of dual supervisor, a switchover will occur.
Error Message XBAR-5-XBAR_INIT_FAILURE: XBAR [chars] initialization failed [chars]

%i
Explanation The supervisor has experienced a fabric initialization failure. The supervisor is going
to reboot. In case of dual supervisor, a switchover will occur.
OL-26589-01 2-629
Error Message XBAR-5-XBAR_INIT_FAIL: Xbar [[dec].[dec]] reported failure durinig

intialization return_code [hex] ([chars]).
Explanation The supervisor has experienced an xbar setup failure .
Error Message XBAR-5-XBAR_MOD_INSERT_SEQ_FAILURE: [chars] for module [dec]
Explanation The xbar manager received failure response and is failing the insert sequence
Error Message XBAR-5-XBAR_MOD_LC_INSERT_SEQ_FAILURE: Module in slot [dec] has

failed insert sequence
Explanation The xbar manager is failing the insert sequence
Error Message XBAR-5-XBAR_PORT_CHECK_SYNC_FAIL: Xbar [[dec].[dec]] reported

failure to check sync on port [dec] return_code [hex] ([chars]).
Error Message XBAR-5-XBAR_PORT_CONTINUE_SYNC_FAIL: Xbar [[dec].[dec]] reported

failure to continue sync on port [dec] return_code [hex] ([chars]).
Error Message XBAR-5-XBAR_PORT_DISABLE_FAIL: Xbar [[dec].[dec]] reported failure

to disable port [dec] return_code [hex] ([chars]).
Error Message XBAR-5-XBAR_PORT_ENABLE_FAIL: Xbar [[dec].[dec]] reported failure to

enable port [dec] return_code [hex] ([chars]).
2-630 OL-26589-01
Error Message XBAR-5-XBAR_PORT_FORCE_POE_DISABLE_FAIL: Xbar [[dec].[dec]] reported

failure to disable force poe mode on [dec] return_code [hex] ([chars]).
Error Message XBAR-5-XBAR_PORT_FORCE_POE_ENABLE_FAIL: Xbar [[dec].[dec]] reported

failure to enable force poe mode on [dec] return_code [hex] ([chars]).
Error Message XBAR-5-XBAR_PORT_LPBACK_DISABLE_FAIL: Xbar [[dec].[dec]] reported

failure to disable port loopback on [dec] return_code [hex] ([chars]).
Error Message XBAR-5-XBAR_PORT_LPBACK_ENABLE_FAIL: Xbar [[dec].[dec]] reported

failure to enable port loopback on [dec] return_code [hex] ([chars]).
Error Message XBAR-5-XBAR_PORT_START_SYNC_FAIL: Xbar [[dec].[dec]] reported

failure to start sync on port [dec] return_code [hex] ([chars]).
Error Message XBAR-5-XBAR_RELEASE_ACCESS_FAIL: Slot [dec] reported failure

releasing [chars] xbar access return_code [hex] ([chars])
Explanation The supervisor has experienced an xbar access failure .
Error Message XBAR-5-XBAR_SET_ACCESS_FAIL: Slot [dec] reported failure acquiring

[chars] xbar access return_code [hex] ([chars])
Explanation The supervisor has experienced an xbar access failure .
OL-26589-01 2-631
Error Message XBAR-5-XBAR_STANDBY_SUP_ARB_FAIL: [chars] return_code [hex]

([chars])
Explanation The supervisor has experienced an arbiter access failure .
Error Message XBAR-5-XBAR_STATUS_REPORT: Module [dec] reported status for

component [dec] code [hex].
Explanation An error status has been reported. If error is on supervisor, the supervisor is going to
reboot. In case of dual supervisors, a switchover will occur. If error is on module, the module will
be power cycled.
Error Message XBAR-5-XBAR_SW_INIT_FAIL: Xbar [[dec].[dec]] reported failure

durinig sw intialization return_code [hex] ([chars]).
Error Message XBAR-5-XBAR_VERSION_CHECK_FAILURE: XBAR [chars] SCZ version check

failed [chars] %i
Explanation This SUP has an older Santacruz version, and so will not be allowed to power-up,
Please upgrade to the latest supervisor version.
XMLMA Messages
This section contains the XMLMA messages.
XMLMA-2
Error Message XMLMA-2-HEARTBEAT_FAIL: XML master agent failed to send heart beat:
[chars]
Explanation XML master agent has failed sending heartbeat.
2-632 OL-26589-01
Error Message XMLMA-2-INITFAIL: XML master agent initialization fails: [chars]
Explanation XML master agent has failed initialization.
Error Message XMLMA-2-MTSERROR: XML master agent mts operation failed: [chars]
Explanation XML master agent mts operation failed.
Error Message XMLMA-2-PSSFAILURE: XML master agent pss operation failed: [chars]
Explanation XML master agent pss operation failed.
Error Message XMLMA-2-XMLMACRIT: XML master agent: [chars]
Explanation XML master agent critical log.
XMLMA-3
Error Message XMLMA-3-XMLMAERR: XML master agent: [chars]
Explanation XML master agent error log.
XMLMA-5
Error Message XMLMA-5-STARTING: XML master agent started [chars]
Explanation XML master agent has been started.
XMLMA-6
Error Message XMLMA-6-XMLMAEXIT: XML master agent exiting...: [chars]
Explanation XML master agent is exiting.
OL-26589-01 2-633
Error Message XMLMA-6-XMLMALOG: XML master agent operation log: [chars]
Explanation XML master agent operation log.
XMLSA Messages
This section contains the XMLSA messages.
XMLSA-2
Error Message XMLSA-2-HEARTBEAT_FAIL: XML sub agent failed sending heart beat:
[chars]
Explanation XML sub agent failed sending heartbeat.
Error Message XMLSA-2-INITFAIL: XML sub agent initialization fails: [chars]
Explanation XML agent has failed initialization.
Error Message XMLSA-2-USER_INACTIVE: XML sub agent timeed out: [chars]
Explanation XML sub agent timedout due to inactivity.
Error Message XMLSA-2-VSH_ERR: XML sub agent vsh cmd error...: [chars]
Explanation XML sub agent vsh cmd error.
XMLSA-5
Error Message XMLSA-5-STARTING: XML sub agent started: [chars]
Explanation XML sub agent has been started.
2-634 OL-26589-01
XMLSA-6
Error Message XMLSA-6-XMLSAEXIT: XML sub agent exiting...: [chars]
Explanation XML sub agent is exiting.
Error Message XMLSA-6-XMLSALOG: XML sub agent log: [chars]
Explanation XML sub agent log.
ZBM Messages
This section contains the ZBM messages.
ZBM-2
Error Message ZBM-2-ZBM_HA_FAILURE: Failed to do high availability operation:

[chars].
Error Message ZBM-2-ZBM_INIT_FAILED: Initialization failed for ZBM: [chars],

reason: [hex].
Explanation Initialization failed for ZBM due to [chars], reason: [hex].
Error Message ZBM-2-ZBM_INIT_WARNING: Initialization warning for ZBM: [chars],

reason: [hex].
Explanation Initialization warning for ZBM due to [chars], reason: [hex].
OL-26589-01 2-635
Error Message ZBM-2-ZBM_LINECARD_STATUS: Status from linecard: [dec], for module:

[chars](ID: [dec]), status : [dec], error_id: [hex], catastrophic: [chars],
restart count: [dec].
Explanation Status from linecard: [dec], for module: [chars](ID: [dec]), status : [dec], error_id:
[hex], catastrophic: [chars], restart count: [dec].
Error Message ZBM-2-ZBM_MALLOC_FAILURE: Memory allocation failed for size [dec]
Error Message ZBM-2-ZBM_MTS_FAILURE: Failed to do MTS operation: [chars].
Error Message ZBM-2-ZBM_MTS_REGISTRATION_FAILED: MTS options setting to [hex]

failed for opCode: [dec].
Error Message ZBM-2-ZBM_PSS_FAILURE: Failed to do PSS operation: [chars], reason:

[hex].
Error Message ZBM-2-ZBM_PSS_VER_FAIL: PSS file [chars] has version

Error Message ZBM-2-ZBM_RUNTIME_FAILURE: [chars] [dec], Error: [hex]
Explanation ZBM runtime failure is reported as [chars] [dec], reason: [hex].
2-636 OL-26589-01
Error Message ZBM-2-ZBM_TCAM_FAILURE: Failed to do TCAM operation: [chars].
Explanation Failed to do TCAM operation. [chars] is the reason.
Error Message ZBM-2-ZBM_TCAM_SEND: [chars]
Explanation Sending to tcam [chars]
ZBM-4
Error Message ZBM-4-ZBM_WARNING: [chars] [dec]
Explanation ZBM warning messages is reported as [chars] [dec].
ZBM-6
Error Message ZBM-6-ZBM_DIAG_EVENT_STATUS: [chars] [hex].
Explanation ZBM system health management event status is reported as [chars] [hex].
Error Message ZBM-6-ZBM_ECHO_PROGRAMMING_FAILED: [chars].
Explanation Programming echo entry failed for [chars].
Error Message ZBM-6-ZBM_E_PORT_EVENT_STATUS: [chars] [chars].
Explanation ZBM xEport event status is reported as [chars] [chars].
Error Message ZBM-6-ZBM_FCC_EVENT_STATUS: [chars] [chars].
Explanation ZBM FCC event status is reported as [chars] [chars].
OL-26589-01 2-637
Error Message ZBM-6-ZBM_INIT_PROCESS: Zone Block Mgr process started [chars] at

[chars]
Explanation Zone Block Mgr process started in [chars] (stateless/stateful) mode at time [chars].
Error Message ZBM-6-ZBM_LINECARD_EVENT_STATUS: [chars] [hex].
Explanation ZBM linecard event status is reported as [chars] [dec].
Error Message ZBM-6-ZBM_MCAST_EVENT_STATUS: [chars] [chars].
Explanation ZBM multicast event status is reported as [chars] [chars].
Error Message ZBM-6-ZBM_NX_PORT_EVENT_STATUS: [chars] [chars].
Explanation ZBM Nx Port event status is reported as [chars] [chars].
Error Message ZBM-6-ZBM_PORT_MODE_EVENT_STATUS: [chars] [chars].
Explanation ZBM portmode event status is reported as [chars] [chars].
Error Message ZBM-6-ZBM_RUNTIME_STATUS: [chars] [dec]
Explanation ZBM runtime status is reported as [chars] [dec].
Error Message ZBM-6-ZBM_STATUS: ZBM Status: [chars].
Explanation ZBM status is reported as [chars].
Error Message ZBM-6-ZBM_UPDATE_SSRAM_QOS_EVENT_STATUS: [chars] [chars].
Explanation ZBM update SSRAM for QoS event status is reported as [chars] [chars].
2-638 OL-26589-01
ZONE Messages
This section contains the ZONE messages.
ZONE-2
Error Message ZONE-2-LZ_EXITING: LUN/Read-only zoning process exited. Reason:

[chars]
Explanation The LUN/Read-only zoning process has exited due to [char]. The process has probably
been restarted automatically.
Error Message ZONE-2-LZ_GENERAL_ERROR: [chars]
Explanation The LUN/Read-only zoning process has encountered a critical error. The description of
error is [str].
Error Message ZONE-2-LZ_INIT_FAILED: Initialization of LUN/Read-only zoning

Process failed at [chars]
Explanation Initialization of LUN/Read-only zoning process failed at [char].
Error Message ZONE-2-LZ_MALLOC_ERROR: Size [dec] bytes
Explanation The LUN/Read-only zoning process could not allocate memory.
Error Message ZONE-2-ZS_ALIAS_LIMIT_EXCEEDED: The limit for maximum number of

aliases exceeded
Explanation The number of aliases configured has exceeded the maximum number of aliases
allowed per vsan Due to this, distribution or merge operation may fail.
Recommended Action Make sure the number of aliases is less than the maximum allowed in a vsan.
OL-26589-01 2-639
Error Message ZONE-2-ZS_ATTR_GROUP_LIMIT_EXCEEDED: The limit for maximum number of

attribute groups exceeded
Explanation The number of attribute groups configured has exceeded the maximum number of
attribute groups allowed in a vsan Due to this, distribution or merge operation may fail.
Recommended Action Make sure the number of attribute groups is less than the maximum allowed
in a vsan.
Error Message ZONE-2-ZS_BLOCKED_ATTR_PRESENT: Module [dec] failed to come online

due to [chars]
Explanation Module [dec] failed to come up due to [chars].
Recommended Action Verify if RO/LUN/Broadcast attributes are configured, in any VSAN, disable
if configured
Error Message ZONE-2-ZS_CHANGE_ACA_FAILED: ACA failed : [chars]
Explanation Zone Server cannot acquire change authorization : [chars].
Recommended Action Verify the interoperability mode on all the switches OR retry later.
Error Message ZONE-2-ZS_CHANGE_ACQUIRE_AUTH_FAILED: Acquire authorization failed

on VSAN [dec]
Explanation Zone Server cannot acquire authorization on VSAN [dec].
Error Message ZONE-2-ZS_CHANGE_ACTIVATION_FAILED_RESN_DOM: Activation failed :

reason [chars] domain [dec]
Explanation Zone Server cannot activate due to reason [chars] on domain [dec].
Error Message ZONE-2-ZS_CHANGE_ACTIVATION_FAILED_RESN: Activation failed : reason

[chars]
Explanation Zone Server cannot activate due to reason [chars].
Error Message ZONE-2-ZS_CHANGE_ACTIVATION_FAILED: Activation failed
Explanation Zone Server cannot activate the zoneset.
2-640 OL-26589-01
Error Message ZONE-2-ZS_CHANGE_APPLY_FAILED: Apply changed failed on VSAN [dec]
Explanation Zone Server cannot apply changes on VSAN [dec].
Error Message ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED_RESN_DOM: Deactivation failed

: reason [chars] domain [dec]
Explanation Zone Server cannot deactivate due to reason [chars] on domain [dec].
Error Message ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED_RESN: Deactivation failed :

reason [chars]
Explanation Zone Server cannot deactivate due to reason [chars].
Error Message ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED: Deactivation failed
Explanation Zone Server cannot deactivate the zoneset.
Error Message ZONE-2-ZS_CHANGE_RELEASE_AUTH_FAILED: Release authorization failed

on VSAN [dec]
Explanation Zone Server cannot release authorization on VSAN [dec].
Error Message ZONE-2-ZS_CHANGE_RRCA_REJECTED: RRCA received from remote domain

[dec] is rejected: [chars]
Explanation Received invalid RRCA from domain [dec]. : [chars]
Recommended Action Verify the interoperability mode on the switch.
Error Message ZONE-2-ZS_CHANGE_RUFC_REJECTED: RUFC received from remote domain

[dec] is rejected: [chars]
Explanation Received invalid RUFC from domain [dec]. : [chars]
OL-26589-01 2-641
Error Message ZONE-2-ZS_CHANGE_SFC_FAILED: SFC failed : [chars]
Explanation Zone Server cannot stage zone configuration : [chars].
Recommended Action Verify the interoperability mode on all the switches.
Error Message ZONE-2-ZS_CHANGE_SFC_REJECTED: SFC received from remote domain [dec]

is rejected: [chars]
Explanation Received invalid SFC from domain [dec]. : [chars]
Error Message ZONE-2-ZS_CHANGE_STAGE_ACTIVATE_ZSSET_BY_NAME_FAILED: Stage

activate zoneset by name failed on VSAN [dec]
Explanation Zone Server cannot stage activate zoneset by name on VSAN [dec].
Error Message ZONE-2-ZS_CHANGE_STAGE_ACTIVATE_ZSSET_ENH_FAILED: Stage activate

zone set enhanced failed on VSAN [dec]
Explanation Zone Server cannot stage activate zone set enhanced on VSAN [dec].
Error Message ZONE-2-ZS_CHANGE_STAGE_DEACTIVATE_ZSSET_ENH_FAILED: Stage

deactivate zoneset enhanced failed on VSAN [dec]
Explanation Zone Server cannot stage deactivate zoneset enhanced on VSAN [dec].
Error Message ZONE-2-ZS_CHANGE_STAGE_DISTRIBUTE_DFLT_ZONE_FAILED: Stage

distribute default zone failed on VSAN [dec]
Explanation Zone Server cannot stage distribute default zone on VSAN [dec].
Error Message ZONE-2-ZS_CHANGE_STAGE_DISTRIBUTE_ZS_DB_FAILED: Stage distribute

zoneset database failed on VSAN [dec]
Explanation Zone Server cannot stage distribute zoneset database on VSAN [dec].
2-642 OL-26589-01
Error Message ZONE-2-ZS_CHANGE_STAGE_SET_ZONING_MODE_FAILED: Stage set zoning mode

failed on VSAN [dec]
Explanation Zone Server cannot stage set zoning mode on VSAN [dec].
Error Message ZONE-2-ZS_CHANGE_STAGE_SET_ZONING_POLICIES_FAILED: Stage set zoning

policies failed on VSAN [dec]
Explanation Zone Server cannot stage set zoning policies on VSAN [dec].
Error Message ZONE-2-ZS_DB_OPERATION_FAILED: Database operation error: [chars]
Explanation Database operation is failed : [chars].
Error Message ZONE-2-ZS_EXPORT_IMPORT_FAILED: [chars] operation failed
Explanation [chars] (Export/Import) operation failed.
Error Message ZONE-2-ZS_FIPS_COMPLIANCE_FAILURE: FIPS compliance error:

consecutively same random numbers
Explanation FIPS compliance error: consecutively same random numbers
Error Message ZONE-2-ZS_INIT_FAILED: [chars]
Explanation Zone Server initialization failed : [chars].
Error Message ZONE-2-ZS_LICENSE_UNAVAIL: License:[chars] unavailable, removing LUN

members, read-only attribute and re-activating active zonesets on all affected
VSANs
Explanation License:[char] unavailable, removing LUN members, read-only attribute and

re-activating active zonesets on all affected VSANs.
OL-26589-01 2-643
Error Message ZONE-2-ZS_LIC_FAILURE: License [chars] operation failed for license

[chars]
Explanation License [char] operation failed for license [char].
Error Message ZONE-2-ZS_LUN_DISABLING_FAILED: license expiry handling failed for

VSAN [dec]
Explanation License expiry handling failed for VSAN [dec].
Error Message ZONE-2-ZS_LUN_MEMBER_LIMIT_EXCEEDED: The limit for maximum number of

lun members exceeded
Explanation The number of lun members configured has exceeded the maximum number of lun
members allowed across all vsans Due to this, distribution or merge operation may fail.
Recommended Action Make sure the number of lun members is less than the maximum allowed
across all vsans.
Error Message ZONE-2-ZS_MALLOC_FAILURE: Memory allocation failed for size [dec]
Error Message ZONE-2-ZS_MEMBER_LIMIT_EXCEEDED: The limit for maximum number of

members exceeded
Explanation The number of members configured has exceeded the maximum number of members
allowed across all vsans Due to this, distribution or merge operation may fail.
Recommended Action Make sure the number of members is less than the maximum allowed across
all vsans.
Error Message ZONE-2-ZS_MERGE_ADJ_NO_RESPONSE: Adjacent switch not responding,

isolating interface [chars]
Explanation Interface [chars] isolated due to adjacent switch not responding to Zone Server
requests.
Recommended Action Flap the interface.
2-644 OL-26589-01
Error Message ZONE-2-ZS_MERGE_FAILED: Zone merge failure, isolating interface

[chars] [chars]
Explanation Interface [chars] isolated due to zone merge failure. error [chars]
Recommended Action Compare active zoneset with the adjacent switch OR use "zone merge
interface [interface] {import/export} VSAN [VSAN-num]" command.
Error Message ZONE-2-ZS_MERGE_FULL_DATABASE_MISMATCH: Zone merge full database

mismatch on interface [chars]
Explanation Full zoning databases are inconsistent between two switches connected by interface
[chars]. Databases are not merged.
Recommended Action Compare full zoning database with the adjacent switch, correct the difference
and flap the link.
Error Message ZONE-2-ZS_MERGE_UNKNOWN_FORMAT: Unknown format, isolating interface

[chars]
Explanation Interface [chars] isolated due to unknown format in merge request.
Recommended Action Set the interoperability mode to same value on both switches.
Error Message ZONE-2-ZS_MTS_OPER_FAILED: MTS [chars] operation failed : [chars]
Explanation Zone Server MTS [chars] operation failed : [chars].
Error Message ZONE-2-ZS_NO_RSCN_ON_SW_CARD: Devices on Module [dec] will not be

receiving RSCN as [chars]
Explanation Devices on Module [dec] will not be receiving RSCN as [chars].
Recommended Action Enable Zone Based RSCN
Error Message ZONE-2-ZS_PORT_SWAP_FAILURE: Port swap operation failed
Explanation Port swap operation failed.
Error Message ZONE-2-ZS_PSS_VER_MISMATCH: PSS version mismatch URL: [chars]

(expected [chars], got [chars])
Explanation Configuration version mismatch. PSS URL [chars]. Expected version [chars], stored
version [chars].
Recommended Action Upgrade/Downgrade to expected version.
OL-26589-01 2-645
Error Message ZONE-2-ZS_TCAM_BROADCAST_ZONE_DISABLED: Broadcast zoning disabled :

Reason: Hard zoning disabled
Explanation Broadcast zoning disabled : Reason: Hard zoning disabled due to TCAM programming
failure.
Error Message ZONE-2-ZS_TCAM_LUN_ZONING_DISABLED: LUN zoning disabled : Reason:

Hard zoning disabled
Explanation LUN zoning disabled : Reason: Hard zoning disabled due to TCAM programming
failure.
Error Message ZONE-2-ZS_TCAM_PROGRAMMING_FAILED: TCAM operation failed : [chars],

Reason: [chars]
Explanation TCAM Programming failure has occurred : [chars]. [chars] is the reason for failure.
Error Message ZONE-2-ZS_TCAM_READ_ONLY_ZONE_DISABLED: Read-only zoning disabled :

Reason: Hard zoning disabled
Explanation Read-only zoning disabled : Reason: Hard zoning disabled due to TCAM programming
failure.
Error Message ZONE-2-ZS_TCAM_SWITCHED_TO_SOFT_ZONING_MODE: Switched to soft zoning

: Reason: Hard zoning disabled
Explanation Switched to soft zoning : Reason: Hard zoning disabled due to TCAM programming
failure.
Error Message ZONE-2-ZS_VIRTUAL_DOMAIN_INCONSISTENT: IVR reporting virtual domain

different from rib and domain manager in vsan [dec]
Explanation IVR reporting virtual domain different from rib and domain manager in vsan [dec].
2-646 OL-26589-01
Error Message ZONE-2-ZS_ZONE_BASED_RSCN_DISABLED: Zone based RSCN Generation has

been Disabled. Devices on non ISOLA line cards will not be receiving RSCN
Explanation Devices on one or more line cards will not be receiving RSCN as RSCN generation by
zone has been disabled on this switch
Error Message ZONE-2-ZS_ZONE_LIMIT_EXCEEDED: The limit for maximum number of zones

exceeded
Explanation The number of zones configured has exceeded the maximum number of zones allowed
across all vsans Due to this, distribution or merge operation may fail.
Recommended Action Make sure the number of zones is less than the maximum allowed across all
vsans.
Error Message ZONE-2-ZS_ZONE_SET_LIMIT_EXCEEDED: The limit for maximum number of

zonesets exceeded
Explanation The number of zonesets configured has exceeded the maximum number of zonesets
allowed across all vsans Due to this, distribution or merge operation may fail.
Recommended Action Make sure the number of zonesets is less than the maximum allowed across
all vsans.
ZONE-3
Error Message ZONE-3-LZ_UNKNOWN_MSG: Recvd. from Node=[dec] SAP=[dec]
Explanation The LUN/Read-only zoning process has received an unknown message from
[dec]].[dec]. This information is for debugging only.
Error Message ZONE-3-ZS_ACTIVATION_FAILED_DUE_TO_QOS_DISABLED: Activation failed

due to qos not enabled
Explanation Activation of zoneset failed due to qos not enabled
Recommended Action Make sure qos is enabled and reactivate the zoneset in vsan.
OL-26589-01 2-647
ZONE-4
Error Message ZONE-4-LZ_OTHER_CMD_TO_ZONED_OUT_LUN: FCP command [hex] received

from SID=[chars] to DID=[chars] for LUN=[chars]
Explanation The LUN/Read-only zoning process has received. FCP command [int] from SID [char]
to DID [char] for a zoned out LUN [char].
Error Message ZONE-4-ROZ_WRITE_ACCESS_TO_READ_ONLY_LUN: FCP command [hex] received

from SID=[chars] to DID=[chars] for LUN=[chars]
Explanation The LUN/Read-only zoning process has received FCP command [int] from SID [char]
to DID [char] for a read-only LUN [char].
Error Message ZONE-4-ZS_BROADCAST_LUN_WARNING: LUN member(s) and Broadcast

attribute are present in zone [chars] in vsan [dec]. Broadcast violations can occur
for LUN members.
Explanation Broadcast violations can happen in zone [chars] in vsan [dec] since it has LUN zone
members.
Error Message ZONE-4-ZS_CHANGE_LC_UPGRADE_IN_PROGRESS: Change protocol request is

received from domain [dec] when linecard upgrade is in progress
Explanation A change request has been received from domain [dec] when a linecard upgrade is in
progress. The change request is rejected.
Error Message ZONE-4-ZS_DB_WARNING: [chars]
Explanation Database operation warning: [chars].
Error Message ZONE-4-ZS_DOMAIN_MGR_WARNING: Unable to retrieve domain info from

domain mgr error: [chars] in vsan [dec]
Explanation Unable to retrieve info of domain from domain manager, error: [chars] in vsan [dec].
2-648 OL-26589-01
Error Message ZONE-4-ZS_FC2_OPER_FAILED: FC2 [chars] operation failed : [chars]
Explanation Zone Server FC2 [chars] operation failed : [chars].
Error Message ZONE-4-ZS_IF_PORT_MODE_CONFLICT: Port mode conflict for if [chars]
Explanation Port mode conflict for if [chars]
Recommended Action Shutdown/no shutdown the interface
Error Message ZONE-4-ZS_INVALID_FPORT_WWN_MEMBER: Virtual device fwwn: [chars] is

not a valid zone/alias member virtual name: [chars] pwwn: [chars]
ExplanationVirtual device fwwn: [chars] is not a valid zone/alias member, virtual name: [chars]
pwwn: [chars].
Error Message ZONE-4-ZS_LC_UPGRADE_CHANGE_IN_PROGRESS: Linecard upgrade request is

received when change protocol is in progress
Explanation A request for linecard upgrade has been received when change protocol is in progress.
The linecard upgrade will occur after the completion of the change protocol.
Error Message ZONE-4-ZS_LICENSE_EXPIRY_WARNING: Feature [chars] evaluation license

[chars] expiry in [dec] days
Explanation Feature [chars1] will exceed

itsevaluationtimeperiodin[dec]daysandwillbeshutdownunlessapermanentlicense[chars2]isinstalled.
'
Error Message ZONE-4-ZS_MEMBER_CONVERSION_FAILED: Zone Member conversion failed

for [chars]. Error: [chars]
Explanation Zone Member conversion has failed in : [chars] due to error: [chars]
OL-26589-01 2-649
Error Message ZONE-4-ZS_NON_INTEROPERABLE_ZONE_SET: Non interoperable active

zoneset present on VSAN [dec] in interoperability mode
Explanation Active zoneset has non interoperable members (FCID, FWWN, ..) when
interoperability mode is turned on the VSAN [dec].
Recommended Action Turn off interoperability mode OR make sure that active zoneset has only
interoperable members (PWWN).
Error Message ZONE-4-ZS_QOS_LUN_WARNING: LUN member(s) and QoS attribute are

present in zone [chars] in vsan [dec]. QoS will not be applicable for LUN members.
Explanation QoS will not be applicable to LUN zone members in zone [chars] in vsan [dec].
Error Message ZONE-4-ZS_SDV_VIRT_REAL_CONFLICT_WARNING: Virtual and Real devices

are zoned together or zoned with same device. virtual name: [chars] pwwn: [chars]
ExplanationVirtual and Real devices are zoned together or zoned with same device, virtual name:
[chars] pwwn: [chars].
Error Message ZONE-4-ZS_TOO_MANY_ALIAS_IN_CURRENT_INTEROP_MODE: Too many aliases

in current interoperability mode
Explanation Too many aliases configured in current interoperability mode on the VSAN. Due to
this, the next zoneset activation, distribution or merge operation may fail.
Recommended Action Set the interoperability mode to appropriate value OR make sure the number
of aliases is less than the maximum allowed in the current interoperability mode.
Error Message ZONE-4-ZS_UNSUPPORTED_MEMBER_IN_CURRENT_INTEROP_MODE: Unsupported

member present in active or full zoneset in current interoperability mode
Explanation Active or full zoneset has members that are not supported in the current interoperability
mode set on the VSAN.
Recommended Action Set the interoperability mode to appropriate value OR make sure that active or
full zoneset has only supported members in the current interoperability mode.
ZONE-5
Error Message ZONE-5-ZS_EXPORT_IMPORT_COMPLETE: [chars] operation completed
Explanation [chars] (Export/Import) operation completed.
2-650 OL-26589-01
Error Message ZONE-5-ZS_POLICY_CHANGE: Default zoning policy changed to [chars]
Explanation Default zoning policy changed to (permit/deny).
Error Message ZONE-5-ZS_ZONE_SET_ACTIVATED: Zoneset [chars] activated
Explanation Zoneset [chars] activated.
Error Message ZONE-5-ZS_ZONE_SET_DEACTIVATED: Zoneset deactivated
Explanation Zoneset deactivated.
ZONE-6
Error Message ZONE-6-LZ_BECAME_ACTIVE: LUN/Read-only zoning process became ACTIVE

from standby mode
Explanation The LUN/Read-only zoning process on the standby supervisor became active.
Error Message ZONE-6-LZ_BECAME_STDBY: LUN/Read-only zoning process became STANDBY

from active mode
Explanation The LUN/Read-only zoning process became standby from active mode.
Error Message ZONE-6-LZ_FAILED_TO_SEND_HEARTBEAT: LUN/Read-only zoning process

failed to send heartbeat to system manager: Reason=[chars]
Explanation The LUN/Read-only zoning process was unable to send heartbeat to the system
manager.
Error Message ZONE-6-LZ_GENERAL_EVENT: [chars]
Explanation The LUN/Read-only zoning process has generated an important event. The description
of the event is [str].
OL-26589-01 2-651
Error Message ZONE-6-LZ_INQUIRY_TO_ZONED_OUT_LUN: INQUIRY command received from

SID=[chars] to DID=[chars] for LUN=[chars]
Explanation The LUN/Read-only zoning process has received INQUIRY FCP command from SID
[char] to DID [char] for a zoned out LUN [char].
Error Message ZONE-6-LZ_REPORT_LUNS_CMD_RCVD: REPORT LUNS command received from

SID=[chars] to DID=[chars] for LUN=[chars]
Explanation The LUN/Read-only zoning process has received REPORT LUNS FCP command from
SID [char] to DID [char] for LUN [char].
Error Message ZONE-6-LZ_REQUEST_SENSE_TO_ZONED_OUT_LUN: REQUEST SENSE command

received from SID=[chars] to DID=[chars] for LUN=[chars]
Explanation The LUN/Read-only zoning process has received. REQUEST SENSE FCP command
from SID [char] to DID [char] for a zoned out LUN [char].
Error Message ZONE-6-LZ_SERVICE_UP: LUN/Read-only zoning Process initialized

[chars]
Explanation The LUN/Read-only zoning process is up. The process was initialized in [char] mode.
Error Message ZONE-6-LZ_SWITCHOVER: LUN/Read-only zoning process switching over to

other supervisor.
Explanation The LUN/Read-only zoning process has successfully switched over to the standby
supervisor card.
Error Message ZONE-6-ZS_CHANGE_ACA_REJECTED: ACA received from remote domain [dec]

is rejected
Explanation Received invalid ACA from domain [dec]. Either the domain list do not match OR
authorization has already been acquired by another switch.
2-652 OL-26589-01
Error Message ZONE-6-ZS_FC2_OPER_INFO: FC2 [chars] operation failed : [chars]
Explanation Zone Server FC2 [chars] operation failed : [chars].
Error Message ZONE-6-ZS_INIT_PROCESS: Zone Server process started [chars] at

[chars]
Explanation Zone Server process started in [chars] (stateless/stateful) mode at time [chars].
Error Message ZONE-6-ZS_INIT_WARNING: [chars]
Explanation Warning during Zone Server Initialization: [chars].
Error Message ZONE-6-ZS_INVALID_MEMBER: Invalid member [dec] [chars]
Explanation Invalid member type [dec] [chars] recieved from the API call.
Recommended Action
Error Message ZONE-6-ZS_UNKNOWN_LIC_FEATURE: [chars]
Explanation Zone Server received an event for an known licensing feature: [chars].
OL-26589-01 2-653
2-654 OL-26589-01

NX Os

Uploaded by

NX Os

Uploaded by

Cisco MDS 9000 Family and Nexus 7000

Series NX-OS System Messages Reference

Text Part Number: OL-26589-01

Document Conventions xviii

Documentation Feedback xviii

Obtaining Documentation and Submitting a Service Request xix

CHAPTER 1 Introduction to System Messages for Cisco NX-OS 1-1

System Log Message Format 1-1

Capturing System Messages and History 1-5

BIOS DAEMON-5 2-32

IMAGE_DNLD Messages 2-213

MFDM Messages 2-304

ORI_FWD Messages 2-331

Chapter Title Description

Screen examples use these conventions:

This document uses the following conventions:

Obtaining Documentation and Submitting a Service Request

System Log Message Format

Syslog Format On a Resident Switch

Table 1-1 System Log Message Format Description

Table 1-1 System Log Message Format Description (continued)

Table 1-2 System Message Severity Levels

MNEMONIC is a code that uniquely identifies the system message.

Table 1-3 Representation of Variable Fields in System Messages

Representation Type of Information

Table 1-3 Representation of Variable Fields in System Messages

Representation Type of Information

Syslog Format On a Remote-Logging Server

Table 1-4 System Log Message Format Description

Table 1-4 System Log Message Format Description (continued)

Table 1-5 System Log Message Format description

MNEMONIC is a code that uniquely identifies the system message.

Table 1-6 Representation of Variable Fields in System Messages

Representation Type of Information

Alarm/event code= SYSTEM_MSG

Capturing System Messages and History

Saving the System Messages Log

Logging System Messages to a Syslog Server

Error Message AAA-1-AAA_SESSION_LIMIT_REJECT: aaa request rejected as maximum aaa

Error Message AAA-2-AAA_NVRAM_UPGRADE_FAILURE: upgrading of accounting log failed.

Explanation Upgrading of accounting log failed.

Error Message AAA-2-AAA_PROGRAM_EXIT: aaa daemon exiting: [chars]

Explanation Aaa daemon is exiting.

Error Message AAA-3-AAA_NVRAMFAILURE: nvram failure

Error Message AAA-6-AAA_ACCOUNTING_MESSAGE: [chars]

Explanation Accounting Message

Recommended Action No action is required.

Error Message AAM-2-ELS_FC2_GL_SINDEX_LOOKUP_FAILED: Failed to lookup global port

Explanation Failed to lookup global port index for interface [chars]

Recommended Action No action is required.

Error Message AAM-3-ALLOC_FAILED: Failed in File:[chars] Line:[dec] for type [dec]

Recommended Action No action is required.

Error Message AAM-3-ASSERTION_FAILED: Failed in File:[chars] Line:[dec]

Explanation AAM Process assertion failed in File:[chars], at line:[dec]

Recommended Action No action is required.

Error Message ACLLOG-4-ACLLOG_MAXFLOW_REACHED: [chars]

Explanation Max flow reached in current interval: [chars]

Recommended Action No action is required.

Error Message ACLLOG-4-ACLLOG_THRESHOLD: [chars]

Explanation Threshold Reached for Flow: [chars]

Recommended Action No action is required.

Error Message ACLLOG-6-ACLLOG_FLOW_INTERVAL: [chars]

Explanation Flow info in current alert interval: [chars]

Recommended Action No action is required.

Error Message ACLLOG-6-ACLLOG_NEW_FLOW: [chars]

Explanation New Acllog Flow: [chars]

Recommended Action No action is required.

Error Message ACLMGR-2-ACLMGR_COMMIT_FAIL: Commit failed: [chars]

Explanation The PPF commit failed

Recommended Action No action is required.

Error Message ACLMGR-2-ACLMGR_NO_ERRDISABLED: [chars] event on interface [chars]

Recommended Action No action is required.

Error Message ACLMGR-2-EXITING: Exit reason: [chars]

Recommended Action No action is required.

Error Message ACLMGR-2-INITFAIL: ACLMGR Service Init failed: [chars]

Recommended Action No action is required.