Cisco MDS 9000 Series Switches NX-OS System Messages Reference

F16_CMN_USD Messages

This section contains the F16_CMN_USD messages.

F16_CMN_USD-6

Explanation Debug log message

Recommended Action No action is required.

F16_FWD_USD Messages

This section contains the F16_FWD_USD messages.

F16_FWD_USD-6

Explanation Debug log message

Recommended Action No action is required.

F16_MAC_USD Messages

This section contains the F16_MAC_USD messages.

F16_MAC_USD-3

Explanation Error log message

Recommended Action No action is required.

F16_MAC_USD-6

Explanation Debug log message

Recommended Action No action is required.

F16_QUE_USD Messages

This section contains the F16_QUE_USD messages.

F16_QUE_USD-6

Explanation Debug log message

Recommended Action No action is required.

F16_XBAR_USD Messages

This section contains the F16_XBAR_USD messages.

F16_XBAR_USD-6

Explanation Debug log message

Recommended Action No action is required.

FABRICPATH Messages

FABRICPATH-2

Explanation Interface is disabled due to conflicts

Recommended Action No action is required.

FABRICPATH-4

Explanation Conflict between Remote ES switch-id and non ES switch-id in database

Recommended Action No action is required.

Explanation Invalid ftag is received from remote

Recommended Action No action is required.

Explanation Invalid switch-id is received from remote

Recommended Action No action is required.

Explanation Resource Allocation Manager was not able to recover the local switch-id

FABRICPATH-6

Explanation Resolving Collision for switch-id

Recommended Action No action is required.

Explanation Link bringup temporarily suspended due to conflicts

Recommended Action No action is required.

Explanation Link bringup temporarily suspended due to conflicts

Recommended Action No action is required.

Explanation New Emulated switch-id received

Recommended Action No action is required.

Explanation New switch-id received

Recommended Action No action is required.

Explanation Local switch-id is changed

Recommended Action No action is required.

Explanation Local switch-id collision with other device

Recommended Action No action is required.

Explanation Local switch-id status changed

Recommended Action No action is required.

Explanation Local switch-id status changed

Recommended Action No action is required.

FALCON Messages

This section contains the FALCON messages.

FALCON-SLOT#-2

Explanation Falcon exited

Recommended Action No action is required.

FC-REDIRECT Messages

This section contains the FC-REDIRECT messages.

FC-REDIRECT-2

Explanation FC-Redirect is unable to program ACL entries. ACL module returned an error.

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries. ACL module returned an error.

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries. ACL module returned an error.

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries. ACL module returned an error.

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries. ACL module returned an error. Hitless upgrade for the module rejected. The module will reload now.

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries. ACL module returned an error. Hitless upgrade for the module rejected. The module will reload now.

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries. ACL module returned an error. Hitless upgrade for the module rejected. The module will reload now.

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries. ACL module returned an error. Hitless upgrade for the module rejected. The module will reload now.

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries. The possible cause can be more than the allowed redirect-able targets on the same switch and more than normal Host(s) are zoned with the Storage Port.

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries possible cause can be more than allowed redirect-able targets on the same switch or more ISL sareco - located on a single line card or more than normal Host(s) are zoned with the Storage Port'

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries possible cause can be more than allowed redirect-able targets on the same switch and more than normal Host(s) are zoned with the Storage Port

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries possible cause can be more than allowed redirect-able targets on the same switch and more than normal Host(s) are zoned with the Storage Port

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries. Possible cause can be linecard is being upgraded/rebooted.

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries. Possible cause can be linecard is being upgraded/rebooted.

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries. Possible cause can be linecard is being upgraded/rebooted.

Recommended Action No action is required.

Explanation FC-Redirect is unable to program ACL entries. Possible cause can be linecard is being upgraded/rebooted.

Recommended Action No action is required.

Explanation FC-Redirect Downgrade to versions 3.2 and lower is not supported, if Active Configuration Exist. Hitful Downgrade for the module is rejected. Please use show fc-redirect configs command and remove appropriate configuration from the applications.

Recommended Action No action is required.

Explanation FC-Redirect Downgrade to versions 3.2 and lower is not supported, if Configuration Exist on this switch. Hitful Downgrade for the module is rejected. Before doing a HITFUL downgrade to any version lower than 3.2.1, Please use clear fc-redirect decommission-switch.

Recommended Action No action is required.

Explanation FC-Redirect Downgrade to versions 3.3.1 and lower is not supported, if Version-2 Configuration Exist. Hitfull Downgrade for the module is rejected.

Recommended Action No action is required.

Explanation FC-Redirect Downgrade to NXOS 4.x or lower is not allowed if the following is true: 1) IVR support is enabled IVR is enabled locally or if FCR app has crested some configurations on local switch 2) FCR has some configuration for local FPC devices Hitful Downgrade for the module is rejected.

Recommended Action No action is required.

Explanation FC-Redirect Rejected FLOGI request as it already has the PWWN with a different FCID in its database.

Recommended Action No action is required.

Explanation FC-Redirect Rejected FLOGI request as the port is on a Gen-1 Line Card and is part of IVR flow with FC-Redirect configuration in vsan fcr_cfg_vsan'.'

Recommended Action No action is required.

Explanation FC-Redirect is Configured in Version 2 Mode. A switch with FC-Redirect version 3.2.x in the fabric is NOT supported in this mode. FC-Redirect has locked the Fabric. No more FC-Redirect configuration changes would be allowed till this switch is disconnected.

Recommended Action No action is required.

Explanation FC-Redirect Rejected Device UP request from IVR as it already has the pwwn with a different FCID in its database.

Recommended Action No action is required.

Explanation FC-Redirect service rejected a request to enable support for IVR flows as it received an error when registering with AAM module. FCR config for IVR virtual devices already exists though IVR support is not enabled. This is not supported. Please remove the appropriate FCR application config and retry again.

Recommended Action No action is required.

Explanation FC-Redirect service rejected a request to enable support for IVR flows as it received an error when registering with AAM module.

Recommended Action No action is required.

Explanation FC-Redirect encountered a PCMAP Error (Internal Error) when processing PORT_UP request for the first member in port channel. The PORT_UP request was rejected.

Recommended Action No action is required.

Explanation FC-Redirect requires that targets must be connected to a switch running FC-Redirect. Please Check Config.

Recommended Action No action is required.

Explanation FC-Redirect Rejected Port Bringup request as the port is on a Gen-1 Line Card and the Vsan is used by FC-Redirect/IVR flow FC-Redirect does NOT support Gen-1 Line Cards for IVR virtual devices with FC-Redirect Configuration.

Recommended Action No action is required.

Explanation FC-Redirect did not receive a response from Error_Switch for a CFS broadcast to update all configurations to Version2 mode. Attempt to configure Version2 mode Failed. All FC-Redirect switches are now in Error Mode. Please make sure the fabric is stable and retry the Configuration command: fc-redirect version2 enable.

Recommended Action No action is required.

Explanation FC-Redirect did not receive a response from Error_Switch' for a CFS broadcast to unlock FC-Redirect configurations after converting them to Version 2 mode. Attempt to configure Version 2 mode Failed. All FC-Redirects switches are now in Error Mode. Please make sure the fabric is stable and retry the Configuration command: 'fc-redirectversion2enable'

Recommended Action No action is required.

Explanation FC-Redirect did not receive a response from Error_Switch' for a CFS broadcast to unlock FC-Redirect configurations after disabling Version 2 mode. Attempt to disable Version 2 mode Failed. All FC-Redirects switches are now in Error Mode. Please make sure the fabric is stable and retry the Configuration command: 'no fc-redirectversion2enable'

Recommended Action No action is required.

FC-REDIRECT-3

Explanation FC-Redirect rejected configuration request for IVR Virtual device as the application switch has NXOS lower than 5.x. FC-Redirect requires the following to be configured before FC-Redirect based applications can create configuration for IVR Virtual devices: 1) IVR AAM register be enabled (config command) 2) FC-Redirect ivr-support enable (Config command) 3) All IVR enabled switches and FC-Redirect application switches must be running NXOS version 5.x or higher.

Recommended Action No action is required.

Explanation FC-Redirect rejected configuration request for IVR Virtual device as IVR-Support is disabled. FC-Redirected requires the following to be configured before FC-Redirect based applications can create configuration for IVR Virtual devices: 1) IVR AAM register be enabled (config command) 2) FC-Redirect ivr-support enable (Config command)

Recommended Action No action is required.

Explanation FC-Redirect rejected configuration request for IVR Virtual device as IVR-Support is disabled. FC-Redirected requires the following to be configured before FC-Redirect based applications can create configuration for IVR Virtual devices: 1) IVR AAM register be enabled (config command) 2) FC-Redirect ivr-support enable (Config command) 3) All IVR enabled switches and FC-Redirect application switches must be running NXOS version 5.x or higher.

Recommended Action No action is required.

Explanation The Pre-Check message is currently used when enabling/disabling Version 2 or ivr-support in fc-redirect. An appropriate sys err would be generated for the purpose.

Recommended Action No action is required.

Explanation The pre-check message is currently used when enabling/disabling Version 2 or ivr-support in fc-redirect. An appropriate sys err would be generated for the purpose.

Recommended Action No action is required.

Explanation FC-Redirect Failed to send CFS request.

Recommended Action No action is required.

Explanation FC-Redirect Failed to send CFS response.

Recommended Action No action is required.

Explanation FC-Redirect Failed to send register request to CFS.

Recommended Action No action is required.

Explanation FC-Redirect on 'switch Error_Switch' rejected delete_ config broadcast. Ignore this error if this was caused by 'test fc-redirect config sync-with-fabric' command. If not, FC-Redirect configuration is out of sync across the fabric. Please force 'Error_Switch' to sync with the fabric again using 'test fc-redirect config sync-with-fabric' command

Recommended Action No action is required.

Explanation FC-Redirect on 'switch Error_Switch' rejected delete_ config broadcast. Ignore this error if this was caused by 'test fc-redirect config sync-with-fabric' command. If not, FC-Redirect configuration is out of sync across the fabric. Please force 'Error_Switch' to sync with the fabric again using 'test fc-redirect config sync-with-fabric' command.

Recommended Action No action is required.

Explanation FC-Redirect did not receive a response from 'Error_Switch' for delete_cfg CFS broadcast. FC-Redirect configuration is out of sync across the fabric. Please delete this configuration and retry it.

Recommended Action No action is required.

Explanation FC-Redirect on switch Error_Switch 'rejected Config PRE_CHECK broadcast for new_config as it is in' Error' state. Create Fail over Config request from the application was rejected. Please resolve the conflict that caused the error state and force 'error-switch' to sync with the fabric again using' test fc-redirect config sync-with-fabric' command.

Recommended Action No action is required.

Explanation FC-Redirect on switch Error_Switch' rejected Config pre-check broadcast for Create Config. Create Failover_Config request from application was rejected

Recommended Action No action is required.

Explanation C-Redirect on switch Error_Switch' rejected Config pre-check broadcast for Create Config. Create Failover_Config request from application was rejected

Recommended Action No action is required.

Explanation FC-Redirect rejected configuration request from the Application as default zone entry for the VSAN is configured as PERMIT. FC-Redirect requires that the default zone entry be DENY for all VSANs with FC-Redirect configuration. FC-Redirect will reject all further FC-Redirect configurations in this vsan till default zone entry is set to DENY. Please set default zone entry to DENY.

Recommended Action No action is required.

Explanation FC-Redirect requires the default zone entry be configured as DENY for vsans with devices that have FC-Redirect configurations. But the specified vsan has default entry permit. FC-Redirect rejected new cfg request from app' on the specified switch. Please change the Default zone entry to DENY for the vsan.

Recommended Action No action is required.

Explanation FC-Redirect received a FC2 frame for some unknown WWN, which it is not expecting. FC-Redirect cannot handle this frame and hence dropping it. This is an internal AAM Error and should not have been forwarded to Fc-Redirect.

Recommended Action No action is required.

Explanation IVR is trying to bring up a Virtual device whose PWWN is same as FC-Redirect Virtual Device. This is a mis-configuration.

Recommended Action No action is required.

Explanation IVR is trying to bring up a Virtual device. FC-Redirect already has a configuration for that device - But FC-Redirect IVR-Support is currently disabled. This is a mis-Configuration. FC-Redirect IVR-Support must be enabled before configuring FC-Redirect based applications to use IVR Virtual devices. FC-Redirect rejected IVR device bring-up. Please delete the relevant application configuration before proceeding further.

Recommended Action No action is required.

Explanation IVR is trying to bring up a Virtual device - But the Message has some Sanity Errors. FC-Redirect failed IVR Device Bringup.

Recommended Action No action is required.

Explanation FC-Redirect requires the default zone entry be configured as DENY for VSANs with devices that have FC-Redirect configurations. But the specified vsan has default zone entry configured as permit. FC-Redirect will reject all further FC-Redirect configuration in this vsan till default entry is configured as DENY. Please set default zone entry to DENY.

Recommended Action No action is required.

Explanation CFS failure. FC-Redirect moved peer to Error state

Recommended Action No action is required.

Explanation CFS failure. FC-Redirect moved peer to Error state

Recommended Action No action is required.

Explanation FC-Redirect Encountered an Internal Error.

Recommended Action No action is required.

Explanation The command ‘no fc-redirect ivr-support enable’ Failed. FC-Redirections with 'Error_Switch' rejected pre-check for IVR Support Disable request as it has one of its peer switches ‘peer_in_err_state’ in Error state. Please resolve the conflict that caused the error state and force 'error-switch' to sync with the fabric again using 'test fc-redirect config sync-with-fabric' command.

Recommended Action No action is required.

Explanation The command 'no fc-redirect ivr-support enable' Failed. FC-Redirection switch 'Error_Switch' rejected pre-check for IVR Support Disable request as it has FC-Redirect configuration for IVR Virtual Devices. Please remove the concerned application configuration and retry the command

Recommended Action No action is required.

Explanation The command ‘no fc-redirect ivr-support enable’ Failed. FC-Redirection switch 'Error_Switch' rejected the pre-check request.

Recommended Action No action is required.

Explanation The command ‘no fc-redirect ivr-support enable' Failed. FC-Redirection switch 'Error_Switch' did not respond to pre-check for IVR Support Disable request'

Recommended Action No action is required.

Explanation IVR is trying to bring up a Virtual device in Curr_Vsan for which FC-Redirect configuration exists on this switch. This is a mis-configuration. FC-Redirect does NOT support ports (FX or ISLs) on Gen-1Cards if there is configuration for IVR Virtual Devices. Please shut down the gen-1ports involved in FCR-IVR flows and retry again

Recommended Action No action is required.

Explanation FC-Redirect on switch Error_Switch' rejected modify_config broadcast as it is in 'Error' state.FC-Redirect configuration is out of sync across the fabric. Please resolve the conflict that caused the error state and force' Error_Switch' to sync with the fabric again using' test fc-redirect config sync-with-fabric' command

Recommended Action No action is required.

Explanation FC-Redirect on switch ‘Error_Switch' rejected modify_config broadcast as it is in 'Error' state. FC-Redirect configuration is out of sync across the fabric. Please delete this configuration and retry it.

Recommended Action No action is required.

Explanation FC-Redirect did not receive a response from Error_Switch' for modify_cfg CFS broadcast. FC-Redirect configuration is out of sync across the fabric.Please delete this configuration and retry it.

Recommended Action No action is required.

Explanation FC-Redirect Failed to send MTS response.

Recommended Action No action is required.

