Cisco MDS 9000 Series Switches NX-OS System Messages Reference

M2FIB Messages

This section contains the M2FIB messages.

M2FIB-SLOT#-0

Explanation M2FIB failed to initialize CLI infrastructure's backend library. This is a fatal error.

Recommended Action No action is required.

Explanation M2FIB failed to initialize timer library. This is a fatal error.

Recommended Action No action is required.

M2FIB-SLOT#-2

Explanation Failed to program the mac table. This is a critical failure please check m2fib error transactions

Recommended Action No action is required.

Explanation Memory allocation failed. This is a critical failure

Recommended Action No action is required.

Explanation M2FIB failed to process the route update as the vlan recvd was invalid

Recommended Action No action is required.

M2FIB-SLOT#-6

Explanation M2FIB has created its internal state stateless/stateful [chars].

Recommended Action No action is required.

Explanation Request to create VDC [dec] in M2FIB was successful.

Recommended Action No action is required.

Explanation M2FIB has successfully removed VDC [dec] from its databases.

Recommended Action No action is required.

Explanation M2FIB has added VLAN [dec] in VDC [dec].

Recommended Action No action is required.

Explanation M2FIB has successfully removed VLAN [dec] from VDC [dec].

Recommended Action No action is required.

M2RIB Messages

This section contains the M2RIB messages.

M2RIB-0

Explanation M2RIB failed to initialize CLI infrastructure's backend library. This is a fatal error.

Recommended Action No action is required.

M2RIB-2

Explanation M2RIB has hit flood PROG error. Collect output of show tech-support m2rib for further analysis

Recommended Action No action is required.

Explanation M2RIB has hit flood prog error. Collect output of show tech-support m2rib for further analysis

Recommended Action No action is required.

Explanation M2RIB encountered an error in processing an MTS message. The error and message are specified in the Message

Recommended Action No action is required.

Explanation M2RIB 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 MFDM returned Failure for flood programming. Collect output of show tech-support m2rib for further analysis

Recommended Action No action is required.

Explanation Transaction timer for the message sent from M2RIB to MFDM has expired. Ack not received from MFDM.

Recommended Action No action is required.

M2RIB-6

Explanation M2RIB has created its internal state stateless/stateful [chars].

Recommended Action No action is required.

Explanation M2RIB line 2.

No action is required.

MAC Messages

This section contains the MAC messages.

MAC-SLOT#-2

Explanation MAC Informational message

Recommended Action No action is required.

MCAST Messages

This section contains the MCAST messages.

MCAST-2

Explanation Mcast is shutting down

Recommended Action The action depends on the situation. The multicast process can shut down gracefully because of a system restart (in which case no action needs to take place) or because of a failure. The message associated with the syslog should be self explanatory to understand the reason for the shutdown. If the process is able to restart properly, there is no immediate harm for the system stability and the suggested action is to report the syslog event together with an explanation of the operations most recently performed on the system.

MCAST-4

Explanation Mcast encountered a generic error

Recommended Action No action is required.

MCAST-5

Explanation Mcast has received a malformed/unrecognized message

Recommended Action No action is required.

Explanation Mcast has been started

Recommended Action No action is required.

MCECTEST Messages

This section contains the MCECTEST messages.

MCECTEST-3

Explanation MCECTEST has hit an assert condition at file [chars]

Recommended Action No action is required.

Explanation MCECTEST Initialization failed. due to [chars]

Recommended Action No action is required.

Explanation MCECTEST encountered an internal error due to [chars]

Recommended Action No action is required.

Explanation MCECTEST encountered an MTS error due to [chars]

Recommended Action No action is required.

MCECTEST-5

Explanation MCECTEST Service Disabled

Recommended Action No action is required.

Explanation MCECTEST Service enabled

Recommended Action No action is required.

MCECTEST-6

Explanation MCECTEST got an internal info [chars]

Recommended Action No action is required.

MCM Messages

This section contains the MCM messages.

MCM-2

Explanation Some critical error

Recommended Action No action is required.

Explanation Replication is disabled

Explanation Error in request-response handshake

Recommended Action No action is required.

Explanation Routing is disabled

Recommended Action No action is required.

MCM-5

Explanation SDB updated failed for MCM

Recommended Action No action is required.

MCM-6

Explanation Replication is enabled

Recommended Action No action is required.

Explanation Routing is enabled

Recommended Action No action is required.

METROPOLIS_USD Messages

This section contains the METROPOLIS_USD messages.

METROPOLIS_USD-3

Explanation Metropolis received packets with CRC error

Recommended Action Use another optical cable and transceivers. If the problem still persists, change the peer ports, such as the remote port to another or the local port to another. Run the commands ‘diagnostic start module <mod> test all’ and ‘show diagnostic result module <mod> test all detail’. The result will display the information about the failures in HW, if any.

MFDM Messages

This section contains the MFDM messages.

MFDM-2

Explanation PIXM returned duplicate DI.

Recommended Action No action is required.

Explanation Download of L2/L3 route databases timed out. Download triggered by VMM insert request.

Recommended Action No action is required.

Explanation MFDM PD hit a internal error. show system internal mfdm errors for further analysis.

Recommended Action No action is required.

Explanation Response from LC timeout for update

Recommended Action No action is required.

Explanation MFDM PI/PD refcount out-of-sync

Recommended Action No action is required.

Explanation MFDM tampered xid in OTV response payload

Recommended Action No action is required.

MODULE Messages

This section contains the MODULE messages.

MODULE-2

Explanation pre- upgrade message failed.

Recommended Action No action is required.

Explanation Upgrade ready message failed.

Recommended Action No action is required.

Explanation Upgrade done message failed.

Recommended Action No action is required.

Explanation Upgrade ready message failed.

Recommended Action No action is required.

Explanation Upgrade ready message failed.

Recommended Action No action is required.

Explanation The module in slot [decimal digit] reported a failure in the runtime diagnostic. Module manager is going to power cycle the module.

Recommended Action Collect information about the module by issuing the command 'show module internal all module [decimal digit]'.

Explanation Module [decimal digit] failed to download a new image from the supervisor.

Recommended Action Collect information about the module by issuing the command 'show module internal all module [decimal digit]'.

Explanation Module [decimal digit] reported a failure during the initialization phase and will be rebooted.

Recommended Action Collect information about the module by issuing the commands 'show module_internal all module '.

Explanation Module [decimal digit] reported a failure during the initialization phase and will be rebooted.

Recommended Action Collect information about the module by issuing the commands show module_internal all module <module> number

Explanation Module [decimal digit] reported a failure during the initialization phase and will be powered down.

Recommended Action Collect information about the module by issuing the commands 'show module_internal all module '.

Explanation A critical failure in service [string] happened at module [decimal digit] is going to reset the module [decimal digit].

Recommended Action Collect information about the module by issuing the command 'show module internal all module [decimal digit]'.

Explanation A non-critical failure in service [string] happened at module [decimal digit] is not going to reset the module [decimal digit].

Recommended Action Collect information about the module by issuing the command 'show module internal all module [decimal digit]'.

Explanation Module [decimal digit] is not replying to the hello message: module manager is then going to reset the module.

Recommended Action No action is required.

Explanation Module [decimal digit] sent the registration message notifying a failure.

Recommended Action Collect module internal information by issuing the command 'show module internal all module [decimal digit]'.

Explanation Module [decimal digit] reported a failure in the runtime diagnostic due to failure in some of the ports.

Recommended Action Collect information about the module by issuing the command 'show module internal all module [decimal digit]'.

Explanation The software card id of module [decimal digit] is not supported by the supervisor.

Recommended Action Collect information about the module by issuing the commands 'show module internal all module [decimal digit]'

Explanation The xbar in slot [decimal digit] reported a failure in the runtime diagnostic. Module manager is going to power cycle the module.

Recommended Action Collect information about the module by issuing the command 'show module internal all xbar [decimal digit]'.

Explanation Xbar [decimal digit] reported a failure during the initialization phase and will be rebooted.

Recommended Action Collect information about the module by issuing the commands 'show module_internal all xbar '.

Explanation Xbar [decimal digit] reported a failure during the initialization phase and will be rebooted.

Recommended Action Collect information about the module by issuing the commands show module_internal all xbar <module> number

Explanation Xbar [decimal digit] reported a failure during the initialization phase and will be powered down.

Recommended Action Collect information about the module by issuing the commands 'show module_internal all xbar '.

Explanation Xbar [decimal digit] reported a failure in the runtime diagnostic due to failure in some of the ports.

Recommended Action Collect information about the module by issuing the command 'show module internal all xbar [decimal digit]'.

Explanation Xbar [decimal digit] reported a failure in the runtime diagnostic due to failure in some of the ports.

Recommended Action Collect information about the module by issuing the command show module internal all xbar [decimal digit]'.

Explanation The software card id of xbar [decimal digit] is not supported by the supervisor.

Recommended Action Collect information about the module by issuing the commands 'show module internal all xbar [decimal digit]''

MODULE-3

Explanation LCM encountered an error while executing a sequence for a module.

Recommended Action No action is required.

Explanation LCM encountered an error while processing a message for module.

Recommended Action No action is required. '

Explanation The software version of module [decimal digit] is not supported by the supervisor.

Recommended Action Collect information about the module by issuing the command 'show module internal all module [decimal digit]'.

MODULE-4

Explanation Module [decimal digit] reported a warning in the runtime diagnostic due to failure in some of the ports.

Recommended Action Collect information about the module by issuing the command 'show module internal all module [decimal digit]'.'

Explanation Xbar [decimal digit] reported a warning in the runtime diagnostic due to failure in some of the ports.

Recommended Action Collect information about the module by issuing the command 'show module internal all xbar [decimal digit]'

MODULE-5

Explanation Module [decimal digit] is ready to be configured and be able to switch traffic.

Recommended Action No action is required.

Explanation Upgrade of the module has ended.

Recommended Action No action is required.

Explanation Upgrade of the module has been started by installer

Recommended Action No action is required.

Explanation Module [decimal digit] is ready to be configured and be able to switch traffic.

Recommended Action No action is required.

Explanation Module [decimal digit] reported a failure during the initialization phase and will be rebooted.

Recommended Action Collect information about the module by issuing the commands show module_internal all module <module> number

Explanation Module [decimal digit] completed image download and is restarting.

Recommended Action No action is required.

Explanation The startup configuration for module [decimal digit] contains information about a different type of module instead of containing information about the current one.

Recommended Action No action is required.

Explanation Module [decimal digit] is ready to be configured and be able to switch traffic.

Recommended Action No action is required.

Explanation Xbar [decimal digit] is ready to be configured and be able to switch traffic.

Recommended Action No action is required.

Explanation Xbar [decimal digit] reported a failure during the initialization phase and will be rebooted.

Recommended Action Collect information about the module by issuing the commands show module_internal all xbar <module> number

MODULE-6

Explanation Notification is being sent to remove the module configurations.

Recommended Action No action is required.

Explanation Module [decimal digit] sent a successful registration message.

Recommended Action No action is required.

MONITOR Messages

This section contains the MONITOR messages.

MONITOR-3

Explanation SPM Request timed out for ERSPAN-DST session

Recommended Action No action is required.

MONITOR-5

Explanation A new span session has been created.

Recommended Action No action is required.

Explanation Session has been deleted.

Recommended Action No action is required.

Explanation Session is down, no further traffic will be spanned.

Recommended Action No action is required.

Explanation The session is experiencing a problem.

Recommended Action Delete the session and try to reconfigure it

Explanation Session is up now. You can monitor Spanned traffic at the destination ports

