Cisco IOS Release 15.x SY System Message Guide
MMLS through RADIO_DRIVER
Downloads: This chapterpdf (PDF - 2.97MB) The complete bookPDF (PDF - 26.81MB) | Feedback

MMLS Messages

Table Of Contents

MMLS Messages

MMLS-3

MMLS-4

MMLS-6

MPLS_ADJ_SB Messages

MPLS_ADJ_SB-4

MPLS_COMMON Messages

MPLS_IPRM Messages

MPLS_IPRM-3

MMLS_RATE Messages

MMLS_RATE-3

MPLSMFISTATIC Messages

MPLSMFISTATIC-3

MPLSOAM Messages

MPLSOAM-3

MPLS_PACKET Messages

MPLS_PACKET-3

MPLS_PACKET-4

MPLS_TE Messages

MPLS_TE-2

MPLS_TE-3

MPLS_TE_AUTOMESH Messages

MPLS_TE_AUTOMESH-5

MPLS_TE_AUTO_TUN-3

MPLS_TE_AUTO_TUN-4

MPLS_TE_LM Messages

MPLS_TE_LM-3

MPLS_TE_LM-5

MPLS_TE_PCALC-2

MPLS_TE_PCALC-3

MPLS_VPN_HA Messages

MPLS_VPN_HA-3

MPLS_VPN_HA-7

MPLS_VPN_ISSU Messages

MPLS_VPN_ISSU-3

MPOA-3

MPOA-4

MPOA-5

MRIB_PROXY Messages

MRIB_PROXY-2

MROUTE Messages

MROUTE-2

MROUTE-3

MROUTE-4

MROUTE-6

MSC100_SPA_CC Messages

MSC100_SPA_CC-0

MSDP Messages

MSDP-3

MSDP-4

MSDP-5

MSPI-1

MSPI-2

MSPI-4

MSPI-6

MSFC2 Messages

MSFC2-3

MTRIE Messages

MTRIE-4

MUESLIX Messages

MUESLIX-1

MUESLIX-3

MUESLIX-4

MVR_RP Messages

MVRP Messages

MVRP-3

MVRP-6

MVRP_CONST Messages

MVRP_CONST-3

MVRP_CONST-6

MVRP_ISSU Messages

MVRP_ISSU-2

MVRP_ISSU-3

MVRP_SWITCH Messages

MVRP_SWITCH-6

MXT_FREEDM-1

MVR_RP Messages

MVR_RP-3

MVR_RP-6

MWAM Messages

NATMIB_HELPER Messages

NATMIB_HELPER-3

NBAR Messages

NBAR-1

NBAR-2

NETCONF Messages

NETCONF-3

NETWORK_CLOCK_SYNCHRONIZATION

NETFLOW_AGGREGATION Messages

NETFLOW_AGGREGATION-3

NETFLOW_AGGREGATION-4

NETFLOW_AGGREGATION-6

NETWORK_PORT_SATELLITE Messages

NETWORK_PORT_SATELLITE-3

NETWORK_PORT_SATELLITE-6

NETWORK_RF_API Messages

NETWORK_RF_API-3

NET_SERV-4

NETWORK_RF_API-6

NHRP Messages

NHRPSNMP Messages

NIM-2

NMSP Messages

NP Messages

NP-2

NP-3

NP-5

NP_BS-2

NP_BS-6

NP_CLIENT Messages

NP_CLIENT-2

NP_CLIENT-3

NP_EST-3

NP_EST-6

NP_MD-0

NP_MD-1

NP_MD-3

NP_MD-6

NP_MM-3

NP_SIGLIB-3

NP_SPE_DS-3

NP_SSM-0

NP_SSM-6

NP-CRASHINFO Messages

NP-DEV Messages

NP_DEV-2

NP_DEV-3

NP_DEV-5

NP_DEV-6

NP_UCODE Messages

NSE100 Messages

NSE100-3

NSE100-4

NSE100-5

NSE100-5

NSP-2

NSP-3

NSP-4

NSPINT-3

NSPINT-5

NSP_APS-4

NSP_OIR-3

NSP_OIR-4

NSP_OIR_6

NP_UCODE Messages

NRP-3

NSE-3

NSE-6

NTI Messages

NTI-3

NTP Messages

NTP-4

NTP-5

NTP-6

OBFL Messages

OBFL-5

OBFL_ERRMSG Messages

OBFL_ERRMSG-5

OCE Messages

OCE-3

ODM Messages

ODM-3

OER_TT_FLOW Messages

OER_TT_FLOW-2

OER_TT_FLOW-4

OIR Messages

OIR-3

OIR-6

OIR_ISSU Messages

OIR_ISSU-3

OIR-SP

OLM Messages

OLM-3

OLM-4

OLM-5

ONLINE Messages

ONLINE-2

ONLINE-3

ONLINE-6

ONLINEDIAG Messages

ONS15530 Messages

ONS15530-1

ONS15530-2

ONS15530-3

ONS15530-4

ONS15530-5

OOBP-4

OPTICAL_MONITOR Messages

OPTICAL_MONITOR-4

OPTICAL_IF-1

OPTICAL_IF-3

OPTICAL_IF_ALARMS-3

OSCP-3

OSCP-4

OSCP-7

OSM_MULTILINK Messages

OSM_MULTILINK-3

OSM_MULTILINK-4

OSM_MULTILINK-5

OSPF Messages

OSPF-3

OSPF-4

OSPF-6

OSPF_NSR Messages

OSPFv3 Messages

OSPFv3-3

OSPFv3-4

OSPFv3-5

OSPFv3-6

OUNIC-4

OTNMGR Messages

PACC Messages

PACC-3

PA-0

PA-2

PA-3

PA-4

PACKET Messages

PACC-0

PACC-1

PACC-3

PACC_IPC-0

PACC_1PC_1

PACC_IPC_3

PACKET-2

PACKET-3

PAD-2

PAD-3

PAGP_DUAL_ACTIVE Messages

PAGP_DUAL_ACTIVE-1

PAGP_DUAL_ACTIVE-3

PAGP_DUAL_ACTIVE-4

PAGP_SWITCH_ISSU Messages

PAGP_SWITCH_ISSU-3

PARSER Messages

PARSER-2

PARSER-3

PARSER-4

PARSER-5

PARSER-6

PARSE_RC Messages

PARSE_RC-3

PARSE_RC-4

PARSE_RC-6

PATCH-3

PBI_OPEN Messages

PBI_OPEN-4

PBR Messages

PBR-2

PBR-3

PBR-4

PCIELIB Messages

PCIELIB-1

PCIELIB-2

PCIELIB-3

PCMCIAFS Messages

PCMCIAFS-3

PCMCIAFS-4

PCMCIAFS-5

PERUSER-3

PF_ASIC Messages

PF_ASIC-3

PF-ETHERCHANNEL Messages

PGM-3

PGM-6

PGMHOST-6

PG_TCP-3

PF Messages

PFINIT Messages

PFINIT-1

PFINIT-2

PFINIT- 4

PFINIT-5

PFINIT-6

PF_ISSU Messages

PF_ISSU-3

PF_OBFL Messages

PF_OBFL-5

PF_PRST_VBL Messages

PF_PRST_VBL-3

PFREDUN Messages

PFREDUN-1

PFREDUN-3

PFREDUN-4

PFREDUN-6

PFREDUN-7

PFREDUN_SP Messages

PFREDUN_SP-3

PHY Messages

PHY-4

PIM Messages

PIM-1

PIM-3

PIM-4

PIM-5

PIM-6

PIM_PROT Messages

PIM_PROT-3

PIM_PROT-4

PIM_PROT-6

PIM_PROT-7

PIMSN Messages

PIMSN-6

PIM_REG_TUN

PKI Messages

PKI-3

PKI-4

PKI-6

PLATFORM Messages

PLATFORM-1

PLATFORM-3

PLATFORM-4

PLATFORM-6

PLATFORM_CAPABILITY-4

PLATFORM_CAT2950-3

PLATFORM_CAT3550-1

PLATFORM_FBM-4

PLATFORM_IPC-3

PLATFORM_PBR-2

PLATFORM_PBR_3

PLATFORM_PBR-4

PLATFORM_PM-3

PLATFORM_RPC-0

PLATFORM_RPC-3

PLATFORM_SPAN-3

PLATFORM_UCAST-3

PLATFORM_VLAN-3

PM Messages

PM-1

PM-3

PM-4

PM-6

PMOD-3

PMB Messages

PMB-4

PM_ISSU Messages

PM_ISSU-3

PM_MODEM_HIST-7

PM_MODEM_MAINT-4

PM_MODEM_MAINT-5

PM_PVLAN_ISSU Messages

PM_PVLAN_ISSU-3

PM_SCP Messages

PM_SCP-1

PM_SCP-2

PM_SCP-3

PM_SCP-4

PM_SCP-6

PNNI-2

PNNI-3

PNNI-4

PNNI-6

PNNI-7

POLARIS Messages

POLARIS-4

POLICY_API Messages

POLICY_API-4

POLICY_MANAGER Messages

POLICY_MANAGER-2

POLICY_MANAGER-3

PORT_SECURITY Messages

PORT_SECURITY-2

PORT_SECURITY-6

POS-1

POS-3

POSDW-1

POSDW-3

POSLC Messages

POLSLC-1

POSLC-3

POT1E1 Messages

POT1E1-1

POT1E1-2

POT1E1-3

POWENET Messages

PPP Messages

PPP-3

PQ3 Messages

PQ3_FE

PQ3_TSEC

PQUICC3 Messages

PQUICC3-1

PQUICC3-3

PRBS Messages

PRBS-5

PROCYON Messages

PROCYON-3

PROCYON_ION_INTR Messages

PROCYON_ION_INTR-3

PRST_IFS Messages

PRST_IFS-3

PRST_VBL Messages

PRST_VBL-3

PT Messages

PXF Messages

PXF_ACL Messages

PXF_ACL-3

PXFAPI Messages

PXFAPI-3

PXF_FIB Messages

PXF_2

PXF_FIB-3

PXF_FLOW Messages

PXF_FLOW-4

PXF_GRE Messages

PXF_GRE-3

PXF_GRE-4

PXF_MPLS_TE Messages

PXF_MPLS_TE-3

PXF_MPLS_TE-4

PXF_QOS Messages

PXF_QOS-3

PXF_VRFS-3

QM Messages

QA-3

QATM-2

QEM-3

QM-2

QM-3

QM-4

QM-6

QLLC-3

QLLC-4

QNQ Messages

QOS Messages

QOS-3

QOS-6

QOSMGR Messages

QOSMGR-3

QOSMGR-4

QUICC-1

QUICC-3

QUICC_ASYNC-3

QUICC_ETHER-1

QUICC_ETHER-3

QUICC_ETHER-5

QUICC_SERIAL-1

QUICC_SERIAL-5

R4K_MP Messages

R4K_MP-3

R4K_MP-5

RAC-3

RADIO-2

RADIO-3

RADIO-4

RADIO-5

RADI0-6

RADIO_DRIVER-1

RADIO_DRIVER-3


MMLS Messages

This section contains Multicast Multilayer Switching (MMLS) messages.

MMLS-3

Error Message    %MMLS-3-ICROIF_BLOCK_ALLOC_FAILED: Allocation of %s block of indices 
for egress distribution over fabric failed 

Explanation    The allocation of the block of indices used for egress distribution over the fabric has failed. As a result, the system will not be able to work in egress replication mode. This condition could be caused by a shortage of hardware resources during boot up or at the time when the first block of indices is completely consumed. A shortage of hardware resources might be caused by having too many VLANs configured.

Recommended Action    Reduce the number of VLANs in the system by entering the no vlan {vlan_id} command and reloading the system, or configure ingress replication mode by entering the mls ip multicast replication-mode ingress command. Ingress replication mode does not use egress distribution indices.

MMLS-4

Error Message    %MMLS-4-ICROIF_INDICES_EXHAUSTED: Unable to allocate index for egress 
distribution over fabric 

Explanation    The indices used for egress distribution over the fabric are exhausted and the system is currently unable to allocate an index. An index is allocated for each unique combination of flow over the fabric and is not freed upon removal of all shortcuts using it. An index-freeing mechanism operates when a threshold for freeing up unused indices is reached. If the number of used indices stays above the threshold after collection of unused indices, another block (up to a maximum of two blocks) of 256 indices is allocated.

Recommended Action    You may not be required to take any action, as the index-freeing mechanism should take care of freeing up unused indices. If the problem remains, try reducing the number of unique combination of flows over the fabric created by the presence of multicast sources and receivers on different line cards.

Error Message    %MMLS-4-VLAN_2K_SR_TR_INSTALL_FAILED: Multicast Multi-Layer 
Switching: Failed to install service reflect translation, hardware resource 
unavailable 

Explanation    The Multicast Service Reflect translation cannot be installed in hardware as a required hardware resource is unavailable.

Recommended Action    Removing tunnel interfaces or reducing the number of service reflect translations would help solve the problem.

MMLS-6

Error Message    %MMLS-6-ADJ_ALLOC_FAILURE: Failed to allocate Adjacency for the 
multicast flow ([IP_address], [IP_address]) 

Explanation    The system is unable to allocate an adjacency for this particular flow. The affected flow will be retried and will be software switched until it is successfully installed in the hardware.

Recommended Action    The adjacency table utilization could be very high and needs to be reduced. Removing some hardware switched flows would help solve the problem.

Error Message    %MMLS-6-BIDIR_ADJ_LIMIT_EXCEEDED: Failed to allocate Adjacency for 
Bidir Multicast shortcuts, exceeded limit of ([dec]), subsequent flows will be 
software switched. 

Explanation    The system limit of maximum adjacencies for bidirectional shortcuts has been exceeded. As a result, any new multicast flows will be switched by the software.

Recommended Action    The number of bidirectional multicast flows is too large to fit in the hardware. There is no workaround.

Error Message    %MMLS-6-FIB_LIMIT_EXCEEDED: Failed to allocate FIB entry, exceeded 
system limit of ([dec]) entries. 

Explanation    The maximum FIB entry limit has been exceeded, so FIB entries cannot be allocated by the MMLS.

Recommended Action    The total number of multicast shortcuts is too large to fit in the FIB table and as a result subsequent shortcuts will be software switched. There is no workaround.

Error Message    %MMLS-6-MCAST_L3FLOW: %s from the Route Processor for Source %i Group 
%i vlan %d 

Explanation    A multicast flow has been installed or deleted.

Recommended Action    No action is required.

Error Message    %MMLS-6-MCAST_STATUS: IP Multicast Multilayer Switching is %sabled 

Explanation    This message indicates whether the multicast Layer 3 multicast feature is enabled or disabled.

Recommended Action    No action is required.

Error Message    %MMLS-6-MET_LIMIT_EXCEEDED: Failed to allocate MET entry, exceeded 
system limit of ([dec]) entries. Number of times MET limit is exceeded in the last 
1 min : [dec] 

Explanation    The maximum MET entry limit has been exceeded, so MET entries cannot be allocated by the MMLS.

Recommended Action    The total number of OIFs is too large to fit in the MET table. Subsequent shortcuts or OIFs will be switched by the software. There is no workaround.

Error Message    %MMLS-6-MMLS_EGRESS_INCAPABLE_LC_INSERTED: MMLS: Egress incapable 
line card ([dec]) inserted in forced egress replication mode 

Explanation    An egress-incapable line card is inserted while the system is operating in forced egress replication mode. The user must not source any multicast traffic on this egress-incapable line card.

Recommended Action    Verify that there is no multicast traffic going through this egress-incapable line card.

Error Message    %MMLS-6-MMLS_EGRESS_INCAPABLE_LC_PRESENT: MMLS: Egress incapable line 
card present while forcing replication mode to egress 

Explanation    There is at least one line card that is egress incapable in the system, but forced egress replication mode is configured on the system. Multicast traffic must not be sourced on the egress-incapable line card.

Recommended Action    Verify that there is no multicast traffic going through this egress-incapable line card.

Error Message    %MMLS-6-MMLS_FSTATS_MAX_PENDING_MSGS: Flow stats enqueued messages 
count([dec]) has reached the maximum and would be reset to [dec] 

Explanation    This message indicates that flow stats pending messages count has reached the maximum. To avoid further flow stats messages from being dropped, the counter would be reset to match the current pending messages count of the ICCQ.

Recommended Action    This message is provided for information only.

Error Message    %MMLS-6-MMLS_HALF_MET: MMLS: IPv6 multicast enabled on supervisor 
uplinks. Available MET space on supervisors is halved 

Explanation    The MET space is being halved to enable IPv6 on supervisor engine uplinks.

Recommended Action    No action is required.

Error Message    %MMLS-6-MMLS_LEGACY_LC_PRESENT: MMLS: Legacy line card present, system 
cannot operate in egress replication mode 

Explanation    There is at least one legacy line card in the system. Therefore, the system cannot operate in egress replication mode when the system is configured for forced egress replication mode.

Recommended Action    Remove the legacy line card(s) if you want the system to operate in forced egress replication mode.

Error Message    %MMLS-6-RPF_ADJ_LIMIT_EXCEEDED: Failed to allocate Adjacency for 
multicast shortcuts with RPF-vlan: ([dec]), exceeded limit of ([dec]), subsequent 
flows will be software switched 

Explanation    The system limit of maximum adjacencies for multicast shortcuts with the same RPF has been exceeded. As a result, any new multicast flows will be software switched.

Recommended Action    The number of multicast flows with the same RPF interface are too large to fit in the hardware. There is no workaround.

Error Message    %MMLS-6-RP_LIMIT_EXCEEDED: Failed to allocate DF index for Bidir-RP, 
exceeded limit of ([dec]) RPs for VPN: ([dec]). Shortcuts for RP: ([IP_address]) 
will be software switched. 

Explanation    The system limit of four RPs per VPN has been exceeded. As a result, the multicast flows for the groups served by this RP will be software-switched.

Recommended Action    The configured RPs are too large to fit in the DF table for one VPN. Attempt to configure the groups among existing RPs in hardware, or configure the RP in another VPN.

Error Message    %MMLS-6-VLAN_ADD_FAILURE_ON_MET_FULL: Error adding vlan [dec] to the 
MET table of some shortcuts 

Explanation    The MET table is full and the system is unable to add the VLAN to some shortcuts. The affected shortcuts will not switch traffic for that VLAN.

Recommended Action    The MET utilization is very high and must be reduced. Removing some VLANs or switching to ingress replication mode will solve the problem.

MPLS_ADJ_SB Messages

The following are MPLS Adjacency Subblock messages.

MPLS_ADJ_SB-4

Error Message    %MPLS_ADJ_SB-4-NO_BACKUP_INTF: [chars] - ifnum [dec] 

Explanation    Backup interface cannot be programmed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

MPLS_COMMON Messages

Error Message    %MPLS_COMMON-3-L3_CONFIG_NOT_RECOMMENDED: LAN interfaces have MPLS 
configured. Do not configure xconnect on interface vlans. 

Explanation    An attempt was made to configure a xconnect on an interface VLAN. The current network configuration has MPLS configured on a LAN interface.

Recommended Action    Do not configure xconnects on an interface VLAN if the network has MPLS configured on a LAN interface.

Error Message    %MPLS_COMMON-3-VPLS_CONFIG_EXCEEDED: The number of EoMPLS/VPLS VCs 
exceeded the maximum supported on %i/%u. 

Explanation    The number of destination routers or the global number of virtual circuits exceeded the maximum supported by the box.

Recommended Action    Refer to network configuration guidelines for the maximum limits

Error Message    %MPLS_COMMON-4-ATOM_ON_MPLS_TE_ONLY: AToM traffic supported only on 
MPLS TE tunnels currently AToM traffic uses interface %s 

Explanation    AToM traffic is supported only on MPLS TE tunnels and not on any other type of tunnels like GRE tunnels. Right now AToM traffic is using the mentioned tunnel interface.

Recommended Action    Please make sure AToM traffic does not use non-MPLS TE tunnels.

MPLS_IPRM Messages

This section contains MPLS IP rewrite manager (IPRM) messages.

MPLS_IPRM-3

Error Message    %MPLS_IPRM-3-DB: [chars] 

Explanation    There is an inconsistency in the information required to request labels from or to process labels received from an IP label distribution module.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_IPRM-3-DB_PATH: [chars] 

Explanation    There is an inconsistency in the information about a prefix path required to request labels from or to process labels received from an IP label distribution module.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_IPRM-3-DB_PNDG_DISC: [chars] 

Explanation    There is an inconsistency in the information about a temporarily deferred action required to populate MPLS forwarding data structures for a prefix.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_IPRM-3-DB_TABLE: [chars] 

Explanation    There is an inconsistency in the information about a (VRF) table ID required to request labels from or to process labels received from an IP label distribution module.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_IPRM-3-DB_TRANS: [chars] 

Explanation    There is an inconsistency in the information about an ongoing transaction required to populate MPLS forwarding data structures for a prefix.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_IPRM-3-INTERNAL: [chars] 

Explanation    An operation required for proper operation of the IP rewrite manager has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_IPRM-3-PATH_LABEL_DEL: [chars] 

Explanation    An attempt to delete MPLS forwarding information for the specified prefix has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_IPRM-3-PATH_LABEL_GET: [chars] 

Explanation    An attempt to access MPLS forwarding information for the specified prefix has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_IPRM-3-PATH_LABEL_UPD: [chars] 

Explanation    An attempt to update MPLS forwarding information for the specified prefix has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_IPRM-3-WALK: [chars] 

Explanation    A request by an IP label distribution module (for example, LDP, BGP) to walk a CEF table cannot be handled.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MMLS_RATE Messages

This section contains Multicast Multilayer Switching Rate Limiting (MMLS_RATE) messages.

MMLS_RATE-3

Error Message    %MMLS_RATE-3-MMLS_PARTIAL_SC_ERROR: Error installing Multicast 
Partial-sc rate-limiter.Operation failed. 

Explanation    The multicast partial SC rate limiter could not be configured because of an error that was returned from the switch processor.

Recommended Action    The LTL index for the partial SC rate limiter might not have initialized yet. Wait several minutes, and try to configure the rate limiter again.

MPLSMFISTATIC Messages

This section contains MPLS Forwarding Infrastructure (MFI) static application messages.

MPLSMFISTATIC-3

Error Message    MPLSMFISTATIC-3-CHUNKMGR: [chars] [hex] 

Explanation    An MPLS MFI static application chunk manager error has occurred.

Recommended Action    This problem may be due to a low memory condition on the device. Check system memory and minimum memory requirements for this release and configuration, and add memory if required. If memory appears to be sufficient and problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show process memory, show version and show running-config commands and your pertinent troubleshooting logs.

Error Message    MPLSMFISTATIC-3-FCALLFAILED: [chars] 

Explanation    A static application function call has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.

Error Message    MPLSMFISTATIC-3-INVALIDPRAMS: [chars] [dec] 

Explanation    Unexpected parameters have been detected in a static application.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.

Error Message    MPLSMFISTATIC-3-WRONGCODEPATH: [chars] 

Explanation    An error involving an unexpected static application code path has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs.

MPLSOAM Messages

This section contains Multiprotocol Label Switching (MPLS) Operations, Administration, and Maintenance (OAM) messages.

MPLSOAM-3

Error Message    %MPLSOAM-3-XDR_COMM: %s:0x%x 0x%x 

Explanation    The XDR communication module reports an unexpected RP/LC XDR condition encountered in the MPLS OAM software. This condition may result in MPLS OAM FIB subblocks becoming out of synchronization between the RP and the line card. This condition should not affect overall system operation.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MPLS_PACKET Messages

This section contains MPLS packet messages.

MPLS_PACKET-3

Error Message    %MPLS_PACKET-3-FWDDISABLE: MPLS [chars] forwarding path disabled 

Explanation    The MPLS forwarding plane has been disabled.

Recommended Action    This log entry is informational only. No action is required.

Error Message    %MPLS_PACKET-3-FWDREENABLE: MPLS [chars] forwarding path reenabled 

Explanation    The MPLS forwarding plane has been reenabled.

Recommended Action    This log entry is informational only. No action is required.