Explanation FC-Redirect on switch Error_Switch' rejected new_config broadcast as it is in 'Error' state. FC-Redirect configuration is out of sync across the fabric. Please resolve the conflict that caused the error state and force' error-switch' to sync with the fabric again using 'test fc-redirect config sync-with-fabric' command.

Recommended Action No action is required.

Explanation FC-Redirect on switch Error_Switch' rejected new_config broadcast. FC-Redirect configuration is out of sync across the fabric. Please delete this configuration and retry it.

Recommended Action No action is required.

Explanation FC-Redirect did not receive a response from Error_Switch' for new_cfg CFS broadcast. FC-Redirect configuration is out of sync across the fabric.Please delete this configuration and retry it.

Recommended Action No action is required.

Explanation FC-Redirect on switch Error_Switch' rejected Config PRE_CHECK broadcast for new_config as it is in 'Error' state. NEW_CONFIG request from the application was rejected. Please resolve the conflict that caused the error state and force' error-switch' to sync with the fabric again using 'test fc-redirect config sync-with-fabric' command.

Recommended Action No action is required.

Explanation FC-Redirect on switch Error_Switch' rejected Config pre-check broadcast for Create_Config. Create_config request from application was rejected.

Recommended Action No action is required.

Explanation FC-Redirect did not receive a response from Error_Switch' for Config pre-check CFS broadcast for new config. Create Config request was rejected.

Recommended Action No action is required.

Explanation FC-Redirect on switch 'Error_Switch' rejected replace_vt request as it is in 'Error' state. FC-Redirect configuration is out of sync across the fabric. Please resolve the conflict that caused the error state and force 'Error_Switch' to sync with the fabric again using 'test fc-redirect config sync-with-fabric' command.

Recommended Action No action is required.

Explanation FC-Redirect on switch Error_Switch' rejected CFS Request of type 'req_type'.

Recommended Action No action is required.

Explanation FC-Redirect did not receive a response from Error_Switch' for a CFS broad cast to abort 'fc-redirect version 2 enable' command. Attempt to configure Version 2 mode Failed. Please make sure the fabric is stable and retry the Configuration command: 'fc-redirect version 2 enable'

Recommended Action No action is required.

Explanation FC-Redirect did not receive a response from Error_Switch' for CHG_MODE_LOCKCFS broadcast. Attempt to configure Version 2 mode Failed.

Recommended Action No action is required.

Explanation FC-Redirect did not receive a response from Error_Switch' for a CFS broad cast to check if 'fc-redirect version 2 enable' command can be executed. Attempt to configure Version 2 mode Failed. Please make sure the fabric is stable and retry the Configuration command: 'fc-redirect version 2 enable'

Recommended Action No action is required.

Explanation FC-Redirect did not receive a response from Error_Switch 'for a CFS broadcast to unlock FC-Redirect configurations when aborting the attempt to configure Version 2 Mode. Attempt to configure Version 2 mode Failed. Please make sure the fabric is stable and retry the Configuration command: 'fc-redirect version 2 enable'

Recommended Action No action is required.

Explanation FC-Redirect did not receive a response from Error_Switch' for a CFS broadcast to unlock FC-Redirect configurations when aborting the attempt to configure Version 2 Mode. Attempt to configure Version 2 mode Failed. Please make sure the fabric is stable and retry the Configuration command: 'fc-redirect version 2 enable'

Recommended Action No action is required.

FC-REDIRECT-5

Explanation Redirect Service requested for the Host / Tgt Pair

Recommended Action No action is required.

Explanation FC-Redirect Service has been decommissioned on this Switch.

Recommended Action No action is required.

Explanation Redirect Service removed for the Host / Tgt Pair

Recommended Action No action is required.

Explanation Application has requested this deletion

Recommended Action No action is required.

Explanation FC Redirect Configuration deleted because of the cli command clear fc-redirect config vt<vt-pwwn

Recommended Action No action is required.

Explanation FC Redirect Configuration deleted because FC Redirect on this switch was decommissioned

Recommended Action No action is required.

Explanation FC Redirect Configuration deleted because of request from peer.

Recommended Action No action is required.

Explanation Peer_Switch had deleted the configuration when it lost connectivity with this switch. Configuration on this switch is now deleted when connection was restored and FC Redirect synced with the Peer_Switch.

Recommended Action No action is required.

Explanation FC Redirect Configuration created by a peer deleted because of local application request.

Recommended Action No action is required.

Explanation FC Redirect Configuration deleted as the peer switch that created the configuration has deleted it. This happened when FC Redirect synced with the peer switch.

Recommended Action No action is required.

Explanation Application has not become online within configured timeout value

Recommended Action No action is required.

Explanation Required Vsan for this configuration deleted in this switch

Recommended Action No action is required.

Explanation FC-Redirect informational message.

Recommended Action No action is required.

Explanation Admin has Disabled FC_Redirect support for IVR flows.

Recommended Action No action is required.

Explanation FC-Redirect service rejected a request to disable support for IVR flows

Recommended Action No action is required.

Explanation Admin has enabled FC_Redirect support for IVR flows.

Recommended Action No action is required.

Explanation FC Redirect has received a request from local Application to delete a config created by a remote switch.

Recommended Action No action is required.

Explanation A local Service request FC-Redirect to sync FC-Redirect Configuration with the peer switches.

Recommended Action No action is required.

Explanation test fc-redirect 'config sync-with-fabric' command was issued on this switch.

Recommended Action No action is required.

Explanation FC-Redirect on Peer switch requested FC-Redirect to sync FC-Redirect Configuration with peer switches.

Recommended Action No action is required.

Explanation Configuration created because of Application Request

Recommended Action No action is required.

Explanation Configuration created after Power-Up

Recommended Action No action is required.

Explanation Configuration created after Process Restart

Recommended Action No action is required.

Explanation Configuration created after SUP Switchover

Recommended Action No action is required.

FC-TUNNEL Messages

This section contains the FC-TUNNEL messages.

FC-TUNNEL-3

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

Recommended Action No action is required.

Explanation FCMPLS tunnel invoked IPFC API and received the error code. [chars] describes the API and 0x[hex] specifies the error

Recommended Action No action is required.

Explanation FCMPLS tunnel process unsuccessfully tried to send a MTS message. MTS error number is specified in [dec]

Recommended Action No action is required.

Explanation FCMPLS tunnel invoked FCNS API and received the error code. [chars] describes the API and 0x[hex] specifies the error

Recommended Action No action is required.

Explanation FCMPLS tunnel invoked Port Manager API and received the error code. [chars] describes the API and 0x[hex] specifies the error

Recommended Action No action is required.

Explanation FCMPLS tunnel read the saved configuration and encountered an error while rebuilding the runtime configuration. [chars] describes the configuration which the process tried to restore and 0x[hex] is the system error code

Recommended Action No action is required.

Explanation [chars] specifies the context where the failure occurred and 0x[hex] specifies the error

Recommended Action No action is required.

Explanation FCMPLS tunnel read the saved runtime database and encountered an error while rebuilding the runtime database. [chars] describes the runtime database which the process tried to restore and 0x[hex] is the system error code

Recommended Action No action is required.

Explanation FCMPLS tunnel invoked RIB API and received the error code. [chars] describes the API and 0x[hex] specifies the error

Recommended Action No action is required.

Explanation RSVP-TE protocol error is encountered. [chars] describes the error and its context.

Recommended Action No action is required.

Explanation FCMPLS tunnel process received unexpected MTS event. MTS opcode is specified in [dec]

Recommended Action No action is required.

FC-TUNNEL-5

Explanation The logical fc tunnel interface is down. This may be due to a reconfiguration on the fc tunnel, or issues on the underlying physical interface

Recommended Action If this is not due to a known reconfiguration, you should verify connectivity at the physical port level, and then on then on the fc tunnel interface. Furthermore, verify the physical ports along the fc tunnel path operate in the TE mode

Explanation The fc interface is up

Recommended Action No action is required.

FCC_LC Messages

This section contains the FCC_LC messages.

FCC_LC-2

Explanation FCC_LC has error sending heart beat

Recommended Action No action is required.

Explanation FCC_LC exiting

Recommended Action No action is required.

Explanation FCC_LC has not sent heart beat

Recommended Action No action is required.

Explanation FCC_LC Process is shutting down

Recommended Action No action is required.

Explanation FCC is unable to read and process relevant FCC data

Recommended Action No action is required.

FCC_LC-5

Explanation FCC_LC has received a malformed/unrecognized message

Recommended Action No action is required.

Explanation FCC_LC has been disabled

Recommended Action No action is required.

Explanation FCC_LC has been enabled

Recommended Action No action is required.

Explanation Process started successfully

Recommended Action No action is required.

FCC_LC-6

Explanation FCC_LC is active for packets with priority <= [threshold]

Recommended Action No action is required.

FCC Messages

This section contains the FCC messages.

FCC-2

Explanation FCC Process is shutting down

Recommended Action No action is required.

FCC-5

Explanation FCC has received a malformed/unrecognized message

Recommended Action No action is required.

Explanation FCC has received a Congestion State Change Notification

Recommended Action No action is required.

Explanation FCC has been disabled

Recommended Action No action is required.

Explanation FCC has been enabled

Recommended Action No action is required.

Explanation FCC has received a Rate Limit End Notification

Recommended Action No action is required.

Explanation FCC has received a Rate Limit Start Notification

Recommended Action No action is required.

Explanation Process started successfully

Recommended Action No action is required.

FCC-6

Explanation FCC is active for packets with priority <= [threshold]

Recommended Action No action is required.

FCDDH Messages

This section contains the FCDDH messages.

FCDDH-SLOT#-3

Explanation Errors which cause program to exit occurred

Recommended Action No action is required.

FCDDH-SLOT#-4

Explanation Serious errors which affect all normal operations occurred

Recommended Action No action is required.

FCDDH-SLOT#-5

Explanation Unexpected errors which affect some normal operations occurred

Recommended Action No action is required.

Explanation Major configuration changes

Recommended Action No action is required.

FCDD Messages

This section contains the FCDD messages.

FCDD-SLOT#-3

Explanation Errors which cause program to exit occurred

Recommended Action No action is required.

FCDD-SLOT#-4

Explanation Serious errors which affect all normal operations occurred

Recommended Action No action is required.

FCDD-SLOT#-5

Explanation Illegal event received in Global Configuration FSM

Recommended Action No action is required.

Explanation Major configuration changes

Recommended Action No action is required.

Explanation Illegal event received in Rescan FSM

Recommended Action No action is required.

Explanation Illegal event received in Twilight Zone Remover FSM

Recommended Action No action is required.

Explanation Illegal event received in VSAN Configuration FSM

Recommended Action No action is required.

Explanation Illegal event received in VSAN Normal Operation FSM

Recommended Action No action is required.

FCDD-SLOT#-7

Explanation Unexpected errors which affect some normal operations occurred

Recommended Action No action is required.

FCDOMAIN Messages

This section contains the FCDOMAIN messages.

FCDOMAIN-2

Explanation Conflict detected ([dec]) domain ID [dec] with WWN [chars].

Recommended Action Check which switches have the same WWN and change either one; then change the other domain ID.

Explanation Fcdomain has isolated interface [chars] (reason: [chars].) Perform a show interface. Based on the reason specified, you might have to ensure domains are adequate and unique in the VSAN and perform a disruptive restart [fcdomain restart disruptive vsan <vsan-id>] or to reinitialize the port.

Recommended Action No action is required.

Explanation Fcdomain has not been able to contact the FC2 module.

Recommended Action No action is required.

Explanation The fcdomain has not been able to complete the initialization sequence with the Fibre Channel subsystem. fcdomain depends on resources not available at the moment: the switch might be short in memory or some other component might be unable to provide the necessary information to fcdomain.

Recommended Action No action is required.

Explanation Fcdomain has not been able to set sockopt to the FC2 module.

Recommended Action No action is required.

Explanation The FCID persistent table is full. Perform [show fcdomain fcid persistent vsan <vsan-id>] to view the entries currently in the table. No more entries can be saved as persistent FCIDs across reboots.

Recommended Action Purge stale entries [purge fcdomain fcid] to obtain more free entries OR disable the feature on certain VSANs which are not critical enough [no fcdomain fcid persistent].

Explanation Fcdomain has not been able to contact the Inter Process Communication (IPC) module for its high priority queue.

Recommended Action No action is required.

Explanation The fcdomain has not been able to complete the initialization sequence. fcdomain depends on resources not available at the moment: the switch might be short in memory or some other component might be unable to provide the necessary information to fcdomain.

Recommended Action No action is required.

Explanation Fcdomain has not been able to contact the Inter Process Communication (IPC) module.

Recommended Action No action is required.

Explanation Fcdomain has not been able to register its messages with the Inter Process Communication (IPC) module.

Recommended Action No action is required.

Explanation The fcdomain has not been able to complete the initialization sequence with the IPC (Inter Process Communication) subsystem. fcdomain depends on resources not available at the moment: the switch might be short in memory or some other component might be unable to provide the necessary information to fcdomain.

Recommended Action No action is required.

Explanation It has been detected that the local switch has the same domain ID [dec] and WWN [chars] of another switch.

Recommended Action Check which switches have the same WWN and change either one; then change the other domain ID.

Explanation It has been detected that two switches have the same non-virtual domain ID [dec] and the same WWN [chars].

Recommended Action Check which switches have the same WWN and change either one; then change the other domain ID.

Explanation Fcdomain has not been able to contact the Persistent Storage Service (PSS).

Recommended Action No action is required.

Explanation An invalid request for domain IDs has been rejected by fcdomain.

Recommended Action Perform [show fcdomain vsan <vsan-id>] for all the switches in the affected VSAN; if a switch does not have a valid current domain ID, configure preferred domain ID zero, then perform [fcdomain restart vsan <vsan-id>] in the affected VSAN.

Explanation Fcdomain has not been able to contact the System Manager.

Recommended Action No action is required.

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

Recommended Action No action is required.

FCDOMAIN-3

Explanation A remote switch attempted to locally apply an allowed domains configuration that doesn't include all currently assigned domains or the locally configured domain.

Recommended Action No action is required.

Explanation The remote switch with domain ID [dec] and WWN [chars] refuses to locally apply the proposed allowed domains probably due to incompatibility with its local configured domain or the domain ID list.

Recommended Action Check the configuration on the remote switch, and make sure that the proposed allowed domains include it. Also, make sure that the proposed allowed domains include all the domains in the domain ID list.

Explanation Fcdomain was not able to open a transaction (HA Purposes).

Recommended Action No action is required.

Explanation Fcdomain has not been able to receive a message from the Inter Process Communication (IPC) module.

Recommended Action Please perform fcdomain restart in the affected VSAN (non disruptive).

Explanation Fcdomain has not been able to reply to a request coming from the Inter Process Communication (IPC) module (error [hex]).

Recommended Action Please perform fcdomain restart in the affected VSAN (non disruptive).

Explanation Fcdomain was not able to send a request using the Inter Process Communication module.

Recommended Action Please perform [fcdomain restart vsan <vsan-id>] in the affected VSAN (non disruptive.)

Explanation Fcdomain has not been able to send a message to the Message Transactional Service (MTS).

Recommended Action Please perform [fcdomain restart vsan <vsan-id>] in the affected VSAN (non disruptive).

Explanation Fcdomain has not been able to receive a message from the Inter Process Communication (IPC) module.

Recommended Action Please perform fcdomain restart in the affected VSAN (non disruptive.)

Explanation Reading the last assigned runtime domain IDs from Non Volatile RAM (NVRAM) failed.