Recommended Action No action is required.

Explanation A new source has been added.

Recommended Action No action is required.

Explanation A source has been removed.

Recommended Action No action is required.

MTM Messages

This section contains the MTM messages.

MTM-SLOT#-0

Explanation MTM failed to initialize CLI infrastructure's backend library. This is a fatal error.

Recommended Action No action is required.

Explanation Driver has failed to respond to MTM request within MTM_FE_TO_TIMER_INTERVAL.This is a fatal error.

Recommended Action No action is required.

Explanation MTM failed to initialize timer library. This is a fatal error.

Recommended Action No action is required.

MTM Messages

MTM-SLOT#-1

Explanation Failed to send request to L2 ASIC driver.

Recommended Action No action is required.

MTM Messages

MTM-SLOT#-2

Explanation Static mac insert failed due to line full condition.

Recommended Action No action is required.

Explanation Failed to get interface for hardware Index for [dec] entries

Recommended Action No action is required.

Explanation Failed to get hardware index for interface Index for [dec] entries.

Recommended Action No action is required.

Explanation Memory allocation failed. This is a critical failure

Recommended Action No action is required.

Explanation Multicast mac address: [hex] sent as source mac in a packet and was learnt in the Mac Table. Please execute: clear mac address-table dynamic multicast-entries

Recommended Action No action is required.

Explanation Failed to program the required registers in L2 ASIC for [chars].

Recommended Action No action is required.

Explanation Failed to program the required registers in L2 ASIC for BPDU matching. BPDUs will not be received by Spanning tree.

Recommended Action No action is required.

Explanation MTM failed to find VLAN [dec] in its database. L2 MAC learning & aging on VLAN [dec] may be affected.

Recommended Action No action is required.

MTM Messages

MTM-SLOT#-5

Explanation Age group allocation for age [dec] failed. The total number of allocated age group has reached system limits.

Recommended Action No action is required.

Explanation Failed to program the required registers in L2 ASIC to disable learning all 0 MAC.

Recommended Action No action is required.

MTM Messages

MTM-SLOT#-6

Explanation MTM has created its internal state stateless/stateful [chars].

Recommended Action No action is required.

Explanation Request to create VDC [dec] in MTM was successful.

Recommended Action No action is required.

Explanation MTM has successfully removed VDC [dec] from its databases.

Recommended Action No action is required.

Explanation MTM has added VLAN [dec] in VDC [dec].

Recommended Action No action is required.

Explanation MTM has successfully removed VLAN [dec] from VDC [dec].

Recommended Action No action is required.

NFM Messages

This section contains the NFM messages.

NFM-2

Explanation The DDB commit failed

Recommended Action No action is required.

Explanation A DDB generated failure

Recommended Action No action is required.

Explanation The NFM service process has exited due to [char]. The process has probably been restarted automatically.

Recommended Action No action is required.

Explanation NFM Service initialization failed. [chars] explains the reason for the failure.

Recommended Action No action is required.

Explanation The NFM service 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 NFM service encountered error while operating on a persistent storage database.

Recommended Action No action is required.

Explanation The DDB Verify failed

Recommended Action No action is required.

NFM-3

Explanation The DDB generated error

Recommended Action No action is required.

Explanation An error occurred while processing a message from FEATURE Manager

Recommended Action No action is required.

Explanation The NFM service encountered a handle that was in use while reading a persistent storage database.

Recommended Action No action is required.

Explanation The NFM service encountered an invalid handle in a persistent storage database.

Recommended Action No action is required.

Explanation An Export Msg from a Linecard contained an invalid Monitor handle

Recommended Action No action is required.

Explanation NFM Service encountered an MTS error. [chars] specifies the context where the error occurred.

Recommended Action No action is required.

Explanation L2 Netflow config is applied on Port-channel with F1 Line Cards only - error

Recommended Action No action is required.

Explanation The DDB generated error

Recommended Action No action is required.

Explanation The NFM service has detected corruption in one of its persistent information database. The database would be recreated.

Recommended Action No action is required.

Explanation An error occurred while processing a message from VLAN Manager

Recommended Action No action is required.

NFM-4

Explanation The DDB generated warning

Recommended Action No action is required.

Explanation The NFM service requires a License to run and exits when the License expires.

Recommended Action No action is required.

Explanation The DDB generated warning

Recommended Action No action is required.

Explanation There was a version mismatch between the NFM service and one of its persistent storage databases. The persistent information has been translated to the new format.

Recommended Action No action is required.

NFM-5

Explanation NetFlow Feature Disabled.

Recommended Action No action is required.

Explanation NetFlow Feature Enabled.

Recommended Action No action is required.

NFM-6

Explanation The NFM service on the standby supervisor became active and it is ready to serve client requests.

Recommended Action No action is required.

Explanation The NFM service became standby from active mode.

Recommended Action No action is required.

Explanation The DDB generated notification

Recommended Action No action is required.

Explanation The NFM service was unable to send heartbeat to the system manger

Recommended Action No action is required.

Explanation The DDB generated notification

Recommended Action No action is required.

Explanation The NFM service is up and ready The service was initialized in [char] mode.

Recommended Action No action is required.

Explanation NFM Service is shutting down gracefully. This is an informational message.

Recommended Action No action is required.

Explanation The NFM service has successfully switched over to the standby supervisor card.

Recommended Action No action is required.

NFM-7

Explanation Debug information is being sent to syslog

Recommended Action No action is required.

NFP Messages

This section contains the NFP messages.

NFP-SLOT#-2

Explanation Acl error

Recommended Action No DDTS.

Explanation Ddb error

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation Nfp error occurred

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 Fib error

Recommended Action No DDTS.

Explanation Nde error

Recommended Action No DDTS.

Explanation Nfm error

Recommended Action No DDTS.

Explanation Qos error

Recommended Action No DDTS.

NFP-SLOT#-5

Explanation Info

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.

NPC Messages

This section contains the NPC messages.

NPC-SLOT#-3

Explanation Errors which cause program to exit occurred

Recommended Action No action is required.

NPC-SLOT#-4

Explanation Serious errors which affect all normal operations occurred

Recommended Action No action is required.

NPC-SLOT#-5

Explanation Unexpected errors which affect some normal operations occurred

Recommended Action No action is required.

Explanation Illegal event received in NPC_NVP FSM

Recommended Action No action is required.

Explanation Illegal event received in NPC_VSAN FSM

Recommended Action No action is required.

NPV Messages

This section contains the NPV messages.

NPV-2

Explanation Due to port flaps, link outages, switch restart etc. a CFS peer switch of NPV was lost. The current configuration changes would not be applied to this peer until the peer merges with this switch. The CFS merge may fail if the configuration at the lost peer conflicts with the changes made in this session. It is recommended that the user abort this CFS session using ivr abort command and then re-enter the configuration changes.

Recommended Action No action is required.

Explanation NPM could not disabled due to the reason specified. Please try again.

Recommended Action No action is required.

Explanation NPM could not enabled due to the reason specified. Please try again.

Recommended Action No action is required.

Explanation NPM process encountered a critical error as specified, and so NPV process cannot continue.

Recommended Action No action is required.

NPV-3

Explanation ACL update request initiated by the NPV process has failed

Recommended Action No action is required.

Explanation NPV process received invalid payload from CFS.

Recommended Action No action is required.

Explanation An error occurred while clearing the lock. The reason for the failure: [chars]

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation An error occurred while committing configuration. The reason for the failure: [chars]

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation An error occurred while committing configuration. Configuration could not be committed on some switches. The reason for the failure: [chars]. Configuration can be inconsistent in the fabric.

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation Commit request received from remote switch is rejected. The reason for the failure: [chars]

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation NPV process could send an FC2 message.

Recommended Action No action is required.

Explanation NPV process sent an F_RJT frame.

Recommended Action No action is required.

Explanation NPV process encountered a general error, one that does not fall in any of the categories. [chars] describes the error and its context.

Recommended Action No action is required.

Explanation LCP programming request initiated by the NPV process has failed

Recommended Action No action is required.

Explanation An error occurred while acquiring the lock. The reason for the failure: [chars]

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation NPV process received an LS_RJT frame.

Recommended Action No action is required.

Explanation NPV process sent an LS_RJT frame.

Recommended Action No action is required.

Explanation NPV process could not allocate memory

Recommended Action No action is required.

Explanation An error occurred while activating merged configuration. The reason for the failure: [chars]

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation An error occurred while merging configuration. The reason for the failure: [chars]

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation NPV process could not send an MTS message.

Recommended Action No action is required.

Explanation NPIV feature could not be disabled.

Recommended Action No action is required.

Explanation NPV CFS distribution might not work. Try enabling it again on the command line. Make sure cfs distribution is enabled.

Recommended Action No action is required.

Explanation NPV process has failed to bringup the port

Recommended Action No action is required.

Explanation Port re-initiate request initiated by the NPV process has failed

Recommended Action No action is required.

Explanation An error occurred while releasing the lock. The reason for the failure: [chars]

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

NPV-4

Explanation This syslog is printed when the external interface fails to come up due to NPIV feature not enabled on the upstream switch.

Recommended Action Verify and enable NPIV feature in upstream switch.

Explanation This syslog is printed when the external interface fails to come up due to upstream port VSAN mis-match with the upstream switch.

Recommended Action Make sure port VSAN is same on both sides of this external link

NPV-5

Explanation An assertion failed in NPV code

Recommended Action No action is required.

Explanation The virtual port WWN will be used as port WWN for devices logging in on this interface.

Recommended Action No action is required.

Explanation The virtual port WWN will be used as port WWN for devices logging in on this interface.

Recommended Action No action is required.

Explanation The physical port WWN will be used as port WWN for devices logging in on this interface.

Recommended Action No action is required.

Explanation NPV process discarded an FC2 frame.

Recommended Action No action is required.

Explanation Server ports are reinitialized to balance the loads on the external interfaces.

Recommended Action No action is required.

Explanation NPV process has received an unexpected event in the current state.

Recommended Action No action is required.

NPV-6

Explanation NPV process sent an ABTS frame.

Recommended Action No action is required.

Explanation NPV process sent an ELS frame to the core switch.

Recommended Action No action is required.

Explanation NPV process sent an ELS frame to the server.

Recommended Action No action is required.

Explanation NPV process has selected an external interface to forward either all frames received on a server interface or frames received from a specific port WWN.

Recommended Action No action is required.

Explanation NPV process sent a LOGO frame to the device as the corresponding external interface went down.

Recommended Action No action is required.

Explanation NPV process received an FDISC frame.

Recommended Action No action is required.

Explanation NPV process sent an FDISC frame to the core switch.

Recommended Action No action is required.

Explanation NPV process received an FLOGI frame.

Recommended Action No action is required.

Explanation NPV process sent an internal FLOGI frame to the core switch on an external interface.

Recommended Action No action is required.

Explanation NPV process received a LOGO frame.

Recommended Action No action is required.

Explanation NPV process sent a LOGO frame.

Recommended Action No action is required.

Explanation NPV process received an LS_ACC frame.

Recommended Action No action is required.

Explanation NPV process sent an LS_ACC frame.

Recommended Action No action is required.

Explanation NPV process received an MTS notification.

Recommended Action No action is required.

Explanation NPV process sent an MTS notification.

Recommended Action No action is required.

Explanation NPV process received an MTS request.

Recommended Action No action is required.

Explanation NPV process sent an MTS request.

Recommended Action No action is required.

Explanation NPV process received an MTS response.

Recommended Action No action is required.

Explanation NPV process sent an MTS response.