Error Message    %MPLS_PACKET-3-LABELCACHE: [chars] [dec]/[dec] 

Explanation    An MPLS label cache error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MPLS_PACKET-4

Error Message    %MPLS_PACKET-4-NOLFDSB: MPLS packet received on non MPLS enabled 
interface [chars] L3 type [hex] label {[dec] [dec] [dec] [dec]} 

Explanation    MPLS packets received on an interface are being dropped as the interface is not setup to handle MPLS. This message may appear when an MPLS application is disabled on a interface, and should disappear when the upstream neighbor has reprogrammed its CEF and MPLS entries.

Recommended Action    If an MPLS application has just been disabled and traffic is flowing, this message is expected and should be ignored. If the message recurs in steady state, the operator should monitor the network for attacks and report the occurrence to Cisco.

MPLS_TE Messages

This section contains MPLS Label Switch Path (LSP) Tunnel messages.

MPLS_TE-2

Error Message    %MPLS_TE-2-ADJ_WALK_ERR: [chars] 

Explanation    An error occurred during a bundle adjacency walk.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_TE-2-BUNDLE_INSERT: [chars][chars] 

Explanation    A request for inserting a traffic engineering tunnel bundle failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_TE-2-UNSUPPORTED_LINK_TYPE: [chars] 

Explanation    An unsupported link type was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MPLS_TE-3

Error Message    %MPLS_TE-3-LSDERROR: [chars]: [chars] [chars] 

Explanation    A traffic engineering request to the label switching database encountered an unexpected condition.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MPLS_TE_AUTOMESH Messages

This section contains MPLS Traffic Engineering (TE) Auto-Tunnel Primary and Backup log and error messages.

MPLS_TE_AUTOMESH-5

Error Message    %MPLS_TE_AUTOMESH-5-AUTOTEMPLATE_HWIDB_DELETE: Failed to delete hwidb 
for Auto-Template %d index %d 

Explanation    The deletion of a hardware interface descriptor block (HWIDB) for an auto-template interface failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MPLS_TE_AUTO_TUN-3

Error Message    %MPLS_TE_AUTO_TUN-3-UNAVAILABLE: Unexpected data structure access. %s 
unlocks with count %u, but expected %u (%u failure%s). 
MPLS_TE_AUTO_TUN_STD_CONFIRM 

Explanation    MPLS_TE_AUTO_TUN_STD_LOCK_EXPLANATION

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_TE_AUTO_TUN-3-UNAVAILABLE: Unexpected data structure access. %s 
unlocks with count %u, but not locked (%u failure%s). MPLS_TE_AUTO_TUN_STD_CONFIRM 

Explanation    MPLS_TE_AUTO_TUN_STD_LOCK_EXPLANATION

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_TE_AUTO_TUN-3-UNAVAILABLE: Unexpected data structure access. 
Non-zero lock count %u when %s locks (%u failure%s). MPLS_TE_AUTO_TUN_STD_CONFIRM 

Explanation    MPLS_TE_AUTO_TUN_STD_LOCK_EXPLANATION

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MPLS_TE_AUTO_TUN-4

Error Message    %MPLS_TE_AUTO_TUN-4-UNAVAILABLE: Removing existing auto tunnels may 
have failed.%s%s MPLS_TE_AUTO_TUN_STD_CONFIRM Use show running-config to confirm 
expected configuration. Repeat CLI configuration as needed. 

Explanation    The MPLS Traffic Engineering Auto-Tunnel software detected a possible problem removing existing automatic tunnels. It may be necessary to repeat the CLI action that caused the removal and reconfiguration of automatic tunnels.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MPLS_TE_LM Messages

This section contains MPLS TE Link Management messages.

MPLS_TE_LM-3

Error Message    %MPLS_TE_LM-3-LSP_BAD_ENCODING_TYPE: LSP [chars] requesting Encoding 
Type [[chars]] that is unsupported on interface [chars]. 

Explanation    The indicated TE LSP, routed on the indicated interface, requested an encoding type that is unsupported on the interface. The requested value appears in the Generalized Label Request.

Recommended Action    Verify that the head end originating the TE LSP has a Generalized Label Request that is specifying an encoding type acceptable to the interface in question. If not, alter the head end configuration to request an LSP with an appropriate value, or cause the LSP to be routed on a different interface. If this problem still persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Also provide a topology diagram showing the hops in the LSP, marking each hop with the vendor and software, and identify which hop is the Cisco IOS device issuing the error message.

Error Message    %MPLS_TE_LM-3-LSP_BAD_GPID: LSP [chars] requesting G-PID [[chars]] 
that is unsupported on interface [chars][chars]. 

Explanation    The indicated TE LSP, routed on the indicated interface, requested a (Generalized) Payload Identifier unsupported on the interface. The requested value appears in the Label Request and Generalized Label Request.

Recommended Action    Verify that the head end originating the TE LSP has a Label Request that is specifying a PID acceptable to the interface in question. If not, one possibility is to alter the head end configuration to request an LSP with an appropriate value. Alternatively, if this error is generated at the penultimate hop of an LSP where the endpoint is advertising an implicit-null label (penultimate hop popping is in use), alter the endpoint to advertise an explicit-null label. If this problem still persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Also provide a topology diagram showing the hops in the LSP, marking each hop with the vendor and software, and identify which hop is the Cisco IOS device issuing the error message.

Error Message    %MPLS_TE_LM-3-LSP_BAD_SWITCHING_TYPE: LSP [chars] requesting 
Switching Type [[chars]] that is unsupported on interface [chars]. 

Explanation    The indicated TE LSP, routed on the indicated interface, requested a Switching Type that is unsupported on the interface. The requested value appears in the Generalized Label Request.

Recommended Action    Verify that the head end originating the TE LSP has a Generalized Label Request that is specifying a Switching Type acceptable to the interface in question. If not, alter the head end configuration to request an LSP with an appropriate value, or cause the LSP to be routed on a different interface. If this problem still persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Also provide a topology diagram showing the hops in the LSP, marking each hop with the vendor and software, and identify which hop is the Cisco IOS device issuing the error message.

MPLS_TE_LM-5

Error Message    %MPLS_TE_LM-5-UNAVAILABLE: Clear MPLS TE Link Management counters by 
%s 

Explanation    The MPLS TE Link Management counters have been cleared

Recommended Action    LOG_STD_NO_ACTION

MPLS_TE_PCALC-2

Error Message    %MPLS_TE_PCALC-2-UNAVAILABLE: %s %d 

Explanation    A failure at an attempt to alloc memory was detected

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_TE_PCALC-2-UNAVAILABLE: %s %i %s 

Explanation    Two nodes have the same stable ip address

Recommended Action    Find the system that has the duplicate ip address and configure a different one

Error Message    %MPLS_TE_PCALC-2-UNAVAILABLE: %s %i %s 

Explanation    Two nodes have the same stable router id

Recommended Action    Find the system that has the duplicate router id and configure a different one

Error Message    %MPLS_TE_PCALC-2-UNAVAILABLE: Invalid router id (%i) received from %s 
in fragment %lu 

Explanation    Received an Invalid Router LSA. LSA should not contain a Router id of zero. The cause of this problem may be misconfiguration, memory corruption or unexpected behaviour on a router

Recommended Action    Locate the problem router and check the configuration. To determine what is causing this problem, call your Cisco technical support representative for assistance.

Error Message    %MPLS_TE_PCALC-2-UNAVAILABLE: Router id (%i) received from %s in 
fragment %lu, previously received in fragment %lu 

Explanation    Received Router ID in multiple fragments

Recommended Action    Locate the problem router and contact your Cisco technical support representative for assistance.

MPLS_TE_PCALC-3

Error Message    %MPLS_TE_PCALC-3-UNAVAILABLE: %s %s 

Explanation    An internal inconsistency was detected when an attempt was made to establish handle received lsa for MPLS TE topology database.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_TE_PCALC-3-UNAVAILABLE: %s 

Explanation    An internal inconsistency was detected when an attempt was made to establish an MPLS TE tunnel using the MPLS TE path calculation subsystem.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_TE_PCALC-3-UNAVAILABLE: pcalc_system_id_size == 0 

Explanation    An internal inconsistency was detected when an attempt was made to initialize the MPLS TE path calculation system id before the system_id size is known.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MPLS_VPN_HA Messages

This section contains MPLS HA messages for checkpointing label bindings.

MPLS_VPN_HA-3

Error Message    %MPLS_VPN_HA-3-CF_GEN_ERROR: [chars] 

Explanation    A general error occurred related to the MPLS VPN HA client CF.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_VPN_HA-3-CLIENTREG: [chars] 

Explanation    The MPLS VPN HA failed to register to CF.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_VPN_HA-3-DBOPERATION: [chars] RD [chars], [IP_address]/[dec], 
label [dec] 

Explanation    An error occurred related to an MPLS VPN HA checkpoint database operation.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_VPN_HA-3-SIZEMISMATCH: Label table size ([dec]) mismatch, get 
label tableid failed. 

Explanation    A mismatch has been detected in the table size of the MPLS VPN HA facility.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MPLS_VPN_HA-7

Error Message    %MPLS_VPN_HA-7-LABELFREE: [chars] [dec] 

Explanation    The MPLS VPN label manager failed to free a label.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_VPN_HA-7-MALLOCFAIL: [chars] 

Explanation    The MPLS VPN HA facility failed to allocate memory.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_VPN_HA-7-XMITFAIL: [chars], message seq no [dec], current seq no 
[dec] 

Explanation    The MPLS VPN label manager has failed to deliver a message.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MPLS_VPN_ISSU Messages

This section contains MPLS VPN ISSU client messages.

MPLS_VPN_ISSU-3

Error Message    %MPLS_VPN_ISSU-3-CF_ERR: [chars] [hex] 

Explanation    An error occurred related to the MPLS VPN ISSU client CF.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_VPN_ISSU-3-GENERR: [chars] 

Explanation    An error occurred related to the MPLS VPN ISSU client.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPLS_VPN_ISSU-3-ISSU_RC_ERR: [chars] [chars] 

Explanation    An error occurred related to the MPLS VPN ISSU client.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MPOA-3

Error Message    %MPOA-3-UNAVAILABLE: %s 

Explanation    A software error has occurred in the multiprotocol-over-ATM server (MPS) software.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPOA-3-UNAVAILABLE: %s 

Explanation    A software error has occurred in the multiprotocol-over-ATM client (MPC) software.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPOA-3-UNAVAILABLE: %s 

Explanation    A software error has occurred in the multiprotocol-over-ATM subsystem.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MPOA-4

Error Message    %MPOA-4-UNAVAILABLE: %s 

Explanation    This is a non-fatal warning from the multiprotocol-over-ATM client (MPC) software, probably the result of an incorrect configuration or operator command. Details about the warning are included in the message.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MPOA-4-UNAVAILABLE: %s 

Explanation    This is a non-fatal warning from the multiprotocol-over-ATM server (MPS) software, probably the result of an incorrect configuration or operator command. Another possible but less likely cause could be an internal software error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MPOA-5

Error Message    %MPOA-5-UNAVAILABLE: %s 

Explanation    A multiprotocol-over-ATM entity was brought up or down. This is only a status message.

Recommended Action    LOG_STD_NO_ACTION

Error Message    %MPOA-6-UNAVAILABLE: %s 

Explanation    This is a multiprotocol-over-ATM client (MPC) status/information message

Recommended Action    LOG_STD_NO_ACTION

Error Message    %MPOA-6-UNAVAILABLE: %s 

Explanation    This is a multiprotocol-over-ATM server (MPS) status/information message

Recommended Action    LOG_STD_NO_ACTION

MRIB_PROXY Messages

This section contains Multicast Routing Information Base proxy (MRIB_PROXY) messages.

MRIB_PROXY-2

Error Message    %MRIB_PROXY-2-MRIB_LC_CREPRC_FAILED: LC in slot [dec] failed to create 
a required process. 

Explanation    The line card could not create a process to perform delayed IPC initialization. The MFIB will not be started on this line card.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MRIB_PROXY-2-MRIB_LC_FAILED_GET_IPC: LC failed allocating IPC buffer 
which may lead to data loss or inconsistent MFIB states, slot = [dec] 

Explanation    The line card has failed in allocating an interprocessor communication buffer.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message    %MRIB_PROXY-2-MRIB_LC_FAILED_IDB_MAP: LC failed in mapping interface 
number [dec] 

Explanation    The line card failed in mapping an interface from the global representation to the local one.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MRIB_PROXY-2-MRIB_LC_FAILED_IPC_ACK: RP failed in getting Ack for IPC 
message of type = [dec], status = [dec], error = [chars] 

Explanation    The route processor has failed to get IPC acknowledgement.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MRIB_PROXY-2-MRIB_LC_FAILED_IPC_OPEN: LC in slot [dec] failed to open 
IPC port to RP, error = [chars] 

Explanation    The line card has failed to open an IPC port towards the route processor.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MRIB_PROXY-2-MRIB_LC_FAILED_SEND_LC_READY: LC in slot [dec] failed to 
send LC ready to RP, error = [chars] 

Explanation    The line card has failed to send a ready message to the route processor.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MRIB_PROXY-2-MRIB_LC_FETCH_FAIL: LC in slot [dec] failed to send an 
RPC fetch request to the RP: [chars] 

Explanation    The line card attempted to read mroute updates from the route processor but the RPC request failed. The line card MFIB state may now be inconsistent or frozen.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MRIB_PROXY-2-MRIB_LC_READY_NOIPC: LC failed allocating IPC buffer to 
send LC ready, slot = [dec] 

Explanation    The line card has failed to allocate an interprocessor communication buffer to send the ready message.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message    %MRIB_PROXY-2-MRIB_LC_UPDATE_IGNORED: LC in slot [dec] ignored one or 
more mroute updates 

Explanation    The line card ignored one or more mroute updates because the buffer containing them failed a sanity check. The line card MFIB state may now be inconsistent.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MRIB_PROXY-2-MRIB_RP_FAILED_GET_IPC: RP failed allocating IPC buffer 
which may lead to data loss or inconsistent MFIB states 

Explanation    The route processor has failed to allocate an interprocessor communication buffer.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MRIB_PROXY-2-MRIB_RP_FAILED_IDB_MAP: RP failed in mapping interface 

Explanation    The route processor failed to map an interface from the global representation to the local one, or vice versa.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MRIB_PROXY-2-MRIB_RP_FAILED_IPC_ACK: LC failed in getting Ack for IPC 
message of type = [dec], status = [dec], error = [chars] 

Explanation    The line card has failed to get an IPC acknowledgement.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MRIB_PROXY-2-MRIB_RP_FAILED_IPC_CREATE: RP failed in creating IPC 
port, error = [chars] 

Explanation    The route processor failed to create an MFIB interprocess communications port.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MRIB_PROXY-2-MRIB_RP_FAILED_LC_DIST_MODE_INIT_PROC: RP failed in 
creating distribute mode init process for a linecard, slot = [dec] 

Explanation    The route processor failed to create a distribute mode initialization process for a line card.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MRIB_PROXY-2-MRIB_RP_FAILED_LC_PORT_INFO: RP failed in creating 
linecard port info for distributed mode, slot = [dec] 

Explanation    The route processor failed to create line card port information for distributed mode.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MRIB_PROXY-2-MRIB_RP_FAILED_LC_PORT_OPEN: RP failed in opening 
linecard port info for distributed mode, slot = [dec] 

Explanation    The route processor failed to open line card port information for distributed mode.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MRIB_PROXY-2-MRIB_RP_FAILED_RPC_REPLY: RP failed in sending [chars] 
reply to a linecard in slot = [dec], IPC error = [chars]. This is normal after 
linecard removal or reset. At other times, data loss or mroute state inconsistency 
may result. 

Explanation    The route processor has failed in sending a remote procedure call reply to a line card. This is normal after line card removal or reset. At other times, data loss or mroute state inconsistency may result.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MROUTE Messages

This section contains MROUTE messages.

MROUTE-2

Error Message    %MROUTE-2-RADIXINIT: Error initializing IP multicast radix for %i 

Explanation    Insufficient memory is available to initialize the IP multicast routing table.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MROUTE-3

Error Message    %MROUTE-3-IGMP_LATE_PROCESS_ERR: IGMP process is not up yet 

Explanation    An error occured accessing IGMP process watched queue

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-3-IGMP_NOT_FOUND: IGMP group [IP address] to delete from 
interface [chars] not found in VRF [chars] 

Explanation    An inconsistency in maintaining the IGMP cache occurred. The group to be deleted from the interface could not be found in the IGMP cache for the VRF. [IP address] is the IP address in the IGMP group, the first [chars] is the interface, and the second [chars] is the VRF.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-3-IGMP_TWHEEL_INIT_ERR: Error trying to initialize the IGMP 
timer wheel 

Explanation    An error occurred during the initialization of a timer wheel.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-3-IGMP_WAVL_ERROR: IGMP wavl [chars] failed for group 
[IP_address] in interface [chars] 

Explanation    The addition/deletion of igmp group in wavl tree failed.

Recommended Action    Collect show tech ipmulticast command output. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %MROUTE-3-MIDB_QUEUE_ERR: Interface %s not in (%i, %i) 

Explanation    The MIDB has the highest expiration timer but was not in the MDB->MIDB.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-3-NO_PIM_NBR: There is no PIM neighbor on this IDB: [chars] 

Explanation    There is no PIM neighbor on the specified IDB. The most probable cause of this error is that PIM is not configured correctly on this interface or on interfaces of the next-hop routers.

Recommended Action    Check PIM configurations on local and neighbor routers. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-3-RECUR_ROUTE_DEPTH_ERR: Recursive route lookup has reached 
its max depth for: [IP_address] 

Explanation    The recursive route lookup has reached its predefined maximum depth limit.

Recommended Action    If possible, reduce the number of rounds of next-hop lookup needed for the network address in question. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-3-ROUTECOUNT_ZERO: Multicast route count reached zero 

Explanation    The running count of multicast routes reached zero when it should be non-zero.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-3-TWHEEL_DELAY_ERR: Exceeded maximum delay (%d ms) requested: 
%d 

Explanation    An attempt was made to schedule a function with a higher delay than the maximum allowed. The function will be scheduled using the maximum delay possible.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-3-TWHEEL_ERR: Timer wheel internal error 

Explanation    A timer wheel internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-3-TWHEEL_INIT_ERR: Trying to re-initialize an already 
initialized timer wheel 

Explanation    An error occurred while intializing a timer wheel.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-3-TWHEEL_INSERT_ERR: An error occured after inserting or 
executing a timer wheel event 

Explanation    An error occurred after inserting or executing a timer wheel event.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-3-TWHEEL_INT_ERR: Timer wheel error at interrupt level %d 

Explanation    A timer wheel internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-3-TWHEEL_SLOT_ERR: Timer wheel event:%x slot:%d func:%x 
unequal to exec slot: %d 

Explanation    The timer wheel event has an inconsistent slot number.

Recommended Action    Enter the clear ip mroute command to delete entries from the IP multicast routing table. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-3-WAVLINIT: Could not initialize WAVL tree for (%i,%i) 

Explanation    The WAVL tree could not be initialized, so the system canot search for Multicast Interface Data Blocks (MIDBs).

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MROUTE-4

Error Message    %MROUTE-4-INCONSISTENT_IDB_TABLEID: PIM detected inconsistency in 
table-id information on [chars]. 

Explanation    The PIM has detected that the interface table ID value is not the same as the value maintained by the multicast code.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-4-MROUTELIMIT: Exceeded multicast limit for group %i, source 
%i on interface %s 

Explanation    The allowed number of multicast routes having the incoming or outgoing interface reached the limit specified by a configured access list. New routes cannot be added unless the interface configuration is changed.

Recommended Action    If multicast traffic over the interface is of any priority among the traffic carried by this router, then enter the ip multicast limit interface command to increase the number of multicast routes. Otherwise, no action is required. Enter the debug ip mroute limit command or the show ip multicast limit command to learn which multicast interface limit was exceeded.

Error Message    %MROUTE-4-MTU_MISMATCH: WARNING: With IP multicast enabled, interfaces 
which transmit traffic from larger to smaller MTU interfaces may not be hardware 
switched due to fragmentation. A degradation in performance may occur. 

Explanation    With IP multicast enabled, interfaces that transmit traffic from larger to smaller MTU interfaces may not be hardware switched due to fragmentation. A degradation in performance may occur.

Recommended Action    Set the MTU values on all interfaces to be identical.