Recommended Action Fcdomain is able to continue without access to the Non Volatile RAM (NVRAM.)

Explanation An FC2 response frame (Command Code [hex]) for SWILS [hex] that was intended for interface [chars] has been received on [chars] instead.

Recommended Action Check the configuration of both interfaces on the local switch and the interfaces on the other side of their corresponding links. In particular, check whether they should all belong to the same port-channel.

Explanation Fcdomain feature has not been able to contact the debug service. Any problems occurring in the fcdomain feature will not be logged.

Recommended Action No action is required.

Explanation Fcdomain feature has not been able to contact the debug history service. Any problems occurring in the fcdomain feature will not be logged to this debug history.

Recommended Action No action is required.

Explanation The local VSAN and VSAN [dec] have the same principal switch [chars], hence are connected in the same logical fabric.

Recommended Action No action is required.

FCDOMAIN-4

Explanation When distribution is enabled, it is recommended to modify the allow domain list on the principal switch only.

Recommended Action Abort the current session on the local switch and start a new one on the principal switch.

Explanation A disruptive reconfiguration (RCF phase) of the VSAN has started. This can happen when two or more fabrics merge disruptively, or when the user manually triggers a disruptive reconfiguration of the VSAN.

Recommended Action No action is required.

Explanation Fcdomain received a malformed FC2-SWILS frame.

Recommended Action No action is required.

Explanation Fcdomain has 80% or more of the FCID persistent table full with entries. Perform [show fcdomain fcid persistent vsan <vsan-id>] to view the entries currently in the table.

Recommended Action Purge stale entries [purge fcdomain fcid] to obtain more free entries.

FCDOMAIN-5

Explanation All the currently existing VSANs have the domain ID type configured as preferred. This means that with a low probability the domain ID of the local VSAN might change after a reconfiguration. A reconfiguration can happen when two or more VSANs are merged or a principal link flaps. A principal link is either an upstream or a downstream link.

Recommended Action Type [fcdomain domain <dom-id> static vsan <vsan-id>] to configure as static the domain ID type in an existing VSAN.

Explanation All the currently existing VSANs have the FCID persistent feature disabled.

Recommended Action Type [fcdomain fcid persistent vsan <vsan-id>] to enable FCID persistent in an existing VSAN. Type [fcdomain fcid persistent global-enable] to automatically enable the FCID persistent feature on all newly created VSANs.

Explanation Fcdomain has 50% of the FCID persistent table full with entries. Perform [show fcdomain fcid persistent vsan <vsan-id>] to view the entries currently in the table.

Recommended Action You may want to purge stale entries [purge fcdomain fcid] to obtain more free entries.

Explanation A CFS Data request from the unknown domain [dec] has been received.

Recommended Action No action is required.

Explanation A CFS Lock request from the unknown domain [dec] has been received.

Recommended Action No action is required.

Explanation A CFS Release request from the unknown domain [dec] has been received.

Recommended Action No action is required.

Explanation A CFS request from the unknown domain [dec] has been received.

Recommended Action No action is required.

FCDOMAIN-6

Explanation Build Fabric has been started in this VSAN

Recommended Action No action is required.

Explanation Impossible to free single FCIDs.

Recommended Action No action is required.

Explanation Lock has been implicitly released due to a clear session operation.

Recommended Action No action is required.

Explanation Requested different FCIDs without any freeing in between.

Recommended Action No action is required.

Explanation The local domain ID is invalid.

Recommended Action No action is required.

Explanation The domain ID [dec] is available.

Recommended Action No action is required.

Explanation Because of a link failure the downstream interface has been fast-switched from [dec] to [dec].

Recommended Action No action is required.

Explanation Interface [chars] already created.

Recommended Action No action is required.

Explanation Interface [chars] already down.

Recommended Action No action is required.

Explanation Fcdomain on interface [chars] has received a cleanup request.

Recommended Action No action is required.

Explanation Fcdomain is going to create interface [chars].

Recommended Action No action is required.

Explanation Fcdomain is going to remove interface [chars] from its database.

Recommended Action No action is required.

Explanation A non disruptive reconfiguration (BF phase) of the VSAN has started. This can happen when two or more fabrics merge, or when the user manually triggers a non disruptive reconfiguration of the VSAN.

Recommended Action No action is required.

Explanation Fabric name not available.

Recommended Action No action is required.

Explanation Fabric name [chars] available.

Recommended Action No action is required.

Explanation FCIDs already free.

Recommended Action No action is required.

Explanation FCIDs not stored.

Recommended Action No action is required.

Explanation The FCID persistency feature is enabled, but the domain ID type is configured as preferred. This means that with a low probability the domain ID of the local VSAN might change after a reconfiguration. A reconfiguration can happen when two or more VSANs are merged or a principal link flaps. A principal link is either an upstream or a downstream link. Should the domain ID change, all the FCIDs associated with it would be invalidated.

Recommended Action Type [fcdomain domain <dom-id> static vsan <vsan-id>] to configure as static the domain ID type in an existing VSAN.

Explanation Assigned a sequence of 256 contiguous FCIDs starting from FCID [hex]:[hex]:[hex].

Recommended Action No action is required.

Explanation Freed a sequence of 256 contiguous FCIDs starting from FCID [hex]:[hex]:[hex].

Recommended Action No action is required.

Explanation Assigned single FCID [hex]:[hex]:[hex].

Recommended Action No action is required.

Explanation Freed single FCID [hex]:[hex]:[hex].

Recommended Action No action is required.

Explanation Requested FCIDs with domain field not in expected range.

Recommended Action No action is required.

Explanation Requested FCIDs with domain field different from local domain.

Recommended Action No action is required.

Explanation Requested FCID of type 00.00.YY, but specifying an entire area.

Recommended Action No action is required.

Explanation It has been detected that the local switch has the same WWN [chars] of another switch, and that they have different domain IDs: [dec] (local) and [dec].

Recommended Action Check which switches have the same WWN and change either one.

Explanation The local domain is not available yet.

Recommended Action No action is required.

Explanation No free FCIDs.

Recommended Action No action is required.

Explanation Feature UUID [dec] cannot free FCID [dec]:[dec]:[dec] because it is not its owner (UUID actual owner is [dec]).

Recommended Action No action is required.

Explanation It has been detected an overlap with the virtual IVR domain ID [dec] from across the link during an attempt to merge the local VSAN.

Recommended Action No action is required.

Explanation Fcdomain started a principal switch selection phase to elect a principal switch in this VSAN.

Recommended Action No action is required.

Explanation Reconfigure Fabric has been started in this VSAN

Recommended Action No action is required.

Explanation Requested single FCIDs in area [dec] within the reserved range.

Recommended Action No action is required.

Explanation Requested FCIDs not free.

Recommended Action No action is required.

Explanation Requested reserved FCIDs.

Recommended Action No action is required.

Explanation Requested persistent FCIDs, but there is a mismatch.

Recommended Action No action is required.

Explanation It has been detected that two switches have the same WWN [chars], but different non-virtual domain IDs: [dec] and [dec].

Recommended Action Check which switches have the same WWN and change either one.

Explanation A timer unknown to fcdomain has expired.

Recommended Action No action is required.

Explanation Because of a link failure the upstream interface has been fast-switched from [dec] to [dec].

Recommended Action No action is required.

Explanation No available space to store the identity of the request or the FCIDs.

Recommended Action No action is required.

Explanation Universal Unique ID (UUID) not found.

Recommended Action No action is required.

Explanation It has been detected an overlap with the local virtual IVR domain ID [dec] during an attempt to merge the local VSAN.

Recommended Action No action is required.

FCDOMAIN-7

Explanation Fcdomain was going to isolate interface [chars], but the interface is already isolated.

Recommended Action No action is required.

Explanation A non disruptive reconfiguration (BF phase) completed. This can happen when two or more fabrics merged, or when the user manually triggered a non disruptive reconfiguration of the VSAN.

Recommended Action No action is required.

Explanation A disruptive reconfiguration (RCF phase) of the VSAN has completed. This can happen when two or more fabrics merged disruptively, or when the user manually triggered a disruptive reconfiguration of the VSAN.

Recommended Action No action is required.

Explanation Fcdomain is retrying an FC2 frame on interface [chars] due to loss/no response. The Command Code of the frame is [hex].

Recommended Action No action is required.

Explanation There may be a problem in the sequence that shuts down all interfaces before fcdomain receives a request from FICON Manager to purge the persistent FCID table.

Recommended Action No action is required.

Explanation Fcdomain state machine generated an invalid event on interface [chars], for which no proper action was defined (current state [chars].)

Recommended Action No action is required.

Explanation Fcdomain state machine has tried to execute a forbidden transition.

Recommended Action No action is required.

Explanation Interface [chars] is ready.

Recommended Action No action is required.

Explanation An undefined pre-action type has been used.

Recommended Action No action is required.

Explanation A Principal Switch Selection (PSwS phase) completed.

Recommended Action No action is required.

Explanation Domain ID [dec] has been received by VSAN with WWN [chars] (requested domain ID was [dec].)

Recommended Action No action is required.

FCD Messages

This section contains the FCD messages.

FCD-7

Explanation SB3 aborted exchange due to reason given. Aborts are caused by either the channel or control unit detecting a device protocol error. Recovery actions are performed to restore communication. In certain circumstances aborts occur in normal operations.

Recommended Action No action is required if communication with CUP device is still operational.

Explanation SB3 failed perform file function. Failure is caused by error in the file main frame sent to director.

Recommended Action No action is required if communication with CUP device is still operational.

FCFWD Messages

This section contains the FCFWD messages.

FCFWD-3

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

FCFWD-4

Explanation Fcfwd is generating a relevant notification

Recommended Action No action is required.

FCFWD-6

Explanation An fc fwd event occurred

Recommended Action No action is required.

FCNS Messages

This section contains the FCNS messages.

FCNS-2

Explanation Name server database is full. The max number of entries, [dec], of ports is already present in the database

Recommended Action No action is required.

Explanation Fcns initialisation has failed due to [chars].

Recommended Action No action is required.

Explanation No response for query [chars] from domain [dec].

Recommended Action No action is required.

Explanation Version mismatch for pss of type [chars].

Recommended Action No action is required.

Explanation Failed to reload information from PSS: [chars].

Recommended Action No action is required.

FCNS-3

Explanation Received a bad frame from the network: [chars].

Recommended Action No action is required.

Explanation A failure related to fcns configuration: [chars].

Recommended Action No action is required.

Explanation Chunk memory failure: [chars].

Recommended Action No action is required.

Explanation A failure occurred in fcns database: [chars].

Recommended Action No action is required.

Explanation Malloc failed: [chars].

Recommended Action No action is required.

Explanation Failure occurred trying to do an MTS operation: [chars] [chars].

Recommended Action No action is required.

Explanation Pss failure: [chars].

Recommended Action No action is required.

FCNS-4

Explanation No response for query [chars] from domain [dec].

Recommended Action No action is required.

FCNS-6

Explanation Database modification:[chars] for entry [hex].

Recommended Action No action is required.

Explanation A change in fcns status: [chars].

Recommended Action No action is required.

FCOE_MGR Messages

This section contains the FCOE_MGR messages.

FCOE_MGR-2

Explanation FCOE_MGR Line Card not licensed

Recommended Action No action is required.

Explanation FCOE Manager PSS Restore operation failed

Recommended Action No action is required.

FCOE_MGR-5

Explanation FCOE_MGR Service Disabled

Recommended Action No action is required.

Explanation FCOE_MGR Service enabled

Recommended Action No action is required.

Explanation FCoE Manager general info

Recommended Action No action is required.

Explanation FCOE_MGR Line Card license checked in

Recommended Action No action is required.

Explanation FCOE_MGR Line Card license checked out

Recommended Action No action is required.

Explanation FCoE Manager received Multicast Solicitation from same MAC

Recommended Action No action is required.

Explanation FCoE Manager has already received unicast advertisement from same MAC on a different VE link

Recommended Action No action is required.

FCOE Messages

This section contains the FCOE messages.

FCOE-5

Explanation FCOE Service Disabled

Recommended Action No action is required.

Explanation FCOE Service Enabled

Recommended Action No action is required.

FCSP-MGR Messages

This section contains the FCSP-MGR messages.

FCSP-MGR-2

Explanation The system has detected an error.

Recommended Action No action is required.

Explanation FC-SP Manager has been unable to initialize with the FC-2 E-Port infrastructure.

Recommended Action No action is required.

Explanation FC-SP Manager has been unable to initialize with the FC-2 F-Port infrastructure.

Recommended Action No action is required.

Explanation The system has detected an error.

Recommended Action No action is required.

Explanation Fibre-Channel Authentication failure on Port [chars].(Reason Code [chars] Detail [chars]). Please check password configurations and ensure appropriate security modes on this port as well as peer port

Recommended Action No action is required.

Explanation Fibre-Channel ESP parameters mismatch with the peer on Port [chars].(Reason: [chars]). Please check ESP configurations on both side of the link and ensure appropriate ESP mode on this port as well as peer port

Recommended Action No action is required.

Explanation The system has detected an error.

Recommended Action No action is required.

Explanation FC-SP Manager has been unable to initialize with the IPC infrastructure.

Recommended Action No action is required.

Explanation License of [chars] is unavailable. Service will exit now

Recommended Action Please install the license file to continue using the feature.

Explanation The system has detected an error.

Recommended Action No action is required.

Explanation The system has detected an error.

Recommended Action No action is required.

Explanation The system has detected an error.

Recommended Action No action is required.

FCS Messages

This section contains the FCS messages.

FCS-2

Explanation Memory allocation failed for size [dec].

Recommended Action Restart the process.

Explanation Chunk memory allocation failed. [chars] indicates the chunk name.

Recommended Action Restart the process.

Explanation Maximum number of retires completed for [chars] form domain [dec] in VSAN [dec].

Recommended Action No action is required.

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.

Explanation There was a critical error during random number generation. [chars] indicates details of the error.

Recommended Action No action is required.

FCS-3

Explanation An error occurred during an FCS 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 An error happened during FCS 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 error occurred in send or receive of an MTS message. [chars] indicates the error that occurred and [chars] indicates the error number.

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

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 There was no response to an MTS request. [chars] indicates details of the MTS message.

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

Explanation There was no response to an FC2 request. [chars] indicates FCS request [dec] indicates the remote domain and [dec] the VSAN ID.

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

Explanation An FCS generic error occurred. [chars] indicates the description of the error.

Recommended Action No action is required.