Recommended Action No action is required.

Explanation NPIV feature has been disabled.

Recommended Action No action is required.

Explanation NPIV feature has been enabled.

Recommended Action No action is required.

Explanation NPV feature enable/disable is in progress. This syslog is printed at the beginning of various significant phases.

Recommended Action No action is required.

Explanation Timer started for upon external interface up or server interface down. When the timer goes off some of the server interfaces may be reinitialized to evenly distribute the server interfaces amongst the eligible external interfaces.

Recommended Action No action is required.

Explanation NPV process sent a LOGO frame to the core switch as the server interface went down.

Recommended Action No action is required.

NPV-7

Explanation CFS request is received. The WWN of the switch originated this request and the RR-token of the request are provided in the syslog message.

Recommended Action No action is required.

Explanation CFS response is sent. The re-token of the corresponding request and the status are provided in the syslog message

Recommended Action No action is required.

NTP Messages

This section contains the NTP messages.

NTP-2

Explanation NTP syslog Critical Error: [chars].

Recommended Action No action is required.

Explanation NTP Initialization Failed: [chars] [chars].

Recommended Action No action is required.

Explanation NTP did not receive response from the linecard for the request sent.

Recommended Action No action is required.

NTP-3

Explanation NTP syslog allocation failed: [chars].

Recommended Action No action is required.

Explanation NTP syslog Error Exit: [chars] [dec].

Recommended Action No action is required.

Explanation NTP syslog Error: [chars].

Recommended Action No action is required.

Explanation NTP MTS Error: [chars].

Recommended Action No action is required.

NTP-6

Explanation NTP syslog created: [chars] [chars].

Recommended Action No action is required.

Explanation NTP syslog Exit: [chars].

Recommended Action No action is required.

Explanation NTP logging: [chars].

Recommended Action No action is required.

Explanation NTP syslog Warning: [chars].

Recommended Action No action is required.

NVP Messages

This section contains the NVP messages.

NVP-6

Explanation NVP daemon informational message

Recommended Action No action is required.

Explanation The NVP daemon successfully started

Recommended Action No action is required.

NVP-SLOT#-2

Explanation Component caused critical error

Recommended Action Restart the linecard

OBFL Messages

This section contains the OBFL messages.

OBFL-3

Explanation Obfl_encountered an error

Recommended Action No action is required.

OC_USD Messages

This section contains the OC_USD messages.

OC_USD-2

Explanation Octopus received packets with CRC error from fabric or from module

Recommended Action Use another optical cable and transceivers. If the problem still persists, change the peer ports, such as the remote port to another or the local port to another. Run the commands ‘diagnostic start module <mod> test all’ and ‘show diagnostic result module <mod> test all detail’. The result will display the information about the failures in HW, if any.

ONEP Messages

This section contains the ONEP messages.

ONEP-2

Explanation The Onepsync ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.

Recommended Action LOG_STD_SH_CMD_ACTION (show logging and show checkpoint client)

Explanation The Onepsync ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.

Recommended Action LOG_STD_ACTION

Explanation The Network Element and Persistent Storage for the running-config are out of sync. If no other error has occurred, the Network Element configuration will take precedence.

