SL Nx-Os

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
Cisco MDS 9000 Family and Nexus 7000 Series NX-OS System Messages Reference
July 27, 2011
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-24654-01
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
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 UCBs 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 of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R) 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 2011 Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface
xvii xvii xvii ii-xvii xviii
Audience
Organization
Document Conventions
Obtaining Documentation and Submitting a Service Request

1
CHAPTER
Introduction to System Messages for Cisco NX-OS System Log Message Format 1-1 Syslog Format On a Resident Switch 1-1 Syslog Format On a Remote-Logging Server Capturing System Messages and History 1-5 Saving the System Messages Log 1-5 Logging System Messages to a Syslog Server
1-1
1-3
1-5
CHAPTER
System Messages and Recovery Procedures for the Cisco MDS 9000 and Nexus 7000 Family 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-6 ACLQOS Messages 2-7 ACLQOS-SLOT#-2 2-7 ACLQOS-SLOT#-3 2-8
2-1
Cisco MDS 9000 Family and Nexus 7000 Series NX-OS System Messages Reference OL-24654-01
Contents
ACLQOS-SLOT#-4 2-9 ACLQOS-SLOT#-5 2-10 ACLTCAM Messages 2-10 ACLTCAM-2 2-11 ACLTCAM-3 2-14 ACLTCAM-4 2-15 ACLTCAM-6 2-16 ACL Messages 2-17 ACL-2 2-17 ACL-3 2-19 ACL-4 2-19 ACL-5 2-19 ACL-6 2-19 AMM Messages 2-21 AMM-SLOT#-0 2-21 AMM-SLOT#-2 2-21 AMM-SLOT#-6 2-22 ASCII-CFG Messages 2-22 ASCII-CFG-2 2-22 ASCII-CFG-3 2-23 ASCII-CFG-6 2-23 ASSOC MGR Messages 2-25 ASSOC MGR-0 2-25 ASSOC MGR-1 2-25 ASSOC MGR-2 2-25 ASSOC MGR-3 2-25 ASSOC MGR-4 2-25 ASSOC MGR-5 2-26 ASSOC MGR-6 2-26 ASSOC MGR-7 2-27 BFDC Messages 2-27 BFDC-SLOT#-2 2-27 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 BIOS DAEMON-5 2-32
ii
OL-24654-01
Contents
BIOS DAEMON-SLOT#-2 2-32 BIOS DAEMON-SLOT#-5 2-32 BOOTUP TEST Messages 2-32 BOOTUP TEST-2 2-33 BOOTVAR Messages 2-33 BOOTVAR-2 2-33 BOOTVAR-3 2-34 BOOTVAR-5 2-35 BOOTVAR-6 2-36 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 CLOUD Messages 2-51 CLOUD-2 2-51 CLOUD-3 2-52 CLOUD-6 2-52 CLUSTER Messages 2-52 CLUSTER-2 2-53
iii
Contents
CMOND Messages 2-53 CMOND-2 2-53 CMPPROXY Messages 2-53 CMPPROXY-2 2-54 CMPPROXY-5 2-54 CMPPROXY-6 2-55 COPP Messages 2-55 COPP-1 2-55 COPP-2 2-55 COPP-3 2-56 COPP-4 2-57 COPP-5 2-57 COPP-6 2-57 COPP-7 2-58 CREDITMON Messages 2-58 CREDITMON-SLOT#-2 2-58 CTS Messages 2-59 CTS-2 2-59 CTS-3 2-62 CTS-5 2-62 CTS-6 2-62 DCEFIB Messages 2-62 DCEFIB-SLOT#-0 2-63 DCEFIB-SLOT#-2 2-63 DCEFIB-SLOT#-6 2-63 DEBUGPROXY Messages 2-64 DEBUGPROXY-6 2-64 DEVICE-ALIAS Messages 2-64 DEVICE-ALIAS-2 2-64 DEVICE-ALIAS-3 2-65 DEVICE-ALIAS-6 2-68 DEVICE_TEST Messages 2-70 DEVICE_TEST-2 2-70 DEVICE_TEST-3 2-73 DEVICE_TEST-4 2-74 DEVICE_TEST-5 2-74 DEVICE_TEST-6 2-74 DEV_LOG Messages 2-74 DEV_LOG-3 2-75 DEV_LOG-SLOT#-4 2-75
iv
OL-24654-01
Contents
DFTM Messages 2-75 DFTM-SLOT#-2 2-75 DFTM-SLOT#-3 2-76 DHCP_SNOOP Messages 2-78 DHCP_SNOOP-2 2-78 DHCP_SNOOP-3 2-78 DHCP_SNOOP-4 2-80 DHCP_SNOOP-5 2-82 DHCP_SNOOP-6 2-83 DIAGCLIENT Messages 2-84 DIAGCLIENT-2 2-85 DIAGCLIENT-3 2-85 DIAGCLIENT-4 2-86 DIAGCLIENT-5 2-86 DIAGMGR Messages 2-87 DIAGMGR-2 2-87 DIAGMGR-3 2-88 DIAGMGR-4 2-88 DIAGMGR-5 2-89 DIAGMGR-6 2-90 DIAG_PORT_LB Messages 2-90 DIAG_PORT_LB-2 2-91 DIAG_PORT_LB-3 2-92 DIAG_PORT_LB-4 2-95 DIAG_PORT_LB-5 2-95 DMM Messages 2-96 DMM-SLOT#-5 2-96 DOT1X Messages 2-98 DOT1X-2 2-98 DOT1X-3 2-98 DOT1X-4 2-99 DOT1X-5 2-100 DPP_DEBUG Messages 2-101 DPP_DEBUG-2 2-102 DPVM Messages 2-102 DPVM-2 2-102 DPVM-3 2-102 DPVM-4 2-103 DPVM-6 2-103 DSTATS Messages 2-104
Contents
DSTATS-2 2-104 DSTATS-3 2-104 ELTMC Messages 2-106 ELTMC-SLOT#-2 2-106 ELTM Messages 2-107 ELTM-2 2-108 ELTM-5 2-108 ELTM-6 2-109 EOU Messages 2-109 EOU-2 2-109 EOU-5 2-109 EOU-6 2-109 EOU-7 2-111 EPLD_UPGRADE Messages 2-112 EPLD_UPGRADE-2 2-112 EPP Messages 2-112 EPP-5 2-112 ETH-PORT-SEC Messages 2-112 ETH-PORT-SEC-3 2-113 ETH-PORT-SEC-5 2-114 ETHPORT Messages 2-115 ETHPORT-2 2-115 ETHPORT-3 2-116 ETHPORT-4 2-117 ETHPORT-5 2-117 ETH_PORT_CHANNEL Messages 2-128 ETH_PORT_CHANNEL-1 2-128 ETH_PORT_CHANNEL-2 2-129 ETH_PORT_CHANNEL-3 2-129 ETH_PORT_CHANNEL-4 2-131 ETH_PORT_CHANNEL-5 2-132 ETH_PORT_CHANNEL-6 2-134 ETH_PORT_CHANNEL-7 2-134 EUREKA_USD Messages 2-135 EUREKA_USD-3 2-135 EVMC Messages 2-135 EVMC-3 2-136 EVMC-4 2-136 EVMC-5 2-136 EVMS Messages 2-136
vi
OL-24654-01
Contents
EVMS-2 2-137 EVMS-4 2-137 EVMS-6 2-137 EXCEPTIONLOG Messages 2-137 EXCEPTIONLOG-SLOT#-2 2-138 FABRICPATH Messages 2-138 FABRICPATH-2 2-138 FABRICPATH-4 2-138 FABRICPATH-6 2-138 FC-TUNNEL Messages 2-140 FC-TUNNEL-3 2-140 FC-TUNNEL-5 2-142 FCC_LC Messages 2-142 FCC_LC-2 2-142 FCC_LC-5 2-143 FCC_LC-6 2-144 FCC Messages 2-144 FCC-2 2-144 FCC-5 2-144 FCC-6 2-145 FCDDH Messages 2-145 FCDDH-SLOT#-3 2-145 FCDDH-SLOT#-4 2-145 FCDDH-SLOT#-5 2-146 FCDD Messages 2-146 FCDD-SLOT#-3 2-146 FCDD-SLOT#-4 2-146 FCDD-SLOT#-5 2-146 FCDD-SLOT#-7 2-147 FCDOMAIN Messages 2-147 FCDOMAIN-2 2-148 FCDOMAIN-3 2-151 FCDOMAIN-4 2-153 FCDOMAIN-5 2-154 FCDOMAIN-6 2-155 FCDOMAIN-7 2-161 FCD Messages 2-163 FCD-7 2-163 FCFWD Messages 2-163 FCFWD-3 2-163
vii
Contents
FCFWD-4 2-163 FCFWD-6 2-164 FCNS Messages 2-164 FCNS-2 2-164 FCNS-3 2-165 FCNS-4 2-166 FCNS-6 2-166 FCOE_MGR Messages 2-166 FCOE_MGR-2 2-166 FCOE_MGR-5 2-167 FCSP-MGR Messages 2-168 FCSP-MGR-2 2-168 FCS Messages 2-170 FCS-2 2-170 FCS-3 2-171 FCS-5 2-172 FCS-6 2-173 FDMI Messages 2-173 FDMI-2 2-173 FDMI-3 2-174 FDMI-4 2-175 FDMI-6 2-175 FEATURE-MGR Messages 2-176 FEATURE-MGR-2 2-176 FEATURE-MGR-6 2-179 FEX Messages 2-179 FEX-2 2-179 FEX-5 2-180 FICON Messages 2-181 FICON-2 2-181 FICON-3 2-182 FICON-5 2-183 FICON-6 2-183 FLOGI Messages 2-184 FLOGI-1 2-184 FLOGI-2 2-185 FLOGI-4 2-185 FLOGI-5 2-185 FS-DAEMON Messages 2-186 FS-DAEMON-2 2-186
viii
OL-24654-01
Contents
FS-DAEMON-6 2-187 FSCM Messages 2-187 FSCM-2 2-187 FSPF Messages 2-188 FSPF-2 2-188 FSPF-2 2-188 FSPF-4 2-190 FSPF-5 2-191 FSPF-6 2-192 FSPF-7 2-193 GLBP Messages 2-193 GLBP-2 2-193 GLBP-3 2-193 GLBP-4 2-195 GLBP-5 2-197 HSRP_ENGINE Messages 2-199 HSRP_ENGINE-3 2-199 HSRP_ENGINE-4 2-200 HSRP_ENGINE-5 2-201 HSRP_ENGINE-6 2-203 IKE Messages 2-203 IKE-3 2-203 IKE-4 2-205 IKE-6 2-205 ILC-SPAN Messages 2-205 ILC-SPAN-3 2-206 ILC_HELPER Messages 2-206 ILC_HELPER-2 2-206 ILC_HELPER-3 2-206 ILC_HELPER-6 2-206 IMAGE_DNLD Messages 2-207 IMAGE_DNLD-SLOT#-2 2-207 IMAGE_DNLD-SLOT#-4 2-208 IMAGE_DNLD-SLOT#-5 2-208 IMAGE_UPGRADE Messages 2-208 IMAGE_UPGRADE-SLOT#-2 2-208 IMAGE_UPGRADE-SLOT#-4 2-209 IM Messages 2-209 IM-3 2-209 IM-5 2-210
ix
Contents
INTERFACE_VLAN Messages 2-210 INTERFACE_VLAN-4 2-210 INTERFACE_VLAN-5 2-211 IOA_LC Messages 2-213 IOA_LC-5 2-213 IPACL Messages 2-213 IPACL-0 2-213 IPACL-1 2-213 IPACL-2 2-214 IPACL-3 2-214 IPACL-4 2-214 IPACL-5 2-214 IPACL-6 2-214 IPFC Messages 2-215 IPFC-2 2-215 IPFC-3 2-215 IPFC-5 2-215 IPFC-6 2-216 IPQOSMGR Messages 2-216 IPQOSMGR-2 2-216 IPQOSMGR-3 2-217 IPQOSMGR-4 2-218 IPQOSMGR-6 2-218 IPSEC Messages 2-219 IPSEC-2 2-219 IPSEC-3 2-219 IPSEC-5 2-220 IPS_SB_MGR Messages 2-221 IPS_SB_MGR-SLOT#-2 2-221 IPS_SB_MGR-SLOT#-3 2-222 IPS_SB_MGR-SLOT#-4 2-222 IPS_SB_MGR-SLOT#-6 2-223 IPS Messages 2-223 IPS-2 2-223 IPS-3 2-223 IPS-4 2-229 IPS-5 2-230 IPS-6 2-238 IPS-7 2-238 IPV6 Messages 2-239
OL-24654-01
Contents
IPV6-2 2-239 IPV6-3 2-240 IPV6-4 2-240 IPV6-6 2-240 IP Messages 2-241 IP-1 2-241 IP-2 2-241 IP-3 2-241 IP-4 2-242 IP-6 2-242 ISAPI Messages 2-243 ISAPI-SLOT#-0 2-243 ISAPI-SLOT#-1 2-244 ISAPI-SLOT#-2 2-244 ISAPI-SLOT#-3 2-245 ISAPI-SLOT#-4 2-246 ISAPI-SLOT#-5 2-246 ISAPI-SLOT#-6 2-247 ISAPI-SLOT#-7 2-248 ISNS Messages 2-248 ISNS-2 2-249 IVR Messages 2-249 IVR-2 2-249 IVR-3 2-253 IVR-4 2-260 IVR-5 2-262 IVR-6 2-265 IVR-7 2-266 L2FMC Messages 2-266 L2FMC-SLOT#-0 2-266 L2FMC-SLOT#-2 2-267 L2FMC-SLOT#-5 2-267 L2FMC-SLOT#-6 2-267 L2FM Messages 2-268 L2FM-0 2-269 L2FM-1 2-269 L2FM-2 2-270 L2FM-4 2-271 L2FM-6 2-271 L2MCAST Messages 2-272
xi
Contents
L2MCAST-SLOT#-0 2-272 L2MCAST-SLOT#-2 2-272 L2MCAST-SLOT#-6 2-272 L3VM Messages 2-273 L3VM-5 2-273 LACP Messages 2-274 LACP-3 2-274 LACP-5 2-275 LC-FCFWD Messages 2-276 LC-FCFWD-3 2-277 LC-SPAN Messages 2-277 LC-SPAN-3 2-277 LC_CFG Messages 2-277 LC_CFG-SLOT#-2 2-277 LC_PORT_CHANNEL Messages 2-278 LC_PORT_CHANNEL-SLOT#-0 2-278 LC_PORT_CHANNEL-SLOT#-3 2-278 LC_PORT_MGR Messages 2-278 LC_PORT_MGR-SLOT#-2 2-279 LC_RDL Messages 2-279 LC_RDL-3 2-279 LC_RDL-6 2-280 LDAP Messages 2-280 LDAP-2 2-281 LDAP-3 2-281 LDAP-5 2-281 LDAP-6 2-281 LDP Messages 2-282 LDP-5 2-282 LIBBASE_SVC Messages 2-282 LIBBASE_SVC-2 2-282 LIBBASE_SVC-4 2-282 LIBBASE_SVC-5 2-283 LIBGD Messages 2-283 LIBGD-2 2-283 LIBGD-3 2-284 LIBGD-5 2-284 LIBGD-6 2-284 LICMGR Messages 2-285 LICMGR-0 2-285
xii
OL-24654-01
Contents
LICMGR-1 2-285 LICMGR-2 2-286 LICMGR-3 2-287 LICMGR-4 2-288 LICMGR-6 2-288 LLDP Messages 2-289 LLDP-3 2-289 LLDP-5 2-290 LLDP-6 2-290 MAC Messages 2-290 MAC-SLOT#-2 2-290 MCAST Messages 2-290 MCAST-2 2-291 MCAST-4 2-291 MCAST-5 2-291 MCECTEST Messages 2-291 MCECTEST-3 2-291 MCECTEST-5 2-292 MCECTEST-6 2-292 MCM Messages 2-292 MCM-2 2-293 MCM-5 2-293 MCM-6 2-293 MFDM Messages 2-294 MFDM-2 2-294 MODULE Messages 2-294 MODULE-2 2-295 MODULE-3 2-298 MODULE-4 2-299 MODULE-5 2-299 MODULE-6 2-301 MONITOR Messages 2-301 MONITOR-5 2-301 NFM Messages 2-302 NFM-2 2-302 NFM-3 2-303 NFM-4 2-304 NFM-5 2-305 NFM-6 2-305 NFM-7 2-306
xiii
Contents
NFP Messages 2-306 NFP-SLOT#-2 2-306 NFP-SLOT#-5 2-307 NPC Messages 2-308 NPC-SLOT#-3 2-308 NPC-SLOT#-4 2-308 NPC-SLOT#-5 2-308 NPV Messages 2-308 NPV-2 2-309 NPV-3 2-309 NPV-4 2-312 NPV-5 2-313 NPV-6 2-314 NPV-7 2-317 NTP Messages 2-317 NTP-2 2-318 NTP-3 2-318 NTP-6 2-319 NVP Messages 2-319 NVP-6 2-319 NVP-SLOT#-2 2-320 OC_USD Messages 2-320 OC_USD-2 2-320 ORI_FWD Messages 2-320 ORI_FWD-2 2-320 ORI_FWD-6 2-320 ORI_MAC Messages 2-320 ORI_MAC-2 2-321 ORI_MAC-6 2-321 OTM Messages 2-321 OTM-2 2-321 OTM-3 2-321 OTM-5 2-321 OTM-6 2-322 PHY_USD Messages 2-322 PHY_USD-SLOT#-4 2-323 PIXM Messages 2-323 PIXM-2 2-323 PIXM-3 2-323 PIXM-4 2-323
xiv
OL-24654-01
Contents
PIXM-7 2-324 PLATFORM Messages 2-324 PLATFORM-0 2-324 PLATFORM-1 2-327 PLATFORM-2 2-328 PLATFORM-3 2-340 PLATFORM-4 2-342 PLATFORM-5 2-342 PLATFORM-6 2-344 PLATFORM-7 2-344 PLOG_SUP Messages 2-345 PLOG_SUP-4 2-345 PLOG Messages 2-345 PLOG-4 2-345 PONG Messages 2-345 PONG-5 2-345 PORT-CHANNEL Messages 2-346 PORT-CHANNEL-1 2-346 PORT-CHANNEL-2 2-346 PORT-CHANNEL-3 2-347 PORT-CHANNEL-4 2-348 PORT-CHANNEL-5 2-349 PORT-CHANNEL-6 2-350 PORT-CHANNEL-7 2-350 PORT-PROFILE Messages 2-351 PORT-PROFILE-2 2-351 PORT-PROFILE-3 2-351 PORT-PROFILE-6 2-353 PORT-RESOURCES Messages 2-354 PORT-RESOURCES-3 2-354 PORT-RESOURCES-5 2-355 PORT-SECURITY Messages 2-355 PORT-SECURITY-2 2-355 PORT-SECURITY-3 2-355 PORT-SECURITY-4 2-357 PORT-SECURITY-6 2-358 PORT Messages 2-358 PORT-2 2-358 PORT-3 2-358 PORT-4 2-359
xv
Contents
PORT-5 2-360 PRIVATE_VLAN Messages 2-380 PRIVATE_VLAN-2 2-381 PRIVATE_VLAN-3 2-382 PRIVATE_VLAN-5 2-382 PROC_MGR Messages 2-383 PROC_MGR-SLOT#-2 2-383 PROC_MGR-SLOT#-3 2-386 PROC_MGR-SLOT#-4 2-386 PROC_MGR-SLOT#-6 2-386 PSS Messages 2-386 PSS-0 2-386 PSS-1 2-388 PSS-2 2-388 PSS-4 2-389 PSS-5 2-389 PTPLC Messages 2-390 PTPLC-3 2-390 PTP Messages 2-390 PTP-5 2-390 PTP-6 2-391 QOS Messages 2-392 QOS-2 2-392 QOS-3 2-393 QOS-4 2-395 QOS-6 2-395 RADIUS Messages 2-397 RADIUS-2 2-397 RADIUS-3 2-398 RADIUS-4 2-398 RADIUS-5 2-398 RADIUS-6 2-398 RDL Messages 2-399 RDL-2 2-399 RDL-3 2-399 RDL-6 2-400 RES_MGR Messages 2-401 RES_MGR-1 2-401 RES_MGR-2 2-401 RES_MGR-3 2-402
xvi
OL-24654-01
Contents
RES_MGR-4 2-402 RES_MGR-5 2-404 RES_MGR-6 2-404 RIB Messages 2-404 RIB-0 2-404 RIB-1 2-404 RIB-2 2-405 RIB-3 2-405 RIB-4 2-406 RIB-5 2-407 RIB-6 2-407 RLIR Messages 2-407 RLIR-2 2-407 RLIR-6 2-408 RM Messages 2-409 RM-6 2-409 RM-SLOT#-2 2-409 RM-SLOT#-4 2-410 RSCN Messages 2-410 RSCN-2 2-410 RSCN-4 2-411 RSCN-6 2-411 SAL Messages 2-412 SAL-5 2-412 SAN_EXT_TUNER Messages 2-412 SAN_EXT_TUNER-3 2-412 SCHEDULER Messages 2-412 SCHEDULER-2 2-413 SCHEDULER-3 2-413 SCHEDULER-4 2-414 SCHEDULER-6 2-414 SCM Messages 2-414 SCM-2 2-414 SCSI-TARGET Messages 2-414 SCSI-TARGET-2 2-415 SCSI-TARGET-3 2-415 SCSI-TARGET-7 2-417 SDV Messages 2-417 SDV-2 2-417 SDV-3 2-418
xvii
Contents
SDV-4 2-420 SDV-6 2-420 SDV-7 2-420 SECURITYD Messages 2-420 SECURITYD-2 2-420 SECURITYD-3 2-422 SECURITYD-6 2-422 SENSOR_USD Messages 2-423 SENSOR_USD-2 2-423 SENSOR_USD-3 2-424 SENSOR_USD-5 2-425 SENSOR_MGR Messages 2-425 SENSOR_MGR-2 2-425 SENSOR_MGR-3 2-425 SENSOR_MGR-4 2-426 SFC Messages 2-426 SFC-3 2-426 SFM Messages 2-426 SFM-2 2-426 SFM-6 2-426 SKSD Messages 2-427 SKSD-2 2-427 SKSD-3 2-427 SKSD-4 2-427 SKSD-5 2-428 SKSD-6 2-429 SKT_USD Messages 2-429 SKT_USD-3 2-430 SKT_USD-6 2-430 SME_CPP Messages 2-430 SME_CPP-2 2-430 SME_CPP-3 2-431 SME_CPP-5 2-436 SME_CPP-SLOT#-2 2-441 SME_CPP-SLOT#-3 2-442 SME_CPP-SLOT#-4 2-445 SNMPD Messages 2-445 SNMPD-1 2-445 SNMPD-2 2-446 SNMPD-3 2-446
xviii
OL-24654-01
Contents
SNMPD-4 2-446 SNMPD-5 2-446 SNMPD-6 2-446 SNMPD-7 2-447 SPAN Messages 2-447 SPAN-2 2-447 SPAN-3 2-447 SPAN-5 2-448 SPAN-6 2-449 SPI Messages 2-449 SPI-SLOT#-2 2-449 STP Messages 2-449 STP-2 2-450 STP-3 2-457 STP-4 2-458 STP-6 2-459 SVC_BATTERY Messages 2-461 SVC_BATTERY-SLOT#-2 2-461 SVC_BATTERY-SLOT#-4 2-463 SVC_BATTERY-SLOT#-6 2-463 SVC Messages 2-464 SVC-0 2-464 SVC-1 2-464 SVC-2 2-464 SVC-3 2-465 SVC-4 2-477 SVC-5 2-486 SVC-6 2-486 SVC-7 2-501 SYSMGR Messages 2-501 SYSMGR-2 2-502 SYSMGR-3 2-525 SYSMGR-4 2-534 SYSMGR-5 2-536 SYSMGR-6 2-541 SYSMGR-7 2-543 SYSTEMHEALTH Messages 2-545 SYSTEMHEALTH-2 2-545 SYSTEMHEALTH-4 2-548 SYSTEMHEALTH-5 2-553
xix
Contents
SYSTEMHEALTH-6 2-555 TACACS Messages 2-557 TACACS-2 2-557 TACACS-3 2-557 TACACS-4 2-557 TACACS-5 2-557 TACACS-6 2-558 TBIRD_CMN_USD Messages 2-558 TBIRD_CMN_USD-6 2-558 TBIRD_FWD_USD Messages 2-558 TBIRD_FWD_USD-6 2-559 TBIRD_MAC_USD Messages 2-559 TBIRD_MAC_USD-3 2-559 TBIRD_MAC_USD-6 2-559 TBIRD_QUE_USD Messages 2-559 TBIRD_QUE_USD-6 2-559 TBIRD_XBAR_USD Messages 2-559 TBIRD_XBAR_USD-6 2-560 TCAP Messages 2-560 TCAP-2 2-560 TPC Messages 2-560 TPC-SLOT#-5 2-560 TTYD Messages 2-561 TTYD-2 2-561 TTYD-3 2-562 TTYD-6 2-562 TUNNEL Messages 2-562 TUNNEL-2 2-562 TUNNEL-3 2-563 TUNNEL-4 2-563 TUNNEL-5 2-563 TUNNEL-7 2-565 U2RIB Messages 2-565 U2RIB-2 2-565 U2RIB-3 2-565 U2RIB-5 2-565 U2RIB-6 2-566 UDLD Messages 2-566 UDLD-3 2-566 UDLD-4 2-567
xx
OL-24654-01
Contents
UDLD-5 2-567 UFDM Messages 2-568 UFDM-2 2-568 VDC_MGR Messages 2-568 VDC_MGR-2 2-568 VDC_MGR-3 2-569 VDC_MGR-5 2-570 VEC Messages 2-571 VEC-SLOT#-3 2-571 VEC-SLOT#-4 2-571 VEC-SLOT#-5 2-571 VEDB_MGR Messages 2-575 VEDB_MGR-2 2-575 VEDB_MGR-6 2-575 VES Messages 2-575 VES-SLOT#-4 2-576 VES-SLOT#-5 2-576 VFC Messages 2-577 VFC-3 2-577 VFC-6 2-577 VLAN_MGR Messages 2-577 VLAN_MGR-2 2-578 VLAN_MGR-3 2-578 VLAN_MGR-4 2-578 VLAN_MGR-5 2-578 VLAN_MGR-6 2-578 VNI Messages 2-579 VNI-2 2-579 VNI-3 2-580 VNI-6 2-580 VPC Messages 2-580 VPC-2 2-580 VPC-3 2-583 VPC-4 2-585 VPC-5 2-586 VPC-6 2-589 VPM Messages 2-592 VPM-2 2-592 VPM-3 2-593 VPM-4 2-594
xxi
Contents
VPM-6 2-594 VPM-SLOT#-2 2-596 VRRP-CFG Messages 2-596 VRRP-CFG-2 2-596 VRRP-CFG-3 2-597 VRRP-CFG-5 2-597 VRRP-ENG Messages 2-597 VRRP-ENG-2 2-597 VRRP-ENG-3 2-598 VRRP-ENG-4 2-599 VRRP-ENG-5 2-599 VRRP-ENG-6 2-600 VSAN Messages 2-600 VSAN-2 2-601 VSAN-3 2-601 VSAN-6 2-601 VSD Messages 2-602 VSD-SLOT#-2 2-602 VSHD Messages 2-603 VSHD-2 2-603 VSHD-3 2-603 VSHD-4 2-604 VSHD-5 2-604 VSHD-7 2-605 WWN Messages 2-605 WWN-1 2-605 WWN-2 2-606 WWN-3 2-607 WWN-4 2-608 WWN-5 2-609 WWN-6 2-609 WWN-7 2-611 XBAR_CLIENT Messages 2-611 XBAR_CLIENT-2 2-611 XBAR_CLIENT-3 2-612 XBAR_CLIENT-SLOT#-2 2-613 XBAR_CLIENT-SLOT#-3 2-614 XBAR Messages 2-614 XBAR-2 2-614 XBAR-3 2-615
xxii
OL-24654-01
Contents
XBAR-5 2-615 XMLMA Messages 2-620 XMLMA-2 2-620 XMLMA-3 2-621 XMLMA-5 2-621 XMLMA-6 2-621 XMLSA Messages 2-621 XMLSA-2 2-621 XMLSA-5 2-622 XMLSA-6 2-622 ZBM Messages 2-622 ZBM-2 2-623 ZBM-4 2-624 ZBM-6 2-625 ZONE Messages 2-626 ZONE-2 2-626 ZONE-3 2-635 ZONE-4 2-635 ZONE-5 2-638 ZONE-6 2-639
xxiii
Contents
xxiv
OL-24654-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 preface describes the audience, organization, and conventions of this guide. It also provides information on how to obtain related documentation.
Audience
This guide is for system administrators who are responsible for managing Cisco NX-OS systems.
Organization
This guide is organized as follows: Chapter Chapter 1 Chapter 2 Title Introduction to System Messages for Cisco NX-OS System Messages and Recovery Procedures for the Cisco MDS 9000 and Nexus 7000 Family Description Describes the structure of system messages and the format of system log files. Lists the messages that may appear in log files, and indicates suggested remedies where applicable for the Cisco MDS and Nexus 7000 Family.
Document Conventions
Command descriptions use these conventions: Convention boldface font italic font Description Commands and keywords are in boldface. Arguments for which you supply values are in italics.
xvii
Preface Document Conventions
[ ] [x|y|z] string Elements in square brackets are optional. Optional alternative keywords are grouped in brackets and separated by vertical bars. 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 boldface screen font italic screen font
Terminal sessions and information that the switch displays are in screen font. Information that you must enter is in boldface 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.
Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly Whats 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 Whats 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.
xviii
OL-24654-01
CH A P T E R
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 month dd hh:mm:ss
Description The date and month of the error or event The time of the error or event
1-1
Chapter 1 System Log Message Format
Table 1-1 System Log Message Format Description (continued)
Element switchname facility severity MNEMONIC %$VDC #%$ %$VRF #%$ description
FACILITY
Description The name of the switch The facility of the error or event (daemon, kernel, VSHD, or other facility) Single-digit code from 0 to 7 that indicates the severity of the message Text string that uniquely describes the system message An optional virtual device context (VDC) ID that appears in the description for messages requiring VDC IDs An optional virtual routing and forwarding (VRF) ID that appears in the description for messages requiring VRF IDs Text string containing detailed information about the event being reported
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 0 emergency 1 alert 2 critical 3 error 4 warning 5 notification 6 informational 7 debugging

MNEMONIC
Description System unusable Immediate action needed Critical condition Error condition Warning condition Normal but significant condition Informational message only Appears during debugging only
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 [dec] [hex]
Type of Information Decimal number Hexadecimal number
1-2
OL-24654-01
Chapter 1
Introduction to System Messages for Cisco NX-OS System Log Message Format
Representation [char] [chars]
Type of Information Single character 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 month dd hh:mm:ss IP-addr-switch facility severity MNEMONIC
Description The date and month of the error or event The time of the error or event The IP address of the switch The facility of the error or event (daemon, kernel, VSHD, or other facility) Single-digit code from 0 to 3 that indicates the severity of the message Text string that uniquely describes the system message
1-3
Chapter 1 System Log Message Format
Table 1-4 System Log Message Format Description (continued)
Element %$VDC #%$ %$VRF #%$ description

FACILITY
Description An optional virtual device context (VDC) ID that appears in the description for messages requiring VDC IDs An optional virtual routing and forwarding (VRF) ID that appears in the description for messages requiring VRF IDs Text string containing detailed information about the event being reported
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 0 emergency 1 alert 2 critical 3 notification

MNEMONIC
Description System unusable Immediate action needed Critical condition Normal but significant condition
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.
Representation [dec] [hex] [char] [chars]
Type of Information Decimal number Hexadecimal number Single character 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-24654-01
Chapter 1
Introduction to System Messages for Cisco NX-OS 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.
Capturing System Messages and History

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.
1-5
Chapter 1 Capturing System Messages and History
1-6
OL-24654-01
CH A P T E R
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 [chars] Explanation AAA-2-AAA_NVRAM_UPGRADE_FAILURE: upgrading of accounting log failed.
Upgrading of accounting log failed.
2-1
Chapter 2
Error Message Explanation AAA-2-AAA_PROGRAM_EXIT: aaa daemon exiting: [chars]
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 No action is required.
Recommended Action
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] No action is required.
Recommended Action
AAM-3
Error Message size [dec] Explanation AAM-3-ALLOC_FAILED: Failed in File:[chars] Line:[dec] for type [dec]
AAM process could not allocate heap memory in File:[chars], at line:[dec], for memory-type:[dec] of Size:[dec] No action is required.
Recommended Action
2-2
OL-24654-01
Chapter 2
Error Message Explanation AAM-3-ASSERTION_FAILED: Failed in File:[chars] Line:[dec]
AAM Process assertion failed in File:[chars], at line:[dec] No action is required.
Recommended Action
ACLLOG Messages
This section contains the ACLLOG messages.
ACLLOG-4
Error Message Explanation ACLLOG-4-ACLLOG_MAXFLOW_REACHED: [chars]
Max flow reached in current interval: [chars] No action is required.
Recommended Action
Error Message Explanation
ACLLOG-4-ACLLOG_THRESHOLD: [chars]
Threshold Reached for Flow: [chars] No action is required.
Recommended Action
ACLLOG-6
Error Message Explanation ACLLOG-6-ACLLOG_FLOW_INTERVAL: [chars]
Flow info in current alert interval: [chars] No action is required.
Recommended Action
ACLLOG-6-ACLLOG_NEW_FLOW: [chars]
New Acllog Flow: [chars] No action is required.
Recommended Action
ACLMGR Messages
This section contains the ACLMGR messages.
2-3
Chapter 2
ACLMGR-2
Error Message Explanation ACLMGR-2-ACLMGR_COMMIT_FAIL: Commit failed: client %llX, [chars]
The PPF commit failed No action is required.
Recommended Action
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

Recommended Action
No action is required.
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. Recommended Action
ACLMGR-2-INITFAIL: ACLMGR Service Init failed: [chars]
ACLMGR Service initialization failed. [chars] explains the reason for the failure. No action is required.
Recommended Action
ACLMGR-2-MALLOC_ERROR: Size [dec] bytes
The ACLMGR service could not allocate memory.
ACLMGR-2-PSS_ERROR: [chars]: PSS ret. val=[dec]
The ACLMGR service encountered error while operating on a persistent storage No action is required.
database.
Recommended Action
2-4
OL-24654-01
Chapter 2
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. No action is required.
Recommended Action
ACLMGR-3-ACLMGR_PPF_ERROR: PPF error: [chars]
The PPF generated error No action is required.
Recommended Action
ACLMGR-3-ACLMGR_PSS_CORRUPTED: [chars] PSS found corrupted
The ACLMGR service has detected corruption in one of its persistent information database. The database would be recreated. No action is required.
Recommended Action
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 No action is required.
been lost
Recommended Action
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 Recommended Action
ACLMGR-3-ACLMGR_VERIFY_FAIL: Verify failed: client %llX, [chars]
The PPF Verify failed No action is required.
Recommended Action
2-5
Chapter 2
Error Message ACLMGR-3-MTSERROR: [chars]
Explanation ACLMGR Service encountered an MTS error. [chars] specifies the context where the error occured. Recommended Action
ACLMGR-4
Error Message Explanation ACLMGR-4-ACLMGR_PPF_WARNING: PPF warning: [chars]
The PPF generated warning No action is required.
Recommended Action
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 Recommended Action
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. Recommended Action
ACLMGR-6
Error Message Explanation ACLMGR-6-ACLMGR_PPF_NOTIF: PPF notification: [chars]
The PPF generated notification No action is required.
Recommended Action
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. Recommended Action
2-6
OL-24654-01
Chapter 2
Error Message Explanation ACLMGR-6-BECAME_STDBY: Became STANDBY from active mode
The ACLMGR service became standby from active mode. No action is required.
Recommended Action
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 No action is required.
Recommended Action
ACLMGR-6-SERVICE_UP: Initialized [chars]
The ACLMGR service is up and ready The service was initialized in [char] mode. No action is required.
Recommended Action
ACLMGR-6-SRVEXIT: ACLMGR Service shutting down gracefully
ACLMGR Service is shutting down gracefully. This is an informational message. No action is required.
Recommended Action
ACLMGR-6-SWITCHOVER: Switching Over to other Sup.
The ACLMGR service has successfully switched over to the standby supervisor card. No action is required.
Recommended Action
ACLQOS Messages
This section contains the ACLQOS messages.
ACLQOS-SLOT#-2
Error Message Explanation ACLQOS-SLOT#-2-ACLQOS_FAILED: ACLQOS failure: [chars]
ACLQOS operation failed in the aclqos client No DDTS.
Recommended Action
2-7
Chapter 2
Error Message ACLQOS-SLOT#-2-ACLQOS_INBAND_INTERFACE_FAILURE: Inband interface lif lookup failed ([chars]) Explanation
Inband interface lif lookup failed No DDTS.
Recommended Action
Error Message [chars] Explanation
ACLQOS-SLOT#-2-ACLQOS_MALLOC_FAILED: Memory allocation failed.
Memory allocation failed. This is a critical failure No DDTS.
Recommended Action
ACLQOS-SLOT#-2-ACLQOS_OOTR: Tcam resource exhausted: [chars]
Tcam resources to program acls exhausted No DDTS.
Recommended Action
ACLQOS-SLOT#-2-PPF_FAILED: Database failure: [chars]
Database operation failed in the aclqos client No DDTS.
Recommended Action
ACLQOS-SLOT#-3
Error Message ACLQOS-SLOT#-3-ACLQOS_CC_INVALID: Invalid Congestion Control parameters: [chars] Explanation
Invalid Congestion Control parameters No DDTS.
Recommended Action
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 No DDTS.
Recommended Action
ACLQOS-SLOT#-3-ACLQOS_PAUSE_INVALID: Invalid Pause parameters:
Invalid Pause parameters No DDTS.
Recommended Action
2-8
OL-24654-01
Chapter 2
Error Message Explanation ACLQOS-SLOT#-3-ACLQOS_QUEUING_ERROR: ACL/QoS queuing error: [chars]
Internal error in ACL/QoS queuing config No DDTS.
Recommended Action
ACLQOS-SLOT#-4
Error Message Explanation ACLQOS-SLOT#-4-ACLQOS_ATOMIC_ERR: [chars]
Tcam will be overused, please turn off atomic update No DDTS.
Recommended Action
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. No DDTS.
Recommended Action
Error Message ACLQOS-SLOT#-4-ACLQOS_MATCH_ALL_MERGE_UPDATE: Warning (match_all merging): [chars] Explanation
Warning (match_all merging) No DDTS.
Recommended Action
Error Message ACLQOS-SLOT#-4-ACLQOS_OVER_THRESHOLD: Tcam [dec] Bank [dec]'s usage has reached its threshold Explanation
Tcam is almost full No DDTS.
Recommended Action
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 No DDTS.
Recommended Action
2-9
Chapter 2
Error Message ACLQOS-SLOT#-4-ACLQOS_QUEUING_INVALID: ACL/QoS invalid queuing policy: [chars] Explanation
Attemped to configure an invalid queuing policy No DDTS.
Recommended Action
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 No DDTS.
Recommended Action
ACLQOS-SLOT#-4-ACLQOS_WARNING: ACLQOS Warning: [chars]
ACLQOS Warnings No DDTS.
Recommended Action
ACLQOS-SLOT#-5
Error Message ACLQOS-SLOT#-5-ACLQOS_DISRUPTIVE_IPv6_UPDATE: Disruptive update of IPv6 compression entries Explanation
Disruptive IPv6 compression entries update No DDTS.
Recommended Action
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 No DDTS.
Recommended Action
ACLTCAM Messages
This section contains the ACLTCAM messages.
2-10
OL-24654-01
Chapter 2
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. Recommended Action
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] No action is required.
Recommended Action
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].
Recommended Action
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: No action is required.
0x[hex].
Recommended Action
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]). No action is required.
Recommended Action
Error Message ACLTCAM-2-ACL_TCAM_INCONSISTENT_DATABASE: Database found inconsistent. Explanation
Database found inconsistent. No action is required.
Recommended Action
2-11
Chapter 2
Error Message ACLTCAM-2-ACL_TCAM_INCONSISTENT_TCAM_CONTENTS: TCAM contents found inconsistent. Explanation
TCAM contents are found inconsistent. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. Recommended Action
Error Message [dec]. Explanation
ACLTCAM-2-ACL_TCAM_MALLOC_FAILURE: Memory allocation failed for size
Memory allocation is failed for size [dec] bytes. Restart the process.
Recommended Action
ACLTCAM-2-ACL_TCAM_MTS_FAILURE: MTS operation failed: [chars].
MTS operation failed. [chars] is the reason. No action is required.
Recommended Action
Error Message ACLTCAM-2-ACL_TCAM_MTS_Q_FULL: MTS queue for SAP [dec] is full Explanation
MTS queue for SAP [dec] is full No action is required.
Recommended Action
Error Message ACLTCAM-2-ACL_TCAM_MTS_REGISTRATION_FAILED: MTS registration failed for opCode: [dec]. Explanation
MTS registration failed for opCode: [dec]. No action is required.
Recommended Action
2-12
OL-24654-01
Chapter 2
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. Recommended Action
Error Message ACLTCAM-2-ACL_TCAM_NO_TCAM_LEFT: ACLTCAM resource exhausted for interface : [chars] Explanation
ACLTCAM hardware resource is completely used. No action is required.
Recommended Action
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]). Recommended Action
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 Recommended Action
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]). No action is required.
Recommended Action
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. No action is required.
Recommended Action
2-13
Chapter 2
Error Message Explanation ACLTCAM-2-PSS_OPEN_FAILED: PSS open failed - [hex].
Persistent database handle could not obtained for ACLTCAM. [hex] is the error. No action is required.
Recommended Action
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. Recommended Action
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. No action is required.
Recommended Action
Error Message ACLTCAM-3-ACL_TCAM_MTS_Q_LEAK: Possible MTS buffer leak for SAP [dec] Explanation
Possible MTS buffer leak for SAP [dec] No action is required.
Recommended Action
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. Recommended Action
Error Message ACLTCAM-3-FC2ERROR: [chars] Explanation
TL Port Manager encountered an FC2 error. [chars] specifies the context where the error occured. No action is required.
Recommended Action
2-14
OL-24654-01
Chapter 2
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. Recommended Action
Error Message ACLTCAM-3-MTSERROR: [chars] Explanation TL Port Manager encountered an MTS error. [chars] specifies the context where the error occured. Recommended Action
Error Message ACLTCAM-3-PSSERROR: [chars] Explanation TL Port Manager encountered a PSS error. [chars] specifies the context where the failure occured. Recommended Action
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.
Recommended Action
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] Recommended Action
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] No action is required.
Recommended Action
2-15
Chapter 2
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]]. Recommended Action
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 No action is required.
[hex].
Recommended Action
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 No action is required.
Recommended Action
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. No action is required.
Recommended Action
ACLTCAM-6
Error Message Explanation ACLTCAM-6-ACL_TCAM_STATUS: Status: [chars].
ACLTCAM status is reported as: [chars]. No action is required.
Recommended Action
Error Message ACLTCAM-6-MGRCREATED: Translation Port Manager created. Explanation
TL Port Manager was created successfully and is up and running. This is an informational message. No action is required.
Recommended Action
2-16
OL-24654-01
Chapter 2
Error Message ACLTCAM-6-MGREXIT: Translation Port Manager shutting down gracefully. Explanation
TL Port Manager is shutting down gracefully. This is an informational message. No action is required.
Recommended Action
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. Recommended Action
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. Recommended Action
ACL Messages
This section contains the ACL messages.
ACL-2
Error Message [chars]. Explanation ACL-2-ACL_HA_FAILURE: Failed to do high availability operation:
Failed to do high availability operation. [chars] is the reason. No action is required.
Recommended Action
Error Message ACL-2-ACL_INIT_FAILED: Initialization failed for ACL: [chars], reason: [hex]. Explanation
Initialization failed for ACL due to [chars], reason: [hex]. No action is required.
Recommended Action
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]. Recommended Action
2-17
Chapter 2
Error Message Explanation ACL-2-ACL_MTS_FAILURE: Failed to do MTS operation: [chars].
Failed to do MTS operation. [chars] is the reason. No action is required.
Recommended Action
Error Message ACL-2-ACL_MTS_Q_FULL: MTS queue for SAP [dec] is full Explanation
MTS queue for SAP [dec] is full No action is required.
Recommended Action
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]. No action is required.
Recommended Action
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] Recommended Action
Error Message [hex]. Explanation
ACL-2-ACL_PSS_FAILURE: Failed to do PSS operation: [chars], reason:
Recommended Action
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. No action is required.
Recommended Action
ACL-2-ACL_RUNTIME_FAILURE: [chars] [dec], Error: [hex]
ACL runtime failure is reported as [chars] [dec], reason: [hex]. No action is required.
Recommended Action
2-18
OL-24654-01
Chapter 2
Error Message Explanation ACL-2-ACL_TCAM_FAILURE: Failed to do TCAM operation: [chars].
Failed to do TCAM operation. [chars] is the reason. No action is required.
Recommended Action
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] No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message ACL-4-ACL_WARNING: [chars] [dec] Explanation
ACL warning messages is reported as [chars] [dec]. No action is required.
Recommended Action
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. No action is required.
Recommended Action
ACL-6
Error Message Explanation ACL-6-ACL_DIAG_EVENT_STATUS: [chars] [hex].
ACL system health management event status is reported as [chars] [hex]. No action is required.
Recommended Action
2-19
Chapter 2
Error Message Explanation ACL-6-ACL_E_PORT_EVENT_STATUS: [chars] [chars].
ACL xEport event status is reported as [chars] [chars]. No action is required.
Recommended Action
ACL-6-ACL_FCC_EVENT_STATUS: [chars] [chars].
ACL FCC event status is reported as [chars] [chars]. No action is required.
Recommended Action
ACL-6-ACL_LINECARD_EVENT_STATUS: [chars] [hex].
ACL linecard event status is reported as [chars] [dec]. No action is required.
Recommended Action
ACL-6-ACL_MCAST_EVENT_STATUS: [chars] [chars].
ACL multicast event status is reported as [chars] [chars]. No action is required.
Recommended Action
ACL-6-ACL_NX_PORT_EVENT_STATUS: [chars] [chars].
ACL Nx Port event status is reported as [chars] [chars]. No action is required.
Recommended Action
ACL-6-ACL_PORT_MODE_EVENT_STATUS: [chars] [chars].
ACL portmode event status is reported as [chars] [chars]. No action is required.
Recommended Action
ACL-6-ACL_RUNTIME_STATUS: [chars] [dec]
ACL runtime status is reported as [chars] [dec]. No action is required.
Recommended Action
ACL-6-ACL_SPAN_DEST_CONFIG_STATUS: [chars] [chars].
ACL SPAN destination config event status is reported as [chars] [chars]. No action is required.
Recommended Action
2-20
OL-24654-01
Chapter 2
Error Message Explanation ACL-6-ACL_SPAN_SRC_CONFIG_STATUS: [chars] [chars].
ACL SPAN source config event status is reported as [chars] [chars]. No action is required.
Recommended Action
ACL-6-ACL_STATUS: ACL Status: [chars].
ACL status is reported as [chars]. No action is required.
Recommended Action
ACL-6-ACL_UPDATE_SSRAM_QOS_EVENT_STATUS: [chars] [chars].
ACL update SSRAM for QoS event status is reported as [chars] [chars]. No action is required.
Recommended Action
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.' No action is required.
Recommended Action
AMM-SLOT#-0-TIMER_INIT_FAILED: Timer subsystem initialization failed!
AMM failed to initialize timer library. This is a fatal error. No action is required.
Recommended Action
AMM-SLOT#-2
Error Message Explanation AMM-SLOT#-2-AMM_MEM_ALLOC: Memory allocation failed. [chars]
Memory allocation failed. This is a critical failure No action is required.
Recommended Action
2-21
Chapter 2
Error Message Explanation AMM-SLOT#-2-AMM_RECOVERY_ERROR: Error in Recovery: [chars]
AMM failed to recover after a re-start. This is a fatal error. No action is required.
Recommended Action
AMM-SLOT#-6
Error Message Explanation AMM-SLOT#-6-INITIALIZED: Internal state created [chars]
AMM has created its internal state stateless/stateful [chars]. No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 Recommended Action
ASCII-CFG-2-ACFG_OPER_FAIL: Operation failed because of [chars]
Operation failed No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-22
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
ASCII-CFG-2-ACFG_SYSLOG_INIT_FAILED: Ascii config Syslog Init Error
Error encountered while Initializing Syslog for Ascii Config No action is required.
Recommended Action
Error Message ASCII-CFG-2-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
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. Recommended Action
ASCII-CFG-6
Error Message ASCII-CFG-6-ACFG_CHECKPOINT_CLEAR_DATABASE: cleared all the configuration checkpoints Explanation
Cleared all the configuration checkpoints No action is required.
Recommended Action
Error Message ASCII-CFG-6-ACFG_CHECKPOINT_CREATED: Created configuration checkpoint [chars] Explanation
Created configuration checkpoint No action is required.
Recommended Action
2-23
Chapter 2
Error Message ASCII-CFG-6-ACFG_CHECKPOINT_DELETED: Deleted configuration checkpoint [chars] Explanation
Deleted configuration checkpoint No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message ASCII-CFG-6-ACFG_ROLLBACK_ATOMIC: Performing configuration rollback to checkpoint [chars] (with atomic option) Explanation
Performing configuration rollback with atomic option No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
ASCII-CFG-6-INFORMATION: [chars]
An event happend that affects Acfg-Rollback. [chars] indicates the event No action is required.
Recommended Action
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 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.
2-24
OL-24654-01
Chapter 2
ASSOC MGR Messages

This section contains the ASSOC MGR messages.
ASSOC MGR-0
Error Message Explanation ASSOC_MGR-0-EMERGENCY_MSG: [chars]
Association Manager Emergency Message Please file the bug for Association Manager Component thro' CDETS
Recommended Action
ASSOC MGR-1
Error Message ASSOC_MGR-1-ALERT_MSG: [chars] Explanation
Association Manager Alert Message Association Manager Internal Operation Alert
Recommended Action
ASSOC MGR-2
Error Message Explanation ASSOC_MGR-2-CRITICAL_MSG: [chars]
Association Manager Critical Message No action is required.
Recommended Action
ASSOC MGR-3
Error Message Explanation ASSOC_MGR-3-ERROR_MSG: [chars]
Association Manager Error Message No action is required.
Recommended Action
ASSOC MGR-4
Error Message Explanation ASSOC_MGR-4-WARN_MSG: [chars]
Association Manager Warning Message No action is required.
Recommended Action
2-25
Chapter 2
ASSOC MGR-5
Error Message Explanation ASSOC_MGR-5-NOTIF_MSG: [chars]
Association Manager Notification Message No action is required.
Recommended Action
ASSOC MGR-6
Error Message ASSOC_MGR-6-ASSOC_ACTIVATED: Association Activated for vlan id:[dec] <--> vsan id:[dec] Explanation
Association Activated No action is required.
Recommended Action
Error Message ASSOC_MGR-6-ASSOC_CREATED: Association Created for vlan id:[dec] <--> vsan id:[dec] Explanation
Association Created No action is required.
Recommended Action
Error Message ASSOC_MGR-6-ASSOC_DEACTIVATED: Association Deactivated for vlan id: [dec] <--> vsan id: [dec] Explanation
Association Deactivated No action is required.
Recommended Action
Error Message ASSOC_MGR-6-ASSOC_DELETED: Association Deleted for vlan id: [dec] <--> vsan id: [dec] Explanation
Association Deleted No action is required.
Recommended Action
Error Message ASSOC_MGR-6-ASSOC_MGR_STATEFULL_RESTART: Association Manager Statefull Restart Explanation
Association Manager Stateful Restart No action is required.
Recommended Action
2-26
OL-24654-01
Chapter 2
Error Message ASSOC_MGR-6-ASSOC_MGR_STATELESS_RESTART: Association Manager Stateless Restart Explanation
Association Manager Stateless Restart No action is required.
Recommended Action
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 No action is required.
Recommended Action
ASSOC_MGR-6-INFO_MSG: [chars]
ASSOC Manager Informational Message No action is required.
Recommended Action
ASSOC MGR-7
Error Message Explanation ASSOC_MGR-7-DEBUG_MSG: [chars]
Association Manager Debug Message No action is required.
Recommended Action
BFDC Messages
This section contains the BFDC messages.
BFDC-SLOT#-2
Error Message Explanation BFDC-SLOT#-2-BFDC_GENERAL_FAILURE: General failure. [chars]
General failure. This is a critical failure No DDTS.
Recommended Action
BFDC-SLOT#-2-BFDC_MALLOC_FAILED: Memory allocation failed. [chars]
Memory allocation failed. This is a critical failure No DDTS.
Recommended Action
2-27
Chapter 2
Error Message Explanation BFDC-SLOT#-2-BFDC_MTS_FAILURE: MTS failure. [chars]
MTS related failure. This is a critical failure No DDTS.
Recommended Action
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 Please remove current bfd sessions to make room for new ones
[dec]
Recommended Action
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
2-28
OL-24654-01
Chapter 2
BFD-4
Error Message [chars]. Explanation BFD-4-INVALID_NBR: Attempt to BFD session failed for application
Attempt to BFD session failed for application [chars]. No action is required.
Recommended Action
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]). No action is required.
Recommended Action
BFD-5
Error Message Explanation BFD-5-BFD_DISABLED: BFD Disabled
BFD Service Disabled No action is required.
Recommended Action
BFD-5-BFD_ENABLED: BFD Enabled
BFD Service enabled No action is required.
Recommended Action
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] No action is required.
Recommended Action
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] No action is required.
Recommended Action
2-29
Chapter 2
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] No action is required.
Recommended Action
Error Message BFD-5-SESSION_MOVED: BFD session [hex]: [chars] Explanation
BFD session 0x[hex]: [chars] No action is required.
Recommended Action
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. No resources for session to neighbor [chars] Recommended Action
Remove other BFD sessions 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] No action is required.
Recommended Action
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. Recommended Action
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. No action is required.
Recommended Action
2-30
OL-24654-01
Chapter 2
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] No action is required.
Recommended Action
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] Recommended Action
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 No action is required.
Recommended Action
Error Message BIOS Flash Explanation
BIOS_DAEMON-2-BIOS_DAEMON_PRI_BOOT_FAIL: System booted from Alternate
Boot from Alternate SYSLOGDOC_NOACTION
Recommended Action
Error Message protected Explanation
BIOS_DAEMON-2-BIOS_DAEMON_SUP_ERROR: BIOS Sector ([dec]) is write
BIOS WRITE PROTECTED
2-31
Chapter 2
BIOS DAEMON-5
Error Message BIOS_DAEMON-5-BIOS_DAEMON_PRI_BOOT: System booted from Primary BIOS Flash Explanation
Boot from Primary SYSLOGDOC_NOACTION
Recommended Action
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 SYSLOGDOC_NOACTION
Recommended Action
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 SYSLOGDOC_NOACTION
Recommended Action
BOOTUP TEST Messages

This section contains the BOOTUP TEST messages.
2-32
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
Error Message BOOTUP_TEST-2-EOBC_SKIP: Module [dec] has failed test [chars] on EOBC due to error [chars] Explanation
Online diagnostics ManagementPort test has failed No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
BOOTVAR Messages
This section contains the BOOTVAR messages.
BOOTVAR-2
Error Message Explanation BOOTVAR-2-ALLOC_MEMORY: Memory allocation failed
The service failed to allocate memory. Check if the system is low on memory, if so reset the switch.
Recommended Action
2-33
Chapter 2
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. Check error id for specified reason.
Recommended Action
Error Message ([hex]) Explanation
BOOTVAR-2-AUTOSYNC_FAILED: Image autosync failed. Reason: [chars]
Image synchronization failed. Check that there is enough space on the flash, as well as system high
Recommended Action
availability status.
BOOTVAR-2-CONFIG_ERROR: Failed to update boot configuration
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. Make sure a right image is specified before reboot.
Recommended Action
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. Clear space on the standby disk.
Recommended Action
BOOTVAR-3-INIT_FAILED: Initialization failed: Component [chars]
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.
2-34
OL-24654-01
Chapter 2
Error Message BOOTVAR-3-LOAD_VERIFY_LIB_FAILED: Fetching library [chars] failed, reason=[chars] Explanation
Failed to load bootvar specified verification library. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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 Turn auto-copy off and back on.
integrity.
Recommended Action
2-35
Chapter 2
Error Message Explanation BOOTVAR-5-AUTOSYNC_DONE: Image autosync done
The image synchronization done successfully. No action is required.
Recommended Action
Error Message autosync Explanation
BOOTVAR-5-AUTOSYNC_REBOOT: Rebooting standby after successful
Image autosync has been successful, resetting the standby supervisor to load the new Check that the standby sup reloads correctly.
image.
Recommended Action
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. No action is required.
Recommended Action
Error Message sup[dec] Explanation
BOOTVAR-5-IMAGE_NOTEXISTS: Warning: image [chars] doesn't exist on
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. No action is required.
Recommended Action
BOOTVAR-6
Error Message Explanation BOOTVAR-6-ALREADY_IN_SYNC: Image already in sync
No need to update the image on the standby-sup. No action is required.
Recommended Action
2-36
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
BOOTVAR-6-CONFIG_UPDATED: Boot configuration updated
The boot-loader configuration files have been successfully updated. No action is required.
Recommended Action
BOOTVAR-6-STARTING: Boot configuration initialized
The service has successfully started. No action is required.
Recommended Action
CALLHOME Messages
This section contains the CALLHOME messages.
CALLHOME-2
Error Message Explanation CALLHOME-2-EVENT: [chars]
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
CALLHOME-2-PROGRAM_EXIT: callhome process ending: [chars]
Callhome process is exiting with reason [chars].
2-37
Chapter 2
CALLHOME-3
Error Message Explanation CALLHOME-3-CALLHOME_CFS_MERGE_OPERATION_FAILED: [chars]
[chars1] Please check the reason for the failure of the cfs operation and rectify the
Recommended Action
problem
CALLHOME-3-CALLHOME_CFS_OPERATION_FAILED: [chars] : [chars]
[chars1] [chars2] Please check the reason for the failure of the cfs operation and rectify the
Recommended Action
problem
CALLHOME-3-CALLHOME_MAX_ALERT_MSG: [chars]
[chars] Please check the reason for the generation of the callhome messages and
Recommended Action
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-24654-01
Chapter 2
CALLHOME-6
Error Message Explanation CALLHOME-6-NONCRIT_EVENT: [chars]
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 Explanation CDP-2-INITFAIL: CDP Daemon Initialization failed: [chars]
CDP Daemon Initialization failed. [chars] explains the reason for the failure. No action is required.
Recommended Action
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.
Recommended Action
Error Message
CDP-3-GENERROR: [chars]
Explanation CDP Daemon encountered a general error, one that does not fall in any of the above categories. [chars] describes the error and its context. Recommended Action
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. Recommended Action
2-39
Chapter 2
Error Message CDP-3-MTSERROR: [chars]
Explanation CDP Daemon encountered an MTS error. [chars] specifies the context where the error
occurred.
Recommended Action
CDP-3-PKTRECVFAIL: Failed to receive packet - [chars]
Failed to receive packet. [char] identifies the reason. No action is required.
Recommended Action
CDP-3-PKTSENDFAIL: Failed to send packet, interface [hex] - [chars]
Failed to send packet. [dec] identifies the interface [char] identifies the reason. No action is required.
Recommended Action
CDP-3-PSSERROR: [chars]
CDP Daemon encountered a PSS error. [chars] specifies the context where the failure No action is required.
occurred.
Recommended Action
CDP-3-SOCKBINDFAIL: Failed to bind to raw socket, interface [hex] -
Failed to bind to raw socket. [dec] identifies the interface [char] identifies the reason. No action is required.
Recommended Action
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 No action is required.
the reason.
Recommended Action
CDP-4
Error Message [chars] CDP-4-DUPLEX_MISMATCH: Duplex mismatch discovered on [chars], with
Explanation Duplex mismatch discovered from the received cdp packet This is a warning message. Recommended Action
2-40
OL-24654-01
Chapter 2
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. No action is required.
Recommended Action
CDP-5
Error Message Explanation CDP-5-DISABLED: CDP is disabled
CDP is disabled on the device. No action is required.
Recommended Action
CDP-5-ENABLED: CDP is enabled
CDP is enabled on the device. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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.
Recommended Action
2-41
Chapter 2
Error Message Explanation CDP-6-CDPEXIT: CDP Daemon shutting down gracefully.
CDP Daemon is shutting down gracefully. This is an informational message. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. Recommended Action
CDP-6-PORTENABLE: CDP enabled on port [chars]
CDP was enabled on a given port. [chars] is the interface-ID string that identifies the port. This is an informational message. No action is required.
Recommended Action
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. Recommended Action
CERT_ENROLL Messages
This section contains the CERT_ENROLL messages.
CERT_ENROLL-2
Error Message [chars] Explanation CERT_ENROLL-2-CERT_EN_PROGRAM_EXIT: cert_enroll daemon exiting:
Cert_enroll daemon is exiting.
2-42
OL-24654-01
Chapter 2
CERT_ENROLL-3
Error Message Explanation CERT_ENROLL-3-CERT_EN_ERROR_MESSAGE: [chars]
CERT_ENROLL Error Message No action is required.
Recommended Action
Error Message CERT_ENROLL-3-CERT_EN_FIPS_MODE_INIT_ERROR: Could not initialize FIPS mode : [chars] Explanation
FIPS mode initialization error No action is required.
Recommended Action
CERT_ENROLL-6
Error Message Explanation CERT_ENROLL-6-CERT_EN_MESSAGE: [chars]
CERT_ENROLL Message No action is required.
Recommended Action
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] No action is required.
Recommended Action
Error Message
CFS-2-EXITING: Exit reason: [chars]
Explanation The CFS service process has exited due to [char]. The process has probably been restarted automatically. Recommended Action
2-43
Chapter 2
Error Message Explanation CFS-2-GENERAL_ERROR: [chars]
The CFS service has encountered an critical error. The description of error is [str.] No action is required.
Recommended Action
CFS-2-INITFAIL: CFS Service Init failed: [chars]
CFS Service initialization failed. [chars] explains the reason for the failure. No action is required.
Recommended Action
CFS-2-LOCK_FAILED: lock failed for sap [dec] due to internal error.
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
CFS-2-MALLOC_ERROR: Size [dec] bytes
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] Recommended Action
CFS-2-PSS_ERROR: [chars]: PSS ret. val=[dec]
The CFS service encountered error while operating on a persistent storage database. No action is required.
Recommended Action
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 Recommended Action
2-44
OL-24654-01
Chapter 2
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
Recommended Action
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. No action is required.
Recommended Action
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. Recommended Action
CFS-3-DBERROR: [chars]
CFS Service encountered a database error. [chars] specifies the context where the failure occured. No action is required.
Recommended Action
CFS-3-FAILURE_RESPONSE: [chars] [hex]
CFS Service failed to get response [chars][hex] specify the context where the failure No action is required.
occured.
Recommended Action
CFS-3-FIPS_TEST_FAILED: FIPS compliance test failed
FIPS compliance test failed No action is required.
Recommended Action
2-45
Chapter 2
Error Message CFS-3-GENERROR: [chars]
Explanation CFS Service encountered a general error, one that does not fall in any of the above categories. [chars] describes the error and its context. Recommended Action
CFS-3-LICERR: [chars]
CFS Service failed to get license. No action is required.
Recommended Action
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. No action is required.
Recommended Action
CFS-3-MTSERROR: [chars]
CFS Service encountered an MTS error. [chars] specifies the context where the error No action is required.
occured.
Recommended Action
CFS-3-PSSERROR: [chars]
CFS Service encountered a PSS error. [chars] specifies the context where the failure No action is required.
occured.
Recommended Action
CFS-3-TIMEOUT_ERROR: [chars] [hex]
CFS Service encountered a timeout [chars][hex] specify the context where the failure No action is required.
occured.
Recommended Action
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.

Recommended Action
2-46
OL-24654-01
Chapter 2
CFS-4
Error Message Explanation CFS-4-LICEXP: [chars]
CFS Service license is going to expire. [chars] gives the expected time of expiry No action is required.
Recommended Action
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.
Recommended Action
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.
Recommended Action
CFS-6-BECAME_STDBY: Became STANDBY from active mode
The CFS service became standby from active mode. No action is required.
Recommended Action
CFS-6-EXCESSIVE_DELAY: [chars]
Excessive time taken for a processing event. The description of the event is [str.] No action is required.
Recommended Action
Error Message CFS-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars] Explanation
The CFS service was unable to send heartbeat to the system manger No action is required.
Recommended Action
2-47
Chapter 2
Error Message CFS-6-GENERAL_EVENT: [chars]
Explanation The CFS service has generated an important event. The description of the event is [str.] Recommended Action
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 No action is required.
Recommended Action
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 Recommended Action
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] No action is required.
Recommended Action
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 No action is required.
[chars]
Recommended Action
CFS-6-PSS_CREATED: [chars] PSS Created
One of the persistent information database of CFS service has been recreated No action is required.
Recommended Action
CFS-6-PSS_DESTROYED: [chars] PSS Destroyed
One of the persistent information databases of CFS Service has been intentionally destroyed and would be recreated. No action is required.
Recommended Action
2-48
OL-24654-01
Chapter 2
Error Message Explanation CFS-6-REGION_CTX_REMOVED: Region info is deleted for [chars]
[chars] is in logical scope. Regions are supported only physical scope applications No action is required.
Recommended Action
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. Recommended Action
CFS-6-SRVCREATED: CFS Service created
CFS Service was created successfully and is up and running. This is an informational No action is required.
message.
Recommended Action
CFS-6-SRVEXIT: CFS Service shutting down gracefully
CFS Service is shutting down gracefully. This is an informational message. No action is required.
Recommended Action
CFS-6-SWITCHOVER: Switching Over to other Sup.
The CFS service has successfully switched over to the standby supervisor card. No action is required.
Recommended Action
CIMSRVPROV Messages
This section contains the CIMSRVPROV messages.
CIMSRVPROV-2
Error Message Explanation CIMSRVPROV-2-CIM_SYSLOG_EXIT: Message:[chars] errcode:[dec]
Exit due to critical error No action is required.
Recommended Action
2-49
Chapter 2
Error Message CIMSRVPROV-2-CIM_SYSLOG_PSS_SNAPSHOT_ERR: Source URI:[chars] Destination URI:[chars] errcode:[dec] Explanation
PSS snapshot error No action is required.
Recommended Action
Error Message CIMSRVPROV-2-CIM_SYSLOG_SDWRAP_ERR: Description:[chars] errcode:[dec] Explanation
Debug infrastructure error No action is required.
Recommended Action
CIMSRVPROV-3
Error Message CIMSRVPROV-3-CIM_SYSLOG_COPY_CONFIG_ERR: Message:[chars] URI:[chars] errcode:[dec] Explanation
Copy running startup error No action is required.
Recommended Action
Error Message CIMSRVPROV-3-CIM_SYSLOG_FILE_ERR: Purpose:[chars] Filename:[chars] errcode:[dec] Explanation
File handling error No action is required.
Recommended Action
CIMSRVPROV-3-CIM_SYSLOG_MTS_ERR: message [chars]
MTS message handling error No action is required.
Recommended Action
Error Message CIMSRVPROV-3-CIM_SYSLOG_PSS_ERR: Purpose:[chars] URI:[chars] errcode:[dec] Explanation
PSS handling error No action is required.
Recommended Action
2-50
OL-24654-01
Chapter 2
CIMSRVPROV-6
Error Message [chars] Explanation CIMSRVPROV-6-LOG_CIM_CERTIFICATE_CLEARED: Cleared certificate
Cleared a certificate named [chars]. No action is required.
Recommended Action
CIMSRVPROV-6-LOG_CIM_CERTIFICATE_INSTALLED: Installed certificate
Installed a certificate named [chars]. No action is required.
Recommended Action
CLIS Messages
This section contains the CLIS messages.
CLIS-5
Error Message [chars] Explanation CLIS-5-CLIS_SYSLOG_CMD_REMOVED: Command deleted from the NVDB:
Command removal due to configuration change No action is required.
Recommended Action
CLOUD Messages
This section contains the CLOUD messages.
CLOUD-2
Error Message Explanation CLOUD-2-PROGRAM_EXIT: cloud-discovery process ending: [chars]
Cloud-discovery process is exiting with reason [chars].
2-51
Chapter 2
CLOUD-3
Error Message Explanation CLOUD-3-CLOUD_CFS_MERGE_OPERATION_FAILED: [chars]
[chars1] Please check the reason for the failure of the cfs operation and rectify the
Recommended Action
problem
CLOUD-3-CLOUD_CFS_OPERATION_FAILED: [chars] : [chars]
[chars1] [chars2] Please check the reason for the failure of the cfs operation and rectify the
Recommended Action
problem
CLOUD-3-CLOUD_FEATURE_MANAGER_ERROR: [chars] : [chars]
[chars1] [chars2] Please check the reason for error using feature manager and rectify the
Recommended Action
problem
CLOUD-3-CLOUD_PSS_OPERATION_FAILED: [chars] : [chars]
[chars1] [chars2] Please check the reason for the failure of the pss operation and rectify the
Recommended Action
problem
CLOUD-6
Error Message Explanation CLOUD-6-CLOUD_DISCOVERY_DONE: discovery over
Cloud-discovery started Check cloud membership
Recommended Action
CLOUD-6-CLOUD_DISCOVERY_STARTED: [chars] discovery started
Cloud-discovery started Check cloud-discovery status after sometime
Recommended Action
CLUSTER Messages
This section contains the CLUSTER messages.
2-52
OL-24654-01
Chapter 2
CLUSTER-2
Error Message [dec] Explanation CLUSTER-2-CLUSTER_CAP_ADD_FAIL: Failed to add cluster capability
Cluster capability addition failed No action is required.
Recommended Action
Error Message [dec] Explanation
CLUSTER-2-CLUSTER_CAP_DEL_FAIL: Failed to delete cluster capability
Cluster capability deletion failed No action is required.
Recommended Action
CMOND Messages
This section contains the CMOND messages.
CMOND-2
Error Message Explanation CMOND-2-CMOND_ALERT_MSG: [chars]
Alert message No action is required.
Recommended Action
CMOND-2-CMOND_ERROR_MSG: [chars]
Error message No action is required.
Recommended Action
CMPPROXY Messages
This section contains the CMPPROXY messages.
2-53
Chapter 2
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 No action is required.
Recommended Action
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

Recommended Action
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

Recommended Action
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 Recommended Action
CMPPROXY-5-MALLOC_FAILURE: Memory allocation failure
Memory allocation in a call to malloc/calloc has failed. No action is required.
Recommended Action
2-54
OL-24654-01
Chapter 2
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 Recommended Action
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. No action is required.
Recommended Action
COPP-2
Recommended Action
COPP-2-COPP_INIT_FAIL: CoPP Initialization failed: [chars]
CoPP Initialization failed. [chars] explains the reason for the failure. No action is required.
Recommended Action
COPP-2-COPP_MTS_FAIL: Failed to do MTS operation: [chars]
Failed to do MTS operation. [chars] explains the reason for the failure. No action is required.
Recommended Action
2-55
Chapter 2
Error Message COPP-2-COPP_NO_POLICY: Control-plane is unprotected. Explanation
There isntanypolicyconfiguredtoprotectcontrol-plane.' No action is required.
Recommended Action
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 Recommended Action
COPP-3
Error Message Explanation COPP-3-COPP_ALLOC_FAIL: Memory allocation failure: [chars]
Failed to alloc required memory. [chars] explains the reason for the failure. No action is required.
Recommended Action
Recommended Action
COPP-3-COPP_PPF_FAIL: Error during PPF operation: [chars]
Failed to do PPF operation. [chars] explains the reason for the failure. No action is required.
Recommended Action
COPP-3-COPP_PSS_FAIL: Error during PSS operation: [chars]
Failed to do PSS operation. [chars] explains the reason for the failure. No action is required.
Recommended Action
2-56
OL-24654-01
Chapter 2
COPP-4
Recommended Action
COPP-5
Error Message Explanation COPP-5-COPP_DISABLED: COPP Disabled
COPP Service Disabled No action is required.
Recommended Action
Recommended Action
COPP-5-COPP_ENABLED: COPP Enabled
COPP Service nabled No action is required.
Recommended Action
COPP-5-COPP_INIT: COPP initialized
COPP Service Initialized No action is required.
Recommended Action
COPP-6
Recommended Action
2-57
Chapter 2
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
COPP-7
Recommended Action
Error Message CORE-DMON-2-MODULE_COREDUMP_DONE: kernel coredump completed on module:[dec] Explanation
Kernel coredump finishing on a module No action is required.
Recommended Action
Error Message CORE-DMON-2-MODULE_COREDUMP_STARTED: kernel coredump started on module:[dec] Explanation
Kernel coredump starting on a module No action is required.
Recommended Action
CREDITMON Messages
This section contains the CREDITMON messages.
CREDITMON-SLOT#-2
Error Message Explanation CREDITMON-SLOT#-2-SYSERR_CREDITMON_APP_EXITED: [chars]
Credit Monitor application exited No action is required.
Recommended Action
2-58
OL-24654-01
Chapter 2
Error Message Explanation CREDITMON-SLOT#-2-SYSERR_CREDITMON_MTS_INIT_ERR: [chars]
Credit Monitor error binding to MTS No action is required.
Recommended Action
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 Recommended Action
Error Message CTS-2-CTS_FIPS_BYPASS_TEST_FAILED: FIPS bypass test failed for interface: [chars] Explanation
. No action is required.
Recommended Action
Error Message CTS-2-CTS_SAP_FAILED: SAP exchange failed on interface [chars]. (Reason: [chars]) Explanation
Recommended Action
Error Message CTS-2-CTS_SAP_REKEY_FAILED: SAP exchange failed on interface [chars]. (Reason: [chars]) Explanation
Recommended Action
Error Message [chars] ) Explanation
CTS-2-DBG_INIT_FAILED: Debug Infrastructure Initialization failed (
Recommended Action
2-59
Chapter 2
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message CTS-2-FC2_UNKNOWN_FRM_RECD_CRIT: Received an unexpected/unknown FC-2 frame on [chars] Explanation
Recommended Action
Error Message CTS-2-FSMU_INIT_FAILED: State Machine Infrastructure Initialization failed ( [chars] ) Explanation
Recommended Action
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. No action is required.
Recommended Action
Error Message exiting Explanation
CTS-2-LICENSE_UNAVAILABLE: License:[chars] unavailable, service
License of [chars] is unavailable. Service will exit now Please install the license file to continue using the feature.
Recommended Action
Error Message CTS-2-MEM_FAILED: Memory operations failed File: [chars] Line [dec] for size [hex] bytes Explanation
Recommended Action
2-60
OL-24654-01
Chapter 2
Error Message Explanation CTS-2-POST_INIT_FAILED: Post-Initialization failed ( [chars] )
Recommended Action
Error Message [chars] ) Explanation
CTS-2-PSS_INIT_FAILED: PSS Infrastructure Initialization failed (
Recommended Action
Error Message CTS-2-RBACL_ENFORCEMENT_FAILED: Failed to [chars] RBACL enforcement on [chars] %lu Explanation
Recommended Action
Error Message CTS-2-RBACL_LC_INSERT_FAILED: RBACL programming failed for inserted module [dec] Explanation
Recommended Action
CTS-2-RBACL_TCAM_SPACE_NOT_ENOUGH: Not enough free space left on TCAM
Recommended Action
CTS-2-RBACL_UNABLE_PARSE_ACE: Unable to parse RBACL ACE substring:
Recommended Action
CTS-2-RBACL_UPDATE_FAILED: Failed to [chars] RBACL [chars]
Recommended Action
2-61
Chapter 2
CTS-3
Error Message [chars] Explanation CTS-3-DOT1X_AUTHC_FAILED: DOT1X authentication failed on port:
DOT1X authentication failed on the port No action is required.
Recommended Action
CTS-5
Error Message [chars] %lu Explanation CTS-5-CTS_IP_SGT_MAP_DELETE: IP-SGT mapping deleted for [chars] on
Recommended Action
CTS-5-CTS_IP_SGT_MAP_UPDATE: [chars] assigned SGT [chars]
Recommended Action
CTS-6
Error Message CTS-6-CTS_FIPS_BYPASS_TEST_PASSED: FIPS bypass test passed for interface: [chars] Explanation
Recommended Action
CTS-6-SXP_STATE_CHANGE: CTS SXP [chars]
Recommended Action
DCEFIB Messages
This section contains the DCEFIB messages.
2-62
OL-24654-01
Chapter 2
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.
Recommended Action
Error Message failed! Explanation
DCEFIB-SLOT#-0-TIMER_INIT_FAILED: Timer subsystem initialization
L2mp unicast fib failed to initialize timer library. This is a fatal error. No action is required.
Recommended Action
DCEFIB-SLOT#-2
Error Message Explanation DCEFIB-SLOT#-2-DCEFIB_MEM_ALLOC: Memory allocation failed. [chars]
Recommended Action
DCEFIB-SLOT#-2-DCEFIB_RECOVERY_ERROR: Error in Recovery: [chars]
L2mp unicast fib failed to recover after a re-start. This is a fatal error. No action is required.
Recommended Action
DCEFIB-SLOT#-2-U2FIB_ERR: [chars]
L2mp unicast fib encountered an error: No action is required.
Recommended Action
DCEFIB-SLOT#-6
Error Message Explanation DCEFIB-SLOT#-6-INITIALIZED: Internal state created [chars]
L2mp unicast fib has created its internal state stateless/stateful [chars]. No action is required.
Recommended Action
2-63
Chapter 2
Error Message Explanation DCEFIB-SLOT#-6-U2FIB_INFO: [chars]
L2mp unicast fib notice: No action is required.
Recommended Action
DCEFIB-SLOT#-6-VDC_CREATED: VDC [dec] created
Request to create VDC [dec] in l2mp unicsat fib was successful. No action is required.
Recommended Action
DCEFIB-SLOT#-6-VDC_REMOVED: VDC [dec] Removed
L2mp unicast fib has successfully removed VDC [dec] from its databases. No action is required.
Recommended Action
DEBUGPROXY Messages
This section contains the DEBUGPROXY messages.
DEBUGPROXY-6
Error Message Explanation DEBUGPROXY-6-SSM_DEBUG_PROXY_COMMON: SSM debug proxy [chars] [dec]
General SSM debug proxy information No action is required.
Recommended Action
DEVICE-ALIAS Messages
This section contains the DEVICE-ALIAS messages.
DEVICE-ALIAS-2
Error Message type:[dec] Explanation DEVICE-ALIAS-2-ALLOC_FAILED: Memory allocation failed for size:[dec]
Memory allocation failed for size [dec] type [dec]
2-64
OL-24654-01
Chapter 2
Error Message Explanation DEVICE-ALIAS-2-INIT_FAILED: [chars]
An error occurred during initialization. [chars] indicates the reason for failure.
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. 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.
DEVICE-ALIAS-3-CLEAR_FAILED: [chars]
An error occurred while clearing the session. [chars] indicates the reason for failure.
DEVICE-ALIAS-3-COMMIT_FAILED: [chars]
An error occurred while committing the database. [chars] indicates the reason for
failure.
DEVICE-ALIAS-3-COMMIT_REJECTED: [chars]
Commit request received from remote switch is rejected. [chars] indicates the reason
for failure.
DEVICE-ALIAS-3-LOCK_FAILED: [chars]
An error occurred while acquiring the lock. [chars] indicates the reason for failure.
2-65
Chapter 2
Error Message Explanation DEVICE-ALIAS-3-LOCK_REJECTED: [chars]
Lock request received from remote switch is rejected. [chars] indicates the reason for
failure.
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. 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.
DEVICE-ALIAS-3-MERGE_FAILED: [chars]
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. 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.
DEVICE-ALIAS-3-MERGE_MRESP_REJECTED: [chars]
MRESP received from remote switch is rejected. [chars] indicates the reason for
failure.
2-66
OL-24654-01
Chapter 2
Error Message Explanation DEVICE-ALIAS-3-MERGE_VALIDATION_FAILED: [chars]
An error occurred while validating the merged database. [chars] indicates the reason
for failure.
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. 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.
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. 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.
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. 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.
DEVICE-ALIAS-3-UNLOCK_FAILED: [chars]
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.
2-67
Chapter 2
Error Message DEVICE-ALIAS-3-VALIDATION_FAILED: [chars]
Explanation An error occurred while validating the database. [chars] indicates the reason for failure. 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.
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 Explanation DEVICE-ALIAS-6-CLEAR_FAILED_INFO: [chars]
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 information regarding failure. 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.
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.
2-68
OL-24654-01
Chapter 2
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.
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
information regarding failure.

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. Recommended Action
No DDTS.
2-69
Chapter 2
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. Recommended Action
No DDTS.
Error Message
DEVICE-ALIAS-6-UNLOCK_FAILED_INFO: [chars]
Explanation An error occurred while releasing the lock. [chars] indicates the additional information regarding failure. 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.
DEVICE-ALIAS-6-VALIDATION_ABORTED: [chars]
Local validation is aborted. [chars] indicates the reason why validation is aborted. No DDTS.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-70
OL-24654-01
Chapter 2
Error Message DEVICE_TEST-2-EOBC_FAIL: Module [dec] has failed test [chars] on EOBC due to error [chars] Explanation
Online diagnostics EOBC test has failed No action is required.
Recommended Action
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 No action is required.
Recommended Action
DEVICE_TEST-2-MALLOC_FAILURE: Memory allocation failed
Device Test process could not allocate memory No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-71
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-72
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message DEVICE_TEST-3-STANDBY_TEST_SOCKET_FAIL: Standby test socket error [chars]: [hex] Explanation
Device Test StandbyFabricLoopback Test Socket error No action is required.
Recommended Action
2-73
Chapter 2
DEVICE_TEST-4
Error Message Explanation DEVICE_TEST-4-THREAD_CREATE_FAIL: Thread creation failed
Device Test process could not create threads No action is required.
Recommended Action
DEVICE_TEST-4-TIMER_CREATE_FAIL: Timer creation failed
Device Test process could not create timer No action is required.
Recommended Action
DEVICE_TEST-4-TIMER_START_FAIL: Timer start failed
Device Test process could not start timer No action is required.
Recommended Action
DEVICE_TEST-5
Error Message Explanation DEVICE_TEST-5-NOTICE_TEST: Memory allocation failed notice
Recommended Action
DEVICE_TEST-6
Error Message Explanation DEVICE_TEST-6-INFO_TEST: Memory allocation failed info
Recommended Action
DEV_LOG Messages
This section contains the DEV_LOG messages.
2-74
OL-24654-01
Chapter 2
DEV_LOG-3
Error Message Explanation DEV_LOG-3-ERROR: [chars]
Dev_log_lc encountered an error No action is required.
Recommended Action
DEV_LOG-SLOT#-4
Error Message Explanation DEV_LOG-SLOT#-4-DEV_LOG_LC_ERROR: [chars]
Dev_log_lc encountered an error No action is required.
Recommended Action
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.' No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
2-75
Chapter 2
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. No action is required.
Recommended Action
Error Message DFTM-SLOT#-2-DFTM_VLAN_NOT_FOUND: VLAN [dec] not found in DFTM database [chars] Explanation
DFTM database doesnthavetheVLAN.' No action is required.
Recommended Action
DFTM-SLOT#-3
Error Message Entry Explanation DFTM-SLOT#-3-DFTM_BDDB_PROG_FAILED: DFTM failed to program BDDB
DFTM failed to program BDDB Entry No action is required.
Recommended Action
Error Message Entry Explanation
DFTM-SLOT#-3-DFTM_BDT_PROG_FAILED: DFTM failed to program BD Table
DFTM failed to program BD Table Entry No action is required.
Recommended Action
Error Message DFTM-SLOT#-3-DFTM_IFIDX_INVALID_PORT_LAYER: Invalid Port Layer Received for interface: [chars] Explanation
Invalid Port Layer Received for interface No action is required.
Recommended Action
Error Message DFTM-SLOT#-3-DFTM_IFIDX_INVALID_PORT_MODE: Invalid Port Mode Received for interface: [chars] Explanation
Invalid Port Mode Received for interface No action is required.
Recommended Action
2-76
OL-24654-01
Chapter 2
Error Message DFTM-SLOT#-3-DFTM_IFIDX_INVALID_PORT_TYPE: Invalid Port Type Received for interface: [chars] Explanation
Invalid Port Type Received for interface No action is required.
Recommended Action
Error Message DFTM-SLOT#-3-DFTM_IFIDX_TYPE_ERROR: Failed to get type for interface: [chars] Explanation
Failed to get type for the interface No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message Table Entry Explanation
DFTM-SLOT#-3-DFTM_SDT_PROG_FAILED: DFTM failed to program SGT DGT
DFTM failed to program SGT DGT Table Entry No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-77
Chapter 2
DHCP_SNOOP Messages
This section contains the DHCP_SNOOP messages.
DHCP_SNOOP-2
Error Message Explanation DHCP_SNOOP-2-DHCP_SNOOP_PROGRAM_EXIT: [chars]
DHCP snoop process did an abnormal exit No action is required.
Recommended Action
DHCP_SNOOP-2-INITFAIL: DHCP Daemon Initialization failed: [chars]
DHCP Daemon Initialization failed. [chars] explains the reason for the failure. No action is required.
Recommended Action
Error Message
DHCP_SNOOP-2-PSSERROR: [chars]
Explanation DHCP Daemon encountered a PSS error. [chars] specifies the context where the failure
occurred.
Recommended Action
DHCP_SNOOP-2-REGPARTREE: Unable to register par tree: [chars]
Could not register par tree. [chars] explains the reason for the failure. No action is required.
Recommended Action
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. Recommended Action
DHCP_SNOOP-3-ASSERTION_FAILED: [chars]:[dec]
DHCP Snoop process has hit an assert condition at file [chars] line number [dec] No action is required.
Recommended Action
2-78
OL-24654-01
Chapter 2
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. Recommended Action
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 No action is required.
rate [dec].
Recommended Action
DHCP_SNOOP-3-HWPGMFAILURE: Hardware programming has failed: [chars]
Hardware programming has failed. [chars] explains the reason for the failure. No action is required.
Recommended Action
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] No action is required.
Recommended Action
Error Message
DHCP_SNOOP-3-MTSERROR: [chars]
Explanation DHCP Daemon encountered an MTS error. [chars] specifies the context where the error
occurred.
Recommended Action
DHCP_SNOOP-3-PKTDROP: Packet dropped. Reason - [chars]
Dropping the packet. [char] identifies the reason. No action is required.
Recommended Action
2-79
Chapter 2
Error Message Explanation DHCP_SNOOP-3-PKTRECVFAIL: Failed to receive packet - [chars]
Failed to receive packet. [char] identifies the reason. No action is required.
Recommended Action
DHCP_SNOOP-3-PKTSENDFAIL: Failed to send packet, - [chars]
Failed to send packet. [char] identifies the reason. No action is required.
Recommended Action
DHCP_SNOOP-3-SOCKBINDFAIL: Failed to bind to raw socket - [chars]
Failed to bind to socket. [char] identifies the reason. No action is required.
Recommended Action
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 No action is required.
reason.
Recommended Action
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]]) No action is required.
Recommended Action
Error Message DHCP_SNOOP-4-DHCP_SNOOPING_DENY: [dec] Invalid ARP messages ([chars]) on [chars], vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]]) Explanation
Recommended Action
2-80
OL-24654-01
Chapter 2
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 Recommended Action
Error Message DHCP_SNOOP-4-INVALID_ARP: [dec] Invalid ARP messages ([chars]) on [chars], vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]]) Explanation
Recommended Action
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. No action is required.
Recommended Action
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 informational message. Recommended Action
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. Recommended Action
2-81
Chapter 2
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]. ([sender-mac [chars]/sender-ip [chars]/ target-mac [chars]/target-ip [chars]/ time-of-day [chars]]) Recommended Action
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 informational message. Recommended Action
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. No action is required.
Recommended Action
Error Message DHCP_SNOOP-5-DHCP_SNOOPING_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]. ([sender-mac [chars]/sender-ip [chars]/ target-mac [chars]/target-ip [chars]/ time-of-day [chars]]) Recommended Action
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. Recommended Action
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. Recommended Action
2-82
OL-24654-01
Chapter 2
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. Recommended Action
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. Recommended Action
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. Recommended Action
DHCP_SNOOP-6-DHCPEXIT: DHCP Daemon shutting down gracefully.
DHCP Daemon is shutting down gracefully. This is an informational message. No action is required.
Recommended Action
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. Recommended Action
DHCP_SNOOP-6-DHCPPKTFWD: Gracefully forwarding DHCP packet. Reason:
Gracefully forwarding DHCP packet. reason [chars] No action is required.
Recommended Action
2-83
Chapter 2
Error Message Explanation DHCP_SNOOP-6-DHCPUP: DHCP Daemon Up.
DHCP Daemon was created successfully and is up and running. This is an informational message. No action is required.
Recommended Action
DHCP_SNOOP-6-INFO: [chars]
An event during switchover. [chars] explains the reason for the failure. No action is required.
Recommended Action
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. Recommended Action
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. Recommended Action
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] Recommended Action
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. Recommended Action
DIAGCLIENT Messages
This section contains the DIAGCLIENT messages.
2-84
OL-24654-01
Chapter 2
DIAGCLIENT-2
Error Message Explanation DIAGCLIENT-2-DIAG_BOOTUP_COMPLETE: Module <[dec]
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
DIAGCLIENT-2-EEM_ACTION_HM_SHUTDOWN: Test <[chars]
Informational Syslog No action is required.
Recommended Action
DIAGCLIENT-2-PSS_READ_FAILURE: Read from PSS failed on Module <[dec]
Read operation from PSS store failed No action is required.
Recommended Action
DIAGCLIENT-2-PSS_WRITE_FAILURE: Write to PSS failed on Module <[dec]
Write operation on PSS store failed No action is required.
Recommended Action
DIAGCLIENT-3
Error Message Explanation DIAGCLIENT-3-DIAG_HM_FAIL: Module <[dec]
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.
DIAGCLIENT-3-ONDEMAND_FAIL_EXCESS: Module <[dec]
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
2-85
Chapter 2
DIAGCLIENT-4
Error Message DIAGCLIENT-4-LC_OFFLINE_FOR_CURR_SLOT: Received LC offline event for the current slot:[dec]. Ignoring it Explanation
Recommended Action
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 No action is required.
Recommended Action
DIAGCLIENT-5
Error Message Explanation DIAGCLIENT-5-CALLOC_FAILURE: Memory allocation failed
DiagClient process could not allocate memory No action is required.
Recommended Action
Error Message DIAGCLIENT-5-DIAG_ONDEMAND_TEST_FINISH: Module [dec]: Ondemand test [chars] finished Explanation
Recommended Action
Error Message DIAGCLIENT-5-DIAG_ONDEMAND_TEST_START: Module [dec]: Ondemand test [chars] started Explanation
Recommended Action
Error Message DIAGCLIENT-5-DIAG_ONDEMAND_TEST_STOP: Module [dec]: Ondemand test [chars] stopped Explanation
Recommended Action
2-86
OL-24654-01
Chapter 2
Error Message Explanation DIAGCLIENT-5-DIAG_SCHED_COMPLETE: Module <[dec]
A scheduled Test was completed No action is required.
Recommended Action
DIAGCLIENT-5-ONDEMAND_FAIL: Module <[dec]
The specified test has reported FAILURE in this Iteration No action is required.
Recommended Action
DIAGCLIENT-5-ONDEMAND_SUCCESS: Module <[dec]
The specified test has reported SUCCESS in this Iteration No action is required.
Recommended Action
DIAGCLIENT-5-PER_PORT_TEST_FAIL: Module <[dec]
Per Port Test has failed on the above all ports No action is required.
Recommended Action
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 No action is required.
Recommended Action
DIAGMGR-2-PSS_DELETE_FAILURE: Read from PSS failed on Module <[dec]
Read operation from PSS store failed No action is required.
Recommended Action
2-87
Chapter 2
Error Message Explanation DIAGMGR-2-PSS_WRITE_FAILURE: Write to PSS failed on Module <[dec]
Write operation on PSS store failed No action is required.
Recommended Action
DIAGMGR-3
Error Message Explanation DIAGMGR-3-DIAG_MAJOR_DEFECT: Module <[dec]
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.
DIAGMGR-3-DIAG_MINOR_DEFECT: Module <[dec]
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. This is an informational message stating that a process initialization failure.
Recommended Action
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. This is an informational message stating that an unexpected event has been
Recommended Action
encountered.
DIAGMGR-4-DISRPT_TST_START: Starting Test <[chars]
Starting a Disruptive Test can disturb the systemsnormalfunctionality' Reset target module
Recommended Action
2-88
OL-24654-01
Chapter 2
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 Explanation DIAGMGR-5-BOOTUP_CONF: Diagnostic Bootup Level: <[chars]
Current Diagnostic BootUp Level being configure or changed No action is required.
Recommended Action
DIAGMGR-5-CALLOC_FAILURE: Memory allocation failure
Memory allocation in a call to malloc/calloc has failed No action is required.
Recommended Action
DIAGMGR-5-CHANGE_ALWAYS_HM: Health Monitoring test <[chars]
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.
DIAGMGR-5-HM_START: Health monitoring test <[chars]
Health Monitoring Test started No action is required.
Recommended Action
DIAGMGR-5-HM_STOP: Disabling health monitoring test <[chars]
Health Monitoring Test has been stopped It can be enabled through the diagnostic monitor..... command No action is required.
Recommended Action
2-89
Chapter 2
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
DIAGMGR-5-NONHM_AS_HM: The Test <[chars]
Non-HM test cannot be scheduled to run as a Health Monitoring test No action is required.
Recommended Action
DIAGMGR-6
Error Message Explanation DIAGMGR-6-BOOTUP_DIAG_OK: Module <[dec]
The diagnostic tests did not detect any error on the card. This is an informational message stating that the line card passed the
Recommended Action
diagnostic tests.
DIAGMGR-6-BOOTUP_TEST_STARTED: Module <[dec]
Starting bootup testing for above module No action is required.
Recommended Action
DIAG_PORT_LB Messages
This section contains the DIAG_PORT_LB messages.
2-90
OL-24654-01
Chapter 2
DIAG_PORT_LB-2
Error Message Explanation DIAG_PORT_LB-2-FIPS_RANDOM_ERROR: Random Number Generation Failure
Random Number genration failed in FIPS module No action is required.
Recommended Action
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. No action is required.
Recommended Action
DIAG_PORT_LB-2-LIF_GET_ERROR: [chars]([dec]) [chars] Error:[chars]
Port Loopback test process failed to get Diagnostic LIF id No action is required.
Recommended Action
Error Message failed. Explanation
DIAG_PORT_LB-2-MALLOC_FAILURE: [chars]([dec]) Memory allocation
Port Loopback test process could not allocate memory No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message DIAG_PORT_LB-2-PROC_INIT_FAILURE: [chars]([dec]) [chars] Error:[chars] Explanation
Port Loopback test process failed in process initialization No action is required.
Recommended Action
2-91
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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. No action is required.
Recommended Action
DIAG_PORT_LB-3-FSM_LIB_ERROR: [chars]([dec]) [chars]. Error:[chars]
Port Loopback test process failed in MTS API. No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-92
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
DIAG_PORT_LB-3-INVALID_TEST_REQUEST: [chars]([dec]) [chars]:[dec]
Port Loopback test process failed to get test request info. No action is required.
Recommended Action
DIAG_PORT_LB-3-INVALID_TEST_RUN: [chars]([dec]) [chars]:[dec]
Port Loopback test process failed to get the current test run information No action is required.
Recommended Action
DIAG_PORT_LB-3-PDB_LIB_API_ERROR: Failed to [chars]. Error:[dec].
The port loopback test was not able to get chassis info No action is required.
Recommended Action
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 <No action is required.
Recommended Action
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. No action is required.
Recommended Action
DIAG_PORT_LB-3-RESULT_ADD_FAILURE: [chars]([dec]) [chars]:[dec]
Port Loopback test process failed to add the port test result No action is required.
Recommended Action
2-93
Chapter 2
Error Message Explanation DIAG_PORT_LB-3-RESULT_SEND_FAILURE: [chars]([dec]) [chars]
Port Loopback test process failed to send the test results No action is required.
Recommended Action
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 No action is required.
Recommended Action
DIAG_PORT_LB-3-SOCKET_ERROR: [chars]([dec]) [chars] Error:[chars]
Port Loopback test process failed in socket operations No action is required.
Recommended Action
DIAG_PORT_LB-3-STATS_LIB_ERROR: [chars]([dec]) [chars]:[dec]
Port Loopback test process failed in stats infra lib API. No action is required.
Recommended Action
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 No action is required.
Recommended Action
DIAG_PORT_LB-3-TIMER_LIB_ERROR: [chars]([dec]) [chars]
Port Loopback test process timer handling failure. No action is required.
Recommended Action
DIAG_PORT_LB-3-VLAN_ERROR: [chars]([dec]) [chars] Error:[chars]
Port Loopback test process failed to get Diagnostic VLAN info No action is required.
Recommended Action
2-94
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 Recommended Action
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. No action is required.
Recommended Action
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 No action is required.
Recommended Action
DIAG_PORT_LB-5
Error Message Explanation DIAG_PORT_LB-5-DIAG_PORT_LB_DISABLED: DIAG_PORT_LB Disabled
DIAG_PORT_LB Service Disabled No action is required.
Recommended Action
DIAG_PORT_LB-5-DIAG_PORT_LB_ENABLED: DIAG_PORT_LB Enabled
DIAG_PORT_LB Service nabled No action is required.
Recommended Action
2-95
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
DMM-SLOT#-5-LOG_EV_DMM_JOB_COMPLETE: Job Id:%Ld NumSession:[dec]
Event indicating the completion of a Data Migration Job No action is required.
Recommended Action
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
Recommended Action
2-96
OL-24654-01
Chapter 2
Error Message Explanation DMM-SLOT#-5-LOG_EV_DMM_JOB_ERROR: Job Id:%Ld NumSession:[dec]
Event indicating the Suspension of Data Migration Job No action is required.
Recommended Action
DMM-SLOT#-5-LOG_EV_DMM_JOB_FINISH: Job Id:%Ld NumSession:[dec]
Event indicating Finish-request for a Method-2 Data Migration Job No action is required.
Recommended Action
DMM-SLOT#-5-LOG_EV_DMM_JOB_START: Job Id:%Ld NumSession:[dec]
Event indicating the start of a Data Migration Job No action is required.
Recommended Action
DMM-SLOT#-5-LOG_EV_DMM_JOB_STOP: Job Id:%Ld NumSession:[dec]
Event indicating that the Data Migration Job was stopped by Administrator No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_ERROR: Job Id:%Ld NumSession:[dec]
Event indicating the Suspension of Data Migration Job Verification due to an error No action is required.
Recommended Action
DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_START: Job Id:%Ld NumSession:[dec]
Event indicating the start of a Data Migration Job Verification No action is required.
Recommended Action
2-97
Chapter 2
Error Message Explanation DMM-SLOT#-5-LOG_EV_DMM_JOB_VERIFY_STOP: Job Id:%Ld NumSession:[dec]
Event indicating the Suspension of Data Migration Job Verification by the user No action is required.
Recommended Action
DOT1X Messages
This section contains the DOT1X messages.
DOT1X-2
Error Message Explanation DOT1X-2-DOT1X_INIT: Dot1x unable to start
The system failed to create the Dot1x process
DOT1X-3
Error Message Explanation DOT1X-3-ERR_SPANDST: It is configured as a SPAN Dest port.
Dot1x and SPAN Dest ports are mutually exclusive features.
Recommended Action Disable SPAN destination port configuration first before reconfiguring Dot1x
on the port.
DOT1X-3-INVALID_INPUT: Invalid on interface [chars].
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.
DOT1X-3-MEM_UNAVAIL: perform the 802.1X action.
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.
Error Message DOT1X-3-NOT_DOT1X_CAPABLE: [chars]. Explanation
Dot1x Authentication can only be enabled on physical Ethernet interfaces. Enable Dot1x Authentication on physical Ethernet interfaces only.
Recommended Action
2-98
OL-24654-01
Chapter 2
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. Initialize dot1x state machine
Recommended Action
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 To enable MAB make sure that port is not member of portchannel
Recommended Action
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 To enable MAB make sure that port is not in trunk mode
Recommended Action
2-99
Chapter 2
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 To change host mode, ensure that port is not a member of portchannel
mode.
Recommended Action
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. To change host mode, ensure that port is not in trunk mode
Recommended Action
DOT1X-5
Error Message Explanation DOT1X-5-DOT1X_DISABLED: dot1x Disabled
Dot1x Service Disabled No action is required.
Recommended Action
DOT1X-5-DOT1X_ENABLED: dot1x Enabled
Dot1x Service Enabled No action is required.
Recommended Action
2-100
OL-24654-01
Chapter 2
Error Message Explanation DOT1X-5-DOT1X_NOTIF: [chars]
Dot1x Notification No action is required.
Recommended Action
Error Message DOT1X-5-INVALID_MAC: broadcast or multicast mac address) [chars] is trying to authenticate. Explanation Authentication using 802.1x is not allowed for zero, broadcast, and multicast source 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 No action is required.
Recommended Action
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 No action is required.
supplicant
Recommended Action
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 No action is required.
Recommended Action
Error Message to [chars] Explanation
DOT1X-5-STATUS: Dot1x interface [chars] status changed from [chars]
Dot1x authenticator has changed its internal state No action is required.
Recommended Action
DPP_DEBUG Messages
This section contains the DPP_DEBUG messages.
2-101
Chapter 2
DPP_DEBUG-2
Error Message Explanation DPP_DEBUG-2-DPP_CRIT: [DPP[dec]] [chars]
A DPP generated a critical message No action is required.
Recommended Action
DPVM Messages
This section contains the DPVM messages.
DPVM-2
Error Message [chars] Explanation DPVM-2-ALLOC_FAILED: Memory allocation failed for size:[dec] for
Memory allocation failed for size [dec] for [chars]
DPVM-2-DPVM_DUPL_REJECT: [chars]
Rejected duplicate pwwn query Dpvm overwrite-duplicate-pwwn
Recommended Action
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
DPVM-3-DDAS_MODE_INVALID: [chars]
DDAS mode Invalid. [chars] Flip DDAS mode
Recommended Action
2-102
OL-24654-01
Chapter 2
Error Message DPVM-3-INIT_FAIL: [chars]
Explanation An error happened during DPVM Initialization. [chars] indicates the reason for failure 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.
DPVM-3-MTS_ERR: [chars]
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 that caused the error 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.
DPVM-4
Error Message Explanation DPVM-4-ACTIVATION_FAIL: [chars]
Activation of DPVM device mappings failed due to [chars] Correct the error and reactivate database again
Recommended Action
DPVM-4-FEATURE_DISABLED: [chars]
DPVM is unavailable and disabled now No action is required.
Recommended Action
DPVM-6
Error Message Explanation DPVM-6-FEATURE_ENABLED: [chars]
DPVM is available and enabled now No action is required.
Recommended Action
2-103
Chapter 2
Error Message Explanation DPVM-6-INFO: [chars]
An event happened that affects DPVM. [chars] indicates the event No action is required.
Recommended Action
DSTATS Messages
This section contains the DSTATS messages.
DSTATS-2
Error Message Explanation DSTATS-2-PSS_INIT_FAIL: pss initialization failed due to error: [hex]
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].
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].
2-104
OL-24654-01
Chapter 2
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].
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] failed due to error: [hex] Explanation Dstats process pss store runtime entry key [hex] value [hex] failure due to error [hex]. Recommended Action Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'
2-105
Chapter 2
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 No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message ELTMC-SLOT#-2-ELTMC_INTERNAL_ERROR: Internal error: [chars], collect output of show tech-support eltm Explanation
Recommended Action
Error Message ELTMC-SLOT#-2-ELTMC_INTF_NOT_FOUND: Interface [chars] not found in ELTM database [chars] Explanation
ELTM database doesnthavetheinterface.' No action is required.
Recommended Action
Error Message ELTMC-SLOT#-2-ELTMC_INTF_NOT_SUPP: Interface [chars] not supported by ELTM [chars] Explanation
ELTM doesntsupporttheinterfaceforthespecifiedoperation' No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-106
OL-24654-01
Chapter 2
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 Recommended Action
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

Recommended Action
Error Message ELTMC-SLOT#-2-ELTMC_L2_LIF_ALLOC_FAIL_VDC: Failed to allocate L2 LIF entries in forwarding engine Explanation ELTM Failed to allocate L2 LIF entries in forwarding engine. This will effect Layer 2
and Layer 3 forwarding in this VDC

Recommended Action
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 Recommended Action
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' Recommended Action
Error Message ELTMC-SLOT#-2-ELTMC_VLAN_INTERNAL_ERROR: Internal error: VLAN [dec]:[chars], collect output of show tech-support eltm Explanation
Recommended Action
ELTM Messages
This section contains the ELTM messages.
2-107
Chapter 2
ELTM-2
Error Message ELTM-2-INTERFACE_INTERNAL_ERROR: Internal error: [chars]:[chars], collect output of show tech-support eltm Explanation
Recommended Action
Error Message ELTM-2-INTERNAL_ERROR: Internal error: [chars], collect output of show tech-support eltm Explanation
Recommended Action
ELTM-2-INTF_NOT_FOUND: Interface [chars] not found in ELTM database
ELTM database doesnthavetheinterface.' No action is required.
Recommended Action
ELTM-2-INTF_NOT_SUPP: Interface [chars] not supported by ELTM [chars]
ELTM doesntsupporttheinterfaceforthespecifiedoperation' No action is required.
Recommended Action
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 No action is required.
Recommended Action
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) Recommended Action
2-108
OL-24654-01
Chapter 2
ELTM-6
Error Message ELTM-6-ELTM_MTS_SEND_FAILED: Failed to send MTS message errno [hex] opcode [dec] Explanation
No action is required. Eltm
Recommended Action
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
EOU-5
Error Message Explanation EOU-5-L2NAC_DISABLED: EOU Disabled
Service EOU Disabled No action is required.
Recommended Action
EOU-5-L2NAC_ENABLED: EOU Enabled
Service EOU enabled No action is required.
Recommended Action
EOU-6
Error Message Explanation EOU-6-AAA_DOWN: Default Policy ip: [chars]:retained
Policy retained No action is required.
Recommended Action
2-109
Chapter 2
Error Message Explanation EOU-6-AUTHTYPE: Authtype: ip: [chars] Authtype:[chars]
Authentication type No action is required.
Recommended Action
EOU-6-BAD_PKT: Bad Packet: ip: [chars] Why: [chars]
Bad Packet because of reason specified No action is required.
Recommended Action
EOU-6-CTA: CTA: ip: [chars] status(detected/not detected): [chars]
CTA detected or not No action is required.
Recommended Action
EOU-6-IDENTITY_MATCH: Identity Match: ip: [chars] Policy: [chars]
Identity Matched or not No action is required.
Recommended Action
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 No action is required.
Recommended Action
EOU-6-POLICY: Policy on ip: [chars]: [chars]: [chars]
Policy applied No action is required.
Recommended Action
EOU-6-POSTURE: Posture:ip: [chars] Status: [chars], Interface:
Posture of host No action is required.
Recommended Action
2-110
OL-24654-01
Chapter 2
Error Message [chars] Explanation EOU-6-SESSION: Session ip: [chars] Action:[chars] , Interface:
Session detected No action is required.
Recommended Action
EOU-6-SOCKET: Service eou on port: [dec]
Eou using above port No action is required.
Recommended Action
EOU-6-SQ_EAP_MSG: Status Query: ip: [chars] status: [chars]
Status query state No action is required.
Recommended Action
EOU-6-UNKN_EVENT_ERR: Unknow Event Err: ip: [chars] Message: [chars]
Error due to unknown event No action is required.
Recommended Action
EOU-6-VERSION_MISMATCH: Eou version mismatch ip: [chars] and version
Eou version mismatch No action is required.
Recommended Action
EOU-7
Error Message Explanation EOU-7-EOU_DISABLED_INTF: eou disabled on interface [chars]
Eou service disabled on interface No action is required.
Recommended Action
EOU-7-EOU_ENABLED_INTF: eou enabled on interface [chars]
Eou service enabled on interface No action is required.
Recommended Action
2-111
Chapter 2
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. Recommended Action
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. No action is required.
Recommended Action
EPP Messages
This section contains the EPP messages.
EPP-5
Error Message Explanation EPP-5-EPP_FAILURE: Interface [chars] EPP Failure
Trunk protocol failed showeppinternalevent-historyerr'willindicatetheerrorsencountered'
Recommended Action
Error Message switch Explanation
EPP-5-EPP_LOOPBACK: Interface [chars] is looped back to the same
The interface is looped back to another interface on the same switch Check the connectivity of this interface and ensure that it is connected to
Recommended Action
another switch
ETH-PORT-SEC Messages
This section contains the ETH-PORT-SEC messages.
2-112
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
ETH-PORT-SEC-3-ETH_PORT_SEC_INVALID_VLAN: Invalid VLAN configuration
Invalid VLAN configuration No action is required.
Recommended Action
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 No action is required.
another
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-113
Chapter 2
Error Message ETH-PORT-SEC-3-ETH_PORT_SEC_VIOL_UPDATE_FAILED: Failed to update violation mode Explanation
Failed to update violation mode No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_DISABLED: eth_port_sec Disabled on if_index:[hex] Explanation
Eth_port_sec Service Disabled No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message ETH-PORT-SEC-5-ETH_PORT_SEC_ENABLED: eth_port_sec Enabled on if_index:[hex] Explanation
Eth_port_sec Service Enabled No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-114
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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. Please follow instructions on the syslog.
Recommended Action
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. None
Recommended Action
ETHPORT-2-SYSLOG_ETHPM_CRITICAL: Critical failure: [chars]
There was a critical failure in the component. Please collect system tech-support
Recommended Action
2-115
Chapter 2
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 Perform shut'and'noshutdown'onthePortChannelinterfacethatitbelongsto'
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
ETHPORT-3-IF_SFP_ALARM: Interface [chars], [chars]
There was an alarm on the transceiver module Please do show interface transceiver details to obtain more information
Recommended Action
ETHPORT-3-IF_SFP_ERROR: Interface [chars], [chars]
There was an error on the transceiver module Please do show interface transceiver details to obtain more information
Recommended Action
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
2-116
OL-24654-01
Chapter 2
Error Message Explanation ETHPORT-3-IF_XCVR_ALARM: Interface [chars], [chars]
There was an alarm on the transceiver module Please do show interface transceiver details to obtain more information
Recommended Action
ETHPORT-3-IF_XCVR_ERROR: Interface [chars], [chars]
There was an error on the transceiver module Please do show interface transceiver details to obtain more information
Recommended Action
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 Please do show interface transceiver details to obtain more information
Recommended Action
ETHPORT-4-IF_XCVR_WARNING: Interface [chars], [chars]
There was an warning on the transceiver module Please do show interface transceiver details to obtain more information
Recommended Action
ETHPORT-5
Error Message Explanation ETHPORT-5-IF_ADMIN_UP: Interface [chars] is admin up [chars]
Interface is admin up No action is required.
Recommended Action
2-117
Chapter 2
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 No action is required.
Recommended Action
Error Message ETHPORT-5-IF_DOWN_ADMIN_DOWN: Interface [chars] is down (Administratively down) Explanation
Interface has been configured to be administratively down Perform noshutdown''
Recommended Action
Error Message change) Explanation
ETHPORT-5-IF_DOWN_CFG_CHANGE: Interface [chars] is down(Config
FCIP interface temporarily down due to reconfiguration No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message ETHPORT-5-IF_DOWN_DOMAIN_INVALID_RCF_RECEIVED: Interface [chars] is down (Isolation due to invalid fabric reconfiguration) Explanation
Invalid RCF received No action is required.
Recommended Action
2-118
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message ETHPORT-5-IF_DOWN_DOMAIN_OVERLAP_ISOLATION: Interface [chars] is down (Isolation due to domain overlap) Explanation
Isolated due to domain overlap No action is required.
Recommended Action
Error Message ETHPORT-5-IF_DOWN_ELP_FAILURE_ISOLATION: Interface [chars] is down (Isolation due to ELP failure) Explanation
ELP failed on the interface Check the output of showportinternalinfo'inthe'ELPfailurereason'field'
Recommended Action
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'
2-119
Chapter 2
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 Ensure that the ethernet cable is connected, the interface is administratively
Recommended Action
enabled
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 Ensure that the ethernet cable is connected and the remote end is also active
Recommended Action
Error Message ETHPORT-5-IF_DOWN_FCOT_NOT_PRESENT: Interface [chars] is down (FCOT not present) Explanation
The FCOT has been removed Insert an FCOT
Recommended Action
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 Please contact customer support for a list of authorized transceiver vendors
Recommended Action
Error Message Failure) Explanation
ETHPORT-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware
The moduleshardwarehasfailed'
Recommended Action Collect more information about failed module using command showmoduleinternalallmodule''
ETHPORT-5-IF_DOWN_INACTIVE: Interface [chars] is down (Inactive)
The port VSAN has been suspended or deleted Assign a new active port VSAN to the interface
Recommended Action
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'
2-120
OL-24654-01
Chapter 2
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 Get the allowed receive B2B credit size from showportinternalinfo''
Recommended Action
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 Get the allowed receive buffer size from showportinternalinfo''
Recommended Action
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
Recommended Action Perform a 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 No action is required.
Recommended Action
Error Message failure) Explanation
ETHPORT-5-IF_DOWN_LINK_FAILURE: Interface [chars] is down (Link
The physical link has gone down Ensure that the cable is connected and the remote end is not shut down
Recommended Action
2-121
Chapter 2
Error Message ETHPORT-5-IF_DOWN_LOOPBACK_DIAG_FAILURE: Interface [chars] is down (Diag failure) Explanation
Diag failed on the interface
Recommended Action Collect more information about failed interface using command attachmodule'toconnecttomodule'
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 Check the connectivity of this interface and ensure that it is connected to
Recommended Action
another switch
Error Message removed) Explanation
ETHPORT-5-IF_DOWN_MODULE_REMOVED: Interface [chars] is down (module
Interface is down because the module was removed No action is required.
Recommended Action
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 No action is required.
Recommended Action
ETHPORT-5-IF_DOWN_OFFLINE: Interface [chars] is down (Offline)
The interface has been placed into the offline state No action is required.
Recommended Action
Error Message ETHPORT-5-IF_DOWN_PARENT_ADMIN_DOWN: Interface [chars] is down (Parent interface down) Explanation
Parent interface is down No action is required.
Recommended Action
2-122
OL-24654-01
Chapter 2
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 Enable at least one of the PortChannelsmembers'
Recommended Action
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 progress) Explanation
ETHPORT-5-IF_DOWN_RCF_IN_PROGRESS: Interface [chars] is down (RCF in
There is an RCF in progress No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-123
Chapter 2
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 No action is required.
Recommended Action
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 different from that of the PortChannel
Recommended Action
Change the speed of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'
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 different from that of the PortChannel Recommended Action Ensure that this interface is connected to the same remote switch as all the other interfaces in the PortChannel
2-124
OL-24654-01
Chapter 2
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 Recommended Action Perform a 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
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
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 No action is required.
Recommended Action
2-125
Chapter 2
Error Message Explanation ETHPORT-5-IF_DOWN_VRF_UNUSABLE: Interface [chars] is down (Vrf down)
The vrf for which this interface is a member is removed No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message ETHPORT-5-IF_DUPLEX: Interface [chars], operational duplex mode changed to [chars] Explanation
Operational duplex mode has changed when link came up No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message [chars]
ETHPORT-5-IF_HARDWARE: Interface [chars], hardware type changed to
Explanation There was a change in the hardware characteristic of an interface, such as a transceiver module plugged in or removed Recommended Action
2-126
OL-24654-01
Chapter 2
Error Message [chars] Explanation ETHPORT-5-IF_L2MP_MODE: Interface [chars], l2mp-mode changed to
The l2mp-mode on the port has changed No action is required.
Recommended Action
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 No action is required.
Recommended Action
ETHPORT-5-IF_TRUNK_DOWN: Interface [chars], vlan [chars] down
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
ETHPORT-5-IF_TRUNK_UP: Interface [chars], vlan [chars] up
Interface [chars] is trunking, VLANs [chars] are up No action is required.
Recommended Action
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 No action is required.
Recommended Action
ETHPORT-5-IF_UP: Interface [chars] is up [chars]
Interface is up in mode specified, if applicable No action is required.
Recommended Action
ETHPORT-5-SPEED: Interface [chars], operational speed changed to
Operational speed has changed when link came up No action is required.
Recommended Action
2-127
Chapter 2
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 No action is required.
Recommended Action
ETH_PORT_CHANNEL Messages
This section contains the ETH_PORT_CHANNEL messages.
ETH_PORT_CHANNEL-1
Error Message [[chars]] Explanation ETH_PORT_CHANNEL-1-LC_CFG_FAILURE: configuring module [dec] failed
Module configuration failed Module will be automatically reset
Recommended Action
Error Message [dec]) Explanation
ETH_PORT_CHANNEL-1-MALLOC_FAILED: cannot allocate memory (size
No enough memory No action is required.
Recommended Action
Error Message ETH_PORT_CHANNEL-1-MAP_PARAM_FAILURE: mapping parameter failed for [chars] [[chars]] Explanation
Parameter mapping failed Specified service is misbehaving; check its status
Recommended Action
2-128
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
ETH_PORT_CHANNEL-3
Error Message Explanation ETH_PORT_CHANNEL-3-ADD_REM_MEMBERS_FAILURE: [chars]
Some service(s) failed to add or remove ports to port-channel None
Recommended Action
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 Explanation
Recommended Action
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
ETH_PORT_CHANNEL-3-GENERAL_ERROR: [chars]
General error No action is required.
Recommended Action
2-129
Chapter 2
Error Message ETH_PORT_CHANNEL-3-MSG_SEND_FAILURE: failed to send [chars] to sap [dec]: [chars] Explanation
Failed to send a message No action is required.
Recommended Action
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 None
Recommended Action
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 None
Recommended Action
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 None
Recommended Action
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 None
Recommended Action
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 None
Recommended Action
2-130
OL-24654-01
Chapter 2
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 Recommended Action
Error Message ETH_PORT_CHANNEL-3-RSP_TIMEOUT: Component [chars] timed out on response to opcode:[chars] (for:[chars]) Explanation
Recommended Action
Error Message ETH_PORT_CHANNEL-3-TIMEOUT: timed out after [dec] seconds [type [chars], state [chars]] Explanation
Some operation timed out Run show port-channel consistency to check all module connectivity and
Recommended Action
consistency
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 individual
ETH_PORT_CHANNEL-4-PORT_INDIVIDUAL: port [chars] is operationally
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
Recommended Action
2-131
Chapter 2
Error Message Explanation ETH_PORT_CHANNEL-4-RACE_WARN: [chars]
Warning of possible race condition No action is required.
Recommended Action
Error Message ETH_PORT_CHANNEL-4-UNEXPECTED_RESPONSE: unexpected response [chars] from [chars] Explanation
Received an unexpected response and discarded No action is required.
Recommended Action
ETH_PORT_CHANNEL-5
Error Message Explanation ETH_PORT_CHANNEL-5-AUTO_CREATE_FAILURE: [chars] [chars]
Auto create process on the port failed No action is required.
Recommended Action
ETH_PORT_CHANNEL-5-CREATED: [chars] created
A port-channel is created No action is required.
Recommended Action
ETH_PORT_CHANNEL-5-DELETED: [chars] deleted
A port-channel is deleted No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message ETH_PORT_CHANNEL-5-IF_DOWN_SUSPENDED_BY_MODE: Interface [chars] is down (Suspended due to incompatible mode Explanation
Compatibility check failed when adding ports to port-channel Make sure the compatibility parameters are consistent between the ports and
Recommended Action
the port-channel
2-132
OL-24654-01
Chapter 2
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 Make sure the compatibility parameters are consistent between the ports and
Recommended Action
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 Delete the set of port channel interface <port-channel interface
Recommended Action
ETH_PORT_CHANNEL-5-PORT_ADDED: [chars] added to [chars]
Ports are added to a port-channel No action is required.
Recommended Action
ETH_PORT_CHANNEL-5-PORT_DOWN: [chars]: [chars] is down
Port goes down in a port-channel No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message hot-standby Explanation
ETH_PORT_CHANNEL-5-PORT_HOT_STANDBY: [chars]: [chars] goes to
Port goes to hot-standby in a port-channel No action is required.
Recommended Action
Error Message down Explanation
ETH_PORT_CHANNEL-5-PORT_INDIVIDUAL_DOWN: individual port [chars] is
Port-channel member operating in individual mode goes down No action is required.
Recommended Action
2-133
Chapter 2
Error Message Explanation ETH_PORT_CHANNEL-5-PORT_REMOVED: [chars] removed from [chars]
Ports are removed from a port-channel No action is required.
Recommended Action
ETH_PORT_CHANNEL-5-PORT_SUSPENDED: [chars]: [chars] is suspended
Port is suspended in a port-channel No action is required.
Recommended Action
ETH_PORT_CHANNEL-5-PORT_UP: [chars]: [chars] is up
Port comes up in a port-channel No action is required.
Recommended Action
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' No action is required.
Recommended Action
ETH_PORT_CHANNEL-6
Error Message Explanation ETH_PORT_CHANNEL-6-RESYNC: resyncing [chars] with all modules
Resync modules with sup after an error or switchover No action is required.
Recommended Action
ETH_PORT_CHANNEL-7
Error Message Explanation ETH_PORT_CHANNEL-7-GSYNC_DONE: global synchronization is done
Port-channel manager finished global synchronization No action is required.
Recommended Action
ETH_PORT_CHANNEL-7-GSYNC_REQ: requesting global synchronization
Port-channel manager requested a global synchronization from active sup No action is required.
Recommended Action
2-134
OL-24654-01
Chapter 2
Error Message Explanation ETH_PORT_CHANNEL-7-START_ACTIVE: started in active mode
Port-channel manager started in active mode No action is required.
Recommended Action
ETH_PORT_CHANNEL-7-START_DEFAULT: started with default configuration
Port-channel manager started with default configuration No action is required.
Recommended Action
ETH_PORT_CHANNEL-7-START_STANDBY: started in standby mode
Port-channel manager started in standby mode No action is required.
Recommended Action
ETH_PORT_CHANNEL-7-START_STATEFUL: started statefully
Port-channel manager started with running configuration No action is required.
Recommended Action
ETH_PORT_CHANNEL-7-START_STATELESS: started statelessly
Port-channel manager started with startup configuration No action is required.
Recommended Action
EUREKA_USD Messages
This section contains the EUREKA_USD messages.
EUREKA_USD-3
Error Message Explanation EUREKA_USD-3-MSG1: [chars]
Eureka log message No action is required.
Recommended Action
EVMC Messages
This section contains the EVMC messages.
2-135
Chapter 2
EVMC-3
Error Message Explanation EVMC-3-MTS_OPERATION_FAILED: [chars]([dec]): [chars]
Internal IPC operation failed in Event Manager Client No action is required.
Recommended Action
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 Recommended Action
EVMC-5
Error Message Explanation EVMC-5-AVL_CREATE_FAIL: [chars]([dec]): AVL Tree creation failure
Event Manager could not initialize local policy store No action is required.
Recommended Action
EVMC-5-MALLOC_FAILURE: [chars]([dec]): Memory allocation failure
Event Manager Client process could not allocate memory No action is required.
Recommended Action
Error Message EVMC-5-RT_PSS_OP_FAILURE: [chars]([dec]): Failed to [chars]. Error:[chars] Explanation
Event Manager Client could not access HA store No action is required.
Recommended Action
EVMS Messages
This section contains the EVMS messages.
2-136
OL-24654-01
Chapter 2
EVMS-2
Error Message Explanation EVMS-2-EVMS_PSS_DELETE_FAILURE: Delete from PSS failed
Delete from PSS failed No action is required.
Recommended Action
EVMS-2-EVMS_PSS_WRITE_FAILURE: Write to PSS failed
Write to PSS failed No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
EXCEPTIONLOG Messages
This section contains the EXCEPTIONLOG messages.
2-137
Chapter 2
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. No action is required.
Recommended Action
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 No action is required.
Recommended Action
FABRICPATH-4
Error Message Explanation FABRICPATH-4-FABRICPATH_INVALID_FTAG: Invalid ftag [dec] received
Invalid ftag is received from remote No action is required.
Recommended Action
Error Message received Explanation
FABRICPATH-4-FABRICPATH_INVALID_SWITCH_ID: Invalid switch-id [dec]
Invalid switch-id is received from remote No action is required.
Recommended Action
FABRICPATH-6
Error Message FABRICPATH-6-FABRICPATH_LINK_BRINGUP_RESOLVE_COLLISION: Resolving Collision for switch-id [dec] Explanation
Resolving Collision for switch-id No action is required.
Recommended Action
2-138
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
Error Message FABRICPATH-6-FABRICPATH_LINK_BRINGUP_STALLED: LINK bringup suspended for [chars] due to conflicts Explanation
Link bringup temporarily suspended due to conflicts No action is required.
Recommended Action
Error Message FABRICPATH-6-FABRICPATH_NEW_ES_SWITCH_ID: New Emulated switch-id [chars] received Explanation
New Emulated switch-id received No action is required.
Recommended Action
FABRICPATH-6-FABRICPATH_NEW_SWITCH_ID: New switch-id [chars]
New switch-id received No action is required.
Recommended Action
Error Message FABRICPATH-6-FABRICPATH_SWID_CHANGED: Switch-id [dec] is assigned with [chars] state Explanation
Local switch-id is changed No action is required.
Recommended Action
Error Message FABRICPATH-6-FABRICPATH_SWID_CONFLICTS: Switch-id [dec] is in conflict with device [chars] Explanation
Local switch-id collision with other device No action is required.
Recommended Action
Error Message FABRICPATH-6-FABRICPATH_SWID_PRI_SEC_CHANGED: Switch-id [dec] is changed to [chars] Explanation
Local switch-id status changed No action is required.
Recommended Action
2-139
Chapter 2
Error Message FABRICPATH-6-FABRICPATH_SWID_STATE_CHANGED: Switch-id [dec] status changed to [chars] Explanation
Local switch-id status changed No action is required.
Recommended Action
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. Recommended Action
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 Recommended Action
FC-TUNNEL-3-MTS_ERROR: MTS message transmission failed with error
FCMPLS tunnel process unsuccessfully tried to send a MTS message. MTS errro number is specified in [dec] No action is required.
Recommended Action
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
API and 0x[hex] specifies the error

Recommended Action
2-140
OL-24654-01
Chapter 2
Error Message [hex] Explanation FC-TUNNEL-3-PM_ERROR: Port Manager API, [chars], failed with error
FCMPLS tunnel invoked Port Manager API and received the error code. [chars] describes the API and 0x[hex] specifies the error No action is required.
Recommended Action
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 Recommended Action
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 Recommended Action
Error Message FC-TUNNEL-3-PSS_RTDB_RESTORE_ERROR: Runtime database restoration for [chars] failed with error [hex] 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 Recommended Action
Error Message
FC-TUNNEL-3-RIB_ERROR: RIB API, [chars], failed with error [hex]
Explanation FCMPLS tunnel invoked RIB API and received the error code. [chars] describes the API and 0x[hex] specifies the error Recommended Action
FC-TUNNEL-3-RSVP_PROTO_ERROR: RSVP protocol error: [chars]
RSVP-TE protocol error is encountered. [chars] describes the error and its context. No action is required.
Recommended Action
2-141
Chapter 2
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]
Recommended Action
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
FC-TUNNEL-5-MSG_INTERFACE_UP: Interface [chars] is up
The fc interface is up No action is required.
Recommended Action
FCC_LC Messages
This section contains the FCC_LC messages.
FCC_LC-2
Error Message Explanation FCC_LC-2-ERROR_SENDING_HEART_BEAT: Error sending heart beat [dec]
FCC_LC has error sending heart beat No action is required.
Recommended Action
FCC_LC-2-EXITING: Exiting fcc_lc: [chars]
FCC_LC exiting No action is required.
Recommended Action
2-142
OL-24654-01
Chapter 2
Error Message Explanation FCC_LC-2-HEART_BEAT_NOT_SENT: Heart beat not sent for [dec] millisecs
FCC_LC has not sent heart beat No action is required.
Recommended Action
FCC_LC-2-SHUTDOWN: Process shutting down: [chars]
FCC_LC Process is shutting down No action is required.
Recommended Action
FCC_LC-2-UNABLE_READ_DATA: Unable to read fcc data ([chars])
FCC is unable to read and process relevant FCC data No action is required.
Recommended Action
FCC_LC-5
Error Message Explanation FCC_LC-5-BAD_MSG: Received bad message: [chars]
FCC_LC has received a malformed/unrecognized message No action is required.
Recommended Action
FCC_LC-5-DISABLE: FCC_LC has been disabled
FCC_LC has been disabled No action is required.
Recommended Action
FCC_LC-5-ENABLE: FCC_LC has been enabled
FCC_LC has been enabled No action is required.
Recommended Action
FCC_LC-5-STARTING: FCC_LC process started
Process started successfully No action is required.
Recommended Action
2-143
Chapter 2
FCC_LC-6
Error Message Explanation FCC_LC-6-PRIO_UPDATE: Updated enable priority to [dec]
FCC_LC is active for packets with priority <= [threshold] No action is required.
Recommended Action
FCC Messages
This section contains the FCC messages.
FCC-2
Error Message Explanation FCC-2-SHUTDOWN: Process shutting down: [chars]
FCC Process is shutting down No action is required.
Recommended Action
FCC-5
Error Message Explanation FCC-5-BAD_MSG: Received bad message: [chars]
FCC has received a malformed/unrecognized message No action is required.
Recommended Action
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 No action is required.
Recommended Action
FCC-5-DISABLE: FCC has been disabled
FCC has been disabled No action is required.
Recommended Action
FCC-5-ENABLE: FCC has been enabled
FCC has been enabled No action is required.
Recommended Action
2-144
OL-24654-01
Chapter 2
Error Message Explanation FCC-5-RATE_LIMIT_END_NOTIF: Received Rate Limit End notification
FCC has received a Rate Limit End Notification No action is required.
Recommended Action
FCC-5-RATE_LIMIT_START_NOTIF: Received Rate Limit Start notification
FCC has received a Rate Limit Start Notification No action is required.
Recommended Action
FCC-5-STARTING: FCC process started
Process started successfully No action is required.
Recommended Action
FCC-6
Error Message Explanation FCC-6-PRIO_UPDATE: Updated enable priority to [dec]
FCC is active for packets with priority <= [threshold] No action is required.
Recommended Action
FCDDH Messages
This section contains the FCDDH messages.
FCDDH-SLOT#-3
Error Message Explanation FCDDH-SLOT#-3-LOG_FCDDH_ERR: Nonrecoverable error - exiting: [chars]
Errors which cause program to exit occurred No action is required.
Recommended Action
FCDDH-SLOT#-4
Error Message Explanation FCDDH-SLOT#-4-LOG_FCDDH_WARNING: Serious error: [chars]
Serious errors which affect all normal operations occurred No action is required.
Recommended Action
2-145
Chapter 2
FCDDH-SLOT#-5
Error Message Explanation FCDDH-SLOT#-5-LOG_FCDDH_DEBUG: Unexpected error: [chars]
Unexpected errors which affect some normal operations occurred No action is required.
Recommended Action
FCDDH-SLOT#-5-LOG_FCDDH_NOTICE: [chars]
Major configuration changes No action is required.
Recommended Action
FCDD Messages
This section contains the FCDD messages.
FCDD-SLOT#-3
Error Message Explanation FCDD-SLOT#-3-LOG_FCDD_ERR: Nonrecoverable error - exiting: [chars]
Recommended Action
FCDD-SLOT#-4
Error Message Explanation FCDD-SLOT#-4-LOG_FCDD_WARNING: Warning!: [chars]
Recommended Action
FCDD-SLOT#-5
Error Message Explanation FCDD-SLOT#-5-LOG_FCDD_GCONF_FSM: [chars]
Illegal event received in Global Configuration FSM No action is required.
Recommended Action
2-146
OL-24654-01
Chapter 2
Error Message Explanation FCDD-SLOT#-5-LOG_FCDD_NOTICE: [chars]
Major configuration changes No action is required.
Recommended Action
FCDD-SLOT#-5-LOG_FCDD_RESCAN_FSM: [chars]
Illegal event received in Rescan FSM No action is required.
Recommended Action
FCDD-SLOT#-5-LOG_FCDD_TZONE_FSM: [chars]
Illegal event received in Twilight Zone Remover FSM No action is required.
Recommended Action
FCDD-SLOT#-5-LOG_FCDD_VCONF_FSM: [chars]
Illegal event received in VSAN Configuration FSM No action is required.
Recommended Action
FCDD-SLOT#-5-LOG_FCDD_VNO_FSM: [chars]
Illegal event received in VSAN Normal Operation FSM No action is required.
Recommended Action
FCDD-SLOT#-7
Error Message Explanation FCDD-SLOT#-7-LOG_FCDD_DEBUG: [chars]
Recommended Action
FCDOMAIN Messages
This section contains the FCDOMAIN messages.
2-147
Chapter 2
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.
Error Message [chars]) Explanation
FCDOMAIN-2-EPORT_ISOLATED: Isolation of interface [chars] (reason:
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. No action is required.
Recommended Action
FCDOMAIN-2-FC2BIND_FAILED: Bind to FC2 Service failed
Fcdomain has not been able to contact the FC2 module. No action is required.
Recommended Action
Error Message failed
FCDOMAIN-2-FC2_INITIALIZATION_FAILED: FC initialization sequence
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. Recommended Action
Error Message failed Explanation
FCDOMAIN-2-FC2_SET_SOCKOPT_DM_SOCK_FAILED: set sockopt to FC2 Service
Fcdomain has not been able to setsockopt to the FC2 module. No action is required.
Recommended Action
2-148
OL-24654-01
Chapter 2
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].
FCDOMAIN-2-HIGH_PRIORITY_MTSBIND_FAILED: Bind for high priority IPC
Explanation Fcdomain has not been able to contact the Inter Process Communication (IPC) module for its high priority queue. Recommended Action
FCDOMAIN-2-INITIALIZATION_FAILED: Initialization sequence failed
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. No action is required.
Recommended Action
Error Message
FCDOMAIN-2-MTSBIND_FAILED: Bind to IPC failed
Explanation Fcdomain has not been able to contact the Inter Process Communication (IPC) module. Recommended Action
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. Recommended Action
FCDOMAIN-2-MTS_INITIALIZATION_FAILED: IPC initialization sequence
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. Recommended Action
2-149
Chapter 2
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].
FCDOMAIN-2-PSSBIND_FAILED: Bind to Persistent Storage Service failed
Fcdomain has not been able to contact the Persistent Storage Service (PSS). No action is required.
Recommended Action
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.
FCDOMAIN-2-SYSBIND_FAILED: Bind to System Manager service failed
Fcdomain has not been able to contact the System Manager. No action is required.
Recommended Action
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. Recommended Action
2-150
OL-24654-01
Chapter 2
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. Recommended Action
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 failed) Explanation
FCDOMAIN-3-MTSOPENTRX_FAILED: IPC failure (opening of a transaction
Fcdomain was not able to open a transaction( HA Purposes.) No action is required.
Recommended Action
Error Message failed)
FCDOMAIN-3-MTSRECV_FAILED: IPC failure (receiving of a message
Explanation Fcdomain has not been able to receive a message from the Inter Process Communication (IPC) module. 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).
2-151
Chapter 2
Error Message failed) Explanation FCDOMAIN-3-MTSSENDREQ_FAILED: IPC failure (sending of a request
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.)
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 failed)
FCDOMAIN-3-MTS_H_RECV_FAILED: IPC failure (receiving of a message
Explanation Fcdomain has not been able to receive a message from the Inter Process Communication (IPC) module. Recommended Action
Please perform fcdomain restart in the affected VSAN (non disruptive.)
FCDOMAIN-3-NVRAMFAILURE: NVRAM open failed
Reading the last assigned runtime domain IDs from Non Volatile RAM (NVRAM) Fcdomain is able to continue without access to the Non Volatile RAM
failed.
Recommended Action
(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. Recommended Action
2-152
OL-24654-01
Chapter 2
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. Recommended Action
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. Recommended Action
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. Recommended Action
FCDOMAIN-4-FC2_CORRUPTED: Received malformed FC2 [chars] frame
Fcdomain received a malformed FC2-SWILS frame. No action is required.
Recommended Action
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.
2-153
Chapter 2
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 half full
FCDOMAIN-5-FCID_PERSISTENT_TBL_HALF_FULL: FCID persistent table is
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. No action is required.
Recommended Action
Error Message FCDOMAIN-5-UNKNOWNDOMAININCFSLOCKREQUEST: Received CFS Lock request from unknown domain [dec]. Explanation
A CFS Lock request from the unknown domain [dec] has been received. No action is required.
Recommended Action
2-154
OL-24654-01
Chapter 2
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. No action is required.
Recommended Action
Error Message FCDOMAIN-5-UNKNOWNDOMAININUNKNOWNCFSREQUEST: Received CFS request from unknown domain [dec]. Explanation
A CFS request from the unknown domain [dec] has been received. No action is required.
Recommended Action
FCDOMAIN-6
Error Message FCDOMAIN-6-BF_STARTED: BF started by [chars] Explanation
Build Fabric has been started in this VSAN No action is required.
Recommended Action
FCDOMAIN-6-CANNOTFREESINGLEFCID: Impossible to free single FCIDs
Impossible to free single FCIDs. No action is required.
Recommended Action
FCDOMAIN-6-CLEARLOCKNOTIFICATIONRECEIVED: Implict lock release.
Lock has been implicitly released due to a clear session operation. No action is required.
Recommended Action
Error Message FCDOMAIN-6-DEVICEALREADYOWNSDIFFERENTFCIDS: The device already owns different FCIDs Explanation
Requested different FCIDs without any freeing in between. No action is required.
Recommended Action
Error Message FCDOMAIN-6-DOMAINID_INVALID: Local domain ID invalid Explanation
The local domain ID is invalid. No action is required.
Recommended Action
2-155
Chapter 2
Error Message Explanation FCDOMAIN-6-DOMAINID_VALID: Local domain ID [dec] available
The domain ID [dec] is available. No action is required.
Recommended Action
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] No action is required.
to [dec].
Recommended Action
FCDOMAIN-6-EPORT_ALREADY_CREATED: Interface [chars] already created
Interface [chars] already created. No action is required.
Recommended Action
FCDOMAIN-6-EPORT_ALREADY_DOWN: Interface [chars] is already down
Interface [chars] already down. No action is required.
Recommended Action
FCDOMAIN-6-EPORT_CLEANUP: Interface [chars] received cleanup request
Fcdomain on interface [chars] has received a cleanup request. No action is required.
Recommended Action
FCDOMAIN-6-EPORT_CREATED: Creation of interface [chars]
Fcdomain is going to create interface [chars]. No action is required.
Recommended Action
FCDOMAIN-6-EPORT_DOWN: Interface [chars] is down
Fcdomain is going to remove interface [chars] from its database. No action is required.
Recommended Action
2-156
OL-24654-01
Chapter 2
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. Recommended Action
FCDOMAIN-6-FABRICNAME_INVALID: Fabric name not available
Fabric name not available. No action is required.
Recommended Action
FCDOMAIN-6-FABRICNAME_VALID: Fabric name [chars] available
Fabric name [chars] available. No action is required.
Recommended Action
FCDOMAIN-6-FCIDALREADYFREE: FCIDs already free
FCIDs already free. No action is required.
Recommended Action
FCDOMAIN-6-FCIDNOTSTORED: FCIDs not stored
FCIDs not stored. No action is required.
Recommended Action
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]. No action is required.
Recommended Action
2-157
Chapter 2
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]. No action is required.
Recommended Action
FCDOMAIN-6-FCID_ASSIGNED: Assigned single FCID [hex]:[hex]:[hex]
Assigned single FCID [hex]:[hex]:[hex]. No action is required.
Recommended Action
FCDOMAIN-6-FCID_FREED: Freed single FCID [hex]:[hex]:[hex]
Freed single FCID [hex]:[hex]:[hex]. No action is required.
Recommended Action
Error Message FCDOMAIN-6-INCORRECTDOMAINRANGE: Requested FCIDs with domain field not in expected range Explanation
Requested FCIDs with domain field not in expected range. No action is required.
Recommended Action
Error Message FCDOMAIN-6-INCORRECTDOMAIN: Requested FCIDs with domain field different from local domain Explanation
Requested FCIDs with domain field different from local domain. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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-158
OL-24654-01
Chapter 2
Error Message Explanation FCDOMAIN-6-NODOMAIN: Local domain not available
The local domain is not available yet. No action is required.
Recommended Action
FCDOMAIN-6-NOFREEFCID: No free FCIDs
No free FCIDs. No action is required.
Recommended Action
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]). Recommended Action
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. No action is required.
Recommended Action
FCDOMAIN-6-PSWSSTARTED: Principal Switch Selection started
Fcdomain started a principal switch selection phase to elect a principal switch in this No action is required.
VSAN.
Recommended Action
FCDOMAIN-6-RCF_STARTED: RCF started by [chars]
Reconfigure Fabric has been started in this VSAN No action is required.
Recommended Action
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. No action is required.
Recommended Action
2-159
Chapter 2
Error Message Explanation FCDOMAIN-6-REQUESTEDFCIDNOTFREE: Requested FCIDs not free
Requested FCIDs not free. No action is required.
Recommended Action
FCDOMAIN-6-REQUESTEDFCIDRESERVED: Requested reserved FCIDs
Requested reserved FCIDs. No action is required.
Recommended Action
Error Message FCDOMAIN-6-REQUESTEDRESERVEDFCIDMISMATCH: Requested persistent FCIDs, but there is a mismatch Explanation
Requested persistent FCIDs, but there is a mismatch. No action is required.
Recommended Action
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]. Check which switches have the same WWN and change either one.
Recommended Action
Error Message FCDOMAIN-6-TIMER_UNKNOWN: fcdomain has received a notification for an unknown timer expiration Explanation
A timer unknown to fcdomain has expired. No action is required.
Recommended Action
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 No action is required.
[dec].
Recommended Action
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. No action is required.
Recommended Action
2-160
OL-24654-01
Chapter 2
Error Message Explanation FCDOMAIN-6-UUIDNOTFOUND: Universal Unique ID (UUID) not found
Universal Unique ID (UUID) not found. No action is required.
Recommended Action
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. Recommended Action
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. No action is required.
Recommended Action
Error Message completed
FCDOMAIN-7-FABRICCONFCOMPLETEDBF: Non disruptive reconfiguration
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. Recommended Action
Error Message completed
FCDOMAIN-7-FABRICCONFCOMPLETEDRCF: Disruptive reconfiguration
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.
Recommended Action
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]. Recommended Action
2-161
Chapter 2
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. Recommended Action
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].) Recommended Action
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. No action is required.
Recommended Action
FCDOMAIN-7-INTERFACERDY: Interface [chars] ready
Interface [chars] is ready. No action is required.
Recommended Action
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. No action is required.
Recommended Action
FCDOMAIN-7-PSWSCOMPLETED: Principal Switch Selection completed
A Principal Switch Selection (PSwS phase) completed. No action is required.
Recommended Action
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].) Recommended Action
2-162
OL-24654-01
Chapter 2
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 Explanation FCFWD-4-WARNING: [chars]
Fcfwd is generating a relevant notification No action is required.
Recommended Action
2-163
Chapter 2
FCFWD-6
Error Message Explanation FCFWD-6-INFO: [chars]
An fcfwd event occurred No action is required.
Recommended Action
FCNS Messages
This section contains the FCNS messages.
FCNS-2
Error Message Explanation FCNS-2-DB_FULL: the database; max entries [dec] exceeded
Name server database is full. The max number of entries, [dec], of ports is already present in the database No action is required.
Recommended Action
FCNS-2-INIT_FAILURE: : [chars]
Fcns initialisation has failed due to [chars]. No action is required.
Recommended Action
FCNS-2-NO_RESPONSE: for query [chars] from domain [dec]
No response for query [chars] from domain [dec]. No action is required.
Recommended Action
FCNS-2-PSS_VERSION_MISMATCH: : for [chars]
Version mismatch for pss of type [chars]. No action is required.
Recommended Action
FCNS-2-RELOAD_FAILURE: : [chars]
Failed to reload information from PSS: [chars]. No action is required.
Recommended Action
2-164
OL-24654-01
Chapter 2
FCNS-3
Error Message Explanation FCNS-3-BAD_FRAME: : [chars]
Received a bad frame from the network: [chars]. No action is required.
Recommended Action
FCNS-3-CFG_FAILURE: : [chars]
A failure related to fcns configuration: [chars]. No action is required.
Recommended Action
FCNS-3-CHUNK_FAILURE: : [chars]
Chunk memory failure: [chars]. No action is required.
Recommended Action
FCNS-3-DB_FAILURE: : [chars]
A failure occured in fcns database: [chars]. No action is required.
Recommended Action
FCNS-3-MALLOC_FAILURE: : [chars]
Malloc failed: [chars]. No action is required.
Recommended Action
FCNS-3-MTS_FAILURE: : [chars] [chars]
Failure occured trying to do an MTS operation: [chars] [chars]. No action is required.
Recommended Action
FCNS-3-PSS_FAILURE: : [chars]
Pss failure: [chars]. No action is required.
Recommended Action
2-165
Chapter 2
FCNS-4
Error Message Explanation FCNS-4-QUERY_NO_RESPONSE: for query [chars] from domain [dec]
No response for query [chars] from domain [dec]. No action is required.
Recommended Action
FCNS-6
Error Message Explanation FCNS-6-DB_INFO: : [chars] [hex]
Database modification:[chars] for entry [hex]. No action is required.
Recommended Action
FCNS-6-STATUS_INFO: : [chars]
A change in fcns status: [chars]. No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-166
OL-24654-01
Chapter 2
FCOE_MGR-5
Error Message FCOE_MGR-5-FCOE_MGR_DISABLED: FCOE_MGR Disabled Explanation
FCOE_MGR Service Disabled No action is required.
Recommended Action
FCOE_MGR-5-FCOE_MGR_ENABLED: FCOE_MGR Enabled
FCOE_MGR Service nabled No action is required.
Recommended Action
Error Message FCOE_MGR-5-FCOE_MGR_INFO: [chars] Explanation
FCoE Manager general info No action is required.
Recommended Action
Error Message FCOE_MGR-5-FCOE_MGR_MODULE_LICENSE_CHECKIN: FCoE Manager License Checkin:[dec] Explanation
FCOE_MGR Line Card license checked in No action is required.
Recommended Action
Error Message FCOE_MGR-5-FCOE_MGR_MODULE_LICENSE_CHECKOUT: FCoE Manager License Checkout:[dec] Explanation
FCOE_MGR Line Card license checked out No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-167
Chapter 2
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 Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message FCSP-MGR-2-FC2_UNKNOWN_FRM_RECD_CRIT: Received an unexpected/unknown FC-2 frame on [chars] Explanation
Recommended Action
2-168
OL-24654-01
Chapter 2
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 Recommended Action
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 Recommended Action
Error Message FCSP-MGR-2-FSMU_INIT_FAILED: State Machine Infrastructure Initialization failed ( [chars] ) Explanation
Recommended Action
Error Message FCSP-MGR-2-IPC_INIT_FAILED: IPC (Inter Process Communication) Initialization failed ( [chars] ) Explanation
FC-SP Manager has been unable to initialize with the IPC infrastructure. No action is required.
Recommended Action
Error Message exiting Explanation
FCSP-MGR-2-LICENSE_UNAVAILABLE: License:[chars] unavailable, service
License of [chars] is unavailable. Service will exit now Please install the license file to continue using the feature.
Recommended Action
Error Message FCSP-MGR-2-MEM_FAILED: Memory operations failed File: [chars] Line [dec] for size [hex] bytes Explanation
Recommended Action
2-169
Chapter 2
Error Message Explanation FCSP-MGR-2-POST_INIT_FAILED: Post-Initialization failed ( [chars] )
Recommended Action
Error Message FCSP-MGR-2-PSS_INIT_FAILED: PSS Infrastructure Initialization failed ( [chars] ) Explanation
Recommended Action
FCS Messages
This section contains the FCS messages.
FCS-2
Error Message Explanation FCS-2-ALLOC_FAILED: Memory allocation failed for size:[dec]
Memory allocation failed for size [dec] Restart the process
Recommended Action
Error Message chunk Explanation
FCS-2-CHUNK_ALLOC_FAILED: Chunk memory allocation failed for [chars]
Chunk memory allocation failed. [chars] indicates the chunk name Restart the process
Recommended Action
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]. Recommended Action
Error Message FCS-2-PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec] Explanation
2-170
OL-24654-01
Chapter 2
Error Message Explanation FCS-2-RANDNUM_FAIL: [chars]
There was a critical error during random number generation. [chars] indicates details No action is required.
of the error
Recommended Action
FCS-3
Error Message Explanation FCS-3-DB_ERR: [chars]
An error occurred during an FCS database operation. [chars] indicates the reason for
the error
FCS-3-INIT_FAIL: [chars]
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 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.
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 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.
2-171
Chapter 2
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 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.
FCS-3-OTHER_ERR: [chars]
An FCS generic error occurred. [chars] indicates the description of the error No action is required.
Recommended Action
FCS-3-PSS_ERR: [chars]
An error occurred during an FCS PSS operation. [chars] indicates the PSS operation that caused the error
FCS-3-SOCK_ERR: sd: [dec], [chars]
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
FCS-5-DB_NOTICE: [chars]
An error occurred during an FCS database operation. [chars] indicates the reason for No action is required.
the error
Recommended Action
2-172
OL-24654-01
Chapter 2
FCS-6
Error Message Explanation FCS-6-BAD_CT_FRAME: Invalid FCS frame: [chars] received from [hex]
An invalid FCS FC-CT frame with [chars] received from FC-ID [hex]. No action is required.
Recommended Action
FCS-6-INFORMATION: [chars]
An event happend that affects FCS. [chars] indicates the event No action is required.
Recommended Action
Error Message VSAN [dec]
FCS-6-REXMIT_PKT: Retransmitting request [chars] to domain [dec] in
Explanation There was a retransmission of an FC2 request. [chars] indicates FCS request [dec] indicates the remote domain and [dec] the VSAN ID Recommended Action
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 No action is required.
Recommended Action
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] Recommended Action
2-173
Chapter 2
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 Recommended Action
Error Message FDMI-2-PSS_RTDB_RESTORE_ERROR: Runtime database restoration for [chars] failed with error [hex] 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 Recommended Action
FDMI-3
Error Message Explanation FDMI-3-BAD_FRAME: Malformed frame received: [chars]
Fdmi process received malformed frame. [chars] describes the malformation No action is required.
Recommended Action
FDMI-3-BAD_RESPONSE: response with command code: [hex]
Fdmi process received bad payload in response No action is required.
Recommended Action
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. Recommended Action
FDMI-3-MTS_API_ERROR: API, [chars] returned [hex]
Fdmi invoked API [chars], received the error code specified in 0x[hex] No action is required.
Recommended Action
2-174
OL-24654-01
Chapter 2
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] Recommended Action
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 Recommended Action
FDMI-3-PSS_ERROR: PSS operation [chars] returned err: [hex]
[chars] specifies the context where the failure occured and 0x[hex] specifies the err No action is required.
Recommended Action
FDMI-3-UNEXPECTED_MTS_MSG: Unexpected MTS message, opcode [dec], is
Fdmi process received unexpected MTS event. MTS opcode is specified in [dec] No action is required.
Recommended Action
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] No action is required.
Recommended Action
FDMI-6
Error Message Explanation FDMI-6-DEBUG_INFO: [chars]
Fdmi process debug info No action is required.
Recommended Action
2-175
Chapter 2
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 No action is required.
Recommended Action
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 Please contact FM team
Recommended Action
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 Please contact service owner with given uuid and FM team
Recommended Action
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 Please contact FM/sysmgr team
Recommended Action
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 Please contact FM/vdc_mgr team
Recommended Action
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 Please contact FM/vdc_mgr and rollback team
Recommended Action
2-176
OL-24654-01
Chapter 2
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 Please contact FM/sysmgr team
Recommended Action
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 Please contact FM/sysmgr team
Recommended Action
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 Please contact FM/sysmgr team and the feature owner
Recommended Action
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 Please contact FM/sysmgr team
Recommended Action
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 Please contact FM/sysmgr team
Recommended Action
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 Please contact FM/sysmgr team
Recommended Action
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 Please contact FM/sysmgr team
Recommended Action
2-177
Chapter 2
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 Please contact FM/sysmgr team
Recommended Action
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 Please contact FM/sysmgr team
Recommended Action
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 Please contact FM/sysmgr team
Recommended Action
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 Please contact FM/sysmgr team
Recommended Action
FEATURE-MGR-2-FM_FSET_VMM_OP_ERROR: [chars]
The error seen at FM and VMM interaction Please contact FM/VMM team
Recommended Action
FEATURE-MGR-2-MODULE_FM_DONE: feature manager completed
Feature manager completed No action is required.
Recommended Action
FEATURE-MGR-2-MODULE_FM_STARTED: feature manager started
Feature manager started No action is required.
Recommended Action
2-178
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
Error Message FEATURE-MGR-6-FM_AUTOCKPT_SUCCEEDED: AutoCheckpoint [chars] created successfully Explanation
AutoCheckpoint with the given name has been created successfully No action is required.
Recommended Action
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 Please contact FM team
Recommended Action
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 No action is required.
Recommended Action
FEX Messages
This section contains the FEX messages.
FEX-2
Error Message SUP ISSU Explanation FEX-2-FEX_NOT_ONLINE_SUP_ISSU: FEX [dec] did not come online after
FEX did not come online after sup ISSU No action is required.
Recommended Action
2-179
Chapter 2
Error Message Explanation FEX-2-FEX_OFFLINE: FEX [dec] has gone OFFLINE
FEX has gone OFFLINE No action is required.
Recommended Action
FEX-2-FEX_ONLINE: FEX [dec] has come ONLINE
FEX has come ONLINE No action is required.
Recommended Action
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 No action is required.
Recommended Action
FEX-2-NOHMS_ENV_FEX_OFFLINE: [chars]
Fex off-line Show inventory
Recommended Action
FEX-2-NOHMS_ENV_FEX_ONLINE: [chars]
Fex on-line Show inventory
Recommended Action
FEX-5
Error Message Explanation FEX-5-FEX_DISABLED: FEX Disabled
FEX Service Disabled No action is required.
Recommended Action
FEX-5-FEX_ENABLED: FEX Enabled
FEX Service Enabled No action is required.
Recommended Action
2-180
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
FEX-5-PINNING_CHANGED: Fex [dec] pinning information is changed
Fex pinning information changed No action is required.
Recommended Action
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 No action is required.
Recommended Action
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
FICON-2-E_PN_PA_NOT_IN_BOUND: [chars]
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.
2-181
Chapter 2
Error Message Explanation FICON-2-SHUTDOWN: FICON Manager process shutting down: [chars]
FICON Manager shutting down This is a severe error. Provide the reason given in the message.
Recommended Action
FICON-3
Error Message Explanation FICON-3-E_ASSIGN_BINDING_PN_FAIL: [chars]
Port number has fcip or port channle binding can not be removed nor changed. Remove port number binding of the logical interface first.
Recommended Action
FICON-3-E_ASSIGN_INVALID_PN_PARAM: [chars]
Invalid port number parameters in command. Check port numbers in the command.\n
Recommended Action
FICON-3-E_ASSIGN_OVERLAP_PN_FAIL: [chars]
Port number assigned to physical and logical can not overlap. Check port numbers in the command.\n
Recommended Action
FICON-3-E_ASSIGN_PN_NOT_DOWN_FAIL: [chars]
Only port number assigned to a port in down state can be removed or changed. Bring down the port first.\n
Recommended Action
FICON-3-E_ASSIGN_PROHIBIT_PN_FAIL: [chars]
Logical port address can not be prohibited. Check port numbers in the command.\n
Recommended Action
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-182
OL-24654-01
Chapter 2
Error Message Explanation FICON-3-E_INVALID_PA_BRINGUP_FAIL: [chars]
This port either has an invalid port address assigned or has no port address assigned. Assign a valid ficon port number to the port.\n
Recommended Action
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
FICON-3-E_UNASSIGN_NO_PN_FAIL: [chars]
Only port number already assigned can be removed. Check port numbers in the command.\n
Recommended Action
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 Explanation FICON-5-STARTING: FICON Manager process starting
FICON Manager process is being started No action is required.
Recommended Action
FICON-6
Error Message to [chars] FICON-6-PDCM_CHANGE: VSAN [dec] port-address [dec] prohibit mask set
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] Recommended Action
2-183
Chapter 2
Error Message Explanation FICON-6-PORT_SWAP: port number [dec] [dec] swapped
FICON portnumbers swapped No action is required.
Recommended Action
FICON-6-VSAN_DISABLED: FICON disabled on VSAN [dec]
FICON has been disabled on the given VSAN No action is required.
Recommended Action
FICON-6-VSAN_ENABLED: FICON enabled on VSAN [dec]
FICON has been enabled on the given VSAN No action is required.
Recommended Action
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-184
OL-24654-01
Chapter 2
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
2-185
Chapter 2
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. Recommended Action
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 Recommended Action
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. No action is required.
Recommended Action
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' Recommended Action
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-186
OL-24654-01
Chapter 2
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 Use 'clear core archived' or 'delete' CLI to free up space on logflash
Recommended Action
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 Please use showsysteminternalflash'tomakesuretherearenoStaleNFShandles'
Recommended Action
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.
2-187
Chapter 2
FSPF Messages
This section contains the FSPF messages.
FSPF-2
Error Message Explanation FSPF-2-SHUTDOWN: Routing daemon shutting down : [chars]
FSPF routing daemon is shutting down because of [chars] reason. This is a severe bug. Provide the reason provided and the log files for FSPF.
Recommended Action
FSPF-2
Error Message [chars] Explanation FSPF-3-BAD_FC2_PKT: Received bad FC2 packet on interface [chars] :
FSPF received a bad FC2 packet on [chars] interface , error description is [chars]. FSPF daemon has received a bad FC frame. Provide the output of 'debug fc2
Recommended Action
pkt '.
FSPF-3-CHECKSUM_FAIL: Checksum test failed for LSR domain [dec]
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
FSPF-3-FLOOD_ERR: Error in flooding the local LSR , Error = [chars]
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-188
OL-24654-01
Chapter 2
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]. Provide output of 'debug fspf error'
Recommended Action
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 '
FSPF-3-RIB_ERR: Error in RIB : [chars]
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.
2-189
Chapter 2
Error Message = [chars] Explanation FSPF-3-ROUTE_COMPUTE_ERR: Error in computing or sending routes : Error
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
FSPF-3-UNLOCK_FAIL: FSPF failure in releasing lock
There is a software failure in releasing lock of the shared resource between FSPF Provide output of 'debug fspf all '
threads.
Recommended Action
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]. Provide output of 'debug fspf error'
Recommended Action
FSPF-4
Error Message Explanation FSPF-4-FC2_DOWN_INTF: Received FC2 packet on DOWN interface [chars]
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
FSPF-4-FC2_DOWN_VSAN: Received FC2 packet on inactive vsan
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-190
OL-24654-01
Chapter 2
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.
FSPF-4-LSR_DROPPED: [chars], Dropping LSR [dec] received on interface
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
FSPF-4-LSU_RX_INIT: Dropping LSU received in state INIT on interface
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. No action is required.
Recommended Action
2-191
Chapter 2
FSPF-6
Error Message Explanation FSPF-6-ADD_LSR: New LSR added for domain [dec]
A new LSR is added to the database for domain [dec] . No action is required.
Recommended Action
FSPF-6-DELETE_LSR: LSR deleted for domain [dec]
The LSR for domain [dec] is deleted from the database. No action is required.
Recommended Action
FSPF-6-INTF_OPER_DOWN: Down on interface [chars]
FSPF has become operationally down on interface [chars]. No action is required.
Recommended Action
FSPF-6-INTF_OPER_UP: Up on interface [chars]
FSPF has become operational on interface [chars]. No action is required.
Recommended Action
FSPF-6-MAX_AGE: LSR [dec] reached Maxage
The LSR for domain [dec] reached the maximum age and will be deleted from all the connected switches . No action is required.
Recommended Action
FSPF-6-ROLLOVER: Rolling over the incarnation number of Local LSR
The incarnation number of local LSR reached the maximum value and is rolling over. No action is required.
Recommended Action
Error Message number
FSPF-6-SELF_ORIGINATED: Received local LSR with higher incarnation
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-192
OL-24654-01
Chapter 2
Error Message Explanation FSPF-6-STATE_CREATED: Internal state created [chars]
FSPF has created its internal state stateless/stateful [chars]. No action is required.
Recommended Action
FSPF-6-VSAN_OPER_DOWN: Down on vsan
FSPF has become operationally down on VSAN. No action is required.
Recommended Action
FSPF-6-VSAN_OPER_UP: Up with local domain [dec]
FSPF has started with local domain [dec]. No action is required.
Recommended Action
FSPF-7
Error Message Explanation FSPF-7-ROUTE_THREAD_STARTED: Thread number [dec] started
Route computation thread number [dec] has been started for FSPF. No action is required.
Recommended Action
GLBP Messages
This section contains the GLBP messages.
GLBP-2
Error Message Explanation GLBP-2-GLBP_URIB_INIT_ERROR: [chars]
Unicast routing initialization failed and the GLBP process terminated Please check syslog messages for URIB failures and rectify the problem
Recommended Action
GLBP-3
Error Message table Explanation GLBP-3-GLBP_ARP_ADD_FAILED: failed to add [chars]/[chars] in arp
The system was unable to add the GLBP vIP into the arp table Please check syslog messages for ARP failures and rectify the problem
Recommended Action
2-193
Chapter 2
Error Message table Explanation GLBP-3-GLBP_ARP_DEL_FAILED: failed to delete [chars]/[chars] in arp
The system was unable to delete the GLBP vIP from the arp table Please check syslog messages for ARP failures and rectify the problem
Recommended Action
GLBP-3-GLBP_FEATURE_MANAGER_ERROR: [chars]: [chars]
There was a problem in GLBP interaction with feature manager. Please check the reason for error using feature manager and rectify the
Recommended Action
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. Please check syslog messages for IP failures and rectify the problem
Recommended Action
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. Please check syslog messages for IP failures and rectify the problem
Recommended Action
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 Please check syslog messages for L2FM failures and rectify the problem
Recommended Action
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 Please check syslog messages for L2FM failures and rectify the problem
Recommended Action
GLBP-3-GLBP_ROUTE_ADD_FAILED: failed to add [chars] in routing table
The system was unable to add the GLBP vIP address into the unicast routing table Please check syslog messages for URIB failures and rectify the problem
Recommended Action
2-194
OL-24654-01
Chapter 2
Error Message table Explanation GLBP-3-GLBP_ROUTE_DEL_FAILED: failed to delete [chars] in routing
The system was unable to delete the GLBP vIP address from the unicast routing table Please check syslog messages for URIB failures and rectify the problem
Recommended Action
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 interface
GLBP-4-BADVIP1: address [chars] is in the wrong subnet for this
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 interface
GLBP-4-BADVIP3: address [chars] is the broadcast address for this
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.
2-195
Chapter 2
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 grp [dec]
GLBP-4-DUPVIP1: address [chars] already assigned to interface [chars]
Explanation The Gateway Load Balancing Protocol virtual IP address contained in the hello 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
Explanation The Gateway Load Balancing Protocol virtual IP address contained in the hello message cannot be learned. It is already assigned to this interface. Recommended Action
GLBP-4-DUPVIP3: address [chars] already assigned to another interface
Explanation The Gateway Load Balancing Protocol virtual IP address contained in the hello message cannot be learned. It is already assigned to, or overlaps with, an address on another interface or application. Recommended Action
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 Please check syslog messages for ARP failures and rectify the problem
Recommended Action
2-196
OL-24654-01
Chapter 2
GLBP-5
Error Message Explanation GLBP-5-ACTIVE_CHANGE: Active gateway is [chars]
The Gateway Load Balancing Protocol has changed active gateway. No action is required
Recommended Action
GLBP-5-FWDSTATECHANGE: fwd [dec] state changed from [chars] to
The Gateway Load Balancing Protocol forwarder has changed state. No action is required
Recommended Action
GLBP-5-FWD_CREATE: fwd [dec] created
The Gateway Load Balancing Protocol forwarder has been created. No action is required
Recommended Action
GLBP-5-FWD_DELETE: fwd [dec] deleted
The Gateway Load Balancing Protocol forwarder has been removed. No action is required
Recommended Action
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. Recommended Action
No action is required
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. Recommended Action
No action is required
GLBP-5-FWD_WEIGHTING: fwd [dec] weighting is [dec]
The Gateway Load Balancing Protocol forwarder has changed the weighting. No action is required
Recommended Action
2-197
Chapter 2
Error Message Explanation GLBP-5-GRPSTATECHANGE: state changed from [chars] to [chars]
The Gateway Load Balancing Protocol gateway has changed state. No action is required
Recommended Action
GLBP-5-MEMBER_ADD: member [chars] [chars] added
The Gateway Load Balancing Protocol gateway has added a member. No action is required
Recommended Action
GLBP-5-MEMBER_REMOVE: member [chars] [chars] removed
The Gateway Load Balancing Protocol gateway has removed a member. No action is required
Recommended Action
GLBP-5-PRIORITY: [chars] gateway priority changed to [dec]
The Gateway Load Balancing Protocol gateway has changed priority. No action is required
Recommended Action
GLBP-5-STANDBY_CHANGE: Standby gateway is [chars]
The Gateway Load Balancing Protocol has changed standby gateway. No action is required
Recommended Action
GLBP-5-TIMER: [chars] timer changed to [chars]
The Gateway Load Balancing Protocol gateway has learnt timers. No action is required
Recommended Action
GLBP-5-VIPLEARN: learnt virtual ip address [chars]
The Gateway Load Balancing Protocol gateway has learnt virtual IP address. No action is required
Recommended Action
GLBP-5-VIPUNLEARN: unlearnt virtual ip address [chars]
The Gateway Load Balancing Protocol gateway has unlearnt virtual IP address. No action is required
Recommended Action
2-198
OL-24654-01
Chapter 2
Error Message Explanation GLBP-5-WEIGHTING: weighting changed to [dec]
The Gateway Load Balancing Protocol gateway has changed the weighting. No action is required
Recommended Action
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 No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message HSRP_ENGINE-3-BFD_SESSION_CREATION_ERROR: Failed to create BFD session information([hex] [hex]), Refer logs Explanation
Recommended Action
Error Message HSRP_ENGINE-3-BFD_SESSION_REMOVAL_ERROR: Failed to remove few HSRP-BFD sessions([hex] [hex]), Refer logs Explanation
Recommended Action
2-199
Chapter 2
Error Message HSRP_ENGINE-3-ERROR_IN_ADD_VIP_TO_U6RIB: Failed to Add VIP [chars] to U6RIB (errno [hex]), Refer logs Explanation
Recommended Action
Error Message HSRP_ENGINE-3-ERROR_IN_DEL_VIP_FROM_U6RIB: Failed to delete VIP [chars] from U6RIB (errno [hex]), Refer logs Explanation
Recommended Action
HSRP_ENGINE-3-NOSOCKET: Unable to open socket
The system was unable to initialize an IP connection for the Hot Standby protocol. Make sure that there is at least one interface configured to run IP.
Recommended Action
HSRP_ENGINE-4
Error Message Explanation HSRP_ENGINE-4-BADAUTH2: Bad authentication from [chars]
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-200
OL-24654-01
Chapter 2
Error Message Explanation HSRP_ENGINE-4-DUPADDR: Duplicate address %i on [chars], sourced by %e
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. Check the configuration on all HSRP routers.
Recommended Action
Error Message HSRP_ENGINE-4-DUPVIP2: [chars] Grp [dec] address [chars] is already assigned on this interface Explanation
The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to this interface. Check the configuration on all HSRP routers.
Recommended Action
Error Message HSRP_ENGINE-4-DUPVIP3: [chars] Grp [dec] address [chars] is already assigned to, or overlaps with, an address on another interface or application Explanation
The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to, or overlaps with, an address on another interface or application. Check the configuration on all HSRP routers.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
2-201
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-202
OL-24654-01
Chapter 2
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. No action is required.
Recommended Action
HSRP_ENGINE-6
Error Message HSRP_ENGINE-6-STATECHANGE2: [chars] [chars] Grp [dec] state moving from [chars] Explanation
The router has changed state No action is required.
Recommended Action
HSRP_ENGINE-6-STATECHANGE: [chars] [chars] Grp [dec] state move to
The router has changed state No action is required.
Recommended Action
IKE Messages
This section contains the IKE messages.
IKE-3
Error Message Explanation IKE-3-CRYPTO_INIT_ERROR: IKEv2 crypto init error: [chars]
Crypto initialization error No action is required.
Recommended Action
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
IKE-3-FIPS_MODE_ERROR: Could not set FIPS mode
The FIPS mode could not be set by IKE No action is required.
Recommended Action
2-203
Chapter 2
Error Message Explanation IKE-3-IKE_PROGRAM_EXIT: [chars]
IKE process did an abnormal exit No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message IKE-3-PHASE1_NEGOTIATION_FAILED: IKEv1: Phase 1 negotiation failed for peer [chars] Explanation
IKE policy negotiation failed for peer [chars]. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message IKE-3-PHASE2_NEGOTIATION_FAILED: IKEv1: Phase 2 negotiation failed for peer [chars] Explanation
IPsec policy negotiation failed for peer [chars]. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message IKE-3-UNSUPPORTED_EXCHANGE: IKEv1: Unsupported exchange [dec] received from [chars] Explanation
A unsupported IKE exchange type [digits] was received from [chars] No action is required.
Recommended Action
2-204
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
IKE-4-MESSAGE_ERROR: IKEv2 message (from [chars]) message error:
Received a malformed message which doesntadheretotheprotocol' No action is required.
Recommended Action
IKE-4-PARSING_ERROR: IKEv2 message (from [chars]) parsing error:
Received a malformed message which can not be parsed appropriately No action is required.
Recommended Action
Error Message IKE-4-UNKNOWN_PAYLOAD: IKEv2 received message (from [chars]) with un-recognized payload ([chars]) Explanation
Received an invalid payload No action is required.
Recommended Action
IKE-4-UNSUPPORT: [chars] is not supported (message from [chars])
Received something unsupported No action is required.
Recommended Action
IKE-6
Error Message Explanation IKE-6-POLL_START_DONE: IKE is exiting since it is not enabled
IKE is exiting since it is not enabled in the configuration No action is required.
Recommended Action
ILC-SPAN Messages
This section contains the ILC-SPAN messages.
2-205
Chapter 2
ILC-SPAN-3
Error Message Explanation ILC-SPAN-3-ERROR: [chars]
Ilc_span_mgr encountered an error
ILC_HELPER Messages
This section contains the ILC-HELPER messages.
ILC_HELPER-2
Error Message Explanation ILC_HELPER-2-NO_LICENSE_REBOOT: Linecard [dec] will reboot now.
SSE License has expired, hence the linecard will be rebooted. Install appropriate SSE license to be able to use SSM features normally
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-206
OL-24654-01
Chapter 2
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.
IMAGE_DNLD-SLOT#-2-IMG_DNLD_COMPLETE: Module image download process.
Image download completed. Module image is being installed. No action is required.
Recommended Action
IMAGE_DNLD-SLOT#-2-IMG_DNLD_FAILED: Module image download process.
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 File-system repair is needed using fsck
Recommended Action
IMAGE_DNLD-SLOT#-2-IMG_DNLD_STARTED: Module image download process.
Image download started. Module image downloads are non-disruptive to module No action is required.
operation.
Recommended Action
2-207
Chapter 2
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. No action is required.
Recommended Action
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. Use the show module cli command to verify the modulesoperationalstatus.'
Recommended Action
IMAGE_UPGRADE Messages
This section contains the IMAGE_UPGRADE messages.
IMAGE_UPGRADE-SLOT#-2
Error Message Explanation IMAGE_UPGRADE-SLOT#-2-IMAGE_UPGRADE_ERROR: [chars]
Image Upgrade Error No action is required.
Recommended Action
2-208
OL-24654-01
Chapter 2
IMAGE_UPGRADE-SLOT#-4
Error Message Explanation IMAGE_UPGRADE-SLOT#-4-IMAGE_UPGRADE_INFO: [chars]
Image Upgrade Info No action is required.
Recommended Action
IM Messages
This section contains the IM messages.
IM-3
Error Message [chars] Explanation IM-3-IM_IF_FEATURE_BIND_FAILURE: Interface feature bind failed
Interface feature bind failed, so applications in that feature set may not behave No action is required.
correctly.
Recommended Action
IM-3-IM_LC_OFFLINE_ERROR: LC Offline could not be sent to vdc:[dec]
LC Offline was not relayed to some vdc, so applications may not behave correctly. No action is required.
Recommended Action
Error Message IM-3-IM_RESP_ERROR: Component [chars] opcode:[chars] in vdc:[dec] returned error:[chars] Explanation
Some component returned an error. No action is required.
Recommended Action
Error Message IM-3-IM_SEQ_ERROR: Error ([chars]) while communicating with component [chars] opcode:[chars] (for:[chars]) Explanation
Some component did not respond to a request in stipulated time. No action is required.
Recommended Action
2-209
Chapter 2
IM-5
Error Message Explanation IM-5-IM_DEMUX_ERROR: [chars]
Demux function returned error No action is required.
Recommended Action
IM-5-IM_INTERNAL_ERROR: [chars]
Internal error occurred No action is required.
Recommended Action
IM-5-IM_INTF_STATE: [chars] [chars] in vdc [dec]
Management interface state changed. No action is required.
Recommended Action
IM-5-IM_UNKNOWN_INTERFACE: [chars]
Interface is not supported or not found No action is required.
Recommended Action
INTERFACE_VLAN Messages
This section contains the INTERFACE_VLAN messages.
INTERFACE_VLAN-4
Error Message Explanation INTERFACE_VLAN-4-SVI_VLAN_DOES_NOT_EXIST: Vlan [dec] does not exist
Vlan not created before assignment Interface-vlan
Recommended Action
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 Recommended Action
2-210
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
Error Message INTERFACE_VLAN-5-IF_DOWN_ERROR_DISABLED: Interface [chars] is down. Reason [dec] Explanation
The interface encountered an error while configuring it No action is required.
Recommended Action
Error Message (Inactive) Explanation
INTERFACE_VLAN-5-IF_DOWN_INACTIVE: Interface [chars] is down
Interface VLAN has been suspended or deleted No action is required.
Recommended Action
INTERFACE_VLAN-5-SVI_DISABLED: SVI Disabled
SVI Service Disabled No action is required.
Recommended Action
INTERFACE_VLAN-5-SVI_ENABLED: SVI Enabled
SVI Service Enabled No action is required.
Recommended Action
Error Message INTERFACE_VLAN-5-SVI_GET_MAC_FAILED: Failed to acquire MAC address for SVI [hex] Explanation
SVI failed to acquire MAC address No action is required.
Recommended Action
INTERFACE_VLAN-5-SVI_INIT: SVI intialization failed with error [hex]
SVI initialziation error No action is required.
Recommended Action
2-211
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
INTERFACE_VLAN-5-SVI_MTS_TIME_OUT: MTS send timed out
SVI did not recieve response for mts message No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message INTERFACE_VLAN-5-SVI_SDB_UPDATE_FAILED: sdb update failed with ret_val [dec] Explanation
SDB updated failed for SVI No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message INTERFACE_VLAN-5-UPDOWN: Line Protocol on Interface [chars], changed state to [chars] Explanation
Line protocol status changed for an interface No action is required.
Recommended Action
2-212
OL-24654-01
Chapter 2
IOA_LC Messages
This section contains the IOA_LC messages.
IOA_LC-5
Error Message Explanation IOA_LC-5-IOA_DISABLED: IOA Disabled
IOA Service Disabled No action is required.
Recommended Action
IOA_LC-5-IOA_ENABLED: IOA Enabled
IOA Service nabled No action is required.
Recommended Action
IPACL Messages
This section contains the IPACL messages.
IPACL-0
Error Message Explanation IPACL-0-EMERG: [chars]
Ipacl caused a system failure
IPACL-1
Error Message Explanation IPACL-1-ALERT: [chars]
Ipacl caused failures in other services
2-213
Chapter 2
IPACL-2
Error Message Explanation IPACL-2-CRIT: [chars]
Ipacl encountered a catastrophic error
IPACL-3
Error Message Explanation IPACL-3-ERR: [chars]
Ipacl encountered an error
IPACL-4
Error Message Explanation IPACL-4-WARN: [chars]
Ipacl ignored the unexpected condition
Recommended Action Please perform debugipaclall',thenrecreatetheoperationscenario,tofindoutmoredetails.'
IPACL-5
Error Message Explanation IPACL-5-NOTE: [chars]
Ipacl does not support this operation
Recommended Action Please perform debugipaclall',thenrecreatetheoperationscenario,tofindoutmoredetails.'
IPACL-6
Error Message Explanation IPACL-6-INFO: [chars]
Ipacl event occurred No action is required.
Recommended Action
2-214
OL-24654-01
Chapter 2
IPFC Messages
This section contains the IPFC messages.
IPFC-2
Error Message Explanation IPFC-2-ALLOC_MEMORY: Memory allocation failed
The service failed to allocate a block of dynamic memory. No action is required.
Recommended Action
IPFC-3
Error Message Explanation IPFC-3-INIT_FAILED: Initialization failed. Component [chars]
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.
IPFC-3-IOCTL_FAILED: IOCTL failed
An IOCTL to the character device failed. Show IPFC internal interface VSAN <number
Recommended Action
IPFC-3-PSSERROR: [chars]
IPFC manager encountered a PSS error. No action is required.
Recommended Action
IPFC-5
Error Message Explanation IPFC-5-CONFIG_EVENT: VSAN interface [dec] [chars]
The specified VSAN Interface has been successfully [chars]. No action is required.
Recommended Action
2-215
Chapter 2
Error Message Explanation IPFC-5-STATE_CHANGE: VSAN interface [dec] [chars]
The specified VSAN Interface is [chars]. No action is required.
Recommended Action
IPFC-6
Error Message Explanation IPFC-6-STARTING: IP Over Fiber Channel service started
Recommended Action
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. No action is required.
Recommended Action
Error Message IPQOSMGR-2-QOSMGR_HA_FAILURE: Failed to do high availability operation: [chars]. Explanation
Recommended Action
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]. No action is required.
Recommended Action
IPQOSMGR-2-QOSMGR_MTS_FAILURE: Failed to do MTS operation: [chars].
Recommended Action
2-216
OL-24654-01
Chapter 2
Error Message IPQOSMGR-2-QOSMGR_MTS_REGISTRATION_FAILED: MTS options setting to [hex] failed for opCode: [dec]. Explanation
Recommended Action
Error Message active Explanation
IPQOSMGR-2-QOSMGR_NETWORK_QOS_POLICY_CHANGE: Policy [chars] is now
[chars] is the new active network-qos policy No action is required.
Recommended Action
Error Message IPQOSMGR-2-QOSMGR_PSS_FAILURE: Failed to do PSS operation: [chars], reason: [hex]. Explanation
Recommended Action
Error Message IPQOSMGR-2-QOSMGR_PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec]. Explanation
Recommended Action
IPQOSMGR-3
Error Message Explanation IPQOSMGR-3-QOSMGR_CONFIG_ERROR: Configuration error: [chars].
Configuration error. [chars] is the reason. No action is required.
Recommended Action
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]. No action is required.
Recommended Action
IPQOSMGR-3-QOSMGR_PPF_ERROR: PPF library error: [chars].
PPF library errors. [chars] is the reason. No action is required.
Recommended Action
2-217
Chapter 2
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]. No action is required.
Recommended Action
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
Recommended Action
IPQOSMGR-4-QOSMGR_PPF_WARNING: PPF library warning: [chars].
PPF library warning. [chars] is the reason. No action is required.
Recommended Action
IPQOSMGR-4-QOSMGR_WARNING_MSG: [chars] [dec]
QOSMGR warning messages is reported as [chars] [dec]. No action is required.
Recommended Action
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.
Recommended Action
Error Message IPQOSMGR-6-QOSMGR_STATUS: QOSMGR Status: [chars]. Explanation
QOSMGR status is reported as [chars]. No action is required.
Recommended Action
2-218
OL-24654-01
Chapter 2
IPSEC Messages
This section contains the IPSEC messages.
IPSEC-2
Error Message Explanation IPSEC-2-IPSEC_INIT: IPSec initialization of [chars] [chars]
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 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.
IPSEC-3-IPSEC_FIPS_TEST_FAILED: IPSEC FIPS compliance test failed
IPSEC FIPS compliance test failed No action is required.
Recommended Action
IPSEC-3-IPSEC_MSG_SEND_FAILURE: failed to send [chars] to sap [dec]:
Recommended Action
2-219
Chapter 2
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) No action is required.
Recommended Action
Error Message Expiry Explanation
IPSEC-5-IPSEC_DISABLED_LIC_EXPIRED: IPSec Disabled due to License
IPSec Disabled due to License Expiry No action is required.
Recommended Action
IPSEC-5-IPSEC_DISABLED: IPSec Disabled
IPSec Disabled No action is required.
Recommended Action
IPSEC-5-IPSEC_ENABLED: IPSec Enabled
IPSec Enabled No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-220
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
IPS_SB_MGR Messages
This section contains the IP_SB_MGR messages.
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 Potential node software issue. Please contact your support representative
Recommended Action
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 Potential node software issue. Please contact your support representative
Recommended Action
2-221
Chapter 2
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.
Recommended Action
Potential node software issue. Please contact your support representative
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 No action is required.
Recommended Action
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. Recommended Action
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. Recommended Action
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. No action is required.
Recommended Action
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 Please contact your support representative
linecard.
Recommended Action
2-222
OL-24654-01
Chapter 2
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 Recommended Action
Please contact your support representative
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. Please contact your support representative
Recommended Action
IPS_SB_MGR-SLOT#-6
Error Message Explanation IPS_SB_MGR-SLOT#-6-SBMGR_EVENT: Sbmgr event: [chars]
This is an event log of sb_mgr relating to a port/node No action is required.
Recommended Action
IPS Messages
This section contains the IPS messages.
IPS-2
Error Message Explanation IPS-2-ISCSI_IPS_INIT: IPS initialization of [chars] [chars]
IPS initialization failed
IPS-3
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 Informational no action required
Recommended Action
2-223
Chapter 2
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 SYSLOGDOC_CONTACT_TAC
Recommended Action
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 SYSLOGDOC_CONTACT_TAC
Recommended Action
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 SYSLOGDOC_CONTACT_TAC
Recommended Action
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 Informational no action required
Recommended Action
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 Informational no action required
Recommended Action
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 Informational no action required
Recommended Action
2-224
OL-24654-01
Chapter 2
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.
IPS-3-IPS_EGRESS_PERR: Parity error on dma-bridge egress. Count:
Parity error occured in dma-bridge egress direction.
Error Message IPS-3-IPS_FIPS_MODE_ERROR: IPS FIPS error: [chars] Explanation
IPS module FIPS mode error No action is required.
Recommended Action
Error Message IPS-3-IPS_FIPS_TEST_FAILED: IPS FIPS compliance test failed Explanation
IPS FIPS compliance test failed No action is required.
Recommended Action
IPS-3-IPS_INGRESS_PERR: Parity error on dma-bridge ingress. Count:
Parity error occured in dma-bridge ingress direction.
IPS-3-ISLB_CFS_CLEAR_FAILED: [chars]
An error occurred while clearing the CFS lock. The reason for the failure : [chars]
IPS-3-ISLB_CFS_COMMIT_FAILED: [chars]; [chars]
An error occurred while commiting the cfs config data. The reason for the failure :
[chars]
2-225
Chapter 2
Error Message Explanation IPS-3-ISLB_CFS_CONFIG_FAILED: [chars]; [chars]
An error occurred while distributing the CFS config data. The reason for the failure :
[chars]
IPS-3-ISLB_CFS_LOCK_FAILED: [chars]
An error occurred while acquiring the CFS lock. The reason for the failure : [chars]
IPS-3-ISLB_CFS_MERGE_ACTIVATION_FAILED: [chars]; [chars]
An error occurred while activating merged configuration. The reason for the failure :
[chars]
IPS-3-ISLB_CFS_MERGE_CLEARED: [chars]
Merge cleared, reason: [chars] No action is required.
Recommended Action
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] 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.
2-226
OL-24654-01
Chapter 2
Error Message Explanation IPS-3-ISLB_CFS_MERGE_FAILED: [chars]; [chars]
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] 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.
IPS-3-ISLB_CFS_MERGE_REQ_REJECTED: [chars]
Merge requested rejected, reason: [chars] No action is required.
Recommended Action
IPS-3-ISLB_CFS_MERGING_CONFIG_DB_FAILED: [chars]; [chars]
An error occurred while merging the config data. The reason for the failure : [chars]
IPS-3-ISLB_CFS_PRECOMMIT_FAILED: [chars]; [chars]
An error occurred while precommiting data. The reason for the failure : [chars]
IPS-3-ISLB_CFS_PWWN_RESV_CLAIM_FAILED: [chars]
PWWN reservation claim failed. The reason for the failure : [chars]
IPS-3-ISLB_CFS_PWWN_RESV_RELEASE_FAILED: [chars]
PWWN reservation release failed. The reason for the failure : [chars]
2-227
Chapter 2
Error Message Explanation IPS-3-ISLB_CFS_UNLOCK_FAILED: [chars]
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] 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.
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 [hex] for VSAN [dec] Explanation
ISLB zoneset activation failed. Zone server busy. Retry the iSLB zonest activation.
Recommended Action
Error Message IPS-3-ISLB_ZONE_NO_ACTIVE_ZONESET: iSLB zoneset activation returned [hex] for VSAN [dec] Explanation
ISLB zoneset activation failed. No active zoneset. Activate a zoneset in the specified VSAN and retry
Recommended Action
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
2-228
OL-24654-01
Chapter 2
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. No action is required.
Recommended Action
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. Recommended Action
2-229
Chapter 2
IPS-5
Error Message [chars] Explanation IPS-5-FCIP_BIND_FAILED: Bind failed for [chars] due to [chars] for
FCIP/ISCSI Interface bind to Ethernet port failed No action is required.
Recommended Action
Error Message IPS-5-FCIP_BPORT_KEEPALIVES_NOT_SUPPORTED: Bport Keepalives not supported for FCIP [chars] Explanation
Bport Keepalives not supported in this release Informational no action required
Recommended Action
IPS-5-FCIP_BPORT_NOT_SUPPORTED: Bport not supported for FCIP [chars]
Bport not supported in this releas Informational no action required
Recommended Action
IPS-5-FCIP_FTA_ALREADY_OFF: FTA Already Off, [chars] VSAN: [dec]
FTA Already Off Informational no action required
Recommended Action
IPS-5-FCIP_FTA_ALREADY_ON: FTA Already ON, [chars] VSAN: [dec]
FTA Already ON Informational no action required
Recommended Action
IPS-5-FCIP_FTA_CB_DOWN: FTA [chars] is DOWN
FTA is DOWN Informational no action required
Recommended Action
IPS-5-FCIP_FTA_CB_UP: FTA [chars], is UP
FTA is UP Informational no action required
Recommended Action
2-230
OL-24654-01
Chapter 2
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 Informational no action required
Recommended Action
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 Informational no action required
Recommended Action
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 Informational no action required
Recommended Action
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 Informational no action required
Recommended Action
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 Informational no action required
Recommended Action
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 Informational no action required
Recommended Action
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 Informational no action required
Recommended Action
2-231
Chapter 2
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 Informational no action required
Recommended Action
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 Informational no action required
Recommended Action
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 Informational no action required
Recommended Action
IPS-5-FCIP_FTA_TURN_ON: Turn ON FTA, [chars] VSAN: [dec]
FTA turned ON Informational no action required
Recommended Action
IPS-5-FCIP_FTA_WARNING: FTA Warning :[chars]
Generic FTA Warning Informational no action required
Recommended Action
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
IPS-5-FCIP_IF_CR_DEL: Interface [chars] [chars]
FCIP Interface was Created or Deleted No action is required.
Recommended Action
2-232
OL-24654-01
Chapter 2
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 Informational no action required
Recommended Action
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' No action is required.
Recommended Action
IPS-5-FCIP_PEER_CAVIUM: Peer FCIP [chars] is a MSM/SSN-16 linecard
Peer linecard is a MSM/SSN-16 Informational no action required
Recommended Action
Error Message linecard Explanation
IPS-5-FCIP_PEER_NON_CAVIUM: Peer FCIP [chars] is a non MSM/SSN-16
Peer linecard is non MSM/SSN-16 Informational no action required
Recommended Action
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
IPS-5-FCIP_SF_NOT_SUPPORTED: Special-Frame not supported for FCIP
Spl-Frame not supported in this release Informational no action required
Recommended Action
Error Message IPS-5-FCIP_TA_CFG_MISMATCH: [chars]: Mismatch in FCIP Tape Acceleration configuration with peer Explanation
The FCIP Tape Acceleration configuration does not match with peersconfiguration' Fix the FCIP Tape Acceleration configuration to be consistent with the peer
Recommended Action
2-233
Chapter 2
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' Fix the FCIP software to be consistent with the peer
Recommended Action
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 No action is required.
Recommended Action
Error Message for [chars] Explanation
IPS-5-FCIP_UNBIND_FAILED: UNBIND failed for [chars] due to [chars]
FCIP/ISCSI Interface UNBIND from Ethernet port failed No action is required.
Recommended Action
Error Message IPS-5-FCIP_WA_CFG_MISMATCH: [chars]: Mismatch in FCIP Write Acceleration configuration with peer Explanation
The FCIP Write Acceleration configuration does not match with peersconfiguration' Fix the FCIP Write Acceleration configuration to be consistent with the peer
Recommended Action
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 No action is required.
Recommended Action
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' Fix the FCIP XRC Emulator configuration to be consistent with the peer
Recommended Action
IPS-5-IPS_IPACL_LOG_MSG: [chars]
Details of the packet dropped due to ACLs No action is required.
Recommended Action
2-234
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-235
Chapter 2
Error Message IPS-5-ISCSI_SB_GET_TGT: iSCSI SB get [dec] targets, initiator [chars] alias [chars] ip [chars] Explanation
ISCSI FCNS query response No action is required.
Recommended Action
Error Message IPS-5-ISCSI_SESSION_CREATE_FAILURE: [chars]: iSCSI Session initiator [chars] target [chars] create failed. [chars] Explanation
ISCSI Session Create failed No action is required.
Recommended Action
Error Message IPS-5-ISCSI_SESSION_CREATE_REDIRECT: [chars]: iSCSI Session initiator [chars] target [chars] redirected to [chars]/[chars] Explanation
ISCSI Session Create redirected No action is required.
Recommended Action
Error Message IPS-5-ISCSI_SESSION_REDIRECT_TIMEOUT: iSCSI Session initiator [chars] to [chars] redirected to [chars] timeout Explanation
ISCSI Session Redirect timeout No action is required.
Recommended Action
IPS-5-ISLB_CFS_SESSION_CLEARED: CFS Session Cleared
CFS Session Cleared by user No action is required.
Recommended Action
IPS-5-PORT_IPCFG_FAILED: Cannot configure IP address for interface
Cannot configure IPS port IP address No action is required.
Recommended Action
Error Message IPS-5-SB_MGR_CORE_FAILED: Ethernet Processing core [chars] failed due to [chars] Explanation
Ethernet Processing Core failed No action is required.
Recommended Action
2-236
OL-24654-01
Chapter 2
Error Message mismatch Explanation IPS-5-SFRAME_ENTITY_ID_MISMATCH: [chars]: special frame profile ID
Special frame received and destination profile ID does not match local profile ID No action is required.
Recommended Action
Error Message mismatch Explanation
IPS-5-SFRAME_FABRIC_WWN_MISMATCH: [chars]: special frame fabric wwn
Special frame received and source/destination fabric wwn does not match local destination/ source fabric wwn No action is required.
Recommended Action
IPS-5-SFRAME_IF_ADMIN_DOWN: [chars]: special frame received if down
Special frame received and interface is admin down No action is required.
Recommended Action
IPS-5-SFRAME_IF_NOT_ENABLED: [chars]: special frame not enabled
Special frame received and interface special frame configuration is disabled No action is required.
Recommended Action
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 No action is required.
frame
Recommended Action
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
Recommended Action
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 Recommended Action
2-237
Chapter 2
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 Recommended Action
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 Informational no action required
Recommended Action
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 Informational no action required
Recommended Action
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 Informational no action required
Recommended Action
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 Informational no action required
Recommended Action
IPS-7
Error Message IPS-7-ISCSI_FCNS_QUERY_REQ: return [hex], wait [dec], VSAN [dec], Init: [chars] Explanation
ISCSI FCNS query No action is required.
Recommended Action
2-238
OL-24654-01
Chapter 2
Error Message IPS-7-ISCSI_FCNS_QUERY_RESP: result [hex], [dec] targets, wait [dec], Init: [chars] Explanation
Recommended Action
IPS-7-ISCSI_NEW_FCNS_QUERY_REQ: return [hex], VSANs [chars], Init:
ISCSI FCNS query No action is required.
Recommended Action
Error Message IPS-7-ISCSI_NEW_FCNS_QUERY_RESP: result [hex], [dec] entries, [dec] targets, [dec] total targets Init: [chars] Explanation
Recommended Action
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 Recommended Action
IPV6 Messages
This section contains the IPV6 messages.
IPV6-2
Error Message Explanation IPV6-2-ALLOC_MEMORY: Memory allocation failed
The IP Configuration Manager failed to allocate a block of dynamic memory. No action is required.
Recommended Action
2-239
Chapter 2
IPV6-3
Error Message [chars] Explanation IPV6-3-FILE_WRITE_FAILED: Writing to file [chars] failed - error:
Writing to a file failed probably due to no space. Ipv6
Recommended Action
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. Ipv6
Recommended Action
IPV6-6
Error Message Explanation IPV6-6-CONFIG_EVENT: IP Configuration Msg: [chars]
Configuration message that needs to be logged. No action is required.
Recommended Action
IPV6-6-INTERFACE_DELETED: The interface [chars] has been deleted
The specified interface has been deleted. The service will delete all the configuration on that interface. No action is required.
Recommended Action
IPV6-6-INTERFACE_EVENT: IP address [chars] [chars] on interface
The IP address [chars] has been successfully [chars] on the interface [chars]. No action is required.
Recommended Action
2-240
OL-24654-01
Chapter 2
Error Message Explanation IPV6-6-ROUTE_NOT_ACTIVE: The [chars] is not active
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.
IPV6-6-STARTING: IP configuration Manager started
The IP Configuration Manager service has successfully started. No action is required.
Recommended Action
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 Explanation IP-2-ALLOC_MEMORY: Memory allocation failed
The IP Configuration Manager failed to allocate a block of dynamic memory. No action is required.
Recommended Action
IP-3
Error Message [chars] Explanation IP-3-FILE_WRITE_FAILED: Writing to file [chars] failed - error:
Writing to a file failed probably due to no space. Ip
Recommended Action
2-241
Chapter 2
Error Message Explanation IP-3-INIT_FAILED: Initialization failed. Component [chars]
[chars].
component.
IP-4
Error Message [chars] Explanation IP-4-DAD_FAILED_EVENT: Duplicate address detected for [chars] on
Duplicate address detected for IP address. Ip
Recommended Action
IP-6
Error Message Explanation IP-6-CONFIG_EVENT: IP Configuration Msg: [chars]
Configuration message that needs to be logged. No action is required.
Recommended Action
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, No action is required.
Recommended Action
IP-6-INTERFACE_DELETED: The interface [chars] has been deleted
The specified interface has been deleted. The service will delete all the configuration on that interface. No action is required.
Recommended Action
IP-6-INTERFACE_EVENT: IP address [chars] [chars] on interface [chars]
The IP address [chars] has been successfully [chars] on the interface [chars]. No action is required.
Recommended Action
2-242
OL-24654-01
Chapter 2
Error Message Explanation IP-6-ROUTE_NOT_ACTIVE: The [chars] is not active
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.
IP-6-STARTING: IP configuration Manager started
The IP Configuration Manager service has successfully started. No action is required.
Recommended Action
ISAPI Messages
This section contains the ISAPI messages.
ISAPI-SLOT#-0
Error Message Explanation ISAPI-SLOT#-0-INVISTA_EMERG: [chars]
Isapi-invista software messages No action is required.
Recommended Action
ISAPI-SLOT#-0-MSM_EMERG: [chars]
Isapi software messages No action is required.
Recommended Action
ISAPI-SLOT#-0-NSP_EMERG: [chars]
Isapi-nsp software messages No action is required.
Recommended Action
ISAPI-SLOT#-0-SSM_EMERG: [chars]
Recommended Action
ISAPI-SLOT#-0-SSN_EMERG: [chars]
Recommended Action
2-243
Chapter 2
ISAPI-SLOT#-1
Error Message Explanation ISAPI-SLOT#-1-INVISTA_ALERT: [chars]
Recommended Action
ISAPI-SLOT#-1-MSM_ALERT: [chars]
Recommended Action
ISAPI-SLOT#-1-NSP_ALERT: [chars]
Recommended Action
ISAPI-SLOT#-1-SSM_ALERT: [chars]
Recommended Action
ISAPI-SLOT#-1-SSN_ALERT: [chars]
Recommended Action
ISAPI-SLOT#-2
Error Message Explanation ISAPI-SLOT#-2-INVISTA_CRIT: [chars]
Recommended Action
ISAPI-SLOT#-2-MSM_CRIT: [chars]
Recommended Action
2-244
OL-24654-01
Chapter 2
Error Message Explanation ISAPI-SLOT#-2-NSP_CRIT: [chars]
Recommended Action
ISAPI-SLOT#-2-SSM_CRIT: [chars]
Recommended Action
ISAPI-SLOT#-2-SSN_CRIT: [chars]
Recommended Action
ISAPI-SLOT#-3
Error Message Explanation ISAPI-SLOT#-3-INVISTA_ERROR: [chars]
Recommended Action
ISAPI-SLOT#-3-MSM_ERROR: [chars]
Recommended Action
ISAPI-SLOT#-3-NSP_ERROR: [chars]
Recommended Action
ISAPI-SLOT#-3-SSM_ERROR: [chars]
Recommended Action
2-245
Chapter 2
Error Message Explanation ISAPI-SLOT#-3-SSN_ERROR: [chars]
Recommended Action
ISAPI-SLOT#-4
Error Message Explanation ISAPI-SLOT#-4-INVISTA_WARN: [chars]
Recommended Action
ISAPI-SLOT#-4-MSM_WARN: [chars]
Recommended Action
ISAPI-SLOT#-4-NSP_WARN: [chars]
Recommended Action
ISAPI-SLOT#-4-SSM_WARN: [chars]
Recommended Action
ISAPI-SLOT#-4-SSN_WARN: [chars]
Recommended Action
ISAPI-SLOT#-5
Error Message Explanation ISAPI-SLOT#-5-INVISTA_NOTICE: [chars]
Recommended Action
2-246
OL-24654-01
Chapter 2
Error Message Explanation ISAPI-SLOT#-5-MSM_NOTICE: [chars]
Recommended Action
ISAPI-SLOT#-5-NSP_NOTICE: [chars]
Recommended Action
ISAPI-SLOT#-5-SSM_NOTICE: [chars]
Recommended Action
ISAPI-SLOT#-5-SSN_NOTICE: [chars]
Recommended Action
ISAPI-SLOT#-6
Error Message Explanation ISAPI-SLOT#-6-INVISTA_INFO: [chars]
Recommended Action
ISAPI-SLOT#-6-MSM_INFO: [chars]
Recommended Action
ISAPI-SLOT#-6-NSP_INFO: [chars]
Recommended Action
2-247
Chapter 2
Error Message Explanation ISAPI-SLOT#-6-SSM_INFO: [chars]
Recommended Action
ISAPI-SLOT#-6-SSN_INFO: [chars]
Recommended Action
ISAPI-SLOT#-7
Error Message Explanation ISAPI-SLOT#-7-INVISTA_DEBUG: [chars]
Recommended Action
ISAPI-SLOT#-7-MSM_DEBUG: [chars]
Recommended Action
ISAPI-SLOT#-7-NSP_DEBUG: [chars]
Recommended Action
ISAPI-SLOT#-7-SSM_DEBUG: [chars]
Recommended Action
ISAPI-SLOT#-7-SSN_DEBUG: [chars]
Recommended Action
ISNS Messages
This section contains the ISNS messages.
2-248
OL-24654-01
Chapter 2
ISNS-2
Error Message Explanation ISNS-2-ISNS_CFS_OPERATION_FAILED: iSNS CFS [chars] failed
ISNS CFS operation failed
ISNS-2-ISNS_INIT: iSNS initialization of [chars] [chars]
ISNS initialization failed
IVR Messages
This section contains the IVR messages.
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' Please upgrade the unsupported switches
Recommended Action
2-249
Chapter 2
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. Recommended Action
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
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
2-250
OL-24654-01
Chapter 2
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
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. No action is required.
Recommended Action
IVR-2-NO_LICENSE_SHUTDOWN: Inter-VSAN Routing is shutting down.
License required for continued IVR operation is not available. Hence IVR is shutting Install appropriate license for IVR services and then enable IVR again.
down
Recommended Action
2-251
Chapter 2
Error Message seconds. IVR-2-NO_LICENSE_WARNING: Inter-VSAN Routing would shutdown in [dec]
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
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.
Recommended Action
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
2-252
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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. Recommended Action
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. Recommended Action
2-253
Chapter 2
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 Recommended Action
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. No action is required.
Recommended Action
IVR-3-CLEAR_FAILED: [chars]
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] 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.
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. 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.
IVR-3-COMMIT_REJECTED: [chars]
Commit request received from remote switch is rejected. The reason for the failure:
[chars]
2-254
OL-24654-01
Chapter 2
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. Recommended Action
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. Recommended Action
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 Recommended Action
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.

Recommended Action
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. Recommended Action
2-255
Chapter 2
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]. Recommended Action
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. Recommended Action
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 No action is required.
device list
Recommended Action
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. Recommended Action
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. [chars] describes the error and its context. Recommended Action
2-256
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message failed Explanation
IVR-3-IVZ_ACTIVATION_FAILED: Inter-VSAN zoneset [chars] activation
Inter-VSAN zoneset activation failed. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message IVR-3-IVZ_DEACTIVATION_FAILED: Inter-VSAN zoneset [chars] deactivation failed Explanation
Inter-VSAN zoneset deactivation failed. No action is required.
Recommended Action
IVR-3-LOCK_FAILED: [chars]
An error occurred while acquiring the lock. The reason for the failure : [chars]
2-257
Chapter 2
Error Message Explanation IVR-3-MERGE_ACTIVATION_FAILED: [chars]
[chars]
IVR-3-MERGE_FAILED: reason is [chars]
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]. Recommended Action
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 0x[hex] specifies the error. Recommended Action
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.
Recommended Action
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. Recommended Action
2-258
OL-24654-01
Chapter 2
Error Message IVR-3-PSS_RTDB_RESTORE_ERROR: Runtime database restoration for [chars] failed with error [hex] 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. Recommended Action
Error Message IVR-3-QOS_IOD_UNDROP_REQUEST_TO_ACL_FAILED: qos iod undrop request vsan [dec] did [chars] failed:[chars]. Explanation This happens when either after IVR retried the request few times or ACL experienced error while processing the request. Recommended Action
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 0x[hex] specifies the error. Recommended Action
Error Message IVR-3-ROUTE_REQUEST_TO_ACL_FAILED: route [chars] request vsan [dec] domain [dec] failed:[chars]. Explanation This happens when either after IVR retried the request few times or ACL experienced error while processing the request. Recommended Action
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 No action is required.
Recommended Action
IVR-3-UNEXPECTED_MTS_MSG: Unexpected MTS message, opcode [dec], is
IVR process received unexpected MTS event. MTS opcode is specified in [dec]. No action is required.
Recommended Action
2-259
Chapter 2
Error Message Explanation IVR-3-UNLOCK_FAILED: [chars]
An error occurred while releasing the lock. The reason for the failure : [chars]
Error Message
IVR-3-VSAN_SEGMENTED: [chars]
Explanation VSAN is segmented. VSAN is removed from the topology graph and hence no Inter-VSAN traffic can flow through this VSAN. 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.
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. Recommended Action
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. Recommended Action
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. Recommended Action
IVR-4
Error Message Explanation IVR-4-AUTO_TOPOLOGY_UPDATE_DISCARDED: [chars]
Received auto topology update is discarded due to conflicts No action is required.
Recommended Action
2-260
OL-24654-01
Chapter 2
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 while processing the request. Recommended Action
IVR-4-PERSISTENT_VIRTUAL_DOMAIN_MERGE_CONFLICT: [chars]
Merge failed due to conflict in the persistent virtual domain configuration No action is required.
Recommended Action
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. Recommended Action
Error Message IVR-4-PERSISTENT_VIRTUAL_FCID_MERGE_CONFLICT: [chars] Explanation
Merge failed due to conflict in the persistent virtual fcid configuration No action is required.
Recommended Action
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. Explanation This happens when either any of the linecards being upgraded or ACL experienced error while processing the request. Recommended Action
Error Message IVR-4-ROUTE_REQUEST_TO_ACL_FAILED_AND_RETRYING: route [chars] request vsan [dec] domain [dec] failed:[chars]. Retrying the request again. Explanation This happens when either any of the linecards being upgraded or ACL experienced error while processing the request. Recommended Action
2-261
Chapter 2
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. Recommended Action
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 No action is required.
Recommended Action
Error Message registered Explanation
IVR-5-AAM_MODE_REGISTERED: Abstract ACL Manager (AAM) mode has been
Abstract ACL Manager (AAM) mode has been registered No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message IVR-5-IVR_ASSERTION_FAILED: Unexpected assertion failure in File [chars] at Line [dec] Explanation
An assertion failed in IVR code No action is required.
Recommended Action
2-262
OL-24654-01
Chapter 2
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. Recommended Action
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] No action is required.
Recommended Action
Error Message VSAN [dec] Explanation
IVR-5-IVZ_ACTIVATED_VSAN: Inter-VSAN zoneset [chars] activated in
Inter-VSAN zoneset activated in VSAN[dec]. No action is required.
Recommended Action
IVR-5-IVZ_ACTIVATED: Inter-VSAN zoneset [chars] activated
Inter-VSAN zoneset activated[dec]. No action is required.
Recommended Action
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
IVR-5-IVZ_CLEANUP_DONE: Inter-VSAN clean-up is done
Inter-VSAN related configuration is cleaned up before exiting. No action is required.
Recommended Action
2-263
Chapter 2
Error Message IVR-5-IVZ_DEACTIVATED_VSAN: Inter-VSAN zoneset [chars] deactivated in VSAN [dec] Explanation
Inter-VSAN zoneset deactivated in VSAN[dec]. No action is required.
Recommended Action
IVR-5-IVZ_DEACTIVATED: Inter-VSAN zoneset [chars] deactivated
Inter-VSAN zoneset deactivated[dec]. No action is required.
Recommended Action
Error Message activated Explanation
IVR-5-IVZ_PARTIALLY_ACTIVATED: Inter-VSAN zoneset [chars] partially
Inter-VSAN zoneset activated[dec]. Check if it is successful in all VSANs by doing show IVR zoneset status.
Recommended Action
Error Message IVR-5-IVZ_PARTIALLY_DEACTIVATED: Inter-VSAN zoneset [chars] partially deactivated Explanation
Inter-VSAN zoneset deactivated[dec]. Check if it is successful in all VSANs by doing show IVR zoneset status.
Recommended Action
Error Message Err=[chars] Explanation
IVR-5-LICENSE_CHECKIN_FAILED: Failed to checkin [chars] license:
Failed to checkin [chars] license No action is required.
Recommended Action
IVR-5-SERVICE_GROUP_ACTIVATED: Inter-VSAN Service Group has been
Inter-VSAN Service Group has been activated. No action is required.
Recommended Action
Error Message deactivated Explanation
IVR-5-SERVICE_GROUP_DEACTIVATED: Inter-VSAN Service Group has been
Inter-VSAN Service Group has been deactivated. No action is required.
Recommended Action
2-264
OL-24654-01
Chapter 2
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. Recommended Action
IVR-5-VSAN_TOPOLOGY_ACTIVATED: Inter-VSAN Topology has been
Inter-VSAN Topology has been activated. No action is required.
Recommended Action
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]

Recommended Action
IVR-6-DRAV_CRITICAL_RETRY_EXCEED: [chars]
DRAV FSM frames are attempted to be resent. The details are in [chars] No action is required.
Recommended Action
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] Recommended Action
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]

Recommended Action
2-265
Chapter 2
Error Message Explanation IVR-6-DRAV_TOPO_UPDATE: [chars]
DRAV FSM Topology has been updated as indicated by [chars] No action is required.
Recommended Action
Error Message obtained Explanation
IVR-6-LICENSE_VALID: A valid license for Inter-VSAN Routing has been
A valid license for Inter-VSAN Routing has been obtained No action is required.
Recommended Action
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. Recommended Action
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 Recommended Action
L2FMC Messages
This section contains the L2FMC messages.
L2FMC-SLOT#-0
Error Message failed! Explanation L2FMC-SLOT#-0-L2FMC_CLI_INIT_FAILED: CLI library initialization
L2FMC failed to initialize CLI infrastructure's backend library. This is a fatal error. No action is required.
Recommended Action
2-266
OL-24654-01
Chapter 2
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. No action is required.
Recommended Action
L2FMC-SLOT#-2
Error Message Explanation L2FMC-SLOT#-2-L2FMC_MEM_ALLOC: Memory allocation failed. [chars]
Recommended Action
Error Message database!
L2FMC-SLOT#-2-L2FMC_VLAN_NOT_FOUND: VLAN [dec] not found in L2FMC
Explanation L2FMC failed to find VLAN [dec] in its database. L2 MAC learning & aging on VLAN [dec] may be affected. Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
2-267
Chapter 2
Error Message Explanation L2FMC-SLOT#-6-L2FMC_INITIALIZED: Internal state created [chars]
L2FMC has created its internal state stateless/stateful [chars]. No action is required.
Recommended Action
L2FMC-SLOT#-6-L2FMC_VDC_CREATED: VDC [dec] created
Request to create VDC [dec] in L2FMC was successful. No action is required.
Recommended Action
L2FMC-SLOT#-6-L2FMC_VDC_REMOVED: VDC [dec] Removed
L2FMC has successfully removed VDC [dec] from its databases. No action is required.
Recommended Action
L2FMC-SLOT#-6-L2FMC_VDC_VLAN_CREATED: VLAN [dec] created
L2FMC has added VLAN [dec]. No action is required.
Recommended Action
L2FMC-SLOT#-6-L2FMC_VDC_VLAN_REMOVED: VLAN [dec] removed from VDC
L2FMC has successfully removed VLAN [dec] from VDC [dec]. No action is required.
Recommended Action
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. No action is required.
Recommended Action
L2FM Messages
This section contains the L2FM messages.
2-268
OL-24654-01
Chapter 2
L2FM-0
Error Message failed! Explanation L2FM-0-L2FM_CLI_INITIALIZATION_FAILED: CLI library initialization
Failed to initialize CLI infrastructure's backend library. This is a fatal error. No action is required.
Recommended Action
L2FM-0-L2FM_VDC_GWMAC_GET_FAILED: Failed to get gwmac for VDC
Failed to get gwmac for VDC. No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 Explanation
No action is required. L2fm
Recommended Action
Error Message L2FM-1-L2FM_LINE_FULL_CONDITION_STRING: Unable to insert the MAC as hardware lines are full Explanation
Recommended Action
Error Message L2FM-1-L2FM_LINE_FULL_CONDITION: Unable to insert the MAC as hardware lines are full Explanation
Recommended Action
2-269
Chapter 2
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
Recommended Action
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 Recommended Action
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 No action is required.
Recommended Action
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] No action is required.
Recommended Action
L2FM-1-L2FM_WRITE_TO_PSS_FAILED: Failed to write to PSS err [chars]
Failed to write to PSS err [chars] No action is required.
Recommended Action
L2FM-2
Error Message vlan [dec] Explanation L2FM-2-L2FM_AGING_TIME_SET_FAILED: Failed to set age time [dec] for
Failed to set age time [dec] for vlan [dec]. No action is required.
Recommended Action
2-270
OL-24654-01
Chapter 2
Error Message time [dec] Explanation L2FM-2-L2FM_GLBL_AGING_TIME_SET_FAILED: Failed to set global age
Failed to set global age time [dec] No action is required.
Recommended Action
Error Message L2FM-2-L2FM_SMAC_INS_FAILED: Failed to insert static mac for VLAN:[dec] MAC:[chars] IfIndex:[hex] Slot:[dec] Explanation
Recommended Action
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 No action is required.
Recommended Action
L2FM-4
Error Message Explanation L2FM-4-L2FM_MAC_MOVE: Mac [chars] has moved from [chars] to [chars]
Mac [string] has moved from [string] to [string] No action is required.
Recommended Action
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] No action is required.
Recommended Action
Error Message L2FM-6-L2FM_MTS_SEND_FAILED: Failed to send MTS message errno [hex] opcode [dec] Explanation
Recommended Action
2-271
Chapter 2
L2MCAST Messages
This section contains the L2MCAST messages.
L2MCAST-SLOT#-0
Error Message failed! L2MCAST-SLOT#-0-L2MCAST_CLI_INIT_FAILED: CLI library initialization
Explanation L2MCAST failed to initialize CLI infrastructure's backend library. This is a fatal error. Recommended Action
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. No action is required.
Recommended Action
L2MCAST-SLOT#-2
Error Message L2MCAST-SLOT#-2-L2MCAST_VLAN_NOT_FOUND: VLAN [dec] not found in L2MCAST database! Explanation L2MCAST failed to find VLAN [dec] in its database. L2 MAC learning & aging on VLAN [dec] may be affected. Recommended Action
L2MCAST-SLOT#-2-L2MCAST: Memory allocation failed. [chars]
Recommended Action
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 Recommended Action
2-272
OL-24654-01
Chapter 2
Error Message Explanation L2MCAST-SLOT#-6-L2MCAST_INITIALIZED: Internal state created [chars]
L2MCAST has created its internal state stateless/stateful [chars]. No action is required.
Recommended Action
L2MCAST-SLOT#-6-L2MCAST_VDC_CREATED: VDC [dec] created
Request to create VDC [dec] in L2MCAST was successful. No action is required.
Recommended Action
L2MCAST-SLOT#-6-L2MCAST_VDC_REMOVED: VDC [dec] Removed
L2MCAST has successfully removed VDC [dec] from its databases. No action is required.
Recommended Action
L2MCAST-SLOT#-6-L2MCAST_VDC_VLAN_CREATED: VLAN [dec] created
L2MCAST has added VLAN [dec]. No action is required.
Recommended Action
Error Message VDC [dec] Explanation
L2MCAST-SLOT#-6-L2MCAST_VDC_VLAN_REMOVED: VLAN [dec] removed from
L2MCAST has successfully removed VLAN [dec] from VDC [dec]. No action is required.
Recommended Action
L3VM Messages
This section contains the L3VM messages.
L3VM-5
Error Message Explanation L3VM-5-FP_TPG_CREATE: Fabricpath topology [dec] created
FP-Topology created No action is required.
Recommended Action
2-273
Chapter 2
Error Message Explanation L3VM-5-FP_TPG_DELETE: Fabricpath topology [dec] deleted
FP-Topology deleted No action is required.
Recommended Action
Error Message L3VM-5-FP_TPG_INTF_DOWN: Interface [chars] down in fabricpath topology [dec] [chars] Explanation
Interface in a FP-Topology went down No action is required.
Recommended Action
L3VM-5-FP_TPG_INTF_UP: Interface [chars] up in fabricpath topology
Interface in a FP-Topology is up No action is required.
Recommended Action
LACP Messages
This section contains the LACP messages.
LACP-3
Error Message Explanation LACP-3-GENERAL_ERROR: [chars]
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-274
OL-24654-01
Chapter 2
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.
Recommended Action
Error Message LACP-3-PACKET_TRANSMIT_ERR: [chars]: Could not send LACP packet err=[dec] Explanation
There was an error in sending LACP packet No action is required.
Recommended Action
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 Recommended Action
LACP-3-SYSTEM_MAC_ERR: [chars]: Could not get system mac[[chars]]
There was an error in acquiring system mac from VDC Mgr No action is required.
Recommended Action
LACP-5
Error Message Explanation LACP-5-LACP_DISABLED: LACP Disabled
LACP Service Disabled No action is required.
Recommended Action
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 No action is required.
Recommended Action
LACP-5-LACP_ENABLED: LACP Enabled
LACP Service Enabled No action is required.
Recommended Action
2-275
Chapter 2
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 No action is required.
Recommended Action
Error Message LACP-5-LACP_REMOTE_NOTIFY_SUCCESS: Remote notify event. Explanation
Remote notify event was successful. No action is required.
Recommended Action
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 No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message LACP-5-PORT_PRIORITY_CHANGED: [chars]: LACP port priority changed from [dec] to [dec] Explanation
LACP port priority has been changed No action is required.
Recommended Action
Error Message LACP-5-SYSTEM_PRIORITY_CHANGED: LACP system priority changed from [hex] to [hex] Explanation
LACP system priority has been changed No action is required.
Recommended Action
LC-FCFWD Messages
This section contains the LC-FCFWD messages.
2-276
OL-24654-01
Chapter 2
LC-FCFWD-3
Error Message Explanation LC-FCFWD-3-ERROR: [chars]
Lc_fcfwd encountered an error
LC-SPAN Messages
This section contains the LC-SPAN messages.
LC-SPAN-3
Error Message Explanation LC-SPAN-3-ERROR: [chars]
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. No action is required.
Recommended Action
LC_CFG-SLOT#-2-LC_CFG_ABORT: registration aborted with code [dec]
Process lc_cfg_mgr aborted registration No action is required.
Recommended Action
2-277
Chapter 2
Error Message Explanation LC_CFG-SLOT#-2-LC_CFG_EXITED: exited with code [dec]
Process lc_cfg_mgr exited No action is required.
Recommended Action
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 Reset the module
Recommended Action
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 Reset the module
Recommended Action
LC_PORT_CHANNEL-SLOT#-3
Error Message Explanation LC_PORT_CHANNEL-SLOT#-3-LC_PORT_CHANNEL_ERROR: [chars]
Recommended Action
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 No action is required.
Recommended Action
LC_PORT_MGR Messages
This section contains the LC_PORT_MGR messages.
2-278
OL-24654-01
Chapter 2
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 Explanation LC_RDL-3-SYSLOG_ALLOC_FAIL: : [chars]
RDL malloc failed : [chars] No action is required.
Recommended Action
LC_RDL-3-SYSLOG_CONTEXT_ERR: : [chars] [dec]
RDL context error: [chars] [dec] No action is required.
Recommended Action
LC_RDL-3-SYSLOG_ERR: : [chars]
RDL syslog errors : [chars] No action is required.
Recommended Action
LC_RDL-3-SYSLOG_EXIT: : [chars]
RDL exiting on errors : [chars] No action is required.
Recommended Action
LC_RDL-3-SYSLOG_INIT_FAIL: : [chars] [chars]
RDL Init Failed: [chars] [chars] No action is required.
Recommended Action
2-279
Chapter 2
Error Message Explanation LC_RDL-3-SYSLOG_MTS_ERR: : [chars]
RDL MTS errors : [chars] No action is required.
Recommended Action
LC_RDL-3-SYSLOG_MTS_REG_FAILED: : [dec] [dec]
RDL context error: [dec] [dec] No action is required.
Recommended Action
LC_RDL-6
Error Message Explanation LC_RDL-6-SYSLOG_DEBUG_1: : [chars] [hex]
RDL Debug logs: [chars] [dec] No action is required.
Recommended Action
LC_RDL-6-SYSLOG_DEBUG_2: : [chars] [hex]
RDL Debug logs: [chars] [dec] No action is required.
Recommended Action
LC_RDL-6-SYSLOG_INFO: : [chars]
RDL Debug logs: [chars] No action is required.
Recommended Action
LC_RDL-6-SYSLOG_RESP_RCVD: : [chars] [dec]
RDL context error: [chars] [dec] No action is required.
Recommended Action
LDAP Messages
This section contains the LDAP messages.
2-280
OL-24654-01
Chapter 2
LDAP-2
Error Message Explanation LDAP-2-LDAP_PROGRAM_EXIT: LDAP daemon exiting: [chars]
LDAP daemon is exiting.
LDAP-3
Error Message Explanation LDAP-3-LDAP_ERROR_MESSAGE: [chars]
LDAP Error Message No action is required.
Recommended Action
LDAP-5
Error Message Explanation LDAP-5-LDAP_MONITOR_STATUS: [chars] [chars]
Notifying Ldap server monitor status change No action is required.
Recommended Action
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 No action is required.
Recommended Action
LDAP-6
Error Message Explanation LDAP-6-LDAP_MESSAGE: [chars]
LDAP Message No action is required.
Recommended Action
2-281
Chapter 2
LDP Messages
LDP-5
Error Message Explanation LDP-5-LDP_DISABLED: LDP Disabled
MPLS_LDP Service Disabled No action is required.
Recommended Action
LDP-5-LDP_ENABLED: LDP Enabled
MPLS_LDP Service nabled No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-282
OL-24654-01
Chapter 2
LIBBASE_SVC-5
Error Message Explanation LIBBASE_SVC-5-FLOW_NOT_ALLOWED: Flow [chars] <-
Flow creation failed No action is required.
Recommended Action
Error Message LIBBASE_SVC-5-IT_NEXUS_FAILURE: [chars]. [chars] bind failure. Reason: [chars]: [hex] Explanation
IT Nexus bind failed No action is required.
Recommended Action
Error Message LIBBASE_SVC-5-IT_NEXUS_OPTIMUM_INTERFACE_LIMIT_REACHED: Interface [chars] exceeded the optimum flow limit Explanation
Iterface Flow Limit No action is required.
Recommended Action
LIBGD Messages
This section contains the LIBGD messages.
LIBGD-2
Error Message Explanation LIBGD-2-GD_ACCESS_FAILED: Guardian Failed to access reg for [chars]
Guardian Access failed No action is required.
Recommended Action
LIBGD-2-GD_CATASTROPHIC: Guardian catastrophic failure: [chars]
Guardian catastrophic error No action is required.
Recommended Action
LIBGD-2-GD_INTR: Guardian Interrupt occurred: [chars]
Interrupt occurred on the Guardian No action is required.
Recommended Action
2-283
Chapter 2
Error Message Explanation LIBGD-2-SHUTDOWN: Guardian software process exiting: [chars]
Guardian shutting down No action is required.
Recommended Action
LIBGD-3
Error Message port:[dec] Explanation LIBGD-3-EN_DATA_FAILED: Guardian enable port failed for inst:[dec]
Guardian Enable port failed for the guardian No action is required.
Recommended Action
LIBGD-5
Error Message Explanation LIBGD-5-STARTING: Guardian process starting
Guardian process is being started No action is required.
Recommended Action
LIBGD-6
Error Message port:[dec] Explanation LIBGD-6-DIS_DATA: Guardian disable port done for inst:[dec]
Disabled port successfully for guardian No action is required.
Recommended Action
LIBGD-6-EN_PORT: Guardian enable port done for inst:[dec] port:[dec]
Enabled port for the Guardian No action is required.
Recommended Action
Error Message LIBGD-6-HW_INIT: GuardianHW initialization has been done for inst: [dec] port: [dec] Explanation
Guardian HW initializtion has been called[dec] No action is required.
Recommended Action
2-284
OL-24654-01
Chapter 2
LICMGR Messages
This section contains the LICMGR messages.
LICMGR-0
Error Message [chars]. LICMGR-0-LOG_LIC_GRACE_EXPIRED: Grace period expired for feature
Explanation Unlicensed feature [chars] has exceeded itsgracetimeperiod.Applicationsusingwillbeshutdownimmediately.' Recommended Action
Please install the license file to continue using the feature.
LICMGR-1
Error Message LICMGR-1-LOG_LIC_LICENSE_EXPIRED: Evaluation license expired for feature [chars]. Explanation The named feature has exceeded itsevaluationtimeperiod.Applicationsusingthelicensewillbeshutdownafteragraceperiod.' Recommended Action
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. Recommended Action
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.
Recommended Action
2-285
Chapter 2
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.' Recommended Action
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. Recommended Action
LICMGR-2-LOG_LIC_EXIT: License manager exiting: [chars]
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.
Recommended Action
2-286
OL-24654-01
Chapter 2
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 Licensing
Recommended Action
LICMGR-3
Error Message [chars]. Explanation LICMGR-3-LOG_LIC_FILE_MISSING: License file(s) missing for feature
One or more license files for feature [chars] are missing and must be reinstalled. Please install the license file to continue using the feature.
Recommended Action
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. No action is required.
Recommended Action
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]. 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.
LICMGR-3-LOG_LIC_SERVER_DOWN: License Server Down [dec]
A connection to the license server was lost.
2-287
Chapter 2
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. Recommended Action
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.' Please install the license file to continue using the feature.
Recommended Action
LICMGR-6
Error Message Explanation LICMGR-6-LOG_CHECKPOINT_CREATED: created during license expiry.
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]. Use the showlicenseusage'commandtoverifythislicensefeatureremoval.'
Recommended Action
Error Message LICMGR-6-LOG_LIC_FEATURE_INSTALLED: Installed [dec] license(s) for feature [chars]. Explanation
Installed [dec] license(s) for feature [chars]. Use the showlicenseusage'commandtoverifythislicensefeatureinstallation.'
Recommended Action
2-288
OL-24654-01
Chapter 2
Error Message Explanation LICMGR-6-LOG_LIC_LICENSE_CLEARED_ALL: Cleared all licenses.
Cleared all license files. No action is required.
Recommended Action
LICMGR-6-LOG_LIC_LICENSE_CLEARED: Cleared license file [chars].
Uninstalled the named license file. Use the showlicense'commandtoverifythislicenseremoval.'
Recommended Action
LICMGR-6-LOG_LIC_LICENSE_INSTALLED: Installed license file [chars].
Installed the named license file. Use the showlicense'commandtoverifythislicenseinstallation.'
Recommended Action
LLDP Messages
This section contains the LLDP messages.
LLDP-3
Error Message Explanation LLDP-3-DETECT_MULTIPLE_PEERS: Multiple peers detected on [chars]
Multiple peers detected on an interface No action is required.
Recommended Action
LLDP-3-INVALID_DCBXP_RECEIVED: Received an invalid DCBXP on [chars]
Received an invalid DCBXP on an interface No action is required.
Recommended Action
LLDP-3-INVALID_LLDP_RECEIVED: Received an invalid LLDP on [chars]
Received an invalid LLDP on an interface No action is required.
Recommended Action
LLDP-3-LLDP_INTERNAL_ERROR: LLDP internal error: [chars]
Internal error is encountered No action is required.
Recommended Action
2-289
Chapter 2
LLDP-5
Error Message LDP-5-LDP_DISABLED: LDP Disabled Explanation
MPLS_LDP Service Disabled No action is required.
Recommended Action
LDP-5-LDP_ENABLED: LDP Enabled
MPLS_LDP Service nabled No action is required.
Recommended Action
LLDP-6
Error Message Explanation LLDP-6-DETECT_REMOTE_CHANGE: Remote change detected on [chars]
Remote change detected on an interface No action is required.
Recommended Action
LLDP-6-DETECT_REMOTE_DCBXP_CHANGE: Remote DCBXP change detected on
Remote DCBXP change detected on an interface No action is required.
Recommended Action
MAC Messages
This section contains the MAC messages.
MAC-SLOT#-2
Error Message Explanation MAC-SLOT#-2-MAC_INFO: [chars]
MAC Informational message No action is required.
Recommended Action
MCAST Messages
This section contains the MCAST messages.
2-290
OL-24654-01
Chapter 2
MCAST-2
Error Message Explanation MCAST-2-SHUTDOWN: Process shutting down: [chars]
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 Explanation MCAST-4-ERROR: [chars]
Mcast encountered a generic error No action is required.
Recommended Action
MCAST-5
Error Message Explanation MCAST-5-BAD_MSG: Received bad message: [chars]
Mcast has received a malformed/unrecognized message No action is required.
Recommended Action
MCAST-5-START: Process has been started
Mcast has been started No action is required.
Recommended Action
MCECTEST Messages
This section contains the MCECTEST messages.
MCECTEST-3
Error Message Explanation MCECTEST-3-ASSERTION_FAILED: [chars]
MCECTEST has hit an assert condition at file [chars] No action is required.
Recommended Action
2-291
Chapter 2
Error Message Explanation MCECTEST-3-INIT_FAIL: [chars]
MCECTEST Initialization failed. due to [chars] No action is required.
Recommended Action
MCECTEST-3-INTERNAL_ERR: [chars]
MCECTEST encountered an internal error due to [chars] No action is required.
Recommended Action
MCECTEST-3-MTS_ERR: [chars]
MCECTEST encountered an MTS error due to [chars] No action is required.
Recommended Action
MCECTEST-5
Error Message Explanation MCECTEST-5-MCECTEST_DISABLED: MCECTEST Disabled
MCECTEST Service Disabled No action is required.
Recommended Action
MCECTEST-5-MCECTEST_ENABLED: MCECTEST Enabled
MCECTEST Service enabled No action is required.
Recommended Action
MCECTEST-6
Error Message Explanation MCECTEST-6-INTERNAL_INFO: [chars]
MCECTEST got an internal info [chars] No action is required.
Recommended Action
MCM Messages
This section contains the MCM messages.
2-292
OL-24654-01
Chapter 2
MCM-2
Error Message Explanation MCM-2-MCM_CRITICAL_ERROR: Internal Critical Error
Some critical error No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
MCM-5
Error Message MCM-5-MCM_SDB_UPDATE_FAILED: sdb update failed with ret_val [dec] Explanation
SDB updated failed for MCM No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-293
Chapter 2
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 No action is required.
Recommended Action
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] and same DI returned for oiflist_index [dec]. Please collect show tech-support forwarding distribution l2/l3 multicast and show tech-support pixm. Explanation
PIXM returned duplicate DI. No action is required.
Recommended Action
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 No action is required.
request.
Recommended Action
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. No action is required.
Recommended Action
MODULE Messages
This section contains the MODULE messages.
2-294
OL-24654-01
Chapter 2
MODULE-2
Error Message [dec] Explanation MODULE-2-LCM_PRE_UPGRADE_GENERAL_FAIL: Pre upgrade message fails seq
Pre upgrade message failed. No action is required.
Recommended Action
Error Message SAP [chars] Explanation
MODULE-2-LCM_UPGRADE_DONE_GENERAL_FAIL: Upgrade done message fails
Upgrade ready message failed. No action is required.
Recommended Action
Error Message MODULE-2-LCM_UPGRADE_OVER_FAIL: Upgrade over message returned [dec] [hex] for SAP [dec] Explanation
Upgrade done message failed. No action is required.
Recommended Action
Error Message MODULE-2-LCM_UPGRADE_READY_FAIL: Upgrade ready message returned [dec] [hex] for SAP [dec] Explanation
Recommended Action
Error Message MODULE-2-LCM_UPGRADE_READY_GENERAL_FAIL: Upgrade ready message fails SAP [chars] Explanation
Recommended Action
Error Message MODULE-2-MOD_DIAG_FAIL: Module [dec] (serial: [chars]) reported failure [chars] due to [chars] in device [dec] (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 showmoduleinternalallmodule[decimaldigit]'.'
2-295
Chapter 2
Error Message MODULE-2-MOD_DNLD_FAIL: Image download failed for module [dec] (serial: [chars]) Explanation
Module [decimal digit] failed to download a new image from the supervisor.
Recommended Action Collect information about the module by issuing the command showmoduleinternalallmodule[decimaldigit]'.'
Error Message MODULE-2-MOD_FAILURE: Re-initializing module [dec] (serial: [chars]) failed. Received lc_failed from sap [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 showmodule_internalallmodule<modulenumber
MODULE-2-MOD_FAIL: Initialization of module [dec] (serial: [chars])
Explanation Module [decimal digit] reported a failure during the initialization phase and will be powered down. Recommended Action Collect information about the module by issuing the commands showmodule_internalallmodule<modulenumber
Error Message MODULE-2-MOD_MAJORSWFAIL: Module [dec] (serial: [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: [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]. Recommended Action Collect information about the module by issuing the command showmoduleinternalallmodule[decimaldigit]'.'
Error Message MODULE-2-MOD_NOT_ALIVE: Module [dec] not responding... resetting (serial: [chars]) Explanation Module [decimal digit] is not replying to the hello message: module manager is then going to reset the module. Recommended Action
2-296
OL-24654-01
Chapter 2
Error Message Explanation MODULE-2-MOD_REGFAILED: Registration failed for module [dec]
Module [decimal digit] sent the registration message notifying a failure.
Recommended Action Collect module internal information by issuing the command showmoduleinternalallmodule[decimaldigit]'.'
Error Message MODULE-2-MOD_SOMEPORTS_FAILED: Module [dec] (serial: [chars]) reported failure on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (error [hex]) Explanation
Module [decimal digit] reported a failure in the runtime diagnostic due to failure in some of the ports.
Error Message supported Explanation
MODULE-2-MOD_UNKNOWN: Module type [[dec]] in slot [dec] is not
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 showmoduleinternalallmodule[decimaldigit]''
Error Message MODULE-2-XBAR_DIAG_FAIL: Xbar [dec] (serial: [chars]) reported failure [chars] due to [chars] in device [dec] (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. Recommended Action Collect information about the module by issuing the command showmoduleinternalallxbar[decimaldigit]'.'
Error Message MODULE-2-XBAR_FAILURE: Re-initializing xbar [dec] (serial: [chars]) failed. Received lc_failed from sap [hex] Explanation
Xbar [decimal digit] reported a failure during the initialization phase and will be
rebooted.
Recommended Action Collect information about the module by issuing the commands showmodule_internalallxbar<modulenumber
MODULE-2-XBAR_FAIL: Initialization of xbar [dec] (serial: [chars])
Explanation Xbar [decimal digit] reported a failure during the initialization phase and will be powered down. Recommended Action Collect information about the module by issuing the commands showmodule_internalallxbar<modulenumber
2-297
Chapter 2
Error Message MODULE-2-XBAR_SOMEPORTS_FAILED: Xbar [dec] (serial: [chars]) reported failure on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [dec] (error [hex]) 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 supported Explanation
MODULE-2-XBAR_UNKNOWN: Xbar type [[dec]] in slot [dec] is not
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 showmoduleinternalallxbar[decimaldigit]''
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. No action is required.
Recommended Action
Error Message MODULE-3-LCM_SYSLOG_ERR: [chars] Explanation
LCM encountered an error while processing a message for module. No action is required.
Recommended Action
Error Message MODULE-3-MOD_SRG_NOT_COMPATIBLE: Module [dec] (serial: [chars]) firmware is not compatible with supervisor, downloading new image Explanation
The software version of module [decimal digit] is not supported by the supervisor.
2-298
OL-24654-01
Chapter 2
MODULE-4
Error Message MODULE-4-MOD_WARNING: Module [dec] (serial: [chars]) reported warning [chars] due to [chars] in device [dec] (device error [hex]) Explanation Module [decimal digit] reported a warning in the runtime diagnostic due to failure in some of the ports. Recommended Action Collect information about the module by issuing the command showmoduleinternalallmodule[decimaldigit]'.'
Error Message MODULE-4-XBAR_WARNING: Xbar [dec] (serial: [chars]) reported warning [chars] due to [chars] in device [dec] (device error [hex]) Explanation Xbar [decimal digit] reported a warning 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]'.'
MODULE-5
Error Message Explanation MODULE-5-ACTIVE_SUP_OK: Supervisor [dec] is active (serial: [chars])
Module [decimal digit] is ready to be configured and be able to switch traffic. No action is required.
Recommended Action
MODULE-5-LCM_MODULE_UPGRADE_END: Upgrade of module [dec] ended
Upgrade of the module has ended. No action is required.
Recommended Action
MODULE-5-LCM_MODULE_UPGRADE_START: Upgrade of module [dec] started
Upgrade of the module has been started by installer No action is required.
Recommended Action
MODULE-5-MOD_OK: Module [dec] is online (serial: [chars])
Recommended Action
2-299
Chapter 2
Error Message Explanation MODULE-5-MOD_REINIT: Re-initializing module [dec] (serial: [chars])
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 showmodule_internalallmodule<modulenumber
MODULE-5-MOD_RESTART: Module [dec] is restarting after image download
Module [decimal digit] completed image download and is restarting. No action is required.
Recommended Action
Error Message MODULE-5-MOD_STARTUP_CFG_MISMATCH: The startup configuration cannot be applied to a different module type for module [dec] (serial: [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. Recommended Action
MODULE-5-STANDBY_SUP_OK: Supervisor [dec] is standby
Recommended Action
MODULE-5-XBAR_OK: Xbar [dec] is online (serial: [chars])
Xbar [decimal digit] is ready to be configured and be able to switch traffic. No action is required.
Recommended Action
MODULE-5-XBAR_REINIT: Re-initializing xbar [dec] (serial: [chars])
Xbar [decimal digit] reported a failure during the initialization phase and will be
rebooted.
Recommended Action Collect information about the module by issuing the commands showmodule_internalallxbar<modulenumber
2-300
OL-24654-01
Chapter 2
MODULE-6
Error Message [dec] Explanation MODULE-6-MOD_PURGE_CONFIG: Purging the configuration for module
Notification is being sent to remove the module configurations. No action is required.
Recommended Action
MODULE-6-MOD_REG_OK: Registration succeeded for module [dec]
Module [decimal digit] sent a successful registration message. No action is required.
Recommended Action
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. No action is required.
Recommended Action
MONITOR-5-ETH_SPAN_SESSION_DELETED: Session [dec] deleted
Session has been deleted. No action is required.
Recommended Action
Error Message "[chars]" Explanation
MONITOR-5-ETH_SPAN_SESSION_DOWN: Session [dec] is down. Reason
Session is down, no further traffic will be spanned. No action is required.
Recommended Action
Error Message MONITOR-5-ETH_SPAN_SESSION_ERROR: Session [dec] is having error. Reason "[chars]" Explanation
The session is experiencing a problem. Delete the session and try to reconfigure it
Recommended Action
2-301
Chapter 2
Error Message Explanation MONITOR-5-ETH_SPAN_SESSION_UP: Session [dec] is up.
Session is up now. You can monitor Spanned traffic at the destination ports No action is required.
Recommended Action
NFM Messages
This section contains the NFM messages.
NFM-2
Error Message Explanation NFM-2-COMMIT_FAIL: Commit failed: client [hex], [chars]
The DDB commit failed No action is required.
Recommended Action
NFM-2-DDB_FAILURE: DDB failure: [chars]
A DDB generated failure No action is required.
Recommended Action
Error Message
NFM-2-EXITING: Exit reason: [chars]
Explanation The NFM service process has exited due to [char]. The process has probably been restarted automatically. Recommended Action
NFM-2-INIT_FAIL: NFM Service Init failed: [chars]
NFM Service initialization failed. [chars] explains the reason for the failure. No action is required.
Recommended Action
NFM-2-MALLOC_ERROR: Function [chars]: Size [dec] bytes
The NFM service could not allocate memory.
2-302
OL-24654-01
Chapter 2
Error Message Explanation NFM-2-PSS_ERROR: [chars]: PSS ret. val=[dec]
The NFM service encountered error while operating on a persistent storage database. No action is required.
Recommended Action
Error Message NFM-2-VERIFY_FAIL: Verify failed - Client [hex], Reason: [chars], Interface: [chars] Explanation
The DDB Verify failed No action is required.
Recommended Action
NFM-3
Error Message Explanation NFM-3-DDB_ERROR: DDB error: [chars]
The DDB generated error No action is required.
Recommended Action
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 No action is required.
Recommended Action
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. Recommended Action
NFM-3-INVALID_HANDLE: [chars]: handle =[hex]
The NFM service encountered an invalid handle in a persistent storage database. No action is required.
Recommended Action
NFM-3-MONITOR_NOT_FOUND: Monitor with handle [hex] from source [hex]
An Export Msg from a Linecard contained an invalid Monitor handle No action is required.
Recommended Action
2-303
Chapter 2
Error Message Explanation NFM-3-MTS_ERROR: NFM encountered the following MTS error: [chars]
NFM Service encountered an MTS error. [chars] specifies the context where the error No action is required.
occurred.
Recommended Action
NFM-3-NFM_DDB_ERROR: DDB error: [chars]
The DDB generated error No action is required.
Recommended Action
Error Message
NFM-3-PSS_CORRUPTED: [chars] PSS found corrupted
Explanation The NFM service has detected corruption in one of its persistent information database.
The database would be recreated.

Recommended Action
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 No action is required.
Recommended Action
NFM-4
Error Message Explanation NFM-4-DDB_WARNING: DDB warning: [chars]
The DDB generated warning No action is required.
Recommended Action
NFM-4-LICENSE_EXPIRED: The License has expired.
The NFM service requires a License to run and exits when the License expires. No action is required.
Recommended Action
NFM-4-NFM_DDB_WARNING: DDB warning: [chars]
The DDB generated warning No action is required.
Recommended Action
2-304
OL-24654-01
Chapter 2
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 storage databases. The persistent information has been translated to the new format. Recommended Action
NFM-5
Error Message Explanation NFM-5-FEATURE_DISABLED: NetFlow Disabled.
NetFlow Feature Disabled. No action is required.
Recommended Action
NFM-5-FEATURE_ENABLED: NetFlow Enabled.
NetFlow Feature Enabled. No action is required.
Recommended Action
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.
Recommended Action
NFM-6-BECAME_STDBY: Became STANDBY from active mode
The NFM service became standby from active mode. No action is required.
Recommended Action
NFM-6-DDB_NOTIF: DDB notification: [chars]
The DDB generated notification No action is required.
Recommended Action
Error Message NFM-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars] Explanation
The NFM service was unable to send heartbeat to the system manger No action is required.
Recommended Action
2-305
Chapter 2
Error Message Explanation NFM-6-NFM_DDB_NOTIF: DDB notification: [chars]
The DDB generated notification No action is required.
Recommended Action
NFM-6-SERVICE_UP: Initialized [chars]
The NFM service is up and ready The service was initialized in [char] mode. No action is required.
Recommended Action
NFM-6-SRV_EXIT: NFM Service shutting down gracefully
NFM Service is shutting down gracefully. This is an informational message. No action is required.
Recommended Action
NFM-6-SWITCH_OVER: Switching Over to other Sup.
The NFM service has successfully switched over to the standby supervisor card. No action is required.
Recommended Action
NFM-7
Error Message Explanation NFM-7-DEBUG: [chars]
Debug information is being sent to syslog No action is required.
Recommended Action
NFP Messages
This section contains the NFP messages.
NFP-SLOT#-2
Error Message Explanation NFP-SLOT#-2-NF_ACL_ERR: [chars]([dec]): acl error. [chars]
Acl error No DDTS.
Recommended Action
2-306
OL-24654-01
Chapter 2
Error Message Explanation NFP-SLOT#-2-NF_DDB_ERR: [chars]([dec]): ddb error. [chars]
Ddb error
NFP-SLOT#-2-NF_ERR: [chars]([dec]): nfp error. [chars]
Nfp error occured
NFP-SLOT#-2-NF_FIB_ERR: [chars]([dec]): fib error. [chars]
Fib error No DDTS.
Recommended Action
NFP-SLOT#-2-NF_NDE_ERR: [chars]([dec]): nde error. [chars]
Nde error No DDTS.
Recommended Action
NFP-SLOT#-2-NF_NFM_ERR: [chars]([dec]): nfm error. [chars]
Nfm error No DDTS.
Recommended Action
NFP-SLOT#-2-NF_QOS_ERR: [chars]([dec]): qos error. [chars]
Qos error No DDTS.
Recommended Action
NFP-SLOT#-5
Error Message Explanation NFP-SLOT#-5-NF_INFO: [chars]
Info
2-307
Chapter 2
NPC Messages
This section contains the NPC messages.
NPC-SLOT#-3
Error Message Explanation NPC-SLOT#-3-LOG_NPC_ERR: Nonrecoverable error: [chars]
Recommended Action
NPC-SLOT#-4
Error Message Explanation NPC-SLOT#-4-LOG_NPC_WARNING: Serious error: [chars]
Recommended Action
NPC-SLOT#-5
Error Message Explanation NPC-SLOT#-5-LOG_NPC_DEBUG: Unexpected error: [chars]
Recommended Action
NPC-SLOT#-5-LOG_NPC_NVP_FSM: Illegal event received: [chars]
Illegal event received in NPC_NVP FSM No action is required.
Recommended Action
NPC-SLOT#-5-LOG_NPC_VSAN_FSM: Illegal event received: [chars]
Illegal event received in NPC_VSAN FSM No action is required.
Recommended Action
NPV Messages
This section contains the NPV messages.
2-308
OL-24654-01
Chapter 2
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.
Recommended Action
NPV-2-NPV_DISABLE_FAILED: NPV could not disabled : [chars] [chars]
NPM could not disabled due to the reason specified. Please try again. No action is required.
Recommended Action
NPV-2-NPV_ENABLE_FAILED: NPV could not enabled : [chars] [chars]
NPM could not enabled due to the reason specified. Please try again. No action is required.
Recommended Action
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 No action is required.
continue.
Recommended Action
NPV-3
Error Message Explanation NPV-3-ACL_UPDATE_FAILED: [chars]
ACL update request initiated by the NPV process has failed No action is required.
Recommended Action
Error Message from CFS Explanation
NPV-3-CFS_INVALID_PAYLOAD_RECEIVED: NPV received invalid payload
NPV process received invalid payload from CFS. No action is required.
Recommended Action
2-309
Chapter 2
Error Message Explanation NPV-3-CLEAR_FAILED: [chars]
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] 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.
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. 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.
NPV-3-COMMIT_REJECTED: [chars]
Commit request received from remote switch is rejected. The reason for the failure:
[chars]
NPV-3-FC2_SEND_FAILED: [chars]
NPV process could send an FC2 message. No action is required.
Recommended Action
NPV-3-F_RJT_SENT: [chars]
NPV process sent an F_RJT frame. No action is required.
Recommended Action
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.
[chars] describes the error and its context.

Recommended Action
2-310
OL-24654-01
Chapter 2
Error Message Explanation NPV-3-LCP_PROGRAMMING_FAILED: [chars]
LCP programming request initiated by the NPV process has failed No action is required.
Recommended Action
NPV-3-LOCK_FAILED: [chars]
An error occurred while acquiring the lock. The reason for the failure : [chars]
NPV-3-LS_RJT_RCVD: [chars]
NPV process received an LS_RJT frame. No action is required.
Recommended Action
NPV-3-LS_RJT_SENT: [chars]
NPV process sent an LS_RJT frame. No action is required.
Recommended Action
NPV-3-MALLOC_FAILED: [chars]
NPV process could not allocate memory No action is required.
Recommended Action
NPV-3-MERGE_ACTIVATION_FAILED: [chars]
[chars]
NPV-3-MERGE_FAILED: [chars]
An error occurred while merging configuration. The reason for the failure : [chars]
2-311
Chapter 2
Error Message Explanation NPV-3-MTS_SEND_FAILED: [chars]
NPV process could not send an MTS message. No action is required.
Recommended Action
NPV-3-NPIV_DISABLE_FAILED: [chars]
NPIV feature could not be disabled. No action is required.
Recommended Action
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. Recommended Action
NPV-3-PORT_BRINGUP_FAILED: [chars]
NPV process has failed to bringup the port No action is required.
Recommended Action
NPV-3-PORT_REINIT_FAILED: [chars]
Port reinit request initiated by the NPV process has failed No action is required.
Recommended Action
NPV-3-UNLOCK_FAILED: [chars]
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.
2-312
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
interface.
Recommended Action
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 No action is required.
interface.
Recommended Action
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 No action is required.
interface.
Recommended Action
NPV-5-FRAME_DISCARDED: [chars]
NPV process discarded an FC2 frame. No action is required.
Recommended Action
2-313
Chapter 2
Error Message Explanation NPV-5-NPV_LOAD_BALANCE_REINIT: Server ports reinitialized : [chars]
Server ports are reinitialized to balance the loads on the external interfaces. No action is required.
Recommended Action
NPV-5-UNEXPECTED_EVENT: [chars]
NPV process has received an unexpected event in the current state. No action is required.
Recommended Action
NPV-6
Error Message Explanation NPV-6-ABTS_SENT: [chars]
NPV process sent an ABTS frame. No action is required.
Recommended Action
NPV-6-ELS_CMD_SENT_TO_CORE: [chars]
NPV process sent an ELS frame to the core switch. No action is required.
Recommended Action
NPV-6-ELS_CMD_SENT_TO_SRV: [chars]
NPV process sent an ELS frame to the server. No action is required.
Recommended Action
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.

Recommended Action
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.
Recommended Action
2-314
OL-24654-01
Chapter 2
Error Message Explanation NPV-6-FDISC_RCVD: [chars]
NPV process received an FDISC frame. No action is required.
Recommended Action
NPV-6-FDISC_SENT: [chars]
NPV process sent an FDISC frame to the core switch. No action is required.
Recommended Action
NPV-6-FLOGI_RCVD: [chars]
NPV process received an FLOGI frame. No action is required.
Recommended Action
Error Message
NPV-6-INTERNAL_FLOGI_SENT: [chars]
Explanation NPV process sent an internal FLOGI frame to the core switch on an external interface. Recommended Action
NPV-6-LOGO_RCVD: [chars]
NPV process received a LOGO frame. No action is required.
Recommended Action
NPV-6-LOGO_SENT: [chars]
NPV process sent a LOGO frame. No action is required.
Recommended Action
NPV-6-LS_ACC_RCVD: [chars]
NPV process received an LS_ACC frame. No action is required.
Recommended Action
NPV-6-LS_ACC_SENT: [chars]
NPV process sent an LS_ACC frame. No action is required.
Recommended Action
2-315
Chapter 2
Error Message Explanation NPV-6-MTS_NOTIF_RCVD: [chars]
NPV process received an MTS notification. No action is required.
Recommended Action
NPV-6-MTS_NOTIF_SENT: [chars]
NPV process sent an MTS notification. No action is required.
Recommended Action
NPV-6-MTS_REQ_RCVD: [chars]
NPV process received an MTS request. No action is required.
Recommended Action
NPV-6-MTS_REQ_SENT: [chars]
NPV process sent an MTS request. No action is required.
Recommended Action
NPV-6-MTS_RESP_RCVD: [chars]
NPV process received an MTS response. No action is required.
Recommended Action
NPV-6-MTS_RESP_SENT: [chars]
NPV process sent an MTS response. No action is required.
Recommended Action
NPV-6-NPIV_DISABLED: [chars]
NPIV feature has been disabled. No action is required.
Recommended Action
NPV-6-NPIV_ENABLED: [chars]
NPIV feature has been enabled. No action is required.
Recommended Action
2-316
OL-24654-01
Chapter 2
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. Recommended Action
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. No action is required.
Recommended Action
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. Recommended Action
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. Recommended Action
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 Recommended Action
NTP Messages
This section contains the NTP messages.
2-317
Chapter 2
NTP-2
Error Message Explanation NTP-2-NTP_SYSLOG_CRIT_ERR: : [chars]
NTP syslog Critial Error : [chars]. No action is required.
Recommended Action
NTP-2-NTP_SYSLOG_INIT_FAIL: : [chars] [chars]
NTP Initialization Failed: [chars] [chars]. No action is required.
Recommended Action
NTP-2-NTP_SYSLOG_NO_RESP_FROM_LC: from LC[dec] for [chars]
NTP did not receive response from the linecard for the request sent. No action is required.
Recommended Action
NTP-3
Error Message Explanation NTP-3-NTP_SYSLOG_ALLOC_FAIL: : [chars]
NTP syslog allocation failed : [chars]. No action is required.
Recommended Action
NTP-3-NTP_SYSLOG_ERR_EXT: : [chars] [chars]
NTP syslog Error Exit : [chars] [dec]. No action is required.
Recommended Action
NTP-3-NTP_SYSLOG_ERR: : [chars]
NTP syslog Error : [chars]. No action is required.
Recommended Action
NTP-3-NTP_SYSLOG_MTS_ERR: : [chars]
NTP MTS Error : [chars]. No action is required.
Recommended Action
2-318
OL-24654-01
Chapter 2
NTP-6
Error Message Explanation NTP-6-NTP_SYSLOG_CREATED: : [chars]; Slot No: [dec]
NTP syslog created : [chars] [chars]. No action is required.
Recommended Action
NTP-6-NTP_SYSLOG_EXIT: : [chars]
NTP syslog Exit : [chars]. No action is required.
Recommended Action
NTP-6-NTP_SYSLOG_LOGGING: : [chars]
NTP logging : [chars]. No action is required.
Recommended Action
NTP-6-NTP_SYSLOG_WARN: : [chars]
NTP syslog Warning : [chars]. No action is required.
Recommended Action
NVP Messages
This section contains the NVP messages.
NVP-6
Error Message Explanation NVP-6-NVP_INFO: [chars]
NVP daemon informational message No action is required.
Recommended Action
NVP-6-STARTING: deamon started
The NVP daemon successfully started No action is required.
Recommended Action
2-319
Chapter 2
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 Restart the linecard
Recommended Action
OC_USD Messages
This section contains the OC_USD messages.
OC_USD-2
Error Message Explanation OC_USD-2-RF_CRC: [chars]
Octopus received packets with CRC error from fabric No action is required.
Recommended Action
ORI_FWD Messages
This section contains the ORI_FWD messages.
ORI_FWD-2
Error Message Explanation ORI_FWD-2-CRIT_MSG: [chars]
Debug log message No action is required.
Recommended Action
ORI_FWD-6
Error Message Explanation ORI_FWD-6-ORF_DEBUG_MSG: [chars]
Recommended Action
ORI_MAC Messages
This section contains the ORI_MAC messages.
2-320
OL-24654-01
Chapter 2
ORI_MAC-2
Error Message Explanation ORI_MAC-2-ORI_MAC_CRIT_MSG: [chars]
Recommended Action
ORI_MAC-6
Error Message Explanation ORI_MAC-6-ORI_MAC_DEBUG_MSG: [chars]
Recommended Action
OTM Messages
This section contains the OTM messages.
OTM-2
Error Message Explanation OTM-2-OTM_EEM_FAIL: OTM failed to register with EEM
OTM process failed to register with eem, exiting now No action is required.
Recommended Action
OTM-3
Error Message Explanation OTM-3-OTM_ERROR: [chars] [chars]
[chars1][chars2] No action is required.
Recommended Action
OTM-5
Error Message [chars] Explanation OTM-5-OTM_OBJECT_STATUS: Status of tracking object [dec] changed to
Status of tracking object [dec] changed to [chars] No action is required.
Recommended Action
2-321
Chapter 2
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] No action is required.
Recommended Action
OTM-6
Error Message Explanation OTM-6-OTM_EXITED: OTM process exited
OTM process is terminated No action is required.
Recommended Action
OTM-6-OTM_OBJ_REM: : Tracking object [dec] removed
Tracking Object [dec] removed No action is required.
Recommended Action
OTM-6-OTM_STARTED: OTM process started
OTM process is up and running No action is required.
Recommended Action
OTM-6-OTM_TRACK_START: Client started tracking object [dec]
Client has started tracking object [dec] No action is required.
Recommended Action
OTM-6-OTM_TRACK_STOP: Client stopped tracking object [dec]
Client has stopped tracking object [dec] No action is required.
Recommended Action Recommended Action
PHY_USD Messages
This section contains the PHY_USD messages.
2-322
OL-24654-01
Chapter 2
PHY_USD-SLOT#-4
Error Message during ISSU PHY_USD-SLOT#-4-LOG_PHY_ISSU_LINK_ST_CHNG: Port [dec]: link state
Explanation Port Link status changed while perfoming an In Service System Upgrade. Disabling the
port.
Recommended Action
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''
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
2-323
Chapter 2
PIXM-7
Error Message PIXM-7-PIXM_SYSLOG_MESSAGE_TYPE_DEBUG: [chars] Explanation This is a debug output from PIXM Recommended Action Please collect PIXM tech support using showtechpixm'and'showtechpixmc-all''
PLATFORM Messages
This section contains the PLATFORM messages.
PLATFORM-0
Error Message clock-[dec] PLATFORM-0-CHASSIS_CLKSWITCH: Hardware clock switched to redundant
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.
Error Message switch
PLATFORM-0-CHASSIS_CLKSW_MODULE_RESET: Modules reset due to clock
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.
2-324
OL-24654-01
Chapter 2
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. Please perform a showenvtemperature'tocollectmoreinformation.'
Recommended Action
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. Recommended Action
Please perform a showenvtemperature'tocollectmoreinformation.'
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. Please perform a showenvtemperature'tocollectmoreinformation.'
Recommended Action
PLATFORM-0-PFM_EMERGENCY: [chars]
Platform Emergency No action is required.
Recommended Action
PLATFORM-0-SUP_SPROM_ERROR: Unable to read SPROM for Sup in slot
The supervisor in slot [decimal digit] was not able to read its SPROM. No action is required.
Recommended Action
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]. No action is required.
Recommended Action
Error Message drivers Explanation
PLATFORM-0-SYS_LC_DRIVER_LOAD_FAILED: Failed to load linecard module
Failed to load drivers. Image is possibly corrupt. Try to load a different image.
Recommended Action
2-325
Chapter 2
Error Message Explanation PLATFORM-0-SYS_RESET: [chars] System shutdown in [dec] seconds
System shutdown in [decimal digit] seconds. Please perform a showenvtemperature'tocollectmoreinformation.'
Recommended Action
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. Please perform a showenvfan'tocollectmoreinformation.'
Recommended Action
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. Please perform a showenvfan'tocollectmoreinformation.'
Recommended Action
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 Please perform a showenvtemperature'tocollectmoreinformation.'
threshold.
Recommended Action
Error Message PLATFORM-0-SYS_SUP_DRIVER_LOAD_FAILED: Failed to load supervisor module drivers Explanation
Failed to load drivers. Image is possibly corrupt. Try to load a different image
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
2-326
OL-24654-01
Chapter 2
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. No action is required.
Recommended Action
PLATFORM-1
Error Message operating. PLATFORM-1-FABRIC_SWITCH_FAN_FAIL: Less than 4 required fans
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. Recommended Action
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. Recommended Action
PLATFORM-1-PFM_ALERT: [chars]
Platform Alert No action is required.
Recommended Action
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.'
2-327
Chapter 2
PLATFORM-2
Error Message PLATFORM-2-9134_FAN_FAIL: Fan module [dec] Failed
PLATFORM-2-9134_FAN_OK: Fan module [dec] ok
Fan module is ok No action is required.
Recommended Action
Error Message
PLATFORM-2-CASA_FAN_FAIL: Fan module [dec] Failed
PLATFORM-2-CASA_FAN_OK: Fan module [dec] ok
Recommended Action
PLATFORM-2-CHASSIS_CLKMODFAULTY: Chassis clock module [dec] faulty
Clock module on chassis is faulty or has been removed. Please perform a showplatforminternalinfo'tocollectmoreinformation.'
Recommended Action
PLATFORM-2-CHASSIS_CLKMODOK: Chassis clock module [dec] ok
Clock module on chassis is functioning properly. No action is required.
Recommended Action
Error Message clock-[dec] Explanation
PLATFORM-2-CHASSIS_CLKSRC: Current chassis clock source is
The current chassis clock source is [decimal digit]. No action is required.
Recommended Action
2-328
OL-24654-01
Chapter 2
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. Recommended Action
Error Message PLATFORM-2-FANMOD_FAN_FAIL: Fan module [dec] ([chars] fan) Failed/Removed Explanation Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms. Recommended Action
PLATFORM-2-FANMOD_FAN_OK: Fan module [dec] ([chars] fan) ok
Recommended Action
PLATFORM-2-FAN_OK: Fan module ok
Recommended Action
Error Message PLATFORM-2-FAN_REMOVED: Fan module [dec] (Serial number [chars]) [chars] removed Explanation
Fan module is removed No action is required.
Recommended Action
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 No action is required.
Recommended Action
PLATFORM-2-MEMORY_ALERT_RECOVERED: Memory Status Alert : [chars]
Memory alert event received None
Recommended Action
2-329
Chapter 2
Error Message PLATFORM-2-MEMORY_ALERT: Memory Status Alert : [chars]. Usage [chars]% of Available Memory Explanation
Memory alert event received None
Recommended Action
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
Recommended Action Please perform a 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. No action is required.
Recommended Action
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.'
PLATFORM-2-MOD_PWRDN: Module [dec] powered down (Serial number
The module in slot [decimal digit] is powered down.
Recommended Action Please perform a 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
Recommended Action Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh owspromxbar[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.'
2-330
OL-24654-01
Chapter 2
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
Recommended Action Please perform a 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
Recommended Action Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh 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
Recommended Action Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh 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 No action needed
Recommended Action
PLATFORM-2-MOD_PWRUP: Module [dec] powered up (Serial number [chars])
The module in slot [decimal digit] is powered up. No action is required.
Recommended Action
PLATFORM-2-MOD_REMOVE: Module [dec] removed (Serial number [chars])
The module in slot [decimal digit] has been removed. No action is required.
Recommended Action
2-331
Chapter 2
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. Please perform a showenvtemperature'tocollectmoreinformation.'
Recommended Action
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. Please perform a showenvtemperature'tocollectmoreinformation.'
Recommended Action
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. Please perform a showenvtemperature'tocollectmoreinformation.'
Recommended Action
Error Message PLATFORM-2-MOD_TEMPMINOR2WARM: [chars] recovered from minor temperature alarm. Warm alarm pending. Sensor=[dec] Temperature=[dec] MinTheshold=[dec] WarmThreshold=[dec] Explanation
Recommended Action
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. Please perform a showenvtemperature'tocollectmoreinformation.'
Recommended Action
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. Recommended Action
Please perform a showenvtemperature'tocollectmoreinformation.'
2-332
OL-24654-01
Chapter 2
Error Message PLATFORM-2-MOD_TEMPWARM_OK: [chars] recovered from warm temperature alarm. Sensor=[dec] Temperature=[dec] WarmThreshold=[dec] Explanation
Recommended Action
PLATFORM-2-PFM_CRITICAL: [chars]
Platform Critical No action is required.
Recommended Action
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 Please perform a showplatforminternalerr''
Recommended Action
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 Please perform a showplatforminternalerr''
Recommended Action
Error Message chassis. Explanation
PLATFORM-2-PFM_IMG_CMPT_FAIL: Image version is not supported in this
This image version is not supported in this chassis. Sup-platform
Recommended Action
PLATFORM-2-PFM_LC_BOOT_DEV_ABSENT: No bootflash found in Module
No bootflash found. Try to put in a bootflash in the module and try again.
Recommended Action
PLATFORM-2-PFM_LC_BOOT_DEV_FAIL: Bootflash access error in Module
Bad bootflash/corrupted filesystem. Try to put in a known good bootflash in the module and try again.
Recommended Action
2-333
Chapter 2
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) Please perform a showmodule'toseethePowerDownreason.'
Recommended Action
PLATFORM-2-PFM_LC_NETBOOT_FAIL: Netboot for Module [dec] failed
Netboot failed. Try to replace the BIOS in the module.
Recommended Action
PLATFORM-2-PFM_LC_REGISTRATION_FAIL: Could not register with Module
Module registration failed. Try to replace the module.
Recommended Action
PLATFORM-2-PFM_LC_STATUS: Module [dec] powered up with [dec] status
Status for the module that failed registration. Try to replace the module.
Recommended Action
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 Switchover
Recommended Action
Error Message PLATFORM-2-PFM_MODULE_POWER_OFF_TRIGGER: Power-off [chars] due to [chars] policy trigger Explanation
Policy trigger initiated a module poweroff None
Recommended Action
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 None
Recommended Action
2-334
OL-24654-01
Chapter 2
Error Message PLATFORM-2-PFM_MODULE_POWER_ON: Manual power-on of [chars] from Command Line Interface Explanation
User initiated a module power-on from the CLI None
Recommended Action
Error Message PLATFORM-2-PFM_MODULE_RESET: Manual restart of Module [dec] from Command Line Interface Explanation
User initiated a module reload from the CLI None
Recommended Action
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. Try to replace the standby supervisor.
Recommended Action
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 Upgrade Power Managment EPLD
Recommended Action
Error Message powerup Explanation
PLATFORM-2-PFM_STDBY_POWERUP_FAIL: standby supervisor failed to
Standby supervisor failed to powerup. Try to replace the standby supervisor.
Recommended Action
Error Message PLATFORM-2-PFM_SYSTEM_RESET_TRIGGER: System restart due to [chars] policy trigger Explanation
Policy/trigger initiated a system reload None
Recommended Action
Error Message Interface Explanation
PLATFORM-2-PFM_SYSTEM_RESET: Manual system restart from Command Line
User initiated a system reload from the CLI None
Recommended Action
2-335
Chapter 2
Error Message PLATFORM-2-PFM_SYSTEM_SHUTDOWN_TRIGGER: System shutdown due to [chars] policy trigger Explanation
Policy/trigger initiated a system shutdown None
Recommended Action
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 None
Recommended Action
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 Load the associated plugin
Recommended Action
Error Message PLATFORM-2-PS_ABSENT: Power supply [dec] is absent/shutdown, ps-redundancy might be affected Explanation
Power Supply is absent. No action is required.
Recommended Action
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 showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.'
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.
Recommended Action Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc. Please perform showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.'
2-336
OL-24654-01
Chapter 2
Error Message PLATFORM-2-PS_DETECT: Power supply [dec] detected but shutdown (Serial number [chars]) 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
Recommended Action Please perform a showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.Pleaserefertopow ersupplydocumentonincreasingdecreasingpowersupplycapacity,configuringpowersupplies,etc.'
PLATFORM-2-PS_FANFAIL: Fan in Power supply [dec] failed
Fan module in the Power Supply has failed
PLATFORM-2-PS_FANOK: Fan in Power supply [dec] ok
Fan module in the Power Supply is ok. No action is required.
Recommended Action
Error Message PLATFORM-2-PS_MISMATCH: Detected power supply [chars]. This reduces the redundant power available to the system and can cause service disruptions (Serial number [chars]) Explanation Detected a new power supply that has reduced capacity than an existing power supply. Recommended Action Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc. Please perform showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.'
PLATFORM-2-PS_OK: Power supply [dec] ok (Serial number [chars])
Power Supply is ok. No action is required.
Recommended Action
2-337
Chapter 2
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. No action is required.
Recommended Action
PLATFORM-2-PS_RED_MODE_CHG: Power supply redundancy mode changed to
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. No action is required.
Recommended Action
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. Power supply unit may be faulty. Contact CISCO to replace the unit.
Recommended Action
PLATFORM-2-PS_REMOVE: Power supply [dec] removed (Serial number
Power Supply is removed. No action is required.
Recommended Action
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.
Recommended Action Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc.
2-338
OL-24654-01
Chapter 2
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.
Recommended Action Please refer to power supply document on increasing decreasing power supply 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.
Recommended Action Please perform a 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.
Recommended Action Please perform a showsprommodule[decimaldigit]1'toreadmoduleIDPROMcontentsandverifytheinformation.'
PLATFORM-2-SYS_IDPROMBAD: Chassis IDPROM [dec] data invalid
Chassis IDPROM [decimal digit] contains invalid data.
Recommended Action Please perform a showsprommodule[decimaldigit]1'toreadmoduleIDPROMcontentsandcollectmoreinformation.'
PLATFORM-2-XBAR_DETECT: Xbar [dec] detected (Serial number [chars])
A new xbar in slot [decimal digit] is detected. No action is required.
Recommended Action
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
Recommended Action Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh owspromxbar[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.''
2-339
Chapter 2
Error Message Explanation PLATFORM-2-XBAR_REMOVE: Xbar [dec] removed (Serial number [chars])
The xbar in slot [decimal digit] has been removed. No action is required.
Recommended Action
PLATFORM-3
Error Message PLATFORM-3-EJECTOR_STAT_CHANGED: Ejectorsstatusinslot[dec]haschanged,[chars]Ejectoris[chars],[chars]Ejectoris[cha rs]' Explanation
Ejector status has changed None
Recommended Action
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]) Explanation
PLATFORM-3-PFM_ERROR: [chars]
Platform Error No action is required.
Recommended Action
Error Message PLATFORM-3-SINGLE_EJECTOR_STAT_CHANGED: Ejectorsstatusinslot[dec]haschanged,Ejectoris[chars]' Explanation
Ejector status has changed None
Recommended Action
2-340
OL-24654-01
Chapter 2
Error Message PLATFORM-3-XBAR_BRINGUP_MULTI_LIMIT: Giving up after multiple attempts were made to bring up the Xbar [dec], (Serial number [chars]) Explanation
Recommended Action Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh 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
PLATFORM-3-XBAR_PWRFAIL: Xbar [dec] failed to power up (Serial number
The xbar in slot [decimal digit] failed to power up
Recommended Action Please perform a 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 Recommended Action Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh owspromxbar[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.'
2-341
Chapter 2
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. Please perform a showenvtemperature'tocollectmoreinformation.'
Recommended Action
PLATFORM-4-MOD_TEMPFAIL: [chars] temperature sensor [dec] failed
Module in slot [decimal digit] contains a faulty temperature sensor. Please perform a showenvtemperature'tocollectmoreinformation.'
Recommended Action
PLATFORM-4-PFM_FAN_FLTR_STATUS: Fan Filter status: [chars]
Fan Filter status: Present/Absent Please perform a showplatforminternalinfo.'
Recommended Action
PLATFORM-4-PFM_PS_RED_MODE_CHG: Power redundancy mode changed to
Power redundancy mode changed Please perform a showplatforminternalinfo.'
Recommended Action
PLATFORM-4-PFM_WARNING: [chars]
Platform Warning No action is required.
Recommended Action
PLATFORM-5
Error Message PLATFORM-5-FAN_DETECT: Fan module [dec] (Serial number [chars]) [chars] detected Explanation
Fan module is detected No action is required.
Recommended Action
2-342
OL-24654-01
Chapter 2
Error Message PLATFORM-5-FAN_STATUS: Fan module [dec] (Serial number [chars]) [chars] current-status is [chars] Explanation
Fan module changed status No action is required.
Recommended Action
PLATFORM-5-FEX_FAN_DETECT: Fex [dec] Fan Module [dec] detected
Fex Fan module is detected No action is required.
Recommended Action
PLATFORM-5-FEX_FAN_REMOVE: Fex [dec] Fan Module [dec] removed
Fex Fan module is removed No action is required.
Recommended Action
Error Message PLATFORM-5-FEX_PS_FOUND: Fex [dec] Power Supply [dec] found (Serial number [chars]) Explanation
Fex power supply is found No action is required.
Recommended Action
Error Message PLATFORM-5-FEX_PS_REMOVE: Fex [dec] Power Supply [dec] removed (Serial number [chars]) Explanation
Fex power supply is removed No action is required.
Recommended Action
PLATFORM-5-MOD_STATUS: [chars] current-status is [chars]
Module in slot [decimal digit] changed status. No action is required.
Recommended Action
PLATFORM-5-PFM_NOTICE: [chars]
Platform Notice No action is required.
Recommended Action
2-343
Chapter 2
Error Message Explanation PLATFORM-5-PS_FOUND: Power supply [dec] found (Serial number [chars])
Power Supply is detected. No action is required.
Recommended Action
PLATFORM-5-PS_STATUS: PowerSupply [dec] current-status is [chars]
Module in slot [decimal digit] changed status. No action is required.
Recommended Action
PLATFORM-5-XBAR_PWRDN: Xbar [dec] powered down (Serial number
The xbar in slot [decimal digit] is powered down.
Recommended Action Please perform a showmodulexbar','showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodul e[decimaldigit]'tocollectmoreinformationifyoususpectmodulehasbeenpowereddownduetoerrors.'
PLATFORM-5-XBAR_PWRUP: Xbar [dec] powered up (Serial number [chars])
The xbar in slot [decimal digit] is powered up. No action is required.
Recommended Action
PLATFORM-6
Error Message Explanation PLATFORM-6-PFM_INFO: [chars]
Platform Info No action is required.
Recommended Action
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. Please perform a showenvtemperature'tocollectmoreinformation.'
Recommended Action
2-344
OL-24654-01
Chapter 2
PLOG_SUP Messages
This section contains the PLOG_SUP messages.
PLOG_SUP-4
Error Message [dec]. Explanation PLOG_SUP-4-PLOG_SUP_EXIT: Persistent Logger encountered an error
Persistent Logger encountered an error No action is required.
Recommended Action
PLOG Messages
This section contains the PLOG messages.
PLOG-4
Error Message Explanation PLOG-4-PLOG_LC_EXIT: Persistent Logger encountered an error [dec]
Persistent Logger encountered an error No action is required.
Recommended Action
PONG Messages
This section contains the PONG messages.
PONG-5
Error Message Explanation PONG-5-PONG_DISABLED: Pong Manager disabled
Pong Service Enabled No action is required.
Recommended Action
PONG-5-PONG_ENABLED: Pong Manager enabled
Pong Service Enabled No action is required.
Recommended Action
2-345
Chapter 2
Error Message Explanation PONG-5-PONG_INJECTED: Pong packet injected
Pong packet injected No action is required.
Recommended Action
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 Module will be automatically reset
Recommended Action
PORT-CHANNEL-1-MALLOC_FAILED: cannot allocate memory (size [dec])
No enough memory No action is required.
Recommended Action
Error Message PORT-CHANNEL-1-MAP_PARAM_FAILURE: mapping parameter failed for [chars] [[chars]] Explanation
Parameter mapping failed Specified service is misbehaving; check its status
Recommended Action
PORT-CHANNEL-1-MCAST_SEND_FAILURE: failed to send multicast [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 Convert the auto created channel to presistent by doing port-channel <n
Recommended Action
2-346
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
PORT-CHANNEL-3
Error Message Explanation PORT-CHANNEL-3-COMPAT_CHECK_FAILURE: [chars] is not compatible
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
PORT-CHANNEL-3-GENERAL_ERROR: [chars]
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
PORT-CHANNEL-3-MSG_SEND_FAILURE: failed to send [chars] to sap [dec]:
Recommended Action
2-347
Chapter 2
Error Message Explanation PORT-CHANNEL-3-PORT_CHANNEL_NOT_FOUND: [chars] is not found
Cannot find port-channel in its database, which indicates an inconsistency with an external component No action is required.
Recommended Action
Error Message PORT-CHANNEL-3-TIMEOUT: timed out after [dec] seconds [type [chars], state [chars]] Explanation
Some operation timed out Run show port-channel consistency to check all module connectivity and
Recommended Action
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 individual
PORT-CHANNEL-4-PORT_INDIVIDUAL: port [chars] is operationally
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
Recommended Action
PORT-CHANNEL-4-RACE_WARN: [chars]
Warning of possible race condition No action is required.
Recommended Action
2-348
OL-24654-01
Chapter 2
Error Message [chars] Explanation PORT-CHANNEL-4-UNEXPECTED_RESPONSE: unexpected response [chars] from
Received an unexpected response and discarded No action is required.
Recommended Action
PORT-CHANNEL-5
Error Message Explanation PORT-CHANNEL-5-AUTO_CREATE_FAILURE: [chars] [chars]
Auto create process on the port failed No action is required.
Recommended Action
PORT-CHANNEL-5-CREATED: [chars] created
A port-channel is created No action is required.
Recommended Action
PORT-CHANNEL-5-DELETED: [chars] deleted
A port-channel is deleted No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 Delete the set of port channel interface <port-channel interface
Recommended Action
PORT-CHANNEL-5-PORT_ADDED: [chars] added to [chars]
Ports are added to a port-channel No action is required.
Recommended Action
2-349
Chapter 2
Error Message Explanation PORT-CHANNEL-5-PORT_DOWN: [chars]: [chars] is down
Port goes down in a port-channel No action is required.
Recommended Action
PORT-CHANNEL-5-PORT_REMOVED: [chars] removed from [chars]
Ports are removed from a port-channel No action is required.
Recommended Action
PORT-CHANNEL-5-PORT_UP: [chars]: [chars] is up
Port comes up in a port-channel No action is required.
Recommended Action
PORT-CHANNEL-6
Error Message Explanation PORT-CHANNEL-6-RESYNC: resyncing [chars] with all modules
Resync modules with sup after an error or switchover No action is required.
Recommended Action
PORT-CHANNEL-7
Error Message Explanation PORT-CHANNEL-7-GSYNC_DONE: global synchronization is done
Port-channel manager finished global synchronization No action is required.
Recommended Action
PORT-CHANNEL-7-GSYNC_REQ: requesting global synchronization
Port-channel manager requested a global synchronization from active sup No action is required.
Recommended Action
PORT-CHANNEL-7-START_ACTIVE: started in active mode
Port-channel manager started in active mode No action is required.
Recommended Action
2-350
OL-24654-01
Chapter 2
Error Message Explanation PORT-CHANNEL-7-START_DEFAULT: started with default configuration
Port-channel manager started with default configuration No action is required.
Recommended Action
PORT-CHANNEL-7-START_STANDBY: started in standby mode
Port-channel manager started in standby mode No action is required.
Recommended Action
PORT-CHANNEL-7-START_STATEFUL: started statefully
Port-channel manager started with running configuration No action is required.
Recommended Action
PORT-CHANNEL-7-START_STATELESS: started statelessly
Port-channel manager started with startup configuration No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 memory-type:[dec] of Size:[dec] No action is required.
Recommended Action
2-351
Chapter 2
Error Message Explanation PORT-PROFILE-3-ASSERTION_FAILED: Failed in File:[chars] Line:[dec]
PPM Process assertion failed in File:[chars], at line:[dec] No action is required.
Recommended Action
Error Message PORT-PROFILE-3-CREATE_IF_FAILED: Running-config collection Failed for intf range [chars] Explanation
Running-config collection failed for :[chars] No action is required.
Recommended Action
PORT-PROFILE-3-IF_APPLY_FAILED: Config Apply Failed
Config Apply Failed No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message PORT-PROFILE-3-PROFILE_CREATE_FAILED: Port-profile [chars] creattion failed with error "[chars]" Explanation
Port-profile:[chars] creation failed with [:chars] No action is required.
Recommended Action
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] No action is required.
Recommended Action
2-352
OL-24654-01
Chapter 2
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] No action is required.
Recommended Action
Error Message PORT-PROFILE-3-PROFILE_DISABLE_FAILED: Port-profile [chars] disable failed with error "[chars]" Explanation
Port-profile:[chars] disable failed with [:chars] No action is required.
Recommended Action
Error Message PORT-PROFILE-3-PROFILE_ENABLE_FAILED: Port-profile [chars] enable failed with error "[chars]" Explanation
Port-profile:[chars] enable failed with [:chars] No action is required.
Recommended Action
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] No action is required.
Recommended Action
PORT-PROFILE-6
Error Message PORT-PROFILE-6-PROFILE_CREATED: Port-profile [chars] is created successfully Explanation
Port-profile:[chars] is created No action is required.
Recommended Action
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] No action is required.
Recommended Action
2-353
Chapter 2
Error Message PORT-PROFILE-6-PROFILE_DELETED: Port-profile [chars] is deleted successfully Explanation
Port-profile:[chars] is deleted No action is required.
Recommended Action
Error Message PORT-PROFILE-6-PROFILE_DISABLED: Port-profile [chars] is disabled successfully Explanation
Port-profile:[chars] is disabled No action is required.
Recommended Action
Error Message PORT-PROFILE-6-PROFILE_ENABLED: Port-profile [chars] is enabled successfully Explanation
Port-profile:[chars] is enabled No action is required.
Recommended Action
Error Message PORT-PROFILE-6-PROFILE_INHERITED: Port-profile [chars] is inherited successfully on [chars] Explanation
Port-profile:[chars] is inherited on [:chars] No action is required.
Recommended Action
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] Explanation
Recommended Action
2-354
OL-24654-01
Chapter 2
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 Install a valid port activation license file
Recommended Action
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]
PORT-SECURITY-2-FEATURE_DISABLED: Feature [chars] disabled due to
Feature [chars] is unavailable and will be disabled now Please install the correct license and reenable
Recommended Action
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-355
Chapter 2
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 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.
PORT-SECURITY-3-DB_ERR: [chars]
An error occurred during an PSM database operation. [chars] indicates the reason for
the error
PORT-SECURITY-3-EFMD_FC2_OPER_FAILED: [chars]
EFMD fc2 operation failed
PORT-SECURITY-3-EFMD_INIT_FAILED: [chars]
EFMD init failed
PORT-SECURITY-3-EFMD_MERGE_UNKNOWN_FORMAT: [chars]
Received a corrupted EFMD Request Packet
2-356
OL-24654-01
Chapter 2
Error Message Explanation PORT-SECURITY-3-INIT_FAIL: [chars]
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.
PORT-SECURITY-3-MTS_ERR: [chars]
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 that caused the error 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.
Error Message PORT-SECURITY-3-PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec] Explanation
PORT-SECURITY-4
Error Message Explanation PORT-SECURITY-4-ACTIVATION_FAIL: [chars]
Activation of bindings failed due to [chars] Correct the error and reactivate it again
Recommended Action
2-357
Chapter 2
PORT-SECURITY-6
Error Message PORT-SECURITY-6-INFO: [chars] Explanation
An event happend that affects PSM. [chars] indicates the event No action is required.
Recommended Action
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]
Recommended Action Collect more information about failed interface using command showportinternalallinterface[char]'.Inmostcases,youcanrecoverusingfollowingcommands'configter minal','interface[char]','shutdown','noshutdown'ontheinterfaceorremovingandre-insertingthefibreop ticcable'
Error Message failure) Explanation
PORT-2-IF_DOWN_LINK_FAILURE_CRIT: Interface [chars] is down (Link
The physical link has gone down Ensure that the cable is connected and the remote end is not shut down
Recommended Action
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 description is configured, the interface description is displayed] Recommended Action
Please do show interface transceiver details to obtain more information
2-358
OL-24654-01
Chapter 2
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 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 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 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 do show interface transceiver details to obtain more information
2-359
Chapter 2
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 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 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 configured, the interface description is displayed] 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 port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] Recommended Action
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 port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] Recommended Action
Try to change the configuration on the interface with the current available
hardware capability
2-360
OL-24654-01
Chapter 2
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 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
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-361
Chapter 2
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 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
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 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 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 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
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] Recommended Action
2-362
OL-24654-01
Chapter 2
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 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
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 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
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 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
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 port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] Recommended Action
2-363
Chapter 2
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 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
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 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
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 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
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 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
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 Configure the attached switchport correctly and try again
Recommended Action
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 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
2-364
OL-24654-01
Chapter 2
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 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
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 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
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 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
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 displayed and if interface description is configured, the interface description is displayed] 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 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
2-365
Chapter 2
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 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
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 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
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 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 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 number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] 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 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 output of showportinternalevent-history'todeterminetheESCprotocolexchangestodeterminehowitfailed'
2-366
OL-24654-01
Chapter 2
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 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 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 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 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 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 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 port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] Recommended Action
Insert an FCOT
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 port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] Recommended Action
Insert an FCOT
2-367
Chapter 2
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, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] Please contact customer support for a list of authorized transceiver vendors
Recommended Action
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 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 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 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 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 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 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 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 This is an intermediary state, whereby the port VSAN of the port is being enabled to be a FICON VSAN.
2-368
OL-24654-01
Chapter 2
Error Message PORT-5-IF_DOWN_HW_FAILURE: Interface [chars] is down (Hardware Failure) [chars] [chars] Explanation The moduleshardwarehasfailed.[optionallyiftheportbelongstoport-channel,theport-channelnumbertowhi chtheportbelongswillbedisplayedandifinterfacedescriptionisconfigured,theinterfacedescriptionisdis played]' 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 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
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 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 a 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 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
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 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
Get the allowed receive buffer size from showportinternalinfo''
2-369
Chapter 2
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 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 a 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 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 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 number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] Recommended Action
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 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 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 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 both the local and peer ports are either both members of the same PortChannel or are not both part of PortChannel
2-370
OL-24654-01
Chapter 2
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 number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] 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 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 cable is connected and the remote end is not shut down
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. [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
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 port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] Recommended Action Collect more information about failed interface using command 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 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 connectivity of this interface and ensure that it is connected to
another switch
2-371
Chapter 2
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 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
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 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 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 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
Error Message PORT-5-IF_DOWN_NOS_RCVD: Interface [chars] is down (NOS received) [chars] [chars] Explanation The physical link has gone 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
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.
2-372
OL-24654-01
Chapter 2
Error Message [chars] PORT-5-IF_DOWN_OFFLINE: Interface [chars] is down (Offline) [chars]
Explanation The interface has been placed into the offline state. [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
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 number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] 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] Explanation The physical link has gone 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
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 port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] Recommended Action
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 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
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-373
Chapter 2
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 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 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] Recommended Action
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 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 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 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 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 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
Enable at least one of the PortChannelsmembers'
2-374
OL-24654-01
Chapter 2
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. [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 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 port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] Recommended Action
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 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
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. [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 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, 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
2-375
Chapter 2
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 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 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 port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] Recommended Action Change the mode and the trunking mode of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'
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 different from that of the PortChannel. [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
Change the speed of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'
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 different from that of the PortChannel. [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 this interface is connected to the same remote switch as all the other interfaces in the PortChannel
2-376
OL-24654-01
Chapter 2
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 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 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 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 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 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 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
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]
2-377
Chapter 2
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 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_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 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
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 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
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 number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed] Recommended Action
Check the VSANs configured on the local end with the remote end
2-378
OL-24654-01
Chapter 2
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 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
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 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
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 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 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 No action is required.
Recommended Action
PORT-5-IF_PSS_DUPLICATE_KEY: Duplicate key found for Interface
Duplicate pss key detected No action is required.
Recommended Action
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 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 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-379
Chapter 2
Error Message [chars] Explanation PORT-5-IF_TRUNK_UP: Interface [chars], vsan [chars] is up [chars]
Interface [chars] is trunking, VSAN [chars] is 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] No action is required.
Recommended Action
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 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
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 Use command "show module <x
Recommended Action
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 No action is required.
Recommended Action
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 Reload the module
Recommended Action
PRIVATE_VLAN Messages
This section contains the PRIVATE_VLAN messages.
2-380
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
Error Message PRIVATE_VLAN-2-PVLAN_ASSOC_UP_FAILED: Failed to bring up the association between [dec] & [dec] Explanation
Association bringup failed No action is required.
Recommended Action
Error Message PRIVATE_VLAN-2-PVLAN_ELTM_MTS_SEND_FAILED: MTS send failed while communicating with ELTM. Explanation
ELTM MTS send failed No action is required.
Recommended Action
Error Message PRIVATE_VLAN-2-PVLAN_ELTM_TIMED_OUT: ELTM timed out while configuring hardware. Explanation
ELTM timed out No action is required.
Recommended Action
Error Message PRIVATE_VLAN-2-PVLAN_ETHPM_TIMED_OUT: ETHPM timed out while configuring/unconfiguring hardware Explanation
ETHPM timed out No action is required.
Recommended Action
Error Message PRIVATE_VLAN-2-PVLAN_HW_ERROR: Error [hex] occurred for ifindex [hex] while programming hardware: [chars] Explanation
Hardware Configuration Error No action is required.
Recommended Action
2-381
Chapter 2
Error Message PRIVATE_VLAN-2-PVLAN_PIXM_MTS_SEND_FAILED: MTS send failed while communicating with PIXM Explanation
PIXM MTS send failed No action is required.
Recommended Action
Error Message PRIVATE_VLAN-2-PVLAN_PIXM_TIMED_OUT: PIXM timed out while configuring hardware. Explanation
PIXM timed out No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
PRIVATE_VLAN-5
Error Message Explanation PRIVATE_VLAN-5-PVLAN_DISABLED: PVLAN Disabled
PVLAN Service Disabled No action is required.
Recommended Action
2-382
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
PRIVATE_VLAN-5-PVLAN_ENABLED: PVLAN Enabled
PVLAN Service Enabled No action is required.
Recommended Action
PROC_MGR Messages
PROC_MGR-SLOT#-2
Error Message Explanation PROC_MGR-SLOT#-2-ERR_MSG: [chars]
Process manager error. No action is required.
Recommended Action
PROC_MGR-SLOT#-2-MESG: [chars]
Process manager information. Process manager information.
Recommended Action
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. Restart the linecard.
Recommended Action
Error Message PROC_MGR-SLOT#-2-PROC_MGR_APP_EXITED: ERROR: Application ([chars]) exited with status=[dec] signal=[dec] Explanation
Application exited. Check the application.
Recommended Action
2-383
Chapter 2
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. Restart the linecard.
Recommended Action
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. Restart the linecard.
Recommended Action
Error Message PROC_MGR-SLOT#-2-PROC_MGR_COMP_DEP_FAIL: ERROR: Dependency failure - Component ([chars]) depends on ([chars]) Explanation
Component dependency failure. Check whether the component exists.
Recommended Action
Error Message PROC_MGR-SLOT#-2-PROC_MGR_COMP_NOT_INSTALLED: ERROR: Component ([chars]) could not be installed errno=[dec] Explanation
Component not installed. Check whether the component exists.
Recommended Action
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. Check the component.
Recommended Action
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. Restart the linecard.
Recommended Action
PROC_MGR-SLOT#-2-PROC_MGR_QUIT: Process manager quitting because:
Process manager quitting. No action is required.
Recommended Action
2-384
OL-24654-01
Chapter 2
Error Message PROC_MGR-SLOT#-2-PROC_MGR_RM_KLM_SCRIPT: Removed: KLM/Script [[chars]] in [dec] sec [dec] usec ... Explanation
Removed KLM/Script. No action is required.
Recommended Action
Error Message PROC_MGR-SLOT#-2-PROC_MGR_STOP_PROC: Process [[chars]] exited in [dec] sec [dec] usec ... Explanation
Process stopped. No action is required.
Recommended Action
Error Message PROC_MGR-SLOT#-2-PROC_MGR_TERM_TIME: * Termination took [dec] sec [dec] usec * Explanation
Process manager termination time. No action is required.
Recommended Action
Error Message PROC_MGR-SLOT#-2-PROC_MGR_UT_PEEK_FAIL: ERROR: Unable to peek on utaker queue Explanation
Peek at utaker queue failed. Restart the linecard.
Recommended Action
Error Message PROC_MGR-SLOT#-2-PROC_MGR_UT_SEM_ALLOC_FAIL: ERROR:Failed to allocate utaker semaphore: [dec] Explanation
Utaker semaphore allocation failed. Restart the linecard.
Recommended Action
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. Restart the linecard.
Recommended Action
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. Restart the linecard.
Recommended Action
2-385
Chapter 2
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. Restart the linecard.
Recommended Action
PROC_MGR-SLOT#-3
Error Message Explanation PROC_MGR-SLOT#-3-PROC_MGR_ERROR_MSG: [chars]
Process manager error message No action is required.
Recommended Action
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. Check the application.
Recommended Action
PROC_MGR-SLOT#-6
Error Message Explanation PROC_MGR-SLOT#-6-PROC_MGR_INFO_MSG: [chars]
Process manager info message No action is required.
Recommended Action
PSS Messages
This section contains the PSS messages.
PSS-0
Error Message Explanation PSS-0-PSS_NO_MORE_PAGES: [chars]: needs more working pages
Service needs more working page buffers
2-386
OL-24654-01
Chapter 2
Error Message PSS-0-PSS_READ_DATA_FAILURE: [chars]: failed to read data to [chars] block [dec]: [chars] Explanation
PSS cannot read data No action is required.
Recommended Action
PSS-0-PSS_SYNC_DATA_FAILURE: [chars]: failed to sync data to [chars]:
PSS cannot sync data due to filesystem or disk error No action is required.
Recommended Action
PSS-0-PSS_SYNC_LOG_FAILURE: [chars]: failed to sync log: [chars]
PSS cannot sync log due to filesystem or disk error No action is required.
Recommended Action
PSS-0-PSS_UNKNOWN_LOG: [chars]: unknown log type [hex] at offset
Unknown logging entry found No action is required.
Recommended Action
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 No action is required.
Recommended Action
PSS-0-PSS_WRITE_FAILURE: [chars]: failed to write data: [chars]
PSS cannot write data due to filesystem or disk error No action is required.
Recommended Action
PSS-0-PSS_WRITE_LOG_FAILURE: [chars]: failed to write log: [chars]
PSS cannot write log due to filesystem or disk error No action is required.
Recommended Action
2-387
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
PSS-1-PSS_STAT_ERROR: [chars]: cannot stat [chars]: [chars]
PSS cannot do fstat on a database No action is required.
Recommended Action
PSS-1-PSS_VERSION_MISMATCH: [chars]: found version mismatch in
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 Explanation PSS-2-PSS_INFRACONVERT: [chars]
Error in libinfraconvert during pss conversion No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-388
OL-24654-01
Chapter 2
Error Message file Explanation PSS-2-PSS_MISSING_FILE: [chars]: database [chars] missing [chars]
PSS database is incomplete; probably due to a crash No action is required.
Recommended Action
PSS-2-PSS_RECOVERY_FAILED: [chars]: failed to recover [chars]
PSS recovery failed No action is required.
Recommended Action
PSS-4
Error Message Explanation PSS-4-PSS_CLEANUP: [chars]: cleaning up [chars]
PSS removed a leftover or corrupted file No action is required.
Recommended Action
PSS-4-PSS_RECOVERY_ENDED: [chars]: recovered [chars] successfully
PSS recovery finished No action is required.
Recommended Action
Error Message PSS-4-PSS_RECOVERY_STARTED: [chars]: recovering [chars]: [dec] valid transactional records Explanation
PSS started recovery of previous aborted transaction No action is required.
Recommended Action
PSS-5
Error Message Explanation PSS-5-PSS_CONVERT_FORMAT: [chars]: converting pss format: [chars]
PSS format is being converted No action is required.
Recommended Action
Error Message PSS-5-PSS_CONVERT_LAYOUT: [chars]: converting pss layout: [chars] (params [dec]/[dec]/[dec] Explanation
PSS layout is being converted No action is required.
Recommended Action
2-389
Chapter 2
Error Message Explanation PSS-5-PSS_SHRINK: [chars]: shrinking pss: [chars]
PSS is being shrunk to remove free space No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message PTPLC-3-PTPLC_PTP_INTF_CONFIG_ERROR: Failed to configure PTP/PONG on port [dec]: [hex], [chars] Explanation
PTP interface configuration error No action is required.
Recommended Action
PTP Messages
This section contains the PTP messages.
PTP-5
Error Message Explanation PTP-5-PTP_DISABLED: PTP disabled
PTP Service Enabled No action is required.
Recommended Action
2-390
OL-24654-01
Chapter 2
Error Message Explanation PTP-5-PTP_DOMAIN_CHANGE: PTP domain changed to [dec]
PTP domain changed No action is required.
Recommended Action
PTP-5-PTP_ENABLED: PTP enabled
PTP Service Enabled No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
PTP-6-PTP_PRIORITY1_CHANGE: PTP priority1 changed to [dec]
PTP priority1 changed No action is required.
Recommended Action
PTP-6-PTP_PRIORITY2_CHANGE: PTP priority2 changed to [dec]
PTP priority2 changed No action is required.
Recommended Action
2-391
Chapter 2
Error Message to [dec] Explanation PTP-6-PTP_SYNC_INTERVAL_CHANGE: PTP sync interval for [hex] changed
PTP sync interval for [chars] changed No action is required.
Recommended Action
PTP-6-PTP_VLAN_CHANGE: PTP vlan for [hex] changed to [dec]
PTP vlan for [chars] changed No action is required.
Recommended Action
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 restarted automatically. Recommended Action
QOS-2-GENERAL_ERROR: [chars]
The QOS Manager has encountered an critical error. The description of error is [str.]. No action is required.
Recommended Action
QOS-2-INITFAIL: QoS Manager Initialization failed: [chars]
QoS Manager initialization failed. [chars] explains the reason for the failure. No action is required.
Recommended Action
QOS-2-MALLOC_ERROR: Size [dec] bytes
The QOS Manager could not allocate memory.
2-392
OL-24654-01
Chapter 2
Error Message QOS-2-PSS_ERROR: [chars]: PSS returned value=[dec]
Explanation The QOS Manager encountered error while operating on a persistent storage database. Recommended Action
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. Recommended Action
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.
Recommended Action
QOS-3-DBERROR: [chars]
QoS Manager encountered a database error. [chars] specifies the context where the failure occurred. No action is required.
Recommended Action
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.]. Recommended Action
Error Message
QOS-3-FAILURE_RESPONSE: [chars] [hex]
Explanation QoS Manager failed to get response [chars][hex] specify the context where the failure
occurred.
Recommended Action
2-393
Chapter 2
Error Message QOS-3-GENERROR: [chars]
Explanation QoS Manager encountered a general error, one that does not fall in any of the above categories. [chars] describes the error and its context. Recommended Action
QOS-3-LICERR: [chars]
QoS Manager failed to get license. No action is required.
Recommended Action
Error Message
QOS-3-MTSERROR: [chars]
Explanation QoS Manager encountered an MTS error. [chars] specifies the context where the error
occurred.
Recommended Action
QOS-3-PSSERROR: [chars]
QoS Manager encountered a PSS error. [chars] specifies the context where the failure No action is required.
occurred.
Recommended Action
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. The database would be recreated. Recommended Action
Error Message
QOS-3-TIMEOUT_ERROR: [chars] [hex]
Explanation QoS Manager encountered a timeout [chars][hex] specify the context where the failure
occurred.
Recommended Action
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. Recommended Action
2-394
OL-24654-01
Chapter 2
QOS-4
Error Message Explanation QOS-4-LICEXP: [chars]
QoS Manager license is going to expire. [chars] gives the expected time of expiry. No action is required.
Recommended Action
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 storage databases. The persistent information has been translated to the new format. Recommended Action
QOS-6
Error Message Explanation QOS-6-BECAME_ACTIVE: Became ACTIVE from standby mode.
The QOS Manager on the standby supervisor became active and it is ready to serve client requests. No action is required.
Recommended Action
QOS-6-BECAME_STDBY: Became STANDBY from active mode.
The QOS Manager became standby from active mode. No action is required.
Recommended Action
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. Recommended Action
Error Message
QOS-6-ENABLED_UP_MARKING: [chars]
Explanation The QoS Manager has enabled marking of time-critical control traffic as high-priority
traffic.
Recommended Action
2-395
Chapter 2
Error Message Explanation QOS-6-EXCESSIVE_DELAY: [chars]
Excessive time taken for a processing event. The description of the event is [str.]. No action is required.
Recommended Action
QOS-6-E_PORT_ACL_SUCCESS: Successfully [chars] QOS ACL for interface
Explanation The QOS Manager has successfully programmed or erased QoS related ACL when an
E-Port came up or went down for interface [str.].

Recommended Action
Error Message QOS-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars] Explanation
The QOS Manager was unable to send heartbeat to the system manager. No action is required.
Recommended Action
QOS-6-GENERAL_EVENT: [chars]
The QOS Manager has generated an important event. The description of the event is No action is required.
[str.].
Recommended Action
Error Message
QOS-6-MGRCREATED: QoS Manager created
Explanation QoS Manager was created successfully and is up and running. This is an informational
message.
Recommended Action
QOS-6-MGREXIT: QoS Manager shutting down gracefully
QoS Manager is shutting down gracefully. This is an informational message. No action is required.
Recommended Action
QOS-6-PSS_CREATED: [chars] PSS Created
One of the persistent information database of QOS Manager has been recreated. No action is required.
Recommended Action
2-396
OL-24654-01
Chapter 2
Error Message Explanation QOS-6-PSS_DESTROYED: [chars] PSS Destroyed
One of the persistent information databases of QoS Manager has been intentionally destroyed and would be recreated. No action is required.
Recommended Action
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. Recommended Action
QOS-6-SWITCHOVER: Switching Over to other Supervisor.
The QOS Manager has successfully switched over to the standby supervisor card. No action is required.
Recommended Action
QOS-6-UNKNOWNMTS: QoS Manager received an unexpected message
QoS Manager received an unexpected message. No action is required.
Recommended Action
RADIUS Messages
This section contains the RADIUS messages.
RADIUS-2
Error Message Explanation RADIUS-2-RADIUS_NO_AUTHEN_INFO: ASCII authentication not supported
ASCII authentication not supported.
RADIUS-2-RADIUS_PROGRAM_EXIT: RADIUS daemon exiting: [chars]
RADIUS daemon is exiting.
2-397
Chapter 2
RADIUS-3
Error Message Explanation RADIUS-3-RADIUS_ERROR_MESSAGE: [chars]
RADIUS Error Message No action is required.
Recommended Action
RADIUS-4
Error Message Explanation RADIUS-4-RADIUS_WARNING: [chars]
RADIUS Warning No action is required.
Recommended Action
RADIUS-5
Error Message Explanation RADIUS-5-RADIUS_MONITOR_STATUS: [chars] [chars]
Notifying Radius server monitor status change No action is required.
Recommended Action
RADIUS-5-RADIUS_NOTIFICATION: [chars]
RADIUS Notification No action is required.
Recommended Action
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 No action is required.
Recommended Action
RADIUS-6
Error Message Explanation RADIUS-6-RADIUS_ACCOUNTING_MESSAGE: [chars]
Recommended Action
2-398
OL-24654-01
Chapter 2
Error Message Explanation RADIUS-6-RADIUS_MESSAGE: [chars]
RADIUS Message No action is required.
Recommended Action
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] Explanation
RDL-3
Error Message Explanation RDL-3-SYSLOG_ALLOC_FAIL: : [chars]
RDL memory allocation failed : [chars]. No action is required.
Recommended Action
RDL-3-SYSLOG_CONTEXT_ERR: : [chars] [dec]
RDL context error: [chars] [dec]. No action is required.
Recommended Action
RDL-3-SYSLOG_ERR: : [chars]
RDL syslog errors : [chars]. No action is required.
Recommended Action
RDL-3-SYSLOG_EXIT: : [chars]
RDL exiting on errors : [chars]. No action is required.
Recommended Action
2-399
Chapter 2
Error Message Explanation RDL-3-SYSLOG_INIT_FAIL: : [chars] [chars]
RDL Initialization Failed: [chars] [chars]. No action is required.
Recommended Action
RDL-3-SYSLOG_MTS_ERR: : [chars]
RDL MTS errors : [chars]. No action is required.
Recommended Action
RDL-6
Error Message Explanation RDL-6-INFORMATION: [chars]
An event happend that affects RDL. [chars] indicates the event No action is required.
Recommended Action
RDL-6-PSS_ERR: [chars]
An error occurred during an RDL PSS operation. [chars] indicates the PSS operation that caused the error
RDL-6-SYSLOG_DEBUG_1: : [chars] [hex]
RDL Debug logs: [chars] [dec]. No action is required.
Recommended Action
RDL-6-SYSLOG_DEBUG_2: : [chars] [hex]
RDL Debug logs: [chars] [dec]. No action is required.
Recommended Action
RDL-6-SYSLOG_INFO: : [chars]
RDL Debug logs: [chars]. No action is required.
Recommended Action
2-400
OL-24654-01
Chapter 2
Error Message Explanation RDL-6-SYSLOG_RESP_RCVD: : [chars] [dec]
RDL context error: [chars] [dec]. No action is required.
Recommended Action
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 Recommended Action
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. No action is required.
Recommended Action
RES_MGR-2-RES_MGR_CRIT: RES_MGR Critical: [chars]
RES_MGR generic critical condition No action is required.
Recommended Action
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 Recommended Action
2-401
Chapter 2
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 Recommended Action
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 Recommended Action
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' Recommended Action
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' Recommended Action
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. No action is required.
Recommended Action
2-402
OL-24654-01
Chapter 2
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 Recommended Action
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 Recommended Action
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 Recommended Action
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. No action is required.
Recommended Action
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 Recommended Action
2-403
Chapter 2
RES_MGR-5
Error Message Explanation RES_MGR-5-RES_MGR_DISABLED: RES_MGR Disabled
RES_MGR Service Disabled No action is required.
Recommended Action
RES_MGR-5-RES_MGR_ENABLED: RES_MGR Enabled
RES_MGR Service Enabled No action is required.
Recommended Action
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 No action is required.
Recommended Action
RIB Messages
This section contains the RIB messages.
RIB-0
Error Message Explanation RIB-0-EMERG: [chars]
Rib caused a system failure
RIB-1
Error Message Explanation RIB-1-ALERT: [chars]
Rib caused failures in other services
2-404
OL-24654-01
Chapter 2
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 Explanation RIB-2-CRIT: [chars]
Rib encountered a catastrophic error
RIB-3
Error Message Explanation RIB-3-ERR: [chars]
Rib encountered an error
RIB-3-FIB_EXIT: fib exited
Fib had exited and may not continue operation
RIB-3-MISS_APPS: Missing response from service
Service not responding to rib
Recommended Action Please perform debugriberror',thenrecreatetheoperationscenario,tofindoutmoredetails.'
RIB-3-NO_MEM: Out of memory
Rib does not have enough memory to continue proper operation.
2-405
Chapter 2
Error Message Explanation RIB-3-SEND_FIB: Cannot talk to fib
Rib to fib IPC failure
RIB-3-SEND_SNMP: Cannot respond to snmp
Rib to snmp IPC failure
RIB-3-SEND_STANDBY: Cannot talk to standby rib
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. Recommended Action Please perform debugriberror',thenrecreatetheoperationscenario,tofindoutmoredetails.'
RIB-4-DUP_FIB: Duplicate response from fib
Rib ignored duplicate response from fib
RIB-4-LATE_FIB: Late response from fib
Rib ignored late response from fib
2-406
OL-24654-01
Chapter 2
Error Message Explanation RIB-4-PC_LIMIT: PC number greater than 128 (ignored by RIB)
Rib ignored pc Please use PC number < 128
Recommended Action
RIB-4-WARN: [chars]
Rib ignored the unexpected condition
Recommended Action Please perform debugriball',thenrecreatetheoperationscenario,tofindoutmoredetails.'
RIB-5
Error Message Explanation RIB-5-NOTE: [chars]
Rib does not support this operation
Recommended Action Please perform debugriball',thenrecreatetheoperationscenario,tofindoutmoredetails.'
RIB-6
Error Message Explanation RIB-6-INFO: [chars]
Rib event occurred No action is required.
Recommended Action
RLIR Messages
This section contains the RLIR messages.
RLIR-2
Error Message code [dec] Explanation RLIR-2-DRLIR_REJECT: DRLIR rejected: [chars]: fcid [chars], reason
DRLIR rejected: [chars] fcid [chars] reason code [dec] No action is required.
Recommended Action
2-407
Chapter 2
Error Message Explanation RLIR-2-FC2_FAILED: RLIR FC2 operation failed: [chars]: [chars]
RLIR FC2 operation failed: [chars] [chars] No action is required.
Recommended Action
RLIR-2-INIT_FAILED: RLIR Init failed: [chars]
RLIR Init failed: [chars] No action is required.
Recommended Action
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 No action is required.
Recommended Action
RLIR-2-MALLOC_FAILED: RLIR Malloc failed: [chars]
RLIR Malloc failed: [chars] No action is required.
Recommended Action
RLIR-2-MTS_FAILED: RLIR MTS operation failed: [chars]: [chars]
RLIR MTS operation failed: [chars] [chars] No action is required.
Recommended Action
RLIR-2-PSS_FAILED: RLIR PSS operation failed: [chars]: [chars]
RLIR PSS operation failed: [chars] [chars] No action is required.
Recommended Action
RLIR-6
Error Message Explanation RLIR-6-SYSLOG_INFO: RLIR Syslog info: [chars]
RLIR Syslog info: [chars] No action is required.
Recommended Action
2-408
OL-24654-01
Chapter 2
Error Message Explanation RLIR-6-SYSLOG_STATUS: RLIR Syslog status: [chars]: [chars]
RLIR Syslog status: [chars] [chars] No action is required.
Recommended Action
RM Messages
This section contains the RM messages.
RM-6
Error Message Explanation RM-6-RMGR_INFO: [chars]
RMGR daemon informational message No action is required.
Recommended Action
RM-6-STARTING: deamon started
The RMGR daemon successfully started No action is required.
Recommended Action
RM-SLOT#-2
Error Message RM-SLOT#-2-CPP_CATASTROPHIC_ERROR: ERROR: Component ([chars]) caused critical error. Service Module will be reloaded Explanation
Recommended Action
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 No action is required.
Recommended Action
RM-SLOT#-2-RM_CRITICAL_ALERT: [chars]
Critical Alert Restart the linecard
Recommended Action
2-409
Chapter 2
Error Message Explanation RM-SLOT#-2-RM_PROCESS_FAILED: ERROR: [chars] failed
Process failed No action is required.
Recommended Action
Error Message RM-SLOT#-2-RM_PROCESS_TMOUT: ERROR: [chars] did not complete. Reloading Service Module Explanation
Component critical error timeout No action is required.
Recommended Action
Error Message RM-SLOT#-2-RM_VICPP_RECREATE_ERROR: All the fast path resources are down VICPP connectivity lost Explanation
Recommended Action
RM-SLOT#-4
Error Message Explanation RM-SLOT#-4-RM_WARNING: [chars]
Warning No action is required.
Recommended Action
RSCN Messages
This section contains the RSCN messages.
RSCN-2
Error Message Explanation RSCN-2-FC2_FAILED: RSCN FC2 operation failed: [chars]: [chars]
RSCN FC2 operation failed: [chars] [chars] No action is required.
Recommended Action
RSCN-2-INIT_FAILED: RSCN Init failed: [chars]
RSCN Init failed: [chars] No action is required.
Recommended Action
2-410
OL-24654-01
Chapter 2
Error Message Explanation RSCN-2-MALLOC_FAILED: RSCN Malloc failed: [chars]
RSCN Malloc failed: [chars] No action is required.
Recommended Action
RSCN-2-MTS_FAILED: RSCN MTS operation failed: [chars]: [chars]
RSCN MTS operation failed: [chars] [chars] No action is required.
Recommended Action
RSCN-2-PSS_FAILED: RSCN PSS operation failed: [chars]: [chars]
RSCN PSS operation failed: [chars] [chars] No action is required.
Recommended Action
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] No action is required.
Recommended Action
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] No action is required.
Recommended Action
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] Recommended Action
RSCN-6
Error Message Explanation RSCN-6-SYSLOG_INFO: RSCN Syslog info: [chars]
RSCN Syslog info: [chars] No action is required.
Recommended Action
2-411
Chapter 2
Error Message Explanation RSCN-6-SYSLOG_STATUS: RSCN Syslog status: [chars]: [chars]
RSCN Syslog status: [chars] [chars] No action is required.
Recommended Action Recommended Action
SAL Messages
This section contains the SAL messages.
SAL-5
Error Message Explanation SAL-5-SAL_DISABLED: SAL Disabled
SAL Service Disabled No action is required.
Recommended Action
Error Message
SAL-5-SAL_ENABLED: SAL Enabled
Explanation SAL Service nabled Recommended Action
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 No action is required.
Recommended Action
SCHEDULER Messages
This section contains the SCHEDULER messages.
2-412
OL-24654-01
Chapter 2
SCHEDULER-2
Error Message Explanation SCHEDULER-2-SCH_SYSLOG_MALLOC_ERR: Out of memory: [chars]
Process memory exhausted. Possible memory leak. Contact TAC
Recommended Action
SCHEDULER-2-SCH_SYSLOG_MTS_ERR: MTS error: [chars]
MTS operation failure Contact TAC
Recommended Action
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 Contact TAC
Recommended Action
Error Message SCHEDULER-2-SCH_SYSLOG_SDWRAP_ERR: Debug infrastructure initialization failed: [chars] Explanation
Debug infrastructure failed to initialize Contact TAC
Recommended Action
SCHEDULER-3
Error Message Explanation SCHEDULER-3-SCH_ERR: [chars]
Scheduler error No action is required.
Recommended Action
SCHEDULER-3-SCH_SYSLOG_FILE_ERR: [chars] Error:[chars]
Recommended Action
2-413
Chapter 2
Error Message Error:[dec] Explanation SCHEDULER-3-SCH_SYSLOG_PSS_ERR: Purpose:[chars] URI:[chars]
Error while performing I/O to PSS Contact TAC
Recommended Action
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 Ensure the user exists. Make sure he is not a remotely authenticated user.
system.
Recommended Action
SCHEDULER-4
Error Message Explanation SCHEDULER-4-SCH_WARN: [chars]
Scheduler warning No action is required.
Recommended Action
SCHEDULER-6
Error Message Explanation SCHEDULER-6-SCH_MSG: [chars]
Scheduler Message No action is required.
Recommended Action
SCM Messages
SCM-2
Error Message Explanation SCM-2-SCMLCINSERTFAIL: [chars]
SCSI-TARGET NONE
Recommended Action
SCSI-TARGET Messages
This section contains the SCSI-TARGET messages.
2-414
OL-24654-01
Chapter 2
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 [hex]
SCSI-TARGET-2-PSS_INIT_FAIL: pss initialization failed due to error:
Explanation SCSI-target process pss initialization failure due to error [hex]. No SCSI discovery can be performed. Recommended Action Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'
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-415
Chapter 2
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. Recommended Action Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'
Error Message SCSI-TARGET-3-PSS_DELETE_FAIL: pss delete runtime entry key:[hex] failed due to error: [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 discovery can be performed. Recommended Action Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'
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 discovery can be performed. Recommended Action Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'
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 discovery can be performed.
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].
2-416
OL-24654-01
Chapter 2
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] failed due to error: [hex] 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]. None
Recommended Action
SDV Messages
This section contains the SDV messages.
SDV-2
Error Message Explanation SDV-2-RANDNUM_FAIL: Random number generation failed
Random number generation failed. Process has to exit due to FIPS compliance No action is required.
Recommended Action
2-417
Chapter 2
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 No action is required.
Recommended Action
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 0x[hex] specifies the error. Recommended Action
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 Recommended Action
SDV-3-ASSERTION_FAILED: [chars]:[dec]
SDM process has hit an assert condition at file [chars] line number [dec]
SDV-3-AUTO_FAILOVER_ERROR: [chars]
SDV Virtual-device failed to auto-failover due to [chars] No action is required.
Recommended Action
Error Message SDV devices Explanation
SDV-3-BCAST_NOT_SUPPORTED: Broadcast attribute will be ignored for
Broadcast attribute will be ignored for SDV devices No action is required.
Recommended Action
SDV-3-ENQUEUE_EVENT_FAIL: Unable to enqueue event into state machine
Unable to enqueue event into state machine No action is required.
Recommended Action
2-418
OL-24654-01
Chapter 2
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 while processing the request. Recommended Action
SDV-3-INIT_FAIL: [chars]
SDM process init has failed due to [chars] No action is required.
Recommended Action
SDV-3-INTERNAL_ERR: [chars]
SDM process encountered an internal error due to [chars] No action is required.
Recommended Action
SDV-3-LOCK_FAILED: [chars]
An error occurred while acquiring the lock. The reason for the failure : [chars] No action is required.
Recommended Action
SDV-3-MERGE_ACTIVATION_FAILED: [chars]
Error while activating the merged SDV database due to [chars] No action is required.
Recommended Action
SDV-3-MERGE_CAP_FAILED: [chars]
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.
SDV-3-MERGE_FAILED: [chars]
SDV fabric merge failed due to [chars] Check the error using "show sdv merge staus vsan <vsan-id
Recommended Action
2-419
Chapter 2
Error Message Explanation SDV-3-MTS_ERR: [chars]
SDM process encountered an MTS error due to [chars] No action is required.
Recommended Action
SDV-4
Error Message SDV-4-FCID_REWRITE_REQUEST_TO_ACL_FAILED_AND_RETRYING: failed:[chars]. Retrying the request again. Explanation This happens when either any of the linecards being upgraded or ACL experienced error while processing the request. Recommended Action
SDV-6
Error Message Explanation SDV-6-INTERNAL_ERR_INFO: [chars]
SDM process encountered ignorable error due to [chars] No action is required.
Recommended Action
SDV-7
Error Message Explanation SDV-7-SRVCREATED: SDM Process started
SDM process has started No action is required.
Recommended Action
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] No action is required.
Recommended Action
2-420
OL-24654-01
Chapter 2
Error Message : [chars] Explanation SECURITYD-2-FIPS_CRNG_SELF_TEST_STATUS: FIPS CRNG self-test status
Status of FIPS self-test [chars] No action is required.
Recommended Action
Error Message SECURITYD-2-FIPS_CRYPTO_SELF_TEST_STATUS: FIPS [chars] Crypto self-test status : [chars] Explanation
Status of FIPS [chars] self-test [chars] No action is required.
Recommended Action
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] No action is required.
Recommended Action
SECURITYD-2-FIPS_POST_ERROR_MSG: [chars]
Fips post Error Message No action is required.
Recommended Action
Error Message SECURITYD-2-FIPS_POST_MAINTENANCE: FIPS Test failed. Moving to maintenance mode Explanation
FIPS Test failed. Moving to maintenance mode No action is required.
Recommended Action
SECURITYD-2-FIPS_POST_TEST_FAILED: FIPS crypto-test failure : [dec]
FIPS crytpo-test failed [chars] No action is required.
Recommended Action
Error Message SECURITYD-2-FIPS_POWERUP_SELF_TESTS_STATUS: FIPS power-up self-test status: [chars] Explanation
Status FIPS self-test [chars] No action is required.
Recommended Action
2-421
Chapter 2
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] No action is required.
Recommended Action
Error Message : [chars] Explanation
SECURITYD-2-FIPS_SELF_TEST_FAILED: FIPS self-test failure : [chars]
FIPS self-test failed [chars] for service [chars] No action is required.
Recommended Action
SECURITYD-2-PROGRAM_EXIT: security/accounting daemon exiting:
Security/accounting daemon is exiting.
SECURITYD-3
Error Message Explanation SECURITYD-3-NVRAMFAILURE: nvram failure
Nvram can not be read/written to. Hence accounting log can not be stored there
SECURITYD-6
Error Message Explanation SECURITYD-6-ACCOUNTING_MESSAGE: [chars]
Recommended Action
SECURITYD-6-CHANGE_PASSWD: changing passwd for [chars]
Changing passwd for [chars] No action is required.
Recommended Action
2-422
OL-24654-01
Chapter 2
Error Message SECURITYD-6-DELETE_STALE_USER_ACCOUNT: deleting expired user account:[chars] Explanation
Deleting expired user account of [chars] No action is required.
Recommended Action
SECURITYD-6-FIPS_MODE_SET_FAILED: Error when setting FIPS mode :
FIPS mode failed [chars] No action is required.
Recommended Action
SECURITYD-6-FIPS_MODE_SET: FIPS mode is [chars] for service [chars]
FIPS mode is changed [chars] [chars] No action is required.
Recommended Action
SECURITYD-6-FIPS_POST_INFO_MSG: [chars]
Fips post Information Message No action is required.
Recommended Action
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 No action is required.
Recommended Action
SENSOR_USD-2-SNSM_SYSLOG_SHUTDOWN: Sensor Mgr process shutting down:
Recommended Action
2-423
Chapter 2
Error Message failed Explanation SENSOR_USD-2-SNSM_SYSYLOG_ALLOC_MEMORY: Sensor Mgr Memory allocation
Recommended Action
SENSOR_USD-3
Error Message SENSOR_USD-3-MSG_SNSM_SYS_MEM_ALOC_FAILURE: Sensor Mgr Error in allocing mem: [dec], Error code = [dec] Explanation
Recommended Action
Error Message errno=[dec] Explanation
SENSOR_USD-3-SNSM_API_CALL_FAILURE: Sensor Mgr Error in [chars] call
Recommended Action
Error Message SENSOR_USD-3-SNSM_SYSLOG_BAD_MTS_MSG: Sensor Mgr Received bad MTS message: [dec] Explanation
Recommended Action
Error Message SENSOR_USD-3-SNSM_SYSLOG_MTS_PROCESS_ERROR: Sensor Mgr Error in processing MTS message: [dec], Error code = [hex] Explanation
Recommended Action
Error Message SENSOR_USD-3-SNSM_SYS_DEQUE_PENDING_QUE_FAILURE: Sensor Mgr Error in Dequing pend Que: %p, Error code = [hex] Explanation
Recommended Action
2-424
OL-24654-01
Chapter 2
Error Message SENSOR_USD-3-SNSM_SYS_ENQUE_PENDING_QUE_FAILED: Sensor Mgr Error in queuing to pending queue: %p, Error code = [hex] Explanation
Recommended Action
Error Message MTS mesg Explanation
SENSOR_USD-3-SNSM_SYS_MTS_RECV_FAILURE: Sensor Mgr Error in receving
Recommended Action
SENSOR_USD-5
Error Message Explanation SENSOR_USD-5-SNSM_SYSLOG_STARTING: Sensor Mgr process started
Recommended Action
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] No action is required.
Recommended Action
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 memory-type:[dec] of Size:[dec] Recommended Action
2-425
Chapter 2
SENSOR_MGR-4
Error Message Explanation SESSION-MGR-4-ISSU_FAILED: [chars] :[hex]
Session manager failed ISSU because of:[string] and error: [hex] No action is required.
Recommended Action
SFC Messages
This section contains the SFC messages.
SFC-3
Error Message Explanation SFC-3-ERROR: [chars]
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. No action is required.
Recommended Action
SFM-6
Error Message obtained Explanation SFM-6-LICENSE_VALID: A valid license for SCSI FLow Manager has been
A valid license for SCSI Flow Manager has been obtained No action is required.
Recommended Action
2-426
OL-24654-01
Chapter 2
SKSD Messages
This section contains the SKSD messages.
SKSD-2
Error Message Explanation SKSD-2-SKSD_CRYPT_SERVICE_CRIT: Encryption-Service: [chars]
Encryption Service critical errors. No action is required.
Recommended Action
SKSD-3
Error Message SKSD-3-SKSD_CRYPT_SERVICE_ERR: Encryption-Service: [chars] Explanation
Encryption Service errors. No action is required.
Recommended Action
Error Message SKSD-3-SKSD_FIPS_MODE_INIT_ERROR: Could not initialize FIPS mode : [chars] Explanation
FIPS mode initialization error No action is required.
Recommended Action
Error Message SKSD-3-SKSD_FIPS_MODE_SELFTEST: FIPS POST for [chars] [chars] Explanation
FIPS Selftest Result No action is required.
Recommended Action
SKSD-4
Error Message Explanation SKSD-4-SKSD_CRYPT_SERVICE_WARN: Encryption-Service: [chars]
Encryption Service warnings. No action is required.
Recommended Action
2-427
Chapter 2
SKSD-5
Error Message SKSD-5-SKSD_CRYPT_SERVICE_NOTICE: Encryption Service: [chars] Explanation
Encryption Service updates. No action is required.
Recommended Action
SKSD-5-SKSD_EXIT: Keystore Application Exiting: [chars]
Keystore Program exiting No action is required.
Recommended Action
SKSD-5-SKSD_FUNC: Keystore Operation: [chars]
Keystore Event upon a receiving a request No action is required.
Recommended Action
SKSD-5-SKSD_HW_INIT: Hardware Keystore Init done
Hardware Keystore Init completed No action is required.
Recommended Action
SKSD-5-SKSD_HW_RESET: Hardware Reset :[chars]
Hardware Reset No action is required.
Recommended Action
SKSD-5-SKSD_HW: Smartcard :[chars]
Smartcard Presence No action is required.
Recommended Action
SKSD-5-SKSD_INIT: Keystore Application Init: [chars]
Keystore Program Init No action is required.
Recommended Action
2-428
OL-24654-01
Chapter 2
Error Message Explanation SKSD-5-SKSD_KEY_ADD: Key added
Key added to keystore No action is required.
Recommended Action
SKSD-5-SKSD_KEY_DELETE: Key deleted
Key deleted from keystore No action is required.
Recommended Action
SKSD-5-SKSD_MKEY_INSTALL: Installing a Master Key on the smartcard(s)
Installing a new Master Key on the smartcard(s) No action is required.
Recommended Action
SKSD-5-SKSD_SUP_STATE: Supervisor card new state: [dec]
Supervisor state change No action is required.
Recommended Action
SKSD-5-SKSD_SW_INIT: Software Keystore Init done
Software Keystore Init completed No action is required.
Recommended Action
SKSD-6
Error Message Explanation SKSD-6-SKSD_CRYPT_SERVICE_INFO: Encryption Service: [chars]
Encryption Service informational updates. No action is required.
Recommended Action
SKT_USD Messages
This section contains the SKT_USD messages.
2-429
Chapter 2
SKT_USD-3
Error Message Explanation SKT_USD-3-SKT_RF_CRC_ERR: [chars]
Skytrain received packet(s) from fabric with CRC error No action is required.
Recommended Action
SKT_USD-6
Error Message Explanation SKT_USD-6-SKT_DEBUG_MSG: [chars]
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
lun paths.
Recommended Action
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. No action is required.
Recommended Action
2-430
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
lun paths.
Recommended Action
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 No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message SME_CPP-2-SME_INIT_FAILED: Initialization failed for SME: [chars], Reason: [hex] Explanation
Initialization failed for SME No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-431
Chapter 2
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 Recommended Action
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 Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-432
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
2-433
Chapter 2
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 No action is required.
module.
Recommended Action
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 Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-434
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-435
Chapter 2
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 No action is required.
Recommended Action
Error Message SME_CPP-3-SME_FIPS_MODE_ERROR: SME FIPS error: [chars] Explanation
SME module FIPS mode error No action is required.
Recommended Action
Error Message SME_CPP-3-SME_MAX_CLUSTERS_LIMIT_EXCEEDED: SME maximum clusters limit of [dec] exceeded Explanation
The maximum sme clusters limit exceeded No action is required.
Recommended Action
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 No action is required.
Recommended Action
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]. Explanation
DPP has persistent state about a previous cluster membership incarnation, but the interface is not part of any cluster. No action is required.
Recommended Action
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]. Explanation
DPP has persistent state about a previous cluster membership incarnation, but the switch has not provisioned the interface for SME. No action is required.
Recommended Action
2-436
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
SME_CPP-5-LOG_SME_INTERFACE_DOWN: SME Interface ([chars]) DOWN
SAN Interface was brought down No action is required.
Recommended Action
SME_CPP-5-LOG_SME_INTERFACE_UP: SME Interface ([chars]) is UP
SAN Interface was brought up No action is required.
Recommended Action
Error Message SME_CPP-5-LOG_SME_IT_NEXUS_FAILURE: [chars]. [chars] bind failure. Reason: [chars]: [hex] Explanation
SME IT Nexus bind failed No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-437
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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) Explanation
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-438
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message SME_CPP-5-LOG_SME_REPLACE_SMARTCARD_COMMIT: Replace smartcard process (type [chars]) committed [chars] in SME cluster (name [chars], id %llx) Explanation
Recommended Action
2-439
Chapter 2
Error Message SME_CPP-5-LOG_SME_REPLACE_SMARTCARD_START: Replace smartcard process (type [chars]) initiated [chars] in SME cluster (name [chars], id %llx) Explanation
Recommended Action
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 No action is required.
Recommended Action
SME_CPP-5-SME_DISABLED: SME Disabled
SME Service Disabled No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-440
OL-24654-01
Chapter 2
Error Message SME_CPP-5-SME_ENABLED: SME Enabled Explanation
SME Service nabled No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 Recommended Action
2-441
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-442
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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] Explanation
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-443
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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]) Explanation
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-444
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
SNMPD Messages
This section contains the SNMPD messages.
SNMPD-1
Error Message Explanation SNMPD-1-ALERT: SNMP log alert : [chars]
SNMP log alert message. No action is required.
Recommended Action
2-445
Chapter 2
SNMPD-2
Error Message Explanation SNMPD-2-CRITICAL: SNMP log critical : [chars]
SNMP log critical message. No action is required.
Recommended Action
SNMPD-3
Error Message Explanation SNMPD-3-ERROR: SNMP log error : [chars]
SNMP log error message. No action is required.
Recommended Action
SNMPD-4
Error Message Explanation SNMPD-4-WARNING: SNMP log warning : [chars]
SNMP log warning message. No action is required.
Recommended Action
SNMPD-5
Error Message Explanation SNMPD-5-NOTIFICATION: SNMP log notification : [chars]
SNMP log notification message. No action is required.
Recommended Action
SNMPD-6
Error Message Explanation SNMPD-6-INFO: SNMP log informational : [chars]
SNMP log info message. No action is required.
Recommended Action
2-446
OL-24654-01
Chapter 2
SNMPD-7
Error Message Explanation SNMPD-7-DEBUG: SNMP log debugging : [chars]
SNMP log debug message. No action is required.
Recommended Action
SPAN Messages
This section contains the SPAN messages.
SPAN-2
Error Message Explanation SPAN-2-MEM_FULL: Memory allocation failed
Memory allocation failed
SPAN-3
Error Message Explanation SPAN-3-IPC_FAIL: IPC Error
Internal IPC error No action is required.
Recommended Action
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. Recommended Action
2-447
Chapter 2
SPAN-5
Error Message session SPAN-5-ATL_VSAN_DEFAULT_ALL: Default to all VSANs for SPAN egress
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 Recommended Action
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 No action is required.
Recommended Action
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.
Recommended Action
Error Message corruption
SPAN-5-SPAN_PSS_CORRUPTION: Span is starting stateless due to PSS
Explanation Due to unrecoverable PSS corruption error, SPAN starts stateless without any configuration Recommended Action
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. Recommended Action
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.
Recommended Action
2-448
OL-24654-01
Chapter 2
SPAN-6
Error Message Explanation SPAN-6-SESSION_DOWN: Session [dec] is inactive ([chars])
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.'
SPAN-6-SESSION_UP: Session [dec] is active, destination SD port
Explanation Session [dec] is active now. You can monitor Spanned traffic at the destination SD port Recommended Action
Error Message switchover.
SPAN-6-STATELESS_SWITCHOVER: Span is starting stateless after
Explanation Active sessions are not preserved across switchover. Span is starting stateless and the configuration will be reapplied to get back the active configuration. Recommended Action
SPI Messages
This section contains the SPI messages.
SPI-SLOT#-2
Error Message Explanation SPI-SLOT#-2-SPI_INFO: [chars]
SPI Informational message No action is required.
Recommended Action
STP Messages
This section contains the STP messages.
2-449
Chapter 2
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 detected].
STP-2-BLOCK_DETECTED_PVST_PEER: Blocking port [chars] [PVST peer
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 local vlan.
STP-2-BLOCK_PVID_LOCAL: Blocking [chars] on [chars]. Inconsistent
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 peer vlan.
STP-2-BLOCK_PVID_PEER: Blocking [chars] on [chars]. Inconsistent
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. 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.
2-450
OL-24654-01
Chapter 2
Error Message [chars]. STP-2-BRIDGE_ASSURANCE_BLOCK: Bridge Assurance blocking port [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 Recommended Action
LOG_STD_NO_ACTION
STP-2-DISPUTE_CLEARED: Dispute resolved for port [chars] on [chars].
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. LOG_STD_NO_ACTION
Recommended Action
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 Recommended Action
2-451
Chapter 2
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.
Recommended Action
Issue the <CmdBold
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. Recommended Action
LOG_STD_NO_ACTION
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 Recommended Action
Issue the <CmdBold
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 [chars].
STP-2-LOOPGUARD_UNBLOCK: Loop guard unblocking port [chars] on
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.
Recommended Action
LOG_STD_NO_ACTION
2-452
OL-24654-01
Chapter 2
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.
STP-2-PVSTSIM_OK: PVST Simulation inconsistency cleared on port
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 Recommended Action
LOG_STD_NO_ACTION
STP-2-RANDNUM_FAIL: [chars]
There was a critical error during random number generation. [chars] indicates details No action is required.
of the error
Recommended Action
STP-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on [chars]
Explanation The list interface received a SSTP BPDU that was missing the VLAN id tag. The BPDU
is discarded.
Recommended Action
2-453
Chapter 2
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.
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-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.
Recommended Action
Issue the <CmdBold
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.
STP-2-ROOTGUARD_UNBLOCK: Root guard unblocking port [chars] on
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. Recommended Action
LOG_STD_NO_ACTION
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 LOG_STD_NO_ACTION
Recommended Action
2-454
OL-24654-01
Chapter 2
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 LOG_STD_NO_ACTION
Recommended Action
STP-2-STP_INIT: STP initialization of [chars] [chars]
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
Recommended Action
LOG_STD_NO_ACTION
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. Recommended Action
LOG_STD_NO_ACTION
Error Message detected].
STP-2-UNBLOCK_DETECTED_PVST_PEER: Unblocking port [chars] [PVST peer
Explanation The listed interface has stopped receiving SSTP BPDUs and so will be restored to normal spanning tree state Recommended Action
LOG_STD_NO_ACTION
2-455
Chapter 2
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 recommended guidelines.
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 recommended guidelines.
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 Recommended Action
LOG_STD_NO_ACTION
2-456
OL-24654-01
Chapter 2
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. Recommended Action
LOG_STD_NO_ACTION
STP-3
Error Message port type. STP-3-BLOCK_PORT_TYPE: Blocking [chars] on [chars]. Inconsistent
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-457
Chapter 2
Error Message [chars]. STP-3-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk [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 LOG_STD_NO_ACTION
Recommended Action
2-458
OL-24654-01
Chapter 2
STP-6
Error Message Explanation STP-6-FIRST_BPDU_TX: First BPDU transmitted
First BPDU transmitted. No action is required.
Recommended Action
Error Message STP-6-MST_DIGEST: MST digest changed to [chars], pre-std digest changed to [chars] Explanation
MST Region configuration has changed LOG_STD_NO_ACTION
Recommended Action
STP-6-MST_PORT_BOUNDARY: Port [chars] [chars] as MST Boundary port
MST Boundary port status of the specified port is changed LOG_STD_NO_ACTION
Recommended Action
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 LOG_STD_NO_ACTION
Recommended Action
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 LOG_STD_NO_ACTION
Recommended Action
STP-6-PORT_COST: Port [chars] instance [chars] cost changed to [dec]
The spanning tree port cost has changed for the specified port LOG_STD_NO_ACTION
Recommended Action
STP-6-PORT_DELETED: Interface [chars], removed from [chars]
This spanning tree port has been deleted LOG_STD_NO_ACTION
Recommended Action
2-459
Chapter 2
Error Message [chars] Explanation STP-6-PORT_LINK_TYPE: Port [chars] instance [chars] link changed to
The spanning tree port link type has changed for the specified port LOG_STD_NO_ACTION
Recommended Action
Error Message to [dec] Explanation
STP-6-PORT_PRIORITY: Port [chars] instance [chars] priority changed
The spanning tree port priority has changed for the specified port LOG_STD_NO_ACTION
Recommended Action
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 LOG_STD_NO_ACTION
Recommended Action
STP-6-PORT_RANGE_DELETED: Interface [chars] removed from [chars]
This range spanning tree logical ports has been deleted LOG_STD_NO_ACTION
Recommended Action
STP-6-PORT_RANGE_ROLE: new_role=[chars] interface=[chars] [chars]
The role of the range of spanning tree logical ports has changed LOG_STD_NO_ACTION
Recommended Action
STP-6-PORT_RANGE_STATE: new_state=[chars] interface=[chars] [chars]
The range of Spanning-Tree logical ports have changed state. LOG_STD_NO_ACTION
Recommended Action
STP-6-PORT_ROLE: Port [chars] instance [chars] role changed to
The spanning tree port role has changed for the specified port LOG_STD_NO_ACTION
Recommended Action
2-460
OL-24654-01
Chapter 2
Error Message to [chars] Explanation STP-6-PORT_STATE: Port [chars] instance [chars] moving from [chars]
The Spanning-Tree port has changed state. LOG_STD_NO_ACTION
Recommended Action
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. Recommended Action
LOG_STD_NO_ACTION
STP-6-ROOT: Root bridge for [chars] changed to [chars]
The spanning tree root bridge has changed LOG_STD_NO_ACTION
Recommended Action
STP-6-SERVICE_UP: Initialized [chars]
STP line 2. No action is required.
Recommended Action
STP-6-STATE_CREATED: Internal state created [chars]
STP has created its internal state stateless/stateful [chars]. No action is required.
Recommended Action
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). Verify fan operation with [show environment fan], and take action to cool
Recommended Action
down the switch.
2-461
Chapter 2
Error Message present. Explanation SVC_BATTERY-SLOT#-2-BATTERY_NOT_PRESENT: Battery [dec] is not
The line card does not have sufficient number of batteries. Two batteries are needed. Remove the line card and plug in batteries in the battery slots that are empty.
Recommended Action
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. Make sure the temperature of the linecard is between 5C and 40C
Recommended Action
Error Message SVC_BATTERY-SLOT#-2-CHARGING_FAILURE: Charging failure in battery [dec] ([hex]). Explanation
The module encountered failures while charging a battery. Replace the battery.
Recommended Action
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. Replace the battery.
Recommended Action
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. Recommended Action
Make sure the temperature of the linecard is between 5C and 40C
Error Message SVC_BATTERY-SLOT#-2-DISCHARGING_FAILURE: Discharging failure in battery [dec] ([hex]). Explanation
The module encountered failures while discharging a battery. Replace the battery.
Recommended Action
2-462
OL-24654-01
Chapter 2
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. Make sure the temperature is within the range to allow charging.
Recommended Action
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. No action is required.
Recommended Action
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. Recommended Action
Make sure the temperature of the linecard is between 5C and 40C
Error Message SVC_BATTERY-SLOT#-6-CONDITIONING_COMPLETED: Conditioning of battery [dec] completed successfully. Explanation
Conditioning process started for a battery is completed successfully. No action is required.
Recommended Action
Error Message SVC_BATTERY-SLOT#-6-CONDITIONING_RESUMED: Conditioning of battery [dec] resumed. Explanation
Conditioning process for a battery is resumed. No action is required.
Recommended Action
Error Message SVC_BATTERY-SLOT#-6-CONDITIONING_STARTED: Conditioning of battery [dec] started. Explanation
Conditioning process started for a battery No action is required.
Recommended Action
2-463
Chapter 2
SVC Messages
This section contains the SVC messages.
SVC-0
Error Message Explanation SVC-0-NODE_EMERG_MSG: [chars]
Syslog message from a SVC interface node No action is required.
Recommended Action
SVC-1
Error Message Explanation SVC-1-NODE_ALERT_MSG: [chars]
Recommended Action
SVC-2
Error Message Explanation SVC-2-NODE_CRIT_MSG: [chars]
Recommended Action
Error Message SVC-2-SVC_SYSLOG_INIT_FAILED: Initialization failed for SVC: [chars], Reason: [hex] Explanation
Initialization failed for SVC No action is required.
Recommended Action
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.
2-464
OL-24654-01
Chapter 2
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.
SVC-2-SVC_SYSLOG_URIFS_FAILURE: [chars] is unreachable for reason:
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 Explanation SVC-3-NODE_ERR_MSG: [chars]
Recommended Action
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-465
Chapter 2
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.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] 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.
2-466
OL-24654-01
Chapter 2
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] 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-467
Chapter 2
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] Explanation
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_PL_ER_NODE_WARMSTART ) Node warmstarted due to software error [chars] Explanation
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.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] 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.
2-468
OL-24654-01
Chapter 2
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.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_BASE_EVENT_RESOURCE_RAN_OUT ) Software error [chars] Explanation
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_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.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] 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-469
Chapter 2
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] 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] 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.
2-470
OL-24654-01
Chapter 2
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.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_LUN_RESOURCE_RAN_OUT ) Too many LUNs were presented to a node [chars] Explanation The configuration is not valid. Too many devices have been presented to the cluster or
node.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] 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-471
Chapter 2
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] 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] 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 all 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_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.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_EID_VL_ER_MDISK_RESOURCE_RAN_OUT ) Too many Managed Disks were presented to the cluster [chars] Explanation The configuration is not valid. Too many devices have been presented to the cluster or
node.
2-472
OL-24654-01
Chapter 2
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] 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.'
Recommended Action
None
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_CREATEPARTNERSHIP ) Remote Copy partnership created [chars] Explanation
svctaskmkpartnership'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_DELETEPARTNERSHIP ) Remote Copy partnership deleted [chars] Explanation
svctaskrmpartnership'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
2-473
Chapter 2
Error Message SVC-3-NODE_ERR_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_MODIFYPARTNERSHIP ) Remote Copy partnership modified [chars] Explanation
svctaskchpartnership'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
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.'
Recommended Action
None
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.'
Recommended Action
None
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. Contact IBM Product support for assistance.
Recommended Action
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 continues, ask IBM Product Support for assistance. It may be necessary to replace the Caching Services Module.
2-474
OL-24654-01
Chapter 2
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 continues, ask IBM Product Support for assistance. It may be necessary to replace the Caching 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] Explanation
2-475
Chapter 2
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 No action is required.
Recommended Action
Error Message SVC-3-SVC_SYSLOG_LC_INTERNAL_ERROR: Unable to send MTS to linecard in slot [dec]: [chars] Explanation
Linecard MTS failure No action is required.
Recommended Action
2-476
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
SVC-4
Error Message Explanation SVC-4-NODE_WARNING_MSG: [chars]
Recommended Action
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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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-477
Chapter 2
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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. 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.
2-478
OL-24654-01
Chapter 2
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. 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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] SS_EID_EC_ER_INTERNAL_UNKNOWN_EXEC_MODE ) Internal error - run mode [chars] Explanation
Node was rebooted due to internal logic error.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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. Recommended Action 1. Ensure that the software is at the latest level on the cluster. 2. Ask IBM Product Support for assistance.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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-479
Chapter 2
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
2-480
OL-24654-01
Chapter 2
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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 you have just repaired as fixed.
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. Recommended Action
None
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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-481
Chapter 2
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.'
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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. None
Recommended Action
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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,configurationcommandssent totheclusterwillfailwithamessageindicatingthatasoftwareupgradeoperationisstillinprogress.Thedow ngradeoperationmighttakeuptothreehours.' 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.
2-482
OL-24654-01
Chapter 2
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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. Perform problem determination on the network and the other cluster.
Recommended Action
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
you have just repaired as fixed.
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-483
Chapter 2
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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. None
Recommended Action
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
2-484
OL-24654-01
Chapter 2
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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.
Error Message SVC-4-NODE_WARNING_MSG: (SVC [dec]/[dec] 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. Contact IBM Product support for assistance.
Recommended Action
Error Message SVC-4-SVC_SYSLOG_IF_INTERNAL_WARN: Interface [chars] internal warning: [chars] Explanation
SVC interface internal warning No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-485
Chapter 2
SVC-5
Error Message Explanation SVC-5-NODE_NOTICE_MSG: [chars]
Recommended Action
Error Message SVC-5-SVC_SYSLOG_IF_CONFIG_DELETED: Interface [chars] configuration was deleted[chars] Explanation
SVC interface configuration was deleted No action is required.
Recommended Action
SVC-5-SVC_SYSLOG_IF_DOWN: Interface [chars] is down
SVC interface is down No action is required.
Recommended Action
SVC-5-SVC_SYSLOG_IF_UP: Interface [chars] is up
SVC interface is up No action is required.
Recommended Action
SVC-6
Error Message Explanation SVC-6-NODE_INFO_MSG: [chars]
Recommended Action
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. None
Recommended Action
2-486
OL-24654-01
Chapter 2
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.)
Recommended Action
None
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. Recommended Action
None
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. Recommended Action
None
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. Recommended Action
None
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. Recommended Action
None
2-487
Chapter 2
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_IC_EV_CLUSTER_RECOVERY_COMPLETE ) Cluster recovery completed [chars] Explanation
Cluster recovery has completed successfully. None
Recommended Action
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. None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] 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. None
Recommended Action
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). None
Recommended Action
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).' Recommended Action
None
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.
2-488
OL-24654-01
Chapter 2
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_EID_VG_EV_MIGRATE_COMPLETE ) Migration complete [chars] Explanation
Migration has completed. None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] 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. None
Recommended Action
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.' None
Recommended Action
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.' None
Recommended Action
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.'
Recommended Action
None
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.'
Recommended Action
None
2-489
Chapter 2
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.' None
Recommended Action
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.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_MODIFY ) Cluster attributes modified [chars] Explanation
svctaskchcluster'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_SHUTDOWN ) Node or Cluster shutdown [chars] Explanation
svctaskstopcluster'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
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.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_CREATE_HOST ) Host created [chars] Explanation
svctaskmkhost'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
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.' None
Recommended Action
2-490
OL-24654-01
Chapter 2
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_HOST ) Hosts deleted [chars] Explanation
svctaskrmhost'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
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.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DELETE_PORT_HOST_LIST ) Ports deleted from a Host [chars] Explanation
svctaskrmhostport'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
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.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_DEVICE_SET_NAME ) Controller attributes modified [chars] Explanation
svctaskchcontroller'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_ANALYSE ) Error log analyzed [chars] Explanation
svctaskfinderr'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_CLEARLOG ) Error log cleared [chars] Explanation
svctaskclearerrlog'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
2-491
Chapter 2
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_DUMPLOG ) Error log dumped [chars] Explanation
svctaskdumperrlog'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
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.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FC_CONSIST_GRP_SET_NAME ) Flash Copy consistency group name modified [chars] Explanation
svctaskchfcconsistgrp-name'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FC_CREATE_CONSIST_GRP ) Flash Copy consistency group created [chars] Explanation
svctaskmkfcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FC_DELETE_CONSIST_GRP ) Flash Copy consistency group deleted [chars] Explanation
svctaskrmconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
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.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_FEATURISATION_CHANGED ) Licensed settings modified [chars] Explanation
svctaskchlicense'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
2-492
OL-24654-01
Chapter 2
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.' None
Recommended Action
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.' None
Recommended Action
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.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_HOST_DELETE ) Host deleted [chars] Explanation
svctaskrmhost'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_HOST_SET_NAME ) Host attributes modified [chars] Explanation
svctaskchhost'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
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.' None
Recommended Action
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-493
Chapter 2
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.' None
Recommended Action
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.' None
Recommended Action
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.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_DELETE_MDISK ) Managed Disk deleted from Managed Disk group [chars] Explanation
svctaskrmmdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
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.' None
Recommended Action
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.' None
Recommended Action
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. None
Recommended Action
2-494
OL-24654-01
Chapter 2
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.' None
Recommended Action
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.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_ADD ) Node added [chars] Explanation
svctaskaddnode'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_CREATE_CLUSTER ) Cluster created [chars] Explanation
clusteradd'orequivalentGUIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_DELETE ) Node deleted from cluster [chars] Explanation
svctaskrmnode'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
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 None
state.
Recommended Action
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. None
Recommended Action
2-495
Chapter 2
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_SET_NAME ) Node attributes modified [chars] Explanation
svctaskchnode'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_SHUTDOWN ) Node shutdown [chars] Explanation
svctaskstopcluster-node'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_NODE_UNPEND ) Node Unpend [chars] Explanation
The node has gone online. None
Recommended Action
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.'
Recommended Action
None
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_PRETRIGGER_FC_MAPPING ) Flash Copy mapping prepared [chars] Explanation
svctaskprestartfcmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_QUORUM_CREATE ) Quorum disk set [chars] Explanation
svctasksetquorum'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_CREATECONSTGRP ) Remote Copy consistency group created [chars] Explanation
svctaskmkrcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
2-496
OL-24654-01
Chapter 2
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_CREATEREL ) Remote Copy relationship created [chars] Explanation
svctaskmkrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_DELETECONSTGRP ) Remote Copy consistency group deleted [chars] Explanation
svctaskrmconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_DELETEREL ) Remote Copy relationship deleted [chars] Explanation
svctaskrmrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_MODIFYCONSTGRP ) Remote Copy consistency group modified [chars] Explanation
svctaskchrcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_MODIFYREL ) Remote Copy relationship modified [chars] Explanation
svctaskchrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_START ) Remote Copy relationship started [chars] Explanation
svctaskstartrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
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.' None
Recommended Action
2-497
Chapter 2
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_STOP ) Remote Copy relationship stopped [chars] Explanation
svctaskstoprcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
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.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_REMOTE_SWITCH ) Remote Copy relationship switched [chars] Explanation
svctaskswitchrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
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.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_SERVICE_APPLY_SOFTWARE ) Software upgrade command accepted [chars] Explanation
clusterupgradesvc-system'orequivalentGUIcommandhasbeeninvoked.Thecommandhasbeenaccepte d.Additionallogentrieswilltracktheprogressoftheupgrade.'
Recommended Action
None
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.' None
Recommended Action
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.' None
Recommended Action
2-498
OL-24654-01
Chapter 2
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 None
committed.
Recommended Action
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). None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_CREATE ) Virtual Disk created [chars] Explanation
svctaskmkvdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_DELETE ) Virtual Disk deleted [chars] Explanation
svctaskrmvdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_EXPAND ) Virtual Disk expanded [chars] Explanation
svctaskexpandvdisksize'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
2-499
Chapter 2
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_EXPAND_SINGLE_EXT ) Virtual Disk expanded by single extent [chars] Explanation
svctaskaddvdiskext'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_MIGRATE_EXTENT ) Extent migration started [chars] Explanation
svctaskmigrateexts'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_MIGRATE_EXTENTS ) Extent migration started [chars] Explanation
svctaskmigrateexts'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
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.' None
Recommended Action
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.' None
Recommended Action
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.' None
Recommended Action
Error Message SVC-6-NODE_INFO_MSG: (SVC [dec]/[dec] SS_ERR_CFG_VDISK_SHRINK ) Virtual Disk shrunk [chars] Explanation
svctaskshrinkvdisksize'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.' None
Recommended Action
2-500
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
SVC-6-SVC_SYSLOG_CL_JOIN: Node [chars] has joined cluster [chars]
SVC interface has joined cluster No action is required.
Recommended Action
SVC-6-SVC_SYSLOG_CL_UNJOIN: Node [chars] has left cluster [chars]
SVC interface has left cluster No action is required.
Recommended Action
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 No action is required.
Recommended Action
SVC-6-SVC_SYSLOG_VSAN_INACTIVE: Vsan [dec] suspended
Vsan was suspended; can cause warnings No action is required.
Recommended Action
SVC-7
Error Message Explanation SVC-7-NODE_DEBUG_MSG: [chars]
Recommended Action
SYSMGR Messages
This section contains the SYSMGR messages.
2-501
Chapter 2
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 No action is required.
Recommended Action
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.
SYSMGR-2-CFGERASE_ABORTED: Write erase aborted.
Write erase has failed. Please verify the other syslog messages printed correct the problem, and try
Recommended Action
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. Recommended Action If the problem persists, please use the vshboot command initsystem'toinitializetheconfigurationpartition.'
SYSMGR-2-CFGSNAPSHOT_ABORTED: Configuration snapshot aborted.
An attempt to save a snapshot of the startup-config has failed. Please verify the other syslog messages printed correct the problem, and try
Recommended Action
again.
2-502
OL-24654-01
Chapter 2
Error Message failed. Explanation SYSMGR-2-CFGSYNC_FAILURE: Syncing of the configuration to the standby
Syncing of the configuration to the standby failed. Please verify the other syslog messages printed correct the problem, and try
Recommended Action
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. Recommended Action If the problem persists, please use the vshboot command initsystem'toinitializetheconfigurationpartition.'
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. Recommended Action If the problem persists, please use the vshboot command initsystem'toinitializetheconfigurationpartition.'
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. 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.
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. Recommended Action If the problem persists, please use the vshboot command initsystem'toinitializetheconfigurationpartition.'
2-503
Chapter 2
Error Message Explanation SYSMGR-2-CFGWRITE_ABORTED: Configuration copy aborted.
A configuration copy has failed. Please verify the other syslog messages printed correct the problem, and try
Recommended Action
again.
Error Message timeout.
SYSMGR-2-CFGWRITE_TIMEOUT_ABORT: Configuration copy aborted by
Explanation A service failed to store its configuration in the timeout period. The operation has been
aborted.
Recommended Action
Error Message user.
SYSMGR-2-CFGWRITE_USER_ABORT: Configuration copy aborted by the
Explanation The user typed CTRL+C while the configuration was being saved, and the operation has been aborted. Recommended Action
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. 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.
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.
2-504
OL-24654-01
Chapter 2
Error Message failed. Explanation SYSMGR-2-CONVERT_STARTUP_ABORTED: Conversion of startup-config
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. 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.
SYSMGR-2-CORE_SAVE_FAILED: [chars]: PID [dec] with message [chars].
Recommended Action
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 Recommended Action
2-505
Chapter 2
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 Recommended Action
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. Recommended Action
If the problem persists, please contact customer support.
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.
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.
2-506
OL-24654-01
Chapter 2
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. Recommended Action
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.'
SYSMGR-2-HASWITCHOVER_START: Supervisor [dec] is becoming active.
A cold switchover has started.
Recommended Action When the other supervisor is back online, use the command showsystemreset-reason'toknowwhatcausedtheswitchover.'
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.
Error Message SYSMGR-2-INVALID_HANDSHAKE: Invalid secret ([dec]) received from service [chars]. Expected [dec]. Explanation
A service cantbestarted.'
2-507
Chapter 2
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.' 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.
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.
SYSMGR-2-ISSU_FAILED: The ISSU has failed: [chars] (error-id [hex])
The ISSU has failed and the switch need to be rebooted. No action is required.
Recommended Action
Error Message [chars]. Explanation
SYSMGR-2-LAST_CORE_BASIC_TRACE: [chars]: PID [dec] with message
Recommended Action
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.
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
2-508
OL-24654-01
Chapter 2
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. Please run the command clearprocesseslogpid<pid
Recommended Action
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. Please run the command clearprocesseslogpid<pid
Recommended Action
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].
Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_DUPLICATEDCONFIG: [chars]: duplicated definition for service config. Previous definition in [chars]. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_DUPLICATEDDEPEND: [chars]: duplicated dependency from [chars] for service [chars]. Previous use in [chars]. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
2-509
Chapter 2
Error Message SYSMGR-2-PARSEERR_DUPLICATEDNAME: [chars]: short name [chars] used by service [chars] is also used by service "[chars]" in [chars]. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_DUPLICATEDOPTION: [chars]: duplicated definition for option [chars]Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_DUPLICATEDSERVICE: [chars]: duplicated definition for service [chars]. Previous definition in [chars]. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_DUPLICATEDVERDB: [chars]: duplicated definition for service version_db. Previous definition in [chars]. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_DUP_UGRPENTRY: [chars]: service [chars] duplicated in the current upgrade group. Previous use in [chars]. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
2-510
OL-24654-01
Chapter 2
Error Message SYSMGR-2-PARSEERR_FT_SET_ID_PARSEERR: [chars]: ft_set_id ([dec]) out of bound for "[chars]". Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_INCONSISTENTOPT: [chars]: option "[chars]=[chars]" not consistent with "[chars]=[chars]" for service "[chars]" Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_INVALIDCOMPCONDDEPEND: [chars] (in dependency list of compulsory conditional service [chars]): optional conditional service "[chars]" not allowed. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_INVALIDCONDDEPEND: [chars] (in dependency list of ASAP service [chars]): conditional service "[chars]" not allowed. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_INVALIDDEPEND: [chars] (in dependency list of service [chars]): service [chars] not defined for scope "[chars]". Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
2-511
Chapter 2
Error Message SYSMGR-2-PARSEERR_INVALIDEXEC: [chars]: invalid executable [chars] for service [chars]: [chars] ([dec]). Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
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]". Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_INVALIDIDENT: [chars]: [chars] "[chars]" not found for service "[chars]". Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message
SYSMGR-2-PARSEERR_INVALIDOPTION: [chars]: option [chars]-
Error Message SYSMGR-2-PARSEERR_INVALIDSTDBYDEPEND: [chars]: service [chars] cannot be dependent on service [chars] due to the standby mode wait for that service. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
2-512
OL-24654-01
Chapter 2
Error Message SYSMGR-2-PARSEERR_INVALIDVDCDEPEND: [chars] (in dependency list of service [chars]): service [chars] is a [chars] service. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_INVALID_CLEANUP_ARGUMENTS: [chars]: cleanup_arguments = "[chars]": only conditional services that are scripts can specify cleanup arguments Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_INVALID_COND_SRV_MODE: [chars]: service [chars] not defined for scope "control" or not mts aware. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_INVALID_DIR: [chars]: "[chars]" is not a valid [chars]: [chars] ([dec]). Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_INVALID_GLOBAL_SYNC: [chars]: mts unaware service may not request for a global sync. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
2-513
Chapter 2
Error Message SYSMGR-2-PARSEERR_INVALID_HB: [chars]: "[dec]" is not a valid heartbeat timeout. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_INVALID_MAX_INSTANCE: [chars]: [dec] is not a valid max_instance. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_INVALID_SHELLTREE: [chars]: invalid shell parser tree [chars] for service [chars]: [chars] ([dec]). Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_INVALID_STANDBY_MODE_GLOBAL_SYNC: [chars]: service with standby mode wait cannot request for a global sync. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message be run.
SYSMGR-2-PARSEERR_INVALID_STANDBY_MODE: [chars]: standby_mode should
2-514
OL-24654-01
Chapter 2
Error Message SYSMGR-2-PARSEERR_INVALID_STARTUP_MODE_DEPENDENCY: [chars]: Invalid dependency. Service [chars]sstartupmode('[chars]')doesnotmatchdependentservice"[chars]"'sstartupmode ('[chars]').' Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' Recommended Action
Error Message SYSMGR-2-PARSEERR_INVALID_TRANSL: [chars]: invalid translator [chars] for service [chars]: [chars] ([dec]). Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_INVALID_UGRPENTRY: [chars]: service "[chars]" is not defined. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message
SYSMGR-2-PARSEERR_MISSINGOPTION: [chars]: option [chars]-
Error Message SYSMGR-2-PARSEERR_MTSUNAWARE_HANDSHAKEDEPEND: [chars]: service [chars] is MTS unaware and cannot have handshake dependencies. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
2-515
Chapter 2
Error Message SYSMGR-2-PARSEERR_NORESTART: [chars]: option [chars]-
Error Message SYSMGR-2-PARSEERR_NOTCONFIG: [chars]: [chars] implemented only for service config. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message be added
SYSMGR-2-PARSEERR_REPARSE_CANNOT_ADD_SRV: Service "[chars]" cannot
Error Message SYSMGR-2-PARSEERR_REPARSE_CANNOT_DELETE_SRV: Service "[chars]" cannot be removed Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_REPARSE_CANNOT_MODIFY_PARAM: Cannot modify parameter [chars] for the service "[chars]", old value = [chars], new value = [chars] Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
2-516
OL-24654-01
Chapter 2
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] Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_REP_UGRPENTRY: [chars]: service [chars] is used in more than one upgrade group. First use in [chars]. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_TOOMANYDEPENDS_MULTIPLE_INST: [chars]: too many multiple instance dependencies ([dec]) for service "[chars]". Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_TOOMANYDEPENDS: [chars]: too many dependencies ([dec]) for service "[chars]". Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message SYSMGR-2-PARSEERR_UGRPDUPLICATEDNAME: [chars]: upgrade group name "[chars]" already used in [chars]. Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
2-517
Chapter 2
Error Message SYSMGR-2-PARSEERR_UGRPNAMEREDEFINED: [chars]: the upgrade group is already called "[chars]". Explanation The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.' 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.
Error Message aborted. Explanation
SYSMGR-2-PARTIAL_CFGWRITE_ABORTED: Partial configuration copy
A partial configuration copy has failed.
Recommended Action Please verify the other syslog messages printed correct the problem, and try 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.
SYSMGR-2-PSS2FILE_CONVERT_FAILED: Conversion of file [chars] failed.
Conversion of internal data format failed.
Error Message SYSMGR-2-PSS2_VOLATILE_DB_FULL: Volatile database usage in kernel is unexpectedly high at [dec]%. Explanation
System volatile database in kernel space is almost full.
Recommended Action Please run the command systemsysteminternalpsskernelmemstats'.Ifthismessagecontinuestopersist,pleasecontactTAC.'
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.
2-518
OL-24654-01
Chapter 2
Error Message ([dec]). Explanation SYSMGR-2-REDSTATE_SETFAILED: Failed to set redundancy state: ret_val
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. If the problem persists, please contact customer support.
Recommended Action
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. 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.
Error Message vdc [dec].
SYSMGR-2-RESTART_SYSTEM_LOG: We will be restarting system soon for
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. Recommended Action
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. 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.
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.
2-519
Chapter 2
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). Recommended Action
Error Message SYSMGR-2-SHUTDOWN_REJECT: The System Manager is busy saving the configuration. Please try again later. Explanation This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a). Recommended Action
SYSMGR-2-SHUTDOWN_SYSTEM_LOG: vdc [dec] will shut down soon.
We are shutting down system the vdc No action is required.
Recommended Action
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. 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.
SYSMGR-2-SOCKET_ERROR: Failed to open socket connection, errno:
Call to open socket connection failed.
2-520
OL-24654-01
Chapter 2
Error Message SYSMGR-2-SRV_CLEAR_MEMORY_ALERT: service "[chars]" clear memory alert ([dec]%) Explanation
Clean Memory Alert Event received No action is required.
Recommended Action
Error Message SYSMGR-2-SRV_MAJOR_MEMORY_ALERT: service "[chars]" major memory alert ([dec]%) Explanation
Major Memory Alert Event received No action is required.
Recommended Action
Error Message SYSMGR-2-SRV_MINOR_MEMORY_ALERT: service "[chars]" minor memory alert ([dec]%) Explanation
Minor Memory Alert Event received No action is required.
Recommended Action
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 No action is required.
Recommended Action
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.'
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. Recommended Action If the problem persists, please use the vshboot command initsystem'toinitializetheconfigurationpartition.'
2-521
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
SYSMGR-2-SWITCHOVER_OVER: Switchover completed.
The switchover is completed. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
2-522
OL-24654-01
Chapter 2
Error Message SYSMGR-2-SWITCHOVER_THRESHOLD_EXCEEDED: Switchover threshold exceeded ([dec] switchovers happened within [dec] seconds). Powering down all linecards. Explanation
Switchover threshold exceeded No action is required.
Recommended Action
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
SYSMGR-2-SYNC_FAILURE_MSG_PAYLOAD: vdc [dec]: [chars]
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 No action is required.
Recommended Action
Error Message SYSMGR-2-TMP_DIR_FULL: System temporary directory usage is unexpectedly high at [dec]%. Explanation
System /tmp space is almost full.
2-523
Chapter 2
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. Recommended Action
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. Recommended Action
Error Message SYSMGR-2-VDC_DELETE_FAILURE: The vdc delete has failed: [chars] (error-id [hex]) Explanation
The vdc delete has failed
SYSMGR-2-VDC_NOT_CLEANEDUP_SRVS: vdc [dec]: [chars]
Recommended Action
Error Message SYSMGR-2-VOLATILE_DB_FULL: System volatile database usage is unexpectedly high at [dec]%. Explanation
System volatile database space is almost full.
Recommended Action Please run the command systempssshrink'.Ifthismessagecontinuestopersist,pleasecontactTAC.'
SYSMGR-2-WARMSWITCHOVER_START: This supervisor is becoming active.
A cold switchover has started.
Recommended Action
When the other supervisor is back online, use the command showsystemreset-reason'toknowwhatcausedtheswitchover.'
2-524
OL-24654-01
Chapter 2
Error Message [dec]. SYSMGR-2-WDT_KGDB: System watchdog kgdb has been [chars] for slot
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. Recommended Action
SYSMGR-3
Error Message Explanation Recommended Action SYSMGR-3-BASIC_TRACE: [chars]: PID [dec] with message [chars].
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.
Recommended Action
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 No action is required.
Recommended Action
Error Message [hex]).
SYSMGR-3-CFGERASE_FAILED: Configuration erase failed (error-id
Explanation The requested configuration erase has failed. [dec] is the error-ID representing the failure reason. Recommended Action
Error Message [hex]).
SYSMGR-3-CFGSNAPSHOT_FAILED: Configuration snapshot failed (error-id
Explanation The requested configuration snapshot has failed. [dec] is the error-id representing the failure reason. Recommended Action
2-525
Chapter 2
Error Message [hex]). SYSMGR-3-CFGWRITE_FAILED: Configuration copy failed (error-id
Explanation The requested configuration copy has failed. [dec] is the error-id representing the failure reason. Recommended Action
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.' Please wait for the other instance to complete.
Recommended Action
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. 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.
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 configuration copy is considered failed.
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.
2-526
OL-24654-01
Chapter 2
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 configuration copy is considered failed. 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.
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. Recommended Action Use the 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 configuration copy is considered failed.
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.
SYSMGR-3-COPY_CORES_FAILED: Copying cores failed ([dec]).
Copying cores to the destination failed because of an error specified in the log. No action is required.
Recommended Action
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 ... No action is required.
Recommended Action
2-527
Chapter 2
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. No action is required.
Recommended Action
SYSMGR-3-CORE_OP_FAILED: Core operation failed: [chars]
Mainly use to display failure on core operation in general No action is required.
Recommended Action
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. No action is required.
Recommended Action
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.' Recommended Action
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. Recommended Action
2-528
OL-24654-01
Chapter 2
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. No action is required.
Recommended Action
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.
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
2-529
Chapter 2
Error Message Explanation SYSMGR-3-ISSU_BEGIN_FAILED: ISSU cannot proceed (error-id [hex]).
This message indicates that some service has blocked the ISSU. No action is required.
Recommended Action
Error Message SYSMGR-3-LC_IMAGE_UPGRADE_FAILURE: Linecard image upgrade request failed(error-id [hex]). Explanation
Linecard image upgrade request failed
SYSMGR-3-LC_RESET: Resetting linecard
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
SYSMGR-3-LC_UPG_ERROR: LC ERROR: [chars]
Linecard upgrade error message
2-530
OL-24654-01
Chapter 2
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. Recommended Action
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. Recommended Action
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. No action is required.
Recommended Action
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 No action is required.
the reason.
Recommended Action
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. Recommended Action
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. Please do a copy running startup, and try again.
Recommended Action
2-531
Chapter 2
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 failure Explanation
SYSMGR-3-RTDBCTRL_SRVFAILURE: Service "[chars]" responded with a
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
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. Recommended Action
2-532
OL-24654-01
Chapter 2
Error Message SYSMGR-3-SHUTDOWN_OVER: The System Manager is shutting down now.
Explanation This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a). Recommended Action
Error Message procedure.
SYSMGR-3-SHUTDOWN_START: The System Manager has started the shutdown
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 No action is required.
Recommended Action
Error Message SYSMGR-3-STANDBY_VDC_RESTART_FAILURE: vdc [dec] on standby failed to restart. error: [chars] ([hex]) Explanation Recommended Action
SYSMGR-3-SYSMGR_CRASHED: Sysmgr (PID [dec]) [chars]
Sysmgr has terminated abnormally. Please use the command showprocess'toverifythatsysmgrhasbeenrestarted.'
Recommended Action
SYSMGR-3-TFTP_CORES_FAILED: TFTPing cores failed ([chars]).
TFTPing cores to the destination failed because of an error specified in the log. No action is required.
Recommended Action
Error Message SYSMGR-3-UNACCEPTABLE_WAIT: Service [chars], no response from System Manager after [dec] seconds. Terminating. Explanation A spawned service couldnthandshakewiththeSystemManagerandit'sabouttobeterminated.' 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.
2-533
Chapter 2
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. No action is required.
Recommended Action
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.

Recommended Action
SYSMGR-4
Error Message [chars]. Explanation Recommended Action SYSMGR-4-BASIC_TRACE_WARNING: [chars]: PID [dec] with message
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.' Recommended Action Use the 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. Recommended Action
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. Recommended Action
2-534
OL-24654-01
Chapter 2
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]. Explanation
Error Message SYSMGR-4-PARSEWARN_VALUE_TOO_SMALL: [chars]: [chars] is too small, replaced with [dec]. Explanation
SYSMGR-4-READCONF_REJECT: Discarding configuration update request:
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]. Explanation
This message is for Cisco TAC debugging. This is not a problem or malfunction. No action is required.
Recommended Action
Error Message SYSMGR-4-SYSMGR_CORE_TRUNCATED: Core seems to be truncated on generation. [dec] / [dec] KB. PID: [dec] Explanation
Core likely truncated No action is required.
Recommended Action
2-535
Chapter 2
Error Message SYSMGR-4-SYSMGR_PLUGIN_FAILURE: Received failure response [hex] from Plugin Manager Explanation
Failure response from plugin mgr No action is required.
Recommended Action
Error Message SYSMGR-4-SYSMGR_VDC_CORE_DELETION: Cores in VDC [dec] will be deleted as part of VDC deletion Explanation
VDC cores deleted No action is required.
Recommended Action
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. Please copy cores off the supervisor and run clearcores'tofreesomespace'
Recommended Action
SYSMGR-5
Error Message Explanation SYSMGR-5-CFGERASE_DONE: Configuration erase successful.
The requested configuration erase has completed successfully. No action is required.
Recommended Action
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. Recommended Action
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. Recommended Action
2-536
OL-24654-01
Chapter 2
Error Message Explanation SYSMGR-5-CFGSNAPSHOT_DONE: Configuration snapshot successful.
The requested configuration snapshot has completed successfully. No action is required.
Recommended Action
Error Message [dec]).
SYSMGR-5-CFGSNAPSHOT_STARTED: Configuration snapshot started (PID
Explanation The requested configuration snapshot has started. [dec] is the Process-ID of the process servicing the request. Recommended Action
SYSMGR-5-CFGWRITE_DONE: Configuration copy successful.
The requested configuration copy has completed successfully. No action is required.
Recommended Action
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,thismessageindicate sthatthesystemissynchronizingthestartup-configfromtheactivesupervisor.[dec]istheProcess-IDofthe processservicingtherequest.' Recommended Action
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. Recommended Action
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. 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.
2-537
Chapter 2
Error Message SYSMGR-5-FSM_STATE_TRANS: System Manager NESTED state transition from [chars] to [chars]. Explanation Recommended Action
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 Recommended Action
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.

Recommended Action
SYSMGR-5-ISSU_BEGIN_STARTED: Notifying services of ISSU (PID [dec]).
This message indicates that the system has started notifying services for the ISSU. Services can block the upgrade at this point. No action is required.
Recommended Action
SYSMGR-5-LC_UPGRADE_REBOOT: Rebooting linecard as a part of upgrade
Linecard is being rebooted as a part of upgrade
SYSMGR-5-LC_UPGRADE_START: Starting linecard upgrade
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. No action is required.
Recommended Action
2-538
OL-24654-01
Chapter 2
Error Message present. Explanation SYSMGR-5-PARTIAL_CFGWRITE_ASCII_CONFIG: Startup-config version not
Startup-config version not present. Startup-config version is not present. Ascii configuration will be applied.
Recommended Action
Error Message successful. Explanation
SYSMGR-5-PARTIAL_CFGWRITE_DONE: Partial configuration copy
The requested configuration copy has completed successfully. No action is required.
Recommended Action
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. Recommended Action
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. No action is required.
Recommended Action
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. Recommended Action
Error Message restored.
SYSMGR-5-RUNTIME_DB_RESTORE_SUCCESS: Runtime database successfully
Explanation This message indicates that the runtime database has been successfully restored for the non-disruptive fabric switch upgrade. Recommended Action
2-539
Chapter 2
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. No action is required.
Recommended Action
Error Message SYSMGR-5-SERVICE_DELETED: Service [chars] has been removed from the System Manager database. Explanation This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a). Recommended Action
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]' Explanation
Recommended Action
Error Message SYSMGR-5-SUBPROC_TERMINATED: "[chars]" (PID [dec]) has finished with error code [chars] ([dec]). Explanation
Recommended Action
Error Message
SYSMGR-5-UGRP_COMPLETED: Upgrade completed for group [dec].
2-540
OL-24654-01
Chapter 2
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. No action is required.
Recommended Action
Error Message SYSMGR-6-HANDSHAKE_DONE: Handshake with service "[chars]" successfully performed. Explanation
Recommended Action
Error Message SYSMGR-6-HANDSHAKE_VERIFYING_DONE: Handshake verification done from service "[chars]". Explanation Recommended Action
SYSMGR-6-LC_UPG_DEBUG: LC DEBUG: [chars]
Linecard upgrade debug message
SYSMGR-6-RLIMIT_INFO: rlimit of service "[chars]"([dec]) = %llu
Recommended Action
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. Recommended Action
2-541
Chapter 2
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. No action is required.
Recommended Action
SYSMGR-6-SRVSCOPE_COMPLETED: Completed execution for scope [chars].
Recommended Action
SYSMGR-6-SRVSCOPE_STARTED: Started execution for scope [chars].
Recommended Action
Error Message SYSMGR-6-SRVSTATE_CHANGED: State for service "[chars]" changed from [chars] to [chars] in vdc [dec]. Explanation
Recommended Action
Error Message SYSMGR-6-SRV_ENQUEUED_FOR_START: Conditional service "[chars]" started by sap "[dec]" has been enqueued for start. Explanation Recommended Action
Error Message SYSMGR-6-STATE_CHANGED: System Manager state changed from [chars] to [chars] for vdc [dec]. Explanation Recommended Action
Error Message SYSMGR-6-SUBPROC_SUCCESS_EXIT: [chars] (PID [dec]) has successfully exited with exit code [chars] ([dec]). Explanation
Recommended Action
2-542
OL-24654-01
Chapter 2
Error Message SYSMGR-6-SUPERSTATE_CHANGED: System Manager super state changed from [chars] to [chars] for vdc [dec]. Explanation Recommended Action
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. Recommended Action
SYSMGR-7
Error Message SYSMGR-7-CFGWRITE_UNEXPECTEDRSP: Discarding unexpected response from service "[chars]". Explanation Recommended Action
Error Message SYSMGR-7-DUPLICATED_PFM_HANDSHAKE: PFM-handshake received from service [chars], but information already available. Explanation
Recommended Action
Error Message libcdb.
SYSMGR-7-LIBCDB_FAILURE: Conversion for service "[chars]" failed in
Explanation This message indicates that either the system could not find conversion tarball or there is no conversion library needed for this service. Recommended Action
Error Message libvdb.
SYSMGR-7-LIBVDB_FAILURE: Conversion for service "[chars]" failed in
Explanation This message indicates that the system could not find package information for this service in the version database. Recommended Action
2-543
Chapter 2
Error Message SYSMGR-7-ND_UPGD_RECOVERY_SRVSUCCEEDED: Service "[chars]" recovered its state during non-disruptive upgrade. Explanation Recommended Action
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. Recommended Action
Error Message SYSMGR-7-SWITCHOVER_SRVSUCCEDED: Service "[chars]" completed its switchover actions. Explanation
Recommended Action
Error Message SYSMGR-7-UNEXPECTEDMSG: Opcode [dec] not expected at this time from service "[chars]" ([chars]). Explanation
Recommended Action
Error Message SYSMGR-7-UNKNOWNADDR: Opcode [dec] received from unknown source [chars]. Discarding. Explanation
Recommended Action
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.
Recommended Action
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. Recommended Action
2-544
OL-24654-01
Chapter 2
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. Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-2-OHMS_BOOTFLASH_FAILED: Bootflash test maximum failures reached for module [dec] Reason: ([chars]). Explanation
Bootflash failed. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-2-OHMS_CACHE_DISK_FAILED: Cache disk [dec] failed for module [dec]. Explanation
Cache disk failed. No action is required.
Recommended Action
2-545
Chapter 2
Error Message [dec]. Explanation SYSTEMHEALTH-2-OHMS_EMGMT_FAILED: Management port failed for module
Ethernet management port failed. No action is required.
Recommended Action
SYSTEMHEALTH-2-OHMS_EOBC_FAILED: EOBC test failed for module [dec].
EOBC test failed for module. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-2-OHMS_FIPS_FAILURE: FIPS compliance error during random number generation. Explanation
FIPS compliance error. No action is required.
Recommended Action
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. Force a switch over if a standby supervisor is available, or reboot the switch
Recommended Action
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. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-2-OHMS_INBAND_FAILED: Inband test maximum failures reached for module [dec]. Explanation
Inband failed. No action is required.
Recommended Action
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. No action is required.
Recommended Action
2-546
OL-24654-01
Chapter 2
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. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-2-OHMS_MOD_SNAKE_TEST_FAILED: Module [dec] has failed snake loopback tests. Explanation
Snake test failure. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-2-OHMS_NVRAM_FAILED: Nvram test maximum failures reached for module [dec] for blocks 0x%llx. Explanation
Nvram failed. No action is required.
Recommended Action
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. Replace the compact flash on this module.
Recommended Action
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. Check the compact flash on the board and any relevant system
Recommended Action
(mis)configurations.
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. Replace the compact flash on this module.
Recommended Action
Error Message SYSTEMHEALTH-2-OHMS_SWITCHOVER_REQ: Supervisor switch over being requested due to errors found [chars] test. Explanation
System Health Switch Over Request. No action is required.
Recommended Action
2-547
Chapter 2
Error Message SYSTEMHEALTH-2-OHMS_SWITCH_RELOAD_REQ: Switch reload request due to errors found [chars] test. Explanation
System Health Switch Reload Request. No action is required.
Recommended Action
SYSTEMHEALTH-2-OHMS_TCAM_PARITY_FAILED: TCAM test failed for module
TCAM test failed for module as uncorrectable parity errors were detected. Please schedule a downtime and replace the module.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
2-548
OL-24654-01
Chapter 2
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. Please schedule a downtime and replace the compact flash on this module.
Recommended Action
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. Please schedule a downtime and replace the compact flash on this module.
Recommended Action
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. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-4-OHMS_EOBC_ERRORS: EOBC test on module [dec] has been suspended due to internal errors. Explanation
EOBC test internal errors. No action is required.
Recommended Action
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. Please upgrade the module with the latest EPLDs.'
Recommended Action
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. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-4-OHMS_FAIL_ACTION_NOTICE: Failure action not taken, failure action is disabled. Explanation
System Health SERDES test failure. No action is required.
Recommended Action
2-549
Chapter 2
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. No action is required.
Recommended Action
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. Force a switch over if a standby supervisor is available, or reboot the switch
Recommended Action
to recover
Error Message SYSTEMHEALTH-4-OHMS_INBAND_FAILING1: Inband test failed [dec] times for module [dec]. Explanation
Inband Failing. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-4-OHMS_LC_DAEMON_RESTARTED: System Health process running on module [dec] restarted. Explanation
System Heath line card daemon restarted. No action is required.
Recommended Action
2-550
OL-24654-01
Chapter 2
Error Message SYSTEMHEALTH-4-OHMS_MOD_SNAKE_PATH_FAILURE: Snake Loopback data path failure on module [dec]. Explanation
Snake data path only error. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-4-OHMS_SERDES_FAILED: SERDES loopback test on interface fc[dec]/[dec] failed. Explanation
System Health SERDES Test Failure. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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. Try restarting the cf-crc-check using system health clear-errors module <x
Recommended Action
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. Try restarting the cf-crc-check using system health clear-errors module <x
Recommended Action
2-551
Chapter 2
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. Please schedule a downtime and replace the compact flash on this module.
Recommended Action
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. Try restarting the test using system health clear-errors module <x
Recommended Action
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. Please schedule a downtime and replace the compact flash on this module.
Recommended Action
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. No action is required.
Recommended Action
2-552
OL-24654-01
Chapter 2
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. No action is required.
Recommended Action
SYSTEMHEALTH-5
Error Message SYSTEMHEALTH-5-OHMS_BATTERY_FAILING: Battery [dec] starting to fail on module [dec]. Reason: [chars]. Explanation
System Health battery failing. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-5-OHMS_BOOTFLASH_FAILING: Bootflash starting to fail on module [dec]. Explanation
System Health bootflash failing. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-5-OHMS_CDISK_FAILING: Cache disk [dec] starting to fail on module [dec]. Explanation
System Health cache disk failing. No action is required.
Recommended Action
2-553
Chapter 2
Error Message SYSTEMHEALTH-5-OHMS_EMGMT_FAILING: Management port on module [dec] starting to show signs of failures. Explanation
System Health emgmt failing. No action is required.
Recommended Action
SYSTEMHEALTH-5-OHMS_EOBC_FAILING: EOBC starting to fail on module
System Health eobc failing. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-5-OHMS_INBAND_FAILING: Inband starting to fail on module [dec]. Explanation
System Health inband failing. No action is required.
Recommended Action
SYSTEMHEALTH-5-OHMS_NVRAM_FAILING: Nvram starting to fail on module
System Health Nvram failing. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-5-OHMS_TCAM_PARITY_FAILING: TCAM starting to fail on module [dec]. Explanation
System Health Tcam failing. No action is required.
Recommended Action
2-554
OL-24654-01
Chapter 2
Error Message SYSTEMHEALTH-5-OHMS_TEST_FAILING: [chars] test starting to fail on module [dec]. Explanation
System Health test failing. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-6-OHMS_BATTERY_CLEARED: Failing conditions for battery [dec] on module [dec] have been cleared. Explanation
System Health battery failure cleared. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-6-OHMS_BOOTFLASH_CLEARED: Failing conditions for bootflash on module [dec] have been cleared. Explanation
System Health bootflash failures cleared. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-6-OHMS_EMGMT_CLEARED: Failing conditions for management port on module [dec] have been cleared. Explanation
System Health emgmt failure cleared. No action is required.
Recommended Action
2-555
Chapter 2
Error Message SYSTEMHEALTH-6-OHMS_EOBC_CLEARED: Failing conditions for EOBC on module [dec] have been cleared. Explanation
System Health eobc failures cleared. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-6-OHMS_FAILURE_CLEARED: Failing conditions for test [chars] have been cleared on module [dec]. Explanation
System Health failure cleared. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-6-OHMS_INBAND_CLEARED: Failing conditions for inband on module [dec] have been cleared. Explanation
System Health inband failures cleared. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-6-OHMS_INBAND_DROP: Inband Dropping frames from module [dec] due to unknown reasons. Explanation
System Health Inband non-timeout drop. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-6-OHMS_INBAND_TO_ERR: Inband Dropping frames from module [dec] due to timeout errors. Explanation
System Health Inband timeout drop. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message SYSTEMHEALTH-6-OHMS_NVRAM_CLEARED: Failing conditions for Nvram on module [dec] have been cleared. Explanation
System Health Nvram failures cleared. No action is required.
Recommended Action
2-556
OL-24654-01
Chapter 2
Error Message Explanation SYSTEMHEALTH-6-OHMS_STARTED: Online System Health started.
Online System Health started. No action is required.
Recommended Action
TACACS Messages
This section contains the TACACS messages.
TACACS-2
Error Message Explanation TACACS-2-TACACS_PROGRAM_EXIT: TACACS+ daemon exiting: [chars]
TACACS+ daemon is exiting.
TACACS-3
Error Message Explanation TACACS-3-TACACS_ERROR_MESSAGE: [chars]
TACACS+ Error Message No action is required.
Recommended Action
TACACS-4
Error Message Explanation TACACS-4-TACACS_WARNING: [chars]
TACACS+ warning No action is required.
Recommended Action
TACACS-5
Error Message Explanation TACACS-5-TACACS_MONITOR_STATUS: [chars] [chars]
Notifying Tacacs+ server monitor status change No action is required.
Recommended Action
2-557
Chapter 2
Error Message Explanation TACACS-5-TACACS_NOTIFICATION: [chars]
TACACS+ notification No action is required.
Recommended Action
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 No action is required.
Recommended Action
TACACS-6
Error Message Explanation TACACS-6-TACACS_ACCOUNTING_MESSAGE: [chars]
Recommended Action
TACACS-6-TACACS_MESSAGE: [chars]
TACACS+ Message No action is required.
Recommended Action
TBIRD_CMN_USD Messages
This section contains the TBIRD_CMN_USD messages.
TBIRD_CMN_USD-6
Error Message Explanation TBIRD_CMN_USD-6-TBIRD_CMN_DEBUG_MSG: [chars]
Recommended Action
TBIRD_FWD_USD Messages
This section contains the TBIRD_FWD_USD messages.
2-558
OL-24654-01
Chapter 2
TBIRD_FWD_USD-6
Error Message Explanation TBIRD_FWD_USD-6-TBIRD_FWD_DEBUG_MSG: [chars]
Recommended Action
TBIRD_MAC_USD Messages
This section contains the TBIRD_MAC_USD messages.
TBIRD_MAC_USD-3
Error Message Explanation TBIRD_MAC_USD-3-FCMAC_ERR_MSG: [chars]
Error log message No action is required.
Recommended Action
TBIRD_MAC_USD-6
Error Message Explanation TBIRD_MAC_USD-6-FCMAC_DEBUG_MSG: [chars]
Recommended Action
TBIRD_QUE_USD Messages
This section contains the TBIRD_QUE_USD messages.
TBIRD_QUE_USD-6
Error Message Explanation TBIRD_QUE_USD-6-TBIRD_QUE_DEBUG_MSG: [chars]
Recommended Action
TBIRD_XBAR_USD Messages
This section contains the TBIRD_XBAR_USD messages.
2-559
Chapter 2
TBIRD_XBAR_USD-6
Error Message Explanation TBIRD_XBAR_USD-6-TBIRD_XBAR_DEBUG_MSG: [chars]
Recommended Action
TCAP Messages
This section contains the TCAP messages.
TCAP-2
Error Message Explanation TCAP-2-MEM_FULL: Memory allocation failed.
TCAP process has failed to allocate memory. Please perform a showtcapevent-history'tocollectmoreinformation.'
Recommended Action
TCAP-2-PROC_DN: Process is shutting down: [chars]
TCAP process is exiting. Please perform a showtcapevent-history'tocollectmoreinformation.'
Recommended Action
TCAP-2-PROC_INITFAIL: Process initialization failed due to [chars].
TCAP process has failed initialization. Please perform a showtcapevent-history'tocollectmoreinformation.'
Recommended Action
TPC Messages
This section contains the TPC messages.
TPC-SLOT#-5
Error Message died Explanation TPC-SLOT#-5-LOG_ERR_TPC_DPP_DEAD: VSAN :[dec] VT pWWN :[chars] DPP
The DPP associated with the Virtual Target has crashed No action is required.
Recommended Action
2-560
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message VSAN down Explanation
TPC-SLOT#-5-LOG_ERR_TPC_VT_VSAN_DOWN: VSAN :[dec] VT pWWN :[chars]
The VSAN where the Virtual Target is configured is down No action is required.
Recommended Action
TTYD Messages
This section contains the TTYD messages.
TTYD-2
Error Message Explanation TTYD-2-TTYD_ERROR: TTYD Error [chars]
Critical TTY daemon error. No action is required.
Recommended Action
TTYD-2-TTYD_MTS: TTYD Message queue [dec] [chars]
TTY daemon message error. No action is required.
Recommended Action
2-561
Chapter 2
Error Message Explanation TTYD-2-TTYD_SDWRAP: TTYD Debug Facility error [dec] [chars]
TTY daemon Debug Facility failed. No action is required.
Recommended Action
TTYD-3
Error Message Explanation TTYD-3-TTYD_MISC_ERROR: Error [chars] with error [chars]([hex])
TTY daemon errors. No action is required.
Recommended Action
TTYD-6
Error Message Explanation TTYD-6-TTYD_MISC: TTYD [chars]
The tty daemon miscellaneous message. No action is required.
Recommended Action
TTYD-6-TTYD_PSS: TTYD Store error:[hex] [chars]
Failed to store configuration for TTY service. No action is required.
Recommended Action
TUNNEL Messages
This section contains the TUNNEL messages.
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"
2-562
OL-24654-01
Chapter 2
TUNNEL-3
Error Message Explanation TUNNEL-3-HW_PROGRAMMING_FAILED: for [chars], reason [chars]
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] No action is required.
Recommended Action
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
TUNNEL-4-TM_MTU_PROGRAMMING: Programming [chars] mtu [dec]...
Programming [chars] mtu [int] No action is required.
Recommended Action
TUNNEL-5
Error Message Explanation TUNNEL-5-IF_CLEAR_COUNTER: Interface [chars] counters is cleared
Interface [char] counters is cleared No action is required.
Recommended Action
2-563
Chapter 2
Error Message Explanation TUNNEL-5-IF_CREATED: Interface [chars] is created
Interface [char] is created No action is required.
Recommended Action
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] No action is required.
Recommended Action
TUNNEL-5-IF_DELETED: Interface [chars] is deleted
Interface [char] is deleted No action is required.
Recommended Action
TUNNEL-5-IF_STATE_UPDATE: Interface [chars] is [chars] reason
Interface [char] is [char] reason [char] No action is required.
Recommended Action
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] No action is required.
Recommended Action
TUNNEL-5-TM_DISABLED: Tunnel Disabled
Tunnel Service Disabled No action is required.
Recommended Action
TUNNEL-5-TM_ENABLED: Tunnel Enabled
Tunnel Service Enabled No action is required.
Recommended Action
2-564
OL-24654-01
Chapter 2
TUNNEL-7
Error Message Explanation TUNNEL-7-TM_INFO: [chars]
Tunnel Service info No action is required.
Recommended Action
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 Recommended Action
U2RIB-2-U2RIB_INIT: U2RIB initialization of [chars] [chars]
U2RIB initialization failed
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 No action is required.
Recommended Action
U2RIB-5
Error Message Explanation U2RIB-5-U2RIB_DISABLED: U2RIB Disabled
U2RIB Service Disabled No action is required.
Recommended Action
2-565
Chapter 2
Error Message Explanation U2RIB-5-U2RIB_ENABLED: U2RIB Enabled
U2RIB Service enabled No action is required.
Recommended Action
U2RIB-6
Error Message Explanation U2RIB-6-STATE_CREATED: Internal state created [chars]
U2RIB has created its internal state stateless/stateful [chars]. No action is required.
Recommended Action
UDLD Messages
This section contains the UDLD messages.
UDLD-3
Error Message Explanation UDLD-3-IDB_ERROR: UDLD error handling [chars] interface: [chars]
A softare error occurred in UDLD processing associated with a specific interface. LOG_STD_SH_TECH_ACTION
Recommended Action
UDLD-3-MSG_SEND_FAILURE: failed to send [chars] to sap [dec]: [chars]
Failed to send a message LOG_STD_SH_TECH_ACTION
Recommended Action
UDLD-3-UDLD_INTERNAL_ERROR: UDLD internal error: [chars]
A softare sanity check failed in the course of UDLD processing. LOG_STD_SH_TECH_ACTION
Recommended Action
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. LOG_STD_SH_TECH_ACTION
Recommended Action
2-566
OL-24654-01
Chapter 2
UDLD-4
Error Message UDLD-4-UDLD_GWRAP_COUNT: UDLD gwrap count is %lu, please log a showtechudld'fordetailinfo.' Explanation
UDLD gwrap count reached high level, show tech udld is needed to debug it. LOG_STD_SH_TECH_ACTION
Recommended Action
Error Message UDLD-4-UDLD_NEIGHBOR_MISMATCH: UDLD neighbor mismatch detected, exp: [chars], rec [chars] 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. Recommended Action
LOG_STD_SH_TECH_ACTION
Error Message detected
UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface [chars], [chars]
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. Recommended Action
LOG_STD_SH_TECH_ACTION
UDLD-4-UDLD_PORT_RESET: UDLD reset interface [chars]
A port which had been disabled for UDLD has been reset. LOG_STD_SH_TECH_ACTION
Recommended Action
UDLD-5
Error Message Explanation UDLD-5-UDLD_AGGRESSIVE: UDLD Aggressive
UDLD Service Aggressive No action is required.
Recommended Action
UDLD-5-UDLD_DISABLED: UDLD Disabled
UDLD Service Disabled No action is required.
Recommended Action
2-567
Chapter 2
Error Message Explanation UDLD-5-UDLD_ENABLED: UDLD Enabled
UDLD Service Enabled No action is required.
Recommended Action
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. Recommended Action
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. Recommended Action
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 No action is required.
analysis.
Recommended Action
VDC_MGR Messages
This section contains the VDC_MGR messages.
VDC_MGR-2
Error Message Explanation VDC_MGR-2-VDC_CRITICAL: vdc_mgr has hit a critical error: [chars]
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
2-568
OL-24654-01
Chapter 2
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 Please contact your sales representative to obtain a license
Recommended Action
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 vdcd 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
VDC_MGR-2-VDC_ONLINE: vdc [dec] has come online
Vdc_mgr has finished creating a vdc and it is ready to use No action is required.
Recommended Action
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 Explanation VDC_MGR-3-VDC_ERROR: vdc_mgr: [chars]
Vdc_mgr has recieved bad data but will try to continue Vdc_mgr will attempt to correct the error at hand
Recommended Action
2-569
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
VDC_MGR-5-VDC_HOSTNAME_CHANGE: vdc [dec] hostname changed to [chars]
Host name for a vdc has changed. No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
VDC_MGR-5-VDC_MODULETYPE: vdc_mgr: Module type changed to [chars]
This vdc has been changed to support only the the type of modules listed No action is required.
Recommended Action
VDC_MGR-5-VDC_STATE_CHANGE: vdc [dec] state changed to [chars]
A vdc state change has happened. This is most likely due to a configuration change. No action is required.
Recommended Action
2-570
OL-24654-01
Chapter 2
VEC Messages
This section contains the VEC messages.
VEC-SLOT#-3
Error Message Explanation VEC-SLOT#-3-LOG_DPP_EXCEPTION: DPP Exception DPP [dec]
No action is required. Vec
Recommended Action
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. Recommended Action
VEC-SLOT#-4
Error Message Explanation VEC-SLOT#-4-LOG_DPP_REBOOTED: DPP [dec] Rebooted
Recommended Action
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] Explanation
Recommended Action
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
Recommended Action
2-571
Chapter 2
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 Recommended Action
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 No action is required.
occured
Recommended Action
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 Recommended Action
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 Recommended Action
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 No action is required.
occured
Recommended Action
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 No action is required.
Recommended Action
2-572
OL-24654-01
Chapter 2
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 No action is required.
occured
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
occured
Recommended Action
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
Recommended Action
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 No action is required.
Recommended Action
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 Recommended Action
2-573
Chapter 2
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 No action is required.
Recommended Action
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 Recommended Action
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 No action is required.
Recommended Action
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 Recommended Action
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
Recommended Action
Error Message seconds
VEC-SLOT#-5-LOG_NOTICE_VEC_SLEEP_THRESH: VEC not scheduled for [dec]
Explanation The VEC process sleep threshold was exceeded which should not have occured. Recovery will be preformed if appropriate. Recommended Action
2-574
OL-24654-01
Chapter 2
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. Recovery will be preformed if appropriate. Recommended Action
VEDB_MGR Messages
This section contains the VEDB_MGR messages.
VEDB_MGR-2
Error Message Explanation VEDB_MGR-2-MALLOC_ERROR: Size [dec] bytes
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. Recommended Action
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.
Recommended Action
VES Messages
This section contains the VES messages.
2-575
Chapter 2
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.
Recommended Action
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 Recommended Action
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 Recommended Action
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 Recommended Action
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
Recommended Action
2-576
OL-24654-01
Chapter 2
Error Message seconds VES-SLOT#-5-LOG_NOTICE_VES_SLEEP_THRESH: VES not scheduled for [dec]
Explanation The VES process sleep threshold was exceeded which should not have occured. Recovery will be preformed if appropriate. Recommended Action
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. Recovery will be preformed if appropriate. Recommended Action
VFC Messages
This section contains the VFC messages.
VFC-3
Error Message Explanation VFC-3-VFC_MEM_ERROR: Memory consistency problem
Miscellaneous target error No action is required.
Recommended Action
VFC-3-VFC_TGT_ERROR: Target error:[chars] 0x%llx
Miscellaneous target error No action is required.
Recommended Action
VFC-6
Error Message Explanation VFC-6-STARTING: deamon started
The VFC daemon successfully started No action is required.
Recommended Action
VLAN_MGR Messages
This section contains the VLAN_MGR messages.
2-577
Chapter 2
VLAN_MGR-2
Error Message Explanation VLAN_MGR-2-CRITICAL_MSG: [chars]
VLAN Manager Critical Message No action is required.
Recommended Action
VLAN_MGR-3
Error Message Explanation VLAN_MGR-3-ERROR_MSG: [chars]
VLAN manager error No action is required.
Recommended Action
VLAN_MGR-4
Error Message Explanation VLAN_MGR-4-WARN_MSG: [chars]
VLAN manager warning No action is required.
Recommended Action
VLAN_MGR-5
Error Message Explanation VLAN_MGR-5-NOTIF_MSG: [chars]
VLAN Manager Notification Message No action is required.
Recommended Action
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 No action is required.
Recommended Action
VLAN_MGR-6
Error Message Explanation VLAN_MGR-6-INFO_MSG: [chars]
VLAN manager info No action is required.
Recommended Action
2-578
OL-24654-01
Chapter 2
Error Message Explanation VLAN_MGR-6-VLAN_CREATED: VLAN [dec], created
VLAN created No action is required.
Recommended Action
Error Message restart Explanation
VLAN_MGR-6-VLAN_MGR_STATEFULL_RESTART: VLAN Manager statefull
VLAN Manager statefull restart No action is required.
Recommended Action
Error Message restart Explanation
VLAN_MGR-6-VLAN_MGR_STATELESS_RESTART: VLAN Manager stateless
VLAN Manager stateless restart No action is required.
Recommended Action
VLAN_MGR-6-VLAN_OPER_STATUS_CHG: VLAN [dec], status changed to
VLAN operational state change No action is required.
Recommended Action
VNI Messages
This section contains the VNI messages.
VNI-2
Error Message Explanation VNI-2-ALLOC_MEMORY: Memory allocation failed
Recommended Action
2-579
Chapter 2
VNI-3
Error Message Explanation VNI-3-INIT_FAILED: Initialization failed. Component [chars]
[chars].
component.
VNI-6
Error Message Explanation VNI-6-INTERFACE_EVENT: VSAN interface [chars] [chars]
The specified VSAN Interface has been successfully [chars]. No action is required.
Recommended Action
VNI-6-STARTING: Virtual Network Interface Manager started
Recommended Action
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.
Recommended Action
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 No action is required.
Recommended Action
2-580
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
Error Message VPC-2-PEER_VPC_RESP_TIMEDOUT: Failed to receive response from peer for vPC: [dec] Explanation
VPC bringup failed No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
list.
Recommended Action
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 No action is required.
Recommended Action
Error Message VPC-2-VPC_ES_FAILED_LID_ALLOC: Failed to negotiate common LID between vPC peers. Explanation
Failed to find common lid. No action is required.
Recommended Action
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. No action is required.
Recommended Action
2-581
Chapter 2
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. No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message VPC-2-VPC_ISSU_END: Peer vPC switch ISSU end, unlocking configuration Explanation
Peer vPC switch issu end No action is required.
Recommended Action
Error Message VPC-2-VPC_ISSU_START: Peer vPC switch ISSU start, locking configuration Explanation
Peer vPC switch issu start No action is required.
Recommended Action
Error Message VPC-2-VPC_LC_FAIL: LC [dec] does not support required hardware for vPC; run showvdcmembershipstatus'forportstatus' Explanation
Lc insertion failed No action is required.
Recommended Action
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. No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-582
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
Error Message VPC-2-VPC_SUSP_ALL_VPC: Peer-link going down, suspending all vPCs on secondary Explanation
Peer link down suspend vPCs No action is required.
Recommended Action
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 No action is required.
Recommended Action
VPC-3
Error Message VPC-3-GLOBAL_CONSISTENCY_FAILED: In domain [dec], global configuration is not consistent ([chars]) Explanation
Global compat-check failed No action is required.
Recommended Action
Error Message VPC-3-INTF_CONSISTENCY_FAILED: In domain [dec], VPC [dec] configuration is not consistent ([chars]) Explanation
MCEC compat-check failed No action is required.
Recommended Action
VPC-3-PEER_UNREACHABLE: Remote Switch Unreachable
Peer unreachable No action is required.
Recommended Action
Error Message ([chars]) Explanation
VPC-3-PEER_VPC_BRINGUP_FAILED: Peer vPC [dec] bringup failed
Peer vPC bringup failed No action is required.
Recommended Action
2-583
Chapter 2
Error Message Explanation VPC-3-VPCM_ASSERTION_FAILED: [chars]
VPCM has hit an assert condition at file [chars] No action is required.
Recommended Action
VPC-3-VPCM_INIT_FAIL: vPC Manager Initialization Failed ([chars])
VPCM Initialization failed. due to [chars] No action is required.
Recommended Action
VPC-3-VPCM_INTERNAL_ERR: [chars]
VPCM encountered an internal error due to [chars] No action is required.
Recommended Action
VPC-3-VPCM_MTS_ERR: [chars]
VPCM encountered an MTS error due to [chars] No action is required.
Recommended Action
VPC-3-VPC_BRINGUP_FAILED: vPC [dec] bringup failed ([chars])
VPC bringup failed No action is required.
Recommended Action
VPC-3-VPC_PEER_LINK_BRINGUP_FAILED: vPC peer-link bringup failed
VPC Peer-link bringup failed No action is required.
Recommended Action
VPC-3-VPC_PEER_LINK_DOWN: VPC Peer-link is down
VPC Peer link is down No action is required.
Recommended Action
2-584
OL-24654-01
Chapter 2
VPC-4
Error Message Explanation VPC-4-PEER_VPC_DELETED: Peer vPC [dec] deleted
Peer vPC configuration deleted No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message VPC-4-VPC_DELETED: vPC [dec] is deleted Explanation
VPC configuration deleted No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message vPC peer Explanation
VPC-4-VPC_LC_UPG_OVER_DELIVERY_FAIL: Failed to deliver LC upgrade to
Failed to deliver LC upgrade to peer No action is required.
Recommended Action
Error Message VPC-4-VPC_PEER_LINK_DELETED: vPC Peer-link deleted. This will bringdown all vPC interfaces Explanation
VPC Peer-link configuration removed No action is required.
Recommended Action
2-585
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message VPC-4-VPC_REINITIALIZED: Reinitializing vpcs assuming peer dead Explanation
Initializing vpcs assuming peer dead No action is required.
Recommended Action
Error Message to [chars] Explanation
VPC-4-VPC_ROLE_CHANGE: In domain [dec], VPC role status has changed
VPC role status changed to (Primary/Secondary No action is required.
Recommended Action
VPC-5
Error Message VPC-5-GLOBAL_CONSISTENCY_SUCCESS: In domain [dec], global configuration is consistent Explanation
Global compat-check passed No action is required.
Recommended Action
Error Message VPC-5-INTF_CONSISTENCY_SUCCESS: In domain [dec], vPC [dec] configuration is consistent Explanation
VPC configuration is consistent No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-586
OL-24654-01
Chapter 2
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 Peer-not-alive
Recommended Action
Error Message VPC-5-ROLE_PRIORITY_CFGD: In domain [dec], vPC role priority changed to [dec] Explanation
Role priority configured No action is required.
Recommended Action
Error Message VPC-5-SYSTEM_MAC_CFGD: In domain [dec], vPC system-mac changed to [chars] Explanation
System mac configured No action is required.
Recommended Action
Error Message VPC-5-SYSTEM_PRIO_CFGD: In domain [dec], vPC system priority changed to [dec] Explanation
System priority changed No action is required.
Recommended Action
2-587
Chapter 2
Error Message VPC-5-VPCM_DISABLED: vPC Manager disabled Explanation
VPCM Service Disabled No action is required.
Recommended Action
VPC-5-VPCM_ENABLED: vPC Manager enabled
VPCM Service Enabled No action is required.
Recommended Action
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 No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message VPC-5-VPC_DOWN: vPC [dec] is down ([chars]) Explanation
VPC is down (reason) No action is required.
Recommended Action
Error Message VPC-5-VPC_PEER_LINK_UP: vPC Peer-link is up Explanation
VPC Peer-link is up No action is required.
Recommended Action
Error Message VPC-5-VPC_RESTORE_TIMER_EXPIRED: vPC restore timer expired, reiniting vPCs Explanation
VPC restore timer expired No action is required.
Recommended Action
2-588
OL-24654-01
Chapter 2
Error Message vPCs Explanation VPC-5-VPC_RESTORE_TIMER_START: vPC restore timer started to reinit
VPC restore timer start No action is required.
Recommended Action
Error Message triggered Explanation
VPC-5-VPC_ROLE_PREMPT: In domain [dec], vPC role pre-emption
VPC preemption triggered No action is required.
Recommended Action
Error Message VPC-5-VPC_UP: vPC [dec] is up Explanation
MCEC is UP No action is required.
Recommended Action
VPC-6
Error Message VPC-6-PEER_LOCK_FAILED: Locking failed on peer switch - Aborting upgrade!! Explanation
Locking failed on peer switch No action is required.
Recommended Action
Error Message changed Explanation
VPC-6-PEER_VPC_CFGD_VLANS_CHANGED: Peer vPC [dec] configured vlans
Remote MCEC configured vlans Changed No action is required.
Recommended Action
VPC-6-PEER_VPC_CFGD: peer vPC [dec] is configured
VPC is configured No action is required.
Recommended Action
VPC-6-PEER_VPC_DOWN: Peer vPC [dec] is down ([chars])
Peer vPC is down No action is required.
Recommended Action
2-589
Chapter 2
Error Message Explanation VPC-6-PEER_VPC_UP: Peer vPC [dec] is up
Peer vPC is up No action is required.
Recommended Action
Error Message VPC-6-STATS_CLEARED: vPC Statistics Cleared Explanation
VPC statistics cleared No action is required.
Recommended Action
Error Message VPC-6-TRACK_OBJ_CONFIGURED: In domain [dec], track object configured [dec] Explanation
VPC track object configured No action is required.
Recommended Action
VPC-6-TRACK_OBJ_DELETED: In domain [dec], track object deleted
VPC track object deconfigured No action is required.
Recommended Action
VPC-6-TYPE1_PARAM_CHANGED: TYPE-1 parameters changed: [chars]
Type-1 Parameters Changed No action is required.
Recommended Action
VPC-6-VPCM_INTERNAL_INFO: [chars]
VPCM got an internal info [chars] No action is required.
Recommended Action
VPC-6-VPC_ALLOWED_VLAN_CHANGED: vPC [dec] operational vlans changed
Operational vlans changed on vPC No action is required.
Recommended Action
VPC-6-VPC_CFGD: vPC [dec] is configured
VPC is configured No action is required.
Recommended Action
2-590
OL-24654-01
Chapter 2
Error Message vPC: [dec] Explanation VPC-6-VPC_CONSISTENCY_CHECK_BYPASS: Bypassing consistency check for
Bypassing consistency check for vpcs No action is required.
Recommended Action
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 Recommended Action No action is required.
Error Message VPC-6-VPC_DOMAIN_ID_CFGD: vPC domain-id configured to [dec] Explanation
VPC domain-id configured No action is required.
Recommended Action
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. No action is required.
Recommended Action
VPC-6-VPC_ES_ID_CFGD: Fabricpath switch ID [dec] configured
Fabricpath switch ID configured No action is required.
Recommended Action
VPC-6-VPC_ES_ID_REMOVED: Fabricpath switch ID [dec] removed
Fabricpath switch ID removed No action is required.
Recommended Action
VPC-6-VPC_PEER_LINK_CFGD: vPC peer-link is configured
VPC Peer-link is configured No action is required.
Recommended Action
2-591
Chapter 2
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 Recommended Action No action is required.
VPM Messages
This section contains the VPM messages.
VPM-2
Error Message Explanation VPM-2-GENERAL_ERROR: [chars]
The VP Manager has encountered an critical error. The description of error is [str.] No action is required.
Recommended Action
VPM-2-MALLOC_ERROR: Size [dec] bytes
The VP Manager could not allocate memory.
VPM-2-PSS_ERROR: [chars]
The VP Manager encountered error while operating on a persistent storage database. No action is required.
Recommended Action
VPM-2-VPMON_CRIT: [chars] [dec]
VPMON daemon critical message No action is required.
Recommended Action
VPM-2-VPMON_DPP_DOWNLOAD: HB failure, Restarting the DPP [dec]
VPMON daemon redownloading DPP(s) ISAPI API users need to re-download config data to fast path
Recommended Action
2-592
OL-24654-01
Chapter 2
Error Message [chars] Explanation VPM-2-VPMON_DPP_RELOAD_FORCE: Force reload of DPP(s) [chars]:
VPMON daemon critical action message No action is required.
Recommended Action
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.] Recommended Action
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]. 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.
VPM-3-SEND_TO_SNMP_AGENT_FAILED: [chars]
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. Recommended Action
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.
The database would be recreated.

Recommended Action
2-593
Chapter 2
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 storage databases. The persistent information has been translated to the new format. Recommended Action
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.
Recommended Action
VPM-6-BECAME_STDBY: Became STANDBY from active mode
The VP Manager became standby from active mode. No action is required.
Recommended Action
VPM-6-DG_DEREGISTERED: [chars]
The VP Manager has deregistered DG [chars] at slot=[dec] processor=[dec] and No action is required.
SAP=[dec].
Recommended Action
VPM-6-DG_REGISTERED: [chars]
The VP Manager has registered DG [chars] from slot=[dec] processor=[dec] and No action is required.
SAP=[dec].
Recommended Action
Error Message
VPM-6-EXITING: Exited due to [chars]
Explanation The VP Manager process has exited due to [char]. The process has probably been restarted automatically. Recommended Action
2-594
OL-24654-01
Chapter 2
Error Message VPM-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars] Explanation
The VP Manager was unable to send heartbeat to the system manger No action is required.
Recommended Action
Error Message
VPM-6-GENERAL_EVENT: [chars]
Explanation The VP Manager has generated an important event. The description of the event is [str.] Recommended Action
VPM-6-PSS_CREATED: [chars] PSS Created
One of the persistent information database of VP Manager has been recreated No action is required.
Recommended Action
VPM-6-PSS_DESTROYED: [chars] PSS Destroyed
One of the persistent information databases of Vp Manager has been intentionally destroyed and would be recreated. No action is required.
Recommended Action
VPM-6-SERVICE_UP: Initialized [chars]
The VP Manager is up and ready to accept client requests The service was initialized in [char] mode. No action is required.
Recommended Action
VPM-6-SWITCHOVER: Switching Over to other Sup.
The VP Manager has successfully switched over to the standby supervisor card. No action is required.
Recommended Action
VPM-6-VPMON_INFO: [chars]
VPMON daemon informational message No action is required.
Recommended Action
2-595
Chapter 2
Error Message Explanation VPM-6-VPMON_STARTING: deamon started
The VPMON daemon successfully started No action is required.
Recommended Action
Error Message : [chars] Explanation
VPM-6-VPM_MDS_LICENSE_GRACE: MDS LICENSE in grace period for feature
MDS license is in grace period. Please retrieve a new MDS license No action is required.
Recommended Action
VPM-6-VPM_MDS_LICENSE_REVOKED: MDS LICENSE REVOKED for feature :
MDS license is revoked. Please retrieve a new MDS license No action is required.
Recommended Action
VPM-6-VPM_MDS_TIMED_LICENSE: Timed MDS LICENSE for feature : [chars]
Timed MDS license No action is required.
Recommended Action
VPM-SLOT#-2
Error Message VPM-SLOT#-2-CPP_CATASTROPHIC_ERROR: ERROR: Component ([chars]) caused critical error please reboot SSM Explanation
Recommended Action
VRRP-CFG Messages
This section contains the VRRP-CFG messages.
VRRP-CFG-2
Error Message Explanation VRRP-CFG-2-ALLOC_MEMORY: Memory allocation failed
Recommended Action
2-596
OL-24654-01
Chapter 2
Error Message [dec] Explanation VRRP-CFG-2-VSH_REGISTER_FAIL: VSH registration failed returning
VRRPsparsetreeregistrationwithVSHfailed' No action is required.
Recommended Action
VRRP-CFG-3
Error Message VRRP-CFG-3-INIT_FAILED: Initialization failed. Component [chars] Explanation
[chars].
component.
Error Message operation Explanation
VRRP-CFG-3-VRRP_FEATURE_MANAGER_ERROR: Error in feature manager
The feature manager operation did not go through fine Please check the reason for error using feature manager and rectify the
Recommended Action
problem
VRRP-CFG-5
Error Message VRRP-CFG-5-STARTING: VRRP Manager service started Explanation
The service successfully started. No action is required.
Recommended Action
VRRP-ENG Messages
This section contains the VRRP-ENG messages.
VRRP-ENG-2
Error Message Explanation VRRP-ENG-2-ALLOC_MEMORY: Memory allocation failed
Recommended Action
2-597
Chapter 2
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.
VRRP-ENG-3
Error Message VRRP-ENG-3-ARP_INIT_ERROR: Failed to init ARP, ret [hex], errno [dec] Explanation
VRRP-ARP interaction failed. No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message VRRP-ENG-3-BFD_SESSION_ADD_ERROR: Failed to add a few VRRP-BFD sessions([hex] [hex]), Refer logs Explanation
Recommended Action
Error Message VRRP-ENG-3-BFD_SESSION_CREATION_ERROR: Failed to create BFD session information([hex] [hex]), Refer logs Explanation
Recommended Action
Error Message VRRP-ENG-3-BFD_SESSION_REMOVAL_ERROR: Failed to remove a few VRRP-BFD sessions([hex] [hex]), Refer logs Explanation
Recommended Action
2-598
OL-24654-01
Chapter 2
Error Message Explanation VRRP-ENG-3-INIT_FAILED: Initialization failed. Component [chars]
[chars].
component.
VRRP-ENG-3-IP_INIT_ERROR: Failed to init IP, ret [hex], errno [dec]
VRRP-IP interaction failed. No action is required.
Recommended Action
VRRP-ENG-3-L3VM_INIT_ERROR: Failed to init L3VM, ret [hex], errno
VRRP-L3VM interaction failed. No action is required.
Recommended Action
VRRP-ENG-3-URIB_INIT_ERROR: Failed to init URIB, ret [hex], errno
VRRP-URIB interaction failed. No action is required.
Recommended Action
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. Check that all VRRP nodes have the same configuration.
Recommended Action
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.' Recommended Action
2-599
Chapter 2
Error Message to [chars] Explanation VRRP-ENG-5-INTERFACE_STATE_CHANGE: Interface [chars] state changed
The interface specified has changed state This could have triggered a VRRP status No action is required.
change.
Recommended Action
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.
VRRP-ENG-5-STARTING: VRRP Engine service started
The service successfully started. No action is required.
Recommended Action
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]. No action is required.
Recommended Action
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]. Recommended Action
VSAN Messages
This section contains the VSAN messages.
2-600
OL-24654-01
Chapter 2
VSAN-2
Error Message Explanation VSAN-2-PROGRAM_EXIT: process exiting with reason: [chars]
VSAN manager process is exiting with reason [chars].
VSAN-3
Error Message Explanation VSAN-3-CFS_OPERATION_FAILED: cfs [chars] operation failed : [chars]
Cfs operation [chars1] has failed. [chars2] Please check the reason for the failure of the cfs operation and rectify the
Recommended Action
problem
VSAN-3-MEM_ALLOC_FAILED: alloc failed for size:[dec]
Memory allocation of size [dec] failed. Do "show process memory" command to see memory usage of processes.
Recommended Action
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 Explanation VSAN-6-ACTIVATED: VSAN:[dec] changing from suspended to active
Making VSAN with ID [dec] active from suspended state. No action is required.
Recommended Action
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 No action is required.
Recommended Action
2-601
Chapter 2
Error Message Explanation VSAN-6-CREATED: Created VSAN:[dec] with name:[chars]
Created VSAN with ID [dec] and name [chars]. No action is required.
Recommended Action
Error Message VSAN-6-MEMBERSHIP_UPDATE: Updated membership for interface:[chars] with VSAN:[dec] Explanation
Updating membership for interface [chars] with VSAN [dec]. No action is required.
Recommended Action
VSAN-6-REMOVED: Removed VSAN:[dec]
Removed VSAN with ID [dec]. No action is required.
Recommended Action
VSAN-6-SUSPENDED: VSAN:[dec] changing from active to suspended
Suspending VSAN with ID [dec] from active state. No action is required.
Recommended Action
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]. Recommended Action
VSD Messages
This section contains the VSD messages.
VSD-SLOT#-2
Error Message VSD-SLOT#-2-CPP_CATASTROPHIC_ERROR: ERROR: Component ([chars]) caused critical error please reboot SSM Explanation
Recommended Action
2-602
OL-24654-01
Chapter 2
VSHD Messages
This section contains the VSHD messages.
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 No action is required.
Recommended Action
Error Message VSHD-2-VSHD_SYSLOG_PSS_SNAPSHOT_ERR: Source URI:[chars] Destination URI:[chars] errcode:[dec] Explanation
PSS snapshot error No action is required.
Recommended Action
VSHD-2-VSHD_SYSLOG_SDWRAP_ERR: Description:[chars] errcode:[dec]
Debug infrastructure error No action is required.
Recommended Action
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 Please retry operation when fabric is stable
Recommended Action
Error Message VSHD-3-VSHD_SYSLOG_FILE_ERR: Purpose:[chars] Filename:[chars] errcode:[dec] Explanation
Recommended Action
VSHD-3-VSHD_SYSLOG_MTS_ERR: message [chars]
MTS message handling error No action is required.
Recommended Action
2-603
Chapter 2
Error Message Explanation VSHD-3-VSHD_SYSLOG_PARSE_TREE_ERR: [chars]
Error while updating parse tree in shell No action is required.
Recommended Action
Error Message VSHD-3-VSHD_SYSLOG_PSS_ERR: Purpose:[chars] URI:[chars] errcode:[dec] Explanation
PSS handling error No action is required.
Recommended Action
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 Please install the license file to continue using the feature.
Recommended Action
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 No action is required.
Recommended Action
2-604
OL-24654-01
Chapter 2
Error Message [chars] Explanation VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by [chars] on
CLI Configuration mode was exited No action is required.
Recommended Action
VSHD-5-VSHD_SYSLOG_ROLE_CREATED: New cli role [chars] created
New cli role created No action is required.
Recommended Action
VSHD-7
Error Message Explanation VSHD-7-VSHD_SYSLOG_PARSE_TREE_UPDATE: Parse tree [chars]
Parse tree updated in shell No action is required.
Recommended Action
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.
WWN-1-TYPES2_5_ALERT: Only [dec] (< [dec] %) Type 2 & 5 WWNs Remain
The WWN Manager has run out of WWNs of NAA Types 2 and 5
and its range.
2-605
Chapter 2
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 restarted automatically. Recommended Action
Error Message
WWN-2-GENERAL_ERROR: [chars]
Explanation The WWN Manager has encountered an critical error. The description of error is [str.]. Recommended Action
WWN-2-MALLOC_ERROR: Size [dec] bytes
The WWN Manager could not allocate memory.
Error Message Free
WWN-2-PSS_BKP_PSS_MISMATCH: Block [dec]: PSS: Not Free; BKPLN PROM:
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. Recommended Action
Error Message
WWN-2-PSS_ERROR: [chars]
Explanation The WWN Manager encountered error while operating on a persistent storage database. Recommended Action
2-606
OL-24654-01
Chapter 2
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. Recommended Action
WWN-2-TYPE1_CRIT: [dec] (< [dec] %) Remain
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.]. Recommended Action
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]. Recommended Action
WWN-3-RELEASE_ERR: Cant Rel. WWN [chars]
WWN Manager received a request to release a WWN that cannot be released. No action is required.
Recommended Action
2-607
Chapter 2
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.].
Recommended Action
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. Recommended Action
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.

Recommended Action
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. Recommended Action
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. Recommended Action
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 storage databases. The persistent information has been translated to the new format. Recommended Action
2-608
OL-24654-01
Chapter 2
Error Message Explanation WWN-4-TYPE1_WARN: [dec] (< [dec] %) Remain
The WWN Manager has only [dec] or less than [dec]-percent WWNs remaining for No action is required.
allocation.
Recommended Action
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 Explanation WWN-5-VSAN_WWN_CHANGE: [chars]
VSAN-WWN created or deleted. The description of error is [str.]. No action is required.
Recommended Action
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.
Recommended Action
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. Recommended Action
WWN-6-BECAME_STDBY: Became STANDBY from active mode
The WWN Manager became standby from active mode. No action is required.
Recommended Action
2-609
Chapter 2
Error Message Explanation WWN-6-EXCESSIVE_DELAY: [chars]
Excessive time taken for a processing event. The description of the event is [str.]. No action is required.
Recommended Action
Error Message WWN-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars] Explanation
The WWN Manager was unable to send heartbeat to the system manager. No action is required.
Recommended Action
WWN-6-GENERAL_EVENT: [chars]
The WWN Manager has generated an important event. The description of the event is No action is required.
[str.].
Recommended Action
WWN-6-PSS_CREATED: [chars] PSS Created
One of the persistent information database of the WWN Manager has been recreated. No action is required.
Recommended Action
Error Message
WWN-6-PSS_DESTROYED: [chars] PSS Destroyed
Explanation One of the persistent information databases has been intentionally destroyed and would be recreated. Recommended Action
WWN-6-RELEASED_BLOCK: Block number [dec]
The WWN Manager has released a block, block number [dec], of 256 WWNs. No action is required.
Recommended Action
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. Recommended Action
2-610
OL-24654-01
Chapter 2
Error Message Explanation WWN-6-SERVICE_UP: Initialized [chars]
The WWN Manager is up and ready to accept client requests for WWNs. The service was initialized in [char] mode. No action is required.
Recommended Action
WWN-6-SWITCHOVER: Switching Over to other Supervisor
The WWN Manager has successfully switched over to the standby supervisor card. No action is required.
Recommended Action
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. Recommended Action
XBAR_CLIENT Messages
This section contains the XBAR_CLIENT messages.
XBAR_CLIENT-2
Error Message Explanation XBAR_CLIENT-2-CROSS_LINK_SYNC_LOSS: XBAR-[chars].
Cross links lost sync and hence xbar is brought down. Please reload the xbar using reloadxbar<xbar-num
Recommended Action
XBAR_CLIENT-2-MEM_FULL: Memory allocation failed.
XBAR_CLIENT process has failed to allocate memory. Please perform a showxbar-clientevent-history'tocollectmoreinformation.'
Recommended Action
XBAR_CLIENT-2-MEM_FULL: memory allocation failed
Process xbar_client failed to allocate memory Please examine the xbar-client event-history for more information.
Recommended Action
2-611
Chapter 2
Error Message Explanation XBAR_CLIENT-2-PROC_DN: Process is shutting down: [chars].
XBAR_CLIENT process is exiting. Please perform a showxbar-clientevent-history'tocollectmoreinformation.'
Recommended Action
XBAR_CLIENT-2-PROC_DN: exiting: [chars].
Process xbar_client is exiting Please examine the xbar-client event-history for more information.
Recommended Action
XBAR_CLIENT-2-PROC_INITFAIL: Process initialization failed due to
XBAR_CLIENT process has failed initialization. Please perform a showxbar-clientevent-history'tocollectmoreinformation.'
Recommended Action
XBAR_CLIENT-2-PROC_INITFAIL: Process initialization failed due to
XBAR_CLIENT process has failed initialization. Please perform a showxbar-clientevent-history'tocollectmoreinformation.'
Recommended Action
XBAR_CLIENT-2-PROC_INITFAIL: initialization failed due to [chars]
Process xbar_client failed initialization Please examine the xbar-client event-history for more information.
Recommended Action
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. Please perform a showxbar-clientevent-history'tocollectmoreinformation.'
Recommended Action
Error Message XBAR_CLIENT-3-IPC_MSGERR: failure processing IPC message [dec], error code = [dec] Explanation
Process xbar_client failed to process IPC message Please examine the xbar-client event-history for more information.
Recommended Action
2-612
OL-24654-01
Chapter 2
Error Message Explanation XBAR_CLIENT-3-IPC_MSGUNKN: Received unexpected IPC message: [dec].
XBAR_CLIENT process has received an unknown message. Please perform a showxbar-clientevent-history'tocollectmoreinformation.'
Recommended Action
XBAR_CLIENT-3-IPC_MSGUNKN: unknown IPC message received: [dec]
Process xbar_client has received an unknown IPC message. Please examine the xbar-client event-history for more information.
Recommended Action
XBAR_CLIENT-3-SUP2_XBC_MOD_INIT_FAIL: [chars], errcode - [hex]
The module initialiazation failed
Recommended Action Please perform a 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
XBAR_CLIENT-SLOT#-2-VEGAS2_XBC_PROC_DN: terminating due to signal
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
2-613
Chapter 2
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 [hex] Explanation
XBAR_CLIENT-SLOT#-3-VEGAS2_XBC_MOD_INIT_FAIL: [chars], errcode -
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 . No action is required.
Recommended Action
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. Recommended Action
Error Message XBAR-2-XBAR_INSUFFICIENT_XBAR_BANDWIDTH: Module in slot [dec] has insufficient xbar-bandwidth. Explanation
To track insufficient xbar-bandwidth. No action is required.
Recommended Action
2-614
OL-24654-01
Chapter 2
Error Message XBAR-2-XBAR_SUFFICIENT_XBAR_BANDWIDTH: Module in slot [dec] has sufficient xbar-bandwidth. Explanation
To track recovery from insufficient xbar-bandwidth. No action is required.
Recommended Action
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.
Recommended Action
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. No action is required.
Recommended Action
XBAR-3
Error Message Explanation Recommended Action XBAR-3-MEM_FULL: Memory allocation failed. [chars] %i
XBAR-5
Error Message XBAR-5-ARBITER_INIT_FAILURE: Re-initializing Arbiter. [chars] [chars] module %i Explanation
Recommended Action
Error Message XBAR-5-ARB_CLEAR_PORT_FAIL: Arbiter reported failure to de-register port [dec] in group [dec] return_code [hex] ([chars]). Explanation
Recommended Action
2-615
Chapter 2
Error Message XBAR-5-ARB_INIT_MOD_DIS_INTR_FAIL: Arbiter reported failure to disable interrupt for module [dec] return_code [hex] ([chars]). Explanation
Recommended Action
Error Message XBAR-5-ARB_INIT_MOD_INSERT_CHECK_FAIL: Arbiter reported failure to recognize module [dec] return_code [hex] ([chars]). Explanation
Recommended Action
Error Message XBAR-5-ARB_INIT_MOD_INSERT_FAIL: Arbiter reported failure to init module [dec] return_code [hex] ([chars]). Explanation
Recommended Action
Error Message XBAR-5-ARB_INIT_MOD_INTR_FAIL: Arbiter reported failure to enable interrupt for module [dec] return_code [hex] ([chars]). Explanation
Recommended Action
Error Message XBAR-5-ARB_INIT_MOD_REMOVE_FAIL: Arbiter reported failure to remove module [dec] return_code [hex] ([chars]). Explanation
Recommended Action
Error Message XBAR-5-ARB_INIT_PORT_FAIL: Arbiter reported failure to register port [dec] in group [dec] return_code [hex] ([chars]). Explanation
Recommended Action
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
2-616
OL-24654-01
Chapter 2
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 No action is required.
reloaded
Recommended Action
Error Message mode failed
XBAR-5-XBAR_ENABLE_FPOE_DB_FAILURE: XBAR [chars] enabling FPOE-DB
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. Recommended Action
Error Message %i
XBAR-5-XBAR_INIT_FAILURE: XBAR [chars] initialization failed [chars]
Explanation The supervisor has experienced a fabric initialization failure. The supervisor is going to reboot. In case of dual supervisor, a switchover will occur. Recommended Action
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 . No action is required.
Recommended Action
XBAR-5-XBAR_MOD_INSERT_SEQ_FAILURE: [chars] for module [dec]
The xbar manager received failure response and is failing the insert sequence No action is required.
Recommended Action
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 No action is required.
Recommended Action
Error Message XBAR-5-XBAR_PORT_CHECK_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to check sync on port [dec] return_code [hex] ([chars]). Explanation
Recommended Action
2-617
Chapter 2
Error Message XBAR-5-XBAR_PORT_CONTINUE_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to continue sync on port [dec] return_code [hex] ([chars]). Explanation
Recommended Action
Error Message XBAR-5-XBAR_PORT_DISABLE_FAIL: Xbar [[dec].[dec]] reported failure to disable port [dec] return_code [hex] ([chars]). Explanation
Recommended Action
Error Message XBAR-5-XBAR_PORT_ENABLE_FAIL: Xbar [[dec].[dec]] reported failure to enable port [dec] return_code [hex] ([chars]). Explanation
Recommended Action
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]). Explanation
Recommended Action
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]). Explanation
Recommended Action
Error Message XBAR-5-XBAR_PORT_LPBACK_DISABLE_FAIL: Xbar [[dec].[dec]] reported failure to disable port loopback on [dec] return_code [hex] ([chars]). Explanation
Recommended Action
Error Message XBAR-5-XBAR_PORT_LPBACK_ENABLE_FAIL: Xbar [[dec].[dec]] reported failure to enable port loopback on [dec] return_code [hex] ([chars]). Explanation
Recommended Action
2-618
OL-24654-01
Chapter 2
Error Message XBAR-5-XBAR_PORT_START_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to start sync on port [dec] return_code [hex] ([chars]). Explanation
Recommended Action
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 . No action is required.
Recommended Action
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 . No action is required.
Recommended Action
XBAR-5-XBAR_STANDBY_SUP_ARB_FAIL: [chars] return_code [hex]
The supervisor has experienced an arbiter access failure . No action is required.
Recommended Action
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. No action is required.
Recommended Action
Error Message XBAR-5-XBAR_SW_INIT_FAIL: Xbar [[dec].[dec]] reported failure durinig sw intialization return_code [hex] ([chars]). Explanation
Recommended Action
2-619
Chapter 2
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. Recommended Action
XMLMA Messages
This section contains the XMLMA messages.
XMLMA-2
Error Message [chars] Explanation XMLMA-2-HEARTBEAT_FAIL: XML master agent failed to send heart beat:
XML master agent has failed sending heartbeat. No action is required.
Recommended Action
XMLMA-2-INITFAIL: XML master agent initialization fails: [chars]
XML master agent has failed initialization. No action is required.
Recommended Action
XMLMA-2-MTSERROR: XML master agent mts operation failed: [chars]
XML master agent mts operation failed. No action is required.
Recommended Action
XMLMA-2-PSSFAILURE: XML master agent pss operation failed: [chars]
XML master agent pss operation failed. No action is required.
Recommended Action
XMLMA-2-XMLMACRIT: XML master agent: [chars]
XML master agent critical log. No action is required.
Recommended Action
2-620
OL-24654-01
Chapter 2
XMLMA-3
Error Message Explanation XMLMA-3-XMLMAERR: XML master agent: [chars]
XML master agent error log. No action is required.
Recommended Action
XMLMA-5
Error Message Explanation XMLMA-5-STARTING: XML master agent started [chars]
XML master agent has been started. No action is required.
Recommended Action
XMLMA-6
Error Message Explanation XMLMA-6-XMLMAEXIT: XML master agent exiting...: [chars]
XML master agent is exiting. No action is required.
Recommended Action
XMLMA-6-XMLMALOG: XML master agent operation log: [chars]
XML master agent operation log. No action is required.
Recommended Action
XMLSA Messages
This section contains the XMLSA messages.
XMLSA-2
Error Message [chars] Explanation XMLSA-2-HEARTBEAT_FAIL: XML sub agent failed sending heart beat:
XML sub agent failed sending heartbeat. No action is required.
Recommended Action
2-621
Chapter 2
Error Message Explanation XMLSA-2-INITFAIL: XML sub agent initialization fails: [chars]
XML agent has failed initialization. No action is required.
Recommended Action
XMLSA-2-USER_INACTIVE: XML sub agent timeed out: [chars]
XML sub agent timedout due to inactivity. No action is required.
Recommended Action
XMLSA-2-VSH_ERR: XML sub agent vsh cmd error...: [chars]
XML sub agent vsh cmd error. No action is required.
Recommended Action
XMLSA-5
Error Message Explanation XMLSA-5-STARTING: XML sub agent started: [chars]
XML sub agent has been started. No action is required.
Recommended Action
XMLSA-6
Error Message Explanation XMLSA-6-XMLSAEXIT: XML sub agent exiting...: [chars]
XML sub agent is exiting. No action is required.
Recommended Action
XMLSA-6-XMLSALOG: XML sub agent log: [chars]
XML sub agent log. No action is required.
Recommended Action
ZBM Messages
This section contains the ZBM messages.
2-622
OL-24654-01
Chapter 2
ZBM-2
Error Message [chars]. Explanation ZBM-2-ZBM_HA_FAILURE: Failed to do high availability operation:
Recommended Action
Error Message ZBM-2-ZBM_INIT_FAILED: Initialization failed for ZBM: [chars], reason: [hex]. Explanation
Initialization failed for ZBM due to [chars], reason: [hex]. No action is required.
Recommended Action
Error Message ZBM-2-ZBM_INIT_WARNING: Initialization warning for ZBM: [chars], reason: [hex]. Explanation
Initialization warning for ZBM due to [chars], reason: [hex]. No action is required.
Recommended Action
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]. Recommended Action
ZBM-2-ZBM_MALLOC_FAILURE: Memory allocation failed for size [dec]
Recommended Action
ZBM-2-ZBM_MTS_FAILURE: Failed to do MTS operation: [chars].
Recommended Action
2-623
Chapter 2
Error Message ZBM-2-ZBM_MTS_REGISTRATION_FAILED: MTS options setting to [hex] failed for opCode: [dec]. Explanation
Recommended Action
Error Message [hex]. Explanation
ZBM-2-ZBM_PSS_FAILURE: Failed to do PSS operation: [chars], reason:
Recommended Action
Error Message ZBM-2-ZBM_PSS_VER_FAIL: PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec]. Explanation
Recommended Action
ZBM-2-ZBM_RUNTIME_FAILURE: [chars] [dec], Error: [hex]
ZBM runtime failure is reported as [chars] [dec], reason: [hex]. No action is required.
Recommended Action
ZBM-2-ZBM_TCAM_FAILURE: Failed to do TCAM operation: [chars].
Failed to do TCAM operation. [chars] is the reason. No action is required.
Recommended Action
ZBM-2-ZBM_TCAM_SEND: [chars]
Sending to tcam [chars] No action is required.
Recommended Action
ZBM-4
Error Message Explanation ZBM-4-ZBM_WARNING: [chars] [dec]
ZBM warning messages is reported as [chars] [dec]. No action is required.
Recommended Action
2-624
OL-24654-01
Chapter 2
ZBM-6
Error Message Explanation ZBM-6-ZBM_DIAG_EVENT_STATUS: [chars] [hex].
ZBM system health management event status is reported as [chars] [hex]. No action is required.
Recommended Action
ZBM-6-ZBM_ECHO_PROGRAMMING_FAILED: [chars].
Programming echo entry failed for [chars]. No action is required.
Recommended Action
ZBM-6-ZBM_E_PORT_EVENT_STATUS: [chars] [chars].
ZBM xEport event status is reported as [chars] [chars]. No action is required.
Recommended Action
ZBM-6-ZBM_FCC_EVENT_STATUS: [chars] [chars].
ZBM FCC event status is reported as [chars] [chars]. No action is required.
Recommended Action
ZBM-6-ZBM_INIT_PROCESS: Zone Block Mgr process started [chars] at
Zone Block Mgr process started in [chars] (stateless/stateful) mode at time [chars]. No action is required.
Recommended Action
ZBM-6-ZBM_LINECARD_EVENT_STATUS: [chars] [hex].
ZBM linecard event status is reported as [chars] [dec]. No action is required.
Recommended Action
ZBM-6-ZBM_MCAST_EVENT_STATUS: [chars] [chars].
ZBM multicast event status is reported as [chars] [chars]. No action is required.
Recommended Action
2-625
Chapter 2
Error Message Explanation ZBM-6-ZBM_NX_PORT_EVENT_STATUS: [chars] [chars].
ZBM Nx Port event status is reported as [chars] [chars]. No action is required.
Recommended Action
ZBM-6-ZBM_PORT_MODE_EVENT_STATUS: [chars] [chars].
ZBM portmode event status is reported as [chars] [chars]. No action is required.
Recommended Action
ZBM-6-ZBM_RUNTIME_STATUS: [chars] [dec]
ZBM runtime status is reported as [chars] [dec]. No action is required.
Recommended Action
ZBM-6-ZBM_STATUS: ZBM Status: [chars].
ZBM status is reported as [chars]. No action is required.
Recommended Action
ZBM-6-ZBM_UPDATE_SSRAM_QOS_EVENT_STATUS: [chars] [chars].
ZBM update SSRAM for QoS event status is reported as [chars] [chars]. No action is required.
Recommended Action
ZONE Messages
This section contains the ZONE messages.
ZONE-2
Error Message [chars] ZONE-2-LZ_EXITING: LUN/Read-only zoning process exited. Reason:
Explanation The LUN/Read-only zoning process has exited due to [char]. The process has probably been restarted automatically. Recommended Action
2-626
OL-24654-01
Chapter 2
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]. Recommended Action
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]. No action is required.
Recommended Action
ZONE-2-LZ_MALLOC_ERROR: Size [dec] bytes
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.
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
2-627
Chapter 2
Error Message Explanation ZONE-2-ZS_CHANGE_ACA_FAILED: ACA failed : [chars]
Zone Server cannot acquire change authorization : [chars]. Verify the interoperability mode on all the switches OR retry later.
Recommended Action
Error Message ZONE-2-ZS_CHANGE_ACQUIRE_AUTH_FAILED: Acquire authorization failed on VSAN [dec] Explanation
Zone Server cannot acquire authorization on VSAN [dec]. No action is required.
Recommended Action
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]. No action is required.
Recommended Action
ZONE-2-ZS_CHANGE_ACTIVATION_FAILED_RESN: Activation failed : reason
Zone Server cannot activate due to reason [chars]. No action is required.
Recommended Action
ZONE-2-ZS_CHANGE_ACTIVATION_FAILED: Activation failed
Zone Server cannot activate the zoneset. No action is required.
Recommended Action
ZONE-2-ZS_CHANGE_APPLY_FAILED: Apply changed failed on VSAN [dec]
Zone Server cannot apply changes on VSAN [dec]. No action is required.
Recommended Action
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]. No action is required.
Recommended Action
2-628
OL-24654-01
Chapter 2
Error Message ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED_RESN: Deactivation failed : reason [chars] Explanation
Zone Server cannot deactivate due to reason [chars]. No action is required.
Recommended Action
ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED: Deactivation failed
Zone Server cannot deactivate the zoneset. No action is required.
Recommended Action
Error Message ZONE-2-ZS_CHANGE_RELEASE_AUTH_FAILED: Release authorization failed on VSAN [dec] Explanation
Zone Server cannot release authorization on VSAN [dec]. No action is required.
Recommended Action
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] Verify the interoperability mode on the switch.
Recommended Action
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] Verify the interoperability mode on the switch.
Recommended Action
ZONE-2-ZS_CHANGE_SFC_FAILED: SFC failed : [chars]
Zone Server cannot stage zone configuration : [chars]. Verify the interoperability mode on all the switches.
Recommended Action
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] Verify the interoperability mode on the switch.
Recommended Action
2-629
Chapter 2
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]. No action is required.
Recommended Action
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]. No action is required.
Recommended Action
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]. No action is required.
Recommended Action
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]. No action is required.
Recommended Action
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]. No action is required.
Recommended Action
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]. No action is required.
Recommended Action
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]. No action is required.
Recommended Action
2-630
OL-24654-01
Chapter 2
Error Message Explanation ZONE-2-ZS_DB_OPERATION_FAILED: Database operation error: [chars]
Database operation is failed : [chars]. No action is required.
Recommended Action
ZONE-2-ZS_EXPORT_IMPORT_FAILED: [chars] operation failed
[chars] (Export/Import) operation failed. No action is required.
Recommended Action
Error Message ZONE-2-ZS_FIPS_COMPLIANCE_FAILURE: FIPS compliance error: consecutively same random numbers Explanation
FIPS compliance error: consecutively same random numbers No action is required.
Recommended Action
ZONE-2-ZS_INIT_FAILED: [chars]
Zone Server initialization failed : [chars]. No action is required.
Recommended Action
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. Recommended Action
ZONE-2-ZS_LIC_FAILURE: License [chars] operation failed for license
License [char] operation failed for license [char]. No action is required.
Recommended Action
Error Message VSAN [dec] Explanation
ZONE-2-ZS_LUN_DISABLING_FAILED: license expiry handling failed for
License expiry handling failed for VSAN [dec]. No action is required.
Recommended Action
2-631
Chapter 2
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.
ZONE-2-ZS_MALLOC_FAILURE: Memory allocation failed for size [dec]
Recommended Action
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 Flap the interface.
requests.
Recommended Action
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.
2-632
OL-24654-01
Chapter 2
Error Message [chars] Explanation ZONE-2-ZS_MERGE_UNKNOWN_FORMAT: Unknown format, isolating interface
Interface [chars] isolated due to unknown format in merge request. Set the interoperability mode to same value on both switches.
Recommended Action
ZONE-2-ZS_MTS_OPER_FAILED: MTS [chars] operation failed : [chars]
Zone Server MTS [chars] operation failed : [chars]. No action is required.
Recommended Action
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]. Enable Zone Based RSCN
Recommended Action
ZONE-2-ZS_PORT_SWAP_FAILURE: Port swap operation failed
Port swap operation failed. No action is required.
Recommended Action
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]. Upgrade/Downgrade to expected version.
Recommended Action
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.
Recommended Action
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 No action is required.
failure.
Recommended Action
2-633
Chapter 2
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. No action is required.
Recommended Action
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.
Recommended Action
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 No action is required.
failure.
Recommended Action
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]. No action is required.
Recommended Action
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

Recommended Action
Error Message exceeded
ZONE-2-ZS_ZONE_LIMIT_EXCEEDED: The limit for maximum number of zones
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.
2-634
OL-24654-01
Chapter 2
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. Recommended Action
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 Make sure qos is enabled and reactivate the zoneset in vsan.
Recommended Action
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]. Recommended Action
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]. Recommended Action
2-635
Chapter 2
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 No action is required.
members.
Recommended Action
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. Recommended Action
ZONE-4-ZS_DB_WARNING: [chars]
Database operation warning: [chars]. No action is required.
Recommended Action
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]. No action is required.
Recommended Action
ZONE-4-ZS_FC2_OPER_FAILED: FC2 [chars] operation failed : [chars]
Zone Server FC2 [chars] operation failed : [chars]. No action is required.
Recommended Action
ZONE-4-ZS_IF_PORT_MODE_CONFLICT: Port mode conflict for if [chars]
Port mode conflict for if [chars] Shutdown/no shutdown the interface
Recommended Action
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] Explanation
Virtual device fwwn: [chars] is not a valid zone/alias member, virtual name: [chars] pwwn: [chars]. No action is required.
Recommended Action
2-636
OL-24654-01
Chapter 2
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. Recommended Action
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. ' Recommended Action
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] No action is required.
Recommended Action
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]. No action is required.
Recommended Action
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] Explanation Virtual and Real devices are zoned together or zoned with same device, virtual name: [chars] pwwn: [chars]. Recommended Action
2-637
Chapter 2
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 Explanation ZONE-5-ZS_EXPORT_IMPORT_COMPLETE: [chars] operation completed
[chars] (Export/Import) operation completed. No action is required.
Recommended Action
ZONE-5-ZS_POLICY_CHANGE: Default zoning policy changed to [chars]
Default zoning policy changed to (permit/deny). No action is required.
Recommended Action
ZONE-5-ZS_ZONE_SET_ACTIVATED: Zoneset [chars] activated
Zoneset [chars] activated. No action is required.
Recommended Action
ZONE-5-ZS_ZONE_SET_DEACTIVATED: Zoneset deactivated
Zoneset deactivated. No action is required.
Recommended Action
2-638
OL-24654-01
Chapter 2
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. No action is required.
Recommended Action
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. No action is required.
Recommended Action
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 No action is required.
manager.
Recommended Action
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]. Recommended Action
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]. Recommended Action
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]. Recommended Action
2-639
Chapter 2
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]. Recommended Action
ZONE-6-LZ_SERVICE_UP: LUN/Read-only zoning Process initialized
Explanation The LUN/Read-only zoning process is up. The process was initialized in [char] mode. Recommended Action
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. Recommended Action
Error Message is rejected
ZONE-6-ZS_CHANGE_ACA_REJECTED: ACA received from remote domain [dec]
Explanation Received invalid ACA from domain [dec]. Either the domain list do not match OR authorization has already been acquired by another switch. Recommended Action
Verify the interoperability mode on the switch.
ZONE-6-ZS_FC2_OPER_INFO: FC2 [chars] operation failed : [chars]
Zone Server FC2 [chars] operation failed : [chars]. No action is required.
Recommended Action
ZONE-6-ZS_INIT_PROCESS: Zone Server process started [chars] at
Zone Server process started in [chars] (stateless/stateful) mode at time [chars]. No action is required.
Recommended Action
ZONE-6-ZS_INIT_WARNING: [chars]
Warning during Zone Server Initialization: [chars]. No action is required.
Recommended Action
2-640
OL-24654-01
Chapter 2
Error Message Explanation ZONE-6-ZS_INVALID_MEMBER: Invalid member [dec] [chars]
Invalid member type [dec] [chars] recieved from the API call.
Recommended Action
ZONE-6-ZS_UNKNOWN_LIC_FEATURE: [chars]
Zone Server received an event for an known licensing feature: [chars]. No action is required.
Recommended Action
2-641
Chapter 2
2-642
OL-24654-01

SL Nx-Os

Uploaded by

Copyright:

Available Formats

SL Nx-Os

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SL Nx-Os

Uploaded by

Copyright:

Available Formats

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 .

Text Part Number: OL-24654-01

Obtaining Documentation and Submitting a Service Request

Preface Document Conventions

Screen examples use these conventions:

This document uses the following conventions:

Obtaining Documentation and Submitting a Service Request

Introduction to System Messages for Cisco NX-OS

System Log Message Format

Syslog Format On a Resident Switch

System Log Message Format Description

Element month dd hh:mm:ss

Chapter 1 System Log Message Format

Introduction to System Messages for Cisco NX-OS

Level 0 emergency 1 alert 2 critical 3 error 4 warning 5 notification 6 informational 7 debugging

is a code that uniquely identifies the system message.

Representation [dec] [hex]

Type of Information Decimal number Hexadecimal number

Representation [char] [chars]

Type of Information Single character Character string

Syslog Format On a Remote-Logging Server

System Log Message Format Description

Element month dd hh:mm:ss IP-addr-switch facility severity MNEMONIC

Chapter 1 System Log Message Format

Introduction to System Messages for Cisco NX-OS

Element %$VDC #%$ %$VRF #%$ description

Level 0 emergency 1 alert 2 critical 3 notification

is a code that uniquely identifies the system message.

Representation [dec] [hex] [char] [chars]

Capturing System Messages and History

Saving the System Messages Log

Logging System Messages to a Syslog Server

Chapter 1 Capturing System Messages and History

Introduction to System Messages for Cisco NX-OS

Upgrading of accounting log failed.

Aaa daemon is exiting.

Accounting Message No action is required.

AAM Process assertion failed in File:[chars], at line:[dec] No action is required.

Max flow reached in current interval: [chars] No action is required.

Error Message Explanation

Threshold Reached for Flow: [chars] No action is required.

Flow info in current alert interval: [chars] No action is required.

Error Message Explanation

New Acllog Flow: [chars] No action is required.

The PPF commit failed No action is required.

successfully because errdisable is disallowed

ACLMGR-2-EXITING: Exit reason: [chars]

Error Message Explanation

ACLMGR-2-INITFAIL: ACLMGR Service Init failed: [chars]

Error Message Explanation

ACLMGR-2-MALLOC_ERROR: Size [dec] bytes

The ACLMGR service could not allocate memory.

Error Message Explanation

ACLMGR-2-PSS_ERROR: [chars]: PSS ret. val=[dec]

ACL PPF database lock acquire/release related message. No action is required.

Error Message Explanation

ACLMGR-3-ACLMGR_PPF_ERROR: PPF error: [chars]

The PPF generated error No action is required.

Error Message Explanation