Explanation An error occurred during an FCS 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 An FC-2 Socket error occurred on socket-ID [dec]. [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.

FCS-5

Explanation An API called by FCS failed. [chars] indicates the API name failed and [chars] the reason for failure.

Recommended Action If this message is seen during a cold boot, it means that the queried module came up after FCS and this case can be ignored.

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

Recommended Action No action is required.

FCS-6

Explanation An invalid FCS FC-CT frame with [chars] received from FC-ID [hex].

Recommended Action No action is required.

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

Recommended Action No action is required.

Explanation There was a retransmission of an FC2 request. [chars] indicates FCS request [dec] indicates the remote domain and [dec] the VSAN ID

Recommended Action No action is required.

FDMI Messages

This section contains the FDMI messages.

FDMI-2

Explanation Fdmi process encountered error while starting.

Recommended Action No action is required.

Explanation Fdmi process unsuccessfully tried to send a MTS message. MTS error number is specified in [dec].

Recommended Action No action is required.

Explanation Fdmi read the saved configuration and encountered an error while rebuilding the runtime configuration. [chars] describes the configuration which the process tried to restore and 0x[hex] is the system err code.

Recommended Action No action is required.

Explanation Fdmi read the saved runtime database and encountered an error while rebuilding the runtime database. [chars] describes the runtime database which the process tried to restore and 0x[hex] is the system err code.

Recommended Action No action is required.

FDMI-3

Explanation Fdmi process received malformed frame. [chars] describes the malformation

Recommended Action No action is required.

Explanation Fdmi process received bad payload in response

Recommended Action No action is required.

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

Recommended Action No action is required.

Explanation Fdmi invoked API [chars], received the error code specified in 0x[hex]

Recommended Action No action is required.

Explanation Fdmi received message from module [chars] which contains unknown message format. MTS opcode is specified in [dec]

Recommended Action No action is required.

Explanation Fdmi process sends a inter-switch packets to switches and has not received the response

Recommended Action No action is required.

Explanation [chars] specifies the context where the failure occurred and 0x[hex] specifies the err

Recommended Action No action is required.

Explanation Fdmi process received unexpected MTS event. MTS opcode is specified in [dec]

Recommended Action No action is required.

FDMI-4

Explanation Fdmi process sends a inter-switch packets to switches and has received the reject response with reason code in [chars]

Recommended Action No action is required.

FDMI-6

Explanation Fdmi process debug info

Recommended Action No action is required.

FEATURE-MGR Messages

This section contains the FEATURE-MGR messages.

FEATURE-MGR-2

Explanation AutoCheckpoint with the given name has been created successfully

Recommended Action No action is required.

Explanation License operation was not successful, check license validity for the feature

Recommended Action Please contact FM team

Explanation License operation was not successful, check license validity for the feature

Recommended Action Please contact FM team

Explanation The error seen at FM and service communication

Recommended Action Please contact service owner with given uuid and FM team

Explanation Failed to add confcheck at enabling feature-set

Recommended Action Please contact FM/sysmgr team

Explanation vdc_mgr failed to response the allow request

Recommended Action Please contact FM/vdc_mgr team

Explanation Checkpoint did not response

Recommended Action Please contact FM/vdc_mgr and rollback team

Explanation Some issues while disabling feature-set

Recommended Action Please contact FM/sysmgr team

Explanation Failed to disable feature at disabling feature-set

Recommended Action Please contact FM/sysmgr team

Explanation Failed to disable feature at disabling feature-set

Recommended Action Please contact FM/sysmgr team and the feature owner

Explanation Some issues during install feature-set

Recommended Action Please contact FM/sysmgr team

Explanation Some issues on the lc while disabling feature-set

Recommended Action Please contact FM/sysmgr team

Explanation Some issue on the lc while enabling feature-set

Recommended Action Please contact FM/sysmgr team

Explanation The message seen when an application rejects feature-set disable request

Recommended Action Please contact FM/sysmgr team

Explanation Some issues during enabling feature-set

Recommended Action Please contact FM/sysmgr team

Explanation Some issues while ungraceful disable feature-set

Recommended Action Please contact FM/sysmgr team

Explanation Some issues while ungraceful uninstall feature-set

Recommended Action Please contact FM/sysmgr team

Explanation Some issues while uninstall feature-set

Recommended Action Please contact FM/sysmgr team

Explanation The error seen at FM and VMM interaction

Recommended Action Please contact FM/VMM team

Explanation Feature manager completed

Recommended Action No action is required.

Explanation Feature manager started

Recommended Action No action is required.

Explanation Service tacacs with uuid [dec] [hex] encountered error: [hex] ([chars])

Recommended Action Please contact Service Owner for details.

FEATURE-MGR-6

Explanation AutoCheckpoint creation has been requested and it should be in progress

Recommended Action No action is required.

Explanation AutoCheckpoint with the given name has been created successfully

Recommended Action No action is required.

Explanation Auto-install feature-set fcoe could be done on isola only

Recommended Action Please contact FM team

Explanation Feature set is in enabled state

Recommended Action No action is required.

FEX Messages

This section contains the FEX messages.

FEX-2

Explanation This is reported when FEX does not come online after ISSU once the SUP came online. When ISSU failure occurs, at the end of the “install all”, the installer will analyze different logs and display the relevant information to diagnose the problem.

Recommended Action If the information from the ISSU analyzer needs to be viewed again, the command "show install all failure-reason" can be used. If FEX did not respond after sup came online during upgrade is reported, investigate the reason for FEX not coming online.

Explanation This is reported when system info message is failed to be sent to FEX, the reason being FEX offline.

Recommended Action Investigate the reason for the FEX going offline. Check the output of the cli show interface ethernet x/y, where x/y is the port to which the FEX is connected.

Explanation Indicates FEX coming online.

Recommended Action No action is required as this syslog is just an indication that FEX is coming online.

Explanation This is reported when there is some incompatibility in configuration detected.

Recommended Action Check the configuration and reconfigure the FEX correctly.

Explanation Indicates FEX going offline.

Recommended Action If this syslog is reported because of intentional invocation of any cli that will make the FEX offline, then no action is required. Else Investigate the reason for the FEX going offline. Check the output of the CLI —show interface ethernet x/y, where x/y is the port to which the FEX is connected.

Explanation Indicates FEX coming online.

Recommended Action No action is required as this syslog is just an indication that FEX is coming online.

FEX-4

Explanation This is reported because the scaling limit has reached for configuring Fabric Extenders with total number of Fabric Extender server interfaces on Supervisor i.e. More FEX/FEX ports in the system than recommended by Cisco.

Recommended Action Do not further scale up the Fabric Extenders with total number of Fabric Extender server interfaces on Supervisor.

FEX-5

Explanation FEX Service Disabled

Recommended Action No action is required.

Explanation FEX Service Enabled

Recommended Action No action is required.

Explanation Fex [decimal-digit] changed port status

Recommended Action No action is required.

Explanation Fex pinning information changed

Recommended Action No action is required.

Explanation This is reported when Disabling of FEX fails.

Recommended Action Remove all FEX related interface configurations manually.

FIB Messages

This section contains the FIB messages.

FIB-SLOT#-0

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

FIB-SLOT#-1

Explanation Fib 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 Hardware resources are approaching limit.

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.

FIB-SLOT#-2

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

Explanation FIB had some HA recovery failures for certain prefixes/labels.

Recommended Action No action is required.

Explanation The TCAM device in the L3 forwarding ASIC has reached its system limits.

Recommended Action No action is required.

FIB-SLOT#-3

Explanation Fib 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 The URPF memory in the L3 forwarding ASIC has reached its system limits.

Recommended Action No action is required.

Explanation Failed to program route into the hardware.

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 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 Fib to supervisor 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.

FIB-SLOT#-4

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

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

Explanation Adjacency memory utilization has is above its threshold

Recommended Action No action is required.

Explanation Failed to allocate an adjacency. Adjacency memory could have been exhausted

Recommended Action No action is required.

Explanation The TCAM device in the L3 forwarding ASIC failed to install prefix. Utilization above threshold.

Recommended Action No action is required.

Explanation The TCAM device in the L3 forwarding ASIC failed to install prefix. Utilization below threshold.

Recommended Action No action is required.

Explanation The TCAM device in the L3 forwarding ASIC is within system limits.

Recommended Action No action is required.

Explanation The TCAM device in the L3 forwarding ASIC is reaching its system limits.

Recommended Action No action is required.

Explanation Fib encountered a possible 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.

FIB-SLOT#-6

Explanation Information that a corrective action was taken by FIB

Recommended Action Message is informational only

FICON Messages

This section contains the FICON messages.

FICON-2

Explanation This port has the same port number assigned to other port in the same FICON VSAN. No more than one port with duplicate port number can be up in each FICON VSAN

Recommended Action Avoid duplicate number assignment in each FICON VSAN

Explanation Port number or port address in startup-configure is out of bound.

Recommended Action Change ficon port number assign configuration and save to startup-configure.

Explanation Failed to save file. Possibly due to asymmetric pdcm matrix. Look for ret_val for actual reason.

Recommended Action Configure port prohibits in symmetrically.

Explanation FICON Manager shutting down

Recommended Action This is a severe error. Provide the reason given in the message.

FICON-3

Explanation Port number has fcip or port channel binding can not be removed nor changed.

Recommended Action Remove port number binding of the logical interface first.

Explanation Invalid port number parameters in command.

Recommended Action Check port numbers in the command.\n

Explanation Port number assigned to physical and logical can not overlap.

Recommended Action Check port numbers in the command.\n

Explanation Only port number assigned to a port in down state can be removed or changed.

Recommended Action Bring down the port first.\n

Explanation Logical port address can not be prohibited.

Recommended Action Check port numbers in the command.\n

Explanation This port has the same port number assigned to other port in the same FICON VSAN. No more than one port should have the same port number in each FICON VSAN

Recommended Action Avoid duplicate number assignment in each FICON VSAN

Explanation This port either has an invalid port address assigned or has no port address assigned.

Recommended Action Assign a valid ficon port number to the port.\n

Explanation This port has been prohibited. Prohibiting E or TE ports is not allowed. This port can not be configured in E mode or TE mode until the prohibit mask configuration is changed

Recommended Action Correct the prohibit mask (PDCM) for this port if you wish to bring it up as an E or TE port in a FICON VSAN

Explanation Only port number already assigned can be removed.

Recommended Action Check port numbers in the command.

Explanation The FICON Prohibit Dynamic Connectivity Mask(PDCM) change rejected because an E or TE port is being prohibited. Prohibiting an E or TE port in not allowed.

Recommended Action Correct the prohibit mask (PDCM) for this port if you wish to bring the port up as an E or TE port in a FICON VSAN.

FICON-5

Explanation FICON Manager process is being started

Recommended Action No action is required.

FICON-6

Explanation The FICON Prohibit Dynamic Connectivity Mask (PDCM) for this port has changed. VSAN [dec], port address [dec] prohibit mask (PDCM) is now set to [chars]

Recommended Action No action is required.

Explanation FICON port numbers swapped

Recommended Action No action is required.

Explanation FICON has been disabled on the given VSAN

Recommended Action No action is required.

Explanation FICON has been enabled on the given VSAN

Recommended Action No action is required.

FIPSM Messages

This section contains the FIPSM messages.

FIPSM-5

Explanation SPLITTER Service Disabled

Recommended Action No action is required.

Explanation SPLITTER Service enabled

Recommended Action No action is required.

FIPS Messages

This section contains the FIPS messages.

FIPS-0

Explanation FIPS cleanup failed [chars]

Recommended Action No action is required.

Explanation FIPS mode failed [chars]

Recommended Action No action is required.

FIPS-6

Explanation FIPS mode is changed [chars] [chars]

Recommended Action No action is required.

FLN_EM Messages

This section contains the FLN_EM messages.

FLN_EM-6

Explanation Debug log message

Recommended Action No action is required.

FLN_FCP Messages

This section contains the FLN_FCP messages.

FLN_FCP-6

Explanation Debug log message

Recommended Action No action is required.

FLN_FCP-SLOT#-2

Explanation The TCAM device in the L3 forwarding ASIC has reached its system limits.

Recommended Action No action is required.

FLN_FCP-SLOT#-3

Explanation The URPF memory in the L3 forwarding ASIC has reached its system limits.

Recommended Action No action is required.

FLN_FCP-SLOT#-4

Explanation Failed to allocate an adjacency. Adjacency memory could have been exhausted

Recommended Action No action is required.

Explanation Failed to allocate a ls-met entry. LS-MET table region for this entry could have been exhausted

Recommended Action No action is required.

Explanation Failed to allocate a multicast met entry. Met table region for this entry could have been exhausted

Recommended Action No action is required.

Explanation L3 oiflist insertion failed because Max supported l3 oiflist size is 4k

Recommended Action No action is required.

Explanation Failed to allocate a MDT entry. MDT table region for this entry could have been exhausted

Recommended Action No action is required.

Explanation The TCAM device in the L3 forwarding ASIC failed to install prefix. Utilization above threshold.

Recommended Action No action is required.

Explanation The TCAM device in the L3 forwarding ASIC failed to install prefix. Utilization below threshold.

Recommended Action No action is required.

Explanation The TCAM device in the L3 forwarding ASIC is within system limits.

Recommended Action No action is required.

Explanation The TCAM device in the L3 forwarding ASIC is reaching its system limits.

Recommended Action No action is required.

FLN_FWD_USD Messages

This section contains the FLN_FWD_USD messages.

FLN_FWD_USD-2

Explanation Critical log message

Recommended Action No action is required.

FLN_FWD_USD-6

Explanation Debug log message

Recommended Action No action is required.

FLN_L3 Messages

This section contains the FLN_L3 messages.

FLN_L3-6

Explanation Debug log message

Recommended Action No action is required.

FLN_QUE Messages

This section contains the FLN_QUE messages.

FLN_QUE-6

Explanation Debug log message

Recommended Action No action is required.

FLN_XBAR Messages

This section contains the FLN_XBAR messages.

FLN_XBAR-2

Explanation Flanker received packets with CRC error from fabric

Recommended Action No action is required.

FLN_XBAR-6

Explanation Debug log message

Recommended Action No action is required.

FLOGI Messages

This section contains the FLOGI messages.

FLOGI-1

Explanation An FDISC was rejected because the F-Port has reached the maximum allowed number of devices.

Recommended Action Check the configuration of the NPIV device connected to the port.

Explanation An FLOGI was rejected because the FL-Port has reached the maximum allowed number of devices.

Recommended Action Reduce the number of devices on the loop.

Explanation The N_Port requested NPIV, but this platform does not support NPIV on trunking F_Ports.

Recommended Action Disable NPIV, or move the N_Port to a switch that supports NPIV on trunking F_Ports

FLOGI-2

Explanation An FLOGI was rejected because the ACLTCAM hardware resource is completely used.

Recommended Action Reduce the number of nodes.

Explanation The number of FLOGI logins on an interface has reached or exceeded the specified limit.

Recommended Action Reduce or redirect the FLOGIs.

Explanation The number of FLOGI logins on a director-class module has reached or exceeded the specified limit.

Recommended Action Reduce or redirect the FLOGIs.

Explanation The number of FLOGI logins on a switch has reached or exceeded the specified limit.

Recommended Action Reduce or redirect the FLOGIs.

FLOGI-4

Explanation This interface received an FLOGI with VF bit set from a non CISCO OUI; in this release Virtual Fabrics are not supported on interfaces connected to third-party devices

Recommended Action Set the trunk mode of this interface to off

FLOGI-5

Explanation The switch received an FLOGI from a trunking interface on a VSAN which has been suspended; the FLOGI frame has been dropped.

Recommended Action To bring up the VSAN again on the trunking port, remove it from the allowed VSAN list and add it again

Explanation The switch received an FLOGI from the interface, which has a duplicate PWWN value.

Recommended Action No action is required.

Explanation The FL/TL interface is re-initialized as ALPA used by device conflicts with an existing FLOGI session after the Loop Initialization Protocol (LIP). All the devices will re-login with new ALPA and PWWN mapping

Recommended Action No action is required.

Explanation Nx port logged in with the specified information.

Recommended Action No action is required.

Explanation Nx port logged out. The following commands will help determine why this Nx port logged out: 'show interface, show VSAN, show module'

Recommended Action No action is required.

FLOGI_REJECTED_DUPLICATE_PWWN_IN_FABRIC

Explanation The switch received an FLOGI/FDISC which has a PWWN value that is already logged in the fabric.

Recommended Action Run the show fcns database detail vsan vsan_id command to determine where the device is already logged into the fabric. Retry the FLOGI/FDISC after the device logs out of the fabric.

FLOGI_REJECTED_DUE_TO_SERVICE_TIMEOUT

Explanation The switch received an FLOGI/FDISC which could not be processed in time because system was busy.

Recommended Action Retry the FLOGI/FDISC after the system load has reduced.

FLOGI_REJECTED_DUPLICATE_PWWN_ON_SWITCH

Explanation The switch received an FLOGI/FDISC from a device which had already logged in to this switch on a different interface.

Recommended Action The device is implicitly logged out and the FLOGI_IMPLICIT_DEVICE_LOGOUT syslog message is generated. If the device retries to log in, the FLOGI/FDISC should succeed.

FLOGI_IMPLICIT_DEVICE_LOGOUT

Explanation The switch implicitly logged out a device because it tried to login on a different interface without logging out first.

Recommended Action Retry the FLOGI/FDISC. This syslog message is generated along with the FLOGI_REJECTED_DUPLICATE_PWWN_ON_SWITCH syslog message.

FLOGI_ON_FPORT_CHANNEL_MEMBER

Explanation The FLOGI request has been dropped because it was received on an fport-channel member interface when the f-port channel is already up. Only one FLOGI is allowed on an f-port channel from the first member.

Recommended Action Remove the member from the port-channel on the local switch or add the member to the port-channel on the remote switch.

FS-DAEMON Messages

This section contains the FS-DAEMON messages.

FS-DAEMON-2

Explanation Move system images from RAM to bootflash to free up some memory

Recommended Action Please remove some unnecessary files on bootflash using delete command and copy images from active supervisor or from remote location.

FS-DAEMON-6

Explanation System logflash space is almost full

Recommended Action Use 'clear core archived' or 'delete' CLI to free up space on logflash.

Explanation System root space is almost full

Recommended Action Use 'clear core archived' or 'delete' CLI to free up space on root dir or /var/log

Explanation System /tmp space usage.

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 Exported NFS mounts are not visible in kernel and had to be reexported

Recommended Action Please use 'show system internal flash' to make sure there are no Stale NFS handles'

FSCM Messages

This section contains the FSCM messages.

FSCM-2

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

FSPF Messages

This section contains the FSPF messages.

FSPF-2

Explanation FSPF routing daemon is shutting down because of [chars] reason.

Recommended Action This is a severe bug. Provide the reason provided and the log files for FSPF.

FSPF-2

Explanation FSPF received a bad FC2 packet on [chars] interface, error description is [chars].

Recommended Action FSPF daemon has received a bad FC frame. Provide the output of 'debug fc2 pkt '.

Explanation Periodic database checksum test failed for LSR for domain [dec]

Recommended Action This indicates that the internal database got corrupted because of some memory corruption bug. Provide output of 'show fspf database'. May need to power cycle the switch

Explanation An error occurred in processing a [chars] FC2 packet on [chars] interface. The internal error code is [chars].

Recommended Action Turn on 'debug fspf error' to get more information. Make sure there is no misconfiguration of FSPF parameters on the two ends of the interface. Provide output of 'show fspf vsan x' 'show fspf vsan x interface' and 'debug fspf fc pkt ' for the specific interface

Explanation FSPF had an error in flooding the local LSR, error description is [chars].

Recommended Action Provide output of 'debug fspf flood', 'debug fspf error'. If error is reported in transmitting packet check if interface is up and turn on 'debug fc2 error'

Explanation There is a mismatch in the [chars] entry in the hello packet received on interface [chars]. The packet will be dropped.

Recommended Action Check the configuration of hello or dead interval on the switches on the two ends of the interface to see if there is a mismatch.

Explanation FSPF had an error in processing timer event for interface chars, error is [chars].

Recommended Action Provide output of 'debug fspf error'

Explanation FSPF had an error in processing message of [dec] opcode, the internal error code is [dec].

Recommended Action Possibly some wrong IPC message is received by FSPF. Provide output of 'debug fspf mts pkt' and 'debug fspf error ' trace.

Explanation There is a software failure in gaining lock of the shared resource between FSPF threads.

Recommended Action Provide output of 'debug fspf all '

Explanation FSPF in standby received an MTS message of opcode [dec] before receiving the GSYNC message.

Recommended Action Provide output of 'debug fspf mts pkt '

Explanation FSPF had an error in interacting with RIB, error description is [chars].

Recommended Action Check if rib application is running using 'show processes'. Provide output of 'debug fspf route' and RIB debug traces.

Explanation FSPF had an error in computing routes, error description is [chars].

Recommended Action Provide the error code and output of 'debug fspf error' and 'debug fspf route' if problem is reproducible

Explanation There is a software failure in releasing lock of the shared resource between FSPF threads.

Recommended Action Provide output of 'debug fspf all '

Explanation FSPF had an internal error in processing timer event, error description is [chars].

Recommended Action Provide output of 'debug fspf error'

FSPF-4

Explanation FSPF received a FC2 packet on inactive interface [chars].

Recommended Action This message may be printed for the first FSPF packet when an interface is brought up. If the message is seen continuously check if FSPF is disabled on one end for the interface or the VSAN. Otherwise check 'show interface ' output to see if interface is physically up only on one side. Also check if there is any Message printed for IPC_PROC_ERR

Explanation FSPF received a FC2 packet on inactive vsan.

Recommended Action If message seen continuously check if FSPF is disabled on the VSAN Investigate if VSAN is active and valid domain has been assigned on the switch Also check if IPC_PROC_ERR message is printed in the syslog

Explanation An illegal protocol event has occurred for the FSPF state machine. The old state was [chars] for the interface [chars].

Recommended Action It is possible to get this message if some protocol packet gets dropped but the it should recover and move back to FULL state. Do 'show fspf interface' to check the state of the interface. If it is stuck in state other than FULL provide output of 'debug fspf event' and 'debug fspf fc pkt ' for the interfaces involved.

Explanation A LSR packet is dropped due to [chars] reason. LSR belonged to domain [dec] and was received on interface [chars].

Recommended Action Provide the reason given for dropping the LSR and output of 'debug fspf fc pkt' If the reason is checksum failure investigate possible packet corruption or truncation

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

Recommended Action This can occur in transient situation and protocol recovers by retransmitting the LSR. If the message is seen continuously provide output of 'debug fspf flood ', 'debug fspf retrans' and 'debug fspf error '. The message may be seen more often when inter operating with other vendors

Explanation A LSU packet is dropped as interface [char] is in INIT state when it received the LSU.

Recommended Action This can occur in some transient situation. If the problem persists provide output of 'show fspf vsan x interface' and 'debug fspf fc pkt ' and 'debug fspf event vsan x'

FSPF-5

Explanation FSPF routing daemon has been started.

Recommended Action No action is required.

FSPF-6

Explanation A new LSR is added to the database for domain [dec].

Recommended Action No action is required.

Explanation The LSR for domain [dec] is deleted from the database.

Recommended Action No action is required.

Explanation FSPF has become operationally down on interface [chars].

Recommended Action No action is required.

Explanation FSPF has become operational on interface [chars].

Recommended Action No action is required.

Explanation The LSR for domain [dec] reached the maximum age and will be deleted from all the connected switches.

Recommended Action No action is required.

Explanation The incarnation number of local LSR reached the maximum value and is rolling over.

Recommended Action No action is required.

Explanation A LSR for the local domain was received with incarnation number higher than the one in database. This situation should only occur initially on a topology change. If this situation persists the domain assignment of switches may not be unique

Recommended Action If this message is received continuously check if domain assignment is unique in the fabric.

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

Recommended Action No action is required.

Explanation FSPF has become operationally down on VSAN.

Recommended Action No action is required.

Explanation FSPF has started with local domain [dec].

Recommended Action No action is required.

FSPF-7

Explanation Route computation thread number [dec] has been started for FSPF.

Recommended Action No action is required.

FVP Messages

This section contains the FVP messages.

FVP-2

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

Recommended Action No action is required.

Explanation The FVP 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 This FVP Manager detected a discrepancy between the information on the chassis and that in its persistent information databases. The persistent information database has been updated with the information on the chassis.

Recommended Action No action is required.

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

Recommended Action No action is required.

FVP-3

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

Recommended Action No action is required.

Explanation Could not send PSS Sync. notification to Standby Supervisor. PSS Type=[str.] Operation=[.str] Key=[Str.]

Recommended Action No action is required.

Explanation A client of FVP Manager attempted to remove a FVP [char] which is not present. This information is for debugging only.

Recommended Action No action is required.

Explanation FVP Manager received a request to release a FVP [char] that could not have been allocated by this FVP Manager.

Recommended Action No action is required.

Explanation FVP Manager received a request to remove a FVP that cannot be removed.

Recommended Action No action is required.

Explanation The FVP Manager received a request to allocate [dec] more than the maximum number of FVPs that can be allocated/released in a single request.

Recommended Action No action is required.

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

Recommended Action No action is required.

FVP-4

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

Recommended Action No action is required.

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

Recommended Action No action is required.

FVP-6

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

Recommended Action No action is required.

Explanation The FVP Manager became standby from active mode.

Recommended Action No action is required.

Explanation The FVP Manager has created a new fv port with ifIndex= [dec].

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 FVP Manager was unable to send heartbeat to the system manger

Recommended Action No action is required.

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

Recommended Action No action is required.

Explanation One of the persistent information database OS FVP Manager has been recreated

Recommended Action No action is required.

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

Recommended Action No action is required.

Explanation The FVP Manager has removed an FV port with ifIndex= [dec].

Recommended Action No action is required.

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

Recommended Action No action is required.

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

Recommended Action No action is required.

FW_APP Messages

This section contains the FW_APP messages.

FW_APP-2

Explanation Firmware extraction error

Recommended Action Please examine show system internal firmware boot-log''

Explanation FW_APP process has failed initialization.

Recommended Action Please examine show system internal firmware event-history errors''

FW_APP-6

Explanation Firmware extraction success

Recommended Action No action is required.

Recommended Action

GLBP Messages

This section contains the GLBP messages.

GLBP-2

Explanation Unicast routing initialization failed and the GLBP process terminated

Recommended Action Please check syslog messages for URIB failures and rectify the problem

GLBP-3

Explanation The system was unable to add the GLBP vIP into the ARP table

Recommended Action Please check syslog messages for ARP failures and rectify the problem

Explanation The system was unable to delete the GLBP vIP from the arp table

Recommended Action Please check syslog messages for ARP failures and rectify the problem

Explanation There was a problem in GLBP interaction with feature manager.

Recommended Action Please check the reason for error using feature manager and rectify the problem

Explanation The system was unable to perform a join to start receiving GLBP protocol packets.

Recommended Action Please check syslog messages for IP failures and rectify the problem

Explanation The system was unable to perform a leave to stop receiving GLBP protocol packets.

Recommended Action Please check syslog messages for IP failures and rectify the problem

Explanation The system was unable to add the GLBP mac address into the mac address table

Recommended Action Please check syslog messages for L2FM failures and rectify the problem

Explanation The system was unable to delete the GLBP mac address from the mac address table

Recommended Action Please check syslog messages for L2FM failures and rectify the problem

Explanation The system was unable to add the GLBP vIP address into the unicast routing table

Recommended Action Please check syslog messages for URIB failures and rectify the problem

Explanation The system was unable to delete the GLBP vIP address from the unicast routing table

Recommended Action Please check syslog messages for URIB failures and rectify the problem

GLBP-4

Explanation Two routers participating in a Gateway Load Balancing Protocol group have a valid authentication string that does not match.

Recommended Action Use the GLBP authentication interface command to repair the Gateway Load Balancing Protocol authentication discrepancy between the local system and the one whose IP address is reported

Explanation The Gateway Load Balancing Protocol virtual IP address is not within the subnet configured on this interface.

Recommended Action Configure the virtual IP address of Gateway Load Balancing Protocol to be within the subnet configured on this interface.

Explanation The Gateway Load Balancing Protocol virtual IP address contained in the hello message cannot be learned. It is not within the subnet configured on this interface.

Recommended Action Check the configuration on all Gateway Load Balancing Protocol routers.

Explanation The Gateway Load Balancing Protocol virtual IP address is a broadcast address for this interface.

Recommended Action Configure the virtual IP address of Gateway Load Balancing Protocol to be a non broadcast address.

Explanation The Gateway Load Balancing Protocol virtual IP address contained in the Hello message from the Active router is different to that configured locally.

Recommended Action Check the configuration on all Gateway Load Balancing Protocol routers

Explanation The IP address in a Gateway Load Balancing Protocol message received on the interface is the same as the IP address of its own router. This condition may be caused by a misconfiguration or because of a malfunctioning switch.

Recommended Action Check the configurations on all the Gateway Load Balancing Protocol routers, and ensure that any switches are functioning properly

Explanation The Gateway Load Balancing Protocol virtual IP address contained in the hello message cannot be learned. It is already assigned to a different Gateway Load Balancing Protocol group.

Recommended Action Check the configuration on all Gateway Load Balancing Protocol routers

Explanation The Gateway Load Balancing Protocol virtual IP address contained in the hello message cannot be learned. It is already assigned to this interface.

Recommended Action Check the configuration on all Gateway Load Balancing Protocol routers.

Explanation The Gateway Load Balancing Protocol virtual IP address contained in the hello message cannot be learned. It is already assigned to, or overlaps with, an address on another interface or application.

Recommended Action Check the configuration on all Gateway Load Balancing Protocol routers.

Explanation The system was unable to send the ARP response for vIP

Recommended Action Please check syslog messages for ARP failures and rectify the problem

GLBP-5

Explanation The Gateway Load Balancing Protocol has changed active gateway.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol forwarder has changed state.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol forwarder has been created.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol forwarder has been removed.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol forwarder has changed the owner MAC address.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol forwarder has changed the virtual MAC address.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol forwarder has changed the weighting.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol gateway has changed state.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol gateway has added a member.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol gateway has removed a member.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol gateway has changed priority.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol has changed standby gateway.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol gateway has learnt timers.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol gateway has learnt virtual IP address.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol gateway has unlearnt virtual IP address.

Recommended Action No action is required

Explanation The Gateway Load Balancing Protocol gateway has changed the weighting.

Recommended Action No action is required

HSRP_ENGINE Messages

This section contains the HSRP_ENGINE messages.

HSRP_ENGINE-3

Explanation Refer logs for more details

Recommended Action No action is required.

Explanation Refer logs for more details.

Recommended Action No action is required.

Explanation Refer logs for more details.

Recommended Action No action is required.

Explanation Refer logs for more details.

Recommended Action No action is required.

Explanation Refer logs for more details.

Recommended Action No action is required.

Explanation Refer logs for more details.

Recommended Action No action is required.

Explanation Refer logs for more details.

Recommended Action No action is required.

Explanation The system was unable to initialize an IP connection for the Hot Standby protocol.

Recommended Action Make sure that there is at least one interface configured to run IP.

HSRP_ENGINE-4

Explanation Two routers participating in HSRP disagree on the valid authentication string.

Recommended Action Use the HSRP authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported.

Explanation Two routers participating in HSRP disagree on the valid authentication string.

Recommended Action Use the HSRP authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported.

Explanation The HSRP virtual IP address contained in the Hello message from the Active router is different to that configured locally.

Recommended Action Check the configuration on all HSRP routers.

Explanation The IP address in an HSRP message received on the interface is the same as the routers own IP address. This may be because of misconfiguration, or because of a malfunctioning switch'

Recommended Action Check the configurations on all the HSRP routers, and make sure that any switches you have are functioning properly.

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

Recommended Action Check the configuration on all HSRP routers.

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

Recommended Action Check the configuration on all HSRP routers.

Explanation The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to, or overlaps with, an address on another interface or application.

Recommended Action Check the configuration on all HSRP routers.

HSRP_ENGINE-5

Explanation The priority of the Active router for the group has changed.

Recommended Action No action is required.

Explanation The Active router for the group has changed.

Recommended Action No action is required.

Explanation The local router has generate virtual ip address

Recommended Action No action is required.

Explanation The HSRP router has changed state

Recommended Action No action is required.

Explanation The mac address of the group has changed.

Recommended Action No action is required.

Explanation The current priority of the HSRP group has changed.

Recommended Action No action is required.

Explanation The priority of the Standby router for the group has changed.

Recommended Action No action is required.

Explanation The Standby router for the group has changed.

Recommended Action No action is required.

Explanation The hello/hold timer value for the HSRP group has changed

Recommended Action No action is required.

Explanation The local router has learnt virtual ip address from the incoming HSRP packet.

Recommended Action No action is required.

HSRP_ENGINE-6

Explanation The router has changed state

Recommended Action No action is required.

Explanation The router has changed state

Recommended Action No action is required.

IDEHSD Messages

This section contains the IDEHSD messages.

IDEHSD-1

Explanation Logflash is not accessible; use format logflash: to format it

Recommended Action No action is required.

IDEHSD-2

Explanation Logflash auto-format event

Recommended Action No action is required.

Explanation The specified disk interface is in use. It can not be unmounted, The user may experience file system corruption

Recommended Action Make sure slot0 is not being used either by mounting or by any command and re-insert the disk again

Explanation Flash file system may be corrupted, the flash was taken while it was being accessed

Recommended Action Reform at the external flash

Explanation Unknown flash filesystem or not cleanly unmounted.

Recommended Action Use vfat flash only and make sure external slot is not being accessed then re-insert flash

Explanation Flash filesystem was not cleanly unmounted

Recommended Action Make sure external slot is not being accessed and re-inset the flash

Explanation Flash filesystem is busy the system could not unmount it

Recommended Action Make sure external slot is not being accessed and re-inset the flash

Explanation The flash daemon failed to fork

Recommended Action No action is required.

Explanation The flash daemon interface returns error

Recommended Action Restart the IDEHSD deamon

Explanation Flash daemon mounting slot

Recommended Action No action is required.

Explanation Flash daemon un-mounting slot

Recommended Action No action is required.

Explanation USB swap event

Recommended Action No action is required.

IDEHSD-3

Explanation The flash daemon device open failed The failure is due to the sub-component [chars]

Recommended Action No action is required.

IDEHSD-5

Explanation Compact flash swap event

Recommended Action No action is required.

IDEHSD-6

Explanation Flash daemon trying to unmount busy slot

Recommended Action No action is required.

Explanation Flash daemon found a disk hot swap handler event

Recommended Action No action is required.

Explanation Flash daemon informational message

Recommended Action No action is required.

Explanation Flash daemon trying to unmount busy slot

Recommended Action No action is required.

Explanation The compact flash swap daemon successfully started

Recommended Action No action is required.

IDEHSD-7

Explanation Flash daemon debug message to trace code path

Recommended Action No action is required.

IFTMC Messages

This section contains the IFTMC messages.

IFTMC-SLOT#-1

Explanation [chars]

Recommended Action No action is required.

IFTMC-SLOT#-2

Explanation IFTMC hit a internal error. Collect show tech-support eltm for further analysis.

Recommended Action No action is required.

Explanation IFTMC hit a internal error. Collect show tech-support eltm for further analysis.

Recommended Action No action is required.

Explanation IFTMC database doesn’t have the interface.

Recommended Action No action is required.

Explanation IFTMC does not support the interface for the specified operation

Recommended Action No action is required.

Explanation IFTMC Failed to get LTL for interface. Packets received on this interface might not be handled correctly by the forwarding engine

Recommended Action No action is required.

Explanation IFTMC Failed to get Slot for interface. Port-channels and L2 Learning might be effected

Recommended Action No action is required.

Explanation IFTMC Failed: Received INVALID Ftags

Recommended Action No action is required.

Explanation IFTMC Failed to allocate L2 LIF entries in forwarding engine. This will effect Layer 2 and Layer 3 forwarding for the interface

Recommended Action No action is required.

Explanation IFTMC Failed to allocate L2 LIF entries in forwarding engine. This will effect Layer 2 and Layer 3 forwarding in this VDC

Recommended Action No action is required.

Explanation IFTMC Failed to allocate L3 Ingress LIF entries in forwarding engine. This will effect Layer 3 forwarding for the interface

Recommended Action No action is required.

Explanation IFTMC Failed to get the reserved vlans. This will effect multicast forwarding on SVI interfaces.

Recommended Action No action is required.

Explanation IFTMC hit a internal error. Collect show tech-support eltm for further analysis.

Recommended Action No action is required.

Explanation IFTMC BD is zero, SVI create before vlan create

Recommended Action No action is required.

Explanation FCOE feature request cannot be processed with ILM sharing, failure status does not get returned to calling app. Possible ACLQOS verify/commit fail prior to this feature request.

Recommended Action No action is required.

Explanation IFTM Failed to apply ftag list on an interface

Recommended Action No action is required.

Explanation IFTM Failed to apply vlan translation table on an interface

Recommended Action No action is required.

Explanation IFTMC failed resource allocation

Recommended Action No action is required.

Explanation IFTMC resource usage has exceeded a preset threshold

Recommended Action No action is required.

Explanation VLAN_MGR SDB call returned FAILURE for FEX

No action is required.

IKE Messages

This section contains the IKE messages.

IKE-3

Explanation Crypto initialization error

Recommended Action No action is required.

Explanation Service failed to store the enable flag in configuration. As a result, it will exit

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 FIPS mode could not be set by IKE

Recommended Action No action is required.

Explanation IKE process did an abnormal exit

Recommended Action No action is required.

Explanation The number of half open connections has exceeded the maximum limit

Recommended Action No action is required.

Explanation IKE policy negotiation failed for peer [chars].

Recommended Action No action is required.

Explanation There is a IKE policy mismatch for the peer.

Recommended Action No action is required.

Explanation IPsec policy negotiation failed for peer [chars].

Recommended Action No action is required.

Explanation There is a IPsec policy mismatch for the peer.

Recommended Action No action is required.

Explanation A unsupported IKE exchange type [digits] was received from [chars]

Recommended Action No action is required.

IKE-4

Explanation Received a payload in an inappropriate exchange

Recommended Action No action is required.

Explanation Received a malformed message which does not adhere to the protocol

Recommended Action No action is required.

Explanation Received a malformed message which can not be parsed appropriately

Recommended Action No action is required.

Explanation Received an invalid payload

Recommended Action No action is required.

Explanation Received something unsupported

Recommended Action No action is required.

IKE-6

Explanation IKE is exiting since it is not enabled in the configuration

Recommended Action No action is required.

ILC-SPAN Messages

This section contains the ILC-SPAN messages.

ILC-SPAN-3

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

ILC_HELPER Messages

This section contains the ILC-HELPER messages.

ILC_HELPER-2

Explanation SSE License has expired, hence the linecard will be rebooted.

Recommended Action Install appropriate SSE license to be able to use SSM features normally

ILC_HELPER-3

Explanation The ssi boot variable is configured to an invalid image. So, the linecard will be bought online in basic mode instead of advanced SSI mode

Recommended Action Configure a proper image for the ssi boot variable

ILC_HELPER-6

Explanation A valid license has been obtained for the SSM

Recommended Action No action is required.

Explanation The SSI upgrade is delayed due to the configured SSM upgrade delay command

Recommended Action No action is required.

IMAGE_DNLD Messages

This section contains the IMAGE_DNLD messages.

IMAGE_DNLD-SLOT#-2

Explanation Addon image download to module failed. This module is not operational until an addon image has been successfully installed.

Recommended Action Verify the location and version of your module image. Use the install module cli command to download a new module image.

Explanation Image download completed. Module image is being installed.

Recommended Action No action is required.

Explanation Image download failed. Module may be inoperable.

Recommended Action Use show module cli command to verify the state of this module. Retry image download with install module cli command.

Explanation File system consistency check failed

Recommended Action File-system repair is needed using fsck

Explanation Image download started. Module image downloads are non-disruptive to module operation.

Recommended Action No action is required.

IMAGE_DNLD-SLOT#-4

Explanation File system checking and recreation if necessary for /images.

Recommended Action No action is required.

IMAGE_DNLD-SLOT#-5

Explanation Addon image download to module has completed.The module should now be installing this new image.

Recommended Action This message is informational only.

Explanation Addon image download to module has started. This is a disruptive download and this module will be inoperable until this download process is complete.

Recommended Action This message is informational only.

Explanation Addon image download and install to module is successful.

Recommended Action Use the show module cli command to verify the modules operational status.

IMAGE_UPGRADE Messages

This section contains the IMAGE_UPGRADE messages.

IMAGE_UPGRADE-SLOT#-2

Explanation Image Upgrade Error

Recommended Action No action is required.

IMAGE_UPGRADE-SLOT#-4

Explanation Image Upgrade Info

Recommended Action No action is required.

IM Messages

This section contains the IM messages.

IM-1

Explanation Standby supervisor mgmt0 link is down. Proceeding with the install will cause the standby supervisor to become active. This will result in loss of out of band management access to the switch. The show interface mgmt0 standby command can be used from the active supervisor to display the standby supervisor's mgmt0 interface status.

Recommended Action Please fix the Standby supervisor mgmt0 link.

Explanation System switchover not allowed when standby supervisor mgmt0 link is down. Use the bypass-standby-mgmt0 parameter to bypass this check and perform switchover to standby supervisor. This will result in a loss of out of band management access to the switch until the mgmt0 port on the newly active supervisor is brought up. The show interface mgmt0 standby command can be used from the active supervisor to display the standby supervisor's mgmt0 interface status.

Recommended Action Please fix the Standby supervisor mgmt0 link or use the system switchover bypass-standby-mgmt0 command.

IM-3

Explanation Interface feature bind failed, so applications in that feature set may not behave correctly.

Recommended Action No action is required.

Explanation LC Offline was not relayed to some VDC, so applications may not behave correctly.

Recommended Action No action is required.

Explanation Some component returned an error.

Recommended Action No action is required.

Explanation Some component did not respond to a request in stipulated time.

Recommended Action No action is required.

IM-5

Explanation Demux function returned error

Recommended Action No action is required.

Explanation Internal error occurred

Recommended Action No action is required.

Explanation Management interface state changed.

Recommended Action No action is required.

Explanation Interface is not supported or not found

Recommended Action No action is required.

INSTALLER Messages

This section contains the INSTALLER messages.

INSTALLER-1

Explanation This message indicates that control plane was down for more than 80 seconds.

Recommended Action No action is required.

INSTALLER-5

Explanation This message indicates that system wide upgrade has aborted.

Recommended Action No action is required.

Explanation This message indicates system wide upgrade has completed.

Recommended Action No action is required.

Explanation System wide upgrade has been initiated by the user.

Recommended Action No action is required.

Explanation This message indicates that system wide upgrade has been stopped by the user.

Recommended Action No action is required.

INTERFACE_VLAN Messages

This section contains the INTERFACE_VLAN messages.

INTERFACE_VLAN-4

Explanation This SAP took long time in processing Interface VLAN delete notification and caused timeout

Recommended Action No action is required.

Explanation This SAP took long time in processing Interface VLAN remove notification and caused timeout

Recommended Action No action is required.

Explanation Vlan not created before assignment

Recommended Action Interface-vlan

Explanation Keeping Interface VLAN up in non-routable VDC may cause potential traffic black hole

Recommended Action No action is required.

INTERFACE_VLAN-5

Explanation Interface has been configured to be administratively down

Recommended Action No action is required.

Explanation The interface encountered an error while configuring it

Recommended Action No action is required.

Explanation Interface VLAN has been suspended or deleted

Recommended Action No action is required.

Explanation SVI Service Disabled

Recommended Action No action is required.

Explanation SVI Service Enabled

Recommended Action No action is required.

Explanation SVI failed to acquire MAC address

Recommended Action No action is required.

Explanation SVI initialization error

Recommended Action No action is required.

Explanation IM failed to release SVI IOD

Recommended Action No action is required.

Explanation SVI encountered an error in with MTS message

Recommended Action No action is required.

Explanation SVI did not receive response for mts message

Recommended Action No action is required.

Explanation SVI failed to get the list reserved vlans

Recommended Action No action is required.

Explanation SDB updated failed for SVI

Recommended Action No action is required.

Explanation SVI failed to get the list of secondary vlans

Recommended Action No action is required.

Explanation Line protocol status changed for an interface

Recommended Action No action is required.

IOA_LC Messages

This section contains the IOA_LC messages.

IOA_LC-5

Explanation IOA Service Disabled

Recommended Action No action is required.

Explanation IOA Service enabled

Recommended Action No action is required.

IPACL Messages

This section contains the IPACL messages.

IPACL-0

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

IPACL-1

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

IPACL-2

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

IPACL-3

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

IPACL-4

Explanation Ipacl warning message

Recommended Action No action is required.

IPACL-5

Explanation Ipacl does not support this operation

Recommended Action No action is required.

IPACL-6

Explanation Ipacl event occurred

Recommended Action No action is required.

IPFC Messages

This section contains the IPFC messages.

IPFC-2

Explanation The service failed to allocate a block of dynamic memory.

Recommended Action No action is required.

IPFC-3

Explanation The service failed to start. The failure occurred while initializing the component [chars].

Recommended Action Show processes to check the status of the other processes, debug the specified component.

Explanation An IOCTL to the character device failed.

Recommended Action Show IPFC internal interface VSAN <number

Explanation IPFC manager encountered a PSS error.

Recommended Action No action is required.

IPFC-5

Explanation The specified VSAN Interface has been successfully [chars].

Recommended Action No action is required.

Explanation The specified VSAN Interface is [chars].

Recommended Action No action is required.

IPFC-6

Explanation The service has successfully started.

Recommended Action No action is required.

IPQOSMGR Messages

This section contains the IPQOSMGR messages.

IPQOSMGR-2

Explanation Port_id [chars] has qos config [chars] which is incompatible with the peer.

Recommended Action No action is required.

Explanation Failed to do high availability operation. [chars] is the reason.

Recommended Action No action is required.

Explanation Initialization failed for QoS Manager due to [chars], reason: [hex].

Recommended Action No action is required.

Explanation Failed to do MTS operation. [chars] is the reason.

Recommended Action No action is required.

Explanation MTS options setting to [hex] failed for opCode: [dec].

Recommended Action No action is required.

Explanation [chars] is the new active network-qos policy

Recommended Action No action is required.

Explanation Failed to do PSS operation [chars]. [hex] is the reason.

Recommended Action No action is required.

Explanation There was a mismatch in the PSS version. [chars] indicates the PSS service, [dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version.

Recommended Action No action is required.

IPQOSMGR-3

Explanation Configuration error. [chars] is the reason.

Recommended Action No action is required.

Explanation For global qos command, PPF verify/commit failed in vdc [dec] with reason [hex].

Recommended Action No action is required.

Explanation PPF library errors. [chars] is the reason.

Recommended Action No action is required.

IPQOSMGR-4

Explanation Linecard [dec] returned an Message which is reported as [chars].

Recommended Action No action is required.

Explanation VLAN(s) [chars] is (are) getting deleted now. This is an informational message to notify that QoS service-policies are present when the vlan is deleted. If the service-policies are not needed, please detach them from the vlans

Recommended Action No action is required.

Explanation PPF library warning. [chars] is the reason.

Recommended Action No action is required.

Explanation QOSMGR warning messages is reported as [chars] [dec].

Recommended Action No action is required.

IPQOSMGR-6

Explanation DCBXP warning: Port_id [chars] has qos config [chars] which is incompatible with the peer.

Recommended Action No action is required.

Explanation QOSMGR status is reported as [chars].

Recommended Action No action is required.

IPSEC Messages

This section contains the IPSEC messages.

IPSEC-2

Explanation IPSec 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 Modifying IP ACL caused Security Policy Database on the interface to overflow, IP ACL filter not applied to security policy database

Recommended Action Undo IP ACL change

IPSEC-3

Explanation Packets dropped in the 14/2 module. Please collect drop statistics using show ipsec internal crypto-acc interface gigabyte <slot/port

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

Explanation IPSEC FIPS compliance test failed

Recommended Action No action is required.

Explanation Failed to send a message

Recommended Action No action is required.

IPSEC-5

Explanation IP ACL updated while it is mapped to a crypto map that is bound to interface(s)

Recommended Action No action is required.

Explanation IPSec Disabled due to License Expiry

Recommended Action No action is required.

Explanation IPSec Disabled

Recommended Action No action is required.

Explanation IPSec Enabled

Recommended Action No action is required.

Explanation IPSec SA created

Recommended Action No action is required.

Explanation IPSec SA deleted

Recommended Action No action is required.

Explanation IPSec SA rekeyed

Recommended Action No action is required.

Explanation IPSec tunnel created

Recommended Action No action is required.

Explanation IPSec tunnel deleted

Recommended Action No action is required.

Explanation IPSec tunnel rekeyed

Recommended Action No action is required.

IPS_SB_MGR Messages

This section contains the IP_SB_MGR messages.

IPS_SB_MGR-SLOT#-2

Explanation Node is not incrementing heartbeats periodically

Recommended Action Potential node software issue. Please contact your support representative

Explanation Node manager is not receiving heartbeat responses from the node

Recommended Action Potential node software issue. Please contact your support representative

Explanation There was a problem during the partitioning of disk and creation of file systems during node install.

Recommended Action Potential node software issue. Please contact your support representative

Explanation The software servicing the data path on the port has failed

Recommended Action No action is required.

IPS_SB_MGR-SLOT#-3

Explanation The compression engine did not respond to heartbeats, due to some failure. SAN-OS will restart the compression engine to clear the problem.

Recommended Action No action is required.

Explanation The encryption engine did not respond to heartbeats, due to some failure. SAN-OS will restart the encryption engine to clear the problem.

Recommended Action No action is required.

Explanation FIPS self test failed for the algorithm. Restarting the octeon.

Recommended Action No action is required.

IPS_SB_MGR-SLOT#-4

Explanation The svc image on the node is not compatible with the add on image running on the linecard.

Recommended Action Please contact your support representative

Explanation The new svc image is not compatible with the svc image currently running on the node

Recommended Action Please contact your support representative

Explanation The svc image on the node is not compatible with the supervisor image.

Recommended Action Please contact your support representative

IPS_SB_MGR-SLOT#-6

Explanation This is an event log of sb_mgr relating to a port/node

Recommended Action No action is required.

IPS Messages

This section contains the IPS messages.

IPS-2

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

IPS-3

Explanation Duplicate IPv4 address is configured in the network

Recommended Action No action is required.

Explanation FTA Exch being aborted

Recommended Action Informational no action required

Explanation Sense data with ERA sent

Recommended Action SYSLOGDOC_CONTACT_TAC

Explanation FCIP got an ERA 35

Recommended Action SYSLOGDOC_CONTACT_TAC

Explanation FCIP got an ERA 38

Recommended Action SYSLOGDOC_CONTACT_TAC

Explanation FCIP-FTA got a Permanent Error

Recommended Action Informational no action required

Explanation FCIP-FTA got a Permanent Error

Recommended Action Informational no action required

Explanation FTA Command timed out

Recommended Action Informational no action required

Explanation FCIP Link Failed with Loss of Sync.

Recommended Action No action is required.

Explanation FIPS error occurred in the IPS module.

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 Parity error occurred in dma-bridge egress direction.

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 IPS module FIPS mode error

Recommended Action No action is required.

Explanation IPS FIPS compliance test failed

Recommended Action No action is required.

Explanation Parity error occurred in dma-bridge ingress direction.

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 clearing the CFS 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 the cfs config data. The reason for the failure: [chars]

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

Explanation An error occurred while distributing the CFS config data. The reason for the failure: [chars]

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

Explanation An error occurred while acquiring the CFS 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 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 Merge cleared, reason: [chars]

Recommended Action No action is required.

Explanation An error occurred while committing the cfs merge config data. The reason for the failure: [chars]

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

Explanation An error occurred while distributing the CFS merge config data. The reason for the failure: [chars]

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

Explanation An error occurred while merging the iSLB CFS fabrics. 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 pre committing merge data. The reason for the failure: [chars]

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

Explanation Merge requested rejected, reason: [chars]

Recommended Action No action is required.

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

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

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

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

Explanation PWWN reservation claim failed. 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 PWWN reservation release failed. 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 releasing the CFS 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 distributing the VRRP CFS runtime data. The reason for the failure: [chars]

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

Explanation ISLB zoneset activation 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 ISLB zoneset activation failed. Zone server busy.

Recommended Action Retry the iSLB zoneset activation.

Explanation ISLB zoneset activation failed. No active zoneset.

Recommended Action Activate a zoneset in the specified VSAN and retry

Explanation Congestion detected on Gigabit Ethernet port due to RED threshold limit

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

IPS-4

Explanation The FCIP Ficon Tape Acceleration configuration does not match with peers configuration'

Recommended Action Fix the FCIP Ficon Tape Acceleration configuration to be consistent with the peer

Explanation The FCIP FICON tape acceleration VSAN configuration experienced an error when disabling and enabling the VSAN over the FCIP tunnel. The FCIP tunnel was disabled and re-enabled as a result of this error to ensure data integrity.

Recommended Action No action is required.

Explanation The FCIP configuration was accepted, but the FCIP interface did not bind to a physical interface because the appropriate license was not available. If a license becomes available in the future, this FCIP interface will bind to a physical interface automatically.

Recommended Action Check the license state with “show license usage” and acquire the necessary FCIP license

Explanation The XRC Acceleration configuration was accepted, but will remain inactive until a valid license is available. When the appropriate license is installed, XRC acceleration will be activated.

Recommended Action Check the license state with “show license usage” and acquire the necessary XRC_ACCL license

Explanation The XRC Acceleration configuration is activated as a valid license has been installed.

Recommended Action No action is required.

IPS-5

Explanation FCIP/ISCSI Interface bind to Ethernet port failed

Recommended Action No action is required.

Explanation Bport Keepalives not supported in this release

Recommended Action Informational no action required

Explanation Bport not supported in this release

Recommended Action Informational no action required

Explanation FTA Already Off

Recommended Action Informational no action required

Explanation FTA Already ON

Recommended Action Informational no action required

Explanation FTA is DOWN

Recommended Action Informational no action required

Explanation FTA is UP

Recommended Action Informational no action required

Explanation FCIP Disbanded a Group

Recommended Action Informational no action required

Explanation FCIP established a Path Group

Recommended Action Informational no action required

Explanation Doing RSCN Cleanup, Pass 1

Recommended Action Informational no action required

Explanation Doing RSCN Cleanup, Pass 2

Recommended Action Informational no action required

Explanation FCIP Resigned a Group

Recommended Action Informational no action required

Explanation Device type discovered is 3490

Recommended Action Informational no action required

Explanation Device type discovered is 3590

Recommended Action Informational no action required

Explanation FCIP discovered a non-tape device

Recommended Action Informational no action required

Explanation FTA turned off for the Last Vsan

Recommended Action Informational no action required

Explanation FTA turned off for the Non-Last Vsan

Recommended Action Informational no action required

Explanation FTA turned ON

Recommended Action Informational no action required

Explanation Generic FTA Warning

Recommended Action Informational no action required

Explanation The FCIP FICON Tape Read Accelerator configuration does not match with peers configuration'

Recommended Action Fix the FCIP FICON Tape Read Accelerator configuration to be consistent with the peer

Explanation FCIP Interface was Created or Deleted

Recommended Action No action is required.

Explanation Change mode1 compression to mode2 on a MSM/SSN-16 linecard

Recommended Action Informational no action required

Explanation Number of configured tcp connections dont match number of connections on current lyup

Recommended Action No action is required.

Explanation Peer linecard is a MSM/SSN-16

Recommended Action Informational no action required

Explanation Peer linecard is non MSM/SSN-16

Recommended Action Informational no action required

Explanation The FCIP Tape Read Acceleration capability does not match with peers configuration.

Recommended Action Fix the FCIP Tape Read Acceleration capability to be consistent with the peer.

Explanation Special-Frame not supported in this release.

Recommended Action Informational no action required.

Explanation The FCIP Tape Acceleration configuration does not match with peers configuration.

Recommended Action Fix the FCIP Tape Acceleration configuration to be consistent with the peer.

Explanation The FCIP Write/Tape Acceleration software capability does not match with peers software capability'

Recommended Action Fix the FCIP software to be consistent with the peer

Explanation Timestamp between local and remote side exceeds the configured tolerance

Recommended Action No action is required.

Explanation FCIP/ISCSI Interface UNBIND from Ethernet port failed

Recommended Action No action is required.

Explanation The FCIP Write Acceleration configuration does not match with peers configuration.

Recommended Action Fix the FCIP Write Acceleration configuration to be consistent with the peer.

Explanation FCIP Write/Tape Acceleration received XFER-RDY after exchange cleanup.

Recommended Action No action is required.

Explanation The FCIP XRC Emulator configuration does not match with peers configuration.

Recommended Action Fix the FCIP XRC Emulator configuration to be consistent with the peer.

Explanation Details of the packet dropped due to ACLs

Recommended Action No action is required.

Explanation IPS Manager feature enabled/disabled

Recommended Action No action is required.

Explanation FCIP and iSCSI interface are trying to use the same local port, please use different ports.

Recommended Action No action is required.

Explanation ISCSI Ingress Data Digest CRC failed.

Recommended Action No action is required.

Explanation Number of SCSI session down during the last time interval.

Recommended Action No action is required.

Explanation ISCSI session goes down.

Recommended Action No action is required.

Explanation ISCSI session comes up and reaches Full-Feature phase

Recommended Action No action is required.

Explanation FC session for the iSCSI session failed over to newly active port

Recommended Action No action is required.

Explanation ISCSI FCNS query response.

Recommended Action No action is required.

Explanation ISCSI Session Create failed.

Recommended Action No action is required.

Explanation ISCSI Session Create redirected.

Recommended Action No action is required.

Explanation ISCSI Session Redirect timeout.

Recommended Action No action is required.

Explanation CFS Session Cleared by user.

Recommended Action No action is required.

Explanation The s_id and / or the d_id field in the frames LRTP header does not match the s_id or d_id field in the inner header.

Recommended Action No action is required.

Explanation Cannot configure IPS port IP address.

Recommended Action No action is required.

Explanation Ethernet Processing Core failed.

Recommended Action No action is required.

Explanation Special frame received and destination profile ID does not match local profile ID

Recommended Action No action is required.

Explanation Special frame received and source/destination fabric wwn does not match local destination/ source fabric wwn

Recommended Action No action is required.

Explanation Special frame received and interface is admin down

Recommended Action No action is required.

Explanation Special frame received and interface special frame configuration is disabled

Recommended Action No action is required.

Explanation Special frame response has a different nonce than was originally sent in the special frame

Recommended Action No action is required.

Explanation Special frame was not received by the passive-side of the FCIP TCP tunnel within given time period

Recommended Action No action is required.

Explanation Special frame response has a mismatch in one of the bytes from what was sent from the FCIP special frame sender

Recommended Action No action is required.

Explanation Special frame response was not received by the active-side of the FCIP TCP tunnel within given time period

Recommended Action No action is required.

IPS-6

Explanation FCIP-FTA Read Acceleration started

Recommended Action Informational no action required

Explanation FCIP-FTA Read Acceleration stopped

Recommended Action Informational no action required

Explanation FCIP-FTA Write Acceleration started

Recommended Action Informational no action required

Explanation FCIP-FTA Write Acceleration stopped

Recommended Action Informational no action required

IPS-7

Explanation ISCSI FCNS query

Recommended Action No action is required.

Explanation ISCSI FCNS query response

Recommended Action No action is required.

Explanation ISCSI FCNS query

Recommended Action No action is required.

Explanation ISCSI FCNS query response

Recommended Action No action is required.

Explanation iSNS server returned an error for register/deregister request. For select error codes iSNS client would retry and re-register all target nodes corresponding to the interface

Recommended Action No action is required.

IPV6 Messages

This section contains the IPV6 messages.

IPV6-2

Explanation The IP Configuration Manager failed to allocate a block of dynamic memory.

Recommended Action No action is required.

IPV6-3

Explanation Writing to a file failed probably due to no space.

Recommended Action Ipv6

Explanation The service failed to start. The failure occurred while initializing the component [chars].

Recommended Action Show processes to check the status of the other processes, debug the specified component.

IPV6-4

Explanation Duplicate address detection for IP address failed.

Recommended Action Ipv6

IPV6-6

Explanation Configuration message that needs to be logged.

Recommended Action No action is required.

Explanation The specified interface has been deleted. The service will delete all the configuration on that interface.

Recommended Action No action is required.

Explanation The IP address [chars] has been successfully [chars] on the interface [chars].

Recommended Action No action is required.

Explanation The specified route is successfully configured but currently is not active.

Recommended Action Check that the route is correct and the outgoing interface is operationally up.

Explanation The IP Configuration Manager service has successfully started.

Recommended Action No action is required.

IP Messages

This section contains the IP messages.

IP-1

Explanation Dhcp-client failed to get the ip from server, probably due to server lease unavailability or cable dis-connectivity.

Recommended Action Ip

IP-2

Explanation The IP Configuration Manager failed to allocate a block of dynamic memory.

Recommended Action No action is required.

IP-3

Explanation Writing to a file failed probably due to no space.

Recommended Action Ip

Explanation The service failed to start. The failure occurred while initializing the component [chars].

Recommended Action Show processes to check the status of the other processes, debug the specified component.

IP-4

Explanation Duplicate address detected for IP address.

Recommended Action Ip

IP-6

Explanation Configuration message that needs to be logged.

Recommended Action No action is required.

Explanation DHCP-client is able to get the ip address from server,

Recommended Action No action is required.

Explanation The specified interface has been deleted. The service will delete all the configuration on that interface.

Recommended Action No action is required.

Explanation The IP address [chars] has been successfully [chars] on the interface [chars].

Recommended Action No action is required.

Explanation The specified route is successfully configured but currently is not active.

Recommended Action Check that the route is correct and the outgoing interface is operationally up.

Explanation The IP Configuration Manager service has successfully started.

Recommended Action No action is required.

ISAPI Messages

This section contains the ISAPI messages.

ISAPI-SLOT#-0

Explanation The Internet Server Application Programming Interface (ISAPI) caused a system failure. The name of the application is INVISTA.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) caused a system failure. The card type is MSM.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) caused a system failure. The name of the application is NSP.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) caused a system failure The card type is SSM.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) caused a system failure The card type is SSN.

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

