- U2RIB Messages
- UDLD Messages
- UFDM Messages
- USBHSD Messages
- VAJRA_USD Messages
- VAL_USD Messages
- VDC_MGR Messages
- VEC Messages
- VEDB_MGR Messages
- VES Messages
- VFC Messages
- VIPER_CMN_USD Messages
- VIPER_ICB_USD Messages
- VIPER_MAC_USD Messages
- VIPER_XBAR_USD Messages
- VIP_FWD Messages
- VIP_ILK Messages
- VLAN_MGR Messages
- VMAN Messages
- VMM Messages
- VNI Messages
- VNTAGC Messages
- VNTAG_MGR Messages
- VPC Messages
- VPM Messages
- VRRP-CFG Messages
- VRRP-ENG Messages
- VSAN Messages
- VSC Messages
- VSD Messages
- VSHA Messages
- VSHD Messages
- VTP Messages
- WWN Messages
- X2_USD Messages
- X2_USD Messages
- XBAR_CLIENT Messages
- XBAR_DRIVER_USD Messages
- XBAR Messages
- XCVR_USD Messages
- XCVR Messages
- XMLMA Messages
- XMLSA Messages
- ZBM Messages
- ZONE Messages
U to Z
This chapter includes system messages for the Cisco NX-OS MDS 9000 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 message is followed by an explanation and a recommended action.
U2RIB Messages
U2RIB-2
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 No action is required.
Message U2RIB-2-U2RIB_INIT: U2RIB initialization of [chars] [chars]Explanation U2RIB initialization 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.
U2RIB-3
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 DEFFIB library.
U2RIB-5
Message U2RIB-5-U2RIB_DISABLED: U2RIB DisabledExplanation U2RIB Service Disabled
Recommended Action No action is required.
Message U2RIB-5-U2RIB_ENABLED: U2RIB EnabledU2RIB-6
Message U2RIB-6-STATE_CREATED: Internal state created [chars]Explanation U2RIB has created its internal state stateless/stateful [chars].
UDLD Messages
UDLD-3
Message UDLD-3-IDB_ERROR: UDLD error handling [chars] interface: [chars]Explanation A software error occurred in UDLD processing associated with a specific interface.
Recommended Action LOG_STD_SH_TECH_ACTION
Message UDLD-3-MSG_SEND_FAILURE: failed to send [chars] to sap [dec]: [chars]Explanation Failed to send a message
Recommended Action LOG_STD_SH_TECH_ACTION
Message UDLD-3-UDLD_INTERNAL_ERROR: UDLD internal error: [chars]Explanation A software sanity check failed in the course of UDLD processing.
Recommended Action LOG_STD_SH_TECH_ACTION
Message UDLD-3-UDLD_INTERNAL_IF_ERROR: UDLD internal error, interface [chars]: [chars]Explanation A software sanity check failed in the course of UDLD processing.
UDLD-4
Message UDLD-4-UDLD_GWRAP_COUNT: UDLD gwrap count is %lu, please log a 'show tech udld' for detail info.Explanation UDLD gwrap count reached high level, show tech udld is needed to debug it.
Recommended Action LOG_STD_SH_TECH_ACTION
Message UDLD-4-UDLD_NEIGHBOR_MISMATCH: UDLD neighbor mismatch detected, exp: [chars], rec [chars]. Please collect debug info using: http://zed.cisco.com/confluence/display/KGP/UDLD+debugExplanation An interface will be disabled because UDLD protocol detected a neighbor 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
Message UDLD-4-UDLD_PORT_DISABLED: Interface [chars], link error detected: [chars]. Please collect debug info using: http://zed.cisco.com/confluence/display/KGP/UDLD+debugExplanation 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
Message UDLD-4-UDLD_PORT_RESET: UDLD reset interface [chars]Explanation A port which had been disabled for UDLD has been reset.
UDLD-5
Message UDLD-5-UDLD_AGGRESSIVE: UDLD AggressiveExplanation UDLD Service Aggressive
Recommended Action No action is required.
Message UDLD-5-UDLD_DISABLED: UDLD DisabledExplanation UDLD Service Disabled
Recommended Action No action is required.
Message UDLD-5-UDLD_ENABLED: UDLD EnabledUFDM Messages
UFDM-2
Message UFDM-2-DNLD_TIMEDOUT: Download timer expired: [chars]Explanation UFDM download timer expired. Collect show tech-support forwarding l3 unicast for further analysis.
Recommended Action No action is required.
Message UFDM-2-FIB_ROUTE_UPDATE_ERR: Route update error from slot [dec] FIBExplanation FIB returned route update error. Collect show tech-support forwarding l3 unicast for further analysis.
Recommended Action No action is required.
Message UFDM-2-INTERNAL_ERROR: Internal error: [chars], collect output of show tech-support forwarding l3 unicast... commandExplanation UFDM hit a internal error. Collect show tech-support forwarding l3 unicast for further analysis.
USBHSD Messages
USBHSD-1
Message USBHSD-1-MANUAL_FORMAT: logflash needs to be formattedExplanation Logflash is not accessible; use format logflash: to format it
USBHSD-2
Message USBHSD-2-AUTO_FORMAT: logflash auto-format [chars]Explanation Logflash auto-format event
Recommended Action No action is required.
Message USBHSD-2-DISK_BUSY_FAILED: Cannot unmount [chars],Explanation The specified disk interface is in use it can not be un-mounted, The user may experience file system corruption
Recommended Action Make sure slot0 is not being used either by mounting or by any command and re-insert the disk again
Message USBHSD-2-DISK_FSCK_FAIL: file system check returned error on slot [dec]Explanation Flash file system may be corrupted, the flash was taken while it was being accessed
Recommended Action Reform at the external flash
Message USBHSD-2-DISK_MOUNT_FAIL: disk mount unsuccessful on [chars]Explanation Unknown flash filesystem or not cleanly un-mounted
Recommended Action Use vfat flash only and make sure external slot is not being accessed then re-insert flash
Message USBHSD-2-DISK_RESCAN_FAIL: disk rescan unsuccessful on [chars]Explanation Flash filesystem was not cleanly un-mounted
Recommended Action Make sure external slot is not being accessed and re-inset the flash
Message USBHSD-2-DISK_UMOUNT_FAIL: disk unmount unsuccessful for [chars]Explanation Flash filesystem is busy the system could not un-mount it
Recommended Action Make sure external slot is not being accessed and re-inset the flash
Message USBHSD-2-FORK: fork failed ([chars] process)Explanation The flash daemon failed to fork
Recommended Action No action is required.
Message USBHSD-2-INTERNAL_ERROR: Internal Error [dec]Explanation The flash daemon interface returns error
Recommended Action Restart the IDEHSD deamon
Message USBHSD-2-MOUNT: [chars] onlineExplanation Flash daemon mounting slot
Recommended Action No action is required.
Message USBHSD-2-UMOUNT: [chars] offlineExplanation Flash daemon un-mounting slot
Recommended Action No action is required.
Message USBHSD-2-USB_SWAP: USB insertion or removal detectedUSBHSD-3
Message USBHSD-3-DEVICEOPEN_FAILED: device open failed. Component [chars]Explanation The flash daemon device open failed The failure is due to the sub-component [chars]
USBHSD-5
Message USBHSD-5-DISK_SWAP: [chars] [chars]USBHSD-6
Message USBHSD-6-DISK_BUSY: trying to unmount disk [chars]Explanation Flash daemon trying to un-mount busy slot
Recommended Action No action is required.
Message USBHSD-6-DISK_EVENT: slot [dec] [chars]Explanation Flash daemon found a disk hotswap handler event
Recommended Action No action is required.
Message USBHSD-6-IOCTL: ioctl: [chars] returns [dec]Explanation Flash daemon trying to un-mount busy slot
Recommended Action No action is required.
Message USBHSD-6-STARTING: deamon startedExplanation The compact flash swap daemon successfully started
Recommended Action No action is required.
Message USBHSD-6-USBHSD_INFO: [chars]USBHSD-7
Message USBHSD-7-USBHSD_TRACE: [chars]() [chars]:[dec] disk=[dec]USDBA-2
Message USDBA-2-USDBA_CRC_ERR: USDBA received packet(s) with CRC errorExplanation USDBA received packet(s) with CRC error on downlink(s)
Recommended Action use another optical cable and transceivers. If the problem still persists, change the peer ports, such as the remote port to another or the local port to another. Run the commands diagnostic start module <mod> test all and show diagnostic result module <mod> test all detail. The result will display the information about the failures in HW, if any.
VAJRA_USD Messages
VAJRA_USD-6
Message VAJRA_USD-6-VAJRA_DEBUG_MSG: [chars]VAL_USD Messages
VAL_USD-6
Message VAL_USD-6-VAL_DEBUG_MSG: [chars]VDC_MGR Messages
VDC_MGR-2
Message VDC_MGR-2-VDC_CRITICAL: vdc_mgr has hit a critical error: [chars]Explanation Vdc_mgr has hit a critical error
Recommended Action A critical error has been hit within vdc_mgr. Please check show vdc to determine the state of the vdcs
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 expireExplanation VDC license is close to expire
Recommended Action Please contact your sales representative to obtain a license
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 recommended
Message VDC_MGR-2-VDC_OFFLINE: vdc [dec] is now offlineExplanation The vdc has been shut down. Either it has been deleted or has just completed ungraceful cleanup
Recommended Action If the vdc was deleted, no action is necessary. Otherwise vdc_mgr may attempt to recreate it according to the ha-policy that has been set
Message VDC_MGR-2-VDC_ONLINE: vdc [dec] has come onlineExplanation Vdc_mgr has finished creating a vdc and it is ready to use
Recommended Action No action is required.
Message VDC_MGR-2-VDC_UNALLOCATED: Module [dec] is unsupported by the current vdc and some of its ports have been placed in the unallocated pool.Explanation The module is of a type unsupported by the current vdc. You can see port membership by 'show vdc membership' and check the current vdc's configuration through 'show vdc'
Recommended Action Allocate interfaces to a vdc that supports this module type or change the current vdc to support this module type via the 'limit-resource module-type' command
Message VDC_MGR-2-VDC_UNGRACEFUL: vdc_mgr: Ungraceful cleanup request received for vdc [dec], restart count for this vdc is [dec] restarts within the last 5 minutesExplanation 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
Message VDC_MGR-3-VDC_ERROR: vdc_mgr: [chars]Explanation Vdc_mgr has received bad data but will try to continue
Recommended Action Vdc_mgr will attempt to correct the error at hand
VDC_MGR-5
Message VDC_MGR-5-VDC_FEATURESET_ALLOW: vdc_mgr: Feature-set [chars] can now be used in this vdcExplanation Allowed feature-set config has changed
Recommended Action No action is required.
Message VDC_MGR-5-VDC_FEATURESET_DISALLOW: vdc_mgr: Feature-set [chars] is now disallowed in this vdcExplanation Allowed feature-set config has changed
Recommended Action No action is required.
Message VDC_MGR-5-VDC_HOSTNAME_CHANGE: vdc [dec] hostname changed to [chars]Explanation Host name for a vdc has changed.
Recommended Action No action is required.
Message VDC_MGR-5-VDC_MEMBERSHIP_ADD: vdc_mgr: Interface [chars] has been added to this vdcExplanation A new interface has been added to this vdc
Recommended Action No action is required.
Message VDC_MGR-5-VDC_MEMBERSHIP_DELETE: vdc_mgr: Interface [chars] has been removed from this vdcExplanation A new interface has been removed from this vdc
Recommended Action No action is required.
Message VDC_MGR-5-VDC_MODULETYPE: vdc_mgr: Module type changed to [chars]Explanation This vdc has been changed to support only the type of modules listed
Recommended Action No action is required.
Message VDC_MGR-5-VDC_STATE_CHANGE: vdc [dec] state changed to [chars]Explanation A vdc state change has happened. This is most likely due to a configuration change.
Recommended Action No action is required.
Message VDC_MGR-5-VDC_SWMODULETYPE: vdc_mgr: System Module type changed to [chars]Explanation This switch has been changed to support only the type of modules listed
VEC Messages
VEC-SLOT#-3
Message VEC-SLOT#-3-LOG_DPP_EXCEPTION: DPP Exception DPP [dec]Explanation No action is required.
Message VEC-SLOT#-3-LOG_GUID_MISMATCH: GUID Mismatch DPP [dec] PWWN [chars] lun [chars] Expected [chars] Read [chars]Explanation The disk GUID verification performed by the DPP failed. Access to the disk is denied.
VEC-SLOT#-4
Message VEC-SLOT#-4-LOG_DPP_REBOOTED: DPP [dec] RebootedVEC-SLOT#-5
Message VEC-SLOT#-5-LOG_ERR_VEC_DISK: SCSI STATUS([hex]) [chars] SENSE_KEY([hex]) [chars] ASC([hex]) ASCQ([hex]) [chars]Explanation No action is required.
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 occurred
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
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 Guide ID FSM which should not have occurred
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
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 respondingExplanation The Host HBA is logged out from the VEP as it is not responding to ADISCs initiated from the VEP
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
Message VEC-SLOT#-5-LOG_ERR_VEC_HOST: Host VSAN :[dec] Host pWWN :[chars] access denied to VEP pWWN :[chars] due to licensingExplanation The Host HBA is denied access to the VEP due to licensing
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
Message VEC-SLOT#-5-LOG_ERR_VEC_VEP_ILC_LIMIT: VEP [VSAN:[dec] pWWN :[chars]] could not be created. Reason: ILC VEP limit [dec] reachedExplanation The VEP could not be created as the per ILC limit of VEPs has been reached
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
Message VEC-SLOT#-5-LOG_NOTICE_VEC_SLEEP_THRESH: VEC not scheduled for [dec] secondsExplanation The VEC process sleep threshold was exceeded which should not have occurred. Recovery will be performed if appropriate.
Recommended Action No action is required.
Message VEC-SLOT#-5-LOG_NOTICE_VEC_WORK_THRESH: VEC did not yeild the cpu for [dec] secondsExplanation The VEC process work threshold was exceeded which should not have occurred. Recovery will be performed if appropriate.
VEDB_MGR Messages
VEDB_MGR-2
Message VEDB_MGR-2-MALLOC_ERROR: Size [dec] bytesExplanation The VEDB library could not allocate memory.
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.
VEDB_MGR-6
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 No action is required.
Message VEDB_MGR-6-SERVICE_UP: Initialized [chars]Explanation The VEDB library is up and ready to accept client requests The service was initialized in [char] mode.
VES Messages
VES-SLOT#-4
Message VES-SLOT#-4-LOG_WARNING_VES_CONFIG_TOO_BIG: Volume [chars] configuration too large to virtualizeExplanation The VES maximum volume configuration was exceeded. Volume will be virtualize by the cop.
VES-SLOT#-5
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 occurred
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
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 occurred
Recommended Action No action is required.
Message VES-SLOT#-5-LOG_NOTICE_VES_SLEEP_THRESH: VES not scheduled for [dec] secondsExplanation The VES process sleep threshold was exceeded which should not have occurred. Recovery will be performed if appropriate.
Recommended Action No action is required.
Message VES-SLOT#-5-LOG_NOTICE_VES_WORK_THRESH: VES did not yeild the cpu for [dec] secondsExplanation The VES process work threshold was exceeded which should not have occurred. Recovery will be performed if appropriate.
VFC Messages
VFC-3
Message VFC-3-VFC_MEM_ERROR: Memory consistency problemExplanation Miscellaneous target error
Recommended Action No action is required.
Message VFC-3-VFC_TGT_ERROR: Target error: [chars] 0x%llxVFC-6
Message VFC-6-STARTING: deamon startedVIPER_CMN_USD Messages
VIPER_CMN_USD-6
Message VIPER_CMN_USD-6-VIPCMN_DEBUG_MSG: [chars]VIPER_ICB_USD Messages
VIPER_ICB_USD-2
Message VIPER_ICB_USD-2-VIP_ICB_TEST: [chars]VIPER_ICB_USD-6
Message VIPER_ICB_USD-6-VIP_ICB_DEBUG_MSG: [chars]VIPER_MAC_USD Messages
VIPER_MAC_USD-6
Message VIPER_MAC_USD-6-VIPER_MAC_DEBUG_MSG: [chars]VIPER_XBAR_USD Messages
VIPER_XBAR_USD-6
Message VIPER_XBAR_USD-6-VIPER_XBAR_DEBUG_MSG: [chars]VIP_FWD Messages
VIP_FWD-6
Message VIP_FWD-6-VIP_FWD_DEBUG_MSG: [chars]VIP_ILK Messages
VIP_ILK-6
Message VIP_ILK-6-VIP_ILK_DEBUG_MSG: [chars]VLAN_MGR Messages
VLAN_MGR-2
Message VLAN_MGR-2-CRITICAL_MSG: [chars]VLAN_MGR-3
Message VLAN_MGR-3-ERROR_MSG: [chars]VLAN_MGR-4
Message VLAN_MGR-4-WARN_MSG: [chars]VLAN_MGR-5
Message VLAN_MGR-5-NOTIF_MSG: [chars]Explanation VLAN Manager Notification Message
Recommended Action No action is required.
Message VLAN_MGR-5-RESERVED_VLAN_RANGE_CHANGED: New Reserved VLAN Range Configured From VLAN [dec] to VLAN [dec]Explanation VLAN Manager Reserved VLAN Reconfiguration Message
VLAN_MGR-6
Message VLAN_MGR-6-INFO_MSG: [chars]Recommended Action No action is required.
Message VLAN_MGR-6-VLAN_CREATED: VLAN [dec], createdRecommended Action No action is required.
Message VLAN_MGR-6-VLAN_MGR_STATEFULL_RESTART: VLAN Manager statefull restartExplanation VLAN Manager stateful restart
Recommended Action No action is required.
Message VLAN_MGR-6-VLAN_MGR_STATELESS_RESTART: VLAN Manager stateless restartExplanation VLAN Manager stateless restart
Recommended Action No action is required.
Message VLAN_MGR-6-VLAN_OPER_STATUS_CHG: VLAN [dec], status changed to [chars]VMAN Messages
VMAN-2
Message VMAN-2-ACTIVATION_STATE: [chars] [chars]'[chars][chars]'Explanation The activation state of the named virtual service has changed as notified by virt-manager.
Recommended Action In the failed case, check virt-managers logs for the cause of the failure. In the successful case, this notification can be ignored.'
Message VMAN-2-ALLOC_VIRT_INST_RCS: Virtual Service [chars]Explanation A memory allocation request failed to allocate a data structure required to activate the virtual service.
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the Virtual-manager logs and scan them for the cause.
Message VMAN-2-COMMIT_VIRT_INST_RCS: Virtual Service [chars]Explanation The request to commit the resources required by the named virtual service failed.
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-CPUSHARES_LIMIT: Virtual Service [chars]Explanation The virtual service machine definition file is requesting more CPU shares than the system has available for virtual services.
Recommended Action Deactivate any other virtual services to free up CPU share resources and activate this virtual service. If that does not address the problem, then enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-CPUTUNES_INTERNAL_ERROR: Virtual Service [chars]Explanation virt-manager and its associated infrastructure experienced an internal error.
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-CPUTUNES_SHARES_LIMIT: Virtual Service [chars]Explanation The virtual service machine definition file is requesting more CPU shares than the system has available for virtual services.
Recommended Action Deactivate any other virtual services to free up CPU share resources and activate this virtual service. If that does not address the problem, then enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-CREATE_VIRT_INST_ENTRY: Virtual Service [chars]Explanation The request to create a DB entry for the named virtual service failed.
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the Virtual-manager logs and scan them for the cause.
Message VMAN-2-DEFER_VIRT_INST_PROC: Virtual Service [chars]Explanation The final activation processing failed to successfully defer.
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-DISK_IMAGE_PATH: Virtual Service [chars]Explanation The virtual service machine definition file contains an invalid disk image path for one of the disk devices. This may be a Hard disk, CDROM or USB storage device.
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-FIND_VIRT_INST_ENTRY: Failed to find virtual service with id [dec] in the Virt-manager DBExplanation The virtual service with the ID named could not be located in the virt-manager DB.
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-GENERAL_FAILURE: Virtual Service [chars]Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
Message VMAN-2-HA_SYNC_ERR: [chars] [chars]' [chars]'Explanation The ha-sync persistent storage disk for the virtual service cannot be watched for sync to standby RP.
Recommended Action Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-INCONSISTENT_CPUTUNES_CONFIG: Virtual Service [chars]Explanation The virtual service machine definition file is requesting invalid CPU tunes parameter.
Recommended Action Use a different valid machine definition file for the virtual service. If the problem persists, then enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-INCONSISTENT_MEM_CONFIG: Virtual Service [chars]Explanation The virtual service machine definition file is inconsistent in the specification of required memory via the <memory>
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-INSERT_VIRT_INST_ENTRY: Virtual Service [chars]Explanation Inserting the named virtual service into the virtual service DB tracked by virt-manager failed.
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-INSTALL_FAILURE: Virtual Service [chars]Explanation The installation of the virtual service failed.
Recommended Action Enable the virt-manager trace logs and repeat the installation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-INSTALL_MEDIA_RETRY: VMAN, VM install media still unavailable.[chars]Explanation The install media was not detected. Waiting for udev to complete install media (hard-disk) detection.
Recommended Action After VMAN exceeds the maximum retry limit, verify if install media (hard-disk) is accessible and retry the installation again.
Message VMAN-2-INSTALL_STATE: Successfully [chars] [chars]''Explanation The installation state of the named virtual service has changed as notified by virt-manager.
Recommended Action In the failed case, check virt-managers logs for the cause of the failure. In the successful case, this notification can be ignored.
Message VMAN-2-INVALID_ACT_MSG: Virtual Service [chars]Explanation The virtual service activate message was received, however, the data it contained could not be interpreted
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-INVALID_DEACT_MSG: Failed to process virtual service deactivate messageExplanation The virtual service deactivate message was received, however, the data it contained could not be interpreted
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-INVALID_PACKAGE: Virtual Service [chars]Explanation The package definition file for the named virtual service has failed to be validated and the virtual service will not run
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause. The most likely cause would be that the package file has been corrupted during file transfer. The suggested action would be to redo the file transfer.
Message VMAN-2-INVALID_UNPROV_MSG: Failed to process virtual service unprovision messageExplanation The virtual service un-provision message was received, however, the data it contained could not be interpreted
Recommended Action Enable the Virt-manager trace logs and repeat the activation followed by deactivation and then un-provision of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-MACHINE_TYPE_NOT_SUPPORTED: Virtual Service [chars]Explanation The virtual service cannot be activated as the machine type specified is not supported; action Enable the support for the machine type and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-MACH_PARSE_FAILURE: Virtual Service [chars]Explanation The named virtual service has an invalid parameter specified in the.xml file inside the.ova package
Recommended Action Fix the.xml file inside the.ova package to have valid values. Then retry installing and activating it
Message VMAN-2-MEMORY_LIMIT_WARN: Virtual service ([chars])[chars] defines [dec] MB of Memory exceeding the maximum [dec] MB.Explanation The virtual service machine definition file is requesting more memory for the specified profile, than the system has available for virtual services.
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-MEMORY_LIMIT: Virtual Service [chars]Explanation The virtual service machine definition file is requesting more memory than the system has available for virtual services.
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-MORETHANONE_CPUTUNES_CONFIG: Virtual Service [chars]Explanation The virtual service machine definition file is requesting more than one CPU tunes parameter.
Recommended Action Use a different valid machine definition file for the virtual service. If the problem persists, then enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-NETWORK_CONFIG_ERROR: Virtual Service [chars]Explanation A network configuration error has been detected for the named virtual service.
Recommended Action No action is required
Message VMAN-2-PROCESS_PKG_DEF: Virtual Service [chars]Explanation The virtual service package for the named virtual service has failed to be validated and the virtual service will not run.
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-PROC_INT_LIST: Virtual Service [chars]Explanation The interface list embedded in the activate request for the named virtual service could not be processed.
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-REMOVE_VIRT_INST_ENTRY: Virtual Service [chars]Explanation Removing the named virtual service from the virtual service DB tracked by virt-manager failed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-SET_VTX_ROMVAR_SPACE: Failed to set ROM monitor variable ENABLE_VTX: No space in tableExplanation Failed to set ENABLE_VTX ROM monitor variable due to no space in Monitor Variable Table.
Recommended Action Verify number of entries in Monitor Variable Table.
Message VMAN-2-SET_VTX_ROMVAR_STRING: Failed to set ROM monitor variable ENABLE_VTX: Invalid string format: [chars]Explanation Failed to set ENABLE_VTX ROM monitor variable due to invalid string format.
Recommended Action Verify format of string from error message.
Message VMAN-2-START_FAILED: Virtual Device:[chars]Explanation The named virtual service failed to start.
Recommended Action Enable the virt-manager trace logs and repeat the activation of the virtual service. Collect the virt-manager logs and scan them for the cause.
Message VMAN-2-VCPU_INVALID: Virtual Service [chars]Explanation The virtual service machine definition file is requesting invalid VCPU value.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Message VMAN-2-VCPU_LIMIT: Virtual Service [chars]Explanation The virtual service machine definition file is requesting more VCPUs than the system has reserved for virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Message VMAN-2-VIRT_INST_DISK: Virtual Service [chars]Explanation The virtual service requires Disk Storage in excess of the Free Disk Storage available to virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Message VMAN-2-VIRT_INST_INTERFACE: Virtual Service [chars]Explanation The number of configured virtual port group interfaces must match the number of Ethernet Network Interfaces defined in the machine definition file
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Message VMAN-2-VIRT_INST_MEMORY: Virtual Service [chars]Explanation The virtual service requires physical memory in excess of the free memory available to virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Message VMAN-2-VIRT_INST_MGMT_INTERFACE: Virtual service [chars] has no management interface defined but it is configured in CLI.Explanation A management interface is configured but none is defined.
Recommended Action Deactivate the virtual service, remove the management interface configuration CLI, and reactivate the virtual-service.
Message VMAN-2-VIRT_INST_STATE: Virtual Service [chars]Explanation The named virtual service has failed. It is no longer running either because the guest OS has failed, the guest OS has shut down the machine or the emulator has failed.
Recommended Action An attempt at restarting the virtual service can be made from the IOS configuration by doing a no activate/activate. For debugging collect the Virt-manager logs and scan them for the cause.
VMAN-3
Message VMAN-3-PSS_ERR: Purpose: [chars], URI: [chars], errcode: [dec]Explanation Persistent Storage Service handling error
Recommended Action Collect the Virt-manager logs and scan them for the cause.
Message VMAN-3-PSS_SNAPSHOT_ERR: Source URI: [chars], Destination URI: [chars], errcode: [dec]Explanation Persistent Storage Service snapshot error
Recommended Action Collect the Virt-manager logs and scan them for the cause.
Message VMAN-3-SDWRAP_ERR: Description: [chars], errcode: [dec]Explanation Debug infrastructure error
Recommended Action Collect the Virt-manager logs and scan them for the cause.
VMAN-4
Message VMAN-4-WATCHDOG_TIMER: [chars] [chars]'[chars][chars]'Explanation The watchdog timer configured for the named virtual service has expired.
Recommended Action Check any logs produced by the virtual service to determine the cause.
VMAN-5
Message VMAN-5-AUX: Virtual Service [chars]Explanation The AUX login to a virtual service may allow the user access to system functions that may not have been tested or may interact with the system in unintended ways. Use with caution.
Recommended Action No action is required
Message VMAN-5-UNSIGNED_PACKAGE: Unsigned software package [chars] loaded for service container [chars].Explanation A software package without a code signing certificate has been loaded.
Recommended Action Take note of the service container and software package. Verify the software package is expected to be unsigned and has the appropriate contents. Un-install the package if unsure of the package origins.
Message VMAN-5-VIRT_INST: LOG FROM VIRTUAL SERVICE [chars]: [chars]Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
VMM Messages
VMM-2
Message VMM-2-VMM_DBG_SEQDELAY_LOG: VDC[dec]: Sending [chars] mts([chars]) request to service [dec] for slot [dec].Explanation VMM sent request for the sap mentioned
Recommended Action No action is required.
Message VMM-2-VMM_SERVICE_ERR: VDC[dec]: Service SAP [chars] for slot [chars] returned error [hex] ([chars]) in [chars] sequenceExplanation Service returned error in the specified sequence
Recommended Action No action is required.
Message VMM-2-VMM_TIMEOUT: VDC[dec]: Service SAP [chars] for slot [chars] timed out in [chars] sequenceExplanation Service did not respond in the specified sequence
VNI Messages
VNI-2
Message VNI-2-ALLOC_MEMORY: Memory allocation failedExplanation The service failed to allocate a block of dynamic memory.
VNI-3
Message VNI-3-INIT_FAILED: Initialization failed. Component [chars]Explanation The service failed to start. The failure occurred while initializing the component [chars].
Recommended Action Show processes to check the status of the other processes, debug the specified component.
VNI-6
Message VNI-6-INTERFACE_EVENT: VSAN interface [chars] [chars]Explanation The specified VSAN Interface has been successfully [chars].
Recommended Action No action is required.
Message VNI-6-STARTING: Virtual Network Interface Manager startedExplanation The service has successfully started.
Recommended Action No action is required.
Message VNI-6-VSAN_DELETED: VSAN [dec] has been deletedExplanation The specified VSAN has been deleted. The service will delete all the configuration on that VSAN.
VNTAGC Messages
VNTAGC-5
Message VNTAGC-5-VNTAGC_GENERIC_SYSLOG: [chars]Explanation This syslog is used for the purpose of internal debugging of VNTAG client.
Recommended Action If this log is seen, then the syslog level might be set to notifications (5). Please modify syslog level accordingly or ignore this syslog, as no action is required for the same.
VNTAG_MGR Messages
VNTAG_MGR-2
Message VNTAG_MGR-2-MCAST_DVIF_ALLOC_FAILURE: DVIF allocation failure during MCAST group creation. TCB RID: [hex]. MCAST LTL: [hex]. Reason: [chars].Explanation MCAST DVIF allocation for MCAST group.
Recommended Action No action is required.
Message VNTAG_MGR-2-VLAN_DVIF_ALLOC_FAILURE: DVIF allocation failure for VLANs [chars]. Reason: [chars].Explanation Flood DVIF allocation failure for VLANs.
Recommended Action No action is required.
Message VNTAG_MGR-2-VNTAG_MGR_OMF_DVIF_ALLOC_FAIL: OMF DVIF allocation failed (DVIF exhaustion).To enable OMF you need to shut down a VLAN/MCAST groupExplanation OMF DVIF reservation failed (dvif exhaustion). To enable OMF a VLAN or MCAST group needs to be disabled to get a free dvif.
Recommended Action No action is required.
Message VNTAG_MGR-2-VNTAG_SEQ_ERROR: [chars]Explanation Some step in an event sequence has failed
Recommended Action No action is required.
Message VNTAG_MGR-2-VNTAG_SEQ_TIMEOUT: [chars]VNTAG_MGR-4
Message VNTAG_MGR-4-VNTAG_MIXED_FPC_HIFPC_PAYLOAD: [chars]Explanation This not allowed from PIXM itself, but could happen due to some incorrect MBL batching.
Recommended Action No action is required.
Message VNTAG_MGR-4-VNTAG_PRUNED_L3_PORT: Port [hex] will not be added to FEX forwarding table as it is a L3 port.Explanation To avoid sending multi destination traffic to L3 ports we do not add them to FEX forwarding table.
VNTAG_MGR-5
Message VNTAG_MGR-5-VNTAG_MGR_DISABLED: VNTag Manager DisabledExplanation VNTag Manager Service Disabled
Recommended Action No action is required.
Message VNTAG_MGR-5-VNTAG_MGR_ENABLED: VNTag Manager EnabledExplanation VNTag Manager Service Enabled
Recommended Action No action is required.
Message VNTAG_MGR-5-VNTAG_MGR_GENERIC_SYSLOG: [chars]VPC Messages
VPC-2
Message VPC-2-PEER_KEEP_ALIVE_RECV_FAIL: In domain [dec], VPC peer keep-alive receive has failedExplanation Peer keep-alive receive failed
Recommended Action No action is required.
Message VPC-2-PEER_KEEP_ALIVE_SEND_FAIL: In domain [dec], VPC peer keep-alive send has failedExplanation Peer keep-alive send failed
Recommended Action No action is required.
Message VPC-2-PEER_VPC_RESP_TIMEDOUT: Failed to receive response from peer for vPC: [dec]Explanation VPC bringup failed
Recommended Action No action is required.
Message VPC-2-TRACK_INTFS_DOWN: In domain [dec], vPC tracked interfaces down, suspending all vPCs and keep-aliveExplanation VPC tracked object down
Recommended Action No action is required.
Message VPC-2-VPC_ADD_L3_BKUP_VLAN_TO_PEER_GW_EXCLUDE_LIST: Exclude L3 backup routing VLAN from vpc peer-gateway config.Explanation Triggered when peer-link is F1 and peer-gateway is configured without exclude-vlan list.
Recommended Action No action is required.
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 configuredExplanation VPC+ Failed to bringup peer-link - switch-ID not configured
Recommended Action No action is required.
Message VPC-2-VPC_ES_FAILED_LID_ALLOC: Failed to negotiate common LID between vPC peers.Explanation Failed to find common lid.
Recommended Action No action is required.
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.
Recommended Action No action is required.
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.
Recommended Action No action is required.
Message VPC-2-ASIC_FAILURE_NOTIF: ASIC failure received from nohms in domain [dec]Explanation ASIC failure notification: From the code, the switch detects an ASIC error and tries to recover the error by suspend vPC Keepalive, suspend vPCs and flap peer link.
Recommended Action Locate the module from the error message and replace the module. If the problem happens to multiple linecard or chassis, please contact TAC.
Message VPC-2-VPC_GRACEFUL_SUSP_ALL_VPC: Operational graceful type-1 check configuration changed, reinstating all vPCsExplanation Graceful configuration change, reinit vPCs
Recommended Action No action is required.
Message VPC-2-VPC_ISSU_END: Peer vPC switch ISSU end, unlocking configurationExplanation Peer vPC switch issu end
Recommended Action No action is required.
Message VPC-2-VPC_ISSU_START: Peer vPC switch ISSU start, locking configurationExplanation Peer vPC switch issu start
Recommended Action No action is required.
Message VPC-2-VPC_LC_FAIL: LC [dec] does not support required hardware for vPC; run show vdc membership status' for port status'Explanation LC insertion failed
Recommended Action No action is required.
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.
Recommended Action No action is required.
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 portExplanation VPC+ Failed to bringup Peer-link - not in Fabric Path mode
Recommended Action No action is required.
Message VPC-2-VPC_PSS_ERROR: [chars], 0x([hex]) present in VPC DB but not is IM DBExplanation Triggered when vPC DB and IM SDB are inconsistent
Recommended Action No action is required.
Message VPC-2-VPC_SUSP_ALL_VPC: Peer-link going down, suspending all vPCs on secondaryExplanation Peer link down suspend vPCs
Recommended Action No action is required.
Message VPC-2-VPC_SVI_EXCLUDE: vPC [dec] has up vlans [chars] which are excluded from suspension on dual-activeExplanation VPC track object un-configured
Recommended Action No action is required.
Message VPC-2-VPC_SDB_UPD_FAIL: Failed to update shared database. De-config and config vPC [dec] to be consistent.VPC-3
Message VPC-3-GLOBAL_CONSISTENCY_FAILED: In domain [dec], global configuration is not consistent ([chars])Explanation Global compact-check failed
Recommended Action No action is required.
Message VPC-3-INTF_CONSISTENCY_FAILED: In domain [dec], VPC [dec] configuration is not consistent ([chars])Explanation MCEC compact-check failed
Recommended Action No action is required.
Message VPC-3-PEER_UNREACHABLE: Remote Switch UnreachableRecommended Action No action is required.
Message VPC-3-PEER_VPC_BRINGUP_FAILED: Peer vPC [dec] bringup failed ([chars])Explanation Peer vPC bringup failed
Recommended Action No action is required.
Message VPC-3-VPCM_ASSERTION_FAILED: [chars]Explanation VPCM has hit an assert condition at file [chars]
Recommended Action No action is required.
Message VPC-3-VPCM_INIT_FAIL: vPC Manager Initialization Failed ([chars])Explanation VPCM Initialization failed. due to [chars]
Recommended Action No action is required.
Message VPC-3-VPCM_INTERNAL_ERR: [chars]Explanation VPCM encountered an internal error due to [chars]
Recommended Action No action is required.
Message VPC-3-VPCM_MTS_ERR: [chars]Explanation VPCM encountered an MTS error due to [chars]
Recommended Action No action is required.
Message VPC-3-VPC_BRINGUP_FAILED: vPC [dec] bringup failed ([chars])Explanation VPC bringup failed
Recommended Action No action is required.
Message VPC-3-VPC_PEER_LINK_BRINGUP_FAILED: vPC peer-link bringup failed ([chars])Explanation VPC Peer-link bringup failed
Recommended Action No action is required.
Message VPC-3-VPC_PEER_LINK_DOWN: VPC Peer-link is downVPC-4
Message VPC-4-FTAG_UPD_PORT_DWN: Warning: receive FTAG update while port is going downExplanation Receive FTAG update while port is going down
Recommended Action No action is required.
Message VPC-4-OOB_DWN_BUT_WAS_ALIVE: Warning: Bring up peer-link when peer keep-alive is downExplanation Try to bring up MCT when OOB fails.
Recommended Action No action is required.
Message VPC-4-PEER_VPC_DELETED: Peer vPC [dec] deletedExplanation Peer vPC configuration deleted
Recommended Action No action is required.
Message VPC-4-VPC_CONSISTENCY_NEW_VLAN_FAIL: Global Consistency check for vPC failed for new vlansExplanation Global Consistency check for vPC failed for new vlans
Recommended Action No action is required.
Message VPC-4-VPC_DELETED: vPC [dec] is deletedExplanation VPC configuration deleted
Recommended Action No action is required.
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
Recommended Action No action is required.
Message VPC-4-VPC_LC_UPG_OVER_DELIVERY_FAIL: Failed to deliver LC upgrade to vPC peerExplanation Failed to deliver LC upgrade to peer
Recommended Action No action is required.
Message VPC-4-VPC_PEER_LINK_DELETED: vPC Peer-link deleted. This will bring down all vPC interfacesExplanation VPC Peer-link configuration removed
Recommended Action No action is required.
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)
Recommended Action No action is required.
Message VPC-4-VPC_PER_VLAN_NO_SUPPORT: image that does not support per-vlan type-1 check will not bring down/up any vlan (i.e. nothing will happen) until next compat-check.Explanation Triggered when ISSU/ISSD to an image which does not support per-vlan compat-check
Recommended Action No action is required.
Message VPC-4-VPC_PER_VLAN_CONSISTENCY_FAILED: Global consistency check for vPC failed for few vlansExplanation Global Consistency check for vPC failed for few vlans
Recommended Action No action is required.
Message VPC-4-VPC_REINITIALIZED: Reinitializing vpcs assuming peer deadExplanation Initializing vpcs assuming peer dead
Recommended Action No action is required.
Message VPC-4-VPC_ROLE_CHANGE: In domain [dec], VPC role status has changed to [chars]VPC-5
Message VPC-5-GLOBAL_CONSISTENCY_SUCCESS: In domain [dec], global configuration is consistentExplanation Global compact-check passed
Recommended Action No action is required.
Message VPC-5-INTF_CONSISTENCY_SUCCESS: In domain [dec], vPC [dec] configuration is consistentExplanation VPC configuration is consistent
Recommended Action No action is required.
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
Recommended Action No action is required.
Message VPC-5-PEER_KEEP_ALIVE_RECV_SUCCESS: In domain [dec], vPC peer keep-alive receive is successfulExplanation Peer keep-alive receive successful
Recommended Action No action is required.
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
Recommended Action No action is required.
Message VPC-5-PEER_KEEP_ALIVE_SEND_SUCCESS: In domain [dec], vPC peer keep-alive send is successfulExplanation Peer keep-alive send successful
Recommended Action No action is required.
Message VPC-5-PEER_KEEP_ALIVE_STATUS: In domain [dec], peer keep-alive status changed to [chars]Explanation Peer keep-alive (oob) status is changed to <peer-alive
Recommended Action Peer-not-alive
Message VPC-5-ROLE_PRIORITY_CFGD: In domain [dec], vPC role priority changed to [dec]Explanation Role priority configured
Recommended Action No action is required.
Message VPC-5-SYSTEM_MAC_CFGD: In domain [dec], vPC system-mac changed to [chars]Explanation System mac configured
Recommended Action No action is required.
Message VPC-5-SYSTEM_PRIO_CFGD: In domain [dec], vPC system priority changed to [dec]Explanation System priority changed
Recommended Action No action is required.
Message VPC-5-VPCM_DISABLED: vPC Manager disabledExplanation VPCM Service Disabled
Recommended Action No action is required.
Message VPC-5-VPCM_ENABLED: vPC Manager enabledExplanation VPCM Service Enabled
Recommended Action No action is required.
Message VPC-5-VPC_DELAY_SVI_BUP_TIMER_EXPIRED: vPC restore, delay interface-vlan bringup timer expired, reiniting interface-vlansExplanation VPC delay interface-vlan restore timer expired
Recommended Action No action is required.
Message VPC-5-VPC_DELAY_SVI_BUP_TIMER_START: vPC restore, delay interface-vlan bringup timer startedExplanation VPC delay interface-vlan restore timer start
Recommended Action No action is required.
Message VPC-5-VPC_DOWN: vPC [dec] is down ([chars])Explanation VPC is down (reason)
Recommended Action No action is required.
Message VPC-5-VPC_PEER_LINK_UP: vPC Peer-link is upExplanation VPC Peer-link is up
Recommended Action No action is required.
Message VPC-5-VPC_RESTORE_TIMER_EXPIRED: vPC restore timer expired, reiniting vPCsExplanation VPC restore timer expired
Recommended Action No action is required.
Message VPC-5-VPC_RESTORE_TIMER_START: vPC restore timer started to reinit vPCsExplanation VPC restore timer start
Recommended Action No action is required.
Message VPC-5-VPC_ROLE_PREMPT: In domain [dec], vPC role pre-emption triggeredExplanation VPC preemption triggered
Recommended Action No action is required.
Message VPC-5-VPC_UP: vPC [dec] is upVPC-6
Message VPC-6-PEER_LOCK_FAILED: Locking failed on peer switch - Aborting upgrade!!Explanation Locking failed on peer switch
Recommended Action No action is required.
Message VPC-6-PEER_VPC_CFGD_VLANS_CHANGED: Peer vPC [dec] configured vlans changedExplanation Remote MCEC configured vlans Changed
Recommended Action No action is required.
Message VPC-6-PEER_VPC_CFGD: peer vPC [dec] is configuredRecommended Action No action is required.
Message VPC-6-PEER_VPC_DOWN: Peer vPC [dec] is down ([chars])Recommended Action No action is required.
Message VPC-6-PEER_VPC_UP: Peer vPC [dec] is upRecommended Action No action is required.
Message VPC-6-STATS_CLEARED: vPC Statistics ClearedExplanation VPC statistics cleared
Recommended Action No action is required.
Message VPC-6-TRACK_OBJ_CONFIGURED: In domain [dec], track object configured [dec]Explanation VPC track object configured
Recommended Action No action is required.
Message VPC-6-TRACK_OBJ_DELETED: In domain [dec], track object deletedExplanation VPC track object un-configured
Recommended Action No action is required.
Message VPC-6-TYPE1_PARAM_CHANGED: TYPE-1 parameters changed: [chars]Explanation Type-1 Parameters Changed
Recommended Action No action is required.
Message VPC-6-VPCM_INTERNAL_INFO: [chars]Explanation VPCM got an internal info [chars]
Recommended Action No action is required.
Message VPC-6-VPC_ALLOWED_VLAN_CHANGED: vPC [dec] operational vlans changedExplanation Operational vlans changed on vPC
Recommended Action No action is required.
Message VPC-6-VPC_CFGD: vPC [dec] is configuredRecommended Action No action is required.
Message VPC-6-VPC_CONSISTENCY_CHECK_BYPASS: Bypassing consistency check for vPC: [dec]Explanation Bypassing consistency check for vpcs
Recommended Action No action is required.
Message VPC-6-VPC_CONSISTENCY_NEW_VLAN_PASS: Global Consistency check for vPC passed for new vlansExplanation Global Consistency check for vPC passed for new vlans
Recommended Action No action is required.
Message VPC-6-VPC_DOMAIN_ID_CFGD: vPC domain-id configured to [dec]Explanation VPC domain-id configured
Recommended Action No action is required.
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.
Recommended Action No action is required.
Message VPC-6-VPC_ES_ID_CFGD: Fabricpath switch ID [dec] configuredExplanation Fabricpath switch ID configured
Recommended Action No action is required.
Message VPC-6-VPC_ES_ID_REMOVED: Fabricpath switch ID [dec] removedExplanation Fabricpath switch ID removed
Recommended Action No action is required.
Message VPC-6-VPC_PEER_LINK_CFGD: vPC peer-link is configuredExplanation VPC Peer-link is configured
Recommended Action No action is required.
Message VPC-6-VPC_PER_VLAN_CONSISTENCY_PASSED: Global Consistency check for vPC passed for all vlansExplanation Global Consistency check for vPC passed for all vlans
VPM Messages
VPM-2
Message VPM-2-GENERAL_ERROR: [chars]Explanation The VP Manager has encountered an critical error. The description of error is [str.]
Recommended Action No action is required.
Message VPM-2-MALLOC_ERROR: Size [dec] bytesExplanation The VP Manager could not allocate memory.
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.
Message VPM-2-PSS_ERROR: [chars]Explanation The VP Manager encountered error while operating on a persistent storage database.
Recommended Action No action is required.
Message VPM-2-VPMON_CRIT: [chars] [dec]Explanation VPMON daemon critical message
Recommended Action No action is required.
Message VPM-2-VPMON_DPP_DOWNLOAD: HB failure, Restarting the DPP [dec]Explanation VPMON daemon re-downloading DPP(s)
Recommended Action ISAPI API users need to re-download config data to fast path
Message VPM-2-VPMON_DPP_RELOAD_FORCE: Force reload of DPP(s) [chars]: [chars]VPM-3
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 No action is required.
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.
Message VPM-3-SEND_TO_SNMP_AGENT_FAILED: [chars]Explanation The VP Manager could not send to SNMP Agent for DG=[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.
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 No action is required.
Message VPM-3-VPM_PSS_CORRUPTED: [chars] PSS found corruptedExplanation The VP Manager has detected corruption in one of its persistent information database. The database would be recreated.
VPM-4
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.
VPM-6
Message VPM-6-BECAME_ACTIVE: Became ACTIVE from standby modeExplanation The VP Manager on the standby supervisor became active and it is ready to serve client requests.
Recommended Action No action is required.
Message VPM-6-BECAME_STDBY: Became STANDBY from active modeExplanation The VP Manager became standby from active mode.
Recommended Action No action is required.
Message VPM-6-DG_DEREGISTERED: [chars]Explanation The VP Manager has deregistered DG [chars] at slot=[dec] processor=[dec] and SAP=[dec].
Recommended Action No action is required.
Message VPM-6-DG_REGISTERED: [chars]Explanation The VP Manager has registered DG [chars] from slot=[dec] processor=[dec] and SAP=[dec].
Recommended Action No action is required.
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 No action is required.
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
Recommended Action No action is required.
Message VPM-6-GENERAL_EVENT: [chars]Explanation The VP Manager has generated an important event. The description of the event is [str.]
Recommended Action No action is required.
Message VPM-6-PSS_CREATED: [chars] PSS CreatedExplanation One of the persistent information database of VP Manager has been recreated
Recommended Action No action is required.
Message VPM-6-PSS_DESTROYED: [chars] PSS DestroyedExplanation One of the persistent information databases of Vp Manager has been intentionally destroyed and would be recreated.
Recommended Action No action is required.
Message VPM-6-SERVICE_UP: Initialized [chars]Explanation The VP Manager is up and ready to accept client requests The service was initialized in [char] mode.
Recommended Action No action is required.
Message VPM-6-SWITCHOVER: Switching Over to other Sup.Explanation The VP Manager has successfully switched over to the standby supervisor card.
Recommended Action No action is required.
Message VPM-6-VPMON_INFO: [chars]Explanation VPMON daemon informational message
Recommended Action No action is required.
Message VPM-6-VPMON_STARTING: deamon startedExplanation The VPMON daemon successfully started
Recommended Action No action is required.
Message VPM-6-VPM_MDS_LICENSE_GRACE: MDS LICENSE in grace period for feature: [chars]Explanation MDS license is in grace period. Please retrieve a new MDS license
Recommended Action No action is required.
Message VPM-6-VPM_MDS_LICENSE_REVOKED: MDS LICENSE REVOKED for feature: [chars]Explanation MDS license is revoked. Please retrieve a new MDS license
Recommended Action No action is required.
Message VPM-6-VPM_MDS_TIMED_LICENSE: Timed MDS LICENSE for feature: [chars]VPM-SLOT#-2
Message VPM-SLOT#-2-CPP_CATASTROPHIC_ERROR: ERROR: Component ([chars]) caused critical error please reboot SSMVRRP-CFG Messages
VRRP-CFG-2
Message VRRP-CFG-2-ALLOC_MEMORY: Memory allocation failedExplanation The service failed to allocate a block of dynamic memory.
Recommended Action No action is required.
Message VRRP-CFG-2-VSH_REGISTER_FAIL: VSH registration failed returning [dec]VRRP-CFG-3
Message VRRP-CFG-3-INIT_FAILED: Initialization failed. Component [chars]Explanation The service failed to start. The failure occurred while initializing the component [chars].
Recommended Action Show processes to check the status of the other processes, debug the specified component.
Message VRRP-CFG-3-VRRP_FEATURE_MANAGER_ERROR: Error in feature manager operationExplanation The feature manager operation did not go through fine
Recommended Action Please check the reason for error using feature manager and rectify the problem
VRRP-CFG-5
Message VRRP-CFG-5-STARTING: VRRP Manager service startedVRRP-ENG Messages
VRRP-ENG-2
Message VRRP-ENG-2-ALLOC_MEMORY: Memory allocation failedExplanation The service failed to allocate a block of dynamic memory.
Recommended Action No action is required.
Message VRRP-ENG-2-VR_FAILURE: Error in VDH=[chars] [dec] interface [chars]. Going to inti stateExplanation The VR [dec] on the interface [chars] is in inti 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
Message VRRP-ENG-3-ARP_INIT_ERROR: Failed to inti ARP, ret [hex], errno [dec]Explanation VRRP-ARP interaction failed.
Recommended Action No action is required.
Message VRRP-ENG-3-BFD_IF_SESSION_REMOVAL_ERROR: Failed to remove interface level VRRP-BFD sessions ([hex] [hex]), Refer logsExplanation Please refer internal error history for more details.
Recommended Action No action is required.
Message VRRP-ENG-3-BFD_SESSION_ADD_ERROR: Failed to add a few VRRP-BFD sessions ([hex] [hex]), Refer logsExplanation Please refer internal error history for more details.
Recommended Action No action is required.
Message VRRP-ENG-3-BFD_SESSION_CREATION_ERROR: Failed to create BFD session information ([hex] [hex]), Refer logsExplanation Please refer internal error history for more details.
Recommended Action No action is required.
Message VRRP-ENG-3-BFD_SESSION_REMOVAL_ERROR: Failed to remove a few VRRP-BFD sessions ([hex] [hex]), Refer logsExplanation Please refer internal error history for more details.
Recommended Action No action is required.
Message VRRP-ENG-3-INIT_FAILED: Initialization failed. Component [chars]Explanation The service failed to start. The failure occurred while initializing the component [chars].
Recommended Action Show processes to check the status of the other processes, debug the specified component.
Message VRRP-ENG-3-IP_INIT_ERROR: Failed to init IP, ret [hex], errno [dec]Explanation VRRP-IP interaction failed.
Recommended Action No action is required.
Message VRRP-ENG-3-L3VM_INIT_ERROR: Failed to init L3VM, ret [hex], errno [dec]Explanation VRRP-L3VM interaction failed.
Recommended Action No action is required.
Message VRRP-ENG-3-URIB_INIT_ERROR: Failed to init URIB, ret [hex], errno [dec]VRRP-ENG-4
Message VRRP-ENG-4-BAD_ADV: VR[chars] ID [dec] on interface [chars] bad advertisement received: reason [chars]Explanation The virtual router specified has received an invalid advertisement.
Recommended Action Check that all VRRP nodes have the same configuration.
VRRP-ENG-5
Message VRRP-ENG-5-INTERFACE_DOWN: Cannot start the VR[chars] [dec] since the interface [chars] is downExplanation The specified VR is enabled but cant change state from in it. The specified interface is down or doesn't have a primary IP address configured.'
Recommended Action No action is required.
Message VRRP-ENG-5-INTERFACE_STATE_CHANGE: Interface [chars] state changed to [chars]Explanation The interface specified has changed state This could have triggered a VRRP status change.
Recommended Action No action is required.
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.
Message VRRP-ENG-5-STARTING: VRRP Engine service startedExplanation The service successfully started.
Recommended Action No action is required.
Message VRRP-ENG-5-VR_STATE_CHANGE: VR[chars] ID [dec] on interface [chars] state changed to [chars], event [chars]Explanation The status of the specified virtual router has changed to [chars].
VRRP-ENG-6
Message VRRP-ENG-6-VSHA_RESULT: VR ID [dec] on interface [chars] state change request result [chars]Explanation The result of the request for status change on the virtual router (with VSHA extension) specified is [chars].
VSAN Messages
VSAN-2
Message VSAN-2-PROGRAM_EXIT: process exiting with reason: [chars]Explanation VSAN manager process is exiting with reason [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.
VSAN-3
Message VSAN-3-CFS_OPERATION_FAILED: cfs [chars] operation failed: [chars]Explanation Cfs operation [chars1] has failed. [chars2]
Recommended Action Please check the reason for the failure of the cfs operation and rectify the problem
Message VSAN-3-MEM_ALLOC_FAILED: alloc failed for size:[dec]Explanation Memory allocation of size [dec] failed.
Recommended Action Do “show process memory” command to see memory usage of processes.
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].
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.
VSAN-6
Message VSAN-6-ACTIVATED: VSAN:[dec] changing from suspended to activeExplanation Making VSAN with ID [dec] active from suspended state.
Recommended Action No action is required.
Message VSAN-6-CFS_MERGE_NOT_SUPPORTED: merging of fctimer configuration data is not supportedExplanation Merging of fctimer configuration data using cfs is not supported
Recommended Action No action is required.
Message VSAN-6-CREATED: Created VSAN:[dec] with name:[chars]Explanation Created VSAN with ID [dec] and name [chars].
Recommended Action No action is required.
Message VSAN-6-MEMBERSHIP_UPDATE: Updated membership for interface:[chars] with VSAN:[dec]Explanation Updating membership for interface [chars] with VSAN [dec].
Recommended Action No action is required.
Message VSAN-6-REMOVED: Removed VSAN:[dec]Explanation Removed VSAN with ID [dec].
Recommended Action No action is required.
Message VSAN-6-SUSPENDED: VSAN:[dec] changing from active to suspendedExplanation Suspending VSAN with ID [dec] from active state.
Recommended Action No action is required.
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].
VSC Messages
VSC-SLOT#-2
Message VSC-SLOT#-2-CPP_CATASTROPHIC_ERR: ERROR: Component ([chars]) caused critical errorExplanation Virtualization software suffers critical error
Recommended Action Perform graceful shutdown and restart the linecard
Message VSC-SLOT#-2-CPP_RELOAD: Component ([chars]) is reloading the linecardExplanation No response to critical error notification from application
Recommended Action Response to critical error notification and perform graceful shutdown
Message VSC-SLOT#-2-REGISTER_NOTIF_REPLY_FAILED: Component ([chars]) fails to register to receive notification replyExplanation System will not receive partner notification reply
Recommended Action Virtualization software will restart the linecard after reply timeout.
VSC-SLOT#-3
Message VSC-SLOT#-3-SSM_GET_SW_CARDID: Get SSM software card ID failedExplanation SSM get software card ID failed
Recommended Action There is a serious error and the linecard need to be restarted
VSC-SLOT#-5
Message VSC-SLOT#-5-RX_PS_CRITICAL_NOTIF_REPLY: Component ([chars]) receives critical error notification replyExplanation Partner software will handle critical error
Recommended Action Virtualization software wont restart the line card. It is partner software responsibility to do shutdown
VSD Messages
VSD-SLOT#-2
Message VSD-SLOT#-2-CPP_CATASTROPHIC_ERROR: ERROR: Component ([chars]) caused critical error please reboot SSMVSD-SLOT#-6
Message VSD-SLOT#-6-VSD_INFO: [chars]VSHA Messages
VSHA-3
Message VSHA-3-VSHA_INIT_FAILED: Initialization failed. Component [chars]Explanation The service failed to start. The failure is happened initializing the specified component
Recommended Action No action is required.
Message VSHA-SLOT#-3-LOG_VSHA_STATE_TIMEOUT: VSHA Shutting Down. Deport Wait Timeout for sg: [chars] (vrid [dec]).Explanation SG was being shutdown. But DG could not be deported within specified time by the linecard
Recommended Action No action is required.
Message VSHA-SLOT#-3-LOG_VSHA_STATE: VSHA Shutting Down. Failure to deport dg: [chars] from sg: [chars] (vrid [dec]).Explanation DG was either removed from SG or SG was offline. But DG could not be deported by the linecard
VSHA-SLOT#-5
Message VSHA-SLOT#-5-LOG_VSHA_ARBT_DISK_STATE: Arbitration_disk [chars] for Service_Group [chars] (vrid [dec]) in error stateExplanation FCDD has reported arbt_disk as deleted/no longer accessible.
Recommended Action No action is required.
Message VSHA-SLOT#-5-LOG_VSHA_DG_STATE: Disk_Group [chars] from Service_Group [chars] (vrid [dec]) in error stateExplanation VSHA resource monitor has detected DG is not accessible.
Recommended Action No action is required.
Message VSHA-SLOT#-5-LOG_VSHA_SG_STATE: State change for sg [chars] (vrid [dec]). New state is [chars]. State change reason is [chars]Explanation Either a fail over or user command caused a sg state change.
VSHD Messages
VSHD-2
Message VSHD-2-VSHD_SYSLOG_EOL_ERR: EOL function [chars] from library [chars] exited due to Signal [dec]Explanation Error in CLI EOL function
Recommended Action No action is required.
Message VSHD-2-VSHD_SYSLOG_PSS_SNAPSHOT_ERR: Source URI:[chars] Destination URI:[chars] errcode:[dec]Explanation PSS snapshot error
Recommended Action No action is required.
Message VSHD-2-VSHD_SYSLOG_SDWRAP_ERR: Description:[chars] errcode:[dec]VSHD-3
Message VSHD-3-VSHD_ROLE_DISTRIBUTE_FAILURE: Role distribution operation ([chars]) failed with error id [hex]Explanation This is probably occurring due to unstable fabric
Recommended Action Please retry operation when fabric is stable
Message VSHD-3-VSHD_SYSLOG_FILE_ERR: Purpose:[chars] Filename:[chars] errcode:[dec]Explanation File handling error
Recommended Action No action is required.
Message VSHD-3-VSHD_SYSLOG_MTS_ERR: message [chars]Explanation MTS message handling error
Recommended Action No action is required.
Message VSHD-3-VSHD_SYSLOG_PARSE_TREE_ERR: [chars]Explanation Error while updating parse tree in shell
Recommended Action No action is required.
Message VSHD-3-VSHD_SYSLOG_PSS_ERR: Purpose:[chars] URI:[chars] errcode:[dec]VSHD-4
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 expiresExplanation Vsan policy would be set default (deny) for all roles when license expires
Recommended Action Please install the license file to continue using the feature.
Message VSHD-4-VSHD_ROLE_DATABASE_OUT_OF_SYNC: Role configuration database found to be different between the switches during mergeExplanation 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
Message VSHD-4-VSHD_ROLE_DATABASE_VERSION_NOT_UNDERSTOOD: This switch does not understand the version of role configuration database received during mergeExplanation 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
Message VSHD-5-VSHD_SYSLOG_CONFIG_CHANGE: VDC=[chars], VTY=[chars], user=[chars], CMD="[chars]"Explanation Configuration change notification
Recommended Action No action is required.
Message VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by [chars] on [chars]Explanation CLI Configuration mode was exited
Recommended Action No action is required.
Message VSHD-5-VSHD_SYSLOG_ROLE_CREATED: New cli role [chars] createdVSHD-7
Message VSHD-7-VSHD_SYSLOG_PARSE_TREE_UPDATE: Parse tree [chars]VTP Messages
VTP-0
Message VTP-0-EMERGENCY_MSG: [chars]VTP-1
Message VTP-1-ALERT_MSG: [chars]VTP-2
Message VTP-2-CRITICAL_MSG: [chars]Explanation VTP Critical Message
Recommended Action No action is required.
Message VTP-2-VTP_MODE_OFF_LONG_VLAN_NAME_EXIST: VTP Mode changed to off as long vlan configuration existsExplanation By default, VTP feature comes up in Server mode. long vlans can only operate in VTP transparent/off mode As long Vlan configuration already exist, VTP mode is changed to off.
Recommended Action No action is required.
Message VTP-2-VTP_MODE_OFF_PVLAN_EXIST: VTP Mode changed to off as Private VLAN configuration existsExplanation By default, VTP feature comes up in Server mode. Private vlans can only operate in VTP transparent/off mode As Private Vlan configuration already exist, VTP mode is changed to off.
Recommended Action No action is required.
Message VTP-2-VTP_MODE_OFF_RESERVED_VLAN_EXIST: VTP Mode changed to off as reserved vlan configuration existsExplanation By default, VTP feature comes up in Server mode. reserved vlans can only operate in VTP transparent/off mode As Reserved Vlan configuration already exist, VTP mode is changed to off.
Recommended Action No action is required.
Message VTP-2-VTP_MODE_TRANSPARENT_VLAN_RES_LIMIT_EXIST: VTP Mode changed to transparent as vlan resource limit configuration existsExplanation By default, VTP feature comes up in Server mode. resource limit configuration can only operate in VTP transparent/off mode As vlan resource limit configuration exists, VTP mode is changed to transparent.
VTP-3
Message VTP-3-ERROR_MSG: [chars]VTP-4
Message VTP-4-BAD_STARTUP_VLAN_CONFIG_FILE: Failed to configure VLAN from startup-config. Fallback to use VLAN configuration file from non-volatile memoryExplanation VLAN software failed to use VLAN configuration from startup-config file. It will fallback to use the binary VLAN configuration file in non-volatile memory.
Recommended Action No action is required.
Message VTP-4-VLAN_CREATE_FAIL: Failed to create VLANs [chars]: [chars]Explanation The VLANs specified in the error message could not be created. The VLAN manager called an VLAN database routine to create one or more VLANs, but the Vlan Manager failed the VLAN creation requests.
Recommended Action Collect show tech-support
Message VTP-4-VTP_BAD_VLAN_CONFIGURATION_FILE_VERSION: VLAN configuration file contained unknown file version: [dec]Explanation The VLAN configuration file read by the VLAN manager contained an unrecognized file version number. (This may indicate an attempt to regress to an older version of the VLAN manager software.)
Recommended Action LOG_STD_ACTION
Message VTP-4-VTP_BAD_VLAN_CONFIGURATION_FILE: Vlan configuration file contained incorrect verification word: [hex]Explanation The VLAN configuration file read by the VLAN manager did not begin with correct value which would indicate a valid VLAN configuration file. Thus, it has been rejected.
Recommended Action Collect show tech-support
Message VTP-4-VTP_BAD_VLAN_DOMAIN_NAME_LENGTH: VLAN configuration file contained incorrect domain name length: [dec]Explanation The VLAN configuration file read by the VLAN manager did not contain a valid domain name length. Thus, it has been rejected.
Recommended Action Please provision VTP domain name again
Message VTP-4-VTP_BAD_VLAN_PASSWORD_LENGTH: VLAN configuration file contained incorrect VTP password length: [dec]Explanation The VLAN configuration file read by the VLAN manager did not contain a valid VTP password length. Thus, it has been rejected.
Recommended Action Please provision VTP password again
Message VTP-4-VTP_INVALID_DATABASE_DATA: VTP received bad dataExplanation Invalid data was received by VTP process
Recommended Action Collect show tech-support
Message VTP-4-VTP_PROTOCOL_ERROR: VTP protocol code internal error: [chars]Explanation VTP protocol code encountered an unexpected error will processing configuration request, packet, or timer expiration.
Recommended Action Collect show tech-support
Message VTP-4-WARN_MSG: [chars]VTP-5
Message VTP-5-NOTIF_MSG: [chars]VTP-6
Message VTP-6-IFS_FAILURE: VLAN manager encountered file operation error: call = [chars] / file = [chars] / code = [dec] ([chars]) / bytes transfered = [dec]Explanation VTP received an unexpected error return from a file system call.
Recommended Action Collect show tech-support
Message VTP-6-INFO_MSG: [chars]Explanation VTP Informational Message
Recommended Action No action is required.
Message VTP-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to [chars].Explanation The VTP domain name was changed through configuration to the name specified in the message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain.
Recommended Action No action is required.
Message VTP-6-VTP_MODE_CHANGE: VLAN manager changing device mode from [chars] to [chars].Explanation Some switch devices must automatically change VTP device modes upon receipt of a VLAN configuration database containing more than a set number of VLANs, depending on the device. This message indicates that such a spontaneous conversion has occurred, what the previous mode was, and what the current mode is.
Recommended Action No action is required.
Message VTP-6-VTP_OLD_CONFIG_FILE_READ: Old version [dec] VLAN configuration file detected and read OK. Version [dec] files will be written in the future.Explanation VLAN software detected an old version of the VLAN configuration file format. It was able to interpret the file with no problems but will create files using the new format in the future.
Recommended Action No action is required.
Message VTP-6-VTP_PRUNING_CHANGE: VTP Operational Pruning [chars].Explanation VTP operational pruning changed. This can happen due to admin pruning change, VTP mode changes or VTP config propagation. show vtp status' output can be looked up to find the reason for this change.
Recommended Action Check 'show vtp status' output to find the reason for this change.No action is required.
VTP-7
Message VTP-7-DEBUG_MSG: [chars]WWN Messages
WWN-1
Message WWN-1-TYPE1_ALERT: [dec] (< [dec] %) RemainExplanation 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.
Message WWN-1-TYPES2_5_ALERT: Only [dec] (< [dec] %) Type 2 & 5 WWNs RemainExplanation The WWN Manager has run out of WWNs of NAA Types 2 and 5
Recommended Action Please add additional WWNs by programming a new Secondary MAC address and its range.
WWN-2
Message WWN-2-BKPLN_PROM_CANT_READ: Can not read backplane PROMExplanation The WWN Manager has failed to read chassis information. No dynamic WWNs could be allocated.
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.
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 No action is required.
Message WWN-2-GENERAL_ERROR: [chars]Explanation The WWN Manager has encountered an critical error. The description of error is [str.].
Recommended Action No action is required.
Message WWN-2-MALLOC_ERROR: Size [dec] bytesExplanation The WWN Manager could not allocate memory.
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.
Message WWN-2-PSS_BKP_PSS_MISMATCH: Block [dec]: PSS: Not Free; BKPLN PROM: FreeExplanation 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 No action is required.
Message WWN-2-PSS_ERROR: [chars]Explanation The WWN Manager encountered error while operating on a persistent storage database.
Recommended Action No action is required.
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 No action is required.
Message WWN-2-TYPE1_CRIT: [dec] (< [dec]%) RemainExplanation The WWN Manager has only [dec] or less than [dec]-percent WWNs remaining.
Recommended Action Please add additional WWNs by programming a new Secondary MAC address and its range.
Message WWN-2-TYPES2_5_CRIT: [dec] (< [dec]%) RemainExplanation The WWN Manager has only [dec] or less than [dec]-percent WWNs of NAA Types 2 and 5 remaining.
Recommended Action Please add additional WWNs by programming a new Secondary MAC address and its range.
WWN-3
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 No action is required.
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 No action is required.
Message WWN-3-RELEASE_ERR: Cant Rel. WWN [chars]Explanation WWN Manager received a request to release a WWN that cannot be released.
Recommended Action No action is required.
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 No action is required.
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 No action is required.
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 No action is required.
Message WWN-3-WWN_PSS_CORRUPTED: [chars] PSS found corruptedExplanation The WWN Manager has detected corruption in one of its persistent information database. The database would be recreated.
WWN-4
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 No action is required.
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 No action is required.
Message WWN-4-TYPE1_WARN: [dec] (< [dec]%) RemainExplanation The WWN Manager has only [dec] or less than [dec]-percent WWNs remaining for allocation.
Recommended Action No action is required.
Message WWN-4-TYPES2_5_WARN: [dec] (< [dec]%) RemainExplanation The WWN Manager has only [dec] or less than [dec]-percent WWNs of NAA Types 2 and 5 remaining.
Recommended Action Please add additional WWNs by programming a new Secondary MAC address and its range.
WWN-5
Message WWN-5-VSAN_WWN_CHANGE: [chars]Explanation VSAN-WWN created or deleted. The description of error is [str.].
WWN-6
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 No action is required.
Message WWN-6-BECAME_ACTIVE: Became ACTIVE from standby modeExplanation The WWN Manager on the standby supervisor became active and it is ready to serve client requests for WWNs.
Recommended Action No action is required.
Message WWN-6-BECAME_STDBY: Became STANDBY from active modeExplanation The WWN Manager became standby from active mode.
Recommended Action No action is required.
Message WWN-6-EXCESSIVE_DELAY: [chars]Explanation Excessive time taken for a processing event. The description of the event is [str.].
Recommended Action No action is required.
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.
Recommended Action No action is required.
Message WWN-6-GENERAL_EVENT: [chars]Explanation The WWN Manager has generated an important event. The description of the event is [str.].
Recommended Action No action is required.
Message WWN-6-PSS_CREATED: [chars] PSS CreatedExplanation One of the persistent information database of the WWN Manager has been recreated.
Recommended Action No action is required.
Message WWN-6-PSS_DESTROYED: [chars] PSS DestroyedExplanation One of the persistent information databases has been intentionally destroyed and would be recreated.
Recommended Action No action is required.
Message WWN-6-RELEASED_BLOCK: Block number [dec]Explanation The WWN Manager has released a block, block number [dec], of 256 WWNs.
Recommended Action No action is required.
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 No action is required.
Message WWN-6-SERVICE_UP: Initialized [chars]Explanation The WWN Manager is up and ready to accept client requests for WWNs. The service was initialized in [char] mode.
Recommended Action No action is required.
Message WWN-6-SWITCHOVER: Switching Over to other SupervisorExplanation The WWN Manager has successfully switched over to the standby supervisor card.
WWN-7
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.
X2_USD Messages
X2_USD-2
Message X2_USD-2-DC3_X2_SYSLOG_INTERNAL_SOFTWARE_ERROR: An internal error in the X2 driver occurred on port [dec]: [chars] [dec]Explanation An unexpected internal X2 driver software error occurred
Recommended Action Contact technical support
Message X2_USD-2-DC3_X2_SYSLOG_INVALID_TRANSCEIVER_TYPE: Module in port [dec] has an invalid transceiver type of [hex]Explanation An unsupported module was plugged into the port
Recommended Action Retry with a supported module
Message X2_USD-2-DC3_X2_SYSLOG_NVRAM_CHKSUM_FAILURE: NVRAM checksum failure for module in port [dec]Explanation Non-volatile memory checksum error in module.
Recommended Action Remove and reinsert module and retry operation. If the error still persists try with new a module. Sometimes the error will be displayed if the module is not inserted properly. All this log suggests is to retry the insertion and see if the error goes away if it doesn’t then it’s a issue with module.
Message X2_USD-2-DC3_X2_SYSLOG_ONEX_INITIALIZATION_FAILURE: A validated OneX module in port [dec] failed initialization with error [hex]Explanation A OneX module was detected and validated, but failed initialization
Recommended Action Remove and reinsert module and retry operation
Message X2_USD-2-DC3_X2_SYSLOG_ONEX_VALIDATION_FAILURE: OneX module in port [dec] failed validation with error [hex]Explanation A counterfeit OneX module detected, or a valid OneX has a corrupt sprom
X2_USD Messages
X2_USD-5
Message X2_USD-5-DC3_X2_SYSLOG_ONEX_INSERTION: OneX inserted into port [dec]Explanation OneX X2 to SFP+ Converter inserted is detected
Recommended Action Ensure OneX insertion an expected action
Message X2_USD-5-DC3_X2_SYSLOG_ONEX_REMOVAL: OneX removed from port [dec]Explanation OneX X2 to SFP+ Converter removal is detected
Recommended Action Ensure OneX removal an expected action
Message X2_USD-5-DC3_X2_SYSLOG_ONEX_SFPPLUS_INSERTION: SFP+ inserted into port [dec]Explanation SFP+ insertion into OneX X2 to SFP+ Converter detected
Recommended Action Ensure SFP+ insertion into OneX an expected action
Message X2_USD-5-DC3_X2_SYSLOG_ONEX_SFPPLUS_REMOVAL: SFP+ removed from port [dec]Explanation SFP+ removal from OneX X2 to SFP+ Converter detected
Recommended Action Ensure SFP+ removal from OneX an expected action
XBAR_CLIENT Messages
XBAR_CLIENT-2
Message XBAR_CLIENT-2-CROSS_LINK_SYNC_LOSS: XBAR-[chars].Explanation Cross links lost sync and hence xbar is brought down.
Recommended Action Please reload the xbar using reload xbar <xbar-num>
Message XBAR_CLIENT-2-MEM_FULL: Memory allocation failed.Explanation XBAR_CLIENT process has failed to allocate memory.
Recommended Action Please perform a show system internal xbar-client internal1 event-history' to collect more information.
Message XBAR_CLIENT-2-MEM_FULL: memory allocation failedExplanation Process xbar_client failed to allocate memory
Recommended Action Please examine the xbar-client event-history for more information.
Message XBAR_CLIENT-2-PROC_DN: Process is shutting down: [chars].Explanation XBAR_CLIENT process is exiting.
Recommended Action Please perform a ‘show system internal xbar-client internal1 event-history' to collect more information.
Message XBAR_CLIENT-2-PROC_DN: exiting: [chars].Explanation Process xbar_client is exiting
Recommended Action Please examine the xbar-client event-history for more information.
Message XBAR_CLIENT-2-PROC_INITFAIL: Process initialization failed due to [chars].Explanation XBAR_CLIENT process has failed initialization.
Recommended Action Please perform a show system internal xbar-client internal1 event-history to collect more information.
Message XBAR_CLIENT-2-PROC_INITFAIL: Process initialization failed due to [chars].Explanation XBAR_CLIENT process has failed initialization.
Recommended Action Please perform a ‘show system internal xbar-client internal1 event-history' to collect more information.
Message XBAR_CLIENT-2-PROC_INITFAIL: initialization failed due to [chars]Explanation Process xbar_client failed initialization
Recommended Action Please examine the xbar-client event-history for more information.
XBAR_CLIENT-3
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.
Recommended Action Please perform a show system internal xbar-client internal1 event-history' to collect more information.
Message XBAR_CLIENT-3-IPC_MSGERR: failure processing IPC message [dec], error code = [dec]Explanation Process xbar_client failed to process IPC message
Recommended Action Please examine the xbar-client event-history for more information.
Message XBAR_CLIENT-3-IPC_MSGUNKN: Received unexpected IPC message: [dec].Explanation XBAR_CLIENT process has received an unknown message.
Recommended Action Please perform a show system internal xbar-client internal1 event-history' to collect more information.
Message XBAR_CLIENT-3-IPC_MSGUNKN: unknown IPC message received: [dec]Explanation Process xbar_client has received an unknown IPC message.
Recommended Action Please examine the xbar-client event-history for more information.
Message XBAR_CLIENT-3-SUP2_XBC_MOD_INIT_FAIL: [chars], errcode - [hex]Explanation The module initialization failed
Recommended Action Please perform a 'show process xbar-client event-history' to collect more information'
XBAR_CLIENT-SLOT#-2
Message XBAR_CLIENT-SLOT#-2-VEGAS2_XBC_MEM_FULL: memory allocation failed in routine [chars]Explanation Process xbar_client failed to allocate memory
Recommended Action Please perform a 'show process xbar-client event-history' to collect more information'
Message XBAR_CLIENT-SLOT#-2-VEGAS2_XBC_PROC_DN: terminating due to signal [dec]Explanation Process xbar_client is exiting
Recommended Action Please perform a 'show process xbar-client event-history' to collect more information
Message XBAR_CLIENT-SLOT#-2-VEGAS2_XBC_PROC_INITFAIL: initialization failed: [chars], errno [dec]Explanation Process xbar_client failed initialization
Recommended Action Please perform a 'show process xbar-client event-history' to collect more information
XBAR_CLIENT-SLOT#-3
Message XBAR_CLIENT-SLOT#-3-VEGAS2_XBC_IPC_MSGUNKN: unknown IPC message received: opcode [dec]Explanation Process xbar_client has received an unknown IPC message
Recommended Action Please perform a 'show process xbar-client event-history' to collect more information
Message XBAR_CLIENT-SLOT#-3-VEGAS2_XBC_MOD_INIT_FAIL: [chars], errcode - [hex]Explanation The module initialization failed
Recommended Action Please perform a 'show process xbar-client event-history' to collect more information
XBAR_DRIVER_USD Messages
XBAR_DRIVER_USD-2
Message XBAR_DRIVER_USD-2-SCZ_ACCESS_FAILED: Xbar Driver Failed to access reg for [chars]Explanation Xbar Driver Access failed
Recommended Action No action is required.
Message XBAR_DRIVER_USD-2-SCZ_CATASTROPHIC: Xbar Driver catastrophic failure: [chars] Message Ex XBAR_DRIVER_USD-2-SCZ_CATASTROPHIC: Xbar Driver catastrophic failure: [chars]Explanation Xbar Driver catastrophic error
Recommended Action No action is required.
Message XBAR_DRIVER_USD-2-SCZ_INTR: Xbar Driver Interrupt occurred: [chars]Explanation Interrupt occurred on the xbar
Recommended Action No action is required.
Message XBAR_DRIVER_USD-2-SCZ_SW_INIT_ABORTED: Xbar Driver Failed to finish Software Initialization: [chars]Explanation Xbar Driver Software Initialization failed
Recommended Action No action is required.
Message XBAR_DRIVER_USD-2-SHUTDOWN: Xbar Driver software process exiting: [chars]Explanation Xbar Driver shutting down
Recommended Action No action is required.
Message XBAR_DRIVER_USD-2-SYNC_FAILED: Xbar Driver sync failed: [chars]XBAR_DRIVER_USD-3
Message XBAR_DRIVER_USD-3-EN_DATA_FAILED: Xbar Driver enable data failed for slot:[dec] asic:[dec] channel: [hex]Explanation Xbar Driver Enable Data path failed for the xbar channel
XBAR_DRIVER_USD-5
Message XBAR_DRIVER_USD-5-STARTING: Xbar Driver process startingXBAR_DRIVER_USD-6
Message XBAR_DRIVER_USD-6-DIS_DATA: Xbar Driver disable datapath done for slot:[dec] asic:[dec] channel: [hex]Explanation Disabled Data path successfully for the xbar channel
Recommended Action No action is required.
Message XBAR_DRIVER_USD-6-EN_DATA: Xbar Driver enable datapath done for slot:[dec] asic:[dec] channel: [hex]Explanation Enabled Data path successfully for the xbar channel
Recommended Action No action is required.
Message XBAR_DRIVER_USD-6-HW_INIT: Xbar Driver HW initialization has been done for Slot: [dec] Asic: [dec]Explanation Xbar Driver HW initialization has been called [dec]
Recommended Action No action is required.
Message XBAR_DRIVER_USD-6-SYNC_DONE: Xbar Driver sync done for slot: [dec] asic: [dec] channel: [hex]Explanation Sync Completed successfully for the xbar channel
XBAR Messages
XBAR-2
Message XBAR-2-ARB_INIT_FAIL: Arbiter Initialization failed return_code [hex] ([chars]).Explanation The supervisor has experienced an arbiter setup failure.
Recommended Action No action is required.
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 No action is required.
Message XBAR-2-XBAR_INSUFFICIENT_XBAR_BANDWIDTH: Module in slot [dec] has insufficient xbar-bandwidth.Explanation To track insufficient xbar-bandwidth.
Recommended Action No action is required.
Message XBAR-2-XBAR_MIXED_SPINES_POLICY_MATCHED: [chars]Explanation Fabric could not be brought online due to policy match:
Recommended Action No action is required.
Message XBAR-2-XBAR_SUFFICIENT_XBAR_BANDWIDTH: Module in slot [dec] has sufficient xbar-bandwidth.Explanation To track recovery from insufficient xbar-bandwidth.
Recommended Action No action is required.
Message XBAR-2-XBM_EEM_FABRIC_ACTION: Fabric [chars] has been reloaded by xbar-manager because of an eem-policy triggered action [chars] %iExplanation 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 No action is required.
Message XBAR-2-XBM_EEM_MODULE_ACTION: Module [chars] has been reloaded by xbar-manager because of an eem-policy triggered actionExplanation 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.
Recommended Action No action is required.
Message XBAR-2-XBAR_MONITOR_INTERNAL_CRC_ERR: Module-[num] detects CRC error at Ingress Qengine, putting it in failure stateExplanation CRC errors reported on the ingress queue of the module [num].
Recommended Action Replace the module that reports error.
Message XBAR-2-XBAR_MONITOR_INTERNAL_CRC_ERR: Module-[num] detects CRC error at Ingress stage2, putting it in failure stateExplanation CRC errors reported on the ingress crossbar of the module [num].
Recommended Action Replace the module that reports error.
Message XBAR-2-XBAR_MONITOR_INTERNAL_CRC_ERR: Xbar [num] detects CRC error at ingress stage3, putting it in failure stateExplanation CRC errors reported on the ingress crossbar [num] of the chassis.
Recommended Action Replace the module that reports error.
Message XBAR-2-XBAR_MONITOR_INTERNAL_CRC_ERR: Module-[num] detects CRC Error at Egress stage4/Qengine, putting it in failure state as there is only one fabricExplanation CRC errors reported on the egress crossbar of the module [num].
Recommended Action Replace the module that reports error.
Message XBAR-2-XBAR_MONITOR_INTERNAL_CRC_ERR: Module-[num] detects CRC Error at Egress stage4/Qengine, putting it in failure state as there is only one fabricExplanation CRC errors reported on the egress crossbar of the module [num].
Recommended Action Replace the module that reports error.
Message XBAR-2-XBAR_MONITOR_INTERNAL_CRC_ERR: Module-[num] detects CRC error at Egress stage4; due to Xbar [5] putting the connected Xbar in failure stateExplanation CRC errors reported on the egress crossbar [num] of the module [num]
Recommended Action Replace the module that reports error.
Message XBAR-2-XBAR_MONITOR_INTERNAL_CRC_ERR: Module-[num] detects CRC Error at Egress Q-engine, putting it in failure stateExplanation CRC errors reported on the egress queue of the module [num].
XBAR-3
Message XBAR-3-MEM_FULL: Memory allocation failed. [chars]%iXBAR-4
Message XBAR-4-XBAR_MIXED_SPINES_IN_CHASSIS: [chars]Explanation There are both FAB-1 and FAB-2 type spines in the Chassis. Please replace the FAB-1 spines with FAB-2 Spines.
XBAR-5
Message XBAR-5-ARBITER_INIT_FAILURE: Re-initializing Arbiter. [chars] [chars] module %iExplanation The supervisor has experienced an arbiter setup failure.
Recommended Action No action is required.
Message XBAR-5-ARB_CLEAR_PORT_FAIL: Arbiter reported failure to de-register port [dec] in group [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an arbiter setup failure.
Recommended Action No action is required.
Message XBAR-5-ARB_INIT_MOD_DIS_INTR_FAIL: Arbiter reported failure to disable interrupt for module [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an arbiter setup failure.
Recommended Action No action is required.
Message XBAR-5-ARB_INIT_MOD_INSERT_CHECK_FAIL: Arbiter reported failure to recognize module [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an arbiter setup failure.
Recommended Action No action is required.
Message XBAR-5-ARB_INIT_MOD_INSERT_FAIL: Arbiter reported failure to init module [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an arbiter setup failure.
Recommended Action No action is required.
Message XBAR-5-ARB_INIT_MOD_INTR_FAIL: Arbiter reported failure to enable interrupt for module [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an arbiter setup failure.
Recommended Action No action is required.
Message XBAR-5-ARB_INIT_MOD_REMOVE_FAIL: Arbiter reported failure to remove module [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an arbiter setup failure.
Recommended Action No action is required.
Message XBAR-5-ARB_INIT_PORT_FAIL: Arbiter reported failure to register port [dec] in group [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an arbiter setup failure.
Recommended Action No action is required.
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 information about XBAR component. Use command show system internal xbar event-history module <module-id>
Message XBAR-5-SYNC_THRESHOLD_FAILURE: Module resync threshold exceeded [chars] [chars] module%iExplanation This module has exceeded the number of resync attempts in a day. Module will be reloaded
Recommended Action No action is required.
Message XBAR-5-XBAR_ENABLE_FPOE_DB_FAILURE: XBAR [chars] enabling FPOE-DB mode failedExplanation 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 No action is required.
Message XBAR-5-XBAR_INIT_FAILURE: XBAR [chars] initialization failed [chars]%iExplanation 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 No action is required.
Message XBAR-5-XBAR_INIT_FAIL: Xbar [[dec].[dec]] reported failure during initialization return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Message XBAR-5-XBAR_MOD_INSERT_SEQ_FAILURE: [chars] for module [dec]Explanation The xbar manager received failure response and is failing the insert sequence
Recommended Action No action is required.
Message XBAR-5-XBAR_MOD_LC_INSERT_SEQ_FAILURE: Module in slot [dec] has failed insert sequenceExplanation The xbar manager is failing the insert sequence
Recommended Action No action is required.
Message XBAR-5-XBAR_PORT_CHECK_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to check sync on port [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Message XBAR-5-XBAR_PORT_CONTINUE_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to continue sync on port [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Message XBAR-5-XBAR_PORT_DISABLE_FAIL: Xbar [[dec].[dec]] reported failure to disable port [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Message XBAR-5-XBAR_PORT_ENABLE_FAIL: Xbar [[dec].[dec]] reported failure to enable port [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
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 The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
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 The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Message XBAR-5-XBAR_PORT_LPBACK_DISABLE_FAIL: Xbar [[dec].[dec]] reported failure to disable port loopback on [dec] returned [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Message XBAR-5-XBAR_PORT_LPBACK_ENABLE_FAIL: Xbar [[dec].[dec]] reported failure to enable port loopback on [dec] returned [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Message XBAR-5-XBAR_PORT_START_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to start sync on port [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
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.
Recommended Action No action is required.
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.
Recommended Action No action is required.
Message XBAR-5-XBAR_STANDBY_SUP_ARB_FAIL: [chars] return_code [hex] ([chars])Explanation The supervisor has experienced an arbiter access failure.
Recommended Action No action is required.
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.
Recommended Action No action is required.
Message XBAR-5-XBAR_SW_INIT_FAIL: Xbar [[dec].[dec]] reported failure during sw intialization return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Message XBAR-5-XBAR_VERSION_CHECK_FAILURE: XBAR [chars] SCZ version check failed [chars] %iExplanation This SUP has an older Santa cruz version, and so will not be allowed to power-up, Please upgrade to the latest supervisor version.
XCVR_USD Messages
XCVR_USD-6
Message XCVR_USD-6-XCVR_USD_DEBUG_MSG: [chars]Recommended Action No action is required.
Message XCVR_USD-6-XCVR_USD_LOG_MSG: [chars]XCVR Messages
XCVR-6
Message XCVR-6-XCVR_LIB_DEBUG_MSG: [chars]Recommended Action No action is required.
Message XCVR-6-XCVR_LIB_DEBUG_MSG: [chars]XMLMA Messages
XMLMA-2
Message XMLMA-2-HEARTBEAT_FAIL: XML master agent failed to send heart beat: [chars]Explanation XML master agent has failed sending heartbeat.
Recommended Action No action is required.
Message XMLMA-2-INITFAIL: XML master agent initialization fails: [chars]Explanation XML master agent has failed initialization.
Recommended Action No action is required.
Message XMLMA-2-MTSERROR: XML master agent mts operation failed: [chars]Explanation XML master agent mts operation failed.
Recommended Action No action is required.
Message XMLMA-2-PSSFAILURE: XML master agent pss operation failed: [chars]Explanation XML master agent pss operation failed.
Recommended Action No action is required.
Message XMLMA-2-XMLMACRIT: XML master agent: [chars]XMLMA-3
Message XMLMA-3-XMLMAERR: XML master agent: [chars]XMLMA-5
Message XMLMA-5-STARTING: XML master agent started [chars]XMLMA-6
Message XMLMA-6-XMLMAEXIT: XML master agent exiting...: [chars]Explanation XML master agent is exiting.
Recommended Action No action is required.
Message XMLMA-6-XMLMALOG: XML master agent operation log: [chars]XMLSA Messages
XMLSA-2
Message XMLSA-2-HEARTBEAT_FAIL: XML sub agent failed sending heart beat: [chars]Explanation XML sub agent failed sending heartbeat.
Recommended Action No action is required.
Message XMLSA-2-INITFAIL: XML sub agent initialization fails: [chars]Explanation XML agent has failed initialization.
Recommended Action No action is required.
Message XMLSA-2-USER_INACTIVE: XML sub agent timed out: [chars]Explanation XML sub agent timedout due to inactivity.
Recommended Action No action is required.
Message XMLSA-2-VSH_ERR: XML sub agent vsh cmd error...: [chars]XMLSA-5
Message XMLSA-5-STARTING: XML sub agent started: [chars]XMLSA-6
Message XMLSA-6-XMLSAEXIT: XML sub agent exiting...: [chars]Explanation XML sub agent is exiting.
Recommended Action No action is required.
Message XMLSA-6-XMLSALOG: XML sub agent log: [chars]ZBM Messages
ZBM-2
Message ZBM-2-ZBM_HA_FAILURE: Failed to do high availability operation: [chars].Explanation Failed to do high availability operation. [chars] is the reason.
Recommended Action No action is required.
Message ZBM-2-ZBM_INIT_FAILED: Initialization failed for ZBM: [chars], reason: [hex].Explanation Initialization failed for ZBM due to [chars], reason: [hex].
Recommended Action No action is required.
Message ZBM-2-ZBM_INIT_WARNING: Initialization warning for ZBM: [chars], reason: [hex].Explanation Initialization warning for ZBM due to [chars], reason: [hex].
Recommended Action No action is required.
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 No action is required.
Message ZBM-2-ZBM_MALLOC_FAILURE: Memory allocation failed for size [dec]Explanation Memory allocation is failed for size [dec] bytes.
Recommended Action Restart the process.
Message ZBM-2-ZBM_MTS_FAILURE: Failed to do MTS operation: [chars].Explanation Failed to do MTS operation. [chars] is the reason.
Recommended Action No action is required.
Message ZBM-2-ZBM_MTS_REGISTRATION_FAILED: MTS options setting to [hex] failed for opCode: [dec].Explanation MTS options setting to [hex] failed for opCode: [dec].
Recommended Action No action is required.
Message ZBM-2-ZBM_PSS_FAILURE: Failed to do PSS operation: [chars], reason: [hex].Explanation Failed to do PSS operation [chars]. [hex] is the reason.
Recommended Action No action is required.
Message ZBM-2-ZBM_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.
Recommended Action No action is required.
Message ZBM-2-ZBM_RUNTIME_FAILURE: [chars] [dec], Error: [hex]Explanation ZBM runtime failure is reported as [chars] [dec], reason: [hex].
Recommended Action No action is required.
Message ZBM-2-ZBM_TCAM_FAILURE: Failed to do TCAM operation: [chars].Explanation Failed to do TCAM operation. [chars] is the reason.
Recommended Action No action is required.
Message ZBM-2-ZBM_TCAM_SEND: [chars]ZBM-4
Message ZBM-4-ZBM_WARNING: [chars] [dec]Explanation ZBM warning messages is reported as [chars] [dec].
ZBM-6
Message ZBM-6-ZBM_DIAG_EVENT_STATUS: [chars] [hex].Explanation ZBM system health management event status is reported as [chars] [hex].
Recommended Action No action is required.
Message ZBM-6-ZBM_ECHO_PROGRAMMING_FAILED: [chars].Explanation Programming echo entry failed for [chars].
Recommended Action No action is required.
Message ZBM-6-ZBM_E_PORT_EVENT_STATUS: [chars] [chars].Explanation ZBM xEport event status is reported as [chars] [chars].
Recommended Action No action is required.
Message ZBM-6-ZBM_FCC_EVENT_STATUS: [chars] [chars].Explanation ZBM FCC event status is reported as [chars] [chars].
Recommended Action No action is required.
Message ZBM-6-ZBM_INIT_PROCESS: Zone Block Mgr process started [chars] at [chars]Explanation Zone Block Mgr process started in [chars] (stateless/stateful) mode at time [chars].
Recommended Action No action is required.
Message ZBM-6-ZBM_LINECARD_EVENT_STATUS: [chars] [hex].Explanation ZBM linecard event status is reported as [chars] [dec].
Recommended Action No action is required.
Message ZBM-6-ZBM_MCAST_EVENT_STATUS: [chars] [chars].Explanation ZBM multicast event status is reported as [chars] [chars].
Recommended Action No action is required.
Message ZBM-6-ZBM_NX_PORT_EVENT_STATUS: [chars] [chars].Explanation ZBM Nx Port event status is reported as [chars] [chars].
Recommended Action No action is required.
Message ZBM-6-ZBM_PORT_MODE_EVENT_STATUS: [chars] [chars].Explanation ZBM portmode event status is reported as [chars] [chars].
Recommended Action No action is required.
Message ZBM-6-ZBM_RUNTIME_STATUS: [chars] [dec]Explanation ZBM runtime status is reported as [chars] [dec].
Recommended Action No action is required.
Message ZBM-6-ZBM_STATUS: ZBM Status: [chars].Explanation ZBM status is reported as [chars].
Recommended Action No action is required.
Message ZBM-6-ZBM_UPDATE_SSRAM_QOS_EVENT_STATUS: [chars] [chars].Explanation ZBM update SSRAM for QoS event status is reported as [chars] [chars].
ZONE Messages
ZONE-2
Message ZONE-2-LZ_EXITING: LUN/Read-only zoning process exited. Reason: [chars]Explanation The LUN/Read-only zoning process has exited due to [char]. The process has probably been restarted automatically.
Recommended Action No action is required.
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 No action is required.
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].
Recommended Action No action is required.
Message ZONE-2-LZ_MALLOC_ERROR: Size [dec] bytesExplanation The LUN/Read-only zoning process could not allocate memory.
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.
Message ZONE-2-ZS_ALIAS_LIMIT_EXCEEDED: The limit for maximum number of aliases exceededExplanation 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.
Message ZONE-2-ZS_ATTR_GROUP_LIMIT_EXCEEDED: The limit for maximum number of attribute groups exceededExplanation 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.
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
Message ZONE-2-ZS_CHANGE_ACA_FAILED: ACA failed: [chars]Explanation Zone Server cannot acquire change authorization: [chars].
Recommended Action Verify the interoperability mode on all the switches OR retry later.
Message ZONE-2-ZS_CHANGE_ACQUIRE_AUTH_FAILED: Acquire authorization failed on VSAN [dec]Explanation Zone Server cannot acquire authorization on VSAN [dec].
Recommended Action No action is required.
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].
Recommended Action No action is required.
Message ZONE-2-ZS_CHANGE_ACTIVATION_FAILED_RESN: Activation failed: reason [chars]Explanation Zone Server cannot activate due to reason [chars].
Recommended Action No action is required.
Message ZONE-2-ZS_CHANGE_ACTIVATION_FAILED: Activation failedExplanation Zone Server cannot activate the zoneset.
Recommended Action No action is required.
Message ZONE-2-ZS_CHANGE_APPLY_FAILED: Apply changed failed on VSAN [dec]Explanation Zone Server cannot apply changes on VSAN [dec].
Recommended Action No action is required.
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].
Recommended Action No action is required.
Message ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED_RESN: Deactivation failed: reason [chars]Explanation Zone Server cannot deactivate due to reason [chars].
Recommended Action No action is required.
Message ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED: Deactivation failedExplanation Zone Server cannot deactivate the zoneset.
Recommended Action No action is required.
Message ZONE-2-ZS_CHANGE_RELEASE_AUTH_FAILED: Release authorization failed on VSAN [dec]Explanation Zone Server cannot release authorization on VSAN [dec].
Recommended Action No action is required.
Message ZONE-2-ZS_CHANGE_RRCA_REJECTED: RRCA received from remote domain [dec] is rejected: [chars]Explanation Received invalid RRCA from domain [dec]: [chars]
Recommended Action Verify the interoperability mode on the switch.
Message ZONE-2-ZS_CHANGE_RUFC_REJECTED: RUFC received from remote domain [dec] is rejected: [chars]Explanation Received invalid RUFC from domain [dec]: [chars]
Recommended Action Verify the interoperability mode on the switch.
Message ZONE-2-ZS_CHANGE_SFC_FAILED: SFC failed: [chars]Explanation Zone Server cannot stage zone configuration: [chars].
Recommended Action Verify the interoperability mode on all the switches.
Message ZONE-2-ZS_CHANGE_SFC_REJECTED: SFC received from remote domain [dec] is rejected: [chars]Explanation Received invalid SFC from domain [dec]: [chars]
Recommended Action Verify the interoperability mode on the switch.
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].
Recommended Action No action is required.
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].
Recommended Action No action is required.
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].
Recommended Action No action is required.
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].
Recommended Action No action is required.
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].
Recommended Action No action is required.
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].
Recommended Action No action is required.
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].
Recommended Action No action is required.
Message ZONE-2-ZS_DB_OPERATION_FAILED: Database operation error: [chars]Explanation Database operation is failed: [chars].
Recommended Action No action is required.
Message ZONE-2-ZS_EXPORT_IMPORT_FAILED: [chars] operation failedExplanation [chars] (Export/Import) operation failed.
Recommended Action No action is required.
Message ZONE-2-ZS_FC2_DB_SIZE_LIMIT_EXCEEDED: Zone database size [dec] bytes exceeded maximum limit of [dec] bytes.Explanation Zone database size exceeded: [chars].
Recommended Action Make sure that database size is less than the maximum limit.
Message ZONE-2-ZS_FIPS_COMPLIANCE_FAILURE: FIPS compliance error: consecutively same random numbersExplanation FIPS compliance error: consecutively same random numbers
Recommended Action No action is required.
Message ZONE-2-ZS_HARD_LIMIT_EXCEEDED: Maximum configurable zone limit of [dec] reached. Creation of any more zones is not supported.Explanation The number of zones configured has exceeded the maximum number of zones: [dec] allowed across all vsan. 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 vsan.
Message ZONE-2-ZS_INIT_FAILED: [chars]Explanation Zone Server initialization failed: [chars].
Recommended Action No action is required.
Message ZONE-2-ZS_LICENSE_UNAVAIL: License:[chars] unavailable, removing LUN members, read-only attribute and re-activating active zonesets on all affected VSANsExplanation License:[char] unavailable, removing LUN members, read-only attribute and re-activating active zonesets on all affected VSANs.
Recommended Action No action is required.
Message ZONE-2-ZS_LIC_FAILURE: License [chars] operation failed for license [chars]Explanation License [char] operation failed for license [char].
Recommended Action No action is required.
Message ZONE-2-ZS_LUN_DISABLING_FAILED: license expiry handling failed for VSAN [dec]Explanation License expiry handling failed for VSAN [dec].
Recommended Action No action is required.
Message ZONE-2-ZS_LUN_MEMBER_LIMIT_EXCEEDED: The limit for maximum number of lun members exceededExplanation 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.
Message ZONE-2-ZS_MALLOC_FAILURE: Memory allocation failed for size [dec]Explanation Memory allocation is failed for size [dec] bytes.
Recommended Action Restart the process.
Message ZONE-2-ZS_MEMBER_SOFT_LIMIT_REACHED: Zone member count has reached the maximum validated limit of [dec]. Creation of any more members could potentially destabilize the fabric.Explanation The number of zone members configured has exceeded the validated number of members: [dec] allowed across all VSANs. Creation of any more zones could potentially destabilize the fabric.
Recommended Action Make sure the number of zone members is less than the validated limit allowed across all VSANs.
Message ZONE-2-ZS_MEMBER_HARD_LIMIT_EXCEEDED: Maximum configurable unique zone member limit of [dec] reached. Creation of any more zone members is not supported.Explanation The number of members configured has exceeded the maximum number of members: [dec] 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.
Message ZONE-2-ZS_MERGE_ADJ_NO_RESPONSE: Adjacent switch not responding, isolating interface [chars]Explanation Interface [chars] isolated due to adjacent switch not responding to Zone Server requests.
Recommended Action Flap the interface.
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.
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.
Message ZONE-2-ZS_MERGE_UNKNOWN_FORMAT: Unknown format, isolating interface [chars]Explanation Interface [chars] isolated due to unknown format in merge request.
Recommended Action Set the interoperability mode to same value on both switches.
Message ZONE-2-ZS_MTS_OPER_FAILED: MTS [chars] operation failed: [chars]Explanation Zone Server MTS [chars] operation failed: [chars].
Recommended Action No action is required.
Message ZONE-2-ZS_NO_RSCN_ON_SW_CARD: Devices on Module [dec] will not be receiving RSCN as [chars]Explanation Devices on Module [dec] will not be receiving RSCN as [chars].
Recommended Action Enable Zone Based RSCN
Message ZONE-2-ZS_PORT_SWAP_FAILURE: Port swap operation failedExplanation Port swap operation failed.
Recommended Action No action is required.
Message ZONE-2-ZS_PSS_VER_MISMATCH: PSS version mismatch URL: [chars] (expected [chars], got [chars])Explanation Configuration version mismatch. PSS URL [chars]. Expected version [chars], stored version [chars].
Recommended Action Upgrade/Downgrade to expected version.
Message ZONE-2-ZS_SHARED_DB_INIT_FAILED: Zone Server shared DB initialization failed: [chars].Explanation Zone Server shared DB initialization failed.
Recommended Action No action is required.
Message ZONE-2-ZS_ZONE_SOFT_LIMIT_REACHED: Zone count has reached the maximum validated limit of [dec]. Creation of any more zones could potentially destabilize the fabric.Explanation The number of zones configured has exceeded the validated number of zones: [dec] allowed across all vsan. Creation of any more zones could potentially destabilize the fabric.
Recommended Action Recommended Action Make sure the number of zones is less than the validated limit allowed across all vsan.
Message ZONE-2-ZS_TCAM_BROADCAST_ZONE_DISABLED: Broadcast zoning disabled: Reason: Hard zoning disabledExplanation Broadcast zoning disabled: Reason: Hard zoning disabled due to TCAM programming failure.
Recommended Action No action is required.
Message ZONE-2-ZS_TCAM_LUN_ZONING_DISABLED: LUN zoning disabled: Reason: Hard zoning disabledExplanation LUN zoning disabled: Reason: Hard zoning disabled due to TCAM programming failure.
Recommended Action No action is required.
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.
Recommended Action No action is required.
Message ZONE-2-ZS_TCAM_READ_ONLY_ZONE_DISABLED: Read-only zoning disabled: Reason: Hard zoning disabledExplanation Read-only zoning disabled: Reason: Hard zoning disabled due to TCAM programming failure.
Recommended Action No action is required.
Message ZONE-2-ZS_TCAM_SWITCHED_TO_SOFT_ZONING_MODE: Switched to soft zoning: Reason: Hard zoning disabledExplanation Switched to soft zoning: Reason: Hard zoning disabled due to TCAM programming failure.
Recommended Action No action is required.
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].
Recommended Action No action is required.
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 RSCNExplanation 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 No action is required.
Message ZONE-2-ZS_ZONE_SET_LIMIT_EXCEEDED: The limit for maximum number of zonesets exceededExplanation 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 vsan.
ZONE-3
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 No action is required.
Message ZONE-3-ZS_ACTIVATION_FAILED_DUE_TO_QOS_DISABLED: Activation failed due to qos not enabledExplanation Activation of zoneset failed due to qos not enabled
Recommended Action Make sure qos is enabled and reactivate the zoneset in vsan.
Message ZONE-3-ZS_MGMT_SEC_SDB_ERR: [chars] : [chars].Explanation FC CT Mgmt Security shared db operation: [chars]: [chars].
ZONE-4
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 No action is required.
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 No action is required.
Message ZONE-4-ZS_BROADCAST_LUN_WARNING: LUN member(s) and Broadcast attribute are present in zone [chars] in vsan [dec]. Broadcast violations can occur for LUN members.Explanation Broadcast violations can happen in zone [chars] in vsan [dec] since it has LUN zone members.
Recommended Action No action is required.
Message ZONE-4-ZS_CHANGE_LC_UPGRADE_IN_PROGRESS: Change protocol request is received from domain [dec] when linecard upgrade is in progressExplanation A change request has been received from domain [dec] when a linecard upgrade is in progress. The change request is rejected.
Recommended Action No action is required.
Message ZONE-4-ZS_DB_WARNING: [chars]Explanation Database operation warning: [chars].
Recommended Action No action is required.
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].
Recommended Action No action is required.
Message ZONE-4-ZS_FC2_OPER_FAILED: FC2 [chars] operation failed: [chars]Explanation Zone Server FC2 [chars] operation failed: [chars].
Recommended Action No action is required.
Message ZONE-4-ZS_IF_PORT_MODE_CONFLICT: Port mode conflict for if [chars]Explanation Port mode conflict for if [chars]
Recommended Action Shutdown/no shutdown the interface
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].
Recommended Action No action is required.
Message ZONE-4-ZS_LC_UPGRADE_CHANGE_IN_PROGRESS: Linecard upgrade request is received when change protocol is in progressExplanation 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 No action is required.
Message ZONE-4-ZS_LICENSE_EXPIRY_WARNING: Feature [chars] evaluation license [chars] expiry in [dec] daysExplanation Feature [chars1] will exceed its evaluation time period in [dec] days and will be shutdown unless a permanent license [chars2] is installed.
Recommended Action Please install the license file to continue using the feature.
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]
Recommended Action No action is required.
Message ZONE-4-ZS_MGMT_SEC_RJT: FC CT Management Server query Rejected: [chars]. from FCID [hex]Explanation mgmt-security has rejected FC CT Management Server query: [chars]. from FCID [hex].
Recommended Action No Action is required.
Message ZONE-4-ZS_NON_INTEROPERABLE_ZONE_SET: Non inter operable active zoneset present on VSAN [dec] in interoperability modeExplanation Active zoneset has non inter operable 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 inter operable members (PWWN).
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].
Recommended Action No action is required.
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 No action is required.
Message ZONE-4-ZS_TOO_MANY_ALIAS_IN_CURRENT_INTEROP_MODE: Too many aliases in current interoperability modeExplanation 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.
Message ZONE-4-ZS_UNSUPPORTED_MEMBER_IN_CURRENT_INTEROP_MODE: Unsupported member present in active or full zoneset in current interoperability modeExplanation 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
Message ZONE-5-ZS_EXPORT_IMPORT_COMPLETE: [chars] operation completedExplanation [chars] (Export/Import) operation completed.
Recommended Action No action is required.
Message ZONE-5-ZS_POLICY_CHANGE: Default zoning policy changed to [chars]Explanation Default zoning policy changed to (permit/deny).
Recommended Action No action is required.
Message ZONE-5-ZS_ZONE_SET_ACTIVATED: Zoneset [chars] activatedExplanation Zoneset [chars] activated.
Recommended Action No action is required.
Message ZONE-5-ZS_ZONE_SET_DEACTIVATED: Zoneset deactivatedZONE-6
Message ZONE-6-LZ_BECAME_ACTIVE: LUN/Read-only zoning process became ACTIVE from standby modeExplanation The LUN/Read-only zoning process on the standby supervisor became active.
Recommended Action No action is required.
Message ZONE-6-LZ_BECAME_STDBY: LUN/Read-only zoning process became STANDBY from active modeExplanation The LUN/Read-only zoning process became standby from active mode.
Recommended Action No action is required.
Message ZONE-6-LZ_FAILED_TO_SEND_HEARTBEAT: LUN/Read-only zoning process failed to send heartbeat to system manager: Reason=[chars]Explanation The LUN/Read-only zoning process was unable to send heartbeat to the system manager.
Recommended Action No action is required.
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 No action is required.
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 No action is required.
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 No action is required.
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 No action is required.
Message ZONE-6-LZ_SERVICE_UP: LUN/Read-only zoning Process initialized [chars]Explanation The LUN/Read-only zoning process is up. The process was initialized in [char] mode.
Recommended Action No action is required.
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 No action is required.
Message ZONE-6-ZS_CHANGE_ACA_REJECTED: ACA received from remote domain [dec] is rejectedExplanation 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.
Message ZONE-6-ZS_FC2_OPER_INFO: FC2 [chars] operation failed: [chars]Explanation Zone Server FC2 [chars] operation failed: [chars].
Recommended Action No action is required.
Message ZONE-6-ZS_INIT_PROCESS: Zone Server process started [chars] at [chars]Explanation Zone Server process started in [chars] (stateless/stateful) mode at time [chars].
Recommended Action No action is required.
Message ZONE-6-ZS_INIT_WARNING: [chars]Explanation Warning during Zone Server Initialization: [chars].
Recommended Action No action is required.
Message ZONE-6-ZS_INVALID_MEMBER: Invalid member [dec] [chars]Explanation Invalid member type [dec] [chars] received from the API call.
Recommended Action No action is required.
Message ZONE-6-ZS_MGMT_SERVER_REQ: ZS received FC CT Mgmt Server [chars]. Command code [hex], from FCID [hex].Explanation FC CT request has been received from Management Server. It is [chars]. Command code [hex], from FCId [hex]
Recommended Action No Action is required.
Message ZONE-6-ZS_UNKNOWN_LIC_FEATURE: [chars]Explanation Zone Server received an event for an known licensing feature: [chars].
Feedback