The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Explanation TACACS+ daemon is exiting.
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.
Explanation Notifying Tacacs+ server monitor status change
Recommended Action No action is required.
Error Message TACACS-5-TACACS_NOTIFICATION: [chars]Explanation TACACS+ notification
Recommended Action No action is required.
Error Message TACACS-5-TACACS_SERVER_STATUS: [chars] server [chars] with auth-port [dec] and acct-port [dec] status has changed from [chars] to [chars]. Server was in previous-state for [chars], and total dead time of the server is [chars]Explanation Accounting Message
Recommended Action No action is required.
Error Message TACACS-6-TACACS_MESSAGE: [chars]Explanation TCAP process has failed to allocate memory.
Recommended Action Please perform a showtcapevent-history'tocollectmoreinformation.'
Error Message TCAP-2-PROC_DN: Process is shutting down: [chars]Explanation TCAP process is exiting.
Recommended Action Please perform a showtcapevent-history'tocollectmoreinformation.'
Error Message TCAP-2-PROC_INITFAIL: Process initialization failed due to [chars].Explanation TCAP process has failed initialization.
Recommended Action Please perform a showtcapevent-history'tocollectmoreinformation.'
Explanation TL Port Manager initialization failed. [chars] explains the reason for the failure.
Explanation TL Port Manager is out of dynamic memory. [chars] specifies the context where the failure occured.
Recommended Action No action is required.
Error Message TLPORT-3-FC2ERROR: [chars]Explanation TL Port Manager encountered an FC2 error. [chars] specifies the context where the error occured.
Recommended Action No action is required.
Error Message TLPORT-3-GENERROR: [chars]Explanation TL Port Manager encountered a general error, one that does not fall in any of the above categories. [chars] describes the error and its context.
Recommended Action No action is required.
Error Message TLPORT-3-MTSERROR: [chars]Explanation TL Port Manager encountered an MTS error. [chars] specifies the context where the error occured.
Recommended Action No action is required.
Error Message TLPORT-3-PSSERROR: [chars]Explanation TL Port Manager encountered a PSS error. [chars] specifies the context where the failure occured.
Explanation TL Port cache is currently fully populated with active entries. Hence, there is no available cache space to be assigned any newly created alpa entry on a TL Port. This is an informational message.
Explanation TL Port Manager was created successfully and is up and running. This is an informational message.
Recommended Action No action is required.
Error Message TLPORT-6-MGREXIT: Translation Port Manager shutting down gracefully.Explanation TL Port Manager is shutting down gracefully. This is an informational message.
Recommended Action No action is required.
Error Message TLPORT-6-PORTDOWN: Translation Port [chars] DOWN.Explanation A port configured as TL Port is DOWN and out of operation. [chars] is the interface-id string that identifies the TL Port. This is an informational message.
Recommended Action No action is required.
Error Message TLPORT-6-PORTUP: Translation Port [chars] UP.Explanation A port configured as TL Port is UP and operational. [chars] is the interface-id string that identifies the TL Port. This is an informational message.
Explanation The DPP associated with the Virtual Target has crashed
Recommended Action No action is required.
Error Message TPC-SLOT#-5-LOG_ERR_TPC_VT_ACT_FAILED: VSAN :[dec] VT pWWN :[chars] VT Activate failedExplanation The activate step for a Virtual Target has failed
Recommended Action No action is required.
Error Message TPC-SLOT#-5-LOG_ERR_TPC_VT_CREATE_FAIL: VSAN :[dec] VT pWWN :[chars] VT and NPort creation FAILED !!!Explanation The Virtual Target and nport creation failed
Recommended Action No action is required.
Error Message TPC-SLOT#-5-LOG_ERR_TPC_VT_DESTROYED: VSAN :[dec] Virtual Target : [chars] DeletedExplanation The Virtual Target in the associated VSAN is being destroyed
Recommended Action No action is required.
Error Message TPC-SLOT#-5-LOG_ERR_TPC_VT_VSAN_DOWN: VSAN :[dec] VT pWWN :[chars] VSAN downExplanation The VSAN where the Virtual Target is configured is down
Explanation Critical TTY daemon error.
Recommended Action No action is required.
Error Message TTYD-2-TTYD_MTS: TTYD Message queue [dec] [chars]Explanation TTY daemon message error.
Recommended Action No action is required.
Error Message TTYD-2-TTYD_SDWRAP: TTYD Debug Facility error [dec] [chars]Explanation The tty daemon miscellaneous message.
Recommended Action No action is required.
Error Message TTYD-6-TTYD_PSS: TTYD Store error:[hex] [chars]Explanation Failed to enable feature tunnel, reason [char] ([int])
Recommended Action Check the failure reason and take appropriate action to fix the failure. if unable to fix, please capture "show tech-support tunnel"
Error Message TUNNEL-2-TM_F2_ONLY_VDC: Tunnel feature is not supported in F2 only VDCExplanation Tunnel feature is not supported in F2 only VDC
Recommended Action Disable the Tunnel feature by the CLI "no feature tunnel"
Explanation Hardware programming failed for tunnel [num] interface
Recommended Action Try shutdown'and'noshutdown'undertunnelinterfacesubmodeaftersometime.ifstilltunnelinterfacedoesn'tcomeupcaptureshowtech-supporttunneltoidentifytheissue'
Explanation [chars] DF programming failed! status [int]
Recommended Action Capture "show tech-support tunnel " to identify why df flag programing failed
Error Message TUNNEL-4-TM_DF_PROGRAMMING: Programming [chars] DF(dont fragment) df.sel [dec] df.val [dec]Explanation Programming [chars] DF df.sel [int] df.val [int]
Recommended Action No action is required.
Error Message TUNNEL-4-TM_MTU_PROGRAMMING_FAILED: [chars] mtu [dec] programming failed! status [hex]Explanation [chars] mtu [int] programming failed! status [int]
Recommended Action Capture show "tech-support tunnel" to identify why MTU programming as failed. tunnel interface will used default mtu value
Error Message TUNNEL-4-TM_MTU_PROGRAMMING: Programming [chars] mtu [dec]...Explanation Interface [char] counters is cleared
Recommended Action No action is required.
Error Message TUNNEL-5-IF_CREATED: Interface [chars] is createdExplanation Interface [char] is created
Recommended Action No action is required.
Error Message TUNNEL-5-IF_CREATE_FAILED: Interface [chars] creation failed due to [[hex]] [chars]Explanation Interface [char] is creation failed due to [int] [char]
Recommended Action No action is required.
Error Message TUNNEL-5-IF_DELETED: Interface [chars] is deletedExplanation Interface [char] is deleted
Recommended Action No action is required.
Error Message TUNNEL-5-IF_STATE_UPDATE: Interface [chars] is [chars] reason [chars]Explanation Interface [char] is [char] reason [char]
Recommended Action No action is required.
Error Message TUNNEL-5-PPF_SESSION_FAILED: session id %llx type [chars] for [chars] failed error [hex] [chars]Explanation Session id [int] type [char] for [char] failed error [int] [char]
Recommended Action No action is required.
Error Message TUNNEL-5-TM_DISABLED: Tunnel DisabledExplanation Tunnel Service Disabled
Recommended Action No action is required.
Error Message TUNNEL-5-TM_ENABLED: Tunnel EnabledExplanation 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.
Error 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.
Explanation Error while communicating with the dcefib library
Explanation U2RIB Service Disabled
Recommended Action No action is required.
Error Message U2RIB-5-U2RIB_ENABLED: U2RIB EnabledExplanation U2RIB has created its internal state stateless/stateful [chars].
Explanation A softare error occurred in UDLD processing associated with a specific interface.
Recommended Action LOG_STD_SH_TECH_ACTION
Error 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
Error Message UDLD-3-UDLD_INTERNAL_ERROR: UDLD internal error: [chars]Explanation A softare sanity check failed in the course of UDLD processing.
Recommended Action LOG_STD_SH_TECH_ACTION
Error Message UDLD-3-UDLD_INTERNAL_IF_ERROR: UDLD internal error, interface [chars]: [chars]Explanation A softare sanity check failed in the course of UDLD processing.
Explanation UDLD gwrap count reached high level, show tech udld is needed to debug it.
Recommended Action LOG_STD_SH_TECH_ACTION
Error Message UDLD-4-UDLD_NEIGHBOR_MISMATCH: UDLD neighbor mismatch detected, exp: [chars], rec [chars]. Please collect debug info using: http://zed.cisco.com/confluence/display/KGP/UDLD+debugExplanation An interface will be disabled because UDLD protocol detected a nieghbor mismatch condition on the interface indicated. Cause is likely due to bad interface hardware or cable misconfiguration. User should investigate.
Recommended Action LOG_STD_SH_TECH_ACTION
Error Message 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
Error Message UDLD-4-UDLD_PORT_RESET: UDLD reset interface [chars]Explanation A port which had been disabled for UDLD has been reset.
Explanation UDLD Service Aggressive
Recommended Action No action is required.
Error Message UDLD-5-UDLD_DISABLED: UDLD DisabledExplanation UDLD Service Disabled
Recommended Action No action is required.
Error Message UDLD-5-UDLD_ENABLED: UDLD EnabledExplanation UFDM download timer expired. Collect show tech-support forwarding l3 unicast for futher analysis.
Recommended Action No action is required.
Error 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 futher analysis.
Recommended Action No action is required.
Error Message UFDM-2-INTERNAL_ERROR: Internal error: [chars], collect output of show tech-support fowarding l3 unicast... commandExplanation UFDM hit a internal error. Collect show tech-support forwarding l3 unicast for futher analysis.
Explanation Vdc_mgr has hit a critical error
Recommended Action A critical error has been hit within vdc_mgr. Please check show vdc to determine the state of the vdcs
Error Message VDC_MGR-2-VDC_LIC_WARN_EXP: WARNING License for vdcs is about to expire! VDCs will be deleted if license is allowed to expireExplanation VDC license is close to expire
Recommended Action Please contact your sales representative to obtain a license
Error Message VDC_MGR-2-VDC_LIC_WARN: Service using grace period will be shutdown in [dec] day(s)Explanation The license for vdcs is not installed and currently running in the grace period
Recommended Action Vdcs will continue to work within the grace period, but obtaining a license is reccomended
Error Message VDC_MGR-2-VDC_OFFLINE: vdc [dec] is now 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
Error 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.
Error Message VDC_MGR-2-VDC_UNALLOCATED: Module [dec] is unsupported by the current vdc and some of its ports have been placed in the unallocated pool.Explanation The module is of a type unsupported by the current vdc. You can see port membership by 'show vdc membership' and check the current vdc's configuration via 'show vdc'
Recommended Action Allocate interfaces to a vdc that supports this module type or change the current vdc to support this module type via the 'limit-resource module-type' command
Error Message VDC_MGR-2-VDC_UNGRACEFUL: vdc_mgr: Ungraceful cleanup request recieved for vdc [dec], restart count for this vdc is [dec] restarts within the last 5 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
Explanation Writing to a file failed probably due to no space.
Error Message VDC_MGR-3-VDC_ERROR: vdc_mgr: [chars]Explanation Vdc_mgr has recieved bad data but will try to continue
Recommended Action Vdc_mgr will attempt to correct the error at hand
Explanation Allowed feature-set config has changed
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message VDC_MGR-5-VDC_MODULETYPE: vdc_mgr: Module type changed to [chars]Explanation This vdc has been changed to support only the the type of modules listed
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_STATE_CHANGE: vdc [dec] state changed to [chars]Explanation A vdc state change has happened. This is most likely due to a configuration change.
Recommended Action No action is required.
Error Message VDC_MGR-5-VDC_SWMODULETYPE: vdc_mgr: System Module type changed to [chars]Explanation This switch has been changed to support only the the type of modules listed
Explanation No action is required.
Error Message VEC-SLOT#-3-LOG_GUID_MISMATCH: GUID Mismatch DPP [dec] PWWN [chars] lun [chars] Expected [chars] Read [chars]Explanation The disk GUID verification performed by the DPP failed. Access to the disk is denied.
Explanation An Event is received for a State in the VEC DPP Monitor FSM which should not have occured
Recommended Action No action is required.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_DPRLI_FSM: Illegal Event [chars] in State [chars] FSM [chars]Explanation An Event is received for a State in the VEC DPRLI FSM which should not have occured
Recommended Action No action is required.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_GID_FSM: Illegal Event [chars] in State [chars] FSM [chars]Explanation An Event is received for a State in the VEC Guid ID FSM which should not have occured
Recommended Action No action is required.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_HOST_LMAP_FSM: Illegal Event [chars] in State [chars] Host VSAN :[dec] Host pWWN :[chars] VEP pWWN :[chars]Explanation An Event is received for a State in the VEC HOST LMAP XP FSM which should not have occured
Recommended Action No action is required.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_HOST_LOGO: Logging out Host [VSAN :[dec] pWWN :[chars]] logged in to VEP [pWWN :[chars]]. Reason : Host not 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.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_HOST_XP_FSM: Illegal Event [chars] in State [chars] Host VSAN :[dec] Host pWWN :[chars] VEP pWWN :[chars]Explanation An Event is received for a State in the VEC HOST XP FSM which should not have occured
Recommended Action No action is required.
Error 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.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_NPORT_FSM: Illegal Event [chars] in State [chars] FSM [chars]Explanation An Event is received for a State in the VEC NPORT FSM which should not have occured
Recommended Action No action is required.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_PID_FSM: Illegal Event [chars] in State [chars] FSM [chars]Explanation An Event is received for a State in the VEC PID FSM which should not have occured
Recommended Action No action is required.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_TARGET_FSM: Illegal Event [chars] in State [chars] FSM [chars]Explanation An Event is received for a State in the VEC TARGET FSM which should not have occured
Recommended Action No action is required.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_TCAM_MON_FSM: Illegal Event [chars] in State [chars] DPP :[dec]Explanation An Event is received for a State in the VEC TCAM MON FSM which should not have occured
Recommended Action No action is required.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_TP_FSM: Illegal Event [chars] in State [chars] Host VSAN :[dec] TP nWWN :[chars] TP pWWN :[chars]Explanation An Event is received for a State in the VEC TP FSM which should not have occured
Recommended Action No action is required.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VEP_FSM: Illegal Event [chars] in State [chars] Host VSAN :[dec] VEP nWWN :[chars] VEP pWWN :[chars]Explanation An Event is received for a State in the VEC VEP FSM which should not have occured
Recommended Action No action is required.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VEP_ILC_LIMIT: VEP [VSAN :[dec] pWWN :[chars]] could not be created. Reason : ILC VEP limit [dec] reachedExplanation The VEP could not be created as the per ILC limit of VEPs has been reached
Recommended Action No action is required.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VLUN_FSM: Illegal Event [chars] in State [chars] FSM [chars]Explanation An Event is received for a State in the VEC VLUN FSM which should not have occured
Recommended Action No action is required.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VO_FSM: Illegal Event [chars] in State [chars] FSM [chars]Explanation An Event is received for a State in the VEC VO FSM which should not have occured
Recommended Action No action is required.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VSAN_FSM: Illegal Event [chars] in State [chars] VSAN [dec]Explanation An Event is received for a State in the VEC VSAN FSM which should not have occured
Recommended Action No action is required.
Error Message VEC-SLOT#-5-LOG_ERR_VEC_VSAN_XCHG_FSM: Illegal Event [chars] in State [chars] VES IP Addr [chars]Explanation An Event is received for a State in the VEC VSAN XCHG FSM which should not have occured
Recommended Action No action is required.
Error 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 occured. Recovery will be preformed if appropriate.
Recommended Action No action is required.
Error 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 occured. Recovery will be preformed if appropriate.
Explanation 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.
Explanation The VEDB library has exited due to [char]. The process has probably been restarted automatically.
Recommended Action No action is required.
Error Message VEDB_MGR-6-SERVICE_UP: Initialized [chars]Explanation The VEDB library is up and ready to accept client requests The service was initialized in [char] mode.
Explanation The VES maximum volume configuration was exceeded. Volume will be virtualized by the cpp.
Explanation An VERIFY MISMATCH Event is received for a State in the VES PATH FSM which should not have occured
Recommended Action No action is required.
Error Message VES-SLOT#-5-LOG_ERR_VES_VEP_FSM: Illegal Event [chars] in State [chars] Host VSAN :[dec] VEP pWWN :[chars]Explanation An Event is received for a State in the VES VEP FSM which should not have occured
Recommended Action No action is required.
Error Message VES-SLOT#-5-LOG_ERR_VES_VSAN_FSM: Illegal Event [chars] in State [chars] VSAN [dec]Explanation An Event is received for a State in the VES VSAN FSM which should not have occured
Recommended Action No action is required.
Error Message VES-SLOT#-5-LOG_ERR_VES_VSAN_XCHG_FSM: Illegal Event [chars] in State [chars] VEC IP Addr [chars]Explanation An Event is received for a State in the VES VSAN XCHG FSM which should not have occured
Recommended Action No action is required.
Error 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 occured. Recovery will be preformed if appropriate.
Recommended Action No action is required.
Error 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 occured. Recovery will be preformed if appropriate.
Explanation Miscellaneous target error
Recommended Action No action is required.
Error Message VFC-3-VFC_TGT_ERROR: Target error:[chars] 0x%llxExplanation VLAN Manager Critical Message
Recommended Action No action is required.
Error Message VLAN_MGR-2-FABRIC_DYNAMIC_CORE_VLAN_RANGE_REMOVED: Fabric dynamic and core VLAN ranges removed. Please delete VLANs [chars] in the rangesExplanation VLAN Manager Core VLAN Range Removal Message
Recommended Action No action is required.
Error Message VLAN_MGR-2-SYS_TRUNK_DYN_VLAN_FEATURE_DISABLE: [chars]Explanation VLAN Manager System Default Trunk Allocate Vlan Dynamic Feature Configuration Disable Message
Explanation VLAN Manager Notification Message
Recommended Action No action is required.
Error Message VLAN_MGR-5-RESERVED_VLAN_RANGE_CHANGED: New Reserved VLAN Range Configured From VLAN [dec] to VLAN [dec]Explanation VLAN Manager Reserved VLAN Reconfiguration Message
Recommended Action No action is required.
Error Message VLAN_MGR-6-VLAN_CREATED: VLAN [dec], createdRecommended Action No action is required.
Error Message VLAN_MGR-6-VLAN_MGR_STATEFULL_RESTART: VLAN Manager statefull restartExplanation VLAN Manager statefull restart
Recommended Action No action is required.
Error Message VLAN_MGR-6-VLAN_MGR_STATELESS_RESTART: VLAN Manager stateless restartExplanation VLAN Manager stateless restart
Recommended Action No action is required.
Error Message VLAN_MGR-6-VLAN_OPER_STATUS_CHG: VLAN [dec], status changed to [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-managerslogsforthecauseofthefailure.Inthesuccessfulcase,thisnotificationcanbeignored.'
Error 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 Virt-manager logs and scan them for the cause.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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 Virt-manager logs and scan them for the cause.
Error Message VMAN-2-DEACT_FOR_ISSU: [chars] Max ([dec]s)Explanation An ISSU event is pending. Any active VMs will be automatically deactivated to allow ISSU preprocessing to validate the environment. Any ISSU-deactivated VMs will be automatically restarted if the ISSU is cancelled.
Recommended Action None. Allow the ISSU to continue and the VMs will restart when the ISSU completes; or cancel the ISSU and vman will automatically restart the VMs.
Error 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.
Error 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 Harddisk, 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.
Error 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.
Error 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
Error Message VMAN-2-HA_STATE: [chars] [chars] [chars] [chars]Explanation VMAN tries to detect the role/slot of various nodes on HA events from the platform. If any of those event callbacks fail, this notification would be raised.
Recommended Action In the failed case, check Virt-managerslogsforthecauseofthefailure.CheckfortheHAeventerrormsgandrootcausethesame.'
Error 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.
Error Message VMAN-2-HA_SYNC_THREAD_STATE: HA remote sychronize thread has failed and exited.Explanation VMAN tries to remote sync the OVA repository to all online nodes using a separate thread. If that thread fails, this notification would be raised.
Recommended Action In the failed case, check Virt-managerslogsforthecauseofthefailure.Checkforthepthreaderrormsgandrootcausethesame.'
Error 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.
Error 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.
Error 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.
Error 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.
Error Message VMAN-2-INSTALL_LOG: [chars] [chars] [chars] [chars]Explanation The installation log of the named virtual service, is to provide more information about long running operation, that could affect the control of CLI
Recommended Action No action is required
Error 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(harddisk) detection.
Recommended Action After VMAN exceeds the maximum retry limit, verify if install media (harddisk) is accessible and retry the installation again.
Error Message VMAN-2-INSTALL_STATE: [chars] [chars]'[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-managerslogsforthecauseofthefailure.Inthesuccessfulcase,thisnotificationcanbeignored.'
Error 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.
Error 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.
Error 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.
Error Message VMAN-2-INVALID_UNPROV_MSG: Failed to process virtual service unprovision messageExplanation The virtual service unprovision 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 unprovision of the virtual service. Collect the Virt-manager logs and scan them for the cause.
Error 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.
Error 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
Error 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.
Error 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.
Error 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.
Error Message VMAN-2-MOVE_STATE: [chars] [chars]'[chars][chars]'Explanation The move of the core or log file of the named virtual service has as been successful or failed as notified by Virt-manager.
Recommended Action In the failed case, check Virt-managerslogsforthecauseofthefailure.Inthesuccessfulcase,thisnotificationcanbeignored.'
Error 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
Error 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.
Error 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.
Error 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.
Error Message VMAN-2-RESET_FORCE: Virtual Services non-recoverable reset command processedExplanation A virtualserviceresetforce'commandhasbeenenteredandprocessed.Thisactioninitiatesacleanupoflastresort.OccasionallyaVMwillgetintoanunrecoverablestatethatpreventsitfromactivatingbutalsofromuninstalling.Thisisarareeventbutwhenithappenstheonlyresortmaybetoremovethe.confcontrolfileandreboot,whichforcesacleanupofallpreviouslyinstalledVMfilesandartifacts.Notethatoncethiscommandisused,currentVMsareconsideredtobeinanunstableorunpredictablestate,andallfutureinstall,uninstall,upgrade,andactivationcommandswillbeblocked.'
Recommended Action Once the command is entered and accepted, there is no recourse but to restart the system.
Error Message VMAN-2-RSYNC_STATE: [chars] [chars] [chars] [chars]Explanation VMAN tries to remote sync the virtual-instance configuration file and the OVA repository to all online nodes. If rsync fails even after consecutive retries, this notification would be raised.
Recommended Action In the failed case, check Virt-managerslogsforthecauseofthefailure.Checkforthersyncerrorcodeandrootcausethesame.'
Error 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.
Error 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.
Error Message VMAN-2-START_FAILED: Virtual Service[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.
Error Message VMAN-2-UNINSTALL_ALL_VMS: All Virtual Services are being uninstalled [chars][chars] [chars]Explanation All virtual services are being uninstalled by Virt-manager.
Recommended Action Examine the reason given as to why all virtual services are being uninstalled for more information. If the reason indicated is due to some error condition, check Virt-managerslogsforthecauseofthefailure.'
Error Message VMAN-2-UPGRADE_LOG: [chars] [chars] [chars] [chars]Explanation The upgrade log of the named virtual service, is to provide more information about long running operation, that could affect the control of CLI
Recommended Action No action is required
Error 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.
Error 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.
Error Message VMAN-2-VIRT_INST_CRIT: VIRTUAL SERVICE [chars] LOG: [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
Error 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.
Error 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.
Error Message VMAN-2-VIRT_INST_LOG_UNTHROTTLE: Failed to unthrottle the log for virtual service [chars]Explanation The named virtual service had sent overwhelming sys log messages and its log had been throttled as a result, but system has failed to unthrottle it for some reason.
Recommended Action For debugging collect the virt-manager logs and scan them for the cause.
Error 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.
Error 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.
Error 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.
Explanation Persistent Storage Service handling error
Recommended Action Collect the Virt-manager logs and scan them for the cause.
Error 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.
Error 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.
Error Message VMAN-3-VIRT_INST_ERR: VIRTUAL SERVICE [chars] LOG: [chars]Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Explanation The package certificate signing level global setting has been changed via configuration under the virtual-service global sub-mode.
Recommended Action Ensure that this setting has been changed as expected by an authorized user.
Error Message VMAN-4-VIRT_INST_WARN: VIRTUAL SERVICE [chars] LOG: [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
Error Message VMAN-4-VIRT_SERV_LIBVIRTD_WARN: VMAN not able to connect to the libvirt daemon after [dec]'attempts'Explanation VMAN has been unable to connect to the libvirt daemon. Virtualization services will not be available until this connection is made.
Recommended Action Collect the logs produced by showvirttech''
Error 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.
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
Error Message VMAN-5-PACKAGE_SIGNING_LEVEL_ON_INSTALL: Package [chars]'forservicecontainer'[chars]'is'[chars]',[chars]'[chars]''Explanation A service container software package with the certificate signing level described is being installed.
Recommended Action Take note of the service container and software package. Verify the software package is expected to be (un)signed as described and has the appropriate contents. Uninstall the package if unsure of the package origins.
Error Message VMAN-5-VIRT_INST_NOTICE: VIRTUAL SERVICE [chars] LOG: [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
Error 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.
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Explanation The service failed to allocate a block of dynamic memory.
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.
Explanation The specified VSAN Interface has been successfully [chars].
Recommended Action No action is required.
Error Message VNI-6-STARTING: Virtual Network Interface Manager startedExplanation The service has successfully started.
Recommended Action No action is required.
Error 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.
Explanation VNSEG encountered an error in processing an MTS message. The error and message are specified in the error message
Recommended Action No action is required.
Error Message VNSEGMENT_MGR-2-RANDNUM_FAIL: [chars]Explanation There was a critical error during random number generation. [chars] indicates details of the error
Recommended Action No action is required.
Error Message VNSEGMENT_MGR-2-VNSEG_INIT: VNSEG initialization of [chars] [chars]Explanation VNSEG 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.
Error Message VNSEGMENT_MGR-2-VNSEG_ISSU_LC_RESET: VNSEG resetting LC[dec] to prevent Loops during ISSU caused by a topology change in the network. Peer on [chars] [chars] could not be DisputedExplanation This can happen as a result of a topology change in the network while the Linecard was undergoing ISSU. Since VNSEG cannot change the port state to blocking on the Linecard undergoing ISSU, it will first try to prevent the Loop by causing a Dispute on the peer ports forcing them into blocking state. But if the peer does not support Dispute mechanism, and VNSEG detects a potential Loop, it will reset the Linecard to prevent the Loop
Explanation This spanning tree port has been added
Recommended Action LOG_STD_NO_ACTION
Error Message VNSEGMENT_MGR-6-PORT_DELETED: Interface [chars], removed from [chars]Explanation This spanning tree port has been deleted
Recommended Action LOG_STD_NO_ACTION
Error Message VNSEGMENT_MGR-6-PORT_RANGE_DELETED: Interface [chars] removed from [chars]Explanation This range spanning tree logical ports has been deleted
Recommended Action LOG_STD_NO_ACTION
Error Message VNSEGMENT_MGR-6-SERVICE_UP: Initialized [chars]Recommended Action No action is required.
Error Message VNSEGMENT_MGR-6-STATE_CREATED: Internal state created [chars]Explanation VNSEG has created its internal state stateless/stateful [chars].
Explanation ASIC failure notification
Recommended Action No action is required.
Error Message VPC-2-OOB_INIT_FAIL: vPC Peer link config fail ([chars])Explanation OOB peer link config failed. due to [chars]
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message VPC-2-VPCM_FEATURE_ENABLE_FAILED: Enabling of vPCM Service failed. Please disable feature Flexlink first.Explanation Enabling of vPCM Service failed
Recommended Action No action is required.
Error Message VPC-2-VPC_ADD_L3_BKUP_VLAN_TO_PEER_GW_EXCLUDE_LIST: Exclude L3 backup routing VLAN from vpc peer-gateway config.Explanation Triggered when peer-link is F1 and peer-gateway is configured without exclude-vlan list.
Recommended Action No action is required.
Error Message VPC-2-VPC_CORE_PORT_FPATH_BUP_FAILED: Failed to bring up vPC+ peer link port [chars] in Fabric Path Port Mode - vPC+ Fabric Path switch ID not configuredExplanation VPC+ Failed to bringup peer-link - switch-ID not configured
Recommended Action No action is required.
Error 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.
Error Message VPC-2-VPC_ES_FAILED_PEERLINK_DOWN: vPC+ operations failed. Bringing down peer-link.Explanation Triggered in mcecm_em_es_failed. Bring down peer-link.
Recommended Action No action is required.
Error Message VPC-2-VPC_ES_ID_REG_FAILED: Fabricpath switch ID configuration failedExplanation Fabricpath switch ID could not be registered. This could be due to Duplicate Switch ID being configured
Recommended Action Configure a different Fabricpath switch ID
Error Message VPC-2-VPC_ES_PEER_LINK_OPERATION_FAILED: Peer-link operation failed due to SAP [dec].Explanation Triggered in mcecm_cfg_es_failed when peer-link bringup fails.
Recommended Action No action is required.
Error Message VPC-2-VPC_GRACEFUL_SUSP_ALL_VPC: Operational graceful type-1 check configuration changed, reiniting all vPCsExplanation Graceful configuration change,reinit vPCs
Recommended Action No action is required.
Error Message VPC-2-VPC_ISSU_END: Peer vPC switch ISSU end, unlocking configurationExplanation Peer vPC switch issu end
Recommended Action No action is required.
Error Message VPC-2-VPC_ISSU_START: Peer vPC switch ISSU start, locking configurationExplanation Peer vPC switch issu start
Recommended Action No action is required.
Error Message VPC-2-VPC_LC_FAIL: LC [dec] does not support required hardware for vPC; run showvdcmembershipstatus'forportstatus'Explanation Lc insertion failed
Recommended Action No action is required.
Error Message VPC-2-VPC_NON_DEF_LID: vPC+ negotiated non-default local id. Flapping orphan edge ports recommended.Explanation Triggered in mcecm_em_es_failed. Bring down peer-link.
Recommended Action No action is required.
Error Message VPC-2-VPC_PEER_LINK_FPATH_BUP_FAILED: Failed to bring up vPC+ peer link port [chars] - port [chars] is not configured as a Fabric Path portExplanation VPC+ Failed to bringup Peer-link - not in Fabric Path mode
Recommended Action No action is required.
Error 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.
Error 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.
Error Message VPC-2-VPC_SVI_EXCLUDE: vPC [dec] (interface [chars]) has up vlans [chars] which are excluded from suspension on dual-activeExplanation Global compat-check failed
Recommended Action No action is required.
Error Message VPC-3-INTF_CONSISTENCY_FAILED: In domain [dec], VPC [dec] configuration (interface [chars]) is not consistent ([chars])Explanation MCEC compat-check failed
Recommended Action No action is required.
Error Message VPC-3-PEER_UNREACHABLE: Remote Switch UnreachableRecommended Action No action is required.
Error Message VPC-3-PEER_VPC_BRINGUP_FAILED: Peer vPC [dec] bringup failed ([chars])Explanation Peer vPC bringup failed
Recommended Action No action is required.
Error Message VPC-3-VPCM_ASSERTION_FAILED: [chars]Explanation VPCM has hit an assert condition at file [chars]
Recommended Action No action is required.
Error Message VPC-3-VPCM_INIT_FAIL: vPC Manager Initialization Failed ([chars])Explanation VPCM Initialization failed. due to [chars]
Recommended Action No action is required.
Error Message VPC-3-VPCM_INTERNAL_ERR: [chars]Explanation VPCM encountered an internal error due to [chars]
Recommended Action No action is required.
Error Message VPC-3-VPCM_MTS_ERR: [chars]Explanation VPCM encountered an MTS error due to [chars]
Recommended Action No action is required.
Error Message VPC-3-VPC_BRINGUP_FAILED: vPC [dec] (interface [chars]) bringup failed ([chars])Explanation VPC bringup failed
Recommended Action No action is required.
Error 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.
Error Message VPC-3-VPC_PEER_LINK_DOWN: VPC Peer-link is down ([chars])Explanation Peer vPC configuration deleted
Recommended Action No action is required.
Error 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.
Error Message VPC-4-VPC_DELETED: vPC [dec] (interface [chars]) is deletedExplanation VPC configuration deleted
Recommended Action No action is required.
Error Message VPC-4-VPC_DISABLE_IP_REDIRECTS: peer-gateway enabled. Disabling IP redirects on all interface-vlans of this vPC domain for correct operation of this feature.Explanation Peer-gateway enabled, hence IP redirects on SVIs are disabled
Recommended Action No action is required.
Error 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.
Error Message VPC-4-VPC_PEER_LINK_DELETED: vPC Peer-link deleted. This will bringdown all vPC interfacesExplanation VPC Peer-link configuration removed
Recommended Action No action is required.
Error Message VPC-4-VPC_PEER_ROLE_CHANGE: In domain [dec], VPC peer role status has changed to [chars]Explanation VPC Peer role status changed to (Primary/Secondary
Recommended Action No action is required.
Error 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.
Error Message VPC-4-VPC_PER_VLAN_NO_SUPPORT: ISSD/ISSU to an 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.
Error Message VPC-4-VPC_REINITIALIZED: Reinitializing vpcs assuming peer deadExplanation Initializing vpcs assuming peer dead
Recommended Action No action is required.
Error Message VPC-4-VPC_ROLE_CHANGE: In domain [dec], VPC role status has changed to [chars]Explanation Global compat-check passed
Recommended Action No action is required.
Error Message VPC-5-INTF_CONSISTENCY_SUCCESS: In domain [dec], vPC [dec] configuration (interface [chars]) is consistentExplanation VPC configuration is consistent
Recommended Action No action is required.
Error Message VPC-5-PEER_KEEP_ALIVE_RECV_INT_LATEST: In domain [dec], VPC peer-keepalive received on interface [chars]Explanation VPC peer-keepalive receive interface changed
Recommended Action No action is required.
Error 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.
Error Message VPC-5-PEER_KEEP_ALIVE_SEND_INT_LATEST: In domain [dec], VPC peer-keepalive sent on interface [chars]Explanation VPC peer-keepalive send interface changed
Recommended Action No action is required.
Error 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.
Error Message VPC-5-PEER_KEEP_ALIVE_STATUS: In domain [dec], peer keep-alive status changed to [chars]Explanation Peer keep-alive (oob) status is changed to <peer-alive
Recommended Action Peer-not-alive
Error Message VPC-5-ROLE_PRIORITY_CFGD: In domain [dec], vPC role priority changed to [dec]Explanation Role priority configured
Recommended Action No action is required.
Error 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.
Error 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.
Error Message VPC-5-VPCM_DISABLED: vPC Manager disabledExplanation VPCM Service Disabled
Recommended Action No action is required.
Error Message VPC-5-VPCM_ENABLED: vPC Manager enabledExplanation VPCM Service Enabled
Recommended Action No action is required.
Error 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.
Error 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.
Error Message VPC-5-VPC_DOWN: vPC [dec] (interface [chars]) is down ([chars])Explanation VPC is down (reason)
Recommended Action No action is required.
Error Message VPC-5-VPC_PEER_LINK_UP: vPC Peer-link is upExplanation VPC Peer-link is up
Recommended Action No action is required.
Error Message VPC-5-VPC_RESTORE_TIMER_EXPIRED: vPC restore timer expired, reiniting vPCsExplanation VPC restore timer expired
Recommended Action No action is required.
Error Message VPC-5-VPC_RESTORE_TIMER_START: vPC restore timer started to reinit vPCsExplanation VPC restore timer start
Recommended Action No action is required.
Error Message VPC-5-VPC_ROLE_PREMPT: In domain [dec], vPC role pre-emption triggeredExplanation VPC preemption triggered
Recommended Action No action is required.
Error Message VPC-5-VPC_UP: vPC [dec] (interface [chars]) is upExplanation Locking failed on peer switch
Recommended Action No action is required.
Error 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.
Error Message VPC-6-PEER_VPC_CFGD: peer vPC [dec] is configuredRecommended Action No action is required.
Error Message VPC-6-PEER_VPC_DOWN: Peer vPC [dec] is down ([chars])Recommended Action No action is required.
Error Message VPC-6-PEER_VPC_UP: Peer vPC [dec] is upRecommended Action No action is required.
Error Message VPC-6-STATS_CLEARED: vPC Statistics ClearedExplanation VPC statistics cleared
Recommended Action No action is required.
Error Message VPC-6-TRACK_OBJ_CONFIGURED: In domain [dec], track object configured [dec]Explanation VPC track object configured
Recommended Action No action is required.
Error Message VPC-6-TRACK_OBJ_DELETED: In domain [dec], track object deletedExplanation VPC track object deconfigured
Recommended Action No action is required.
Error Message VPC-6-TYPE1_PARAM_CHANGED: TYPE-1 parameters changed: [chars]Explanation Type-1 Parameters Changed
Recommended Action No action is required.
Error Message VPC-6-VPCM_INTERNAL_INFO: [chars]Explanation VPCM got an internal info [chars]
Recommended Action No action is required.
Error Message VPC-6-VPC_ALLOWED_VLAN_CHANGED: vPC [dec] (interface [chars]) operational vlans changedExplanation Operational vlans changed on vPC
Recommended Action No action is required.
Error Message VPC-6-VPC_CFGD: vPC [dec] (interface [chars]) is configuredRecommended Action No action is required.
Error Message VPC-6-VPC_CONSISTENCY_CHECK_BYPASS: Bypassing consistency check for vPC: [dec] (interface [chars])Explanation Bypassing consistency check for vpcs
Recommended Action No action is required.
Error 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.
Error Message VPC-6-VPC_DOMAIN_ID_CFGD: vPC domain-id configured to [dec]Explanation VPC domain-id configured
Recommended Action No action is required.
Error Message VPC-6-VPC_ES_EGRESS_DF_STATE_CHANGED: Egress designated forwarder state changed from [chars] to [chars] for vPC [dec].Explanation DF state changed for some vPC.
Recommended Action No action is required.
Error Message VPC-6-VPC_ES_ID_CFGD: Fabricpath switch ID [dec] configuredExplanation Fabricpath switch ID configured
Recommended Action No action is required.
Error Message VPC-6-VPC_ES_ID_REMOVED: Fabricpath switch ID [dec] removedExplanation Fabricpath switch ID removed
Recommended Action No action is required.
Error Message VPC-6-VPC_PEER_LINK_CFGD: vPC peer-link is configuredExplanation VPC Peer-link is configured
Recommended Action No action is required.
Error 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
Explanation The VP Manager has encountered an critical error. The description of error is [str.]
Recommended Action No action is required.
Error 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.
Error 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.
Error Message VPM-2-VPMON_CRIT: [chars] [dec]Explanation VPMON daemon critical message
Recommended Action No action is required.
Error Message VPM-2-VPMON_DPP_DOWNLOAD: HB failure, Restarting the DPP [dec]Explanation VPMON daemon redownloading DPP(s)
Recommended Action ISAPI API users need to re-download config data to fast path
Error Message VPM-2-VPMON_DPP_RELOAD_FORCE: Force reload of DPP(s) [chars]: [chars]Explanation Could not send PSS Sync. notification to Standby Supervisor. PSS Type=[str.] Operation=[.str] Key=[Str.]
Recommended Action No action is required.
Error Message VPM-3-SEND_TO_ILC_FAILED: [chars]Explanation The VP Manager could not send to ILC for DG=[chars], at slot=[dec] processor=[dec] and SAP=[dec].
Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.
Error 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.
Error Message VPM-3-UNKNOWN_MSG: Recvd. from Node=[dec] SAP=[dec]Explanation The VP Manager has received an unknown message from [dec]].[dec]. This information is for debugging only.
Recommended Action No action is required.
Error 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.
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.
Explanation The VP Manager on the standby supervisor became active and it is ready to serve client requests.
Recommended Action No action is required.
Error Message VPM-6-BECAME_STDBY: Became STANDBY from active modeExplanation The VP Manager became standby from active mode.
Recommended Action No action is required.
Error 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.
Error 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.
Error Message VPM-6-EXITING: Exited due to [chars]Explanation The VP Manager process has exited due to [char]. The process has probably been restarted automatically.
Recommended Action No action is required.
Error Message VPM-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars]Explanation The VP Manager was unable to send heartbeat to the system manger
Recommended Action No action is required.
Error Message VPM-6-GENERAL_EVENT: [chars]Explanation The VP Manager has generated an important event. The description of the event is [str.]
Recommended Action No action is required.
Error 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.
Error 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.
Error Message VPM-6-SERVICE_UP: Initialized [chars]Explanation The VP Manager is up and ready to accept client requests The service was initialized in [char] mode.
Recommended Action No action is required.
Error 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.
Error Message VPM-6-VPMON_INFO: [chars]Explanation VPMON daemon informational message
Recommended Action No action is required.
Error Message VPM-6-VPMON_STARTING: deamon startedExplanation The VPMON daemon successfully started
Recommended Action No action is required.
Error Message VPM-6-VPM_MDS_LICENSE_GRACE: MDS LICENSE in grace period for feature : [chars]Explanation MDS license is in grace period. Please retrieve a new MDS license
Recommended Action No action is required.
Error Message VPM-6-VPM_MDS_LICENSE_REVOKED: MDS LICENSE REVOKED for feature : [chars]Explanation MDS license is revoked. Please retrieve a new MDS license
Recommended Action No action is required.
Error Message VPM-6-VPM_MDS_TIMED_LICENSE: Timed MDS LICENSE for feature : [chars]Explanation Component caused critical error
Recommended Action Restart the linecard
Error 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.
Error Message VRRP-CFG-2-VSH_REGISTER_FAIL: VSH registration failed returning [dec]Explanation VRRPsparsetreeregistrationwithVSHfailed'
Recommended Action No action is required.
Error 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.
Error 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
Error Message VRRP-CFG-5-STARTING: VRRP Manager service startedExplanation The service successfully started.
Recommended Action No action is required.
Error 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.
Error Message VRRP-ENG-2-VR_FAILURE: Error in VR[chars] [dec] interface [chars]. Going to init stateExplanation The VR [dec] on the interface [chars] is in init state for an internal error.
Recommended Action Show interface to check the status of the interface, show configuration, status and statistics of the specified virtual router, enable the vrrp debug and shut/ no shut the specified virtual router.
Error Message VRRP-ENG-3-ARP_INIT_ERROR: Failed to init ARP, ret [hex], errno [dec]Explanation VRRP-ARP interaction failed.
Recommended Action No action is required.
Error Message VRRP-ENG-3-BFD_IF_SESSION_REMOVAL_ERROR: Failed to remove interface level VRRP-BFD sessions ([hex] [hex]), Refer logsExplanation Plz refer internal error history for more details.
Recommended Action No action is required.
Error Message VRRP-ENG-3-BFD_SESSION_ADD_ERROR: Failed to add a few VRRP-BFD sessions([hex] [hex]), Refer logsExplanation Plz refer internal error history for more details.
Recommended Action No action is required.
Error Message VRRP-ENG-3-BFD_SESSION_CREATION_ERROR: Failed to create BFD session information([hex] [hex]), Refer logsExplanation Plz refer internal error history for more details.
Recommended Action No action is required.
Error Message VRRP-ENG-3-BFD_SESSION_REMOVAL_ERROR: Failed to remove a few VRRP-BFD sessions([hex] [hex]), Refer logsExplanation Plz refer internal error history for more details.
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error Message VRRP-ENG-3-URIB_INIT_ERROR: Failed to init URIB, ret [hex], errno [dec]Explanation VRRP-URIB interaction failed.
Recommended Action No action is required.
Error Message VRRP-ENG-4-BAD_ADV: VR[chars] ID [dec] on interface [chars] bad advertisement received: reason [chars]Explanation The virtual router specified has received an invalid advertisement.
Recommended Action Check that all VRRP nodes have the same configuration.
Error Message VRRP-ENG-5-INTERFACE_DOWN: Cannot start the VR[chars] [dec] since the interface [chars] is downExplanation The specified VR is enabled but cantchangestatefrominit.Thespecifiedinterfaceisdownordoesn'thaveaprimaryIPaddressconfigured.'
Recommended Action No action is required.
Error Message VRRP-ENG-5-INTERFACE_STATE_CHANGE: Interface [chars] state changed to [chars]Explanation The interface specified has changed state This could have triggered a VRRP status change.
Recommended Action No action is required.
Error Message VRRP-ENG-5-INVALID_CONFIG: Cannot start the VR[chars] [dec] on the interface [chars]. Invalid IP configuration. Reason: [chars]Explanation The specified VR on interface [chars] is enabled but the IP configuration is not valid because of [chars].
Recommended Action Show interface to check that the IP address of the interface is configured and it is in the same subnet of the virtual router address.
Error Message VRRP-ENG-5-STARTING: VRRP Engine service startedExplanation The service successfully started.
Recommended Action No action is required.
Error Message VRRP-ENG-5-VR_STATE_CHANGE: VR[chars] ID [dec] on interface [chars] state changed to [chars], event [chars]Explanation The status of the specified virtual router has changed to [chars].
Recommended Action No action is required.
Error Message VRRP-ENG-6-VSHA_RESULT: VR ID [dec] on interface [chars] state change request result [chars]Explanation The result of the request for status change on the virtual router (with VSHA extension) specified is [chars].
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.
Explanation Cfs operation [chars1] has failed. [chars2]
Recommended Action Please check the reason for the failure of the cfs operation and rectify the problem
Error Message VSAN-3-MEM_ALLOC_FAILED: alloc failed for size:[dec]Explanation Memory allocation of size [dec] failed.
Recommended Action Do "show process memory" command to see memory usage of processes.
Error Message VSAN-3-MESSAGE_ERROR: could not handle message:[chars] of type [dec] sent by addr [dec]:[dec]Explanation Got an IPC message [chars] of type [dec1] sent by a component running on node [dec2] with sap [dec3].
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.
Explanation Making VSAN with ID [dec] active from suspended state.
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error Message VSAN-6-REMOVED: Removed VSAN:[dec]Explanation Removed VSAN with ID [dec].
Recommended Action No action is required.
Error 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.
Error Message VSAN-6-TRUNKING_MEMBERSHIP_UPDATE: trunking membership updated for interface:[chars] with VSAN bitmap:[chars]Explanation Updated trunking membership for interface [chars1] with allowed VSAN list [chars2].
Explanation There are too many rules and policies configured causing the entire role database too exceed 120KB
Recommended Action Please delete some rules, policies, or roles and try to better optimize the RBAC database
Error Message VSHD-2-VSHD_SYSLOG_EOL_ERR: EOL function [chars] from library [chars] exited due to Signal [dec]Explanation Error in CLI EOL function
Recommended Action No action is required.
Error 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.
Error Message VSHD-2-VSHD_SYSLOG_SDWRAP_ERR: Description:[chars] errcode:[dec]Explanation This is probably occurring due to unstable fabric
Recommended Action Please retry operation when fabric is stable
Error Message VSHD-3-VSHD_SYSLOG_FILE_ERR: Purpose:[chars] Filename:[chars] errcode:[dec]Explanation File handling error
Recommended Action No action is required.
Error Message VSHD-3-VSHD_SYSLOG_MTS_ERR: message [chars]Explanation MTS message handling error
Recommended Action No action is required.
Error Message VSHD-3-VSHD_SYSLOG_PARSE_TREE_ERR: [chars]Explanation Error while updating parse tree in shell
Recommended Action No action is required.
Error Message VSHD-3-VSHD_SYSLOG_PSS_ERR: Purpose:[chars] URI:[chars] errcode:[dec]Explanation 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.
Error 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
Error 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
Explanation Configuration change notification
Recommended Action No action is required.
Error 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.
Error Message VSHD-5-VSHD_SYSLOG_ROLE_CREATED: New cli role [chars] createdExplanation The WWN Manager has run out of WWNs. No new dynamically allocated WWNs are available. However, statically assigned WWNs such as switch WWN, port WWN, etc. are still available.
Recommended Action Please add additional WWNs by programming a new Secondary MAC address and its range.
Error Message WWN-1-TYPES2_5_ALERT: Only [dec] (< [dec] %) Type 2 & 5 WWNs 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.
Explanation 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.
Error Message WWN-2-EXITING: Exited due to [chars]Explanation The WWN Manager process has exited due to [char]. The process has probably been restarted automatically.
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message WWN-2-STDOUT_ROTATE_FAILURE: Failed to rotate stdout file: [chars]Explanation The WWN Manager has failed to rotate its current stdout file with filename [str.]. The filesize could grow beyond its maximum limit.
Recommended Action No action is required.
Error 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.
Error 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.
Explanation Could not send PSS Sync. notification to Standby Supervisor. PSS Type=[str.] Operation=[.str] Key=[Str.].
Recommended Action No action is required.
Error Message WWN-3-RELEASE_ERR_UNKNOWN: Unknown WWN [chars] [chars]Explanation WWN Manager received a request to release a WWN [char] that could not have been allocated by this WWN Manager due to [char].
Recommended Action No action is required.
Error 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.
Error Message WWN-3-STARTUP_COPY_TO_RUNNING_FAILED: [chars]Explanation Could not snapshot Startup-Config PSS to Running-Config. The description of error is [str.].
Recommended Action No action is required.
Error Message WWN-3-TOOMANY_REQ_REL: WWNs [chars] = [dec]Explanation The WWN Manager received a request to allocate [dec] WWN, which is more than the maximum number of WWNs that can be allocated/released in a single request.
Recommended Action No action is required.
Error Message WWN-3-UNKNOWN_MSG: Received from Node=[dec] SAP=[dec] Opcode=[dec]Explanation The WWN Manager has received an unknown message from [dec]].[dec] with opcode [dec]. This information is for debugging only.
Recommended Action No action is required.
Error 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.
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.
Error Message WWN-4-PSS_VERSION_MISMATCH: PSS [dec] Code [dec]Explanation There was a version mismatch between the WWN Manager and one of its persistent storage databases. The persistent information has been translated to the new format.
Recommended Action No action is required.
Error 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.
Error 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.
Explanation VSAN-WWN created or deleted. The description of error is [str.].
Explanation The WWN Manager has allocated a new block, block number [dec], of 256 WWNs for internal use.
Recommended Action No action is required.
Error 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.
Error Message WWN-6-BECAME_STDBY: Became STANDBY from active modeExplanation The WWN Manager became standby from active mode.
Recommended Action No action is required.
Error 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.
Error Message WWN-6-FAILED_TO_SEND_HEARTBEAT: Failed to send heartbeat to system manager: Reason=[chars]Explanation The WWN Manager was unable to send heartbeat to the system manager.
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message WWN-6-SEC_MAC_UPDATED: MAC=[chars] Range=[dec]Explanation The WWN Manager had updated the Secondary MAC address with MAC address [char] and range [dec]. This update was initiated from a management entity.
Recommended Action No action is required.
Error Message WWN-6-SERVICE_UP: Initialized [chars]Explanation The WWN Manager is up and ready to accept client requests for WWNs. The service was initialized in [char] mode.
Recommended Action No action is required.
Error Message WWN-6-SWITCHOVER: Switching Over to other SupervisorExplanation The WWN Manager has successfully switched over to the standby supervisor card.
Explanation A client of WWN Manager attempted to release WWN [char] which is already free. This information is for debugging only.
Explanation Cross links lost sync and hence xbar is brought down.
Recommended Action Please reload the xbar using reloadxbar<xbar-num
Error Message XBAR_CLIENT-2-MEM_FULL: Memory allocation failed.Explanation XBAR_CLIENT process has failed to allocate memory.
Recommended Action Please perform a showxbar-clientevent-history'tocollectmoreinformation.'
Error Message XBAR_CLIENT-2-MEM_FULL: memory allocation failedExplanation Process xbar_client failed to allocate memory
Recommended Action Please examine the xbar-client event-history for more information.
Error Message XBAR_CLIENT-2-PROC_DN: Process is shutting down: [chars].Explanation XBAR_CLIENT process is exiting.
Recommended Action Please perform a showxbar-clientevent-history'tocollectmoreinformation.'
Error 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.
Error Message XBAR_CLIENT-2-PROC_INITFAIL: Process initialization failed due to [chars].Explanation XBAR_CLIENT process has failed initialization.
Recommended Action Please perform a showxbar-clientevent-history'tocollectmoreinformation.'
Error Message XBAR_CLIENT-2-PROC_INITFAIL: Process initialization failed due to [chars].Explanation XBAR_CLIENT process has failed initialization.
Recommended Action Please perform a showxbar-clientevent-history'tocollectmoreinformation.'
Error 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.
Explanation XBAR_CLIENT process has encountered an error in processing message.
Recommended Action Please perform a showxbar-clientevent-history'tocollectmoreinformation.'
Error 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.
Error 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 showxbar-clientevent-history'tocollectmoreinformation.'
Error 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.
Error Message XBAR_CLIENT-3-SUP2_XBC_MOD_INIT_FAIL: [chars], errcode - [hex]Explanation The module initialiazation failed
Recommended Action Please perform a showprocessxbar-clientevent-history'tocollectmoreinformation'
Explanation Process xbar_client failed to allocate memory
Recommended Action Please perform a showprocessxbar-clientevent-history'tocollectmoreinformation'
Error 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 showprocessxbar-clientevent-history'tocollectmoreinformation'
Error 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 showprocessxbar-clientevent-history'tocollectmoreinformation'
Explanation Process xbar_client hass received an unknown IPC message
Recommended Action Please perform a showprocessxbar-clientevent-history'tocollectmoreinformation'
Error Message XBAR_CLIENT-SLOT#-3-VEGAS2_XBC_MOD_INIT_FAIL: [chars], errcode - [hex]Explanation The module initialiazation failed
Recommended Action Please perform a showprocessxbar-clientevent-history'tocollectmoreinformation'
Explanation The supervisor has experienced an arbiter setup failure.
Recommended Action No action is required.
Error Message XBAR-2-INCOMPATIBLE_CONFIG: [chars] [dec] [chars].Explanation This module is not compatible with the current fabric mode. It will be powered down.
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error Message XBAR-2-XBM_EEM_MODULE_ACTION: Module [chars] has been reloaded by xbar-manager because of an eem-policy triggered action [chars] %iExplanation 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.
Explanation There are both FAB-1 and FAB-2 type spines in the Chassis. Please replace the FAB-1 spines with FAB-2 Spines.
Explanation The supervisor has experienced an arbiter setup failure.
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message XBAR-5-MOD_CONNECTION_REATTEMPT: Re-attempting XBAR connection with module [dec]Explanation The module has experienced a setup failure on connecting the module to the fabric.
Recommended Action Collect more informations about XBAR component Use command showxbarinternalevent-historymodule<moduleid
Error Message XBAR-5-SYNC_THRESHOLD_FAILURE: Module resync threshold exceeded [chars] [chars] module %iExplanation This module has exceeded the number of resync attempts in a day. Module will be reloaded
Recommended Action No action is required.
Error 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.
Error 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.
Error Message XBAR-5-XBAR_INIT_FAIL: Xbar [[dec].[dec]] reported failure durinig intialization return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Error Message XBAR-5-XBAR_MOD_INSERT_SEQ_FAILURE: [chars] for module [dec]Explanation The xbar manager received failure response and is failing the insert sequence
Recommended Action No action is required.
Error 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.
Error Message XBAR-5-XBAR_PORT_CHECK_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to check sync on port [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_CONTINUE_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to continue sync on port [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Error 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.
Error 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.
Error Message XBAR-5-XBAR_PORT_FORCE_POE_DISABLE_FAIL: Xbar [[dec].[dec]] reported failure to disable force poe mode on [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_FORCE_POE_ENABLE_FAIL: Xbar [[dec].[dec]] reported failure to enable force poe mode on [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_LPBACK_DISABLE_FAIL: Xbar [[dec].[dec]] reported failure to disable port loopback on [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_LPBACK_ENABLE_FAIL: Xbar [[dec].[dec]] reported failure to enable port loopback on [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Error Message XBAR-5-XBAR_PORT_START_SYNC_FAIL: Xbar [[dec].[dec]] reported failure to start sync on port [dec] return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Error Message XBAR-5-XBAR_RELEASE_ACCESS_FAIL: Slot [dec] reported failure releasing [chars] xbar access return_code [hex] ([chars])Explanation The supervisor has experienced an xbar access failure.
Recommended Action No action is required.
Error Message XBAR-5-XBAR_SET_ACCESS_FAIL: Slot [dec] reported failure acquiring [chars] xbar access return_code [hex] ([chars])Explanation The supervisor has experienced an xbar access failure.
Recommended Action No action is required.
Error 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.
Error Message XBAR-5-XBAR_STATUS_REPORT: Module [dec] reported status for component [dec] code [hex].Explanation An error status has been reported. If error is on supervisor, the supervisor is going to reboot. In case of dual supervisors, a switchover will occur. If error is on module, the module will be power cycled.
Recommended Action No action is required.
Error Message XBAR-5-XBAR_SW_INIT_FAIL: Xbar [[dec].[dec]] reported failure durinig sw intialization return_code [hex] ([chars]).Explanation The supervisor has experienced an xbar setup failure.
Recommended Action No action is required.
Error Message XBAR-5-XBAR_VERSION_CHECK_FAILURE: XBAR [chars] SCZ version check failed [chars] %iExplanation This SUP has an older Santacruz version, and so will not be allowed to power-up, Please upgrade to the latest supervisor version.
Explanation XML master agent has failed sending heartbeat.
Recommended Action No action is required.
Error Message XMLMA-2-INITFAIL: XML master agent initialization fails: [chars]Explanation XML master agent has failed initialization.
Recommended Action No action is required.
Error Message XMLMA-2-MTSERROR: XML master agent mts operation failed: [chars]Explanation XML master agent mts operation failed.
Recommended Action No action is required.
Error Message XMLMA-2-PSSFAILURE: XML master agent pss operation failed: [chars]Explanation XML master agent pss operation failed.
Recommended Action No action is required.
Error Message XMLMA-2-XMLMACRIT: XML master agent: [chars]Explanation XML master agent is exiting.
Recommended Action No action is required.
Error Message XMLMA-6-XMLMALOG: XML master agent operation log: [chars]Explanation XML sub agent failed sending heartbeat.
Recommended Action No action is required.
Error Message XMLSA-2-INITFAIL: XML sub agent initialization fails: [chars]Explanation XML agent has failed initialization.
Recommended Action No action is required.
Error Message XMLSA-2-USER_INACTIVE: XML sub agent timeed out: [chars]Explanation XML sub agent timedout due to inactivity.
Recommended Action No action is required.
Error Message XMLSA-2-VSH_ERR: XML sub agent vsh cmd error...: [chars]Explanation XML sub agent is exiting.
Recommended Action No action is required.
Error Message XMLSA-6-XMLSALOG: XML sub agent log: [chars]Explanation Failed to do high availability operation. [chars] is the reason.
Recommended Action No action is required.
Error 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.
Error 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.
Error Message ZBM-2-ZBM_LINECARD_STATUS: Status from linecard: [dec], for module: [chars](ID: [dec]), status : [dec], error_id: [hex], catastrophic: [chars], restart count: [dec].Explanation Status from linecard: [dec], for module: [chars](ID: [dec]), status : [dec], error_id: [hex], catastrophic: [chars], restart count: [dec].
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message ZBM-2-ZBM_TCAM_SEND: [chars]Explanation ZBM warning messages is reported as [chars] [dec].
Explanation ZBM system health management event status is reported as [chars] [hex].
Recommended Action No action is required.
Error Message ZBM-6-ZBM_ECHO_PROGRAMMING_FAILED: [chars].Explanation Programming echo entry failed for [chars].
Recommended Action No action is required.
Error 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.
Error 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.
Error Message ZBM-6-ZBM_INIT_PROCESS: Zone Block Mgr process started [chars] at [chars]Explanation Zone Block Mgr process started in [chars] (stateless/stateful) mode at time [chars].
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message ZBM-6-ZBM_RUNTIME_STATUS: [chars] [dec]Explanation ZBM runtime status is reported as [chars] [dec].
Recommended Action No action is required.
Error Message ZBM-6-ZBM_STATUS: ZBM Status: [chars].Explanation ZBM status is reported as [chars].
Recommended Action No action is required.
Error Message ZBM-6-ZBM_UPDATE_SSRAM_QOS_EVENT_STATUS: [chars] [chars].Explanation ZBM update SSRAM for QoS event status is reported as [chars] [chars].
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.
Error Message ZONE-2-LZ_GENERAL_ERROR: [chars]Explanation The LUN/Read-only zoning process has encountered a critical error. The description of error is [str].
Recommended Action No action is required.
Error Message ZONE-2-LZ_INIT_FAILED: Initialization of LUN/Read-only zoning Process failed at [chars]Explanation Initialization of LUN/Read-only zoning process failed at [char].
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error Message ZONE-2-ZS_BLOCKED_ATTR_PRESENT: Module [dec] failed to come online due to [chars] in VSAN [dec] to bring up the module.Explanation Module [dec] failed to come up due to [chars].
Recommended Action Verify if RO/LUN/Broadcast attributes are configured, in the VSAN, disable if configured
Error Message ZONE-2-ZS_CHANGE_ACA_FAILED: ACA failed : [chars]Explanation Zone Server cannot acquire change authorization : [chars].
Recommended Action Verify the interoperability mode on all the switches OR retry later.
Error Message ZONE-2-ZS_CHANGE_ACQUIRE_AUTH_FAILED: Acquire authorization failed on VSAN [dec]Explanation Zone Server cannot acquire authorization on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_ACTIVATION_FAILED_RESN_DOM: Activation failed : reason [chars] domain [dec]Explanation Zone Server cannot activate due to reason [chars] on domain [dec].
Recommended Action No action is required.
Error 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.
Error Message ZONE-2-ZS_CHANGE_ACTIVATION_FAILED: Activation failedExplanation Zone Server cannot activate the zoneset.
Recommended Action No action is required.
Error 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.
Error Message ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED_RESN_DOM: Deactivation failed : reason [chars] domain [dec]Explanation Zone Server cannot deactivate due to reason [chars] on domain [dec].
Recommended Action No action is required.
Error 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.
Error Message ZONE-2-ZS_CHANGE_DEACTIVATION_FAILED: Deactivation failedExplanation Zone Server cannot deactivate the zoneset.
Recommended Action No action is required.
Error 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.
Error Message ZONE-2-ZS_CHANGE_RRCA_REJECTED: RRCA received from remote domain [dec] is rejected: [chars]Explanation Received invalid RRCA from domain [dec]. : [chars]
Recommended Action Verify the interoperability mode on the switch.
Error Message ZONE-2-ZS_CHANGE_RUFC_REJECTED: RUFC received from remote domain [dec] is rejected: [chars]Explanation Received invalid RUFC from domain [dec]. : [chars]
Recommended Action Verify the interoperability mode on the switch.
Error Message ZONE-2-ZS_CHANGE_SFC_FAILED: SFC failed : [chars]Explanation Zone Server cannot stage zone configuration : [chars].
Recommended Action Verify the interoperability mode on all the switches.
Error Message ZONE-2-ZS_CHANGE_SFC_REJECTED: SFC received from remote domain [dec] is rejected: [chars]Explanation Received invalid SFC from domain [dec]. : [chars]
Recommended Action Verify the interoperability mode on the switch.
Error Message ZONE-2-ZS_CHANGE_SMART_ZONING_POLICY_CHANGE_FAILED: Smart Zoning Policy Change FailedExplanation Zone Server cannot distribute smart zoning policy change.
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_STAGE_ACTIVATE_ZSSET_BY_NAME_FAILED: Stage activate zoneset by name failed on VSAN [dec]Explanation Zone Server cannot stage activate zoneset by name on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_STAGE_ACTIVATE_ZSSET_ENH_FAILED: Stage activate zone set enhanced failed on VSAN [dec]Explanation Zone Server cannot stage activate zone set enhanced on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_STAGE_DEACTIVATE_ZSSET_ENH_FAILED: Stage deactivate zoneset enhanced failed on VSAN [dec]Explanation Zone Server cannot stage deactivate zoneset enhanced on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_STAGE_DISTRIBUTE_DFLT_ZONE_FAILED: Stage distribute default zone failed on VSAN [dec]Explanation Zone Server cannot stage distribute default zone on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_STAGE_DISTRIBUTE_ZS_DB_FAILED: Stage distribute zoneset database failed on VSAN [dec]Explanation Zone Server cannot stage distribute zoneset database on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_STAGE_SET_ZONING_MODE_FAILED: Stage set zoning mode failed on VSAN [dec]Explanation Zone Server cannot stage set zoning mode on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_CHANGE_STAGE_SET_ZONING_POLICIES_FAILED: Stage set zoning policies failed on VSAN [dec]Explanation Zone Server cannot stage set zoning policies on VSAN [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_DB_OPERATION_FAILED: Database operation error: [chars]Explanation Database operation is failed : [chars].
Recommended Action No action is required.
Error Message ZONE-2-ZS_DDAS_TABLE_CLEANUP_DUPLICATE_ENTRIES: Zone Device-alias table cleanup failed. Please try again. Do not initiate any Zone configuration commands until this command is successful.Explanation Zone device-alias table cleanup failed due to error: [chars]
Recommended Action Please try again. Do not initiate any zone configuration command until this command is successful.
Error Message ZONE-2-ZS_EXPORT_IMPORT_FAILED: [chars] operation failedExplanation [chars] (Export/Import) operation failed.
Recommended Action No action is required.
Error 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.
Error Message ZONE-2-ZS_INIT_FAILED: [chars]Explanation Zone Server initialization failed : [chars].
Recommended Action No action is required.
Error 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.
Error 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.
Error 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.
Error 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.
Error 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.
Error Message ZONE-2-ZS_MEMBER_LIMIT_EXCEEDED: The limit for maximum number of members exceededExplanation The number of members configured has exceeded the maximum number of members allowed across all vsans Due to this, distribution or merge operation may fail.
Recommended Action Make sure the number of members is less than the maximum allowed across all vsans.
Error Message ZONE-2-ZS_MERGE_ADJ_NO_RESPONSE: Adjacent switch not responding, isolating interface [chars]Explanation Interface [chars] isolated due to adjacent switch not responding to Zone Server requests.
Recommended Action Flap the interface.
Error Message ZONE-2-ZS_MERGE_FAILED: Zone merge failure, isolating interface [chars] [chars]Explanation Interface [chars] isolated due to zone merge failure. error [chars]
Recommended Action Compare active zoneset with the adjacent switch OR use "zone merge interface [interface] {import/export} VSAN [VSAN-num]" command.
Error Message ZONE-2-ZS_MERGE_FULL_DATABASE_MISMATCH: Zone merge full database mismatch on interface [chars]Explanation Full zoning databases are inconsistent between two switches connected by interface [chars]. Databases are not merged.
Recommended Action Compare full zoning database with the adjacent switch, correct the difference and flap the link.
Error Message ZONE-2-ZS_MERGE_UNKNOWN_FORMAT: Unknown format, isolating interface [chars]Explanation Interface [chars] isolated due to unknown format in merge request.
Recommended Action Set the interoperability mode to same value on both switches.
Error Message ZONE-2-ZS_MTS_OPER_FAILED: MTS [chars] operation failed : [chars]Explanation Zone Server MTS [chars] operation failed : [chars].
Recommended Action No action is required.
Error Message ZONE-2-ZS_NO_RSCN_ON_SW_CARD: Devices on Module [dec] will not be receiving RSCN as [chars]Explanation Devices on Module [dec] will not be receiving RSCN as [chars].
Recommended Action Enable Zone Based RSCN
Error Message ZONE-2-ZS_PORT_SWAP_FAILURE: Port swap operation failedExplanation Port swap operation failed.
Recommended Action No action is required.
Error Message ZONE-2-ZS_PSS_VER_MISMATCH: PSS version mismatch URL: [chars] (expected [chars], got [chars])Explanation Configuration version mismatch. PSS URL [chars]. Expected version [chars], stored version [chars].
Recommended Action Upgrade/Downgrade to expected version.
Error Message ZONE-2-ZS_SHARED_DB_INIT_FAILED: [chars]Explanation Zone Server shared DB initialization failed : [chars].
Recommended Action No action is required.
Error 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.
Error 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.
Error Message ZONE-2-ZS_TCAM_PROGRAMMING_FAILED: TCAM operation failed : [chars], Reason: [chars]Explanation TCAM Programming failure has occurred : [chars]. [chars] is the reason for failure.
Recommended Action No action is required.
Error 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.
Error 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.
Error Message ZONE-2-ZS_VIRTUAL_DOMAIN_INCONSISTENT: IVR reporting virtual domain different from rib and domain manager in vsan [dec]Explanation IVR reporting virtual domain different from rib and domain manager in vsan [dec].
Recommended Action No action is required.
Error Message ZONE-2-ZS_ZONE_BASED_RSCN_DISABLED: Zone based RSCN Generation has been Disabled. Devices on non ISOLA line cards will not be receiving 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.
Error Message ZONE-2-ZS_ZONE_LIMIT_EXCEEDED: The limit for maximum number of zones exceededExplanation The number of zones configured has exceeded the maximum number of zones allowed across all vsans Due to this, distribution or merge operation may fail.
Recommended Action Make sure the number of zones is less than the maximum allowed across all vsans.
Error Message ZONE-2-ZS_ZONE_SET_LIMIT_EXCEEDED: The limit for maximum number of zonesets 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 vsans.
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.
Error 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.
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.
Error Message ZONE-4-ROZ_WRITE_ACCESS_TO_READ_ONLY_LUN: FCP command [hex] received from SID=[chars] to DID=[chars] for LUN=[chars]Explanation The LUN/Read-only zoning process has received FCP command [int] from SID [char] to DID [char] for a read-only LUN [char].
Recommended Action No action is required.
Error Message ZONE-4-ZS_BROADCAST_LUN_WARNING: LUN member(s) and Broadcast attribute are present in zone [chars] in vsan [dec]. Broadcast violations can occur for LUN members.Explanation Broadcast violations can happen in zone [chars] in vsan [dec] since it has LUN zone members.
Recommended Action No action is required.
Error 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.
Error Message ZONE-4-ZS_DB_WARNING: [chars]Explanation Database operation warning: [chars].
Recommended Action No action is required.
Error Message ZONE-4-ZS_DOMAIN_MGR_WARNING: Unable to retrieve domain info from domain mgr error: [chars] in vsan [dec]Explanation Unable to retrieve info of domain from domain manager, error: [chars] in vsan [dec].
Recommended Action No action is required.
Error 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.
Error Message ZONE-4-ZS_IF_PORT_MODE_CONFLICT: Port mode conflict for if [chars]Explanation Port mode conflict for if [chars]
Recommended Action Shutdown/no shutdown the interface
Error Message ZONE-4-ZS_INVALID_FPORT_WWN_MEMBER: Virtual device fwwn: [chars] is not a valid zone/alias member virtual name: [chars] pwwn: [chars]Explanation Virtual device fwwn: [chars] is not a valid zone/alias member, virtual name: [chars] pwwn: [chars].
Recommended Action No action is required.
Error 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.
Error Message ZONE-4-ZS_LICENSE_EXPIRY_WARNING: Feature [chars] evaluation license [chars] expiry in [dec] daysExplanation Feature [chars1] will exceed itsevaluationtimeperiodin[dec]daysandwillbeshutdownunlessapermanentlicense[chars2]isinstalled.'
Recommended Action Please install the license file to continue using the feature.
Error Message ZONE-4-ZS_MEMBER_CONVERSION_FAILED: Zone Member conversion failed for [chars]. Error: [chars]Explanation Zone Member conversion has failed in : [chars] due to error: [chars]
Recommended Action No action is required.
Error Message ZONE-4-ZS_NON_INTEROPERABLE_ZONE_SET: Non interoperable active zoneset present on VSAN [dec] in interoperability modeExplanation Active zoneset has non interoperable members (FCID, FWWN,..) when interoperability mode is turned on the VSAN [dec].
Recommended Action Turn off interoperability mode OR make sure that active zoneset has only interoperable members (PWWN).
Error Message ZONE-4-ZS_QOS_LUN_WARNING: LUN member(s) and QoS attribute are present in zone [chars] in vsan [dec]. QoS will not be applicable for LUN members.Explanation QoS will not be applicable to LUN zone members in zone [chars] in vsan [dec].
Recommended Action No action is required.
Error Message ZONE-4-ZS_SDV_VIRT_REAL_CONFLICT_WARNING: Virtual and Real devices are zoned together or zoned with same device. virtual name: [chars] pwwn: [chars]Explanation Virtual and Real devices are zoned together or zoned with same device, virtual name: [chars] pwwn: [chars].
Recommended Action No action is required.
Error Message ZONE-4-ZS_SMART_ZONING_AUTO_CONVERSION_FAILED: Smart Zoning auto conversion failed for [chars]. Error: [chars]Explanation Smart Zoning auto conversion has failed in : [chars] due to error: [chars]
Recommended Action No action is required.
Error 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.
Error 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.
Explanation [chars] (Export/Import) operation completed.
Recommended Action No action is required.
Error 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.
Error Message ZONE-5-ZS_ZONE_SET_ACTIVATED: Zoneset [chars] activatedExplanation Zoneset [chars] activated.
Recommended Action No action is required.
Error Message ZONE-5-ZS_ZONE_SET_DEACTIVATED: Zoneset deactivatedExplanation The LUN/Read-only zoning process on the standby supervisor became active.
Recommended Action No action is required.
Error 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.
Error Message ZONE-6-LZ_FAILED_TO_SEND_HEARTBEAT: LUN/Read-only zoning process failed to send heartbeat to system manager: Reason=[chars]Explanation The LUN/Read-only zoning process was unable to send heartbeat to the system manager.
Recommended Action No action is required.
Error Message ZONE-6-LZ_GENERAL_EVENT: [chars]Explanation The LUN/Read-only zoning process has generated an important event. The description of the event is [str].
Recommended Action No action is required.
Error Message ZONE-6-LZ_INQUIRY_TO_ZONED_OUT_LUN: INQUIRY command received from SID=[chars] to DID=[chars] for LUN=[chars]Explanation The LUN/Read-only zoning process has received INQUIRY FCP command from SID [char] to DID [char] for a zoned out LUN [char].
Recommended Action No action is required.
Error Message ZONE-6-LZ_REPORT_LUNS_CMD_RCVD: REPORT LUNS command received from SID=[chars] to DID=[chars] for LUN=[chars]Explanation The LUN/Read-only zoning process has received REPORT LUNS FCP command from SID [char] to DID [char] for LUN [char].
Recommended Action No action is required.
Error Message ZONE-6-LZ_REQUEST_SENSE_TO_ZONED_OUT_LUN: REQUEST SENSE command received from SID=[chars] to DID=[chars] for LUN=[chars]Explanation The LUN/Read-only zoning process has received. REQUEST SENSE FCP command from SID [char] to DID [char] for a zoned out LUN [char].
Recommended Action No action is required.
Error Message ZONE-6-LZ_SERVICE_UP: LUN/Read-only zoning Process initialized [chars]Explanation The LUN/Read-only zoning process is up. The process was initialized in [char] mode.
Recommended Action No action is required.
Error Message ZONE-6-LZ_SWITCHOVER: LUN/Read-only zoning process switching over to other supervisor.Explanation The LUN/Read-only zoning process has successfully switched over to the standby supervisor card.
Recommended Action No action is required.
Error 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.
Error 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.
Error Message ZONE-6-ZS_INIT_PROCESS: Zone Server process started [chars] at [chars]Explanation Zone Server process started in [chars] (stateless/stateful) mode at time [chars].
Recommended Action No action is required.
Error Message ZONE-6-ZS_INIT_WARNING: [chars]Explanation Warning during Zone Server Initialization: [chars].
Recommended Action No action is required.
Error Message ZONE-6-ZS_INVALID_MEMBER: Invalid member [dec] [chars]Explanation Invalid member type [dec] [chars] recieved from the API call.
Error Message ZONE-6-ZS_UNKNOWN_LIC_FEATURE: [chars]Explanation Zone Server received an event for an known licensing feature: [chars].