ISAPI-SLOT#-1

Explanation The Internet Server Application Programming Interface (ISAPI) caused failures in dependent services. The name of the application is INVISTA.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) caused failures in dependent services. The card type is MSM.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) caused failures in dependent services. The name of the application is NSP.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) caused failures in dependent services. The card type is SSM.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) caused failures in dependent services. The card type is SSN.

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

ISAPI-SLOT#-2

Explanation The Internet Server Application Programming Interface (ISAPI) has encountered a catastrophic error. The name of the application is INVISTA.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) has encountered a catastrophic error. The card type is MSM.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) has encountered a catastrophic error. The name of the application is NSP.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) has encountered a catastrophic error. The card type is SSM.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) has encountered a catastrophic error. The card type is SSN.

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

ISAPI-SLOT#-3

Explanation The Internet Server Application Programming Interface (ISAPI) has encountered a an error. The name of the application is INVISTA.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) has encountered a an error. The card type is MSM.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) has encountered a an error. The name of the application is NSP.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) has encountered a an error. The card type is SSM.

Recommended Action 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 Internet Server Application Programming Interface (ISAPI) has encountered a an error. The card type SSN.

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

ISAPI-SLOT#-4

Explanation This is an Internet Server Application Programming Interface (ISAPI) warning message from the application INVISTA.