Error Message    %MROUTE-4-RADIXDELETE: Error trying to delete multicast route entry 
%i/%d for %i (expected %#x, got %#x) 

Explanation    A route could not be deleted from the routing table.

Recommended Action    Enter the clear ip mroute command to delete entries from the IP multicast routing table. Determine whether the router is low on memory. If the problem recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-4-RADIXINSERT: Error trying to add multicast route entry %i/%d 
for %i (expected %#x, got %#x) 

Explanation    A route could not be inserted into the routing table.

Recommended Action    Enter the clear ip mroute command to delete entries from the IP multicast routing table. Determine whether the router is low on memory. If the problem recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MROUTE-4-REGISTER_SOURCE_CONFIG: Removing pim register source 
configuration for [chars] 

Explanation    The register source interface was deleted, or its IP address was removed, or its VRF forwarding was changed.

Recommended Action    Check the ip pim register-source configuration.

Error Message    %MROUTE-4-ROUTELIMIT: Current count of %u exceeds multicast 
route-limit of %d 

Explanation    The number of multicast routes equals the configured maximum allowed. New routes cannot be added unless the configuration is changed.

Recommended Action    If multicast traffic is of any priority among the traffic carried by this router, then use the ip multicast route-limit command to increase the number of multicast routes. Otherwise, no action is required.

Error Message    %MROUTE-4-ROUTELIMIT_ATTEMPT: Attempt to exceed multicast route-limit 
of [dec] 

Explanation    The number of multicast routes equals the configured maximum allowed. New routes cannot be added unless the configuration is changed.

Recommended Action    If multicast traffic is of any priority among the traffic carried by this router, then enter the ip multicast route-limit command to increase the number of multicast routes. Otherwise, no action is required.

Error Message    %MROUTE-4-ROUTELIMITWARNING: multicast route-limit warning (curr %u 
threshold %u) 

Explanation    The number of multicast routes reached the configured percentage of the multicast route-limit.

Recommended Action    Increase the multicast route-limit.

Error Message    %MROUTE-4-RPF_LOOKUP_LOOP: RPF route lookup loop for %i, route %i/%d 

Explanation    A routing loop exists, possibly caused by routers reverse path forwarding to different tables .

Recommended Action    Check the routing tables used for reverse path forwarding (RPF).

MROUTE-6

Error Message    %MROUTE-6-LARGE_TWHEEL_DELAY: Exceeded maximum delay (%d ms) 
requested: %d 

Explanation    An attempt was made to schedule a function with a higher delay than the maximum allowed. The function will be scheduled using the maximum delay possible minus a small delay offset.

Recommended Action    Check whether a large IGMP query-interval is set. Some timers may refresh periodically to allow for the large delay.

MSC100_SPA_CC Messages

This section contains Cisco 7304 SPA carrier card messages.

MSC100_SPA_CC-0

Error Message    %MSC100_SPA_CC-0-FPGA_BAY_ERROR_EXCEED_LIMIT: [chars] detected 
[chars] exceed limit ([dec]) (hardware-status = [hex]) 

Explanation    A critical FPGA error was detected on the SPA or carrier card for the specified subslot. The SPA in this subslot has been disabled.

Recommended Action    Try to reactivate the card using the hw-module subslot slot-number/subslot-number start command. If the error persists, enter the show diag slot-number command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show diag slot-number output, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MSC100_SPA_CC-0-FPGA_ERROR: [chars] Slot [dec]: Hardware error 
detected [[chars]] 

Explanation    A critical FPGA error was detected on the carrier card. The carrier card is deactivated and then an automatic recovery is initiated. If a similar error occurs more than five times within an hour, the carrier card is deactivated.

Recommended Action    If the line card is no longer automatically reactivating, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show diag slot-number output, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MSC100_SPA_CC-0-FPGA_ERROR_EXCEED_LIMIT: [chars] Slot [dec] detected 
[chars] exceed limit ([dec]) (hardware-status = [hex]) 

Explanation    A critical FPGA error was detected on the carrier card. The carrier card is deactivated and then an automatic recovery is initiated. If a similar error occurs more than five times within an hour, the carrier card is deactivated.

Recommended Action    If the line card is no longer automatically reactivating, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show diag slot-number output, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MSC100_SPA_CC-0-MISSING_RP_FPGA_SUPPORT: The 7304-MSC-100 in slot 
[int] has been deactivated because the RP FPGA requires an upgrade. 

Explanation    The MSC-100 SPA carrier card in the specified slot requires a particular version of the RP FPGA. The MSC-100 will be deactivated until this FPGA incompatibility is addressed.

Recommended Action    Enter the upgrade fpga all command to upgrade the RP FPGA. After upgrading the RP FPGA, reactivate the MSC-100 by removing and reinserting the MSC-100.

MSDP Messages

This section contains Multicast Source Discovery Protocol (MSDP) messages.

MSDP-3

Error Message    %MSDP-3-DNS_ERROR: DNS lookup time out. DNS lookup for ssm mapping will 
be disabled for 60 sec 

Explanation    DNS source lookup timeout. DNS server not respond to the DNS query, this may be due to DNS server is down. DNS lookup will be stopped for next 60 sec.

Recommended Action    Disbale DNS ssm mapping till the DNS server come up. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %MSDP-3-NO_RPF_NODE: SA message could not be sent to peer [IP_address]. 
Expecting RPF node with host address [IP_address] but found node with host 
[IP_address] in the rpf tree. 

Explanation    The reverse path forwarding (RPF) node could not be found while sending a Source-Active (SA) message to the peer. The SA will not be sent in this period.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MSDP-4

Error Message    %MSDP-4-PKT_TOO_BIG: Message size violation on %u-byte packet from %i, 
discarded 

Explanation    A message larger than the maximum MSDP message size was received. This message could also indicate an internal error.

Recommended Action    Obtain the manufacturer and the version information of the router that sent the oversize packet. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show version commands and your pertinent troubleshooting logs.

Error Message    %MSDP-4-SA_LIMIT: SA from peer %i, RP %i for (%i, %i) exceeded sa-limit 
of %d 

Explanation    The number of MSDP SAs exceeds the configured maximum number. SA cache entries cannot be added unless the configuration is changed.

Recommended Action    If the MSDP SAs come from legitimate sources or RPs, then enter the ip msdp sa-limit command to increase the number of SA entries allowed from the subject peer. Otherwise, no action is required.

MSDP-5

Error Message    %MSDP-5-PEER_IS_SELF: Peering with self (%i) 

Explanation    Multicast Source Discovery Protocol (MSDP) on this device is peering with itself.

Recommended Action    Check the address of the intended MSDP peer.

Error Message    %MSDP-5-PEER_UPDOWN: Session to peer %i going %s 

Explanation    A session to an MSDP peer going up or down.

Recommended Action    Determine whether the router is low on memory.

Error Message    %MSDP-5-PEER_IS_SELF: Peering with self ([IP_address]) 

Explanation    MSDP peering with ourselves

Recommended Action    Check the address of the MSDP peer.

MSPI-1

Error Message    %MSPI-1-UNAVAILABLE: MSPI-bad configuration, %s 

Explanation    A configuration error was detected.

Recommended Action    Add or fix the Dial Peer configuration

Error Message    %MSPI-1-UNAVAILABLE: msgtxt_nomemory 

Explanation    The requested operation could not be accomplished because of a low memory condition.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

MSPI-2

Error Message    %MSPI-2-UNAVAILABLE: MSPI-Internal software error, cid=%d, %s 

Explanation    An internal software error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MSPI-2-UNAVAILABLE: MSPI-bad context pointer, %s 

Explanation    A bad context pointer was passed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MSPI-4

Error Message    %MSPI-4-UNAVAILABLE: MSPI- Bad message received: %s 

Explanation    An unexpected message was received.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MSPI-4-UNAVAILABLE: MSPI- Can't connect to the SMTP server, cid=%d, %s 

Explanation    No connection was created to the specified SMTP server.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MSPI-4-UNAVAILABLE: MSPI- Could notsend data to the SMTP server, 
cid=%d, %s 

Explanation    A connection was made to the SMTP server, but no data can be sent.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MSPI-4-UNAVAILABLE: SMTP- failed %s, %d 

Explanation    A connection attempt to a remote mail server was not successful. This unexpected behavior.

Recommended Action    LOG_STD_NO_ACTION

MSPI-6

Error Message    %MSPI-6-UNAVAILABLE: SMTP- opening %s, %d 

Explanation    A connection attempt ...

Recommended Action    LOG_STD_NO_ACTION

MSFC2 Messages

This section contains Multilayer Switch Feature Card 2 (MSFC2) messages.

MSFC2-3

Error Message    %MSFC2-3-IDB_INCORRECT_UNTHROTTLE_VECTOR: attempting to throttle idb 
[hex] ([chars]) with enable vector [hex] 

Explanation    An invalid interface enable vector was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MSFC2-3-TOOBIG: Attempt to send giant packet on [chars] ([dec] bytes 
from [hex], max allowed [dec])

Explanation    An attempt was made to send an oversized packet. This message typically appears when the Layer 3 switch is not fragmenting packets with a message size larger than 1500 bytes.

Recommended Action    Increase the interface MTU size.

MTRIE Messages

This section contains MTRIE messages.

MTRIE-4

Error Message    %MTRIE-4-MTRIECORRUPTLEAF: [IP_address]/[dec] - [chars] 

Explanation    An internal software error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MTRIE-4-MTRIELEAFOPFAIL: [IP_address]/[dec] - [chars] 

Explanation    An internal software error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MTRIE-4-PLACEALLOC: Failed to allocate place holder 

Explanation    An internal software error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MUESLIX Messages

This section contains Mx serial ASIC messages.

MUESLIX-1

Error Message    %MUESLIX-1-UNAVAILABLE: %s: %s%s: 0x%08x, 0x%08x 

Explanation    Pull the info from the port adaptor to show what error caused the STOPFAIL/STARTFAIL problem.

Recommended Action    Enable 'debug serial mueslix' debug command. Then collect the 'show tech' and 'show log' information and send them to the technical support representative. After that you can disable the 'debug serial mueslix' command.

Error Message    %MUESLIX-1-UNAVAILABLE: %s: Start Failed at %s 

Explanation    The Mueslix serial interface is not responding to commands used to initialize it.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MUESLIX-1-UNAVAILABLE: %s: Stop Failed at %s 

Explanation    The Mueslix serial board failed to respond to a request to disable an interface.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MUESLIX-1-UNAVAILABLE: %s:Link is brought %s due to clock rate change, 
threshold configured = %u, received clock rate = %u 

Explanation    The received clock rate is changed from below the threshold configured to above or vice versa..

Recommended Action    Check the received clock rate from the provider end, if the clock rate falls below the threshold configured

Error Message    %MUESLIX-1-UNAVAILABLE: MUESLIX slot %d: Init Failed at %s 

Explanation    The Mueslix serial board failed to complete hardware initialization.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MUESLIX-1-UNAVAILABLE: Mueslix microcode down load failed. 

Explanation    The Mueslix serial hardware failed. Hardware could not download microcode into mueslix chip.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MUESLIX-1-UNAVAILABLE: Mx serial (bay %d), Init Failed at %s 

Explanation    The Mx serial port adaptor failed to complete hardware initialization.

Recommended Action    Try to reseat the PA properly in the system slots. If the error still happens, then verify for the hardware failure including the 7200 chasis in case of 7200 or vip in case of 7500 and the PA as this error will come only if there is a failure in hardware.

Error Message    %MUESLIX-1-UNAVAILABLE: Mx serial (bay %d): PA down load failed 

Explanation    The Mx serial hardware failed. It could not download its operational microcode.

Recommended Action    Try to reseat the PA properly in the system slots. If the error still happens, then verify for the hardware failure including the 7200 chasis in case of 7200 or vip in case of RSP and the PA as this error will come only if there is a failure in hardware.

Error Message    %MUESLIX-1-UNAVAILABLE: Mx serial, %s Start Failed at %s 

Explanation    A software or hardware error occurred. The Mx microcode is not responding to the enable command used to restart the serial interface

Recommended Action    Enable 'debug serial mueslix' debug command. Then collect the 'show tech' and 'show log' information and send them to the DE team or CSE team. After that you can disable the 'debug serial mueslix' command.

Error Message    %MUESLIX-1-UNAVAILABLE: Mx serial, %s Stop Failed at %s 

Explanation    A software or hardware error occurred. The Mx microcode is not responding to the disable command used to stop the serial port.

Recommended Action    Enable 'debug serial mueslix' debug command. Then collect the 'show tech' and 'show log' information and send them to the technical support representative. After that you can disable the 'debug serial mueslix' command.

Error Message    %MUESLIX-1-UNAVAILABLE: Mx serial: %s TPU halted: cause 0x%2x status 
0x%08x shadow 0x%08x 

Explanation    The Mx serial firmware is not in sync with the driver.

Recommended Action    This conditions will clear by itself. Enable 'debug serial mueslix' debug command. Then collect the 'show tech' and 'show log' information and send them to the DE team or CSE team. After that you can disable the 'debug serial mueslix' command.

MUESLIX-3

Error Message    %MUESLIX-3-ERROR: %s 

Explanation    General error information.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MUESLIX-3-UNAVAILABLE: %d packet buffer, pak=0x%x 

Explanation    A software or hardware error occurred. The Mx serial driver detected that the transmit ring is in an inconsistent and unrecoverable state.

Recommended Action    Enable 'debug serial mueslix' debug command. Then collect the 'show tech' and 'show log' information and send them to the DE team or CSE team. After that you can disable the 'debug serial mueslix' command.

Error Message    %MUESLIX-3-UNAVAILABLE: %s 

Explanation    General error information.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MUESLIX-3-UNAVAILABLE: Mx serial (bay %d): Device reported %#x 

Explanation    The system hardware failed. A non-Mx serial device pointed at the Mx serial software.

Recommended Action    Check the system configuration for the failure in the bay number that is reported in the error message. If it is not a mueslix based PA, then contact the appropriate component to which that PA belongs. If it is a mueslix based PA, then try to reseat the PA once agian and if the error still comes, then collect the 'show tech' and 'show log' information at the time of this problem and send it to the technical support representative

Error Message    %MUESLIX-3-UNAVAILABLE: Mx serial (bay %d): Interface found: %d 

Explanation    The system couldn't able to recognize all the Mueslix devices that are there on the system

Recommended Action    Try to reseat the PA properly in the system slots. If the error is still happening, then verify for the hardware failure including the 7200 chasis in case of 7200 or vip in case of RSP and the PA as this error will come only if there is a failure in hardware.

Error Message    %MUESLIX-3-UNAVAILABLE: Unit %d, buffer ownership error, pak = 0x%x 

Explanation    The Mueslix serial driver detected that the transmit ring is in an inconsistent state.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Recommended Action    representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MUESLIX-4

Error Message    %MUESLIX-4-UNAVAILABLE: %s %s 

Explanation    User has changed the dsu bandwidth using DS3 remote management commands. This won't change the user configured dsu bandwidth

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

MVR_RP Messages

Error Message    %MVR_RP-3-OPER_PORT_SET_FAILED: MVR port operational type setting 
failed. Reason: %d 

Explanation    MVR source/receiver port operational type setting on SP failed because of failure on SP or ICC failure.

Recommended Action    Unconfigure MVR type from this switchport and configure it back

Error Message    %MVR_RP-6-RCVR_ACCESS_PORTMODECHNG: %s MVR type receiver on %s, this 
access port %s MVR vlan 

Explanation    MVR type reciever should not be configured on a MVR vlan port. Since this port is configured as dynamic auto/desirable and due to mode change in the neighboring switch the operational switchport mode on this switch has become access and the corresponding vlan is MVR vlan

Recommended Action    Either unconfigure MVR type receiver from this switchport or change the access vlan to non-MVR vlan

Error Message    %MVR_RP-6-RCVR_TRUNK_PORTMODECHNG: %s MVR type receiver on %s, MVR 
type receiver should not be configured on trunk ports 

Explanation    MVR type reciever should not be configured on a trunk port. Since this port is configured as dynamic auto/desirable and due to mode change in the neighboring switch the operational switchport mode on this switch has become trunk, MVR type receiver should be disabled

Recommended Action    Either unconfigure MVR type receiver from this switchport or change the mode to access and vlan to non-MVR vlan

Error Message    %MVR_RP-6-SRC_ACCESS_PORTMODECHNG: %s MVR type source on %s, this 
access port %s MVR vlan 

Explanation    MVR type source should not be configured on a non-MVR vlan port. Since this port is configured as dynamic auto/desirable and due to mode change in the neighboring switch the operational switchport mode on this switch has become access and the corresponding vlan is non-MVR

Recommended Action    Either unconfigure MVR type source from this switchport or change the access vlan to MVR vlan

Error Message    %MVR_RP-6-SRC_TRUNK_PORTMODECHNG: %s MVR type source on %s, this trunk 
port allowed vlans %s MVR vlan 

Explanation    MVR type source should not be configured on a non-MVR vlan port. Since this port is configured as dynamic auto/desirable and due to mode change in the neighboring switch the operational switchport mode on this switch has become trunk and the corresponding vlan range does not contain MVR vlan

Recommended Action    Either unconfigure MVR type source from this switchport or change the trunk allowed vlan range to include MVR vlan

MVRP Messages

This section contains Multicast VLAN Registration Protocol (MVRP) messages.

MVRP-3

Error Message    %MVRP-3-ADD_REGISTRY_FAILED: MVRP subsystem fails to add callback 
function %s 

Explanation    Another subsystem has mistakenly added its own callback functions. This message is for debugging purposes.

Recommended Action    No action is required.

Error Message    %MVRP-3-ENABLE_FAILED: MVRP can't be enabled because %s 

Explanation    Multicast VLAN Registration Protocol (MVRP) cannot be enabled for the specified reason.

Recommended Action    Take action according to the specified reason. For example, if the failure is due to insufficient memory, add more memory to the system.

Error Message    %MVRP-3-HA_INIT_FAILED: MVRP High Availability subsystem fails to be 
initialized and hence MVRP won't support HA stateful switchover. 

Explanation    The MVRP CF client or the MVRP RF client failed to initialize.

Recommended Action    Enter the show redundancy clients command and the show checkpoint clients command to learn which client was not initialized.

Error Message    %MVRP-3-SUBSYS_INIT_FAILED: MVRP subsystem failed in 
initialization(%s) and MVRP won't function properly. 

Explanation    MVRP could not initialize, probably due to insufficient memory. Other accompanying system messages may provide further information about the failure.

Recommended Action    Enter the show memory summary command to check the memory usage. Contact the TAC with the output of the show memory summary, show version, and show run commands and the associated syslog messages from the time of the problem.

MVRP-6

Error Message    %MVRP-6-MODECHANGE: The operating mode is changed to %s mode on 
interface %s. 

Explanation    As a result of protocol negotiation, the operating mode changed to the specified mode on the specified interface.

Recommended Action    No action is required.

MVRP_CONST Messages

This section contains MVRP messages on Constellation platforms.

MVRP_CONST-3

Error Message    %MVRP_CONST-3-MAC_MATCH_REG_FAILED: Unable to reserve needed MAC match 
register - cannot run MVRP on interfaces of slot %d 

Explanation    Multicast VLAN Registration Protocol (MVRP) attempted to reserve a MAC match register for the slot indicated, but there is no dedicated register or programmable register available. MVRP cannot be activated on interfaces of this card.

Recommended Action    Disable conflicting protocols that use the MAC match register or use a different card type that supports MVRP.

MVRP_CONST-6

Error Message    %MVRP_CONST-6-FEATURE_CONFLICT: Failed to enable MVRP on %s because 
conflicting feature %s is enabled on the interface 

Explanation    MVRP could not be enabled on the given interface because of conflicting features. For example, unknown unicast flood blocking(UUFB) and MVRP cannot be enabled on the same interface.

Recommended Action    If MVRP is required on the interface, enter the show running-config interface command to investigate whether incompatible features are enabled on the interface.

Error Message    %MVRP_CONST-6-MAC_LEARNING: MAC learning on VLAN %s is %s 

Explanation    If only two MVRP ports are forwarding and not pruned in a VLAN, MVRP will disable MAC learning on that VLAN in order to save room in the MAC table, which is a limited system-wide resource.

Recommended Action    No action is required.

Error Message    %MVRP_CONST-6-MAC_LRN_SETTING_FAILED: Failed to %s MAC learning on 
VLAN %s 

Explanation    MVRP failed to enable or disable MAC learning on the given VLAN, probably because MAC learning was already configured on the VLAN by the administrator.

Recommended Action    To determine the status of MAC learning on the VLAN, enter the show mac-address-table learning command.

MVRP_ISSU Messages

This section contains MVRP in-service software upgrade messages.

MVRP_ISSU-2

Error Message    %MVRP_ISSU-2-GET_BUFFER: MVRP ISSU client failed to get buffer for 
message. Error: %d (%s) 

Explanation    The Multicast VLAN Registration Protocol (MVRP) ISSU client was unable to reserve buffer space for building a negotiation message. As a result, the negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.

Error Message    %MVRP_ISSU-2-INIT: MVRP ISSU client initialization failed to %s. 
Error: %d (%s) 

Explanation    The MVRP ISSU client could not be initialized. This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed. Otherwise, a software upgrade or downgrade will result in downtime.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MVRP_ISSU-2-SEND_NEGO_FAILED: MVRP ISSU client failed to send 
negotiation message. Error: %d (%s) 

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

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.

Error Message    %MVRP_ISSU-2-SESSION_NEGO: MVRP ISSU client encountered unexpected 
client nego_done. Error: %d (%s) 

Explanation    The MVRP ISSU client encountered a client negotiation done state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %MVRP_ISSU-2-SESSION_REGISTRY: MVRP ISSU client failed to register 
session information. Error: %d (%s) 

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

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

MVRP_ISSU-3

Error Message    %MVRP_ISSU-3-INVALID_SESSION: MVRP ISSU client does not have a valid 
registered session. 

Explanation    The Multicast VLAN Registration Protocol (MVRP) ISSU client does not have a valid registered session.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %MVRP_ISSU-3-MSG_NOT_OK: MVRP ISSU client 'Message Type %d' is not 
compatible 

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

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message    %MVRP_ISSU-3-MSG_SIZE: MVRP ISSU client failed to get the MTU for 
Message Type %d. Error: %d (%s) 

Explanation    The MVRP ISSU client was unable to calculate the MTU for the specified message. As a result, the MVRP ISSU client is not able to send the message to the standby device.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message    %MVRP_ISSU-3-SESSION_UNREGISTRY: MVRP ISSU client failed to unregister 
session information. Error: %d (%s) 

Explanation    The MVRP ISSU client was unable to unregister session information.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %MVRP_ISSU-3-TRANSFORM_FAIL: MVRP ISSU client %s transform failed for 
'Message Type %d'. Error: %d (%s) 

Explanation    The MVRP ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the MVRP state between the active device and the standby device is not identical.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

MVRP_SWITCH Messages

This section contains MVRP messages on switch platforms.

MVRP_SWITCH-6

Error Message    %MVRP_SWITCH-6-IGNORE_USER_CONFIG: The user configured list of pruned 
VLANs on interface %s is ignored as MVRP will prune VLANs dynamically. 

Explanation    The switchport trunk pruning vlan command is used by VTP pruning to prune VLANs numbered from 1 to 1001 only. This configuration command does not apply to MVRP, which prunes all 4096 VLANs. The command will be ignored.

Recommended Action    No action is required.

Error Message    %MVRP_SWITCH-6-VLAN_CREATED: MVRP created VLANs %s on this device 

Explanation    MVRP has created the specified VLANs. MVRP can create VLANs dynamically if the feature is enabled with the mvrp vlan create command.

Recommended Action    No action is required.

MXT_FREEDM-1

Error Message    %MXT_FREEDM-1-UNAVAILABLE: 8PRI/4T board slot %d: Firmware download 
failed. 

Explanation    Failed to download firmware into 8PRI/4T board

Recommended Action    Power Cycle the router. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MXT_FREEDM-1-UNAVAILABLE: 8PRI/4T board slot %d: Firmware sent a HALT 
interrupt. 

Explanation    Double bus fault occurred in the 8PRI/4T board firmware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MXT_FREEDM-1-UNAVAILABLE: Invalid Shared Memory size detected 

Explanation    Current shared memory present in the box is not supported

Recommended Action    Replace the Shared Memory by the supported configuration. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MXT_FREEDM-1-UNAVAILABLE: PCI-DBUS Bridge in slot %d Failure: %s 

Explanation    Internal error occured in 8PRI/4T board

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

MVR_RP Messages

This section contains Multicast VLAN Registration (MVR) route processor messages.

MVR_RP-3

Error Message    %MVR_RP-3-OPER_PORT_SET_FAILED: MVR port operational type setting 
failed. Reason: [dec] 

Explanation    A failure occurred while setting the MVR source or receiver port operational type on the switch port. The cause was either a failure on the switch port or an ICC failure.

Recommended Action    Unconfigure the MVR type from this switch port and reconfigure it.

MVR_RP-6

Error Message    %MVR_RP-6-RCVR_ACCESS_PORTMODECHNG: [chars] MVR type receiver on 
[chars], this access port [chars] MVR vlan 

Explanation    An MVR type receiver should not be configured on a MVR VLAN port. Because this port is configured as dynamic auto/desirable, and due to a mode change in the neighboring switch, the operational switchport mode on this switch has become access and the corresponding VLAN is an MVR VLAN.

Recommended Action    Either unconfigure MVR type receiver from this switch port or change the access VLAN to a non-MVR VLAN.

Error Message    %MVR_RP-6-RCVR_TRUNK_PORTMODECHNG: [chars] MVR type receiver on 
[chars], MVR type receiver should not be configured on trunk ports 

Explanation    An MVR type receiver should not be configured on a trunk port. Because this port is configured as dynamic auto/desirable, and due to a mode change in the neighboring switch, the operational switch port mode on this switch has become trunk. MVR type receiver should be disabled.

Recommended Action    Either unconfigure MVR type receiver from this switch port or change the mode to access and change the VLAN to a non-MVR VLAN.

Error Message    %MVR_RP-6-SRC_ACCESS_PORTMODECHNG: [chars] MVR type source on [chars], 
this access port [chars] MVR vlan 

Explanation    MVR type source should not be configured on a non-MVR VLAN port. Because this port is configured as dynamic auto/desirable, and due to mode change in the neighboring switch, the operational switch port mode on this switch has become access and the corresponding VLAN is non-MVR.

Recommended Action    Either unconfigure MVR type source from this switch port or change the access VLAN to an MVR VLAN.

Error Message    %MVR_RP-6-SRC_TRUNK_PORTMODECHNG: [chars] MVR type source on [chars], 
this trunk port allowed vlans [chars] MVR vlan 

Explanation    MVR type source should not be configured on a non-MVR VLAN port. Because this port is configured as dynamic auto/desirable, and due to mode change in the neighboring switch, the operational switch port mode on this switch has become trunk and the corresponding VLAN range does not contain the MVR VLAN.

Recommended Action    Either unconfigure MVR type source from this switch port or change the trunk allowed VLAN range to include the MVR VLAN.

MWAM Messages

This section contains Multiprocessor WAN Application Module (MWAM) messages.

Error Message    %MWAM-4-FAILED_FILE_SYNC: Failure creating or synchronizing MWAM 
configuration file to standby: [chars], [chars] 

Explanation    The active supervisor engine has failed to copy an MWAM configuration file from bootflash: to slavebootflash:. The standby supervisor engine will not be up to date with the MWAM configuration files if a switchover occurs.

Recommended Action    Verify that there is space available on the bootflash: and slavebootflash: devices. It may be necessary to compress either or both devices to recover space used by deleted or overwritten files. After taking these actions, a new attempt to synchronize files can be started either by resetting the standby supervisor engine or by configuring no mwam bootflash access followed immediately by mwam bootflash access. If these actions do not resolve the issue, obtain the output from the following commands:

- dir bootflash:
- dir slavebootflash:
- show bootflash:
- show slavebootflash:

If possible, set debug mwam all on the active supervisor engine, and then reset the standby supervisor engine with the hw-module module slot reset command, capturing the debug information that appears on the active supervisor engine console. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %MWAM-4-FAILED_TASK_INIT: Failed to start a required task: [chars], 
[chars] 

Explanation    A necessary process failed to be created.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NATMIB_HELPER Messages

This section contains Network Address Translator (NAT) MIB helper messages.

NATMIB_HELPER-3

Error Message    %NATMIB_HELPER-3-NOCREAT: NATMIB Helper Process not created - NAT MIB 
will not work properly 

Explanation    An attempt to start the NATMIB helper process failed when the NATMIB subsystem was initialized. The NATMIB helper process could not be created. This condition might be caused by a lack of memory.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Reload the system after reconfiguring it.

NBAR Messages

This section contains network-based application recognition (NBAR) messages.

NBAR-1

Error Message    %NBAR-1-UNAVAILABLE: Nodes size mismatch between parsing and 
sending:%s 

Explanation    Failure during the distribution of NBAR graph nodes from the route processor to the linecards. Failure is related to node size changes between parsing and sending phase

Recommended Action    Disable nbar protocols

Error Message    %NBAR-1-UNAVAILABLE: Reached maximum amount of memory allocated for 
stile 

Explanation    This platform allows NBAR to use a limited amount of memory for classification and that amount has been used up because of high traffic conditions.

Recommended Action    Increase amount of memory in router.

Error Message    %NBAR-1-UNAVAILABLE: link-next not NULL when allocated. link-next = %s 

Explanation    An attempt was made to get a link from the free bucket which is pointing to another resource. Links within the free bucket should be NULL, therefore this link is corrupted and should not be used

Recommended Action    Configure the router with the ip nbar resources to allocate a larger initial pool of resources.

Error Message    %NBAR-1-UNAVAILABLE: link-prev not NULL when allocated. link-prev = %s 

Explanation    An attempt was made to get a link from the free bucket which is pointing to another resource. Links within the free bucket should be NULL, therefore this link is corrupted and should not be used

Recommended Action    Configure the router with the ip nbar resources to allocate a larger initial pool of resources.

NBAR-2

Error Message    %NBAR-2-UNAVAILABLE: Failure in the heuristic subsystem of NBAR: %s 

Explanation    Failure during the distribution of NBAR heuristic data structures from the route processor to the linecards.

Recommended Action    Disable heuristic protocols

Error Message    %NBAR-2-UNAVAILABLE: Memory for maintaining state used up 

Explanation    NBAR uses memory to maintain state information about stateful flows. There is a maximum limit on how much memory NBAR can use for this purpose and this limit has been reached.

Recommended Action    Increase memory on platform

Error Message    %NBAR-2-UNAVAILABLE: NBAR resource manager : too many buckets (%d) 

Explanation    NBAR was configured such that the internal data structures needed to maintain stateful protocol information were too large.

Recommended Action    Configure the router with the ip nbar resources with a smaller max-idle time.

Error Message    %NBAR-2-UNAVAILABLE: NBAR resources exhausted 

Explanation    In order to save stateful information on protocols, NBAR must use dynamic resources. These resources have been exhausted.

Recommended Action    Configure the router with the ip nbar resources to allocate a larger initial pool of resources. The default number of initial resources is 10000. Also try configuring a shorter max-idle time.

Error Message    %NBAR-2-UNAVAILABLE: No memory available for %s 

Explanation    An attempt at memory allocation failed.

Recommended Action    Try these actions to remedy the problem: Add memory. Disable some features. Apply filtering to decrease the size of system data structures - the routing table, for example. In general, reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

NETCONF Messages

This section contains network configuration protocol (NETCONF) messages.

NETCONF-3

Error Message    %NETCONF-3-MEMORY: %s 

Explanation    The network configuration protocol (NETCONF) subsystem was unable to reserve the required memory to complete this operation.

Recommended Action    Check the system memory for memory allocation errors. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

NETWORK_CLOCK_SYNCHRONIZATION

Error Message    %NETWORK_CLOCK_SYNCHRONIZATION-4-UNAVAILABLE: Network clock %s PLL 
lost lock - clock source failed. 

Explanation    The clock source has failed.

Recommended Action    If alternate source is available, it will be used.

Error Message    %NETWORK_CLOCK_SYNCHRONIZATION-4-UNAVAILABLE: Network clock source 
initialised to local oscillator. 

Explanation    Warning indicates that network clock used will be internal.

Recommended Action    No action is required.

Error Message    %NETWORK_CLOCK_SYNCHRONIZATION-4-UNAVAILABLE: Network clock source 
transitioned from Priority %d %s %s to Priority %d %s %s 

Explanation    This warning message indicates a change in the clock source.

Recommended Action    No action required.

NETFLOW_AGGREGATION Messages

This section contains NetFlow Aggregation (NETFLOW_AGGREGATION) messages.

NETFLOW_AGGREGATION-3

Error Message    %NETFLOW_AGGREGATION-3-FLOWMASK_CONFLICT: Netflow [chars] cannot set 
the required flowmask 

Explanation    The NetFlow aggregation flow mask conflicts with other features.

Recommended Action    If NetFlow Data Export is configured, increase the size of the NDE flow mask to VLAN full flow by entering the mls flow ip interface-full command, and then reconfigure the NetFlow aggregation scheme. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NETFLOW_AGGREGATION-4

Error Message    %NETFLOW_AGGREGATION-4-NO_TOS_AGGR: Disable hardware switching to 
enable [chars] 

Explanation    NetFlow does not currently support ToS-based aggregation schemes for hardware-switched flows.

Recommended Action    If ToS-based aggregation is required, disable hardware switching.

Error Message    %NETFLOW_AGGREGATION-4-OER_AGG_EXPORT_ERROR: OER Error [chars] 

Explanation    An error occurred in receiving an Optimized Edge Routing (OER) aggregation export packet.

Recommended Action    Disable OER monitor prefix aggregation.

NETFLOW_AGGREGATION-6

Error Message    %NETFLOW_AGGREGATION-6-OER_MLS_LONG_AGING: MLS long aging time 
modified by OER to [dec] 

Explanation    OER modified the long aging time to a value that may be different from the configured value.

Recommended Action    No action is required.

NETWORK_PORT_SATELLITE Messages

This section contains network port satellite messages.

NETWORK_PORT_SATELLITE-3

Error Message    %NETWORK_PORT_SATELLITE-3-PHY_LOCKUP: Repeated phy lockup seen on 
[chars]. Interface will be shut down. 

Explanation    The physical interface has locked up an excessive number of times. To avoid the interface becoming active, and then quickly becoming inactive numerous times (link flapping), the interface has been shut down.

Recommended Action    To reenable the interface, enter the shutdown command, followed by the no shutdown command in interface configuration mode, to shut down and restart the interface.

NETWORK_PORT_SATELLITE-6

Error Message    %NETWORK_PORT_SATELLITE-6-UNAVAILABLE: Transmit lock up is detected in 
%s. This port is adminstratively down. 

Explanation    When the PHY is powered on and off, the MAC cycles from Gigabit to 100, and the port might lock up and stop sending packets. The PHY refers to the physical layer device on the switch, which sends and receives optical signals and provides framing and line integrity.

Recommended Action    Shut down the port by using the shutdown interface configuration command, and bring it back up by using the no shutdown interface configuration command

NETWORK_RF_API Messages

This section contains network redundancy feature API (NETWORK_RF_API) messages.

NETWORK_RF_API-3

Error Message    %NETWORK_RF_API-3-CLIENT_REGISTER_FAIL: Failed to register with 
[chars], rc =[dec] 

Explanation    A redundancy client could not be registered. An internal failure associated with client registration occurred in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure that was detected. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-FAILDECODEDATADESC: Cannot decode data descriptor 
for [chars], descriptor type=[dec] 

Explanation    An internal data descriptor could not be decoded for synchronization for the interface or controller in the run-time module specified in the message output. The failure most likely occurred because of a software error. The descriptor type specified in the message output, if it is a nonzero value, identifies the type of failure. The system state between the active and standby units might not be properly synchronized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-FAILDECODEDATADESCINSTDBY: Cannot decode data 
descriptor in Standby for [chars], descriptor type=[dec] 

Explanation    An internal data descriptor could not be decoded in the standby unit. The message identifies the interface or controller that caused the decoding failure in the standby unit. This interface was encoded in the active unit but could not be decoded in the standby unit. The failure is probably caused by a software error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-FAILENCODEDATADESC: Cannot encode data descriptor 
for [chars], descriptor type=[dec] 

Explanation    An internal data descriptor could not be encoded for synchronization for the interface or controller in the run-time module specified in the message output. The failure most likely occurred because of a software error. The descriptor type specified in the message output identifies the type of failure. The system state between the active and standby units might not be properly synchronized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-FAILSENDMSGTOACTIVE: Failed to send [chars] message 
to active for [chars], [chars] 

Explanation    The specified synchronization message, which is an internal IPC message, could not be sent to the active unit in the specified run-time module. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-FAILSENDMSGTOSTDBY: Failed to send [chars] message 
to standby for [chars], rc=[dec] 

Explanation    The specified synchronization message, which is an internal IPC message, could not be sent to the standby unit in the specified run-time module. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the type of failure. The system state between the active and standby units might not be properly synchronized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-INVALID_CHKPT_STATUS_CODE: Invalid checkpointing 
status code received, rc=[dec] 

Explanation    An invalid checkpoint status code has been detected. An internal status code that is associated with checkpointing was found to be invalid. The return code that is specified in the message output identifies the invalid code that was detected. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-INVALID_MSG_RECEIVED: Invalid [chars] message 
received 

Explanation    A message that is used for state synchronization was not received correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-IPC: [chars] [chars] 

Explanation    An interprocess communication (IPC) error has occurred. Additional details on the cause of the error are specified in the message text on the console or in the system log.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-ISSU_MSG_MTU_INVALID: The ISSU message MTU is 
invalid: [chars] 

Explanation    A message buffer size that is used for state synchronization was found to be invalid. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-ISSU_MSG_TYPE_INCOMPAT: The active and standby ISSU 
message types are incompatible 

Explanation    An incompatible message was used for state synchronization. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-ISSU_REG_SES_INFO: Failed to register ISSU session 
information: [chars] 

Explanation    The system failed to register the ISSU session information required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-ISSU_START_NEGO_SES: Failed to start ISSU session: 
[chars] 

Explanation    The system failed to start the ISSU negotiation session required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-ISSU_TRANSFORM_FAIL: The ISSU message [chars] 
transformation failed: [chars] 

Explanation    A message that is used for state synchronization could not be transformed correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-ISSU_UNREG_SES_INFO: Failed to register ISSU session 
information: [chars] 

Explanation    The system failed to unregister the ISSU session information required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-NO_CHKPT_BUFFER: No checkpointing buffer for 
[chars], rc=[dec] 

Explanation    A message data buffer that is used for state synchronization could not be obtained. An internal data structure could not be allocated for synchronization in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure. The failure most likely occurred because of a software error or a lack of system memory. The system state between the active and standby units might not be properly synchronized.

Recommended Action    If you determine that this condition was caused by a lack of system memory, reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-NO_MSG_BUFFER: No message buffer for [chars] 

Explanation    A message data buffer that is used for state synchronization could not be obtained. An internal data structure could not be allocated for synchronization in the run-time module specified in the message output. The failure most likely occurred because of a software error or a lack of system memory. The system state between the active and standby units might not be properly synchronized.

Recommended Action    If you determine that this condition was caused by a lack of system memory, reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NETWORK_RF_API-3-NO_RESOURCES: [chars] 

Explanation    A run-time module could not obtain the resources that are required to complete a task. The failure most likely occurred because of a software error or a lack of system memory. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.

Recommended Action    If you determine that this condition was caused by a lack of system memory, reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NET_SERV-4

Error Message    %NET_SERV-4-UNAVAILABLE: Unexpected condition: %s 

Explanation    An unexpected condition was detected while performing a services timer operation

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NET_SERV-4-UNAVAILABLE: Unexpected error: %s 

Explanation    An unexpected error occurred while performing a services timer operation

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NETWORK_RF_API-6

Error Message    %NETWORK_RF_API-6-IDB_TRANSITIONS_PENDING: Switchover terminated with 
[dec] transitions pending after there was no transition activity for [dec] seconds 

Explanation    The system terminated the switchover IDB transitioning phase with a number of IDB transitions still pending because no switchover-related IDB transitions were logged during the specified time interval. Some connected routes may experience a temporary loss of traffic.

Recommended Action    No action is required.

NHRP Messages

This section contains Next Hop Resolution Protocol (NHRP) messages.

Error Message    %NHRP-3-TIMERLOOP: Timer process looping 
([dec]/[dec]/[dec]/[dec]/[dec]/[dec]). 

Explanation    The process that handles timer events is looping, possibly on a malfunctioning timer event.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NHRPSNMP Messages

Error Message    %NHRPSNMP-3-TREEINVALID: Setting tree to Invalid State @ - (%d) 

Explanation    NHRP SNMP agent tree is not behaving as excepted.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NHRPSNMP-5-TREERECOVERD: Tree recovered fromInvalid State @ - (%d) 

Explanation    NHRP SNMP agent tree is not behaving as expected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NIM-2

Error Message    %NIM-2-UNAVAILABLE: All hardware addresses have been allocated - 
maximum of %d 

Explanation    An internal software error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NIM-2-UNAVAILABLE: Attempted to manipulate uninitialized ichainQ in 
%s 

Explanation    A software or hardware error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NIM-2-UNAVAILABLE: Couldn't find idb 0x%x in ichainQ in %s 

Explanation    A software or hardware error occurred.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %NIM-2-UNAVAILABLE: Illegal reference to non-existent slot %d 

Explanation    An internal software error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NIM-2-UNAVAILABLE: Illegal reference to non-existent subunit %d in 
slot %d 

Explanation    An internal software error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NIM-2-UNAVAILABLE: Unsupported %s NIM in slot %d 

Explanation    The indicated NIM is not supported on this platform.

Recommended Action    Remove the NIM.

Error Message    %NIM-2-UNAVAILABLE: Unsupported version of %s NIM in slot %d Version 
0x%x 

Explanation    The indicated network interface module (NIM) is not supported because it is not of the correct revision. Certain platforms (Cisco 4500 or Cisco 4700, for example) require some NIMs to be of a minimum rev level.

Recommended Action    Upgrade the NIM to the proper level.

Recommended Action   

NMSP Messages

Error Message    %NMSP-3-INIT_FAIL: NMSP process failed to initialize 

Explanation    NMSP process failed to initialize and cannot accept incoming NMSP messages

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NMSP-3-INIT_SPI: NMSP SPI process %s failed reason %d 

Explanation    NMSP SPI process failed to initialize and cannot forward NMSP messages to WCM

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NP Messages

This section contains Network Processor messages.

NP-2

Error Message    %NP-2-BADREAD: Read failed for [chars] on NP [dec]. 

Explanation    There was a read error on the file during the microcode image load.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %NP-2-HDRCORRUPT: Microcode header has been corrupted, expected [hex], 
got [hex]. 

Explanation    Network Processor microcode appears to be corrupted. This could be due to an already corrupted image or, less likely, a software problem.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %NP-2-INVALID: Corrupted microcode retrieved from the image bundle for 
NP [dec]. 

Explanation    The retrieved microcode appears to be corrupted.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %NP-2-NONEXIST: Could not open or file does not exist [chars] for NP 
[dec]. 

Explanation    There is a possibility that the Network Processor microcode may not be bundled into the image correctly or a software error occurred that prevented locating the microcode.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %NP-2-RESTARTED: NP [dec] restarted. 

Explanation    Network Processor has been restarted, either manually or by a microcode reload, or as a result of an exception.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %NP-2-WRONGHARD: The microcode type does not match, expected [hex], 
got [hex]. 

Explanation    There is a possibility the images has been corrupted or, less likely, an incorrect microcode set is bundled into the image.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %NP-2-WRONGMAGIC: Microcode section contains inalid magic for NP 
[dec]. 

Explanation    Network Processor microcode appears to mismatch the ucode hdr type. This could be due to an already corrupted image or a read error on the file during the downloading on the NP.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

NP-3

Error Message    %NP-3-UNAVAILABLE: %s queue is full for Slot %d, DFC %d, Module %d. 

Explanation    TX queue is full for this module.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP-3-UNAVAILABLE: Control buffer pool could not be created 

Explanation    NextPort driver could not create the control buffer pool required for tx and rx of NP control messages

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP-3-UNAVAILABLE: DFC Reset-Cleared Failed - DFC %d 

Explanation    DFC Reset-Cleared Failed

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP-3-UNAVAILABLE: Message Id %x not supported. 

Explanation    The Nextport does not supported this control message id.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP-3-UNAVAILABLE: NAK Response Received - command 0x%x, result code 
0x%x, msg id 0x%x, session id 0x%x, msg tag 0x%x 

Explanation    A NAK response was sent by the NextPort module.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %NP-3-UNAVAILABLE: Slot %d, DFC %d, Module %d not exist. 

Explanation    No Virtual Console opens for this module.

Error Message    Copy the error message exactly as it appears, and report it to your technical support representative.

NP-5

Error Message    %NP-5-RESTARTEDALL: All NPs have been restarted. 

Explanation    All Network Processors have been restarted, either manually or by a microcode reload, or as a result of an exception.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

NP_BS-2

Error Message    %NP_BS-2-UNAVAILABLE: DFC in slot %d does not have three NP108s! 

Explanation    DFC does not have three NP108s which is an illegal configuration

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_BS-3-UNAVAILABLE: %s 

Explanation    Failed NextPort BootStrap and Crash Monitor Initialization.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_BS-3-UNAVAILABLE: %s 

Explanation    NextPort BootStrap and Crash Monitor Could not allocate memory for internal module database

Recommended Action    No action is required.

Error Message    %NP_BS-3-UNAVAILABLE: %s nonexisting NP module %d/%d/%d 

Explanation    NextPort BootStrap and Crash Monitor detected an internal database error

Recommended Action    No action is required.

Error Message    %NP_BS-3-UNAVAILABLE: Failed to access NextPort module %d/%d/%d crash 
info 

Explanation    NextPort BootStrap and Crash Monitor failed to access crash information

Recommended Action    No action is required.

Error Message    %NP_BS-3-UNAVAILABLE: Invalid NextPort Firmware for %d/%d/%d 

Explanation    NextPort BootStrap and Crash Monitor detected aninvalid NextPort firmware

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_BS-3-UNAVAILABLE: NULL NextPort Firmware pointer for %d/%d/%d 

Explanation    NextPort BootStrap and Crash Monitor detected aNULL NextPort firmware pointer

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_BS-3-UNAVAILABLE: NextPort Module %d/%d/%d control queue creation 
failure 

Explanation    NextPort BootStrap and Crash Monitor detected ancontrol queue creation failure

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_BS-3-UNAVAILABLE: NextPort Module %d/%d/%d detected a module POST 
failure 0x%x 

Explanation    NextPort BootStrap and Crash Monitor detected ana module POST failure

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_BS-3-UNAVAILABLE: NextPort Module %d/%d/%d detected an invalid IDT 

Explanation    NextPort BootStrap and Crash Monitor detected aninvalid IDT

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_BS-3-UNAVAILABLE: NextPort Module %d/%d/%d failed firmware image 
validation 

Explanation    NextPort BootStrap and Crash Monitor detected ana failed NextPort firmware CRC validation

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_BS-3-UNAVAILABLE: NextPort Module %d/%d/%d memory test failed 

Explanation    NextPort BootStrap and Crash Monitor detected a failedNextPort module memory test

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_BS-3-UNAVAILABLE: NextPort module %d/%d/%d failed to respond to 
keepalive message 

Explanation    NextPort BootStrap and Crash Monitor detected a module failed to respond to keepalive message

Recommended Action    No action is required.

NP_BS-6

Error Message    %NP_BS-6-UNAVAILABLE: NextPort module %d/%d/%d Started - %d.%d.%d.%d 

Explanation    NextPort BootStrap and Crash Monitor successfully started module

Recommended Action    No action is required.

Error Message    %NP_BS-6-UNAVAILABLE: NextPort module %d/%d/%d Stopped 

Explanation    NextPort BootStrap and Crash Monitor stopped module

Recommended Action    No action is required.

NP_CLIENT Messages

This section contains NextPort (NP) client messages.

NP_CLIENT-2

Error Message    %NP_CLIENT-2-FATAL: NP Client %s : %s (%d, %d) 

Explanation    NP Client software detected a critical programming error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NP_CLIENT-3

Error Message    %NP_CLIENT-3-ALLEXISTS: NP Client Previously Defined Software Element 
- %s: %s %s 

Explanation    The NP Client has detected a previously defined software element.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_CLIENT-3-INITFAIL: NP Client Initialization Failed - [chars]: 
[chars] [chars] 

Explanation    The NP client could not initialize memory needed to service one or more network processors. This error may indicate that an incompatibility exists between the NP firmware and the associated Cisco IOS image.

Recommended Action    Attempt to reload the Cisco IOS image on the affected card or platform. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_CLIENT-3-INTF: [chars] ([chars]) on [chars] - [chars] 
if_number=[dec] 

Explanation    The interface NP client detected an error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_CLIENT-3-MAXEXCEED: NP Client Max Services Exceeded - [chars]: 
[chars] [chars] 

Explanation    The maximum number of NP client services has been exceeded.

Recommended Action    Change the configuration to reduce the number of services configured. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_CLIENT-3-METADATA: [chars] failed: [chars] [[chars]] [chars] 

Explanation    Processing of the metadata for the specified network processor has failed. The specified network processor will fail to operate.

Recommended Action    Attempt to reload the network processor microcode. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_CLIENT-3-NOMEM: Memory Allocation Failure - [chars]: [chars] 
[chars] 

Explanation    The NP client could not allocate the required memory needed to service one or more network processors.

Recommended Action    This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled by the configuration.
Try to reload the Cisco IOS image on the affected card or platform. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_CLIENT-3-NOTFOUND: NP Client Software Element Not Found - [chars]: 
[chars] [chars] 

Explanation    The NP client could not locate a required software element.

Recommended Action    Attempt to reload the Cisco IOS image on the affected card or platform. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_CLIENT-3-NOTSUP: NP Client Feature Not Supported - [chars]: 
[chars] [chars] 

Explanation    The NP client does not support the specified feature.

Recommended Action    Verify that the correct Cisco IOS image is loaded on the affected card or platform for the configured features. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_CLIENT-3-NPUNKNOWN: NP Client Unsupported NP - [chars]: [chars] 
[chars] 

Explanation    The NP client detected an unsupported NP.

Recommended Action    Verify that the correct Cisco IOS image is loaded on the affected card or platform for the configured features. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NP_EST-3

Error Message    %NP_EST-3-UNAVAILABLE: %s 

Explanation    EST detected an internal error

Recommended Action    No action is required.

NP_EST-6

Error Message    %NP_EST-6-UNAVAILABLE: %s 

Explanation    EST Control No-Acknowledge Notification is sent to IOS to convey additional debug data regarding a NAK that occurred on the Control Queue

Recommended Action    No action is required.

Error Message    %NP_EST-6-UNAVAILABLE: %s 

Explanation    EST Diagnostic/POST Notification is sent to IOS to convey additional information about the power-on self-test or a diagnostic test result

Recommended Action    No action is required.

Error Message    %NP_EST-6-UNAVAILABLE: %s 

Explanation    EST Run-time Error Notification is sent to IOS to convey additional debug data that may help to identify the cause of the error

Recommended Action    No action is required.

NP_MD-0

Error Message    %NP_MD-0-UNAVAILABLE: Attempt to %s a data channel on the unexisting 
line %d/%d 

Explanation    An internal software error occured that probably resulted in corrupted modem database

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-0-UNAVAILABLE: Attempt to %s a data channel on the unexisting 
modem %d/%d 

Explanation    An internal software error occured that probably resulted in corruptedmodem database

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-0-UNAVAILABLE: Cannot allocate %d bytes of memory for %s 

Explanation    The system failed to allocate an important data structure due to the lack of memory

Recommended Action    Show mem. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-0-UNAVAILABLE: Cannot allocate TTY%d (%d/%02d) 

Explanation    Allocation of TTY structure failed. Either there is not enough memory or the TTY number is too big

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-0-UNAVAILABLE: Cannot allocate interface Async%d/%02d 

Explanation    Allocation of interface structure failed. Either there is not enough memory or the maximum number of interfaces was exceeded

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-0-UNAVAILABLE: Cannot bring up the module %d/%d/%d due to lack 
of module elements 

Explanation    NextPort Modem Driver cannot allocate an important data structure, called module element which is necessary to bring up the module. This should not normally happen and possibly indicates an error condition

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-0-UNAVAILABLE: Slot %d is already present in the system 

Explanation    An internal software error occured, that possibly resulted in corrupted slot database.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-0-UNAVAILABLE: Slot %d is not present in the system 

Explanation    An internal software error occured, that possibly resulted in corrupted slot database.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-0-UNAVAILABLE: TTY %s: Cannot allocate %s 

Explanation    An important buffer cannot be allocated due to the shortage of packet memory.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NP_MD-1

Error Message    %NP_MD-1-UNAVAILABLE: TTY %s: Attempt to set an unknown special 
character (type %d) to %#02x 

Explanation    NextPort Modem Driver received a request for hardware detection of an unknown type of a special character due to an internal software error

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NP_MD-3

Error Message    %NP_MD-3-UNAVAILABLE: %s is NULL in %s for port %d 

Explanation    Unexpected NULL pointer at specified location

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-3-UNAVAILABLE: Contiguous packet sent for transmit 

Explanation    A software error occurred resulting in an unexpected packet being set up for transmission and the packet was dropped by the NextPort Modem Driver

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-3-UNAVAILABLE: Could not seed data queue for module %d/%d/%d 

Explanation    NextPort Modem Driver could not seed the data queue with buffers

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-3-UNAVAILABLE: Could not send to data queue for port %d, 
inflight tx buffers %d 

Explanation    NextPort Modem Driver could not send buffer to Interface driver

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-3-UNAVAILABLE: Failed to return data buffer for port %d 

Explanation    Call to NextPort Interface Driver to replenish data buffer for this channel failed

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-3-UNAVAILABLE: Failed to send inband message for TTY %s 

Explanation    Call to send inband message on data queue failed

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-3-UNAVAILABLE: Modem slot structure for slot %d could not be 
created 

Explanation    NextPort modem driver could not create the modem slot structure which is required for modem services of this card

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-3-UNAVAILABLE: No buffer to seed data queue for module %d/%d/%d 

Explanation    NextPort Modem Driver could not obtain a buffer whilst trying to seed the module data queue. Due to packet memory shortage

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-3-UNAVAILABLE: Static transmit paktype unavailable 

Explanation    A software structure was found in an unexpected state during run-time for the indicated modem.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-3-UNAVAILABLE: TTY %s: No buffers available to set up the 
transmit queue 

Explanation    A software error occurred resulting in an unexpected exhaustion of the pool of data buffers used by the modem drivers.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-3-UNAVAILABLE: TTY %s: RTS is incorrectly deasserted; 
reasserting now 

Explanation    A software error occurred resulting in an invalid state for the RTS modem signal

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-3-UNAVAILABLE: TTY %s: Unknown NextPort in-band message (msg_id 
%04x) received 

Explanation    NextPort Modem driver received an unknown message from a NextPort module.This can happen if new firmware is used with an obsolete version of IOS

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-3-UNAVAILABLE: Too many buffers (%d) rxd for port %d 

Explanation    NextPort Module sent more buffers than is allowed for this channel

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MD-3-UNAVAILABLE: Unknown encapsulation %d on interface %s 

Explanation    A software error occurred resulting in an unknown encapsulation type on the interface specified by the error message.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NP_MD-6

Error Message    %NP_MD-6-UNAVAILABLE: NextPort module %d/%d/%d down 

Explanation    NextPort Modem Driver detected a module going down

Recommended Action    No action is required.

Error Message    %NP_MD-6-UNAVAILABLE: NextPort module %d/%d/%d up 

Explanation    NextPort Modem Driver detected a module coming up

Recommended Action    No action is required.

Error Message    %NP_MD-6-UNAVAILABLE: Slot %d (%d ports max) inserted 

Explanation    NextPort Modem driver detected a slot being inserted in the system. During the startup all slots that are present in the system are treated as being inserted

Recommended Action    No action is required.

Error Message    %NP_MD-6-UNAVAILABLE: Slot %d removed 

Explanation    Slot has been removed from the system

Recommended Action    No action is required.

NP_MM-3

Error Message    %NP_MM-3-UNAVAILABLE: Failed to allocate control message buffer for NP 
module %d/%d/%d - %s 

Explanation    NextPort Module Manager failed to allocate control message buffer

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MM-3-UNAVAILABLE: Failed to create Data Q for NP module %d/%d/%d 

Explanation    NextPort Module Manager failed to create Data Queue

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MM-3-UNAVAILABLE: Failed to send %s message to NP module %d/%d/%d 

Explanation    NextPort Module Manager failed to send control message

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MM-3-UNAVAILABLE: Invalid NP module state(%s) %d/%d/%d - %s 

Explanation    NextPort Module Manager detected invalid NP module state

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MM-3-UNAVAILABLE: Invalid NP_ADDRESS %d/%d/%d/%d - %s 

Explanation    NextPort Module Manager detected invalid NP_ADDRESS

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MM-3-UNAVAILABLE: Module Crash detected %d/%d/%d: state = %d, 
cause code = %d 

Explanation    NextPort Module Manager detected a crashed module

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MM-3-UNAVAILABLE: Module Run Time Error %d/%d/%d : recovery = 0x%x, 
error = 0x%x 

Explanation    NextPort Module Manager received a module run time error

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MM-3-UNAVAILABLE: Module country code failure %d/%d/%d 

Explanation    NextPort Module Manager failed to set the country code

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MM-3-UNAVAILABLE: Module exceeded restart threshold %d/%d/%d 

Explanation    NextPort Module exceeded the restart threshold

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MM-3-UNAVAILABLE: Unsupported module ACK response %d/%d/%d: msg 
len = %d, session ID = %d, msg tag = %d, msg ID = %d, cmd msg ID = %d, result code 
= %d 

Explanation    NextPort Module Manager received an unsupported message response

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_MM-3-UNAVAILABLE: Unsupported module response %d/%d/%d: msg len = 
%d, session ID = %d msg tag = %d, msg ID = %d 

Explanation    NextPort Module Manager received an unsupported message response

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NP_SIGLIB-3

Error Message    %NP_SIGLIB-3-UNAVAILABLE: Format of cp tone failed for tone-id %d, port 
%d/%d 

Explanation    Formatting of the call processing tone message to the nextport module failed

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NP_SPE_DS-3

Error Message    %NP_SPE_DS-3-UNAVAILABLE: %s 

Explanation    SPE download code failed to initialise - SPE download will fail

Recommended Action    LOG_STD_NO_ACTION

Error Message    %NP_SPE_DS-3-UNAVAILABLE: Cannot allocate %d bytes of memory for %s 

Explanation    The system failed to allocate an important data structure due to the lack of memory

Recommended Action    Show mem. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_SPE_DS-3-UNAVAILABLE: SPE %d/%d/%d/%d: %s 

Explanation    SPE download code failed - download aborted

Recommended Action    LOG_STD_NO_ACTION.

NP_SSM-0

Error Message    %NP_SSM-0-UNAVAILABLE: Cannot allocate %d bytes of memory for %s 

Explanation    The system failed to allocate an important data structure due to the lack of memory

Recommended Action    Show mem. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_SSM-3-UNAVAILABLE: SSM(%d/%d): Invalid Session/Service Instance 
Handle 

Explanation    Session and Service Manager Received failed to obtain its instance handle for the slot/port

Recommended Action    No action is required.

Error Message    %NP_SSM-3-UNAVAILABLE: SSM(%d/%d): Session Runtime Error Code = %d, 
Recovery Action = %d 

Explanation    Session and Service Manager Received a Runtime Error for the slot and port

Recommended Action    No action is required.

Error Message    %NP_SSM-3-UNAVAILABLE: SSM: Invalid Session/Service Message, ID = 0x%x 

Explanation    Session and Service Manager Received an invalid message from the NextPort Message Dispatcher

Recommended Action    No action is required.

NP_SSM-6

Error Message    %NP_SSM-6-UNAVAILABLE: NULL SSM Info Handle for slot %d, port %d 

Explanation    NextPort Session and Service Manager failed to obtain a controlinformation handle for the indicated slot and port numbers

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NP_SSM-6-UNAVAILABLE: NULL Vdev Common Handle for slot %d, port %d 

Explanation    NextPort Session and Service Manager failed to obtain aVoice Device Information handle for the indicated slot and port numbers

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NP-CRASHINFO Messages

This section contains Network Processor messages.

Error Message    %NP_CRASHINFO-2-OPEN_FAILED: Could not open crashinfo file [[chars]] 

Explanation    The file for writing crashinfo could not be opened. This is usually caused by the file system problem.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %NP_CRASHINFO-2-WRITE_FAILED: Could not write crashinfo file [[chars]] 

Explanation    Could not write crashinfo to the file. This is usuallycaused by the file system problem.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %NP_CRASHINFO-2-WRITING: Writing crashinfo file [[chars]] 

Explanation    NP detected a watchdog timeout. The crashinfo is collectedfrom problematic NP and stored in the location.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

NP-DEV Messages

This section contains Network Processor messages.

NP_DEV-2

Error Message    %NP_DEV-2-INVREGINTR: Illegal Write on NP RMA Register: [hex], Data: 
[hex] 

Explanation    This is an illegal Write to an NP RMA Register. This is to debug NP Parity Error issue. Examine traceback and forward it to development team.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %NP_DEV-2-WATCHDOG: Watchdog detected on NP [dec] 

Explanation    A software exception occured on an NP device.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

NP_DEV-3

Error Message    %NP_DEV-3-ECC_DOUBLE: Double-bit ECC error detected on NP [dec], Mem 
[dec], SubMem [hex],SingleErr [dec], DoubleErr [dec] Count [dec] Total [dec] 

Explanation    A double-bit ECC error was detected for a Network Processor device component.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %NP_DEV-3-ERRINTR: Error caused by: [chars] on NP [dec] 

Explanation    An error in Network Processor device operation was detected.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %NP_DEV-3-PERR: Non-recoverable Parity error detected on NP [dec], 
cause [dec] count [int] uqParityMask [hex], uqSRAMLine [hex], bRecov [dec], bRewr 
[dec] Total [dec] 

Explanation    A non-recoverable parity error was detected for a Network Processor device component.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

NP_DEV-5

Error Message    %NP_DEV-5-INTRTHR: Interrupt: cause [dec] for NP([int]) throttled 

Explanation    Too many interrupts are being generated from Network Processor device.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

NP_DEV-6

Error Message    %NP_DEV-6-PERR_RECOVERED: Recovered from a Parity error on NP [dec], 
cause [dec], count [int] uqParityMask [hex], uqSRAMLine [hex], bRecov [dec], bRewr 
[dec] Total [dec] 

Explanation    Recovered from a Parity error detected for a Network Processor device component.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %NP_DEV-6-ECC_SINGLE: Recovered from a single-bit ECC error detected 
on NP [dec], Mem [dec], SubMem [hex],SingleErr [dec], DoubleErr [dec] Count [dec] 
Total [dec] 

Explanation    Recovered from a single-bit ECC error detected for a Network Processor device component.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

NP_UCODE Messages

Error Message    %NP_UCODE-3-INVALID_FILE: NP microcode %s for device %s is invalid (%s) 

Explanation    The file containing the microcode for an NP is not specified or not accessible. This could be due to an invalid configuration or because the microcode is missing in this image.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

NSE100 Messages

This section contains network services engine messages.

NSE100-3

Error Message    %NSE100-3-IOBUSTIMEOUT: IO access to the address [hex] timed out 
(Target: [chars]) 

Explanation    The system controller flagged an I/O access timeout, indicating either a transient/fatal system component issue or an underlying software initialization issue. The source of the problem can be determined more accurately by decoding the address being accessed. If the I/O address is valid in the system memory map and if the system has been up and operational for a while, the problem is probably hardware related. If this problem is seen repeatedly, the corresponding component might need to be replaced.

Recommended Action    If the message is seen repeatedly, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: description of the user activity just before the occurrence of this incident, prevailing system operational conditions like traffic pattern, amount of traffic, system neighbors, system console messages and the output of the following commands: show running-config, show c7300 pxf accounting, show c7300 pxf interfaces all, show diag and show c7300.

Error Message    %NSE100-3-PINNACLE_PORT: [chars] - [chars] 

Explanation    A failure occurred while one of the Gigabit Ethernet (GE) ports on the NSE-100 was being initialized. This condition is probably caused by either a software error or a transient condition before the GE port becomes successfully initialized.

Recommended Action    If the GE ports either do not initialize or fail to forward traffic as a result of this condition, enter the shutdown command, followed by the no shutdown command, in interface configuration mode to shut down and restart the affected GE ports to restore the forwarding. If the message is seen repeatedly, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format:

- The user activity immediately preceding the receipt of this message.
- The prevailing system operational conditions such as the traffic patterns, amount of traffic, and system neighbors.
- Any additional system console messages.
- The output of the following commands: show version, show running-config, show controller gigabitEthernet, show interface gigabitEthernet, show pxf accounting, show c7300, show logging and show tech-support.

Error Message    %NSE100-3-UNEXPECTED_TIMEREVENT: The NSE-100 GE port driver couldn't 
determine the port associated with the expired internal managed timer.The expired 
managed timer is pointing to [chars] 

Explanation    The expired managed timer returned a null context. This condition indicates a software failure in the management of the timer.

Recommended Action    If the message is seen repeatedly, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format:

- The user activity immediately preceding the receipt of this message.
- The prevailing system operational conditions such as the traffic patterns, amount of traffic, and system neighbors.
- Any additional system console messages.
- The output of the following commands: show version, show running-config, show platform, show controller gigabitEthernet, show interface gigabitEthernet, show pxf accounting, show c7300, show logging and show tech-support.

Error Message    %NSE100-3-VA_ERROR: Vanallen ASIC detected an error condition: [chars] 

Explanation    The Van Allen ASIC has detected an error condition. Either a hardware error or an error in the packet was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NSE100-4

Error Message    %NSE100-4-UNAVAILABLE: CI-DEMUX FPGA detected an error (Status 0x%08x) 

Explanation    The Cluster Internnect DEMUX FPGA found an error with the egress packet. Type of error is indicated in the status. The message is informational.

Recommended Action    If the mesage is seen repeatedly, please collect following information and contact Cisco technical support representative. Output of the commands, show c7300 pxf accounting, show c7300 pxf interfaces all, show diag, show c7300

Error Message    %NSE100-4-UNAVAILABLE: ROM monitor upgrade in ROM %d terminated. 

Explanation    ROM monitor upgrade process was terminated by the user. The user had terminated the IOS boot up process from a first-time image in the writable ROM. This causes the verification process of this new ROM monitor to fail. This automatically sets the ROM monitor image to be INVALID.

Recommended Action    After downloading a new ROM monitor image to the writeable ROM, you must reload IOS for the new ROM monitor image to take effect. The first time a new ROM monitor image is loaded, you must allow the system to boot up IOS before doing any resets or power cycling. If the ROM monitor loading process is interrupted, the system interprets this as a boot up failure of the new ROM monitor image. Please re-download the ROM monitor image to the writable ROM and start the ROM monitor upgrade process again. If the problem persists, please issue the show tech-support command to gather more information and call your Cisco technical support representative and provide the representative with the gathered information.

Error Message    %NSE100-4-UNAVAILABLE: System hardware configuration %scompliant with 
recommended guidelines. 

Explanation    The aggregate throughput of the line cards exceeds the capacity of the NSE to line card interface in this system.

Recommended Action    Refer to the configuration guidelines for the maximum allowed aggregate throughput for the line cards in this system.

Error Message    %NSE100-4-UNAVAILABLE: The aggregate throughput of the Line Cards 
changed from %d kbps (%scompliant) to %d kbps (%scompliant) 

Explanation    The aggregate throughput of the line cards in the system changed to make the system compliant or non-compliant with the hardware configuration guidelines.

Recommended Action    Refer to the configuration guidelines for the maximum allowed aggregate throughtput for the line cards in this system.

Error Message    %NSE100-4-UNAVAILABLE: Unknown GBIC type or GBIC not inserted properly 
for interface GigabitEthernet%d/%d 

Explanation    Sometimes if GBIC is not inserted all the way into its slot, the GBIC type may return as Unknown Media Type

Recommended Action    Take out the GBIC and reinsert all the way in

NSE100-5

Error Message    %NSE100-5-AUTONEG_ENABLE: Auto negotiation is enabled for interface 
GigabitEthernet[dec]/[dec] due to [chars] 

Explanation    The auto-negotiation feature has been enabled for the Gigabit Ethernet interface in the slot and port specified in the message text. The reason why the feature was enabled is specified in the message text. The auto-negotiation feature is required for the interface to work properly.

Recommended Action    No action is required.

NSE100-5

Error Message    %NSE100-6-UNAVAILABLE: ROM monitor upgrade in ROM %d successful. 

Explanation    ROM monitor upgrade has successfully performed.

Recommended Action    LOG_STD_NO_ACTION

NSP-2

Error Message    %NSP-2-UNAVAILABLE: msgtxt_nomemory 

Explanation    An operation could not be accomplished because of a low-memory condition. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the system's memory.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a configuration that has more memory.

NSP-3

Error Message    %NSP-3-UNAVAILABLE: Bogus parameter passed: %s %d 

Explanation    Internal error: parameter pased to routine is invalid

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NSP-3-UNAVAILABLE: Invalid slots[]: %x 

Explanation    Internal error: slottype pointer is invalid

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NSP-4

Error Message    %NSP-4-UNAVAILABLE: %s: %s %s 

Explanation    A SONET line warning condition has been detected

LOG_STD_NO_ACTION.

NSPINT-3

Error Message    %NSPINT-3-UNAVAILABLE: no handler for index %d 

Explanation    Internal error: an interrupt has been detected for which no handler has been registered.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NSPINT-5

Error Message    %NSPINT-5-UNAVAILABLE: Spurious level %d interrupt (%d) 

Explanation    An interrupt for which no cause could be found has been detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NSP_APS-4

Error Message    %NSP_APS-4-UNAVAILABLE: Interface %s switched from %s to %s channel 

Explanation    The APS logic has determined that a switch over from one port to another was called for.

Recommended Action    LOG_STD_NO_ACTION

NSP_OIR-3

Error Message    %NSP_OIR-3-UNAVAILABLE: Cannot enable card slot(%d) subslot redundancy 
is active on subcard in slot(%d) 

Explanation    Cards present in chassis in current mode are incompatible

Recommended Action    Remove card and clear out alarms. Card could also be incompatible with existing cards and cannot run redundantly

Error Message    %NSP_OIR-3-UNAVAILABLE: Cannot enable half height card, redundancy 
conflict 

Explanation    Redundancy/Card conflict with cards in adjacent slot.

Recommended Action    LOG_STD_NO_ACTION

Error Message    %NSP_OIR-3-UNAVAILABLE: Inserted card incompatible with previously 
removed card 

Explanation    Card inserted is not same type as one previously removed and thus invalid.

Recommended Action    Please insert card similar to one which was previously removed or clear out alarm source

Error Message    %NSP_OIR-3-UNAVAILABLE: Insufficient system resources to complete card 
insertion/redundancy request, Reverting Configuration 

Explanation    Unable to allocate internal data structures for interface

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NSP_OIR-3-UNAVAILABLE: Invalid card/configuration in slot(%d) 
Ignoring Card 

Explanation    Cards present in chassis in current mode are incompatible

Recommended Action    Remove card and clear out alarms. Card could also be incompatible with existing cards and cannot run redundantly

Error Message    %NSP_OIR-3-UNAVAILABLE: Long bus stall (%u s) The newly inserted card 
may not seated properly. Please remove it and try again. 

Explanation    Card Bad or not properly seated.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NSP_OIR-3-UNAVAILABLE: OIR event structure allocation failure 

Explanation    Internal Oir element allocation failure. Usually this will indicate some memory leak

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Restart/reboot box at a convenient time. This problem will not affect normal operation but you will be unable to remove old hardware, or insert new hardware and bring it online

Error Message    %NSP_OIR-3-UNAVAILABLE: Unrecognized Card, Driver for Card not 
available in system software, ignoring card type 0x%x 

Explanation    Card inserted into system is not recognized by software -- ignoring.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NSP_OIR-4

Error Message    %NSP_OIR-4-UNAVAILABLE: 6400 Card %d/%d found off line - will 
'virtually' remove and reinsert to bring online 

Explanation    Card has somehow gone off line. Possibly a power glitch?? SW will bring it back online

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NSP_OIR-4-UNAVAILABLE: Redundancy submode not present! 

Explanation    System config does not have Redundancy submode

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NSP_OIR_6

Error Message    %NSP_OIR-6-UNAVAILABLE: Card %s inserted into slot: %d 

Explanation    Full card inserted into slot

Recommended Action    LOG_STD_NO_ACTION

Error Message    %NSP_OIR-6-UNAVAILABLE: Card %s inserted into subslot: %d/%d 

Explanation    Half height card inserted into subslot

Recommended Action    LOG_STD_NO_ACTION

Error Message    %NSP_OIR-6-UNAVAILABLE: Card %s removed from slot: %d 

Explanation    Full card removed from slot

Recommended Action    LOG_STD_NO_ACTION

Error Message    %NSP_OIR-6-UNAVAILABLE: Card %s removed from subslot: %d/%d 

Explanation    Half height card removed from subslot

Recommended Action    LOG_STD_NO_ACTION

Error Message    %NSP_OIR-6-UNAVAILABLE: Card %s, slot: %d, being brought online 

Explanation    Full card being brought online

Recommended Action    LOG_STD_NO_ACTION

Error Message    %NSP_OIR-6-UNAVAILABLE: Card %s, subslot: %d/%d, being brought online 

Explanation    Half Height card being brought online

Recommended Action    LOG_STD_NO_ACTION

NP_UCODE Messages

This section contains NextPort (NP) microcode messages.

Error Message    %NP_UCODE-3-INVALID_FILE: NP microcode [chars] for device [chars] is 
invalid ([chars]) 

Explanation    The file containing the microcode for an NP is not specified or not accessible. This could be due to an invalid configuration or because the microcode is missing in this image.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NRP-3

Error Message    %NRP-3-UNAVAILABLE: %s %s 

Explanation    An Interprocess Communication (IPC) error occurred. The details about what was attempted and what went wrong will be printed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NSE-3

Error Message    %NSE-3-UNAVAILABLE: Attempt to set ACL base address to null. Update 
aborted. 

Explanation    An attempt has been made to set the PXF ACL base address to a null. This condition will result in PXF exceptions being made and will eventually result in the PXF being disabled. The base address has not been updated.

Recommended Action    Make a change in the access list that will force a reevaluation of the ACL data.

Error Message    %NSE-3-UNAVAILABLE: QoS queue hung on interface %s. 

Explanation    The system was unable to close down the QoS support in PXF for the interface cleanly. Problems may arise if the QoS support in PXF for the interface is restarted without first reloading the pxf microcode.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NSE-3-UNAVAILABLE: Unknown QoS action type: 0x%x. 

Explanation    A QoS feature, unrecognised by PXF, has been configured with the Modular QoS CLI. The feature will work but excessive punting may occur if the feature is on an output interface

Recommended Action    If performance is poor, try disabling PXF.

NSE-6

Error Message    %NSE-6-UNAVAILABLE: No VLAN statistics are avaliable for PXF switched 
interface %s. 

Explanation    No 802.1Q statistics are avaliable for packets that are PXF switched

Recommended Action    No action is required.

NTI Messages

This section contains Negotiation Trigger Infrastructure (NTI) messages.

NTI-3

Error Message    %NTI-3-AGENT_ERR: %s Notifying platform about AGENT ERROR %s, AGENT EP 
ID 0x%x for EP ID 0x%x, EP type %s, EP group %s 

Explanation    A Negotiation Trigger Infrastructure (NTI) AGENT error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-CLIENT_NOT_REGSTRD_FOR_EPTYPE: %s Client (#%d - %s) has NOT 
registered for platform EP type %s 

Explanation    A client has not registered for a platform endpoint (EP) type.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_AGENT_LIST_ALLOC: Failed to allocate agent bitlist for 
endpoint 0x%x 

Explanation    The NTI ISSU process was unable to allocate the agent bitlist for an endpoint. The endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_DUMMY_MSG_FAILED: Failed to send a dummy nego msg to 
endpoint 0x%x 

Explanation    The NTI ISSU process was unable to send a dummy negotiation message to trigger negotiation on the peer. The endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_EXISTING_SESSION: Session already exists for ep 0x%x 

Explanation    The NTI ISSU session already exists for this endpoint. The endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_INVALID_MEDMAN: Invalid MEDMan data 

Explanation    The Multiple Endpoint Data Manager (MEDMan) data is invalid. The endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_INVALID_MSG_TRANS: NTI ISSU transformation function got an 
invalid message in argument 

Explanation    The NTI ISSU process transformation function received an invalid message. The message cannot be transformed and will not be processed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_INVALID_RC: Invalid ISSU rc argument for endpoint 0x%x 

Explanation    The NTI ISSU process received an invalid ISSU return code argument. ISSU negotiation will fail and the endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_INVALID_RCVD_MSG: NTI ISSU received an invalid message for 
transformation from endpoint 0x%x 

Explanation    The NTI ISSU process received an invalid message for transformation. The message cannot be processed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_INVALID_SESSION: Invalid session for ep 0x%x 

Explanation    The NTI ISSU session is invalid for the endpoint. The endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_MEDMAN_CREATE: Failed to create MEDMan data for endpoint 
0x%x 

Explanation    The NTI ISSU process was unable to create the Multiple Endpoint Data Manager (MEDMan) data for an endpoint. Negotiation cannot be done, and the endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_MEDMAN_GET: Failed to get MEDMan data for endpoint 0x%x 
(%s) 

Explanation    The NTI ISSU process was unable to retrieve MEDMan data for an endpoint. ISSU negotiation will fail for this endpoint, and the endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_MTU_FAILED: NTI ISSU failed to get MTU for message type %d 
(%s) 

Explanation    The NTI ISSU process was unable to get the message MTU for transformation. The message cannot be sent.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_NEGO_ALREADY_STARTED: NTI ISSU negotiation already 
started, endpoint 0x%x 

Explanation    An attempt was made to start the NTI ISSU negotiation, but it has already been started. The endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_NEGO_ASYNC_ERROR: Aync error during nego with 0x%x (%s) 

Explanation    The NTI ISSU process received an asynchronous error during negotiation with an endpoint. The endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_NEGO_INCOMPATIBLE: Negotiation incompatible for endpoint 
0x%x 

Explanation    The NTI ISSU negotiation is not compatible for this endpoint. The endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_NOT_INIT: NTI ISSU is not initialized, endpoint 0x%x. 

Explanation    The NTI ISSU process is not initialized. The endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_PLATFORM_TRANSPORT_NEGO_GET_REQ_PAK: NTI ISSU failed to 
get an platform transport nego message 

Explanation    The NTI ISSU process was unable to receive a platform transport negotiation message. The endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_PLATFORM_TRANSPORT_NEGO_SEND: NTI ISSU failed to send an 
platform transport nego message to 0x%x 

Explanation    The NTI ISSU process was unable to send a negotiation message using the platform transport. The endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_RCVD_NEGO_NOT_DONE: NTI ISSU negotiation not done when 
received a message from 0x%x 

Explanation    The NTI ISSU process received a message before negotiation was done. The message cannot be processed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_RCVD_TRANS_FAILED: NTI ISSU failed to transform received 
message from 0x%x 

Explanation    The NTI ISSU process was unable to transform a received message. The message cannot be processed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_RCVD_UNKNOWN_MSG: NTI ISSU received an unknown message 
type %d from 0x%x 

Explanation    The NTI ISSU process received a message whose type is unknown. The message cannot be processed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_RCV_FAILED: NTI ISSU failed to transform message type %d 
for receive from 0x%x (%s) 

Explanation    The NTI ISSU process was unable to transform the message for receive. The message cannot be processed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_REG_ADD: NTI ISSU failed to hook to the registry %s 

Explanation    The NTI ISSU process was unable to hook to a registry. This endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_REG_RECEIVE_NEGO_MSG: NTI ISSU failed call the platform 
receive nego message registry 

Explanation    The NTI ISSU process was unable to call the platform receive negotiation message registry. The endpoint will probably be reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_TRIG_NEGO_NOT_DONE: NTI ISSU negotiation not done when 
getting a trigger from 0x%x 

Explanation    The NTI ISSU process received a trigger from this endpoint before the negotiation was done. The trigger will be ignored.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_UNKNOWN_MSG_TYPE: NTI ISSU got an unknown message type: %d 

Explanation    The NTI ISSU process received an unknown message type while trying to get the message MTU. The message cannot be sent.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-ISSU_XMIT_FAILED: NTI ISSU failed to transform message type %d 
for transmit to 0x%x (%s) 

Explanation    The NTI ISSU process was unable to transform the message for transmit. The message cannot be sent.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-TRIG_ABORT_ALL_CLIENTS: %s Aborting trigger processing for all 
clients as requested by the platform, EP ID 0x%x trigger type %s trigger group %s 

Explanation    Trigger processing has been aborted for all clients due to a platform request.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-TRIG_CLIENT_NOTINLIST: %s Cannot trigger NTI client (%d) for 
this EP: could not find client in list, EP ID 0x%x 

Explanation    An NTI client could not be triggered for an endpoint because the client could not be found in the list.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-TRIG_INIT_ALREADY_IN_PROGRESS: %s Cannot initiate NTI trigger 
for EP ID 0x%x at this time: trigger processing of trigger type %s, trigger group 
%s already in progress 

Explanation    An NTI trigger could not be initiated because a trigger is already in progress.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %NTI-3-TRIG_PROCESSING: %s Trigger processing ERROR for client (#%d - 
%s), EP ID 0x%x trigger type %s trigger group %s : %s 

Explanation    An NTI trigger processing error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

NTP Messages

This section contains network time protocol (NTP) messages.

NTP-4

Error Message    %NTP-4-PEERUNREACH: Peer [IP_address] is unreachable 

Explanation    The NTP peer is unreachable.

Recommended Action    Check the network connection to the peer and ensure that NTP is running on the peer.

Error Message    %NTP-4-UNSYNC: NTP sync is lost 

Explanation    NTP synchronization to its peer is lost.

Recommended Action    Perform the following actions:

- Check the network connection to the peer.
- Check to ensure that NTP is running on the peer.
- Check that the peer is synchronized to a stable time source.
- Check to see if the NTP packets from the peer have passed the validity tests specified in RFC1305.

NTP-5

Error Message    %NTP-5-PEERSYNC: NTP synced to peer [IP_address] 

Explanation    NTP has synchronized the local clock to a new peer.

Recommended Action    No action is required.

NTP-6

Error Message    %NTP-6-PEERREACH: Peer [IP_address] is reachable 

Explanation    The NTP peer is reachable.

Recommended Action    No action is required.

Error Message    %NTP-6-RESTART: NTP process starts 

Explanation    The NTP process has just started or restarted.

Recommended Action    No action is required.

Error Message    %NTP-6-STOP: NTP process stops 

Explanation    NTP is disabled.

Recommended Action    Check to see if NTP has been manually disabled by the administrator.

OBFL Messages

This section contains Onboard Failure Logging (OBFL) messages.

OBFL-5

Error Message    %OBFL-5-DISABLED: Onboard Failure Logging disabled 

Explanation    Onboard Failure Logging has been disabled.

Recommended Action    No action is required.

OBFL_ERRMSG Messages

This section contains Onboard Failure Logging (OBFL) error messages.

OBFL_ERRMSG-5

Error Message    %OBFL_ERRMSG-5-FILECREATEFAIL: OBFL [chars] App failed to open/create 
file [chars] . Errno = [dec] 

Explanation    The file open or creation operation failed.

Recommended Action    No action is required.

Error Message    %OBFL_ERRMSG-5-FILEFSTATFAIL: OBFL [chars] App failed to fstat file 
[chars] . Errno = [dec] 

Explanation    The file fstat operation failed.

Recommended Action    No action is required.

Error Message    %OBFL_ERRMSG-5-FILELSEEKFAIL: OBFL [chars] App failed to Lseek file 
[chars] . Errno = [dec] 

Explanation    The file lseek operation failed.

Recommended Action    No action is required.

Error Message    %OBFL_ERRMSG-5-FILEMINFREEFAIL: OBFL [chars] App failed to set 
coalesce min free 

Explanation    Failed to set the coalesce minimum free value.

Recommended Action    No action is required.

Error Message    %OBFL_ERRMSG-5-FILEOPENFAIL: OBFL [chars] App failed to open file 
[chars] . Errno = [dec] 

Explanation    The file open operation failed.

Recommended Action    No action is required.

Error Message    %OBFL_ERRMSG-5-FILEREADFAIL: OBFL [chars] App read failure on file 
[chars] . Errno = [dec] 

Explanation    The file read operation failed.

Recommended Action    No action is required.

Error Message    %OBFL_ERRMSG-5-HISTFILESMALL: OBFL [chars] App: history file is 
exceedingly small 

Explanation    The history file for this application has been detected to be very small.

Recommended Action    No action is required.

OCE Messages

This section contains output chain elements (OCE) infrastructure messages.

OCE-3

Error Message    %OCE-3-MISSING_HANDLER_FOR_SW_OBJ: Missing handler for '[chars]' 
function 

Explanation    An internal API request has been ignored because it was unexpected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OCE-3-MISSING_HANDLER_FOR_SW_OBJ_TYPE: Missing handler for '[chars]' 
function for type [chars] 

Explanation    An internal API request has been ignored because it was unexpected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OCE-3-OCE_CHANGED_BY_APPLY_FUNCTION: Target OCE[hex_addr] changed 
to[hex_addr] by apply function[hex_addr]

Explanation    An internal API request has been ignored because it was unexpected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OCE-3-OCEDEPDUMP: [chars] 

Explanation    An error condition triggered display of OCE dependents.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OCE-3-OCE_FWD_STATE_HANDLE: Limit of oce forward state handle 
allocation reached; maximum allowable number is [int] 

Explanation    Did not store the reinject forwarding state handle, as the maximum number of handles are already in use.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OCE-3-OCE_FWD_STATE_HANDLE_INIT: Failed to initialize a stack of 
reusable forward state handles; at element [int], initial stack size is [int] 
elements 

Explanation    Could not allocate enough forwarding state handles for initial handle reuse.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OCE-3-QUEUE_UNLOCK: Failed to [chars] unlock[chars] for [chars] oce 
[hex] 

Explanation    Failed to enqueue a unlock for an OCE. This condition may lead to a memory leak.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OCE-3-UNEXPECTED_DISP_TYPE: Unexpected disposition type is encounted; 
expecting disposition types are [chars], found [chars] 

Explanation    An internal disposition counter measure request has been ignored because it was unexpected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OCE-3-UNEXPECTED_SW_OBJ_TYPE: SW_OBJ handle/type mismatch; expecting 
oce type [chars], found [dec] 

Explanation    An internal API request has been ignored because it was unexpected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OCE-3-UNINITIALIZED_VECTOR: Improperly initialized [chars] vector in 
[chars] OCE bundle [hex], packet dropped 

Explanation    An OCE bundle vector was improperly initialized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ODM Messages

This section contains online diagnostics manager (ODM) subsystem messages.

ODM-3

Error Message    %ODM-3-PEER_INCOMPATIBLE: Online Diags Peer Version is different 

Explanation    The version of the peer online diagnostics manager is different from the expected version.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %ODM-3-SC_TEST_FAIL: Slot [dec], Subcard [dec],[chars] [chars] Failed 

Explanation    The online diagnostic test for the subcard specified in the error message has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

OER_TT_FLOW Messages

This section contains Optimized Edge Routing (OER) top talkers flow border router messages.

OER_TT_FLOW-2

Error Message    %OER_TT_FLOW-2-OER_TT_FLOW_BR_CACHEINIT: Error initializing OER TT 
Flow BR cache 

Explanation    The NetFlow top talker cache could not be initialized on the border router because of a low-memory condition.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message    %OER_TT_FLOW-2-OER_TT_FLOW_BR_EXPORTINIT: Error initializing OER TT 
Flow BR Export queue 

Explanation    The OER NetFlow top talker export queue could not be initialized on the border router because of a low-memory condition.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

OER_TT_FLOW-4

Error Message    %OER_TT_FLOW-4-OER_TT_FLOW_BR_FLOWEXPORT: Error exporting [chars] 

Explanation    An error involving a flow to the route processor has occurred.

Recommended Action    This is a debug message only. No action is required.

OIR Messages

This section contains online insertion and removal (OIR) messages.

OIR-3

Error Message    %OIR-3-HARD_RESET: Module [dec] is being hard reset as a part of 
switchover error recovery 

Explanation    The specified module is being hard reset as a recovery for failure to respond to a switchover message.

Recommended Action    No action is required.

Error Message    %OIR-3-ISSU_RESET: Module %d is being hard reset as a part of ISSU 
upgrade 

Explanation    The specified module is being hard reset as part of a planned ISSU upgrade.

Recommended Action    No action is required.

Error Message    %OIR-3-LC_FAILURE: Module %d has Major online diagnostic failure, %s 

Explanation    This module experienced a major online diagnostic failure.

Recommended Action    Re-seat the card. If the problem persists, copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.

Error Message    %OIR-3-PSM_SUBCARDDETECT: Slot [dec] [chars] [dec]: subcard [dec] 
inserted 

Explanation    A protection switch module (PSM) subcard has been detected in the slot specified in the message text.

Recommended Action    No action is required.

Error Message    %OIR-3-PSM_SUBCARDREMOVE: Slot [dec] [chars] [dec]: subcard [dec] 
removed 

Explanation    A protection switch module (PSM) subcard has been removed from the specified slot.

Recommended Action    No action is required.

Error Message    %OIR-3-PWRCYCLE: Card in module %d, is being power-cycled '%s' 

Explanation    The OIR facility detected the line card as unresponsive and attempted to power-cycle the card.

Recommended Action    No action is required.

Error Message    %OIR-3-SOFT_RESET: Module [dec] is being soft reset as a part of 
switchover error recovery 

Explanation    The specified module is being soft reset as a part of switchover error recovery.

Recommended Action    No action is required.

Error Message    %OIR-3-SOFT_RESET_SSO: Module %d is being soft reset as a part of 
switchover error recovery 

Explanation    The specified module is being soft reset as a part of a switchover error recovery.

Recommended Action    No action is required.

Error Message    %OIR-3-STDBY_PWRCYCLE: Standby was notified, Card in module [dec] is 
being power-cycled [chars] 

Explanation    The OIR facility on the redundant supervisor engine was notified that a module on the active supervisor engine is unresponsive. The module is being power-cycled.

Recommended Action    No action is required.

Error Message    %OIR-3-STDBY_UNKNOWN: Standby was notified, Unknown card in slot [dec] 

Explanation    The OIR facility on the redundant supervisor engine was notified that an undetermined module was detected on the active supervisor engine.

Recommended Action    Reseat the module in the specified slot.

Error Message    %OIR-3-UCODE_INTERNAL: The image download to card in slot [dec] failed 
due to internal error: [chars], [chars] 

Explanation    An internal error has occurred in the line card image download code.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the remote command switch dir system:image/ command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OIR-3-UNKNOWN: Unknown card in slot %d, card is being disabled 

Explanation    The OIR facility detected a line card but could not determine the type.

Recommended Action    Reseat the card in the indicated slot.

Error Message    %OIR-3-UNKNOWN_FANTRAY: Fan Tray idprom read error. Unknown fan-tray 
in slot %d. 

Explanation    The OIR facility detected a fan-tray but could not determine the type by reading idprom. Fan-tray will not go into high cooling modes.

Recommended Action    Reseat the fan-tray in the indicated slot.

Error Message    %OIR-3-VSS_PWRCYCLE: Card in Switch %d module %d, is being power-cycled 
'%s' 

Explanation    The OIR facility detected the line card as unresponsive and attempted to power-cycle the card.

Recommended Action    No action required.

Error Message    %OIR-4-DISABLE: Unsupported service module [chars] in slot [dec] 
disabled 

Explanation    This service module is not supported in this release of software.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OIR-4-INSERTION: Possible half inserted module detected in slot [dec] 
or a slow insertion 

Explanation    This module is either inserted improperly or is not making a full contact to the backplane or it is being insert very slowly. The user should follow the cisco recommandation on module insertion procedures.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.

Error Message    %OIR-4-WARN: [chars] 

Explanation    The OIR facility detected the specified condition.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

OIR-6

Error Message    %OIR-6-CONSOLE: Changing console ownership to %s processor 

Explanation    The OIR facility has switched the console to the specified processor.

Recommended Action    No action is required.

Error Message    %OIR-6-CWANVSSISSU: CWAN card present in slot [dec] in the slave 
chassis is powered down because ISSU is in progress 

Explanation    CWAN card already present in the slave chassis of a virtual switch should not be powered up during ISSU. It will be powered up on switchover or upon completion of ISSU.

Recommended Action    No action is required.

Error Message    %OIR-6-DIAG_OFFLINE: Card inserted in slot [dec], is now ready for 
offline diagnostics 

Explanation    The OIR facility detected a newly inserted line card. The line card is configured for the offline diagnostic state by the user. This state can be entered only after the module is in the online diagnostic state.

Recommended Action    This is an informational message only. No action is required.

Error Message    %OIR-6-DIAG_ONLINE: Card inserted in slot [dec], is now ready for 
online diagnostics 

Explanation    The OIR facility detected a newly inserted line card. The line card is configured for the online diagnostic state by the user or if diagnostic failure is detected during bootup.

Recommended Action    This is an informational message only. No action is required.

Error Message    %OIR-6-DISALLOW: Supervisor attempting to come up as secondary in EHSA 
mode, will not be allowed. 

Explanation    Primary is in RF mode. As EHSA and RF cannot co-exist, the software will disallow any attempts from secondary to come up.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OIR-6-DOWNGRADE: Fabric capable module [dec] not at an appropriate 
hardware revision level, and can only run in flowthrough mode 

Explanation    This fabric capable module is not at an appropriate hardware revision level, and can run only in flowthrough (bus) mode.

Recommended Action    Upgrade the line card hardware.

Error Message    %OIR-6-DOWNGRADE_EARL: Module [dec] [chars] installed is not identical 
to system PFC and will perform at current system operating mode. 

Explanation    The PFC/DFC module is at a higher hardware revision than the level of the system PFC. The PFC/DFC module will operate at the same level as that of the system PFC.

Recommended Action    This is an informational message only. No action is required.

Error Message    %OIR-6-INSFAN: Fan [dec] inserted 

Explanation    The OIR facility detected a newly inserted fan tray.

Recommended Action    This is an informational message only. No action is required.

Error Message    %OIR-6-INSPS: Power supply inserted in slot %d 

Explanation    The OIR facility detected the insertion of a powersupply [n]. When turned on, the total power will be adjusted.

Recommended Action    This is an informational message only. No action is required.

Error Message    %OIR-6-NOPWRISSU: Card inserted in slot %d powered down because ISSU 
is in progress 

Explanation    The online insertion and removal (OIR) facility detected a newly inserted line card during an ISSU upgrade process. The new card will be powered down until completion of the ISSU.

Recommended Action    No action is required.

Error Message    %OIR-6-PROVISION: Module %d does not meet the provisioning 
requirements, power denied 

Explanation    The provisioning configuration does not allow the type of line card that was inserted.

Recommended Action    This is an informational message only. No action is required.

Error Message    %OIR-6-PWRFAILURE: Module [dec] is being disabled due to power 
convertor failure [hex] 

Explanation    The DC-DC power converter failed on this module and must be replaced.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OIR-6-REMFAN: Fan [dec] removed 

Explanation    The OIR facility detected the removal of a fan tray [n].

Recommended Action    This is an informational message only. No action is required.

Error Message    %OIR-6-REMPS: Power supply removed from slot %d 

Explanation    The OIR facility detected the removal of a powersupply from slot [n]. The total power will be adjusted and power will be denied to some linecards if needed.

Recommended Action    This is an informational message only. No action is required.

Error Message    %OIR-6-RUNNING_CONFIG: %s %s failed %d (%s) 

Explanation    During switchover, the OIR facility is unable to clean up running-config processor.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OIR-6-SEQ_MISMATCH: SCP seq mismatch for card in slot [dec] : [chars] 

Explanation    The OIR facility detected an SCP sequence mismatch for the card in the specified slot.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OIR-6-SOFT_RESET_ISSU: Module [dec] is being soft reset as a part of 
ISSU cycle 

Explanation    The module specified in error message is being soft reset as a part of ISSU cycle.

Recommended Action    No action is required.

Error Message    %OIR-6-SP_INSCARD: Card inserted in %sslot %d, interfaces are now 
online 

Explanation    The OIR facility detected a newly inserted line card. The inserted interfaces will be shut down until it is configured by the user or, if an interface of that type was previously configured, it will be restored to its previous state.

Recommended Action    This is an informational message only. No action is required.

Error Message    %OIR-6-SP_REMCARD: Card removed from slot %d, interfaces disabled 

Explanation    The OIR facility detected the removal of a processor from slot [n]. The interfaces on that processor will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OIR-6-SPINE_PWRFAILURE: Spine Module %d is being disabled due to power 
convertor failure. 

Explanation    The DC-DC power convertor failed on this module, need to replace hardware.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OIR-6-STDBY_INSCARD: Standby was notified, card online in slot [dec] 

Explanation    The OIR facility on the standby supervisor engine was notified by the active supervisor engine that a processor was inserted in slot [n] and that all the interfaces are now usable.

Recommended Action    No action is required.

Error Message    %OIR-6-STDBY_REMCARD: Standby was notified, card removed from slot 
[dec] 

Explanation    The OIR facility on the standby supervisor engine was notified by the active supervisor engine that a processor from the specified slot has been removed.

Recommended Action    No action is required.

Error Message    %OIR-6-STDBY_SPINE_INSCARD: Standby was notified, xbar module in slot 
%d is now online. 

Explanation    The OIR facility on Standby Supervisor was notified by the Active that a spine module inserted in slot [n] and the spine module is online

Recommended Action    No action is required.

Error Message    %OIR-6-STDBY_SPINE_REMCARD: Standby was notified, spine card removed 
from slot %d 

Explanation    The OIR facility on Standby Supervior was notifed by the Active that a spine card in slot[n] has been removed

Recommended Action    No action is required.

OIR_ISSU Messages

This section contains online insertion and removal (OIR) in-service software upgrade (ISSU) messages.

OIR_ISSU-3

Error Message    %OIR_ISSU-3-BUFFER: Cat6K OIR ISSU client failed to a buffer for 
message, error %d 

Explanation    The online insertion and removal (OIR) ISSU client failed to get a buffer for building a negotiation message. As a result, the client cannot send a negotiation message to the standby unit and the standby unit cannot be brought up.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.

Error Message    %OIR_ISSU-3-CAPABILITY: Cat6K OIR ISSU client %s 

Explanation    During capability negotiation, the OIR ISSU client detected an error that results in a mismatch between the client capability of the active and standby units.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %OIR_ISSU-3-INIT: Cat6K OIR ISSU client initialization failed at %s, 
error %s 

Explanation    The OIR ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OIR_ISSU-3-MSG_NOT_OK: Cat6K OIR ISSU client message %d is not 
compatible 

Explanation    The OIR ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message    %OIR_ISSU-3-MSG_SIZE: Cat6K OIR ISSU client failed to get the message 
size for message %d 

Explanation    The OIR ISSU client was unable to calculate the message size for the message specified. The client will be unable to send the message to the standby unit.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

Error Message    %OIR_ISSU-3-POLICY: Cat6K OIR ISSU client message type %d is %s 

Explanation    The OIR ISSU client received a message type that it does not support. A policy is applied to make the session compatible.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu session commands and your pertinent troubleshooting logs.

Error Message    %OIR_ISSU-3-SEND_FAILED: Cat6K OIR ISSU client failed to send a 
negotiation message, error %d 

Explanation    The OIR ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.

Error Message    %OIR_ISSU-3-SESSION: Cat6K OIR ISSU client %s 

Explanation    The OIR ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message    %OIR_ISSU-3-TRANSFORM: Cat6K OIR ISSU client %s transform failed, 
error %s 

Explanation    The OIR ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the OIR state of the bay will not be identical with the active unit.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.

OIR-SP

Error Message    %OIR-SP-6-CONSOLE: Changing console ownership to %s processor

Explanation    The OIR facility has switched the console to the specified processor.

Recommended Action    No action is required.

Error Message    %OIR-SP-6-DOWNGRADE_EARL: Module %d %s installed is not identical to 
system PFC and will perform at current system operating mode.

Explanation    The PFC/DFC module is at a higher hardware revision than the level of the system PFC. The PFC/DFC module will operate at the same level as that of the system PFC.

Recommended Action    No action is required.

Error Message    %OIR-SP-6-INSCARD: Card inserted in slot [dec], interfaces are now 
online

Explanation    The OIR facility detects a newly inserted module. The interfaces associated with that module are operational, but are shut down until they are configured by the user. If any interfaces of that type were previously configured, they are restored to their previous state.

Recommended Action    No action is required.

Error Message    %OIR-SP-6-INSPS: Power supply inserted in slot [dec]

Explanation    The OIR facility has detected the insertion of a power supply in the specified slot. The total power adjusts after the power supply is turned on,

Recommended Action    No action is required.

OLM Messages

This section contains Optical Link Management (OLM)) and Link Management Protocol (LMP) messages.

OLM-3

Error Message    %OLM-3-UNAVAILABLE: Failed to send LMP msg to %s 

Explanation    Attempt to send LMP control message has failed; this could be due to an internal error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OLM-3-UNAVAILABLE: Internal error: Couldn't find neighbor while %s 

Explanation    An LMP processing that requires to access information about the neighbor has found that no such neighbor exists. This could be due to internal error.

Recommended Action    Turn on generic and packet level debugging using the command, debug ip lmp and gather LMP configuration using the command, show ip olm and gather the displayed information and contact Cisco technical assistance.

Error Message    %OLM-3-UNAVAILABLE: Service Discovery: Attribute %s incompatible with 
neighbor %s 

Explanation    Specified service attribute does not match with neighbor. The neighbor and/or the local node may not be properly configured.

Recommended Action    Use the show mpls uni lmp neighbor command on the local as well as the neighbor node (where applicable), to determine the service attributes and modify the configuration, where feasible, to ensure that the attributes match

Error Message    %OLM-3-UNAVAILABLE: Service Discovery: Attributes for port %s 
incompatible with nbr %s 

Explanation    Port-level service attribute does not match with those of the neighbor. The neighbor and/or the local node may not be properly configured.

Recommended Action    Use the show mpls uni lmp neighbor command on the local as well as the neighbor node (where applicable), to determine the service attributes and modify the configuration, where feasible, to ensure that the port-level service attributes match

Error Message    %OLM-3-UNAVAILABLE: State %s; Event %s 

Explanation    An LMP state machine has encountered an event that is not legal or allowed in the current state.

Recommended Action    Write down the state and the event and call your Cisco technical support representative for assistance.

OLM-4

Error Message    %OLM-4-UNAVAILABLE: Bad LMP Msg; type %u 

Explanation    An LMP message has been received with invalid message type. This suggests that we have a broken LMP implementation on the sending neighbor

Recommended Action    Locate the sending neighbor and turn on packet level debugging using the debug ip lmp packets command. On seeing an ill-formed LMP packet, gather displayed information and contact the Cisco technical assistance.

Error Message    %OLM-4-UNAVAILABLE: Bad TLV; type %u 

Explanation    An LMP message has been received with invalid TLV type. This suggests that we have a broken LMP implementation on the sending neighbor

Recommended Action    Locate the sending neighbor and turn on packet level debugging using the debug ip lmp packets command. On seeing an ill-formed LMP packet, gather displayed information and contact the Cisco technical assistance.

Error Message    %OLM-4-UNAVAILABLE: Invalid TLV Length %u in LMP msg; remaining size %u 

Explanation    An LMP message has been received with invalid TLV length. This suggests that we have a broken LMP implementation on the sending neighbor.

Recommended Action    Locate the sending neighbor and turn on packet level debugging using the debug ip lmp packets command. On seeing an ill-formed LMP packet, gather displayed information and contact the Cisco technical assistance.

OLM-5

Error Message    %OLM-5-UNAVAILABLE: Internal error: Couldn't find IPCC to send LMP msg; 
msg type : %u 

Explanation    This is generally caused by race conditions wherein an LMP message is received from a neighbor before the first control channel goes UP [locally]. This conditions usually happens when a node reboots.

Recommended Action    If the problem persists even after the node has completed initialization, enter sho ip olm command to find the LMP configuration and use the debug ip lmp packets and debug ip lmp generic command to gather additional context type information and call Cisco technical assistance.

Error Message    %OLM-5-UNAVAILABLE: Invalid TE Link ID %u in Link Summary message 

Explanation    A Link Summary or Link Summary Ack or Link Summary Nack message has been received with bad TE Link ID. The sending node probably doesn't have LMP configured correctly.

Recommended Action    Locate the neighbor from which the LMP message with invalid TE Link ID was received and enter show ip olm command and make sure that the port ID mappings between the two nodes are correct

Error Message    %OLM-5-UNAVAILABLE: LMP %s msg id %u not 1+%u 

Explanation    An LMP message has been received with message id that is not sequential within the Control channel or TE Link. This situation is not caused by the known cases that cause message id sequence to be broken, including local node reboot, neighbor node reboot and neighbor retransmission

Recommended Action    Enter the show ip olm stat command when this problem occurs and gather the information displayed and call the Cisco technical assistance.

Error Message    %OLM-5-UNAVAILABLE: LMP rcvd msg from unknown src ip 0x%i, link % 

Explanation    An LMP message has been received from a neighbor that we don't know about. This could be due to the fact that the neighbor in question has not yet been configured on this node.

Recommended Action    Locate the problem neighbor using the IP address and enter a show ip olm command; gather the displayed info and contact Cisco technical assistance.

Error Message    %OLM-5-UNAVAILABLE: Link Summary parameter(%s) mismatch 

Explanation    Port ID and other link summary parameters do not match with those on the neighbor in question. The neighbor and/or the local node is not properly configured.

Recommended Action    Enter the show ip olm command on the local as well as the neighbor node and make sure that the port IDs match.

Error Message    %OLM-5-UNAVAILABLE: No such neighbor to assign 

Explanation    User attempted to assign interface to invalid neighbor

Recommended Action    Use show olm to find the correct neighbor name

ONLINE Messages

This section contains SCP (Switch-module Configuration Protocol) download processor messages.

ONLINE-2

Error Message    %ONLINE-2-LCP_BOOT_MISMATCH: The system detected LCP boot version 
mismatch for module in slot [dec], and will upgrade with new LCP boot image bundled 
into the system image, and power cycle the module. 

Explanation    The system detected LCP boot version mismatch for module. This condition would normally occur if the LCP boot version on the legacy modules is old for the modules, which require rapid boot support. The LCP boot version is upgraded automatically and the module will be power-cycled.

Recommended Action    No action is required.

ONLINE-3

Error Message    %ONLINE-3-UNKNOWN_CARD_TYPE: Unknown card type is encountered: 
card_type = [int] 

Explanation    The card type is unknown or not supported.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ONLINE-6

Error Message    %ONLINE-6-BOOT_TIMER: Module %d, Proc. %d. Failed to bring online 
because of boot timer event 

Explanation    The system was unable to download the runtime image to the module and processor because the boot did not complete in the allocated time.

Recommended Action    No action is required.

Error Message    %ONLINE-6-DNLDFAIL: Module %d, Proc. %d, Runtime image download failed 
because of %s 

Explanation    The system was not able to download the runtime image to the module/proc because of the displayed reason

Recommended Action    No action is required.

Error Message    %ONLINE-6-DNLD_TIMER: Downloading image to Module [dec], Proc. [dec]. 
has failed, due to download timer expiry 

Explanation    The system was unable to download the runtime image to the module and processor because the download did not complete in the allocated time.

Recommended Action    No action is required.

Error Message    %ONLINE-6-DOWNLOAD_TIMER: Module %d, Proc. %d. Failed to bring online 
because of download timer event 

Explanation    The system was unable to download the runtime image to the module and processor because the download did not complete in the allocated time.

Recommended Action    No action is required.

Error Message    %ONLINE-6-FIND_MASTER_FAIL: Module %d, Proc. %d. SCP_DNLD failed to 
find master 

Explanation    The system was unable to find the master to download an image to the module and processor within the allocated time.

Recommended Action    No action is required.

Error Message    %ONLINE-6-GET_IMAGE_FAIL: Module %d, Proc. %d. SCP_DNLD failed to get 
image 

Explanation    The system was unable to get the image from the master for downloading to the module and processor.

Recommended Action    No action is required.

Error Message    %ONLINE-6-INITFAIL: Module %d: Failed to %s 

Explanation    The system failed to bring the module [n] online, due to the displayed reason

Recommended Action    No action is required.

Error Message    %ONLINE-6-INVALID_DNLD_REQ: Received an unexpected image download 
request from Linecard Module [dec], Proc [dec]. Linecard image download request 
reason was [chars] 

Explanation    The system received an image download request from the module and processor complex specified in the message text, but that complex has already downloaded the image and should be initialized and operating normally.

Recommended Action    No action is required.

Error Message    %ONLINE-6-LCC_CONFIG_FAIL: Module %d. LCC Client %s failed to 
configure at %08x 

Explanation    During a Secure Copy (SCP) download, the Linecard Configuration Coordinator (LCC) client failed to finish configuration of the module.

Recommended Action    No action is required.

Error Message    %ONLINE-6-LCP_DNLD: Error while downloading image to Module [dec], 
Proc. [dec].: [chars]  

Explanation    An error was encountered while downloading an image to a switching module. The first [dec] is the module number, the second [dec] is the process number, and [chars] is the message explanation.

Recommended Action    No action is required.

Error Message    %ONLINE-6-ONLINE_TIMER: Module %d, Proc. %d. Failed to bring online 
because of online timer event 

Explanation    The system was unable to download the runtime image to the module and processor because the online event did not happen in the allocated time.

Recommended Action    No action is required.

Error Message    %ONLINE-6-READY_TIMER: Module %d, Proc. %d. Failed to bring online 
because of ready timer event 

Explanation    The system was unable to download the runtime image to the module and processor because the ASIC initialization did not complete in the allocated time.

Recommended Action    No action is required.

Error Message    %ONLINE-6-REGN_TIMER: Module %d, Proc. %d. Failed to bring online 
because of registration timer event 

Explanation    The system was unable to download the runtime image to the module and processor because the registration did not complete in the allocated time.

Recommended Action    No action is required.

Error Message    %ONLINE-6-RUNNING_TIMER: Module %d, Proc. %d. Failed to bring online 
because of running timer event 

Explanation    The system was unable to download the runtime image to the module and processor because the running event did not happen in the allocated time.

Recommended Action    No action is required.

Error Message    %ONLINE-6-VSS_INITFAIL: Switch %d,Module %d: Failed to %s 

Explanation    The system failed to bring the module [n] online, due to the displayed reason

Recommended Action    No action is required.

Error Message    

ONLINEDIAG Messages

Error Message    %ONLINEDIAG-2-CPU_SWITCH_LB_TST_PKT_THRESH_ERROR: CPU Switch 
Interface : [dec]/[dec] of online diagnostic packets in error.

Explanation    The packet loss can be due to congestion.

Recommended Action    Issue the command show diag online cpu sw to get more details about the failure. If this error occurs frequently, contact your technical representative for assistance with the output of the command show techsupport.

ONS15530 Messages

This section contains Cisco ONS 15530 trunk card messages.

ONS15530-1

Error Message    %ONS15530-1-DISCOVER_ENET: Failed to init Ethernet device [dec] 

Explanation    The software could not be initialized.

Recommended Action    Power down the system, reseat the interface card, and reboot the system. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ONS15530-2

Error Message    %ONS15530-2-UNAVAILABLE: Invalid resource number from PXF (%d). 
(PLEASE REPORT THIS!) 

Explanation    The PXF hardware diversion path specified a bad resource number.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %ONS15530-2-UNAVAILABLE: No memory available for %s 

Explanation    An attempt at memory allocation failed.

Recommended Action    Try these actions to remedy the problem: Add memory. Disable some features. Apply filtering to decrease the size of system data structures - the routing table, for example. In general, reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message    %ONS15530-2-UNAVAILABLE: Out of range Card interface, %d on slot %d 

Explanation    The software specified an out-of-range card interface.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %ONS15530-2-UNAVAILABLE: Out of range card slot index%d 

Explanation    The software specified an out-of-range card slot index.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %ONS15530-2-UNAVAILABLE: Out of range card slot/subslot pair%d/%d 

Explanation    The software specified an out-of-range card slot/subslot pair.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %ONS15530-2-UNAVAILABLE: Recursive loop while getting the daughtercard 
info for card type %d 

Explanation    While getting the daughter card info for the chassismib the platform snmp code goes into an infinite loop.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ONS15530-3

Error Message    %ONS15530-3-UNAVAILABLE: Access to %s temperature sensor failed 

Explanation    Accesses to chassis temperature sensor failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %ONS15530-3-UNAVAILABLE: Err calculating xpolated value: %s 

Explanation    physubcard or idprom ptr is NULL

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %ONS15530-3-UNAVAILABLE: Interrupt %s not expected, masking off 

Explanation    An interrupt of a certain type was signalled, but the interrupt handler for this type of interrupt is not yet installed.

Recommended Action    This problem should be self-correcting but indicates either a hardware or a software defect. If it's a hardware defect, further problems are to be expected. If it's a software problem, certain types of error and alarm conditions may be left undetected. Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %ONS15530-3-UNAVAILABLE: Mismatch in backplane IDPROM, %s: 
Active-side=%d, Sby-side=%d 

Explanation    There are two backplane IDPROMS. Each is readable by one of the two redundant CPUs. Most IDPROM fields should be programmed by manufacturing to contain identical information. Only the first mismatched field is shown. Use a CLI show command to see additional mismatches.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %ONS15530-3-UNAVAILABLE: Mismatch in backplane IDPROM, %s: 
Active-side=%s, Sby-side=%s 

Explanation    There are two backplane IDPROMS. Each is readable by one of the two redundant CPUs. Most IDPROM fields should be programmed by manufacturing to contain identical information. Only the first mismatched string is shown. Use a CLI show command to see additional mismatches.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %ONS15530-3-UNAVAILABLE: Unknown chassis model. 

Explanation    Data stored in midplane is bad or incomplete.

Recommended Action    Contact technical support to update your system.

Error Message    %ONS15530-3-UNAVAILABLE: card in slot [%d/%d] disabled. 

Explanation    The card is being deactivated.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ONS15530-4

Error Message    %ONS15530-4-UNAVAILABLE: Invalid CPU ID, assuming revision 1 

Explanation    The CPU ID could not be read from EEPROM. This is probably due to a hardware failure.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %ONS15530-4-UNAVAILABLE: Unknown MAC address block size. 

Explanation    Data stored in midplane is bad or incomplete.

Recommended Action    Contact technical support to update your system.

ONS15530-5

Error Message    %ONS15530-5-UNAVAILABLE: Compact flash card (disk0) %s 

Explanation    A file system's status has changed. Follow any instructions provided with the message.

Recommended Action    No action is required.

OOBP-4

Error Message    %OOBP-4-UNAVAILABLE: Warning -- oobp can't be used 

Explanation    Async driver can't send out the oobp message because no resource.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OOBP-4-UNAVAILABLE: Warning -- reset async oobp no response 

Explanation    Async driver does not response to the ASYNC RESET command.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

OPTICAL_MONITOR Messages

This section contains optical monitoring messages.

OPTICAL_MONITOR-4

Error Message    %OPTICAL_MONITOR-4-FAILED: [chars] [chars] 

Explanation    The current hardware version cannot support monitoring for the rate that was specified.

Recommended Action    Specify a different rate for monitoring, if possible. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

OPTICAL_IF-1

Error Message    %OPTICAL_IF-1-UNAVAILABLE: %s, %s: %s 

Explanation    The specified Alarm has been declared or cleared

Recommended Action    Recommended action is to repair the source of the alarm.

OPTICAL_IF-3

Error Message    %OPTICAL_IF-3-UNAVAILABLE: %s 

Explanation    The metopt subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

OPTICAL_IF_ALARMS-3

Error Message    %OPTICAL_IF_ALARMS-3-UNAVAILABLE: High Alarm Threshold for %s on port 
%s %s 

Explanation    High alarm threshold was exceeded.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OPTICAL_IF_ALARMS-3-UNAVAILABLE: High Warning Threshold for %s on 
port %s %s 

Explanation    High warning threshold was exceeded.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OPTICAL_IF_ALARMS-3-UNAVAILABLE: Low Alarm Threshold for %s on port 
%s %s 

Explanation    Low alarm threshold was exceeded.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OPTICAL_IF_ALARMS-3-UNAVAILABLE: Low Warning Threshold for %s on port 
%s %s 

Explanation    Low warning threshold was exceeded.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

OSCP-3

Error Message    %OSCP-3-UNAVAILABLE: %s %x 

Explanation    An internal software error occurred. The message contains more information that can be used to identify the problem.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

OSCP-4

Error Message    %OSCP-4-UNAVAILABLE: Configuration Error: %s 

Explanation    This message indicates a configuration error in the OSCP subsystem. The message will display more specific information about the cause of problem.

Recommended Action    Change the configuration to correct the error.

Error Message    %OSCP-4-UNAVAILABLE: Invalid pkt: %s %d %d 

Explanation    An invalid packet was received from a network peer.

Recommended Action    Check the originating device for a cause of the corrupted packets.

OSCP-7

Error Message    %OSCP-7-UNAVAILABLE: %s 

Explanation    This is an informational message only. It is used by Cisco for testing.

Recommended Action    Informational messages can be disabled by changing logging level.

OSM_MULTILINK Messages

This section contains Optical Services Module distributed multilink (OSM_MULTILINK) messages.

OSM_MULTILINK-3

Error Message    %OSM_MULTILINK-3-PROCESS_FAIL: Process creation failed for [chars] 

Explanation    The system failed to create a process. The probable cause of this condition is that the system has low memory.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

OSM_MULTILINK-4

Error Message    %OSM_MULTILINK-4-BUNDLEERROR: Bundle([chars]) is not distributed 

Explanation    The bundle specified in the message is not associated with the OSM.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSM_MULTILINK-4-BUNDLENULL: Unexpected bundle missing in [chars] 
searching for [chars] 

Explanation    A software error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSM_MULTILINK-4-BUNDLEVC: [chars] for vc [dec] and if_index [dec] 

Explanation    A software error has occurred while a bundle was being provisioned.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSM_MULTILINK-4-IDBNULL: Unexpected hwidb missing in [chars] 

Explanation    A software error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSM_MULTILINK-4-IPCNOTREADY: Bundle process on the line card is not 
ready to handle message of type [dec] 

Explanation    Bundle is being deleted on the line card due to an ip cef disable command and is not ready to process other messages. The most likely cause of this condition is that CEF was disabled and enabled in very quick succession.

Recommended Action    Reset the line card.

Error Message    %OSM_MULTILINK-4-MLPSBNULL: Unexpected subblock missing for [chars] 

Explanation    A software error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSM_MULTILINK-4-NUMLINKS: The bundle had an unexpected number of 
links([dec]) in [chars] 

Explanation    A software error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSM_MULTILINK-4-QUEUE_BUNDLE: Not able to queue the bundle ([chars]), 
Num. of bundles [dec] 

Explanation    A software error has occurred while a bundle was being inserted in the queue.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

OSM_MULTILINK-5

Error Message    %OSM_MULTILINK-5-BUNDLEEXCEEDED: Bundle([chars]) cannot be associated 
with link([chars]), max [dec] 

Explanation    The number of bundles has exceeded the limit for the group belonging to the link. The bundle specified in the error message will not work in distributed mode. If the module is CT3 (OSM-CT3 module), then ports 1-12 belong to one group. If the module is a CHOC-3 module (OSM-CHOC-DS0 module), then ports 1-4 belong to one group. If the module is a CHOC-12 module (OSM-CHOC-DS0 module), then port 1 belongs to one group, and port 2 belongs to the second group. Only 168 bundles can be supported per group. The new bundle created will cause an extra load on the RP CPU.

Recommended Action    Remove the multilink interface that is causing this condition.

Error Message    %OSM_MULTILINK-5-CFGERROR: Cannot set up this bundle link-- [chars] to 
bundle [chars] reason:[chars] 

Explanation    The bundle link could not be set up. A configuration or resource limit has been reached. The bundle may be forced to become inactive (go down). If the line card is a CT3 (OSM-CT3 line card), then ports 1-12 belong to one group. If the line card is a CHOC-3 (OSM-CHOC-DS0 line card), then ports 1-4 belong to one group. If the line card is a CHOC-12 (OSM-CHOC-DS0 line card), then port 1 belongs to one group and port 2 belongs to the second group. Only 168 bundles can be supported per group and each bundle can have a maximum of 12 links.

Recommended Action    Ensure that all links belong to the same group and slot. Check the number of links in the bundle and number of bundles in the group. After the configuration has been corrected, enter the shutdown and no shutdown commands on the multilink interface to shut down and restart the interface.

OSPF Messages

This section contains Open Shortest Path First (OSPF) messages.

OSPF-3

Error Message    %OSPF-3-CFG_NBR_ALLOC_FAILED: Could not allocate or find neighbor 
[IP_address] 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPF-3-CFG_NBR_FAILED: Neighbor [IP_address] not configured 

Explanation    The configured neighbor options are not valid.

Recommended Action    Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.

Error Message    %OSPF-3-INT_ATTACHED_MULTI_AREAS: Interface [chars] is attached to 
more than one area 

Explanation    The interface is attached on the interface list to an area other than the one that the interface links to.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPF-3-INT_INIT_FAILED: Init failed for interface [chars], [chars]. 

Explanation    The interface initialization failed. The following are possible reasons:

- The area to which the interface is being attached is being deleted.
- It was not possible to create a neighbor datablock for the local router.

Recommended Action    Remove the configuration command that covers the interface and try again. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPF-3-LSA_LEN: Area [chars] router-LSA of length [dec] bytes plus 
update overhead [dec] bytes is too large to flood. 

Explanation    The router tried to build a router-LSA that is larger than the huge system buffer size or the OSPF protocol imposed maximum.

Recommended Action    If the reported total length (LSA size plus overhead) is larger than the huge system buffer size but less than 65535 bytes (the OSPF protocol imposed maximum), you may increase the huge system buffer size. If the reported total length is greater than 65535, you must decrease the number of OSPF interfaces in the reported area.

OSPF-4

Error Message    %OSPF-4-AREA_ALLOC_FAIL: Can not allocate memory for area structure 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPF-4-ASBR_WITHOUT_VALID_AREA: Router is currently an ASBR while 
having only one area which is a stub area 

Explanation    An ASBR must be attached to an area which can carry AS external or NSSA LSAs.

Recommended Action    Make the area to which the router is attached into an NSSA or regular area.

Error Message    %OSPF-4-CFG_NBR_INVAL_NBMA_OPT: Can not use configured neighbor: cost 
and database-filter options are allowed only for a point-to-multipoint network 

Explanation    The configured neighbor was found on an NBMA network and either the cost or database-filter option was configured. These options are only allowed on point-to-multipoint type networks.

Recommended Action    Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.

Error Message    %OSPF-4-CFG_NBR_INVAL_NET_TYPE: Can not use configured neighbor: 
neighbor command is allowed only on NBMA and point-to-multipoint networks 

Explanation    The configured neighbor was found on a network for which the network type was neither NBMA or point-to-multipoint.

Recommended Action    No action is required.

Error Message    %OSPF-4-CFG_NBR_INVAL_P2MP_OPT: Can not use configured neighbor: poll 
and priority options are allowed only for a NBMA network 

Explanation    The configured neighbor was found on a point-to-multipoint network and either the poll or priority option was configured. These options are only allowed on NBMA type networks.

Recommended Action    Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.

Error Message    %OSPF-4-CFG_NBR_P2MP_NEEDS_COST: Can not use configured neighbor: cost 
or database-filter option is required for point-to-multipoint broadcast network 

Explanation    The configured neighbor was found on a point-to-multipoint broadcast network. Either the cost or database-filter option needs to be configured.

Recommended Action    Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.

Error Message    %OSPF-4-INVALID_METRIC: OSPF-%d Area %s: Router %i originating invalid 
type %d LSA, ID %i, Metric %d on Link ID %i Link Type %d 

Explanation    The router indicated in this message has originated a Link-State Advertisement (LSA) with an invalid metric. If this is a router LSA and the link metric is zero, routing loops and traffic loss could occur in the network.

Recommended Action    On the router that originated the reported LSA, configure a valid metric for the given LSA type and link type.

Error Message    %OSPF-4-INV_LSA_BLD_FLG: Invalid build flag [hex] for LSA 
[IP_address], type [dec] 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPF-4-NO_IPADDRESS_ON_INT: No IP address for interface [chars] 

Explanation    The interface is not point-to-point and is unnumbered.

Recommended Action    Either change the interface type to point-to-point or give the interface an IP address.

Error Message    %OSPF-4-NO_OUTPUTQ: Packet not written to the output queue 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPF-4-NORTRID: OSPF process [dec] failed to allocate unique 
router-id and cannot start 

Explanation    OSPF failed while attempting to allocate a unique router ID from the IP addresses of its interfaces.

Recommended Action    Ensure that at least one interface is active (up) and has a valid IP address. If multiple OSPF processes are running on the router, each requires a unique router ID. Configure a unique router ID manually by entering the router-id a.b.c.d command, or configure an interface in the same VRF table by entering the ip vrf forwarding word command to which the OSPF process belongs. Configure on that interface an IP address that is not used as a router ID by any other OSPF process.

Error Message    %OSPF-4-NULL_LINKAGE: Doubly linked list linkage is NULL 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPF-4-NULL_PREV_LINKAGE: Doubly linked list prev linkage is NULL 
[hex] 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPF-4-OSPF_MAX_LSA: Maximum number of non self-generated LSA has 
been exceeded "[chars]" - [dec] LSAs 

Explanation    The maximum number of non-self-generated LSAs has been exceeded.

Recommended Action    Check if some router in the network is generating a large number of LSAs as a result of misconfiguration.

Error Message    %OSPF-4-OSPF_MAX_LSA_THR: Threshold for maximum number of non 
self-generated LSA has been reached "[chars]" - [dec] LSAs 

Explanation    The threshold for the maximum number of non-self-generated LSA has been reached.

Recommended Action    Check if some router in the network is generating a large number of LSAs as a result of misconfiguration.

Error Message    %OSPF-4-RTRID_IN_USE: Router-ID [IP_address] is in use by ospf process 
[dec] 

Explanation    An attempt was made to assign a router ID that is in use by another process.

Recommended Action    Configure another router ID for one of the processes.

Error Message    %OSPF-4-UNREC_TIMER: Unrecognized timer [dec] in OSPF [chars] 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

OSPF-6

Error Message    %OSPF-6-BAD_LSA_COUNT: OSPF-%d Area %s: LSA ID %i, Type %d, Adv-rtr 
%i, LSA counter %s 

Explanation    An internal error was found and automatically corrected in an OSPF Link-State Advertisement (LSA). This error does not affect operation.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show tech-support ospf commands and your pertinent troubleshooting logs.

Error Message    %OSPF-6-PROC_REM_FROM_INT: OSPF process [dec] removed from interface 
[chars] 

Explanation    The OSPF process was removed from the interface due to IP VRF removal.

Recommended Action    No action is required.

Error Message    %OSPF-6-UNREC_VIRT_INT_TYPE: Unrecognized virtual interface [chars]. 
Treat it as loopback stub route 

Explanation    Because the virtual interface type was not recognized by OSPF, it will be treated as a loopback interface stub route.

Recommended Action    No action is required.

OSPF_NSR Messages

Error Message    %OSPF_NSR-2-ISSU_INIT: ISSU client initialization failed to %s, error: 
%d (%s) 

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

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPF_NSR-3-CF_ADD_CLIENT: Error adding OSPF checkpoint client: %s 

Explanation    OSPF was not able to register as a client of the checkpoint facility.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support ospf commands and your pertinent troubleshooting logs.

Error Message    %OSPF_NSR-3-CF_NOMEM: Unable to allocate checkpoint buffer: %s 

Explanation    NSR operation may be degraded because of insufficient memory.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support ospf commands and your pertinent troubleshooting logs.

Error Message    %OSPF_NSR-3-CF_NOMSG: No space in checkpoint buffer 

Explanation    NSR operation may be degraded because of insufficient memory.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support ospf commands and your pertinent troubleshooting logs.

Error Message    %OSPF_NSR-3-CHKPT_MSG: Invalid checkpoint message: %s (%s) 

Explanation    NSR will not operate because of an error in a checkpoint message.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support ospf commands and your pertinent troubleshooting logs.

Error Message    %OSPF_NSR-3-ISSU_MSG_SIZE: OSPF%s ISSU client failed to get the MTU 
for message type %s (%u): %u (%s) 

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

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support ospf, show issu sessions, show issu negotiated versions commands and your pertinent troubleshooting logs.

Error Message    %OSPF_NSR-3-ISSU_SESSION_UNREGISTR: OSPF%s ISSU client failed to 
unregister session information, error: %d (%s) 

Explanation    The OSPF ISSU client failed to unregister session information.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support ospf, show issu sessions, show issu negotiated versions commands and your pertinent troubleshooting logs.

Error Message    %OSPF_NSR-3-ISSU_TRANSFORM_FAIL: OSPF%s ISSU client %s transform 
failed for message type %d (%s): %d (%s) 

Explanation    The OSPF ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the Archive state between the active device and the standby device is not identical.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support ospf, show issu sessions, show issu negotiated versions commands and your pertinent troubleshooting logs.

OSPFv3 Messages

This section contains Open Shortest Path First (OSPF) version 3 messages.

OSPFv3-3

Error Message    %OSPFv3-3-IPSEC_POLICY_SPI_REUSE: %s %s is already configured with SPI 
%u. 

Explanation    An attempt was made to use a SPI that has already been used

Recommended Action    Unconfigure the SPI first, or choose a different one.

Error Message    %OSPFv3-3-UNAVAILABLE: Could not allocate or find the neighbor 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-3-UNAVAILABLE: DB already exist : area %s lsid %i adv %i type 
0x%x 

Explanation    OSPF has a problem locating the LSA, which could lead to a memory leak.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-3-UNAVAILABLE: Flagged as being an ABR without a backbone area 

Explanation    The router was flagged as an Area Border Router (ABR) without backbone area in the router.

Recommended Action    Restart the OSPF process.

Error Message    %OSPFv3-3-UNAVAILABLE: Init failed for interface %s, %s. 

Explanation    The interface initialization failed. Possible reasons: 1) The area to which the interface is being attached is being deleted. 2) It was not possible to create the link scope database 3) It was not possible to create a neighbor datablock for the local router