Recommended Action LOG_STD_SH_CMD_ACTION (Try reconfiguring the item, possibly using the [no] form to restore a default value if a new one doesn’t take. The 'show running-config' command should be used to see if this error persists.

Explanation The Network Element and Persistent Storage for the running-config are out of sync. If no other error has occurred, the Network Element configuration will take precedence.

Recommended Action LOG_STD_SH_CMD_ACTION (Try reconfiguring the item, possibly using the [no] form to restore a default value if a new one doesn’t take. The 'show running-config' command should be used to see if this error persists.

Explanation The Onepsync ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.

Recommended Action LOG_STD_SH_CMD_ACTION (show logging and show checkpoint client)

Explanation The Onepsync ISSU client failed to start session negotiation. If a problem occurs with the ISSU session start, the standby device cannot be brought up properly.

Recommended Action LOG_STD_SH_CMD_ACTION (show issue session <client_id>

Explanation The Onepsync ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.

Recommended Action LOG_STD_SH_CMD_ACTION (show issu capability entries <client_id>

ONEP-3

Explanation The session authentication has failed

Recommended Action LOG_STD_SH_CMD_ACTION (Check users credentials are matched against the AAA/ local users configured on the Network Element.)'

Explanation The usage of the resource has exceeded the configured threshold value

Recommended Action LOG_STD_SH_CMD_ACTION (Check the current resource usage and configured resource threshold. cpu threshold rising <value>

Explanation The requested service set is in disabled state. All the service requests for that service set will be rejected.

Recommended Action LOG_STD_SH_CMD_ACTION (Make sure the service set is enabled. connect edness service set <name>

Explanation The connection request to the network element already exists

Recommended Action LOG_STD_SH_CMD_ACTION (Make sure the uniqueness of the application name. One session per application is allowed on a network element.)

Explanation The Onepsync ISSU client does not have a valid registered session.

Recommended Action LOG_STD_SH_CMD_ACTION (show issue capability entries <client_id>

Explanation The requested service set is in disabled state. All the service requests for that service set will be rejected.

Recommended Action LOG_STD_SH_CMD_ACTION (Make sure the service set is enabled. connected apps service set lisp)

Explanation The Onepsync ISSU client received an incompatible message from the peer device. The message cannot be processed.

Recommended Action LOG_STD_SH_CMD_ACTION (show issu message group <client_id>

Explanation The Onepsync ISSU client failed to calculate the MTU for the specified message. The Onepsync ISSU client is not able to send the message to the standby device.

Recommended Action LOG_STD_SH_CMD_ACTION (show issu message group <client_id>

Explanation The Onepsync ISSU client failed to unregister session information.

Recommended Action LOG_STD_SH_CMD_ACTION (show issu session <client_id

Explanation The ONE-P client service set version is incompatible with the one installed on the network element

Recommended Action LOG_STD_SH_CMD_ACTION (Make sure the version running on the client side is compatible with the one installed on the network element)

ONEP-4

Explanation Administrator has disabled ONEP feature while application sessions were active. All active sessions have been terminated. To enable ONEP again use 'feature onep' command in configuration mode.

Recommended Action LOG_STD_SH_CMD_ACTION (No action is required if this was deliberate operation. To enable ONEP again use 'feature onep' command in configuration mode.)

ONEP-6

Explanation This syslog message is used to display one PK history messages when the history syslog' one p command is enabled.

Recommended Action LOG_STD_SH_CMD_ACTION (No action is required. Use no history syslog at the onep configuration prompt to turn off this logging if desired).

ORI_FWD Messages

This section contains the ORI_FWD messages.

ORI_FWD-2

Explanation Debug log message

Recommended Action No action is required.

ORI_FWD-6

Explanation Debug log message

Recommended Action No action is required.

ORI_MAC Messages

This section contains the ORI_MAC messages.

ORI_MAC-2

Explanation Debug log message

Recommended Action No action is required.

ORI_MAC-6

Explanation Debug log message

Recommended Action No action is required.

ORI_XBAR_USD Messages

This section contains the ORI_XBAR_USD messages.

ORI_XBAR_USD-2

Explanation Critical log message

Recommended Action No action is required.

Explanation FR CRC Message

Recommended Action No action is required.

Explanation Sync loss error

Recommended Action No action is required.

ORI_XBAR_USD-4

Explanation Warning log message

Recommended Action No action is required.

ORI_XBAR_USD-6

Explanation Debug log message

Recommended Action No action is required.

OTM Messages

This section contains the OTM messages.

OTM-2

Explanation OTM process failed to register with eem, exiting now

Recommended Action No action is required.

OTM-3

Explanation [chars1][chars2]

Recommended Action No action is required.

OTM-5

Explanation Status of tracking object [dec] changed to [chars]

Recommended Action No action is required.

Explanation Tracking Object [dec] configured, status of the object [chars]

Recommended Action No action is required.

OTM-6

Explanation OTM process is terminated

Recommended Action No action is required.

Explanation Tracking Object [dec] removed

Recommended Action No action is required.

Explanation OTM process is up and running

Recommended Action No action is required.

Explanation Client has started tracking object [dec]

Recommended Action No action is required.

Explanation Client has stopped tracking object [dec]

Recommended Action No action is required.

Recommended Action

PHY_USD Messages

This section contains the PHY_USD messages.

PHY_USD-SLOT#-4

Explanation Port Link status changed while performing an In Service System Upgrade. Disabling the port.

Recommended Action No action is required.

PIXM Messages

This section contains the PIXM messages.

PIXM-2

Explanation PIXM has encountered a critical error

Recommended Action Please collect PIXM tech support using show tech pixm' and 'show tech pixmc-all''

PIXM-3

Explanation PIXM has encountered a error

Recommended Action Please collect PIXM tech support using show tech pixm' and 'show tech pixmc-all'

PIXM-4

Explanation PIXM has encountered a warning-level error

Recommended Action Please collect PIXM tech support using show tech pixm' and 'show tech pixmc-all'

PIXM-7

Explanation This is a debug output from PIXM

Recommended Action Please collect PIXM tech support using 'show tech pixm' and 'show tech pixmc-all''

PLATFORM Messages

This section contains the PLATFORM messages.

PLATFORM-0

Explanation Clock module on chassis detected a failure and switched to redundant clock module.

Recommended Action Please perform a 'show platform internal info' to collect more information.

Explanation Chassis clock source has failed and system will be reset. System will automatically start using redundant clock module.

Recommended Action Please refer to the platform document on clock modules.

Explanation Chassis clock source has switched and all Vegas line cards will be reset. System will automatically continue using redundant clock module.

Recommended Action Please refer to the platform document on clock modules.

Explanation Fan module is removed. This could lead to temperature alarms.

Recommended Action Replace the fan module ASAP.

Explanation Module in slot [decimal digit] exceeded major temperature threshold.

Recommended Action Please perform a 'show environment temperature' to collect more information.

Explanation Module in slot [decimal digit] shutdown due to temperature exceeding major threshold.

Recommended Action Please perform a 'show environment temperature' to collect more information.

Explanation Module in slot [decimal digit] exceeded warm temperature threshold.

Recommended Action Please perform a 'show environment temperature' to collect more information.'

Explanation Platform Emergency

Recommended Action No action is required.

Explanation The supervisor in slot [decimal digit] was not able to read its SPROM.

Recommended Action No action is required.

Explanation The supervisor is coming up in wrong slot [decimal digit].

Recommended Action No action is required.

Explanation Failed to load drivers.

Recommended Action Image is possibly corrupt. Try to load a different image.

Explanation System shutdown in [decimal digit] seconds.

Recommended Action Please perform a 'show environment temperature' to collect more information.

Explanation System shutdown in [decimal digit] seconds due to removal of fan module.

Recommended Action Please perform a 'show environment fan' to collect more information.

Explanation System shutdown in [decimal digit] seconds due to less than 4 fans operating.

Recommended Action Please perform a 'show environment fan' to collect more information.

Explanation System shutdown in [decimal digit] seconds due to temperature exceeding major threshold.

Recommended Action Please perform a 'show environment temperature' to collect more information.

Explanation Failed to load drivers.

Recommended Action Image is possibly corrupt. Try to load a different image

Explanation The xbar in slot [decimal digit] encountered clock failure.

Recommended Action No action is required.

Explanation The xbar in slot [decimal digit] is incompatible with backplane chassis.

Recommended Action No action is required.

Explanation The xbar in slot [decimal digit] powered up in wrong slot.

Recommended Action No action is required.

PLATFORM-1

Explanation Fan module has failed leaving less than 4 total fans operating. Fan needs to be replaced. This can lead to overheating and temperature alarms.

Recommended Action Please perform a 'show platform internal info' to collect more information.'

Explanation Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.

Recommended Action Please perform a 'show plat form internal info' to collect more information.'

Explanation Platform Alert

Recommended Action No action is required.

Explanation Current power supply redundancy mode may not be optimal

Recommended Action Please perform a 'show environment power' and 'show platform internal info' to collect more information.'

Explanation Available power in power supplies is not sufficient to power up the xbar

Recommended Action You can verify available power and current usage using command 'show environment power'. Please Refer To Power Supply Document On How To Increase Power Supply Capacity.

PLATFORM-2

Explanation Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.

Recommended Action Please perform a 'show platform internal info' to collect more information.

Explanation Fan module is ok.

Recommended Action No action is required.

Explanation Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.

Recommended Action Please perform a 'show platform internal info' to collect more information.

Explanation Fan module is ok.

Recommended Action No action is required.

Explanation Clock module on chassis is faulty or has been removed.

Recommended Action Please perform a 'show platform internal info' to collect more information.

Explanation Clock module on chassis is functioning properly.

Recommended Action No action is required.

Explanation The current chassis clock source is [decimal digit].

Recommended Action No action is required.

Explanation The specified fanlets have failed. This can lead to overheating and temperature alarms.

Recommended Action Please perform a to collect more information 'show platform internal info' to collect more information.

Explanation Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.

Recommended Action Please perform a 'show platform internal info' to collect more information.'

Explanation Fan module is ok

Recommended Action No action is required.

Explanation Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.

Recommended Action Please perform a 'show platform internal info' to collect more information.'

Explanation Fan is ok

Recommended Action No action is required.

Explanation Fan module is ok

Recommended Action No action is required.

Explanation Fan module is removed

Recommended Action No action is required.

Explanation Fan module is removed

Recommended Action No action is required.

Explanation Could not program the mac address for the management port of all the VDCs

Recommended Action No action is required.

Explanation Memory alert event received

Recommended Action None

Explanation Memory alert event received

Recommended Action None

Explanation All modules in switch are powered down because all xbar modules are offline

Recommended Action Please perform a 'show module', 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' to collect more information if you suspect module has been powered down due to errors. At least one Xbar module has to be for modules to function'

Explanation A new module in slot [decimal digit] is detected.

Recommended Action No action is required.

Explanation Available power in power supplies is not sufficient to power up the module

Recommended Action You can verify available power and current usage using command 'show environment power'. Please refer to power supply document on how to increase power supply capacity.

Explanation The module in slot [decimal digit] is powered down.

Recommended Action Please perform a 'show module', 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' to collect more information if you suspect module has been powered down due to errors'

Explanation The module can not be powered up because all the ejectors are open

Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information

Explanation The module in slot [decimal digit] failed to power up

Recommended Action Please perform a 'show platform internal all module [decimal digit]' and to collect more information.

Explanation The module can not be powered up due to IDPROM read error

Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.

Explanation The module can not be powered up due to missing SWID in core-plugin for this CARDID

Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.

Explanation Modules powered up because at least one xbar module is online

Recommended Action No action needed

Explanation The module in slot [decimal digit] is powered up.

Recommended Action No action is required.

Explanation The module in slot [decimal digit] has been removed.

Recommended Action No action is required.

Explanation Module in slot [decimal digit] warm temperature threshold.

Recommended Action Please perform a 'show environment temperature' to collect more information.'

Explanation Module in slot [decimal digit] major temperature threshold.

Recommended Action Please perform a 'show environment temperature' to collect more information.

Explanation Module in slot [decimal digit] has exceeded minor temperature threshold.

Recommended Action Please perform a 'show environment temperature' to collect more information.

Explanation Module in slot [decimal digit] warm temperature threshold.

Recommended Action Please perform a 'show environment temperature' to collect more information.

Explanation Module in slot [decimal digit] minor temperature threshold.

Recommended Action Please perform a show environment temperature' to collect more information.

Explanation Module in slot [decimal digit] recovered from major temperature threshold. Minor threshold still exceeded.

Recommended Action Please perform a 'show environment temperature' to collect more information.

Explanation Module in slot [decimal digit] warm temperature threshold.

Recommended Action Please perform a 'show environment temperature' to collect more information

Explanation Platform Critical

Recommended Action No action is required.

Explanation Could not access some modules using BUS_A, but can access using BUS_B

Recommended Action Please perform a 'show platform internal err''

Explanation Could not access some modules using BUS_A, but can access using BUS_B

Recommended Action Please perform a 'show platform internal err’

Explanation This image version is not supported in this chassis.

Recommended Action Sup-platform

Explanation No bootflash found.

Recommended Action Try to put in a bootflash in the module and try again.

Explanation Bad bootflash/corrupted filesystem.

Recommended Action Try to put in a known good bootflash in the module and try again.

Explanation Module Powered Down, because Module is not supported in this chassis. (Chassis Incompatible card)

Recommended Action Please perform a 'show module' to see the Power Down reason.'

Explanation Netboot failed.

Recommended Action Try to replace the BIOS in the module.

Explanation Module registration failed.

Recommended Action Try to replace the module.

Explanation Status for the module that failed registration.

Recommended Action Try to replace the module.

Explanation Supervisor is running low on memory

Recommended Action Switchover

Explanation Policy trigger initiated a module power off

Recommended Action None

Explanation User initiated a module power-off from the CLI

Recommended Action None

Explanation User initiated a module power-on from the CLI

Recommended Action None

Explanation User initiated a module reload from the CLI

Recommended Action None

Explanation Standby supervisor failed to power up.

Recommended Action Try to replace the standby supervisor.

Explanation Deep sleep mode initiated by the Connectivity Management Processor (CMP) for this supervisor

Recommended Action No action is required.

Explanation Using a wrong version of Epld version can result in unexplainable behaviour

Recommended Action Upgrade Power Management EPLD

Explanation Standby supervisor failed to power up.

Recommended Action Try to replace the standby supervisor.

Explanation Policy/trigger initiated a system reload

Recommended Action None

Explanation User initiated a system reload from the CLI

Recommended Action None

Explanation Policy/trigger initiated a system shutdown

Recommended Action None

Explanation User initiated a xbar reload from the CLI

Recommended Action None

Explanation Plugin not loaded, The LC cannot be powered up

Recommended Action Load the associated plugin

Explanation Power Supply is absent.

Recommended Action No action is required.

Explanation Only one power supply is functional. The Cisco MDS 9250i Switch requires at least two power supplies.

Recommended Action Please perform a 'show environment power' and 'show platform internal info' to collect more information.'

Explanation Only one power supply is functional. The Cisco MDS 9250i Switch requires at least two power supplies.

Recommended Action Please perform a 'show environment power' and 'show platform internal info' to collect more information.'

Explanation Only two Power supply are functional, please connect third Power supply for redundancy

Recommended Action Please perform a 'show environment power' and 'show platform internal info' to collect more information.'

Explanation Detected power supply capacity change.

Recommended Action Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc. Please perform 'show environment power 'and 'show platform internal info' to collect more information.'

Explanation Detected a power supply that has differing capacity than an the other power supply.

Recommended Action Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc. Please perform 'show environment power' and 'show platform internal info' to collect more information.

Explanation Power Supply is detected but shutdown.

Recommended Action Please perform a 'show environment power' and 'show platform internal info' to collect more information.

Explanation Power Supply has failed or has been shutdown

Recommended Action Please perform a 'show environment power' and 'show platform internal info' to collect more information. Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc.

Explanation Fan module in the Power Supply has failed

Recommended Action Please perform a 'show environment power' and 'show platform internal info' to collect more information.

Explanation Fan module in the Power Supply is OK.

Recommended Action No action is required.

Explanation Detected a new power supply that has reduced capacity than an existing power supply.

Recommended Action Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc. Please perform 'show environment power' and 'show platform internal info' to collect more information.

Explanation Power Supply is OK.

Recommended Action No action is required.

Explanation Power Supply is present but not at full capacity.

Recommended Action No action is required.

Explanation Power supply redundancy mode changed notification

Recommended Action Please perform a 'show environment power' and 'show platform internal info' to collect more information.

Explanation Power Supply redundancy mode changes.

Recommended Action No action is required.

Explanation Unexpected removal the only power supply in the system.

Recommended Action Power supply unit may be faulty. Contact CISCO to replace the unit.

Explanation Power Supply is removed.

Recommended Action No action is required.

Explanation Unable to determine power supply type. Default power supply types will be assumed.

Recommended Action Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc.

Explanation This power supply is not supported for the CISCO Multilayer Switches.

Recommended Action Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc.

Explanation Chassis IDPROM [decimal digit] re-initialization was unsuccessful. Data is invalid.

Recommended Action Please perform a 'shows prom module [decimal digit]1' to read module IDPROM contents and collect more information.

Explanation Chassis IDPROM [decimal digit] invalid data was successfully re-initialized to valid.

Recommended Action Please perform a 'shows prom module [decimal digit]1' to read module IDPROM contents and collect more information.

Explanation Chassis IDPROM [decimal digit] contains invalid data.

Recommended Action Please perform a 'shows prom module [decimal digit]1' to read module IDPROM contents and collect more information.

Explanation A new xbar in slot [decimal digit] is detected.

Recommended Action No action is required.

Explanation The xbar can not be powered up because all the ejectors are open

Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.

Explanation The xbar in slot [decimal digit] has been removed.

Recommended Action No action is required.

PLATFORM-3

Explanation Ejector status has changed

Recommended Action None

Explanation The module can not be powered up even after three attempts

Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.

Explanation The module can not be powered up even after three attempts

Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.

Explanation Platform Error

Recommended Action No action is required.

Explanation Ejector status has changed

Recommended Action None

Explanation The module can not be powered up even after three attempts

Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.

Explanation The xbar can not be powered up even after three attempts

Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.

Explanation The xbar in slot [decimal digit] failed to power up

Recommended Action Please perform a 'show platform internal all module [decimal digit]' and to collect more information.

Explanation The xbar can not be powered up due to IDPROM read error

Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.

Explanation The xbar can not be powered up due to missing SWID in core-plugin for this CARDID

Recommended Action Please perform a 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' 'show sprom xbar [dec] [dec]' to read module IDPROM contents to collect more information.

PLATFORM-4

Explanation Module in slot [decimal digit] unable to access temperature sensor.

Recommended Action Please perform a 'show environment temperature' to collect more information.

Explanation Module in slot [decimal digit] contains a faulty temperature sensor.

Recommended Action Please perform a 'show environment temperature' to collect more information.

Explanation Fan Filter status: Present/Absent

Recommended Action Please perform a 'show platform internal info.'

Explanation Power redundancy mode changed

Recommended Action Please perform a 'show platform internal info.'

Explanation Platform Warning

Recommended Action No action is required.

PLATFORM-5

Explanation Fan module is detected

Recommended Action No action is required.

Explanation Fan module is detected

Recommended Action No action is required.

Explanation Fan module changed status

Recommended Action No action is required.

Explanation Fan module changed status

Recommended Action No action is required.

Explanation FEX Fan module is detected

Recommended Action No action is required.

Explanation FEX Fan module is removed

Recommended Action No action is required.

Explanation FEX power supply is found

Recommended Action No action is required.

Explanation FEX power supply is removed

Recommended Action No action is required.

Explanation Module in slot [decimal digit] changed status.

Recommended Action No action is required.

Explanation Platform Notice

Recommended Action No action is required.

Explanation Power Supply is detected.

Recommended Action No action is required.

Explanation Module in slot [decimal digit] changed status.

Recommended Action No action is required.

Explanation The xbar in slot [decimal digit] is powered down.

Recommended Action Please perform a 'show module xbar', 'show platform internal all module [decimal digit]' and 'show module internal all module [decimal digit]' to collect more information if you suspect module has been powered down due to errors.'

Explanation The xbar in slot [decimal digit] is powered up.

Recommended Action No action is required.

PLATFORM-6

Explanation Platform Info

Recommended Action No action is required.

PLATFORM-7

Explanation System shutdown in [decimal digit] seconds.

Recommended Action Please perform a 'show environment temperature' to collect more information.

PLOG_SUP Messages

This section contains the PLOG_SUP messages.

PLOG_SUP-4

Explanation Persistent Logger encountered an error

Recommended Action No action is required.

PLOG Messages

This section contains the PLOG messages.

PLOG-4

Explanation Persistent Logger encountered an error

Recommended Action No action is required.

PLSM Messages

This section contains the PLSM messages.

PLSM-3

Explanation Error Disabled Policy State for a interface.

Recommended Action None

PLSM-6

Explanation EDP State cleared for a interface.

Recommended Action None

PLTFM_CONFIG Messages

This section contains the PLTFM_CONFIG messages.

PLTFM_CONFIG-3

Explanation LOU threshold response to commit failed.

Recommended Action No action is required.

Explanation LOU threshold response to commit timed out.

Recommended Action No action is required.

Explanation LOU threshold response to verify failed, so sending abort msg to all LC aclqos.

Recommended Action No action is required.

Explanation LOU threshold response to verify timed out, so sending abort msg to all LC aclqos.

Recommended Action No action is required.

PLTFM_CONFIG-4

Explanation Port-channel load-balancing works properly for non proxy VDCs only.

Recommended Action No action is required.

Explanation Port-channel load-balancing works properly for non proxy VDCs only.

Recommended Action No action is required.

Explanation This is a reminder that mixing non-XL and XL modules in the same VDC may limit XL modules to the capacity of non-XL modules.

Recommended Action No action is required.

PLUGIN Messages

This section contains the PLUGIN messages.

PLUGIN-2

Explanation Load request failed on standby

Recommended Action No action is required.

Explanation Plugin notify message returned failure.

Recommended Action No action is required.

Explanation The service failed to allocate memory.

Recommended Action No action is required.

Explanation Plugin extraction failed on standby

Recommended Action No action is required.

Explanation Plugin has internal error

Recommended Action No action is required.

Explanation Plugin has internal error

Recommended Action No action is required.

Explanation Failed to send plugin notify message

Recommended Action No action is required.

Explanation Standby received load sync and current standby does not have an outstanding load request

Recommended Action No action is required.

Explanation Standby received unload sync and current standby does not have an outstanding unload request

Recommended Action No action is required.

Explanation Unload request failed on standby

Recommended Action No action is required.

Explanation Failed to update system information

Recommended Action No action is required.

PLUGIN-3

Explanation Failed to send a message

Recommended Action No action is required.

PMON Messages

This section contains the PMON messages.

PMON-2

Explanation Port Group Rising Threshold Crossed

Recommended Action No action is required.

Explanation Port Monitor Critical Information

Recommended Action No action is required.

Explanation Initialization failed, need to exit.

Recommended Action No action is required.

Explanation Theres mts error.'

Recommended Action No action is required.

Explanation Port Guard config Applied

Recommended Action No action is required.

PMON-3

Explanation Port Monitor error

Recommended Action No action is required.

PMON-5

Explanation Port Group Falling Threshold Crossed

Recommended Action No action is required.

PMON-6

Explanation Port Monitor Log Information

Recommended Action No action is required.

PMON-SLOT-[num]-3-RISING_THRESHOLD_REACHED

Explanation [port-monitor counter] rising threshold value was reached.

Recommended Action No action is required.

PMON-SLOT-[num]-3-FALLING_THRESHOLD_REACHED

Explanation [port-monitor counter] falling threshold value was reached.

Recommended Action No action is required.

POAP Messages

This section contains the POAP messages.

POAP-2

Explanation Received DHCP NAK

Recommended Action No action is required.

Explanation POAP DHCP Discover phase started

Recommended Action No action is required.

Explanation POAP failure

Recommended Action No action is required.

Explanation POAP Info

Recommended Action No action is required.

Explanation POAP process initialized

Recommended Action No action is required.

Explanation Successfully downloaded POAP script file

Recommended Action No action is required.

Explanation POAP script execution success

Recommended Action No action is required.

Explanation POAP script execution started(MD5 not validated)

Recommended Action No action is required.

Explanation POAP script execution started(MD5 validated)

Recommended Action No action is required.

Explanation POAP boot file validation failed.

Recommended Action No action is required.

POAP-5

Explanation POAP Service Disabled

Recommended Action No action is required.

Explanation POAP Service enabled

Recommended Action No action is required.

PONG Messages

This section contains the PONG messages.

PONG-5

Explanation Pong Service Enabled

Recommended Action No action is required.

Explanation Pong Service Enabled

Recommended Action No action is required.

Explanation Pong packet injected

Recommended Action No action is required.

PORT-CHANNEL Messages

This section contains the PORT-CHANNEL messages.

PORT-CHANNEL-1

Explanation Module configuration failed

Recommended Action Module will be automatically reset

Explanation No enough memory

Recommended Action No action is required.

Explanation Parameter mapping failed

Recommended Action Specified service is misbehaving; check its status

Explanation Failed to send a multicast message to all modules, usually because some module went down

Recommended Action Run show port-channel consistency to check consistency

PORT-CHANNEL-2

Explanation Auto create port-channel is deprecated and disabled

Recommended Action Convert the auto created channel to persistent by doing port-channel <n

Explanation A module is reset for not responding or returning error

Recommended Action No action is required.

PORT-CHANNEL-3

Explanation Compatibility check failed when adding ports to port-channel

Recommended Action Make sure the compatibility parameters are consistent while adding ports to port-channel, or use force option

Explanation General error

Recommended Action No action is required.

Explanation Failed to send a lc_config message

Recommended Action No action is required.

Explanation Failed to send a lc_config unicast message

Recommended Action No action is required.

Explanation Failed to send a lc_config unicast message

Recommended Action No action is required.

Explanation Failed to send a message

Recommended Action No action is required.

Explanation Cannot find port-channel in its database, which indicates an inconsistency with an external component

Recommended Action No action is required.

Explanation Some operation timed out

Recommended Action Run show port-channel consistency to check all module connectivity and consistency

PORT-CHANNEL-4

Explanation Port is removed from a port-channel because different module was inserted or module config purged

Recommended Action You lost some ports from port-channel, check if you want to add ports in the new module to the same port-channel.

Explanation The port is operating as an individual link even though it is locally or remotely configured to be part of a port channel

Recommended Action Check the configuration of the port locally and remotely to ensure that it can operate as part of a port channel

Explanation Cannot find the port in port-channel database, which indicates an inconsistency with an external component

Recommended Action No action is required.

Explanation Warning of possible race condition

Recommended Action No action is required.

Explanation Received an unexpected response and discarded

Recommended Action No action is required.

PORT-CHANNEL-5

Explanation Auto create process on the port failed

Recommended Action No action is required.

Explanation A port-channel is created

Recommended Action No action is required.

Explanation A port-channel is deleted

Recommended Action No action is required.

Explanation The first operational port in a port-channel is changed

Recommended Action No action is required.

Explanation The port-channel number configured on the switch is larger than 128

Recommended Action Delete the set of port channel interface <port-channel interface

Explanation Ports are added to a port-channel

Recommended Action No action is required.

Explanation Port goes down in a port-channel

Recommended Action No action is required.

Explanation Ports are removed from a port-channel

Recommended Action No action is required.

Explanation Port comes up in a port-channel

Recommended Action No action is required.

PORT-CHANNEL-6

Explanation Resync modules with sup after an error or switchover

Recommended Action No action is required.

PORT-CHANNEL-7

Explanation Port-channel manager finished global synchronization

Recommended Action No action is required.

Explanation Port-channel manager requested a global synchronization from active sup

Recommended Action No action is required.

Explanation Port-channel manager started in active mode

Recommended Action No action is required.

Explanation Port-channel manager started with default configuration

Recommended Action No action is required.

Explanation Port-channel manager started in standby mode

Recommended Action No action is required.

Explanation Port-channel manager started with running configuration

Recommended Action No action is required.

Explanation Port-channel manager started with startup configuration

Recommended Action No action is required.

PORT-PROFILE Messages

This section contains the PORT-PROFILE messages.

PORT-PROFILE-2

Explanation Interface Database Refresh failed

Recommended Action No action is required.

PORT-PROFILE-3

Explanation SDM process could not allocate heap memory in File: [chars], at line: [dec], for memory-type:[dec] of Size:[dec]

Recommended Action No action is required.

Explanation PPM Process assertion failed in File: [chars], at line: [dec]

Recommended Action No action is required.

Explanation Running-config collection failed for: [chars]

Recommended Action No action is required.

Explanation Config Apply Failed

Recommended Action No action is required.

Explanation Interface could not be shutdown after profile re-inherit

Recommended Action No action is required.

Explanation Interface could not be shutdown after failure to apply commands

Recommended Action No action is required.

Explanation Port-profile:[chars] creation failed with [:chars]

Recommended Action No action is required.

Explanation Port-profile:[chars] de-inherit failed with [:chars] on [:chars]

Recommended Action No action is required.

Explanation Port-profile:[chars] deletion failed with [:chars]

Recommended Action No action is required.

Explanation Port-profile:[chars] disable failed with [:chars]

Recommended Action No action is required.

Explanation Port-profile:[chars] enable failed with [:chars]

Recommended Action No action is required.

Explanation Port-profile:[chars] inherit failed with [:chars] on [:chars]

Recommended Action No action is required.

PORT-PROFILE-6

Explanation Port-profile:[chars] is created

Recommended Action No action is required.

Explanation Port-profile:[chars] is de-inherited on [:chars]

Recommended Action No action is required.

Explanation Port-profile:[chars] is deleted

Recommended Action No action is required.

Explanation Port-profile:[chars] is disabled

Recommended Action No action is required.

Explanation Port-profile:[chars] is enabled

Recommended Action No action is required.

Explanation Port-profile:[chars] is inherited on [:chars]

Recommended Action No action is required.

PORT-RESOURCES Messages

This section contains the PORT-RESOURCES messages.

PORT-RESOURCES-3

Explanation Failed to send a message

Recommended Action No action is required.

PORT-RESOURCES-5

Explanation Interfaces may not acquire port activation license during installation

Recommended Action Install a valid port activation license file

PORT-SECURITY Messages

This section contains the PORT-SECURITY messages.

PORT-SECURITY-2

Explanation Memory allocation failed for size [dec] for [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 Feature [chars] is unavailable and will be disabled now

Recommended Action Please install the correct license and reenable

PORT-SECURITY-3

Explanation An already logged in device is in conflict with the PSM active binding configurations. [chars] indicates the WWN of the login entity, interface

Recommended Action For port-security, the auto-learn feature can be used with activation to prevent this. This violating device or switch will be logged out

Explanation A login happened that violates PSM binding configurations [chars] indicates the WWN of the login entity

Recommended Action Only entries in the activated database of PSM can login. Change the config and activate it again

Explanation An error occurred during the processing of a CFS notification. [chars] indicates the actual cause for the error

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation An error occurred during an PSM database operation. [chars] indicates the reason for the error

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation EFMD fc2 operation 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 EFMD initiate 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 Received a corrupted EFMD Request Packet

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 An error happened during PSM Initialization. [chars] indicates the reason for failure

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation An already logged in device that is learnt during activation is in conflict with the PSM active binding configurations. [chars] indicates the WWN of the login entity, interface

Recommended Action Copy the active-db to config-db and reactivate. Not doing so could result in unexpected login rejects later on that interface.

Explanation An error occurred in processing of an MTS message. [chars] indicates the error that occurred

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 An error occurred during an PSM PSS operation. [chars] indicates the PSS operation that caused the error

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

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 Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

PORT-SECURITY-4

Explanation Activation of bindings failed due to [chars]

Recommended Action Correct the error and reactivate it again

PORT-SECURITY-6

Explanation An event happened that affects PSM. [chars] indicates the event

Recommended Action No action is required.

PORT Messages

This section contains the PORT messages.

PORT-2

Explanation The interface encountered an error while configuring it. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Collect more information about failed interface using command ‘show port internal all interface [char]'. In most cases, you can recover using following commands 'config terminal', 'interface [char]', 'shutdown', 'noshutdown' on the interface or removing and re-inserting the fibre optic cable

Explanation The physical link has gone down

Recommended Action Ensure that the cable is connected and the remote end is not shut down

PORT-3

Explanation There was an alarm on the transceiver module. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please do show interface transceiver details to obtain more information

Explanation Transceiver error read failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Remove and insert the SFP back again. If the problem persists check if the transceiver is supported using the command: show interface transceiver. Please contact customer support to resolve the condition

Explanation Transceiver is not from an authorized vendor

Recommended Action This command will determine the transceiver being used: show interface transceiver. Please contact customer support for a list of authorized transceiver vendors

PORT-4

Explanation The transceiver for the interface specified has not been qualified on this platform for this software release

Recommended Action Replace the module with a supported transceiver. Contact Cisco TAC to get platform transceiver qualification details

Explanation SFP clock rate mismatch/failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Remove the SFP and insert a new one with a different frequency type. If the problem persists check if the transceiver is supported using the command: show interface transceiver. Please contact customer support to resolve the condition

Explanation There was an warning on the transceiver module. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please do show interface transceiver details to obtain more information

Explanation The port has detected port security violation. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Check port security configuration on interface

PORT-5

Explanation Trunk protocol, EPP is disabled in the local/peer switch

Recommended Action Perform the following commands on the local/peer switch to enable EPP: config terminal, 'trunk protocol enable''

Explanation The Enterprise Package license is not available, so the extended credit feature has been disabled even though it was present in startup config

Recommended Action Install the Enterprise Package license and re-enable the extended credit feature

Explanation The Forward Correction Error (FEC) is not enabled on this link because the FEC may not have been configured at the peer.

Recommended Action Check the FEC configuration on both sides of the link.

Explanation SFP checksum on this interface failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Try to replace the SFP on this interface

Explanation Check peer interface configuration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation Check interface configuration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Try to change the configuration on the interface with the current available hardware capability

Explanation Interface has been configured to be administratively down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Perform the following commands to bring up the interface: config terminal', 'interface [char]', 'no shutdown''

Explanation The port has detected too high bit error rate in frames received from attached device. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Check the attached device; replace it if needed

Explanation One port across a link is part of a PortChannel while the other is not. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action While adding or deleting a member port from a PortChannel, both ports across the link should be added/deleted. No operation should be performed on either ports until they are both added/deleted.

Explanation FCIP interface temporarily down due to reconfiguration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation This interface belongs to a PortChannel and the PortChannel is configured to be administratively down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Perform the following commands on the PortChannel interface to which it belongs to bring the interface up: 'config terminal', 'interface [char]', 'shutdown', 'noshutdown''

Explanation The interface belongs to a PortChannel and a configuration is being attempted on the interface while there is a configuration in progress on the PortChannel. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Retry the configuration again

Explanation The F port is suspended due to being denied by port binding. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please check the port binding database to allow the host port to log in.

Explanation Isolated due to a failure while assigning a domain. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation The runtime fcdomain ID does not equal the static configured fcdomain ID. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Ensure that the fcdomain ID configuration matches the runtime config.

Explanation Invalid RCF received. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation Isolated due to domain manager being disabled. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation Remote end domain manager not responding. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation There are not enough allowed domains to merge the VSANs across the link. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Ensure that all assigned domain ids are in the configured allowed domains on both sides of the link.

Explanation Isolating this interface due to the remote end being isolated. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation Isolated due to domain overlap. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation The specified dynamic vsan is not configured on this switch. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Configure the dynamic vsan.

Explanation The specified dynamic vsan is in suspended state. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Un-suspend the dynamic vsan.

Explanation ELP failed on the interface due to class F param error. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Configure the attached switchport correctly and try again

Explanation ELP failed on the interface due to class N param error. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Configure the attached switchport correctly and try again

Explanation ELP failed on the interface due to invalid payload size

Recommended Action Configure the attached switchport correctly and try again

Explanation ELP failed on the interface due to invalid port name. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Configure the attached switchport correctly and try again

Explanation ELP failed on the interface due to invalid switch name. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Configure the attached switchport correctly and try again

Explanation ELP failed on the interface due to loopback connection detected. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Connect to a port on another switch and try again

Explanation ELP failed on the interface due to invalid transmit B2B credit. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Configure the attached switchport correctly and try again

Explanation ELP failed on the interface due to R_A_TOV or E_D_TOV mismatch. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Configure R_A_TOV and E_D_TOV values correctly and try again

Explanation ELP failed on the interface due to revision mismatch. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Configure the attached switchport correctly and try again

Explanation ELP failed on the interface due to invalid flow control code. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Configure the attached switchport correctly and try again

Explanation ELP failed on the interface due to invalid flow control param. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Configure the attached switchport correctly and try again

Explanation ELP failed on the interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Check the output of 'show port internal info' in the ELP failure reason field

Explanation Trunk protocol failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action 'show port internal even history msgs' will indicate the trunk protocol exchanges to determine why it failed.

Explanation ESC failed on the interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Check the output of 'show port internal event-history' to determine the ESC protocol exchanges to determine how it failed.

Explanation Ethernet link to which the FCIP interface is bound is down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Ensure that the ethernet cable is connected, the interface is administratively enabled

Explanation Ethernet link to which the FCIP interface is bound is down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Ensure that the ethernet cable is connected and the remote end is also active

Explanation Fabric binding failed on this port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please check the fabric binding database to ensure that the remote port is allowed to connect to this port

Explanation The FCOT has been removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Insert an FCOT

Explanation The FCOT has been removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Insert an FCOT

Explanation FCOT inserted is not a supported one. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please contact customer support for a list of authorized transceiver vendors

Explanation The port failed FC-SP authentication with its peer. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please check the FC-SP configuration.

Explanation FICON is being enabled on the port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please wait. This might take a while

Explanation FICON not enabled on port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please enable FICON on port

Explanation FICON is being enabled on the port VSAN of this port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action This is an intermediary state, whereby the port VSAN of the port is being enabled to be a FICON VSAN.

Explanation The modules hardware has failed.[optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Collect more information about failed module using command 'show module internal all module'

Explanation The port VSAN has been suspended or deleted. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Assign a new active port VSAN to the interface

Explanation The configured mode is not supported on this interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Perform a 'show port internal info' to determine the list of modes supported on this interface

Explanation The configured receive B2B credit size is not supported. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Get the allowed receive B2B credit size from show port internal info''

Explanation The configured receive buffer size is not supported. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Get the allowed receive buffer size from 'show port internal info'

Explanation The configured speed is not supported on this interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Perform a 'show port internal info' to determine the range of speed supported on this interface

Explanation The interface is in the process of coming up. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action If the interface is stuck in this state for a while, check the output of 'show port internal event-history' to determine what it is waiting for.

Explanation Interface removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation The peer port does not have the compatible security attributes. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please ensure that the peer port has compatible security attributes as the local port.

Explanation The local and peer port have a PortChannel membership misconfiguration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Ensure that both the local and peer ports are either both members of the same PortChannel or are not both part of PortChannel

Explanation Fabric binding failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please check fabric binding database

Explanation The physical link has gone down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Ensure that the cable is connected and the remote end is not shut down

Explanation Fcdomain applied a locally disruptive reconfiguration (local domain became invalid. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation Diag failed on the interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Collect more information about failed interface using command 'attach module' to connect to module

Explanation The interface is looped back to another interface on the same switch. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Check the connectivity of this interface and ensure that it is connected to another switch

Explanation Interface is down because the module was removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation There is no apparent reason the interface is down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Collect more information about port using command show port internal all interface [char]' to determine why it went down

Explanation The loop port has been put into non participating mode. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation The physical link has gone down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Ensure that the cable is connected and the remote end is not shut down

Explanation The trunk port is isolated as there are no common VSANs to be brought up with the peer port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please check that there are common VSANs configured and allowed to come up between the ports.

Explanation The interface has been placed into the offline state. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation Loopback tests. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please wait. This might take a while

Explanation The physical link has gone down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Ensure that the cable is connected and the remote end is not shut down

Explanation Parent interface is down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation The FCIP peer connected to this interface closed the TCP connection. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action This command will provide the peer IP address of this FCIP interface: show interface. Check to see why the peer closed the TCP connection

Explanation TCP connection to the FCIP peer got reset. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Check to see why the peer reset the TCP connection

Explanation Assign a port activation license to this port or install additional port activation licenses as needed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation Port binding failed on this port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please check the port binding database to ensure that the remote port is allowed to connect to this port

Explanation The port has been blocked by FICON configuration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please unblock the port in FICON configuration.

Explanation This is a PortChannel interface and all its members are operationally down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Enable at least one of the PortChannel members'

Explanation Isolated due to a mismatch in the configured port VSAN of the local and remote ends. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Configure the port VSAN of the local and remote interfaces to be the same and perform a shutdown' and a 'no shutdown'.

Explanation There is an RCF in progress. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation The software servicing the data path on the port has failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation Module that has the tunnel source port of this FCIP interface is not fully online. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action The module that has the tunnel src port is coming online. Please use show mod to find module status

Explanation Tunnel port source interface unbound. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation Tunnel source port of this FCIP interface has been removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action The src interface with ip address that matches the ip address of the bound entity is removed. This happens normally due to the module on which the src interface exists is removed

Explanation This interface belongs to a PortChannel and operational mode of the interface is different from that of the PortChannel. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Change the mode and the trunking mode of the PortChannel from auto and check to ensure that the remote end of the interface also belongs to the same Port Channel

Explanation This interface belongs to a PortChannel and operational speed of the interface is different from that of the PortChannel. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Change the speed of the PortChannel from auto and check to ensure that the remote end of the interface also belongs to the same Port Channel

Explanation This interface belongs to a PortChannel and remote switch WWN of the interface is different from that of the PortChannel. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Ensure that this interface is connected to the same remote switch as all the other interfaces in the PortChannel

Explanation This interface belongs to a PortChannel and has been suspended to an error while bringing it up. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action In most cases, you can recover using following commands 'config terminal', 'interface [char]', 'shutdown', 'noshutdown' on the interface.If this happens again obtain output of 'show port internal all interface [char]' on the interface

Explanation TCP session to the FCIP peer got closed due to loss of TCP keep alive. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command: trace route ip addr

Explanation Interface is down due to maximum retransmission failure. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command: trace route ip addr

Explanation TCP session to the FCIP peer closed because TCP persist timer expired. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command: trace route ip addr

Explanation The port has received too many interrupts in the hardware. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Check the attached device; replace it if needed

Explanation The port is suspended due to receiving a large number of invalid FLOGIs.[optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Please check the HBA and perform a shut, followed by no shut on the port.

Explanation Upgrade of the linecard software is in progress. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation Isolated due to virtual IVR domain overlap. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation This is a trunking interface and the VSANs configured do not match with the VSANs configured on the remote end. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Check the VSANs configured on the local end with the remote end

Explanation Isolated due to a failure during zone merge. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation Isolated due to remote zone server not responding. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation The interface is down due to port guard configuration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action Perform a shut followed by no shut to bring up the interface

Explanation There may be few packet drops due to this failure

Recommended Action No action is required.

Explanation Duplicate pss key detected

Recommended Action No action is required.

Explanation Interface [chars] is trunking, VSAN [chars] is down with reason in (). [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action The following commands will help determine why this VSAN is down on this interface: show interface, show port internal info interface VSAN, show port internal event-history interface VSAN

Explanation Interface [chars] is trunking, VSAN [chars] is up. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation Interface is up in mode specified, if applicable. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]

Recommended Action No action is required.

Explanation Module is not allowed to be operational due to the current system state

Recommended Action Use command show module <x>

Explanation Restore of module index may fail due to overlap of indices

Recommended Action No action is required.

Explanation Interfaces of the module may be in indeterminate state

Recommended Action Reload the module

PREFPATH Messages

This section contains the PREFPATH messages.

PREFPATH-1

Explanation Module configuration failed

Recommended Action No action is required.

Explanation Failed to send a multicast message to all modules, usually because some module went down

Recommended Action No action is required.

PREFPATH-2

Explanation Preferred Path initialization failed. [chars] explains the reason for the failure.

Recommended Action No action is required.

Explanation Preferred Path component encountered an error in processing an MTS message. The error and message are specified in the Message

Recommended Action No action is required.

Explanation Preferred Path 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.

PREFPATH-3

Explanation The Preferred Path has failed to program or erase Preferred Path related ACL. The error code returned by ACL module is [int.].

Recommended Action No action is required.

Explanation Preferred Path encountered a database error. [chars] specifies the context where the failure occurred.

Recommended Action No action is required.

Explanation Preferred Path failed to get response [chars] [int.] specify the context where the failure occurred.

Recommended Action No action is required.

Explanation General error

Recommended Action No action is required.

Explanation Preferred Path encountered an MTS error. [chars] specifies the context where the error occurred.

Recommended Action No action is required.

Explanation The Preferred Path has failed to activate route. The reason is [str.].

Recommended Action No action is required.

Explanation Preferred Path encountered a PSS error. [chars] specifies the context where the failure occurred.

Recommended Action No action is required.

Explanation Failed to interact with RIB for static route update, error description in [chars].

Recommended Action No action is required.

Explanation Preferred Path encountered a timeout [chars] [int.] specify the context where the failure occurred.

Recommended Action No action is required.

PREFPATH-4

Explanation Received an unexpected response and discarded

Recommended Action No action is required.

PREFPATH-6

Explanation The Preferred Path has successfully programmed or erased Preferred Path related ACL.

Recommended Action No action is required.

Explanation Preferred Path Service Up

Recommended Action No action is required.

Explanation Preferred Path has created its internal state stateless/stateful [chars].

Recommended Action No action is required.

PRIVATE_VLAN Messages

This section contains the PRIVATE_VLAN messages.

PRIVATE_VLAN-2

Explanation Association bring down failed

Recommended Action No action is required.

Explanation Association bringup failed

Recommended Action No action is required.

Explanation ELTM MTS send failed

Recommended Action No action is required.

Explanation ELTM timed out

Recommended Action No action is required.

Explanation ETHPM timed out

Recommended Action No action is required.

Explanation Hardware Configuration Error

Recommended Action No action is required.

Explanation PIXM MTS send failed

Recommended Action No action is required.

Explanation PIXM timed out

Recommended Action No action is required.

PRIVATE_VLAN-3

Explanation SDB Update failed

Recommended Action No action is required.

Explanation PVLAN in use

Recommended Action No action is required.

Explanation Restoring association operational status failed

Recommended Action No action is required.

PRIVATE_VLAN-5

Explanation PVLAN Service Disabled

Recommended Action No action is required.

Explanation Disabling of private-vlan failed

Recommended Action No action is required.

Explanation PVLAN Service Enabled

Recommended Action No action is required.

PROC_MGR Messages

This section contains the PROC_MGR messages.

PROC_MGR-SLOT#-2

Explanation Process manager error.

Recommended Action No action is required.

Explanation Process manager information.

Recommended Action Process manager information.

Explanation Application caused critical error.

Recommended Action Restart the linecard.

Explanation Application exited.

Recommended Action Check the application.

Explanation Component caused critical error.

Recommended Action Restart the linecard.

Explanation Critical error for component.

Recommended Action Restart the linecard.

Explanation Component dependency failure.

Recommended Action Check whether the component exists.

Explanation Component not installed.

Recommended Action Check whether the component exists.

Explanation Component initialization timed out.

Recommended Action Check the component.

Explanation Message to core client failed.

Recommended Action Restart the linecard.

Explanation Process manager quitting.

Recommended Action No action is required.

Explanation Removed KLM/Script.

Recommended Action No action is required.

Explanation Process stopped.

Recommended Action No action is required.

Explanation Process manager termination time.

Recommended Action No action is required.

Explanation Peek at utaker queue failed.

Recommended Action Restart the linecard.

Explanation Utaker semaphore allocation failed.

Recommended Action Restart the linecard.

Explanation Utaker semaphore get failed.

Recommended Action Restart the linecard.

Explanation Utaker semaphore give failed.

Recommended Action Restart the linecard.

Explanation Utaker semaphore take failed.

Recommended Action Restart the linecard.

PROC_MGR-SLOT#-3

Explanation Process manager Message

Recommended Action No action is required.

PROC_MGR-SLOT#-4

Explanation Application not sending heartbeat.

Recommended Action Check the application.

PROC_MGR-SLOT#-6

Explanation Process manager info message

Recommended Action No action is required.

PROFILER Messages

This section contains the PROFILER messages.

PROFILER-0

Explanation Profiler Emergency Message

Recommended Action Please file the bug for Profiler Library Component through CDETS

PROFILER-1

Explanation Profiler Alert Message

Recommended Action Profiler Internal Operation Alert

PROFILER-2

Explanation Profiler Critical Message

Recommended Action No action is required.

PROFILER-3

Explanation Profiler Message

Recommended Action No action is required.

PROFILER-4

Explanation Profiler Warning Message

Recommended Action No action is required.

PROFILER-5

Explanation Profiler Notification Message

Recommended Action No action is required.

PROFILER-6

Explanation Profiler Informational Message

Recommended Action No action is required.

PROFILER-7

Explanation Profiler Debug Message

Recommended Action No action is required.

PSS Messages

This section contains the PSS messages.

PSS-0

Explanation Service needs more working page buffers

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 PSS cannot read data

Recommended Action No action is required.

Explanation PSS cannot sync data due to filesystem or disk error

Recommended Action No action is required.

Explanation PSS cannot sync log due to filesystem or disk error

Recommended Action No action is required.

Explanation Unknown logging entry found

Recommended Action No action is required.

Explanation PSS cannot write data due to filesystem or disk error

Recommended Action No action is required.

Explanation PSS cannot write data due to filesystem or disk error

Recommended Action No action is required.

Explanation PSS cannot write log due to filesystem or disk error

Recommended Action No action is required.

PSS-1

Explanation PSS found a corrupted database with invalid magic number

Recommended Action No action is required.

Explanation PSS cannot read meta page of a database

Recommended Action No action is required.

Explanation PSS cannot do fstat on a database

Recommended Action No action is required.

Explanation PSS found a database whose format it cannot interpret due to version mismatch

Recommended Action The image upgrade was not done properly; write erase should cure it as a last step

PSS-2

Explanation Error in lib infra convert during pss conversion

Recommended Action No action is required.

Explanation PSS found a database with invalid size - probably due to a crash

Recommended Action No action is required.

Explanation PSS database is incomplete; probably due to a crash

Recommended Action No action is required.

Explanation PSS recovery failed

Recommended Action No action is required.

PSS-4

Explanation PSS removed a leftover or corrupted file

Recommended Action No action is required.

Explanation PSS recovery finished

Recommended Action No action is required.

Explanation PSS started recovery of previous aborted transaction

Recommended Action No action is required.

PSS-5

Explanation PSS format is being converted

Recommended Action No action is required.

Explanation PSS layout is being converted

Recommended Action No action is required.

Explanation PSS is being shrunk to remove free space

Recommended Action No action is required.

Explanation Publisher received SDB commit but sdb was already closed

Recommended Action No action is required.

PTPLC Messages

PTPLC-3

Explanation PTP interface configuration error

Recommended Action No action is required.

Explanation PTP interface configuration error

Recommended Action No action is required.

PTP Messages

This section contains the PTP messages.

PTP-5

Explanation PTP Service Enabled

Recommended Action No action is required.

Explanation PTP domain changed

Recommended Action No action is required.

Explanation PTP Service Enabled

Recommended Action No action is required.

PTP-6

Explanation PTP announce interval for [chars] changed

Recommended Action No action is required.

Explanation PTP announce timeout interval for [chars] changed

Recommended Action No action is required.

Explanation PTP delay-req interval for [chars] changed

Recommended Action No action is required.

Explanation PTP priority1 changed

Recommended Action No action is required.

Explanation PTP priority2 changed

Recommended Action No action is required.

Explanation PTP sync interval for [chars] changed

Recommended Action No action is required.

Explanation PTP vlan for [chars] changed

Recommended Action No action is required.

PULSE Messages

This section contains the PULSE messages.

PULSE-0

Explanation Pulse Emergency Message

Recommended Action Please file the bug for Pulse Library Component through CDETS'

PULSE-1

Explanation Pulse Alert Message

Recommended Action Pulse Internal Operation Alert

PULSE-2

Explanation Pulse Critical Message

Recommended Action No action is required.

PULSE-3

Explanation Pulse Message

Recommended Action No action is required.

PULSE-4

Explanation Pulse Warning Message

Recommended Action No action is required.

PULSE-5

Explanation Pulse Notification Message

Recommended Action No action is required.

PULSE-6

Explanation Pulse Informational Message

Recommended Action No action is required.

PULSE-7

Explanation Pulse Debug Message

Recommended Action No action is required.

QD Messages

This section contains the QD messages.

QD-3

Explanation Cos map update timed out.

Recommended Action No action is required.

QOS Messages

This section contains the QOS messages.

QOS-2

Explanation The QOS Manager process has exited due to [char]. The process has probably been restarted automatically.

Recommended Action No action is required.

Explanation The QOS Manager has encountered an critical error. The description of error is [str.].

Recommended Action No action is required.

Explanation QoS Manager initialization failed. [chars] explains the reason for the failure.

Recommended Action No action is required.

Explanation The QOS 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.

Explanation The QOS Manager encountered error while operating on a persistent storage database.

Recommended Action No action is required.

Explanation The QOS Manager has failed to rotate its current stdout file with filename [str.]. The file size could grow beyond its maximum limit.

Recommended Action No action is required.

QOS-3

Explanation QoS Manager is out of dynamic memory. [chars] specifies the context where the failure occurred.

Recommended Action No action is required.

Explanation QoS Manager encountered a database error. [chars] specifies the context where the failure occurred.

Recommended Action No action is required.

Explanation The QOS Manager has failed to program or erase QoS related ACL when an E-Port came up or went down for interface [str.]. The error code returned by ACL module is [int.].

Recommended Action No action is required.

Explanation QoS Manager failed to get response [chars][hex] specify the context where the failure occurred.

Recommended Action No action is required.

Explanation QoS Manager encountered a general error, one that does not fall in any of the above categories. [chars] describes the error and its context.

Recommended Action No action is required.

Explanation QoS Manager failed to get license.

Recommended Action No action is required.

Explanation QoS Manager encountered an MTS error. [chars] specifies the context where the error occurred.

Recommended Action No action is required.

Explanation QoS Manager encountered a PSS error. [chars] specifies the context where the failure occurred.

Recommended Action No action is required.

Explanation The QOS Manager has detected corruption in one of its persistent information database. The database would be recreated.

Recommended Action No action is required.

Explanation QoS Manager encountered a timeout [chars][hex] specify the context where the failure occurred.

Recommended Action No action is required.

Explanation The QOS Manager has received an unknown message from [dec]].[dec]. This information is for debugging only.

Recommended Action No action is required.

QOS-4

Explanation QoS Manager license is going to expire. [chars] gives the expected time of expiry.

Recommended Action No action is required.

Explanation There was a version mismatch between the QOS Manager and one of its persistent storage databases. The persistent information has been translated to the new format.

Recommended Action No action is required.

QOS-6

Explanation The QOS Manager on the standby supervisor became active and it is ready to serve client requests.

Recommended Action No action is required.

Explanation The QOS Manager became standby from active mode.

Recommended Action No action is required.

Explanation The QoS Manager has disabled marking of time-critical control traffic as high-priority traffic. Priority of such traffic is now not altered by QoS Manager.

Recommended Action No action is required.

Explanation The QoS Manager has enabled marking of time-critical control traffic as high-priority traffic.

Recommended Action No action is required.

Explanation Excessive time taken for a processing event. The description of the event is [str.].

Recommended Action No action is required.

Explanation The QOS Manager has successfully programmed or erased QoS related ACL when an E-Port came up or went down for interface [str.].

Recommended Action No action is required.

Explanation The QOS Manager was unable to send heartbeat to the system manager.

Recommended Action No action is required.

Explanation The QOS Manager has generated an important event. The description of the event is [str.].

Recommended Action No action is required.

Explanation QoS Manager was created successfully and is up and running. This is an informational message.

Recommended Action No action is required.

Explanation QoS Manager is shutting down gracefully. This is an informational message.

Recommended Action No action is required.

Explanation One of the persistent information database of QOS Manager has been recreated.

Recommended Action No action is required.

Explanation One of the persistent information databases of QoS Manager has been intentionally destroyed and would be recreated.

Recommended Action No action is required.

Explanation The QOS Manager is up and ready to accept client requests. The service was initialized in [char] mode.

Recommended Action No action is required.

Explanation The QOS Manager has successfully switched over to the standby supervisor card.

Recommended Action No action is required.

Explanation QoS Manager received an unexpected message.

Recommended Action No action is required.

R2D2_USD Messages

This section contains the R2D2_USD messages.

R2D2_USD-2

Explanation Gross interrupt threshold exceeded for asic instance. So interrupts have been disabled permanently on the MAC asic.

Recommended Action Reload the module or reload the SUP will recover.

R2D2_USD-6

Explanation R2D2 log message

Recommended Action No action is required.

RADIUS Messages

This section contains the RADIUS messages.

RADIUS-2

Explanation ASCII authentication not supported.

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 RADIUS 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.

RADIUS-3

Explanation RADIUS Message

Recommended Action No action is required.

RADIUS-4

Explanation RADIUS Warning

Recommended Action No action is required.

RADIUS-5

Explanation Notifying Radius server monitor status change

Recommended Action No action is required.

Explanation RADIUS Notification

Recommended Action No action is required.

Explanation Notifying Radius server status change

Recommended Action No action is required.

RADIUS-6

Explanation Accounting Message

Recommended Action No action is required.

Explanation RADIUS Message

Recommended Action No action is required.

RDL Messages

This section contains the RDL messages.

RDL-2

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 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.

RDL-3

Explanation RDL memory allocation failed: [chars].

Recommended Action No action is required.

Explanation RDL context error: [chars] [dec].

Recommended Action No action is required.

Explanation RDL syslog errors: [chars].

Recommended Action No action is required.

Explanation RDL exiting on errors: [chars].

Recommended Action No action is required.

Explanation RDL Initialization Failed: [chars] [chars].

Recommended Action No action is required.

Explanation RDL MTS errors: [chars].

Recommended Action No action is required.

RDL-6

Explanation An event happened that affects RDL. [chars] indicates the event

Recommended Action No action is required.

Explanation An error occurred during an RDL PSS operation. [chars] indicates the PSS operation that caused the error

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation RDL Debug logs: [chars] [dec].

Recommended Action No action is required.

Explanation RDL Debug logs: [chars] [dec].

Recommended Action No action is required.

Explanation RDL Debug logs: [chars].

Recommended Action No action is required.

Explanation RDL context error: [chars] [dec].

Recommended Action No action is required.

RES_MGR Messages

This section contains the RES_MGR messages.

RES_MGR-1

Explanation RES_MGR Received HA msg for resource which does not exist Please check standby status and restart standby to recover

Recommended Action No action is required.

RES_MGR-2

Explanation The user should try and release the conflicting resource.

Recommended Action No action is required.

Explanation RES_MGR generic critical condition

Recommended Action No action is required.

Explanation RES_MGR Received HA msg for resource which does not exist Please check standby status and restart standby to recover

Recommended Action No action is required.

RES_MGR-3

ES_MGR-3-RES_MGR_RES_ALREADY_EXCEEDED: The VDC [dec] is currently already using more [chars] resources (total: [dec]) than the desired new maximum limit ([dec])

Explanation A limit-resource command was issued such that a VDC would be a forbidden state if we obeyed, having already allocated more resources than the new maximum limit

Recommended Action No action is required.

Explanation A limit-resource command was issued such that the desired maximum limit was lower than the desired minimum limit

Recommended Action No action is required.

Explanation A limit-resource command was issued such that a desired limit could not be sat is fixed because of static policies

Recommended Action No action is required.

Explanation A limit-resource command was issued such that the desired minimum limit could not be sat is fixed because of static policies

Recommended Action No action is required.

RES_MGR-4

Explanation When startup config was saved, more VDCs were allowed in the system.

Recommended Action No action is required.

Explanation A limit-resource command was issued such that a VDC may not have enough memory for holding the current amount of routing entries when the new limits will be enforced upon switchover

Recommended Action No action is required.

Explanation A copy running-config startup-config command was issued from a local admin resource limits for the specified resource in the specified vdc had to be saved as a side-effect of it

Recommended Action No action is required.

Explanation A copy running-config startup-config command was issued from another VDC resource limits for the specified resource had to be saved as part of it

Recommended Action No action is required.

Explanation A message of unexpected length was received.

Recommended Action No action is required.

Explanation User should delete VLANS in range 4048-4093 and use following command: system vlan 3968 reserve

Recommended Action No action is required.

RES_MGR-5

Explanation RES_MGR Service Disabled

Recommended Action No action is required.

Explanation RES_MGR Service Enabled

Recommended Action No action is required.

RES_MGR-6

Explanation RES_MGR is spotting some issue when VDC got created

Recommended Action No action is required.

RIB Messages

This section contains the RIB messages.

RIB-0

Explanation Rib caused a system failure

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

RIB-1

Explanation Rib caused failures in other services

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 RIB stopped linecard from coming online due to error received from FIB during merge operation

Recommended Action Check RIB error logs to see error received from FIB

RIB-2

Explanation Rib encountered a catastrophic error

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

RIB-3

Explanation Rib encountered an error

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation Fib had exited and may not continue operation

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 Service not responding to rib

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 Rib does not have enough memory to continue proper operation.

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 Rib to fib IPC failure

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation Rib to snmp IPC failure

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

Explanation Lost a rib-fib transaction log due to IPC failure

Recommended Action Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.

RIB-4

Explanation Either rib was not scheduled to run, or rib was busy, and rib did not service the message or timer queue for an extended period.

Recommended Action Please perform debug rib error', then recreate the operation scenario, to find out more details.'

Explanation Rib ignored duplicate response from fib

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 Rib ignored late response from fib

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 Rib ignored pc

Recommended Action Please use PC number < 128 >

Explanation Rib ignored the unexpected condition

Recommended Action Please perform debug rib error, then recreate the operation scenario, to find out more details.

RIB-5

Explanation Rib does not support this operation

Recommended Action Please perform debug rib error, then recreate the operation scenario, to find out more details.

RIB-6

Explanation Rib event occurred

Recommended Action No action is required.

RLIR Messages

This section contains the RLIR messages.

RLIR-2

Explanation DRLIR rejected: [chars] fcid [chars] reason code [dec]

Recommended Action No action is required.

Explanation RLIR FC2 operation failed: [chars] [chars]

Recommended Action No action is required.

Explanation RLIR Init failed: [chars]

Recommended Action No action is required.

Explanation RLIR module detected an unintentional Link Incident

Recommended Action No action is required.

Explanation RLIR Malloc failed: [chars]

Recommended Action No action is required.

Explanation RLIR MTS operation failed: [chars] [chars]

Recommended Action No action is required.

Explanation RLIR PSS operation failed: [chars] [chars]

Recommended Action No action is required.

RLIR-6

Explanation RLIR Syslog info: [chars]

Recommended Action No action is required.

Explanation RLIR Syslog status: [chars] [chars]

Recommended Action No action is required.

RM Messages

This section contains the RM messages.

RM-6

Explanation RMGR daemon informational message

Recommended Action No action is required.

Explanation The RMGR daemon successfully started

Recommended Action No action is required.

RM-SLOT#-2

Explanation Component caused critical error

Recommended Action Restart the linecard

Explanation Component critical error timeout

Recommended Action No action is required.

Explanation Critical Alert

Recommended Action Restart the linecard

Explanation Process failed

Recommended Action No action is required.

Explanation Component critical error timeout

Recommended Action No action is required.

Explanation Component caused critical error

Recommended Action Restart the linecard

RM-SLOT#-4

Explanation Warning

Recommended Action No action is required.

RSCN Messages

This section contains the RSCN messages.

RSCN-2

Explanation RSCN FC2 operation failed: [chars] [chars]

Recommended Action No action is required.

Explanation RSCN Init failed: [chars]

Recommended Action No action is required.

Explanation RSCN Malloc failed: [chars]

Recommended Action No action is required.

Explanation RSCN MTS operation failed: [chars] [chars]

Recommended Action No action is required.

Explanation SCR rejected: [chars] fcid [chars] Reason code [chars] Reason code expl [chars]

Recommended Action No action is required.

RSCN-3

Explanation RSCN PSS operation failed: [chars] [chars]

Recommended Action No action is required.

RSCN-4

Explanation RSCN rejected: [chars] fcid [chars] Reason code [chars] Reason code expl [chars]

Recommended Action No action is required.

Explanation SW-RSCN rejected: [chars] fcid [chars] Reason code [chars] Reason code expl [chars]

Recommended Action No action is required.

RSCN-6

Explanation RSCN Syslog info: [chars]

Recommended Action No action is required.

Explanation RSCN Syslog status: [chars] [chars]

Recommended Action No action is required.