Recommended Action No action is required.

Explanation This is an Internet Server Application Programming Interface (ISAPI) warning message. The card type is MSM.

Recommended Action No action is required.

Explanation This is an Internet Server Application Programming Interface (ISAPI) warning message. The name of the application is NSP.

Recommended Action No action is required.

Explanation This is an Internet Server Application Programming Interface (ISAPI) warning message. The card type is SSM.

Recommended Action No action is required.

Explanation This is an Internet Server Application Programming Interface (ISAPI) warning message. The card type is SSN.

Recommended Action No action is required.

ISAPI-SLOT#-5

Explanation This is an Internet Server Application Programming Interface (ISAPI) notification. The name of the application is INVISTA.

Recommended Action No action is required.

Explanation This is an Internet Server Application Programming Interface (ISAPI) notification. The card type is MSM.

Recommended Action No action is required.

Explanation This is an Internet Server Application Programming Interface (ISAPI) notification. The name of the application is NSP.

Recommended Action No action is required.

Explanation This is an Internet Server Application Programming Interface (ISAPI) notification. The card type is SSM.

Recommended Action No action is required.

Explanation This is an Internet Server Application Programming Interface (ISAPI) notification. The card type is SSN.

Recommended Action No action is required.

ISAPI-SLOT#-6

Explanation This is a message that indicates that an Internet Server Application Programming Interface (ISAPI) event has occurred. The name of the application is INVISTA.