Recommended Action    Remove the configuration command that covers the interface and then try it again. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-3-UNAVAILABLE: Interface %s is attached to more than one area 

Explanation    The interface is on the interface list for an area other than the one which the interface links to.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-3-UNAVAILABLE: Internal error: %s 

Explanation    An internal software error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-3-UNAVAILABLE: OSPF is enabled on %s during idb initialization 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-3-UNAVAILABLE: OSPF process %d is changing router-id. 
Reconfigure virtual link neighbors with our new router-id 

Explanation    OSPF process is being reset, and it is going to select a new router-id. This will bring down all virtual links. To make them work again, virtual link configuration needs to be changed on all virtual link neighbors.

Recommended Action    Change virtual link configuration on all the virtual link neighbors, to reflect our new router-id.

Error Message    %OSPFv3-3-UNAVAILABLE: Reached unknown state in neighbor state machine 

Explanation    An internal software error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-3-UNAVAILABLE: if %s if_state %d 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-3-UNAVAILABLE: lsid %i adv %i type 0x%x gateway %i metric %d 
network %i mask %i protocol %#x attr %#x net-metric %d 

Explanation    OSPF found inconsistency between its database and IP routing table.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

OSPFv3-4

Error Message    %OSPFv3-4-AREA_MISMATCH: Received packet with incorrect area 
from[ipv6_addr], [chars], area [IP_address], packet area [IP_address] 