Recommended Action No action is required.

Explanation This message indicates that an Internet Server Application Programming Interface (ISAPI) event has occurred. The card type is MSM.

Recommended Action No action is required.

Explanation This is a message that indicates that an Internet Server Application Programming Interface (ISAPI) event has occurred. The name of the application is NSP.

Recommended Action No action is required.

Explanation This message indicates that an Internet Server Application Programming Interface (ISAPI) event has occurred. The card type is SSM.

Recommended Action No action is required.

Explanation This message indicates that an Internet Server Application Programming Interface (ISAPI) event has occurred. The card type is SSN.

Recommended Action No action is required.

ISAPI-SLOT#-7

Explanation This message provides debug information for the conditions that occurred in the Internet Server Application Programming Interface (ISAPI). The name of the application is INVISTA.

Recommended Action No action is required.

Explanation This message provides debug information for the conditions that occurred in the Internet Server Application Programming Interface (ISAPI). The card type is MSM.

Recommended Action No action is required.

Explanation This message provides debug information for the conditions that occurred in the Internet Server Application Programming Interface (ISAPI), specifically in the application: NSP.

Recommended Action No action is required.

Explanation This message provides debug information for the conditions that occurred in the Internet Server Application Programming Interface (ISAPI). The card type is SSM.

Recommended Action No action is required.