Explanation    An OSPF packet was received with an area ID in its header that does not match the area of this interface.

Recommended Action    Check the OSPF configuration of the receiver and the sender for inconsistency.

Error Message    %OSPFv3-4-ASBR_WITHOUT_VALID_AREA: Router is currently an ASBR while 
having only one area which is a stub area 

Explanation    An ASBR must be attached to an area which can carry AS external or NSSA LSAs.

Recommended Action    Make the area to which the router is attached into an NSSA or regular area.

Error Message    %OSPFv3-4-CFG_NBR_INVAL_NBMA_OPT: Can not use configured neighbor: 
cost and database-filter options are allowed only for a point-to-multipoint 
network 

Explanation    The configured neighbor was found on an NBMA network and either the cost or database-filter option was configured. These options are only allowed on point-to-multipoint type networks.

Recommended Action    Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.

Error Message    %OSPFv3-4-CFG_NBR_INVAL_NET_TYPE: Can not use configured neighbor: 
neighbor command is allowed only on NBMA and point-to-multipoint networks 

Explanation    The configured neighbor was found on a network for which the network type was neither NBMA or point-to-multipoint.

Recommended Action    No action is required.

Error Message    %OSPFv3-4-CFG_NBR_INVAL_P2MP_OPT: Can not use configured neighbor: 
poll and priority options are allowed only for a NBMA network 

Explanation    The configured neighbor was found on a point-to-multipoint network and either the poll or priority option was configured. These options are only allowed on NBMA type networks.

Recommended Action    Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.

Error Message    %OSPFv3-4-CFG_NBR_NOT_NBMA_NET: Neighbor command allowed only on NBMA 
networks 

Explanation    Neighbor command allowed only on NBMA networks.

Recommended Action    Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.

Error Message    %OSPFv3-4-CFG_NBR_P2MP_NEEDS_COST: Can not use configured neighbor: 
cost or database-filter option is required for point-to-multipoint broadcast 
network 

Explanation    The configured neighbor was found on a point-to-multipoint broadcast network. Either the cost or database-filter option needs to be configured.

Recommended Action    Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.

Error Message    %OSPFv3-4-DBD_ALLOC_FAIL: Could not allocate DBD packet 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-4-DB_NOT_FOUND: Can't find LSA database type [hex], area [hex] 
, interface [hex] 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-4-INVALID_METRIC: OSPFv3-%d Area %s: Router %i originating 
invalid type 0x%x LSA, ID %u, Metric %d on Link ID %d Link Type %d 

Explanation    The specified router has originated a Link-State Advertisement (LSA) with an invalid metric. If this is a router LSA and the link metric is zero, routing loops and traffic loss could occur in the network.