Explanation This message provides debug information for the conditions that occurred in the Internet Server Application Programming Interface (ISAPI). The card type is SSN.

Recommended Action No action is required.

ISCM Messages

ISCM-2

Explanation RMAP

Recommended Action ACL cannot be completely deleted.

Explanation License or grace-period has expired.

Recommended Action Take steps to renew license. Feature will be disabled.

Explanation License does not exist when attempting to enable ITD feature.

Recommended Action Acquire license or grace-period permission.

Explanation License or grace-period has expired.

Recommended Action Take steps to renew license. Feature will be disabled.

Explanation License does not exist when attempting to enable RISE feature.

Recommended Action Acquire license or grace-period permission.

ISCM-3

Explanation Acl was not created/deleted.

Recommended Action Check TCAM resource limit, and the sys admin.

Explanation 7K cannot find a route to the real server.

Recommended Action Check real server network reachability in the current switch.

Explanation PBR entries for RISE cannot be deleted cleanly.

Recommended Action Manually delete pbr entries.

Explanation Rmap step was not completed.

Recommended Action Check TCAM resource limit, or rmap collision on the same interface, and the sys admin.

Explanation URIB dropped this RHI request. See reason string with the following possibilities: 1. SVI for data vlan [dec] does not exist. 2. SVI for data vlan [dec] is down. 3. urib issues.

Recommended Action Take corrective action per the reason.

ISCM-4

Explanation PBR entries for RISE cannot be deleted cleanly.

Recommended Action Manually delete pbr entries.

Explanation APBR will not function correctly without pbr feature.

Recommended Action Manually enable pbr feature.

Explanation See reason string in the Message with the following possibilities: 1. Error in bootstrap/health-monitoring response. 2. Timed out while waiting for bootstrap/health-monitoring response. 3. Failed to send bootstrap/health-monitoring message. 4. Control VLAN interface is not operational. 5. RISE interface [chars] is not operational. 6. RISE interface [chars] does not have control VLAN [dec] as trunk member. 7. Control VLAN ([dec]) interface does not have valid IP. 8. RISE port channel po [dec] has no member ports. 9. Failed to send vlan-group. 10. RISE IP [chars] is already assigned to another service, slot id [dec].

Recommended Action Take corrective action per the reason

Explanation See the reason.

Recommended Action Try again with the upgrade.

Explanation Application should not send msg during ISSU. iSCM will ignore.

Recommended Action No action is required.

Explanation License or grace-period expiration warning.

Recommended Action Take steps to renew license. Prepare for feature disable.

ISCM-5

Explanation See the reason.

Recommended Action Check the network connectivity and the appliance status.

ISNS Messages

This section contains the ISNS messages.

ISNS-2

Explanation ISNS CFS 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 ISNS 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.

IVR Messages

This section contains the IVR messages.

IVR-2

Explanation This can happen if failure happens during building, distributing or committing the virtual dynamic pfcid table

Recommended Action Please 1. check the fabric connection or 2. check current virtual user-configured pfcid entries and internally assigned virtual fcid entries for possible conflict

Explanation This can happen if some switches does not support the virtual pfcid auto learn feature'

Recommended Action Please upgrade the unsupported switches

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

Recommended Action No action is required.

Explanation Failed to program FCID rewrite entries probably because the hardware ran out of FCID rewrite entries. This can happen if there are too many devices in Inter-VSAN zone or too many local VSANs in VSAN topology

Recommended Action Reduce the number of devices involved in IVR in the active IVR zoneset. Also, reduce the number of redundant transit VSANs, if any

Explanation This probably happened because NAT mode was modified without completely deactivating the active IVR zoneset

Recommended Action The switch needs to be rebooted

Explanation Failed to program VSAN rewrite entries probably because the hardware ran out of VSAN rewrite entries. This can happen if there are too many devices in Inter-VSAN zone or too many local VSANs in VSAN topology

Recommended Action Reduce the number of domains involved in IVR by moving the members of active IVR zoneset to fewer switches. Also, reduce the number of redundant transit VSANs, if any

Explanation Build Fabric (BF) failed in VSAN [dec]. The BF was initiated in order to remove an unused virtual domain [dec] from the fcdomain list in that VSAN. The virtual domain still remains in the fcdomain list and hence it would not be available in that VSAN for assignment.

Recommended Action Perform a manual build fabric using fc domains interface if you would like to remove the unused virtual domain (s) from the fc domain list.

Explanation Request Domain Identifier (RDI) command to allocate virtual domain [dec] failed in VSAN [dec]. Received another domain [chars] instead. IVR-members connected to third-party switch may not participate in IVR communications. It is likely that the domain requested in the RDI command is already in use.

Recommended Action Reassign the domains so that the domain requested via RDI does not overlap with any existing domain in that VSAN.

Explanation Inter-VSAN Routing disable failed for reason: [chars]. Cleanup might not have completed

Recommended Action Deactivate ivr zoneset and disable ivr again. If that fails, then the ivr process would terminate itself in 5 minutes

Explanation Inter-VSAN zoneset activation failed in VSAN [dec]: [chars]. This could be an intermittent regular zoneset activation error. The activation will be retried in [dec] seconds.

Recommended Action No action is required.

Explanation License required for continued IVR operation is not available. Hence IVR is shutting down

Recommended Action Install appropriate license for IVR services and then enable IVR again.

Explanation License required for continued IVR operation is not available. Unless the required license is installed IVR would shutdown in [dec] seconds. IVR configurations would be lost.

Recommended Action Install appropriate license for IVR services to continue to operate uninterrupted within [dec] seconds

Explanation This can happen if conflict happens during persistent virtual domain, or virtual fcid entry configuration.

Recommended Action Please assign a non-conflict persistent virtual domain or fcid entry with current dynamic entries

Explanation This can happen if the virtual domain/fcid configured by the user is - a) Already in use (either by IVR or a real switch) b) Not allowed due to interop mode or allowed domain list

Recommended Action Please make sure that the configured virtual domain/fcid is allowed and available for use

Explanation Currently advertised virtual domain [dec] in VSAN [dec] is native to VSAN [dec]. This switch has learned of a device that is member of active IVR zone and has the same domain ID, but belongs to a different native VSAN. This device would not be advertised in that VSAN until the domain conflict is resolved.

Recommended Action No action is required.

Explanation This can happen if the virtual domain/fcid internally configured is already in use by another active device

Recommended Action Please assign a different persistent virtual fcid by CLI command

IVR-3

Explanation Could be caused by ivr NAT is not enable

Recommended Action No action is required.

Explanation Abstract ACL Manager (AAM) mode deregister failed

Recommended Action No action is required.

Explanation Abstract ACL Manager (AAM) register failed

Recommended Action No action is required.

Explanation IVR invoked ACL API and received the error code. [chars] describes the API and [chars] specifies the error.

Recommended Action No action is required.

Explanation ACL could not program permit entries for IVR traffic. [chars] describes the interface named and [chars] describes the system Message from ACL. IVR traffic coming from the interface may be dropped.

Recommended Action If the problem persists, please contact TAC, or your reseller for support.

Explanation ACL could not program IVR PLOGI could not be programmed. slot[dec] describes the line card slot number and [chars] describes the system Message. PLOGI and its response may be dropped because ivr process cannot capture those frames.

Recommended Action No action is required.

Explanation AFID configuration is different at different ivr-enabled switches in the same VSAN. Change AFID configuration (auto mode) or vsan topology configuration (user mode) to make it consistent

Recommended Action No action is required.

Explanation Inter-VSAN 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 When device-alias sends the validation request, IVR database is locked and a timer is started. For any reason, if device-alias commit/abort notification is not received within the expected time frame, the lock timer gets expired and the lock is released. If device-alias commit notification is received after the lock is released, the changes are not applied and this could cause inconsistency between IVR and device-alias.

Recommended Action No action is required.

Explanation This happens if ficon is enabled on VSANs [chars] and native switch of device with port WWN [chars] is not present in the current active fabric binding database of those VSANs. This is a requirement for ficon compliance.

Recommended Action No action is required.

Explanation Device has come online on a AFID/VSAN different from the configured native AFID/VSAN

Recommended Action No action is required.

Explanation Device has come online on a VSAN different from the configured native VSAN or the device does not satisfy unique domain criteria.

Recommended Action No action is required.

Explanation IVR invoked DM API and received the error code. [chars] describes the API and 0x[hex] specifies the error.

Recommended Action No action is required.

Explanation VSAN interop modes place restrictions on what domain ranges are allowed. This domain is out of the range allowed for this interop mode. See the Cisco MDS 9000 Family Configuration Guide for details on the domain range limitations.

Recommended Action Change the domain of the switch to which this IVR zone member is connected to so that it is within the allowed domain list for the interop mode. The domain identifier can be statically assigned using fcdomain interface. You can also configure a range of domains allowed in a VSAN using the fc domains allowed-domains' interface.

Explanation Device with port WWN [chars] and FCID [dec] may not be able to participate in Inter-VSAN zone since domain [dec] is already assigned in VSAN [dec].

Recommended Action No action is required.

Explanation IVR invoked FC2 API for [chars] socket and received the error code. [chars] describes the API and 0x[hex] specifies the error.

Recommended Action No action is required.

Explanation Could be caused by active zoneset, pending activation /deactivation or non-empty device list

Recommended Action No action is required.

Explanation This happens when either after IVR retried the request few times or ACL experienced error while processing the request.

Recommended Action No action is required.

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

Recommended Action No action is required.

Explanation Inter-VSAN member properties incompatible with interop mode vsan

Recommended Action No action is required.

Explanation Fcid-nat must be enabled before IVR zoneset activation for Sabre platform.

Recommended Action No action is required.

Explanation DU Vsan Segmented, ivr traffic may be impact by du vsan segmentation.

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 Inter-VSAN zoneset activation failed in VSAN.

Recommended Action No action is required.

Explanation Inter-VSAN zoneset activation failed.

Recommended Action No action is required.

Explanation Inter-VSAN zoneset deactivation failed in VSAN.

Recommended Action No action is required.

Explanation Inter-VSAN zoneset deactivation 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 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 IVR process unsuccessfully tried to send a MTS message. MTS error number is specified in [dec].

Recommended Action No action is required.

Explanation IVR invoked FCNS API and received the error code. [chars] describes the API and 0x[hex] specifies the error.

Recommended Action No action is required.

Explanation IVR read the saved configuration and encountered an error while rebuilding the runtime configuration. [chars] describes the configuration which the process tried to restore and 0x[hex] is the system err code.

Recommended Action No action is required.

Explanation [chars] specifies the context where the failure occurred and 0x[hex] specifies the error.

Recommended Action No action is required.

Explanation IVR read the saved runtime database and encountered an error while rebuilding the runtime database. [chars] describes the runtime database which the process tried to restore and 0x[hex] is the system error code.

Recommended Action No action is required.

Explanation This happens when either after IVR retried the request few times or ACL experienced error while processing the request.

Recommended Action No action is required.

Explanation IVR invoked RIB API and received the error code. [chars] describes the API and 0x[hex] specifies the error.

Recommended Action No action is required.

Explanation This happens when either after IVR retried the request few times or ACL experienced error while processing the request.

Recommended Action No action is required.

Explanation Inter-VSAN Topology has failed due to [chars]. Possible reasons are (a) Number of AFID/VSAN combination is more than the maximum supported value of 128, or (b) Number of ivr-enabled switches is more than the maximum supported value of 128

Recommended Action No action is required.

Explanation IVR process received unexpected MTS event. MTS opcode is specified in [dec].

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.