Recommended Action    On the router that originated the reported LSA, configure a valid metric for the given LSA type and link type.

Error Message    %OSPFv3-4-INV_LSA_BLD_FLG: Invalid build flag [hex] for LSA 
[IP_address], type [hex] 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-4-NO_GLOBAL_ADDR: Could not select a global IPv6 address. 
Virtual links require at least one global IPv6 address. 

Explanation    A virtual link was configured. For the virtual link to function, a global IPv6 address must be available. However, no global IPv6 address could be found on the router.

Recommended Action    Configure a global IPv6 address on an interface on this router.

Error Message    %OSPFv3-4-NO_OUTPUTQ: Packet not written to the output queue 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-4-NULL_LINKAGE: Doubly linked list linkage is NULL 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-4-NULL_PREV_LINKAGE: Doubly linked list prev linkage is NULL 
[hex] 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-4-RTRID_IN_USE: Router-ID [IP_address] is in use by ospf 
process [dec] 

Explanation    An attempt was made to assign a router ID that is in use by another process.

Recommended Action    Configure another router ID for one of the processes.

Error Message    %OSPFv3-4-TIMER_ERROR: Error for timer [dec] in OSPF process [chars] 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %OSPFv3-4-TWO_INT_ON_LINK: Multiple interfaces ([chars]/[chars]) on a 
single link detected. This is not supported 

Explanation    OSPFv3 enabled on multiple interfaces that are on the same link is not supported.

Recommended Action    OSPFv3 should be disabled or made passive on all but one of the interfaces.

Error Message    %OSPFv3-4-UNREC_TIMER: Unrecognized timer [dec] in OSPF [chars] 

Explanation    An internal error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

OSPFv3-5

Error Message    %OSPFv3-5-UNAVAILABLE: Process %d, Nbr %i on %s from %s to %s, %s 

Explanation    An OSPF neighbor has changed state. The message describes the change and the reason for it. This message appears only if the log-adjacency-changes command is configured for the OSPF process.

Recommended Action    LOG_STD_NO_ACTION

OSPFv3-6

Error Message    %OSPFv3-6-UNREC_VIRT_INT_TYPE: Unrecognized virtual interface 
[chars]. Treat it as loopback stub route 

Explanation    Because the virtual interface type was not recognized by OSPFv3, it will be treated as a loopback interface stub route.

Recommended Action    No action is required.

OUNIC-4

Error Message    %OUNIC-4-UNAVAILABLE: %s 

Explanation    IOS OS API routine return error

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OUNIC-4-UNAVAILABLE: %s(%s): %s 

Explanation    RSVP API routine return error

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %OUNIC-4-UNAVAILABLE: failed getting local_port_id for: neighor %i, 
remote_port_id=%d 

Explanation    Destination O-UNI client cannot find its own local_port_id

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

OTNMGR Messages

Error Message    %OTNMGR-3-OTN_STATS_CREATE_IF_FAIL: stats for interface index [dec] 
could not be created with status [dec] 

Explanation    N/A

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

PACC Messages

This section contains Cisco 7300 port adapter carrier card (PACC) messages.

PACC-3

Error Message    %PACC-3-RXPAKLEN: PA-CC FPGA detected an ingress packet length error 
on slot [dec] 

Explanation    The PA carrier card has detected a packet length error during reception of an ingress packet.This condition could be caused by one of the following:

- Faulty hardware (either the Cisco 7300 or the PA carrier card)
- A corrupted FPGA image
- A software problem (least likely).

Recommended Action    If this message occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later Cisco IOS image may have an updated FPGA bundle that could solve the problem. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PACC-3-TXPAKLEN: PA-CC FPGA detected an egress packet length error on 
slot [dec] 

Explanation    The PA carrier card has detected a packet length error during transmission of an egress packet. This condition could be caused by one of the following:

- Faulty hardware (either the Cisco 7300 or the PA carrier card)
- A corrupted FPGA image
- A software problem (least likely).

Recommended Action    If this message occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later Cisco IOS image may have an updated FPGA bundle that could solve the problem. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

PA-0

Error Message    %PA-0-UNAVAILABLE: Conflict detected when trying to install %s 
interrupt handler, bay %d. 

Explanation    An attempt was made to register an interrupt handler for either a non existent port adaptor or the wrong interrupt prority level.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

PA-2

Error Message    %PA-2-UNAVAILABLE: Bad default register(%x) setting(%x) in PA bridge 

Explanation    The software is unable to configure certain settings for the port adapter protocol control information bridge in the specified bay.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: Failed to config bridge for PA %d 

Explanation    The system side PCI bridge for this PA failed initialization. The PA will not be operational because of this.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: Illegal Port Adaptor type %d in bay %d of %s. 

Explanation    The port adapter is not supported by the controller to which it is plugged into.

Recommended Action    Remove the port adapter and return the controller to its original configuration.

Error Message    %PA-2-UNAVAILABLE: Out of range PCI Port Adaptor bay %d 

Explanation    The software specified an out-of-range port adapter bay.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: Out of range PCI Port Adaptor interface, %d on bay 
%d 

Explanation    The software specified an out-of-range port adapter interface.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: PA interface data incorrect, %#x 

Explanation    Incorrect PA interface data found

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: PA interface idb incorrect, %#x 

Explanation    The port adapter system control block (PASCB) data structure indicates a zero interface descriptor block (IDB).

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: PA interface pa incorrect, %#x 

Explanation    Incorrect PA interface specified

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: PA interface pascb incorrect, %#x 

Explanation    The port adapter system control block (PASCB) data structure was incorrectly set in the command data structure.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: PA interface port_inst incorrect, %#x 

Explanation    Failure to access port instance internal data

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: PA interface vcont incorrect, %#x 

Explanation    Incorrect VC interface specified

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: PA null adapter, %#x 

Explanation    Null PA interface specified

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: PA queue overflow, cmd %#x 

Explanation    PA queue has overflowed; programming lost

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: Recursive loop while getting the daughtercard info 
for PA type %d 

Explanation    While getting the daughter card info for the chassismib the platform snmp code goes into an infinite loop.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: Undefined Port Adaptor type %d in bay %d 

Explanation    The software does not have a driver for the port adapter type in the specified bay.

Recommended Action    Make sure the image you are running is supposed to support this card. Check that the card is properly seated. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: Unsupported I/O Controller (type %d) in I/O Bay. 
The I/O Controller network interfaces will be unavailable. 

Explanation    The software does not have a driver for the port adapter type in the specified bay.

Recommended Action    Make sure the image you are running is supposed to support this card. Newer I/O Controllers will only work with the -kboot- image. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-2-UNAVAILABLE: Unsupported Port Adaptor Bridge %#x in bay %d 

Explanation    The software does not have a driver for that port adapter protocol control information bridge in the specified bay.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

PA-3

Error Message    %PA-3-UNAVAILABLE: Improper insertion for slot %d. Remove and then 
re-insert the PA 

Explanation    PCI Activation of PA has failed, thus the PA is deactivated and must be removed and then re-inserted.

Recommended Action    Remove and then re-insert the PA firmly into the slot.

Error Message    %PA-3-UNAVAILABLE: PA in slot%d (%s) is not supported on this %s 

Explanation    This port adaptor is not supported on this chassis/cpucard.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-3-UNAVAILABLE: PA in slot%d (%s) requires base h/w revision of 
(%d.%d) for this %s 

Explanation    A newer hardware revision of the port adaptor is required for functional operation on this chassis.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-3-UNAVAILABLE: Recommended port adapter configuration exceeded 

Explanation    The total bandwidth of fast and medium bandwidth port adapters exceed the rated capacity of this system.

Recommended Action    Refer to the configuration guidelines for the maximum allowed high and medium bandwidth port adapters for the system.

Error Message    %PA-3-UNAVAILABLE: This PA type (%s) is not supported in slot%d of this 
%s 

Explanation    This port adaptor is not supported on this slot of this chassis/cpucard.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-3-UNAVAILABLE: Unable to create driver for Port Adaptor type %d in 
bay %d 

Explanation    Possible memory shortage or adaptor hardware error

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-3-UNAVAILABLE: port adapter in bay [%d] failed to reset. 

Explanation    An attempt to reset and initialize the port adapter timed out.

Recommended Action    This situation should correct itself. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    %PA-3-UNAVAILABLE: port adapter in bay [%d] powered off. 

Explanation    The port adapter is being powered off.

Recommended Action    This situation should correct itself. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

PA-4

Error Message    %PA-4-UNAVAILABLE: Improper removal for slot %d. 

Explanation    PA was inserted and then removed while being initialised.

Recommended Action    After an insertion, the PA should be pulled out only after the initialisation is complete. If there is any traffic running through the router, the initialisation can take up to 30 seconds

Error Message    %PA-4-UNAVAILABLE: PCI activation failed, bay %d, 0x%x 

Explanation    The system received an invalid PCI signal from the port adapter. This is probably due to a hardware failure.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

PACKET Messages

This section contains packet messages.

Error Message    %PACKET-2-ACCESSERROR: Client process %ld attempted to access packet 
%x owned by process %ld 

Explanation    A packet manager client can only access and modify packets that have been assigned to its process

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-BLOCKERROR: Client process %ld has packet 0x%8x , the buffer 
0x%8x has been corrupted. 

Explanation    Data has been written past the end of the previous buffer causing memory to be corrupted.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-CHANCREATEFAIL: Packet server fails to create a channel and 
event manager error: %s 

Explanation    Packet server fails to create an event manager and channel. Clients will be unable to connect to packet server, and packet server will be unable to send and receive messages.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-CHUNKCREATEFAIL: chunk_create for %s pool failed 

Explanation    The packet manager encountered a chunk creation failure while creating the packet header chunk

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-CONNECTFAIL: Client process %ld failed to connect to Packet 
Manager (reason %s) 

Explanation    A packet manager client failed to connect to Packet Manager

Recommended Action    Restart the process which could not connect to Packet Manager. Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-CTXERROR: The context information 0x%8x is not valid. 

Explanation    An application to the memory block manager has passed either a context pointer that is not valid.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-DEQUEUEFAIL: Fail to remove client %ld from pak_client_list 
at %s 

Explanation    Can not remove the client from client list queue. This may cause the client fail to reconnect to packet server

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-ENQUEUEFAIL: Fail to insert client %ld into pak_client_list 
at %s 

Explanation    Can not insert the client into client list queue. This causes the client unable to connect to packet server

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-EVENTATTACHFAIL: event attach failure 

Explanation    The packet subsystem encountered an error when registering for synchronous or asynchronous events.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-EVENTBLOCKFAIL: event_block failure 

Explanation    event block error was encountered when blocking for external events

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-EVENTCONTEXTALLOCFAIL: event_context_alloc failure 

Explanation    Failed while allocating the event context

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-GETNODENAMEFAIL: failed to get node name in pakman server 
init 

Explanation    packet manager server unable to retrieve the hostname for node/linecard

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-HDRPOOLINITFAIL: Packet header pool init failed 

Explanation    Failed to initialize the packet pool headers

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-MEMBLKERROR: Memory block 0x%8x is not valid. 

Explanation    An application to the memory block manager has passed a memory block that is not valid.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-MEMFREEERROR: Memory block 0x%8x has already been freed. 

Explanation    An application to the memory block manager has attempted to free or lock a memory block that is not allocated.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-MUTEXFAIL: mutex %s operation on %s in %s failed; reason %s 

Explanation    Mutex operation failed in the packet server

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-NEXTBLOCKERROR: The next block after buffer 0x%8x (packet 
0x%8x) has been corrupted. 

Explanation    Data has been written past the end of the current buffer causing memory to be corrupted.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-PTHREADCREATEFAIL: pthread create fail in pakman while 
creating the %s thread 

Explanation    packet manager server unable to create a new thread

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-PTHREADMUTEXFAIL: pthread_mutex_init failed on packet mutex. 
Reason : %s 

Explanation    The packet manager failed to initialize the global mutex

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-SHMCREATEFAIL: Error in creating the shared buffer mem: %s 

Explanation    Fatal error encountered while creating shared packet buffers

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message    %PACKET-2-SHMCTLFAIL: Error in shm_ctl: %s 

Explanation    Fatal error encountered while doing the shm_ctl operations on the shared packet memory

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.