Cisco IE 3010 Switch System Message Guide, Cisco IOS Release 15.0(2)SE

ACLMGR Messages
AUTHMGR Messages
BACKUP_INTERFACE Messages
CMP Messages
DHCP_SNOOPING Messages
DOT1X Messages
DOT1X_SWITCH Messages
DTP Messages
DWL Messages
EC Messages
ENVIRONMENT Messages
EPM Messages
ETHCNTR Messages
EXPRESS_SETUP Messages
FLASH_DEVICE Messages
GBIC_SECURITY Messages
GBIC_SECURITY_CRYPT Messages
HARDWARE Messages
HLFM Messages
IDBMAN Messages
IFMGR Messages
IGMP_QUERIER Messages
ILET Messages
ILPOWER Messages
IP_DEVICE_TRACKING_HA Messages
KEYMAN Messages
MAC_LIMIT Messages
MAC_MOVE Messages
PHY Messages
PLATFORM Messages
PLATFORM_ENV Messages
PLATFORM FRULink 10G Service Module Messages
PLATFORM_IPv6 Messages
PLATFORM_PM Messages
PLATFORM_RPC Messages
PLATFORM_VLAN Messages
PM Messages
PORT_SECURITY Messages
QOSMGR Messages
REP Messages
RMON Messages
SCHED Messages
SESA Messages
SPAN Messages
SPANTREE Messages
SPANTREE_FAST Messages
SPANTREE_VLAN_SW Messages
STORM_CONTROL Messages
SUDI Messages
SUPERVISOR Messages
SUPQ Messages
SW_MACAUTH Messages
SW_VLAN Messages
SWITCH_QOS_TB Messages
TCAMMGR Messages
UDLD Messages
VQPCLIENT Messages

Message and Recovery Procedures

This chapter describes the Cisco IE 3010 switch system messages in alphabetical order by facility. Within each facility, the messages are listed by severity levels 0 to 7: 0 is the highest severity level, and 7 is the lowest severity level. Each message is followed by an explanation and a recommended action.

Note The messages listed in this chapter do not include the hostname or the date/time-stamp designation that appears only if the software is configured for system log messaging.

•ACLMGR Messages

•AUTHMGR Messages

•BACKUP_INTERFACE Messages

•CMP Messages

•DHCP_SNOOPING Messages

•DOT1X Messages

•DOT1X_SWITCH Messages

•DTP Messages

•DWL Messages

•EC Messages

•ENVIRONMENT Messages

•EPM Messages

•ETHCNTR Messages

•EXPRESS_SETUP Messages

•FLASH_DEVICE Messages

•GBIC_SECURITY Messages

•GBIC_SECURITY_CRYPT Messages

•IGMP_QUERIER Messages

•ILET Messages

•ILPOWER Messages

•IP_DEVICE_TRACKING_HA Messages

•PLATFORM_ENV Messages

•PLATFORM FRULink 10G Service Module Messages

•PLATFORM_IPv6 Messages

•PLATFORM_PM Messages

•PLATFORM_RPC Messages

•PLATFORM_VLAN Messages

•PM Messages

•PORT_SECURITY Messages

•SPANTREE_FAST Messages

•SPANTREE_VLAN_SW Messages

•STORM_CONTROL Messages

•SWITCH_QOS_TB Messages

•TCAMMGR Messages

•UDLD Messages

•VQPCLIENT Messages

ACLMGR Messages

This section contains the access control list (ACL) manager messages. Most messages in this section are the result of a switch memory shortage, which includes hardware memory and label space but not CPU memory. Both kinds of memory shortages are described.

Error Message    ACLMGR-2-NOMAP: Cannot create ACL Manager data structures for VLAN Map 
[chars].

Explanation The ACL manager could not allocate the data structures needed to describe a VLAN map into a form that can be loaded into the hardware. This is most likely caused by lack of free memory. [chars] is the VLAN map name.

Recommended Action Reduce other system activity to ease memory demands.

Error Message    ACLMGR-2-NOVLB: Cannot create memory block for VLAN [dec].

Explanation The ACL manager could not save per-VLAN information needed for its correct operation. Some per-interface features, such as access groups or VLAN maps, will not be configured correctly. [dec] is the VLAN ID.

Recommended Action Use a less complicated configuration that requires less memory.

Error Message    ACLMGR-2-NOVMR: Cannot generate hardware representation of access list 
[chars]

Explanation Available resources are not sufficient to create a hardware representation of the ACL. This is caused by the lack of available logical operation units or specialized hardware resources. Logical operation units are needed for a TCP flag match or a test other than eq (ne, gt, lt, or range) on TCP, UDP, or SCTP port numbers.

Recommended Action Modify the ACL configuration to use fewer resources, or rename the ACL with a name or number that alphanumerically precedes the other ACL names or numbers.

Error Message    ACLMGR-3-ACLTCAMFULL: Acl Tcam Full. Drop packets on Output Acl label 
[dec] on [chars] [chars].

Explanation The platform-specific TCAM cannot support the number of configured ACLs. [dec] is the label number, the first [chars] is Layer 3, and the second [chars] is Layer 2. If only one layer of TCAM is full, only one string is displayed, and the other string is NULL.

Recommended Action Reduce the number of IP or MAC access lists to be applied to interfaces.

Error Message    ACLMGR-3-AUGMENTFAIL: Augmenting of access-map [chars] on [chars] 
label [dec] failed.

Explanation The system ran out of CPU DRAM when trying to merge internally required elements with the configured access maps. The first [chars] is the access-map name, the second [chars] is the direction in which the map was applied (input or output), and [dec] is the label number.

Recommended Action Reduce other system activity to ease memory demands.

Error Message    ACLMGR-3-IECPORTLABELERROR: ACL labels are out-of-sync on interface 
[chars], label [dec] is not available on asic [dec].

Explanation An internal software error has occurred. [chars] is the interface name. The first [dec] is the label associated with the ACL, and the second [dec] is the ASIC number.

Error Message    ACLMGR-3-INSERTFAIL: Insert of access-map [chars] #[dec] into [chars] 
label [dec] failed.

Explanation The system ran out of CPU memory when trying to merge sections of an access map. The first [chars] is the map name, and the second [chars] is the direction in which the map was applied. The first [dec] is the entry number, and the second [dec] is the label number.

Recommended Action Reduce other system activity to ease memory demands. For example, remove any ACLs that have been defined but not used. Use simpler ACLs with fewer access control entries (ACEs). Use fewer VLANs, and remove any unneeded VLANs from the VLAN database.

Error Message    ACLMGR-3-INTTABLE: Not in truth table: VLMAP [dec] RACL [dec] Mcb [dec] 
Feat [dec].

Explanation An unrecoverable software error occurred while trying to merge the configured input features. [dec] are internal action codes.

Error Message    ACLMGR-3-MAXRECURSION: Too many ([dec]) levels of recursion while 
merging ACLs (code [dec]).

Explanation The configuration is too complicated for the platform-specific ACL merge code to support. The most likely cause is too many separate access lists in a single VLAN map or policy map. The first [dec] is the number of levels of recursion. The second [dec] is an internal code number of the merge stage that encountered the problem.

Recommended Action Reduce the number of IP or MAC access lists (considered separately) in any one VLAN or policy map to fewer than the number of levels reported by this log message.

Error Message    ACLMGR-3-MERGEFAIL: [chars] ACL merge error [dec] ([chars]) on [chars] 
label [dec].

Explanation The ACL manager could not complete the merge of the configured features into a form suitable for loading into the hardware. Packets potentially affected by this feature will be sent to the CPU for processing. The most likely cause is specifying an ACL that is too large or too complex for the system. The first [chars] is the ACL-type error (ip or mac), the first [dec] is the error code, the second [chars] is the message string for the preceding error code, the second [dec] is the label number, and the third [chars] is either input or output.

Recommended Action Specify a smaller and less complicated configuration.

Error Message    ACLMGR-3-NOLABEL: Cannot allocate [chars] label for interface [chars].

Explanation The ACL manager could not allocate a label for the features on this interface. This means that the hardware cannot be programmed to implement the features, and packets for this interface will be filtered in software. There is a limit of 256 labels per direction. The first [chars] is the direction (input or output), and the second [chars] is the interface name.

Recommended Action Use a simpler configuration. Use the same ACLs on multiple interfaces, if possible.

Error Message    ACLMGR-3-OUTTTABLE: Not in truth table: RACL [dec] VLMAP [dec].

Explanation An unrecoverable software error occurred while trying to merge the configured output features. [dec] are internal action codes.

Error Message    ACLMGR-3-QOSTTABLE: Not in truth table: ACL [dec] in map, action [dec].

Explanation Asoftware error occurred while trying to merge a quality of service (QoS) policy map. The first [dec] is the ACL number, and the second [dec] is the action corresponding to the specified ACL number.

Error Message    ACLMGR-3-RELOADED: Reloading [chars] label [dec] feature.

Explanation The ACL manager can now load more of the configured features on this label into the hardware. One or more features had previously been unloaded because of lack of space. [chars] is the direction (input or output), and [dec] is the label number.

Recommended Action No action is required.

Error Message    ACLMGR-3-UNKNOWNACTION: Unknown VMR access group action [hex].

Explanation An internal software error has occurred. [hex] is an internal action code.

Error Message    ACLMGR-3-UNLOADING: Unloading [chars] label [dec] feature.

Explanation The ACL manager could not load the complete configuration into the hardware, so only few features will be applied in the software. Some or all of the packets in a VLAN are forwarded by the CPU. Multicast packets might be dropped entirely instead of being forwarded. [chars] is the direction (input or output), and [dec] is the label number.

Recommended Action Use a simpler configuration. Use the same ACLs on multiple interfaces, if possible.

AUTHMGR Messages

Error Message    AUTHMGR-0-CONFIG_CORRUPT,MSGDEF_LIMIT_MEDIUM: Checksummed interface 
configuration corruption detected.

Explanation There was an unexpected modification in the interface configuration field.

Recommended Action No action is required.

Error Message    AUTHMGR-4-UNAUTH_MOVE, MSGDEF_LIMIT_MEDIUM: [chars] MAC address 
([enet]) from [chars] to [chars]

Explanation There was an authenticated move on the old IDB. The first [chars] is slow or fast, the second [chars] is the source interface name, the third [chars] is the destination interface name, and [enet] is the MAC address.

Recommended Action No action is required.

Error Message    AUTHMGR-4-ILLEGAL_TRACE_REQ: Component ID [dec] not registered.

Explanation There was an attempt to log a message with an unregistered ID. [dec] is the component ID.

Recommended Action No action is required.

Error Message    AUTHMGR-5-SECURITY_VIOLATION: Security violation on the interface 
[chars], new MAC address ([enet) is seen. AuditSessionID [chars]

Explanation The interface host mode limits the number of hosts that can be attached to an interface. The limit was exceeded and caused a security violation. The interface is error disabled. The first [chars] is the interface, [enet] is the host MAC address, and the second [chars] is the session ID.

Recommended Action Reconfigure the interface to support the number of attached hosts. Enter the shutdown interface configuration command followed by the no shutdown interface configuration command to re-enable the interface.

Error Message    AUTHMGR-5-VLANASSIGN: VLAN [dec] assigned to Interface [chars] 
AuditSessionID [chars]

Explanation A VLAN was assigned. [dec] is the VLAN ID, the first [chars] is the interface, and the second [chars] is the session ID.

Recommended Action No action is required.

Error Message    AUTHMGR-7-FAILOVER: Failing over from [chars] for client ([chars]) on 
Interface [chars] AuditSessionID [chars]

Explanation The authorization manager is failing over from the current authentication method to another method. The first [chars] is the current authentication method, the second [chars] is the client ID, the third [chars] is the interface, and the fourth [chars] is the session ID.

Recommended Action No action is required.

Error Message    AUTHMGR-7-NOMOREMETHODS: Exhausted all authentication methods for 
client ([chars]) on Interface [chars] AuditSessionID [chars]

Explanation All available authentication methods have been tried for the client, but authentication failed. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.

Recommended Action No action is required. If local authorization has been configured, the port is authorized based on the local authorization method. Otherwise, authentication restarts according to the configured reauthentication period.

Error Message    AUTHMGR-7-RESULT: Authentication result [chars] from [chars] for 
client [chars] on Interface [chars] AuditSessionID [chars]

Explanation Notification message. The first [chars] is the status of the authentication, the second [chars] is the authentication method, the third [chars] is the client ID, the fourth [chars] is the interface, and the fifth [chars] is the session ID.

Recommended Action No action is required.

BACKUP_INTERFACE Messages

Error Message    BACKUP_INTERFACE-5-PREEMPT: Preempting interface [chars] in backup 
pair ([chars], [chars]), preemption mode is [chars]

Explanation The switch is pre-empting the current forwarding interface in the backup interface pair. The first [chars] is the number of the current forwarding interface. The second and third [chars] are the names of the interfaces in the backup pair, and the fourth [chars] is the pre-emption mode.

Recommended Action No action is required.

Error Message    BACKUP_INTERFACE-5-VLB_NON_TRUNK: Warning:  Flexlink VLB is not 
allowed on non-trunk ports.  Please configure [chars] to be a trunk port.

Explanation Flex Link VLAN load-balancing (VLB) detects a nontrunk port. [chars] is the interface name.

Recommended Action Change the interface to trunking mode.

CMP Messages

Error Message    CMP-4-MEM_CMPIP_ADDR_CONFLICT: Conflict with CMP IP address 
[IP_address], Reissuing a new CMP IP address to member [dec]

Explanation The cluster commander found a conflict with the assigned CMP IP address of the member. A new unique CMP IP address is assigned to the member. [dec] is the member number.

Recommended Action This is only a warning message. The commander has already assigned the cluster member a new unique address. Clear any open TCP connections on the member by using clear tcp privileged EXEC command.

Error Message    CMP-5-ADD: The Device is added to the cluster (Cluster Name: [chars], 
CMDR IP Address [IP_address]).

Explanation The device is added to the cluster. [chars] is the cluster name, and [IP_address] is the Internet address of the command switch.

Recommended Action No action is required.

Error Message    CMP-5-MEMBER_CONFIG_UPDATE: Received member configuration from member 
[dec].

Explanation The active or standby command switch received a member configuration. [dec] is the member number of the sender.

Recommended Action No action is required.

Error Message    CMP-5-MGMT_VLAN_CHNG: The management vlan has been changed to [dec].

Explanation The management VLAN has changed. [dec] is the new management VLAN ID.

Recommended Action No action is required.

Error Message    CMP-5-NBR_UPD_SIZE_TOO_BIG: Number of neighbors in neighbor update is 
[int], maximum number of neighbors allowed in neighbor update is [int].

Explanation The number of cluster neighbors in the clustering neighbor update packet exceeds the number of neighbors supported by the clustering module. The first [int] is the new number of neighbors, and the second [int] the maximum number of neighbors.

Recommended Action No action is required.

Error Message    CMP-5-REMOVE: The Device is removed from the cluster (Cluster Name: 
[chars]).

Explanation The device is removed from the cluster. [chars] is the cluster name.

Recommended Action No action is required.

DHCP_SNOOPING Messages

Error Message    DHCP_SNOOPING-3-DHCP_SNOOPING_INTERNAL_ERROR: DHCP Snooping internal 
error, [chars].

Explanation Asoftware sanity check failed in the DHCP snooping process. [chars] is the error.

Error Message    DHCP_SNOOPING-4-AGENT_OPERATION_FAILED: DHCP snooping binding 
transfer failed. [chars].

Explanation The DHCP snooping binding transfer process failed. [chars] is the reason the process failed.

Recommended Action No action is required.

Error Message    DHCP_SNOOPING-4-AGENT_OPERATION_FAILED_N: DHCP snooping binding 
transfer failed ([dec]). [chars].

Explanation The DHCP snooping binding transfer process failed. This message is rate-limited. [dec] is the number of times the process failed, and [chars] is the reason the process failed.

Recommended Action No action is required.

Error Message    DHCP_SNOOPING-4-DHCP_SNOOPING_ERRDISABLE_WARNING: DHCP Snooping 
received [dec] DHCP packets on interface [chars].

Explanation The switch detected a DHCP packet rate-limit violation on the specified interface and put the interface in the error disabled state. [dec] is the number of DCHP packets, and [chars] is the interface.

Recommended Action No action is required.

Error Message    DHCP_SNOOPING-4-DHCP_SNOOPING_PVLAN_WARNING: DHCP Snooping 
configuration may not take effect on secondary vlan [dec]. [chars]

Explanation Warning message. If the private VLAN feature is configured, the DHCP snooping configuration on the primary VLAN automatically propagates to all the secondary VLANs. [dec] is the VLAN ID of the secondary VLAN, and [chars] is the warning.

Recommended Action No action is required.

Error Message    DHCP_SNOOPING-4-IP_SOURCE_BINDING_NON_EXISTING_VLAN_WARNING: IP 
source binding is configured on non existing vlan [dec].

Explanation An IP source binding was configured on a VLAN that has not been configured yet. [dec] is the VLAN.

Recommended Action No action is required.

Error Message    DHCP_SNOOPING-4-IP_SOURCE_BINDING_PVLAN_WARNING: IP source filter may 
not take effect on secondary vlan [dec] where IP source binding is configured. 
[chars].

Explanation Warning message. If private VLANs are configured, the IP-source-guard filter on the primary VLAN automatically propagates to all secondary VLANs. [dec] is the secondary VLAN, and [chars] is the warning.

Recommended Action No action is required.

Error Message    DHCP_SNOOPING-4-NTP_NOT_RUNNING: NTP is not running; reloaded binding 
lease expiration times are incorrect.

Explanation If the DHCP snooping database agent loads the DHCP snooping bindings and Network Time Protocol (NTP) is not running, the calculated lease duration for the bindings is incorrect.

Recommended Action Configure NTP on the switch to provide an accurate time and date for the system clock. Then disable and re-enable DHCP snooping to clear the DHCP snooping binding database.

Error Message    DHCP_SNOOPING-4-QUEUE_FULL: Fail to enqueue DHCP packet into 
processing queue: [chars], the queue is most likely full and the packet will be 
dropped.

Explanation The CPU is receiving DHCP at a higher rate than the DHCP snooping can process. These DHCP packets are dropped to prevent a denial of service attack. [chars] is the warning.

Recommended Action No action is required.

Error Message    DHCP_SNOOPING-4-STANDBY_AGENT_OPERATION_FAILED: DHCP snooping binding 
transfer failed on the Standby Supervisor. [chars].

Explanation The DHCP snooping binding transfer process failed on a standby supervisor engine. [chars] is the standby supervisor engine.

Recommended Action No action is required.

Error Message    DHCP_SNOOPING-6-AGENT_OPERATION_SUCCEEDED: DHCP snooping database 
[chars] succeeded.

Explanation The DHCP binding transfer process succeeded. [chars] is the DCHP snooping database.

Recommended Action No action is required.

Error Message    DHCP_SNOOPING-6-BINDING_COLLISION: Binding collision. [dec] bindings 
ignored.

Explanation The specified number of bindings were ignored when the switch read the database file. The bindings from the database file have MAC address and VLAN information that a configured DHCP snooping binding already uses.

Recommended Action No action is required.

Error Message    DHCP_SNOOPING-6-INTERFACE_NOT_VALID: Interface not valid. [dec] 
bindings ignored.

Explanation The specified number of bindings were ignored when the switch read the database file because the interface in binding database is not available, the interface is a routed port, or the interface is a DHCP snooping-trusted Layer 2 interface. [dec] is the number of bindings that the switch ignores.

Recommended Action No action is required.

Error Message    DHCP_SNOOPING-6-LEASE_EXPIRED: Lease Expired. [dec] bindings ignored.

Explanation The specified number of bindings were ignored when the switch read the database file because the DHCP lease expired. [dec] is the number of bindings.

Recommended Action No action is required.

Error Message    DHCP_SNOOPING-6-PARSE_FAILURE: Parsing failed for [dec] bindings.

Explanation The specified number of bindings were ignored when the switch read the database file because the database read operation failed. [dec] is the number of bindings.

Recommended Action No action is required.

Error Message    DHCP_SNOOPING-6-VLAN_NOT_SUPPORTED: Vlan not supported. [dec] bindings 
ignored.

Explanation The specified number of bindings were ignored when the switch read the database file because the VLAN is not configured on the switch. [dec] is the number of bindings that the switch ignores.

Recommended Action No action required.

DOT1X Messages

Error Message    DOT1X-4-PROC_START_ERR: Dot1x unable to start.

Explanation The system did not start the 802.1x process.

Recommended Action Restart the 802.1x process by entering the dot1x system-auth-control global configuration command. If this message recurs, reload the device.

Error Message    DOT1X-4-UNKN_ERR: An unknown operational error occurred.

Explanation The 802.1x process cannot operate because of an internal system error.

Recommended Action Reload the device.

Error Message    DOT1X-5-FAIL: Authentication failed for client ([chars]) on Interface 
[chars]

Explanation Authentication was unsuccessful. The first [chars] is the hostname, and the second [chars] is the interface.

Recommended Action No action is required.

Error Message    DOT1X-4-MEM_UNAVAIL: Memory was not available to perform the 802.1X 
action. AuditSessionID [chars]

Explanation The switch does not have enough memory to run 802.1x authentication. [chars] is the session ID.

Recommended Action Reconfigure the switch to reduce memory usage.

Error Message    DOT1X-5-FAIL: Authentication failed for client ([chars]) on Interface 
[chars] AuditSessionID [chars]

Explanation The authentication was unsuccessful. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.

Recommended Action No action is required.

Error Message    DOT1X-5-SUCCESS: Authentication successful for client ([chars]) on 
Interface [chars] AuditSessionID [chars]

Explanation Authentication was successful. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.

Recommended Action No action is required.

Error Message    DOT1X-5-RESULT_OVERRIDE: Authentication result overridden for client 
([chars]) on Interface [chars] AuditSessionID [chars]

Explanation The authentication result was overridden. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.

Recommended Action No action is required.

DOT1X_SWITCH Messages

Error Message    DOT1X_SWITCH-4-PROC_START_ERR: Unable to start dot1x switch process.

Explanation The software could not start the 802.1x authentication process.

Recommended Action Use the reload privileged EXEC command to reload the switch.

Error Message    DOT1X_SWITCH-5-ERR_INVALID_PRIMARY_VLAN: Attempt to assign primary 
VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]

Explanation An attempt was made to assign a primary VLAN to an 802.1x port, which is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action Use a different VLAN.

Note This message applies to switches running the IP base image.

Error Message    DOT1X_SWITCH-5-ERR_INVALID_SEC_VLAN: Attempt to assign invalid 
secondary VLAN [dec] to PVLAN host 802.1x port [chars] AuditSessionID [chars]

Explanation An attempt was made to assign a nonsecondary VLAN to a private VLAN host 802.1x port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action Change the port mode so that it is not a PVLAN host port, or use a valid secondary VLAN.

Note This message applies to switches running the IP base image.

Error Message    DOT1X_SWITCH-5-ERR_PRIMARY_VLAN_NOT_FOUND: Attempt to assign VLAN 
[dec], whose primary VLAN does not exist or is shutdown, to 802.1x port [chars] 
AuditSessionID [chars]

Explanation An attempt was made to assign a private VLAN whose primary VLAN does not exist or is shut down. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action Check that the primary VLAN exists and is not shut down. Verify that the private VLAN is associated with a primary VLAN.

Note This message applies to switches running the IP base image.

Error Message    DOT1X_SWITCH-5-ERR_RADIUS_VLAN_NOT_FOUND: Attempt to assign 
non-existent VLAN [chars] to dot1x port [chars]

Explanation RADIUS attempted to assign a VLAN with a particular name or ID to a supplicant on a port, but the name or ID could not be found on the switch. [dec] is the VLAN, and [chars] is the port.

Recommended Action Check a VLAN with the specified name or ID exists on the switch.

Error Message    DOT1X_SWITCH-5-ERR_SEC_VLAN_INVALID: Attempt to assign secondary VLAN 
[dec] to non-PVLAN host 802.1x port [chars] AuditSessionID [chars]

Explanation An attempt was made to assign a secondary VLAN to a port that is not a private VLAN host port, which is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action Change the port mode so that it is configured as a private VLAN host port, or use a different VLAN that is not configured as a secondary VLAN.

Error Message    DOT1X_SWITCH-5-ERR_SPAN_DST_PORT: Attempt to assign VLAN [dec] to 
802.1x port [chars], which is configured as a SPAN destination AuditSessionID 
[chars]

Explanation An attempt was made to assign a VLAN to an 802.1x port that is configured as a Switched Port Analyzer (SPAN) destination port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action Change the SPAN configuration so that the port is not a SPAN destination port, or change the configuration so that no VLAN is assigned.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_EQ_MDA_INACTIVE: Multi-Domain Authentication 
cannot activate because Data and Voice VLANs are the same on port AuditSessionID 
[chars]

Explanation Multi-Domain Authentication (MDA) host mode cannot start when the configured data VLAN on a port is the same as the voice VLAN. [chars] is the port session ID.

Recommended Action Change either the voice VLAN or the data VLAN on the interface so that they are not the same. MDA then starts.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_EQ_VVLAN: Data VLAN [dec] on port [chars] 
cannot be equivalent to the Voice VLAN AuditSessionID [chars]

Explanation An attempt was made to assign a data VLAN to an 802.1x port that is the same as the voice VLAN. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action Change either the voice VLAN or the 802.1x-assigned VLAN on the interface so that they are not the same.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_INTERNAL: Attempt to assign internal VLAN 
[dec] to 802.1x port [chars] AuditSessionID [chars]

Explanation An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is used internally and cannot be assigned to this port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action Assign a different VLAN.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_INVALID: Attempt to assign invalid VLAN [dec] 
to 802.1x port [chars] AuditSessionID [chars]

Explanation An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is out of range. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action Update the configuration to use a valid VLAN.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_ON_ROUTED_PORT: Attempt to assign VLAN [dec] 
to routed 802.1x port [chars] AuditSessionID [chars]

Explanation An attempt was made to assign a VLAN to a supplicant on a routed port, which is not allowed. [dec] is the VLAN ID, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action Either disable the VLAN assignment, or change the port type to a nonrouted port.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_PROMISC_PORT: Attempt to assign VLAN [dec] to 
promiscuous 802.1x port [chars] AuditSessionID [chars]

Explanation An attempt was made to assign a VLAN to a promiscuous 802.1x port, which is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action Change the port mode so that it is not a promiscuous port, or change the configuration so that no VLAN is assigned.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_RESERVED: Attempt to assign reserved VLAN 
[dec] to 802.1x port [chars] AuditSessionID [chars]

Explanation An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is a reserved VLAN and cannot be assigned to this port. [dec] is the VLAN, the first [chars] is the port, and the seconds [chars] is the session ID.

Recommended Action Assign a different VLAN.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_RSPAN: Attempt to assign RSPAN VLAN [dec] to 
802.1x port [chars]. 802.1x is incompatible with RSPAN AuditSessionID [chars]

Explanation Remote SPAN should not be enabled on a VLAN with 802.1x-enabled. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action Either disable remote SPAN configuration on the VLAN, or disable 802.1x on all the ports in this VLAN.

Error Message    DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on 
[chars] AuditSessionID [chars]

Explanation The client MAC address could not be added to the MAC address table because the hardware memory is full or the address is a secure address on another port. This message might appear if 802.1x is enabled. [enet] is the client MAC address, the first [chars] is the interface, and the second [chars] is the session ID.

Recommended Action If the hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, remove it from that port.

Note This messages applies to switches running the IP base image.

Error Message    DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND: Attempt to assign non-existent or 
shutdown VLAN [chars] to 802.1x port [chars] AuditSessionID [chars]

Explanation An attempt was made to assign a VLAN to an 802.1x port, but the VLAN was not found in the VLAN Trunking Protocol (VTP) database. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.

Recommended Action Check the VLAN exists and is not shut down, or use another VLAN.

DTP Messages

Error Message    DTP-4-MEM_UNAVAIL: Memory was not available to perform the trunk 
negotiation action.

Explanation The system cannot negotiate trunks because of lack of memory.

Recommended Action Reduce other system activity to ease memory demands.

Error Message    DTP-4-TMRERR: An internal timer error occurred when trunking on 
interface [chars].

Explanation A timer used by the trunking protocol unexpectedly expired. [chars] is the trunked interface.

Recommended Action This problem is corrected internally and has no long-term ramifications. However, if more problems with trunking occur, reload the switch by using the reload privileged EXEC command.

Error Message    DTP-4-UNKN_ERR: An unknown operational error occurred.

Explanation The system cannot negotiate trunks because an internal operation generated an unexpected error.

Recommended Action Reload the switch by using the reload privileged EXEC command.

Error Message    DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port 
[chars] because of VTP domain mismatch.

Explanation The two ports in the trunk negotiation belong to different VLAN Trunking Protocol (VTP) domains. Trunking can be configured only when the ports belong to the same VTP domain. [chars] is the port number.

Recommended Action Check that the ports in the trunk negotiation belong to the same VTP domain.

Error Message    DTP-5-ILGLCFG: Illegal config (on, isl--on,dot1q) on [chars].

Explanation One end of the trunk link is configured as on with ISL encapsulation and the other end is configured as on with 802.1Q encapsulation. [chars] is the interface.

Recommended Action This configuration is illegal and will not establish a trunk between two switches. You must change the encapsulation type so that both ends of the trunk match.

Error Message    DTP-5-NONTRUNKPORTON: Port [chars] has become non-trunk.

Explanation The interface changed from a trunk port to an access port. [chars] is the interface that changed.

Recommended Action This message is provided only for information.

Error Message    DTP-5-TRUNKPORTCHG: Port [chars] has changed from [chars] trunk to 
[chars] trunk.

Explanation The encapsulation type of the trunk port has changed. The first [chars] is the interface, the second is the original encapsulation type, and the third [chars] is the new encapsulation type.

Recommended Action This message is provided only for information.

Error Message    DTP-5-TRUNKPORTON: Port [chars] has become [chars] trunk.

Explanation The interface has changed from an access port to a trunk port. The first [chars] is the interface, and the second [chars] is the encapsulation type.

Recommended Action This message is provided only for information.

DWL Messages

This section contains down-when-looped (DWL) messages. This feature disables an interface when a loopback is detected.

Error Message    DWL-3-LOOP_BACK_DETECTED: Loop-back detected on [chars].

Explanation There is a loopback on the specified port. The cause might be a Token-Ring Type-1 cable connected to the port or a misconfiguration in the network. [chars] is the port.

Recommended Action Correct the problem that is causing the loopback condition. Then enter the shutdown and the no shutdown interface configuration commands.

EC Messages

Error Message    EC-4-NOMEM: Not enough memory available for [chars].

Explanation Either the LACP or the PAgP EtherChannel could not obtain the memory it needed to initialize the required data structures. [chars] is the data structure name.

Error Message    EC-5-BUNDLE: Interface [chars] joined port-channel [chars].

Explanation The listed interface joined the specified EtherChannel. The first [chars] is the physical interface, and the second [chars] is the EtherChannel interface.

Recommended Action No action is required.

Error Message    EC-5-CANNOT_ALLOCATE_AGGREGATOR: Aggregator limit reached, cannot 
allocate aggregator for group [dec].

Explanation A new aggregator cannot be allocated in the group. [dec] is the affected group.

Recommended Action Change the port attributes of the ports in the group so that they match and join the same aggregator.

Error Message    EC-5-CANNOT_BUNDLE1: Port-channel [chars] is down, port [chars] will 
remain stand-alone.

Explanation The aggregation port is down. The port remains standalone until the aggregation port is up. The first [chars] is the EtherChannel, and the second [chars] is the port number.

Recommended Action Check that the other ports in the bundle have the same configuration.

Error Message    EC-5-CANNOT_BUNDLE2: [chars] is not compatible with [chars] and will 
be suspended ([chars]).

Explanation The interface has different interface attributes than the other ports in the EtherChannel. For the interface to join the bundle (EtherChannel), change the interface attributes to match the EtherChannel attributes. The first [chars] is the interface to be bundled, the second [chars] is the physical interface (a switch port or a routed port) that is already in the bundle, and the third [chars] is the reason for the incompatibility.

Recommended Action Change the interface attributes to match the EtherChannel attributes.

Error Message    EC-5-CANNOT_BUNDLE_LACP: [chars] is not compatible with aggregators in 
channel [dec] and cannot attach to them ([chars]).

Explanation The port has different port attributes than the port channel or ports within the port channel. [chars] is the incompatible port, [dec] is the channel group number, and the last [chars] is the reason.

Recommended Action For the port to join the bundle, change the port attributes so that they match the port.

Error Message    EC-5-COMPATIBLE: [chars] is compatible with port-channel members.

Explanation A port was not operational because its attributes were different from those of the port channel or ports within the port channel. The system has detected that the attributes of the port now match the port-channel attributes. [chars] is the affected port.

Recommended Action No action is required.

Error Message    EC-5-DONTBNDL: [chars] suspended: incompatible remote port with 
[chars]

Explanation The configuration of the remote port is different from the configuration of other remote ports in the bundle. A port can only join the bundle when the configuration of the local port and the configuration of the remote port are the same as other ports already in the bundle. The first [chars] is the name of the local interface that is being suspended, and the second [chars] is the name of the local interface that is already bundled.

Recommended Action Check that the configuration of the remote ports is the same for all ports in the bundle.

Error Message    EC-5-ERRPROT: Channel protocol mismatch for interface [chars] in group 
[dec]: the interface can not be added to the channel group.

Explanation The interface cannot be added to the channel group with the specified mode. [chars] is the interface, and [dec] is the channel group.

Recommended Action Change the channel group or the mode for the interface.

Error Message    EC-5-ERRPROT2: Command rejected: the interface [chars] is already part 
of a channel with a different type of protocol enabled.

Explanation The interface cannot be selected for the specified protocol because it is already part of a channel with a different protocol. [chars] is the interface.

Recommended Action Remove the interface from the channel group.

Error Message    EC-5-ERRPROT3: Command rejected: the interface [chars] is already part 
of a channel.

Explanation The interface cannot be unselected for the specified protocol because it is already part of a channel group. [chars] is the interface.

Recommended Action Remove the interface from the channel group.

Error Message    EC-5-MINLINKS_MET: Port-channel [chars] is up as its bundled ports 
([dec]) meets min-links

Explanation The administrative configuration of minimum links is equal to or less than the number of EtherChannel ports. The port channel is up. [chars] is the EtherChannel, and [dec] is the EtherChannel group number.

Recommended Action No action is required.

Error Message    EC-5-MINLINKS_NOTMET: Port-channel [chars] is down bundled ports 
([dec]) doesn't meet min-links

Explanation The administrative configuration of minimum links is greater than the number of bundled ports. The port channel is down. [chars] is the EtherChannel, and [dec] is the EtherChannel group number.

Recommended Action Reduce the value of the minimum-links configuration parameter for an EtherChannel, or add more ports to the EtherChannel to create a bundle.

Error Message    EC-5-NOLACP: Invalid EC mode, LACP not enabled.

Explanation The EtherChannel mode cannot be set because LACP is not included in the software image.

Recommended Action Install a software image that includes LACP, and set the EC mode to on.

Error Message    EC-5-NOPAGP: Invalid EC mode, PAgP not enabled.

Explanation PAgP is not included in the Cisco IOS image and the EtherChannel mode cannot be set to desirable or auto.

Recommended Action Obtain an image with PAgP included, or set the mode to on by using the channel-group channel-group-number mode on interface configuration command.

Error Message    EC-5-PORTDOWN: Shutting down [chars] as its port-channel is 
admin-down.

Explanation The administrative state of the port is controlled by the administrative state of its aggregate port. If the administrative state of the aggregate port is down, the administrative state of the port is also forced to be down. [chars] is the physical interface.

Recommended Action Enter the no shutdown interface configuration command on the aggregate port to activate the aggregation port.

Error Message    EC-5-STAYDOWN: [chars] will remain down as its port-channel [chars] is 
admin-down.

Explanation The administrative state of the aggregation port overrides that of the affected port. If the aggregation port is administratively down, all ports in the aggregation port are forced to be administratively down. The first [chars] is the physical interface, and the second [chars] is the EtherChannel.

Recommended Action Enter the no shutdown interface configuration command on the aggregation port to activate (unshut) the aggregation port.

Error Message    EC-5-STAYDOWN: no-shut not allowed on [chars]. Module [dec] not online.

Explanation An interface with an EtherChannel configuration cannot be enabled by using the no shutdown interface configuration command because it is a member of an EtherChannel group and that group has been administratively shut down. The interface has an EtherChannel configuration, but no information is available yet about its port channel. [chars] is the interface, and [dec] is the module.

Recommended Action No action is required. Wait until the module is online to find out the port-channel setting of the EtherChannel.

Error Message    EC-5-UNBUNDLE: Interface [chars] left the port-channel [chars].

Explanation The listed interface left the specified EtherChannel. The first [chars] is the physical interface, which can be a switch port or a routed port, and the second [chars] is the EtherChannel.

Recommended Action No action is required.

Error Message    EC-5-UNSUITABLE: [chars] will not join any port-channel, [chars].

Explanation This message means that one of the interfaces cannot join the EtherChannel because it is configured for PortFast, as a VLAN Membership Policy Server (VMPS), for 802.1x, as a voice VLAN, or as a SPAN destination port. All of these are illegal configurations for EtherChannels. The first [chars] is the interface name, and the second [chars] describes the details of the illegal configuration.

Recommended Action Reconfigure the port by removing the illegal configuration.

ENVIRONMENT Messages

Error Message    ENVIRONMENT-2-PS_A_HIGHVOLTAGE: [chars] [chars] [chars] [chars] 
[chars]

Explanation The power supply input voltage has exceeded the maximum threshold. This could be caused by the operational environment or faulty components. The first [chars] is the mode, the second [chars] is the severity, the third [chars] is the description, the fourth [chars] is the alarm string, and the fifth [chars] is the error message.

Recommended Action Save the system configuration and power down the system to prevent damage caused by high voltage. If the message recurs, hardware replacement maybe necessary.

Error Message    ENVIRONMENT-2-PS_A_LOWVOLTAGE: [chars] [chars] [chars] [chars] [chars]

Explanation The power supply input voltage is below the minimum threshold. This could be caused by the operational environment or faulty components. The first [chars] is the mode, the second [chars] is the severity, the third [chars] is the description, the fourth [chars] is the alarm string, and the fifth [chars] is the error message.

Recommended Action Save the system configuration and power down the system to prevent damage caused by low voltage. If the message recurs, hardware replacement maybe necessary.

Error Message    ENVIRONMENT-2-PS_B_LOWVOLTAGE: [chars] [chars] [chars] [chars] [chars]

Explanation The power supply input voltage is below minimum threshold. This could be caused by the operational environment or faulty components. The first [chars] is the mode, the second [chars] is the severity, the third [chars] is the description, the fourth [chars] is the alarm string, and the fifth [chars] is the error message.

Recommended Action Save the system configuration and power down the system to prevent damage caused by low voltage. If the message recurs, hardware replacement maybe necessary.

Error Message    ENVIRONMENT-3-POWER_ERROR: PSU [chars] model is not supported - 
Voltage threshold monitor is skipped

Explanation There is a power supply problem. [chars] is either A or B.

Recommended Action Check the connected power supply. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

EPM Messages

Error Message    EPM-6-AUTH_ACL: POLICY [chars]| EVENT [chars]

Explanation The switch has sent or received a download request for a downloadable ACL (dACL). The first [chars] is the dACL policy. The second [chars] is the event.

Recommended Action No action is required.

ETHCNTR Messages

This section contains the Ethernet controller messages. These messages appear when the switch software fails to program the hardware, which leads to incorrect switch behavior.

Error Message    ETHCNTR-3-HALF_DUX_COLLISION_EXCEED_THRESHOLD: Collision at [chars] 
exceed threshold. Consider as loop-back.

Explanation The collisions at a half-duplex port exceeded the threshold, and the port is treated as a loopback. On switches that support Power over Ethernet (PoE), this message might be displayed when a device that can be powered by either a PoE switch port or by AC power is not being powered by an external AC power source and is connected to a port that has been configured with the power inline never interface configuration command. [chars] is the port where the threshold was exceeded.

Recommended Action On switches that support PoE, remove the device or configure the port by entering the power inline auto, shutdown, and no shutdown interface configuration commands. No action is required on non-PoE switches. The port goes into error disabled mode until the problem is resolved.

Error Message    ETHCNTR-3-LOOP_BACK_DETECTED:, Loop-back detected on [chars]. The port 
is forced to linkdown.

Explanation A keepalive packet is looped back to the port that sent the keepalive. The loopback condition might be caused by a balun cable being accidentally connected to the port, or there might be a loop in the network. [chars] is the port.

Recommended Action Examine the cables. If a balun cable is connected and the loopback condition is desired, no action is required. Otherwise, connect the correct cable, and bring the port up by entering the no shutdown interface configuration command. We do not recommend using the no keepalive interface command to disable keepalives. The cause of this network loop must be found and corrected. Although disabling keepalives prevents the port from being error-disabled, it does not resolve the cause of the problem and can affect network stability. See CSCea46385 for more information.

Error Message    ETHCNTR-3-NO_HARDWARE_RESOURCES: Not enough hardware resources. 
Shutting down [chars].

Explanation The are too many VLANs and routed ports (if the switch supports routed ports) configured. [chars] is the short interface name, or the VLAN name, such as VLAN0002.

Recommended Action Reduce the total number of VLANs and routed ports to less than 1023. To preserve configuration and connections across reboots, save the configuration.

EXPRESS_SETUP Messages

Error Message    EXPRESS_SETUP-3-UNABLE_TO_RESET_CONFIG: [chars].

Explanation The system cannot reset the configuration. [chars] explains why the reset failed. For example, error renaming config file, error removing config file, or error removing private config file.

Error Message    EXPRESS_SETUP-6-CONFIG_IS_RESET: [chars].

Explanation The configuration is reset. [chars] clarifies the reset event, such as The configuration is reset and the system will now reboot.

Error Message    EXPRESS_SETUP-6-MODE_ENTERED.

Explanation The Express Setup mode is active.

Recommended Action No action is required.

Error Message    EXPRESS_SETUP-6-MODE_EXITED.

Explanation The Express Setup mode is not active.

Recommended Action No action is required.

FLASH_DEVICE Messages

Error Message    FLASH-1-DEVICE_REMOVED: Flash device removed

Explanation The compact flash card has been removed from the switch. There is no access to the flash file system.

Recommended Action To access the flash file system, reinsert the compact flash card.

Error Message    FLASH-6-DEVICE_INSERTED: Flash device inserted

Explanation The compact flash card has been inserted into the switch. There is now access to the flash file system.

Recommended Action No action is required.

GBIC_SECURITY Messages

This section contains the Cisco Gigabit Interface Converter (GBIC) and the small form-factor pluggable (SFP) module security messages. The GBIC and SFP modules have a serial EEPROM that contains the serial number, security code, and cyclic redundancy check (CRC). When the module is inserted into the switch, the software reads the EEPROM to recompute the security code and CRC. The software generates an error message if the CRC is invalid or if the recomputed security code does not match the one stored in the EEPROM.

Note The Cisco IE 3000 switch supports SFP modules and does not support GBIC modules. Although the error message text refers to GBIC interfaces and modules, the messages from the switch actually refer to the SFP module interfaces and modules.

Error Message    GBIC_SECURITY-4-EEPROM_CRC_ERR: EEPROM checksum error for GBIC in 
[chars].

Explanation The GBIC in the specified port has invalid EEPROM data. [chars] is the port in which the GBIC is inserted.

Recommended Action Remove the GBIC from the port.

Error Message    GBIC_SECURITY-4-EEPROM_READ_ERR: Error in reading GBIC serial ID in 
[chars].

Explanation An error occurred while the switch was reading the GBIC type from the EEPROM. [chars] is the port in which the GBIC is inserted.

Recommended Action Remove the GBIC from the port.

Error Message    GBIC_SECURITY-4-EEPROM_SECURITY_ERR: GBIC in [chars] failed security 
check.

Explanation The GBIC in the specified port has invalid EEPROM data. [chars] is the port in which the GBIC is inserted.

Recommended Action Remove the GBIC from the port.

Error Message    GBIC_SECURITY-4-GBIC_INTERR: Internal error occurred in setup for GBIC 
interface [chars].

Explanation The system could not allocate resources or had some other problem during the specified SFP module interface setup. [chars] is the interface in which the SFP module is installed.

Recommended Action Reload the switch by using the reload privileged EXEC command. If the problem persists, find out more about the error by using the show tech-support privileged EXEC command. Copy the error message exactly as it appears on the console or system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

Error Message    GBIC_SECURITY-6-SFP_INSERTED: Transceiver SFP [chars] module inserted 
in [chars]

Explanation The online insertion and removal (OIR) facility detected a newly inserted transceiver module for the interface specified in the message. The first [chars] is the module, and the second [chars] is the interface.

Recommended Action No action is required.

Error Message    GBIC_SECURITY-6-SFP_REMOVED: Transceiver SFP [chars] module removed 
from [chars]

Explanation The OIR facility detected the removal of a transceiver module from the interface specified in the message. The first [chars] is the module, and the second [chars] is the interface.

Recommended Action No action is required.

GBIC_SECURITY_CRYPT Messages

This section contains the Cisco GBIC module and SFP module security messages. The switch recognizes the module as a Cisco module but identifies another problem with it.

Error Message    GBIC_SECURITY_CRYPT-4-ID_MISMATCH: Identification check failed for 
GBIC interface [chars].

Explanation The SFP module was identified as a Cisco SFP module, but the system could not verify its identity. [chars] is the port.

Recommended Action Check that the Cisco IOS software running on the switch supports the SFP module. You might need to upgrade your software. Otherwise, verify that the SFP module was obtained from Cisco or from a supported vendor.

Error Message    GBIC_SECURITY_CRYPT-4-UNRECOGNIZED_VENDOR: GBIC interface [chars] 
manufactured by an unrecognized vendor.

Explanation The SFP module was identified as a Cisco SFP module, but the switch could not match its manufacturer with one on the known list of Cisco SFP module vendors. [chars] is the port.

Recommended Action Check that the Cisco IOS software running on the switch supports the SFP module. You might need to upgrade your software.

Error Message    GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC interface [chars] has 
bad crc.

Explanation The SFP module was identified as a Cisco SFP module, but it does not have a valid cyclic redundancy check (CRC) in the EEPROM data. [chars] is the port.

Recommended Action Check that the Cisco IOS software running on the switch supports the SFP module. You might need to upgrade your software. Even if the switch does not recognize the SFP module, it might still operate properly but have limited functionality.

HARDWARE Messages

Error Message    HARDWARE-2-FAN_ERROR: Fan [chars] Failure

Explanation The switch fan is not working. [chars] is the fan name.

Recommended Action This is a hardware failure. The fan might recover automatically. If the fan failure persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

Error Message    HARDWARE-2-THERMAL_WARNING: Temperature has reached warning threshold.

Explanation The temperature sensor valve inside the switch reached the warning threshold. The switch can function normally until the temperature reaches the critical threshold.

Recommended Action The external temperature is high. Reduce the temperature in the room.

Error Message    HARDWARE-3-MCU_I2C_BAD_DEV: I2C bad device address: [hex] 
(alchemy[dec])

Explanation MCU I2C read or write failed at a particular I2C device address. [hex] is the message number, and [dec] is the alchemy number].

Recommended Action Ensure the environment temperature is not too high or too low.

Error Message    HARDWARE-3-ASICNUM_ERROR: Port-ASIC number [dec] is invalid.

Explanation The port ASIC number used is invalid. Each port ASIC is identified by an ID. [dec] is the ASIC number.

Error Message    HARDWARE-3-INDEX_ERROR: Index value [dec] is invalid.

Explanation The index into the hardware table is out-of-range. [dec] is the index value.

Error Message    HARDWARE-3-INTRNUM_ERROR: Port-ASIC Interrupt number [dec] is invalid.

Explanation The interrupt ID used in a port ASIC is invalid. [dec] is the interrupt number.

Error Message    HARDWARE-3-PORTNUM_ERROR: port number [dec] is invalid.

Explanation The port number used is invalid (out of range). Each interface in a given port ASIC is identified by an index value. [dec] is the port number.

Error Message    HARDWARE-3-STATS_ERROR: Statistics ID [dec] is invalid.

Explanation The statistics ID is out of range. The statistics supported by the port ASIC are identified by an ID. [dec] is the statistics ID.

Error Message    HARDWARE-3-ASICNUM_ERROR: [traceback] Port-ASIC number [dec] is 
invalid

Explanation The port ASIC number is invalid. [dec] is the port ASIC number.

Error Message    HARDWARE-3-PORTNUM_ERROR: [traceback] port number [dec] is invalid

Explanation The port number is out of range. [dec] is the port number.

HLFM Messages

Error Message    HLFM-3-MACFREE_ERROR: MAC address [enet], vlan [dec] is still 
referenced; cannot free.

Explanation An attempt was made to free a MAC address before releasing all references to it. [enet] is the MAC address, and [dec] is the VLAN ID.

Error Message    HLFM-3-MAP_ERROR: IP address [IP_address] not in mac tables, 
mac-address [enet], vlan [dec].

Explanation The IP address and MAC address tables are out of sync. [IP_address] is the IP address, [enet] is the MAC address, and [dec] is the VLAN ID.

Error Message    HLFM-3-MOD_SD: Failed to modify Station Descriptor with index [dec], 
vlan [dec], di [dec], error [dec], mad [dec], ref-count [dec].

Explanation The forwarding manager attempted to modify a station descriptor that is not in use or is invalid. The first [dec] is the station index, the second [dec] is the VLAN ID, the third [dec] is the destination index, the fourth [dec] is the error code, the fifth [dec] is the MAC address descriptor, and the sixth [dec] is the ref-count for this MAC address descriptor.

IDBMAN Messages

Error Message    IDBMAN-3-AGGPORTMISMATCH: [chars]: [chars]([dec] / [dec]) does not 
match internal slot/port state [chars]([dec] / [dec]).

Explanation An internal error caused an invalid aggregate port to be used by the software. The first [chars] is the name of the function where the error occurred. The second and third [chars] are the port-channel names, and the ([dec] / [dec]) are the slot and port numbers (slot/port).

Error Message    IDBMAN-3-DELETEDAGGPORT: [chars]([dec] / [dec]) Group [dec] has been 
deleted, but is being reused.

Explanation A deleted interface was reused for a new aggregate port. [chars] is the port-channel name, and the ([dec] / [dec]) are the slot and port numbers (slot/port). The last [dec] is the channel-group number.

Error Message    IDBMAN-3-INVALIDAGGPORTBANDWIDTH: [chars]([dec] / [dec]) has an 
invalid bandwidth value of [dec].

Explanation An invalid bandwidth wa used for an aggregate port. [chars] is the port-channel name. The ([dec] / [dec]) are the slot and port numbers (slot/port). The last [dec] is the bandwidth.

Error Message    IDBMAN-3-INVALIDPORT: [chars]: trying to use invalid port number [dec] 
( Max [dec] ).

Explanation An invalid port number was used by the software. [chars] is the interface name. The first [dec] is the port number that is invalid, and the second [dec] is the maximum allowed value for a port number.

Error Message    IDBMAN-3-INVALIDVLAN: [chars]: trying to use invalid Vlan [dec].

Explanation An invalid VLAN wa used by the software. [chars] is the interface name, and [dec] is the VLAN ID that is invalid.

Error Message    IDBMAN-3-NOTANAGGPORT: [chars]( [dec] / [dec] ) is not an aggregate 
port.

Explanation An interface that is not an aggregate port was used for aggregate port operations. [chars] is the interface name, and ([dec] / [dec]) are the slot and port number (slot/port).

Error Message    IDBMAN-3-PORTNOTINAGGPORT: [chars]([dec] / [dec]) is not present in 
Aggport [chars [([dec] / [dec]).

Explanation A port that was supposed to be in an aggregate port was found not to be. The first [chars] is the interface name, and the second [chars] is the port-channel name. The ([dec] / [dec]) are the slot and port numbers (slot/port).

Error Message    IDBMAN-3-VLANNOTSET: [chars]: Vlan [dec] not set since it already has 
Vlan [dec].

Explanation An interface VLAN was not set to the requested value. [chars] is the interface name. The first [dec] is the recently configured VLAN ID, and the second [dec] is the currently assigned VLAN ID.

Error Message    IDBMAN-4-ACTIVEPORTSINAGGPORT: [chars]( [dec] / [dec] ) has [dec] 
active ports, but is being removed.

Explanation An internal error removed an aggregate port that has active ports. [chars] is the port-channel name, and the ([dec] / [dec]) are the slot and port number (slot/port). The last [dec] is the number of currently active ports.

IFMGR Messages

Error Message    IFMGR-3-IFINDEX_PERSIST_ENTRY_CORRUPT: [chars] seems to be corrupted. 
Trying to read [dec] size

Explanation The ifIndex table is corrupted. [chars] is the path to the IfIndex file, and [dec] is the number of bytes that was being read from the ifIndex table when the corruption was detected.

Recommended Action Use the delete nvram:ifindex-table privileged EXEC command to delete the ifindex table.

Error Message    IFMGR-3-INVALID_PERSISTENT_DATA: Invalid persistent data

Explanation The interface manager attempted to write invalid persistent data.

IGMP_QUERIER Messages

Error Message    IGMP_QUERIER-4-NO_IP_ADDR_CFG: The IGMP querier cannot send out 
General Query messages in VLAN [dec] because there is no IP address configured on 
the system.

Explanation The IGMP querier could not send messages to the interface because an IP address was not specified at either the global or per-VLAN level. [dec] is the VLAN ID.

Recommended Action Configure a source IP address for the IGMP querier.

Error Message    IGMP_QUERIER-4-SNOOPING_DISABLED: The IGMP querier is operationally 
disabled in VLAN [dec] because IGMP snooping has been disabled in this VLAN.

Explanation IGMP snooping is disabled on this VLAN. Do not enable the IGMP querier when IGMP snooping is disabled. [dec] is the VLAN IDs.

Recommended Action Confirm that IGMP snooping is enabled both globally and on the VLAN.

Error Message    IGMP_QUERIER-6-PIM_DISABLED: The IGMP querier is now operationally 
enabled in VLAN [dec] because PIM is no longer enabled on the SVI.

Explanation Protocol-Independent Multicast (PIM) is disabled on the switch virtual interface (SVI), and the IGMP querier function is now enabled. [dec] is the VLAN ID.

Recommended Action No action is required.

Error Message    IGMP_QUERIER-6-SNOOPING_ENABLED: The IGMP querier is now operationally 
enabled in VLAN [dec] because IGMP snooping is no longer disabled.

Explanation IGMP snooping was enabled. As a result, the IGMP querier function is now enabled. [dec] is the VLAN ID.

Recommended Action No action is required.

ILET Messages

Error Message    ILET-1-AUTHENTICATION_FAIL: This Switch may not have been manufactured 
by Cisco or with Cisco's authorization.  This product may contain software that 
was copied in violation of Cisco's license terms.  If your use of this product is 
the cause of a support issue, Cisco may deny operation of the product, support 
under your warranty or under a Cisco technical support program such as Smartnet.  
Please contact Cisco's Technical Assistance Center for more information.

Explanation A license authentication failure occurred for the switch.

Recommended Action Contact your Cisco sales representative for assistance.

Error Message    ILET-1-DEVICE_AUTHENTICATION_FAIL: The [chars] inserted in this switch 
may not have been manufactured by Cisco or with Cisco's authorization. If your use 
of this product is the cause of a support issue, Cisco may deny operation of the 
product, support under your warranty or under a Cisco technical support program 
such as Smartnet.  Please contact Cisco's Technical Assistance Center for more 
information.

Explanation A license authentication failure occurred for an installed component. [chars] is the component.

Recommended Action Contact your Cisco sales representative for assistance.

ILPOWER Messages

Error Message    ILPOWER-3-CONTROLLER_ERR: Controller error, Controller number [dec]: 
[chars].

Explanation An error was reported or caused by the PoE controller. [dec] is the controller instance, which is 0 to 5 on a 24-port PoE switch and 0 to 11 on a 48-port PoE switch. [chars] describes the error.

Error Message    ILPOWER-3-CONTROLLER_IF_ERR: Controller interface error, [chars]: 
[chars].

Explanation An interface error was detected between the PoE controller and the system. The first [chars] is the interface. The second [chars] describes the error.

Error Message    ILPOWER-3-CONTROLLER_PORT_ERR:Controller port error, Interface 
Fa0/7:Power given, but link is not up.

Explanation The inline-power-controller reported an error on an interface.

Recommended Action Enter the shutdown and no shutdown interface configuration commands on the affected interface.

Error Message    ILPOWER-3-CONTROLLER_POST_ERR: Inline Power Feature is disabled on 
this switch because Power On Self Test (POST) failed on this switch. Please consult 
TECH support for further assistance

Explanation The Power over Ethernet (PoE) controller reported or caused an error during power-on self-test (POST).

Error Message    ILPOWER-3-ILPOWER_INTERNAL_IF_ERROR: Inline Power internal error, 
interface [chars]: [chars].

Explanation A software check failed during PoE processing. The first [chars] is the interface. The second [chars] describes the error.

Error Message    ILPOWER-3-SHUT_OVERDRAWN: Interface [chars] is shutdown as it is 
consuming more than the maximum configured power ([dec]) milliwatts.

Explanation The interface is shut down because it is consuming more than the maximum power allocation. [chars] is the port, and [dec] is the maximum configured power.

Recommended Action Check that the cutoff-power value is configured for the device and is based on the powered-device specifications or ratings. We recommend configuring the cutoff power to a value higher than the required power for the device.

Error Message    ILPOWER-4-LOG_OVERDRAWN: Interface [chars] is overdrawing power. it is 
consuming [dec] milliwatts where as maximum configured power is ([dec]) 
milliwatts.

Explanation The powered device is drawing more power than the maximum power configured on the interface. The power budgeting calculations determined by the switch are not valid, and you risk overloading the switch. [chars] is the interface, and [dec] is the maximum configured power.

Recommended Action Check that the correct power is budgeted for this interface based on the powered-device electrical specifications or ratings. We recommend that you change the cutoff power value.

Error Message    ILPOWER-5-CLR_OVERDRAWN: Interface [chars] is NOT overdrawing power. 
it is consuming [dec] milliwatts where as maximum configured value is ([dec]) 
milliwatts.

Explanation The device connected to the PoE interface is consuming less power than the maximum power allocation. [chars] is the interface. The first [dec] is the power being consumed, and the second [dec] is the maximum allocated power value.

Recommended Action No action is required.

Error Message    ILPOWER-5-IEEE-DISCONNECT: Interface [chars]: PD removed.

Explanation The powered device is not connected to the switch, or the connected powered device is being powered by an external AC power source. The switch is not providing power to the port. [chars] is the interface.

Recommended Action No action is required.

Error Message    ILPOWER-5-ILPOWER_POWER_CDP_SHUT: Interface [chars]: inline power shut

Explanation Inline power was shut down because CDP consumption power on this PoE port was greater than the allocated power, the hardware interface limit, the user-configured maximum power, or the available power on this switch. [chars] is the interface.

Recommended Action No action is required.

Error Message    ILPOWER-5-ILPOWER_POWER_DENY: Interface [chars]: inline power denied.

Explanation There is not enough switch power to supply to the PoE port. [chars] is the interface.

Recommended Action Connect the powered device to an external AC power source.

Error Message    ILPOWER-5-INVALID_IEEE_CLASS: Interface [chars]: has detected invalid 
IEEE class: [dec] device. Power denied

Explanation The powered device has an invalid IEEE class so that the switch is not providing power to the device. [chars] is the interface. [dec] is the IEEE class number.

Recommended Action No action is required.

Error Message    ILPOWER-5-LINKDOWN_DISCONNECT: Interface [chars]: Link down 
disconnect.

Explanation The powered device was not connected to the switch, or the connected powered device was being powered by an external AC power source. The switch was not providing power on the interface. [chars] is the interface.

Recommended Action No action is required.

Error Message    ILPOWER-5-POLICE_POWER_INVALID: Interface [chars]: invalid power 
police [dec] milliwatts current [dec] mA voltage [dec] mV

Explanation The power policing current or voltage value is invalid. [chars] is the interface. The first [dec] is the power policing limit (cutoff value in mW), the second [dec] is the power usage in mA, and the third [dec] is the power usage in mV.

Error Message    ILPOWER-5-POWER_GRANTED: Interface [chars]: Power granted.

Explanation The switch can provide power to the interface. [chars] is the interface.

Recommended Action No action is required.

Error Message    ILPOWER-5-SENSE_POWER_INVALID: Interface [chars]: invalid power sense 
[dec] milliwatts current [dec] mA voltage [dec] mV

Explanation The power-monitoring voltage or current value is invalid. [chars] is the interface. The first [dec] is the power-monitoring cutoff value, the second [dec] is the real-time power consumption in mA, and the third [dec] is the real-time power consumption in mV.

Error Message    ILPOWER-7-DETECT: Interface [chars]: Power Device detected:[chars].

Explanation The switch has detected a connected powered device. The first [chars] is the interface. The second [chars] is the Cisco prestandard powered device or the IEEE-compliant powered device.

Recommended Action No action is required.

IP_DEVICE_TRACKING_HA Messages

Error Message    IP_DEVICE_TRACKING_HA-4-ENTRY_OUT_OF_SYNC: Host mac-address [enet] 
ip-address [IP_address] interface [chars]

Explanation The IP device tracking table has detected an inconsistency between active and standby for this host. [enet] is the host MAC address, [IP_address] is the host IP address, and [chars] is the interface.

Recommended Action No action is required.

KEYMAN Messages

Error Message    KEYMAN-4-KEYSTR_CRYPTO_TYPE: Type [dec] encryption unknown.  
Interpreting keystring as literal

Explanation The format type is not recognized by the system. The unrecognized format type is either a keystring format type value of 0 (unencrypted keystring) or 7 (hidden keystring). [dec] is the public key type.

Recommended Action Use the correct format for the value type or remove the space following the value type.

Error Message    KEYMAN-4-KEYSTR_BAD_CRYPTO: Bad encrypted keystring for key id [dec].

Explanation The system could not decrypt an encrypted keystring. The keystring may have been corrupted during system configuration. [dec] is the key ID.

Recommended Action Reenter the keystring command and reconfigure the keystring.

MAC_LIMIT Messages

This section contains the MAC_LIMIT messages, which describe the entries in the MAC address table.

Error Message    MAC_LIMIT-4-DROP: Vlan [dec] with Configured limit = [dec] has 
currently [dec] Entries.

Explanation The number of MAC address table entries for a VLAN is less than or equal to the maximum number allowed. The first [dec] is the VLAN ID, the second [dec] is the maximum number of MAC address entries, and the third [dec] is the number of entries in the MAC address table.

Recommended Action Your system administrator configures an action.

Error Message    MAC_LIMIT-4-ENFORCE: Enforcing limit on Vlan [dec] with Configured 
limit = [dec].

Explanation The number of MAC address entries for the VLAN exceeds the maximum number allowed. The configured action is to limit the number of entries to the maximum allowed. The first [dec] is the VLAN ID, and the second [dec] is the maximum number of MAC address entries.

Recommended Action Your system administrator configures an action.

Error Message    MAC_LIMIT-4-EXCEED: Vlan [dec] with Configured limit = [dec] has 
currently [dec] Entries.

Explanation The number of MAC address entries for a VLAN exceeds the maximum number allowed. The first [dec] is the VLAN ID, the second [dec] is the maximum number of MAC address entries, and the third [dec] is the number of entries in the MAC address table.

Recommended Action Your system administrator configures an action.

MAC_MOVE Messages

Error Message    MAC_MOVE-4-NOTIF: Host [enet] in vlan [dec] is flapping between port 
[chars] and port [chars].

Explanation The host is moving between the specified ports. [enet] is the Ethernet address of the host, [dec] is the VLAN ID, the first [chars] is the first port, and the second [chars] is the second port.

Recommended Action Check your network for loops.

PHY Messages

Error Message    PHY-4-BADTRANSCEIVER: An inappropriate transceiver has been inserted 
in interface [chars].

Explanation A transceiver that should not be used is in the specified interface.

Recommended Action Remove the transceiver. If the transceiver is a Cisco device, contact your Cisco technical support representative.

Error Message    PHY-4-CHECK_SUM_FAILED: SFP EEPROM data check sum failed for SFP 
interface [chars].

Explanation The SFP module was identified as a Cisco SFP module, but the system cannot read the vendor data information to verify whether it is correct. [chars] is the interface in which the SFP module is installed.

Recommended Action Remove and then reinsert the SFP module. If it fails again with the same error message, the SFP module might be defective.

Error Message    PHY-4-EXCESSIVE_ERRORS: Excessive FCS, data, or idle word errors found 
on interface [chars].

Explanation The system detected excessive frame check sequence (FCS), data word, or idle word errors on the specified interface. [chars] is the interface.

Recommended Action Enter the show interface privileged EXEC command on the specified interface, and check for cyclic redundancy check (CRC) and other input errors. If errors are excessive, enter the shutdown interface configuration command and then the no shutdown interface configuration command to reset the interface.

Error Message    PHY-4-MODULE_DUP: SFPs in [chars] and in [chars] have duplicate 
vendor-id and serial numbers.

Explanation The SFP module was identified as a Cisco SFP module, but its vendor ID and serial number match that of another SFP module in the system. The first [chars] is the interface in which the SFP module is installed, the second [chars] is the interface where the duplicate SFP module is installed.

Error Message    PHY-4-SFP_NOT_SUPPORTED: The SFP in [chars] is not supported

Explanation This SFP module type is not supported on this switch. [chars] is the interface.

Error Message    PHY-4-SFP_PLUS_NOT_SUPPORTED: The SFP PLUS in [chars] is not supported

Explanation The Cisco X2 transceiver module is not supported on the switch. [chars] is the port in which the SFP module is inserted.

Error Message    PHY-4-UNSUPPORTED_SFP_CARRIER: Unsupported SFP carrier module found in 
[chars]

Explanation The SFP carrier module was identified as an unsupported, non-Cisco SFP carrier module. [chars] is the unsupported module.

Error Message    PHY-4-UNSUPPORTED_TRANSCEIVER:Unsupported transceiver found in 
[chars]

Explanation The SFP module was identified as an unsupported, non-Cisco SFP module. [chars] is the unsupported module.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section on page 1-5.

PLATFORM Messages

Error Message    PLATFORM-1-CRASHED: [chars].

Explanation The system is trying to display the error message that appeared when the switch failed in a previous instance. [chars] is the description of the error message.

Error Message    PLATFORM-3-PHYFWDOWNLOAD_FAILED: Phy Firmware download failed for 
[chars] Hotswap the Frulink module or use cli to reboot the Frulink.

Explanation The firmware download to the PHY device has failed. [chars] is the interface name.

Recommended Action No action is required.

PLATFORM_ENV Messages

Error Message    PLATFORM_ENV-1-PWR_LOPWR: Switch is operating in low power mode, 
switch is not fully operational. Current power source is [chars]

Explanation The switch does not have enough power to power up the ports. [chars] is the interface name.

Recommended Action Connect a Type2 capable power source to both the uplink PD ports.

Error Message    PLATFORM_ENV-1-PWR_NONOPTIMAL: Switch is fully operational but in 
non-optimal mode. Current power source is [chars]

Explanation The switch could change into low power mode on loss of the Type1 power supply. [chars] is the interface name.

Recommended Action Make sure both the uplink ports are connected to a Type2 capable power source.

Error Message    PLATFORM_ENV-6-PWR_OPTIMAL: Switch is fully operational. Current power 
source is [chars]

Explanation The switch is fully operational in optimal mode. [chars] is the interface name.

Recommended Action No action is required.

Error Message    PLATFORM_ENV-6-RPS_PRESENCE: Redundant Power Supply(RPS) [chars]

Explanation The Redundant Power Supply (RPS) changed state. [chars] is what was added or removed.

Recommended Action No action is required.

PLATFORM FRULink 10G Service Module Messages

Error Message    PLATFORM_SM10G-3-HARDWARE: FRULink 10G Service Module (C3KX-SM-10G) 
features are not supported on this revision of switch hardware. Please upgrade the 
switch hardware to use the module's features.

Explanation The current switch hardware version does not support the features of the module.

Recommended Action Upgrade the switch hardware to support the features of the module.

Error Message    PLATFORM_SM10G-3-NO_RESPONSE: The FRULink 10G Service Module 
(C3KX-SM-10G) is not responding.

Explanation The device is not responding. This could be due to hardware or software failure or a module reload.

Recommended Action Reboot or replace the module.

Error Message    PLATFORM_SM10G-3-AUTHENTICATION,: The FRULink 10G Service Module 
(C3KX-SM-10G) may not have been entirely manufactured by Cisco. Module is in 
pass-through mode.

Explanation Apart of the module's hardware could not be verified as official Cisco hardware. Extended services and features are disabled and the module will only operate in pass-thru mode.

Recommended Action Contact your Cisco technical support representative and replace the module.

Error Message    PLATFORM_SM10G-3-SW_VERSION_MISMATCH: The FRULink 10G Service Module 
(C3KX-SM-10G) in switch <switch-number> has a software version that is 
incompatible with the IOS software version. Please update the software. Module is 
in pass-thru mode.

Explanation The IOS and FRULink 10G service module software are incompatible.

Recommended Action Upgrade the software.

Error Message    PLATFORM_SM10G-3-FPGA_UPDATE_INITIATED: The FRULink 10G Service Module 
(C3KX-SM-10G) firmware is being updated due to a version mismatch. Please wait a 
few minutes for the update to complete.

Explanation The firmware is corrupted and needs to be restored.

Recommended Action Wait for the update to complete.

Error Message    PLATFORM_SM10G-3-FPGA_RELOADED: The FRULink 10G Service Module 
(C3KX-SM-10G) firmware has been updated and the module will be reloaded

Explanation The firmware is corrupted and has been restored

Recommended Action Upgrade the firmware.

Error Message    PLATFORM_SM10G-3-FPGA_RELOAD_FAILED: The FRULink 10G Service Module 
(C3KX-SM-10G) firmware could not be updated.

Explanation The firmware image is corrupted and could not be restored

Recommended Action Contact your Cisco technical support representative and replace the module.

Error Message    PLATFORM_SM10G-3-CORRUPT_SW_IMAGE: The FRULink 10G Service Module 
(C3KX-SM-10G) software version is corrupted. Please update the software. Module 
is in pass-thru mode.

Explanation The FRULink 10G Service Module software is invalid.

Recommended Action Update the software.

Error Message    PLATFORM_SM10G-6-LINK_UP: The FRULink 10G Service Module (C3KX-SM-10G) 
communication has been established.

Explanation Communication is established with the FRULink 10G service module.

Recommended Action No actions is required.

Error Message    PLATFORM_SM10G-6-LICENSE: FRULink 10G Service Module (C3KX-SM-10G) 
features are not supported with this license level. Module is in pass-thru mode.

Explanation The services and features of the module require an IPBASE or IPSERVICES license level. If the necessary license is not installed and activated, then the module operates only in the pass-through mode.

Recommended Action Install and activate an IPBASE or IPSERVICES license.

PLATFORM_IPv6 Messages

Error Message    PLATFORM_IPv6_UCAST-6-PREFIX: One or more, more specific prefixes 
could not be programmed into TCAM and are being covered by a less specific prefix

Explanation A more specific prefix was not programmed into TCAM and is covered by a less specific prefix. This could be a temporary condition. The output of the show platform ipv6 unicast retry route privileged EXEC command lists the failed prefixes.

Recommended Action No action is required.

PLATFORM_PM Messages

Error Message    PLATFORM_PM-3-IFCOUNTERROR: Unit number [dec] of interface [chars] is 
more than max allowed value of [dec].

Explanation There are too many interfaces configured for the interface type. [dec] is the interface count, [chars] is the interface, and [dec] is the maximum number of interfaces.

Error Message    PLATFORM_PM-3-INTVLANINUSE: internal vlan-id [dec] allocated for 
interface [chars] is still in use.

Explanation An internal VLAN ID allocated for an interface was still in use. [dec] is the VLAN ID, and [chars] is the interface.

Error Message    PLATFORM_PM-3-NOINTVLAN: internal vlan of interface [chars] is not 
active for vlan-id [dec].

Explanation Internal vlan_data was not active for the given VLAN ID. [chars] is the interface, and [dec] is the VLAN ID.

PLATFORM_RPC Messages

Error Message    PLATFORM_RPC-3-DECRYPT_FAIL, MSG_TRACEBACK: System is unable to 
decrypt the packets (Switch [dec]-> [dec])(class [dec])(req_size [dec])(dlen 
[dec])(total_size [dec])(too many indicate critical situation)

Explanation Packet decryption failed due to sequencing and key exchange. Thi s is not critical unless many such messages appear within a short period of time, like an hour. It is normal to see this message after a master failover. The first [dec] is the source switch number, the second [dec] is the switch box bit, the third [dec] is the message class, the fourth [dec] is the packet size, the fifth [dec] is the data size, and the sixth [dec] is the response length.

Recommended Action No action is required.

Error Message    PLATFORM_RPC-3-ENCRYPT_FAIL, MSG_TRACEBACK: System is unable to 
encrypt the packets (switch [dec]) (too many indicate critical situation)

Explanation Packet encryption failed due to sequencing and key exchange. Thi s is not critical unless many such messages appear within a short period of time, like an hour. It is normal to see this message after a master failover. [dec] is the switch box bit.

Recommended Action No action is required.

PLATFORM_VLAN Messages

Error Message    PLATFORM_VLAN-3-LOCK_FAIL: Failed to lock vlan-id [dec], associated 
mapped vlan id value [dec].

Explanation The VLAN lock operation failed. This can occur if the VLAN is already active in the system or if the VLAN ID is not active. The first [dec] is the VLAN ID, and the second [dec] is the mapped-vlan-id (MVID).

Error Message    PLATFORM_VLAN-3-MVID_ERROR: Mapped Vlan ID value [dec] associated with 
vlan-id [dec] is invalid.

Explanation An active VLAN was not correctly associated with a MVID. The first [dec] is the VLAN ID, and the second [dec] is the MVID.

Error Message    PLATFORM_VLAN-3-UNLOCK_FAIL: Failed to unlock vlan-id [dec], 
associated mapped vlan id value [dec].

Explanation The switch did not unlock a VLAN ID. The most likely cause was that the VLAN was already unlocked. The first [dec] is the VLAN ID, and the second [dec] is the MVID.

PM Messages

This section contains the port manager messages. The port manager is a state machine that controls all the logical and physical interfaces. All features, such as VLANs, UDLD, and so forth, work with the port manager to provide switch functions.

Error Message    PM-2-LOW_SP_MEM: Switch process available memory is less than [dec] 
bytes.

Explanation The available memory for the switch processor was low. This can occur when too many Layer 2 VLANs are configured. [dec] is the available memory.

Recommended Action Remove VLANs from the system to reduce memory usage.

Error Message    PM-2-NOMEM: Not enough memory available for [chars].

Explanation The port manager subsystem could not obtain the memory it needed to initialize the specified operation. [chars] is the port manager operation.

Error Message    PM-2-VLAN_ADD: Failed to add VLAN [dec] - [chars].

Explanation The software did not add the VLAN to the VLAN Trunking Protocol (VTP) database. [dec] is the VLAN ID, and [chars] specifies the reason the software did not add the VLAN.

Error Message    PM-3-INTERNALERROR: Port Manager Internal Software Error ([chars]: 
[chars]: [dec]: [chars]).

Explanation An internal software error occurred in the port manager. The parameters identify the problem for technical support. The first [chars] is the error message, and the second [chars] is the filename. [dec] is the line number, and the last [chars] is the function name.

Error Message    PM-4-BAD_APP_ID: an invalid application id ([dec]) was detected.

Explanation The port manager detected an invalid request. [dec] is the application ID.

Error Message    PM-4-BAD_APP_REQ: an invalid [chars] request by the '[chars]' 
application was detected.

Explanation The port manager detected an invalid request. The first [chars] is the invalid request, and the second [chars] is the application making the request.

Error Message    PM-4-BAD_CARD_COOKIE: an invalid card cookie was detected.

Explanation The port manager detected an invalid request.

Error Message    PM-4-BAD_CARD_SLOT: an invalid card slot ([dec]) was detected.

Explanation The port manager detected an invalid request. [dec] is the slot number.

Error Message    PM-4-BAD_COOKIE: [chars] was detected.

Explanation The port manager detected an invalid request. [chars] is the invalid request.

Error Message    PM-4-BAD_HA_ENTRY_EVENT: Invalid Host access entry event ([dec]) is 
received.

Explanation An invalid host access entry event was received. The host access table entry event should be an add, delete, or update event. [dec] is the event that is received.

Error Message    PM-4-BAD_PORT_COOKIE: an invalid port cookie was detected.

Explanation The port manager detected an invalid request.

Error Message    PM-4-BAD_PORT_NUMBER: an invalid port number ([dec]) was detected.

Explanation The port manager detected an invalid request. [dec] is the port number.

Error Message    PM-4-BAD_VLAN_COOKIE: an invalid vlan cookie was detected.

Explanation The port manager detected an invalid request.

Error Message    PM-4-BAD_VLAN_ID: an invalid vlan id ([dec]) was detected.

Explanation The port manager detected an invalid request. [dec] is the VLAN ID.

Error Message    PM-4-ERR_DISABLE: [chars] error detected on [chars], putting [chars] 
in err-disable state.

Explanation The port manager detected a misconfiguration or misbehavior and error disabled the interface. A recovery is attempted after the configured retry time (the default is 5 minutes). On PoE switches, this message might appear when a device that can be powered by either a PoE switch port or by AC power is not being powered by an external AC power source and is connected to a port that has been configured with the power inline never interface configuration command. The first [chars] is the error, and both the second and third [chars] are the affected interface.

Recommended Action On non-PoE switches, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. On PoE switches, remove the device or configure the port by entering the power inline auto, shutdown, and no shutdown interface configuration commands. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

Error Message    PM-4-ERR_DISABLE_VP: [chars] error detected on [chars], vlan [dec].  
Putting in err-disable state.

Explanation The virtual port (that is, the port-VLAN pair) is error disabled when it detects a misconfiguration or misbehavior. If configured, a recovery will be attempted after the configured retry time (default time is 5 minutes). The first [chars] is the error, and the second [chars] is the port.

Error Message    PM-4-ERR_RECOVER: Attempting to recover from [chars] err-disable state 
on [chars].

Explanation The port manager is trying to restart an error disabled interface. The first [chars] is the error, and the second [chars] is the interface.

Error Message    PM-4-ERR_RECOVER_VP: Attempting to recover from [chars] err-disable 
state on [chars], vlan [dec].

Explanation The port manager is trying to restart an error disabled virtual port. The first [chars] is the error, the second [chars] is the virtual port, and [dec] is the VLAN ID.

Error Message    PM-4-EXT_VLAN_INUSE: VLAN [dec] currently in use by [chars].

Explanation The port manager did not allocate the VLAN for external use because the VLAN is being used by another feature. [dec] is the VLAN that is being used, and [chars] is the feature that is using it.

Recommended Action Reconfigure the feature (for example, the routed port) to use another internal VLAN or to request another available VLAN.

Error Message    PM-4-EXT_VLAN_NOTAVAIL: VLAN [dec] not available in Port Manager.

Explanation The port manager did not allocate the requested VLAN. The VLAN is probably being used as an internal VLAN by other features. [dec] is the requested VLAN.

Recommended Action Configure a different VLAN on the device.

Error Message    PM-4-INACTIVE: putting [chars] in inactive state because [chars].

Explanation The port was inactive because the port manager could not create a virtual port for the switch port and VLAN. The reason for this condition is specified in the error message. The first [chars] is the interface name, and the second [chars] is the reason.

Error Message    PM-4-INT_FAILUP: [chars] failed to come up. No internal VLAN available.

Explanation The port manager did not allocate an internal VLAN. The interface cannot be enabled. [chars] is the interface name.

Recommended Action Remove the extended-range VLAN by using the no vlan vlan-id global configuration command to free up resources.

Error Message    PM-4-INT_VLAN_NOTAVAIL: Failed to allocate internal VLAN in Port 
Manager.

Explanation The port manager did not find any available internal VLAN.

Recommended Action Delete some extended-range VLANs created by users, or remove some features (such as routed ports) that require internal VLAN allocation. To delete extended-range VLANs, use the no vlan vlan-id global configuration command. To delete a routed port, use the no switchport interface configuration command.

Error Message    PM-4-INVALID_HOST_ACCESS_ENTRY: Invalid Host access entry type ([dec]) 
is received.

Explanation An invalid host access entry type was received. The host access entry should be a configured or a dynamic type. [dec] is the entry type that is received.

Error Message    PM-4-LIMITS: The number of vlan-port instances on [chars] exceeded the 
recommended limit of [dec].

Explanation The total number of individual VLAN ports on the module or the switch exceeded the recommended limit. VLANs can be counted more than once. If VLAN 1 is carried on ten interfaces, it counts as ten VLAN ports. On some platforms, bundling is also ignored for purposes of this count. If eight interfaces on the same module are in one bundle, and the port channel is carrying VLAN 1, it counts as eight VLAN ports. [chars] is the module name (for example, switch or the module number), and [dec] is the recommended limit.

Recommended Action Reduce the number of trunks and VLANs configured in the module or switch as recommended in [dec]. Enter the show interfaces trunk privileged EXEC command to see the total number of trunks and VLANs.

Error Message    PM-4-NO_SUBBLOCK: No PM subblock found for [chars].

Explanation The port manager did not find the subblock for this interface. [chars] is the interface name.

Error Message    PM-4-PORT_BOUNCED: Port [chars] was bounced by [chars].

Explanation During a change-over when the port was in the link-down state, the port manager restarted the port. A port can be restarted only when the port data structures are not consistent in the active and standby supervisors. Active ports in the link-down state return to the link-up state when the port is restarted. The first [chars] is the port number, and the second [chars] is the re-activation event.

Recommended Action No action is required.

Error Message    PM-4-PVLAN_TYPE_CFG_ERR: Failed to set VLAN [dec] to a [chars] VLAN.

Explanation The platform did not set a private VLAN type. [dec] is the VLAN ID.

Error Message    PM-4-TOO_MANY_APP: application '[chars]' exceeded registration limit.

Explanation The port manager detected an invalid request. [chars] is the application.

Error Message    PM-4-UNKNOWN_HOST_ACCESS: Invalid Host access value ([dec]) is 
received.

Explanation The host access table was being accessed with an invalid host access value. [dec] is the value that is received.

Error Message    PM-4-VMPS_CFG: Dynamic access VLAN [dec] same as voice vlan on [chars].

Explanation The access VLAN ID on the VMPS server was the same as the voice VLAN ID on the interface. [dec] is the access VLAN ID, and [chars] is the physical interface.

Recommended Action Assign the access VLAN on the VMPS server to a VLAN ID that is different from the voice VLAN ID.

PORT_SECURITY Messages

Error Message    PORT_SECURITY-2-PSECURE_VIOLATION:Security violation occurred caused 
by MAC [enet] on port [chars].

Explanation An unauthorized device attempted to connect on a secure port. [enet] is the MAC address of the unauthorized device, and [chars] is the secure port.

Recommended Action Identify the device that attempted to connect on the secure port. Notify your network system administrator of this condition.

Error Message    PORT_SECURITY-2-PSECURE_VIOLATION_VLAN: Security violation on port 
[chars] due to MAC address [enet] on VLAN [dec]

Explanation An unauthorized device attempted to connect on a secure trunk port. [chars] is the secure port, [enet] is the MAC address of the unauthorized device, and [dec] is the VLAN ID.

Recommended Action Identify the device that attempted to connect through the secure trunk port. Notify your network system administrator of this condition.

Error Message    PORT_SECURITY-6-ADDR_REMOVED: Address [dec]:[enet] exists on port 
[chars]. It has been removed from port [chars].

Explanation A routed port was reconfigured as a switch port. The address in the previous switch configuration conflicts with the running configuration and has been deleted. [dec]:[enet] is the MAC address of the port, and [chars] is the reconfigured port.

Recommended Action No action is required.

Error Message    PORT_SECURITY-6-ADDRESSES_REMOVED: Maximum system secure address count 
reached. Some secure addresses configured on port [chars] removed.

Explanation Some configured and sticky MAC addresses on the specified port were removed from the configuration. The number of secure addresses that the system supports was exceeded. This condition occurs only during hot swapping or port-mode changes (for example, when the port is converted from a Layer 3 to a Layer 2 port). [chars] is the port.

Recommended Action No action is required.

Error Message    PORT_SECURITY-6-VLAN_FULL: Vlan [dec] on port [chars] has reached its 
limit. Address [enet] has been removed.

Explanation The voice VLAN was the same as the access VLAN. Because the maximum number of MAC addresses allowed on the access VLAN was reached, the specified Ethernet address was deleted. [dec] is the VLAN ID, [chars] is the port assigned to the voice VLAN and the access VLAN, and [enet] is the Ethernet address.

Recommended Action No action is required.

Error Message    PORT_SECURITY-6-VLAN_REMOVED: VLAN [dec] is no longer allowed on port 
[chars]. Its port security configuration has been removed.

Explanation A configured VLAN was excluded either due to a port-mode change or an allowed VLAN list change, and was removed from the configuration. [int] is the VLAN ID, and [chars] is the switch port assigned to the VLAN.

Recommended Action No action is required.

QOSMGR Messages

Error Message    QOSMGR-3-FEATURE_NOT_FOUND: Cannot find feature for [chars].

Explanation An internal software error occurred. [chars] is the description of the feature that the software cannot find.

Error Message    QOSMGR-3-FILTERTYPE_INVALID: Internal Error Invalid Policy filtertype 
[dec].

Explanation An internal software error occurred. [dec] is the invalid filter type identification.

Error Message    QOSMGR-3-MERGE_RES_COUNT: Internal Error Invalid count.

Explanation An internal software error occurred.

Error Message    QOSMGR-3-NO_POLICER_QOSLABEL: Creating port Class Label Failed.

Explanation An internal software error occurred.

Error Message    QOSMGR-3-NO_VMR_QOSLABEL: qm_generate_vmrs have no qos label.

Explanation An internal software error occurred.

Error Message    QOSMGR-3-NULL_POLICER: Internal Error Invalid Policer.

Explanation An internal software error occurred.

Error Message    QOSMGR-3-POLICER_RES_COUNT: Internal Error Invalid Policer count.

Explanation An internal software error occurred.

Error Message    QOSMGR-3-POLICYMAP_NOT_FOUND: Cannot find policymap for [chars].

Explanation An internal software error occurred. [chars] is the policy-map name.

Error Message    QOSMGR-3-QUEUE_PTR_ERROR: queue pointers out of order [hex] [hex] 
[hex] [hex].

Explanation An internal software error occurred. [hex] [hex] [hex] [hex] are the software-computed queue pointer values. The parameters provide error details for technical support.

Error Message    QOSMGR-3-RESERVE_COUNT_ERROR: Reserved Count Exceeding total [dec].

Explanation An internal software error occurred in the allocated reserved buffers. [dec] is the reserved count computed by the software.

Error Message    QOSMGR-3-RESOURCE_INTERNAL: Internal Error in resource allocation.

Explanation An internal software error occurred.

Error Message    QOSMGR-3-VMRSEQ_INVALID: Internal Error Invalid VMR sequence.

Explanation An internal software error occurred.

Error Message    QOSMGR-4-ACTION_NOT_SUPPORTED: Action is not supported in policymap 
[chars].

Explanation An action other than the set, trust, and police policy-map class configuration commands was configured in a policy map. This is a hardware limitation. [chars] is the policy-map name.

Recommended Action Configure only the supported actions of set, trust, and police when in policy-map class configuration mode.

Error Message    QOSMGR-4-CLASS_NOT_SUPPORTED: Classification is not supported in 
classmap [chars].

Explanation An unsupported match class-map configuration command was configured in a policy map and attached to an egress interface, or more than one match class-map command was configured. This is a hardware limitation. [chars] is the class-map name.

Recommended Action Reconfigure the class map or the policy map. Use only the match ip dscp dscp-list class-map configuration command in a policy map that is attached to an egress interface. Only one match per class map is supported.

Error Message    QOSMGR-4-COMMAND_FAILURE: Execution of [chars] command failed.

Explanation The command to configure a QoS setting failed. This is possibly due to lack of hardware resources. [chars] is the description of the command.

Recommended Action Look for any other messages that indicate resource failure. If other messages indicate that the hardware resources exceeded, retry the command with a smaller configuration. Find out more about the error by using the show tech-support privileged EXEC command. Copy the error message exactly as it appears on the console or system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

Error Message    QOSMGR-4-HARDWARE_NOT_SUPPORTED: Hardware limitation has reached for 
policymap [chars].

Explanation The policy-map configuration exceeded the limitation of the hardware. You configured more QoS ACL entries than the number specified in the Switch Database Management (SDM) template. [chars] is the policy-map name.

Recommended Action Reconfigure the class map or the policy map, and reduce the number of QoS ACLs.

Error Message    QOSMGR-4-MATCH_NOT_SUPPORTED: Match type is not supported in classmap 
[chars].

Explanation An unsupported match type was entered. Only the access-group acl-index-or-name, ip dscp dscp-list, and ip precedence ip-precedence-list match types are supported with the match class-map configuration command. [chars] is the class-map name.

Recommended Action Reconfigure the class map using only the match access-group, match ip dscp, and match ip precedence class-map configuration commands within the class map.

Error Message    QOSMGR-4-NOT_SUPPORTED: Action '[chars]' is not supported for a 
policymap attached to output side.

Explanation A set or trust policy-map class configuration command was configured in a policy map and attached to an egress interface. A warning message is logged, and the actions do not take effect. This is a hardware limitation. [chars] is either the set or trust action.

Recommended Action Do not configure a set or trust policy-map class configuration command in a policy map and attach it to an egress interface. These policy-map actions are supported only on ingress interfaces.

Error Message    QOSMGR-4-POLICER_PLATFORM_NOT_SUPPORTED: Policer configuration has 
exceeded hardware limitation for policymap [chars].

Explanation The policy-map configuration exceeded the hardware limitation. An attempt to configure more policers in all policy maps (by using the police or police aggregate policy-map class configuration command) than supported by the hardware, which is not allowed, caused this condition. [chars] is the policy-map name.

Recommended Action Reconfigure the class maps or the policy maps, or delete the policy map from some interfaces.

Error Message    QOSMGR-4-POLICER_POLICY_NOT_SUPPORTED: Number of policers has exceeded 
per policy hardware limitation for policymap [chars].

Explanation The policy-map configuration exceeded the hardware limitation. An attempt to configure more policers in a policy map (by using the police or police aggregate policy-map class configuration command) than supported by the hardware, which is not allowed, caused this condition. [chars] is the policy-map name.

Recommended Action Reconfigure the class map or the policy map, and reduce the number of policers.

REP Messages

Error Message    REP-3-INVALIDPKT: received invalid pkt: [chars]

Explanation The switch received an invalid Resilient Ethernet Protocol (REP) packet. [chars] is information about the invalid packet.

Error Message    REP-3-NOPPPROC: [traceback] Failed to create REP LSL Fast Hello Process

Explanation The switch could not exchange hello packets with its Resilient Ethernet Protocol (REP) neighbors because the Link Status Layer (LSL) age timer was set to more than 3 seconds.

Recommended Action Reload the switch.

RMON Messages

Error Message    RMON-5-FALLINGTRAP: Falling trap is generated because the value of 
[chars] has fallen below the falling-threshold value [dec].

Explanation A falling trap was generated. The value of the specified MIB object was below the falling threshold value. [chars] is the MIB object, and [dec] is the threshold value.

Recommended Action Take appropriate action on the specified MIB object to compensate for the changed value.

Error Message    RMON-5-RISINGTRAP: Rising trap is generated because the value of 
[chars] exceeded the rising-threshold value [dec].

Explanation A rising trap was generated. The value of the specified MIB object was above the rising threshold value. [chars] is the MIB object, and [dec] is the threshold value.

Recommended Action Take appropriate action on the specified MIB object to compensate for the changed value.

SCHED Messages

Error Message    SCHED-3-UNEXPECTEDEVENT: [traceback] [process information] Process 
received unknown event (maj [hex], min [hex])

Explanation An event was not processed. The first [hex] is the major event number, and the second [hex] is the minor event number.

SESA Messages

Error Message    SESA-3-MASTER_AUTENTICATION_FAIL: Failed to [chars] SESA MA auth at 
remote end (src[dec]) (dest [dec]) Err [dec])

Explanation The master switch cannot be remotely authenticated. Check Federal Information Processing Standards Publication (FIPS) authorization key on master switch and the remote switch and reboot. [chars] is the action value, the first [dec] is the source switch, the second [dec] is the destination switch, and the third [dec] is the error value.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message    SESA-2-MEMORY_ALLOC_FAIL: Failed to allocate memory (location 
[chars])(src [dec])(dest [dec])(Err [dec])

Explanation The switch failed to allocate memory. You have to fix the problem immediately. [chars] is the request type, the first [dec] is the source switch, the second [dec] is the destination switch, and the third [dec] is the error value.

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

Error Message    SESA-2-MASTER_THREAD_FAIL: Failed to start master thread processes 
(location [chars]) on switch [dec](rebooting...)(Err [dec])

Explanation The master rekey processess are not starting and the switch will reboot automatically. [chars] is the request type, the first [dec] is the switch box bit, and the second [dec] is the error value.

Recommended Action If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

Error Message    SESA-2-REKEY_FAIL: Failed to rekey (location [chars]) (switch: 
[dec])(Err [dec]),(rebooting...)

Explanation The master rekey is failing and the switch will reboot automatically. [chars] is the type of request, the first [dec] is the switch box bit, and the second [dec] is the error value.

Error Message    SESA-3-MISMATCH: The [chars] is not compatible with SESA (location 
[chars]) (rebooting...)

Explanation The SESA mixed mode requires the system to support matching features and version. The first [chars] is the version and feature, and the second [chars] is the request type.

Recommended Action Use the right image version and license.

Error Message    SESA-3-INTERNAL_ERROR: There was an internal error (reason [chars]) 
(location [chars]) (rebooting...)

Explanation There was a SESA internal error. The first [chars] is the error value, and the second [chars] is the request type.

Recommended Action Check the error log and reboot if necessary. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

Error Message    SESA-3-REMOTE_AUTHENTICATION_FAIL: Failing AT Match check on (box 
[dec])(sn [chars])(op-1=[hex])(op-N= [hex])

Explanation Remote authentication failed. [dec] is the switch number, [chars] is the switch box bit, the first [hex] is the first index value, and the second [hex] is the last index value.

Recommended Action Check the authorization key or error log and reboot if necessary. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

Error Message    SESA-3-INTERNAL_HRPC_ERROR: hrpc bloc error [chars](Error [dec])(idx 
[dec])(tobits= [hex])

Explanation HRPC is not allowing SESA to complete. [chars] is the request type, the first [dec] is the error value, the second [dec] is the switch box bit, and [hex] is the destination switch box bit.

Recommended Action Check error log for sequence, check stack cables, and reboot. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

Error Message    SESA-3-ZEROIZATION_FAIL, MSG_TRACEBACK: Key Zeroizatiion failed on 
switch [dec]

Explanation There is a problem with memory references, which are preventing zeroization of the SESA Keys. If it recurs, it may be an attack. [dec] is the switch box bit.

Error Message    SESA-3-AKS_DECRYPT_FAIL:Failed to decrypt AKS (location 
[chars])(reason [chars])(src [dec])(dest [dec])(Err [dec])

Explanation The remote switch failed to decrypt. The first [chars] is the request type, the second [chars] is the reason for failure, the first [dec] is the source switch, the second [dec] is the destination switch, the third [dec] is the error value.

Recommended Action Check the authorozation key on the master switch and the remote switch and reboot. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

Error Message    SESA_ESP-3-NOT_READY **Panic**-The system is not ready (mode [chars]) 
for SESA (class [dec])(rebooting...)

Explanation There is a race condition in the initialization reboot. [chars] is either encrypt or decrypt, and [dec] is the class value.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support privileged EXEC command to gather data that might provide information about the error. If you cannot determine the nature of the error from the error message or from the show tech-support command display, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message    SESA_ESP-3-BLOCK_FAILURE: Failure to [chars] ecrypted block (reason 
[chars]) (class [dec])(pd_sz [dec])(dlen [dec]) Too many indicate a critical 
situation

Explanation There is an error in the request. The message normally appears after a master failover. The first [chars] is the action, the second [chars] is the failure reason, the first [dec] is the class value, the second [dec] is the padding size, the third [dec] is the data length.

Error Message    SESA_ESP-3-REPLAY_ERROR: Possible replay on switch (Switch 
[dec]->Switch([dec]),(seq= [hex])(curr= [hex])(class [dec])

Explanation The switches are replaying and this could be an intrusion. The first [dec] is the source switch box bit, the second [dec] is the destination switch box bit, the third [dec] is the class value, the first [hex] is the message sequence, and the second [hex] is the error value.

Recommended Action Check the log and reboot the switch. You can also change the authorization keys on all stack members to prevent an attack. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

Error Message    SESA-6-THREAD_START: Starting [chars] thread on switch [dec]

Explanation SESA rekeying threads are spinning off after starting successfully. [chars] is the name of the thread, [dec] is the switch box bit.

Recommended Action No action is required.

SPAN Messages

Error Message    SPAN-3-MEM_UNAVAIL: Memory was not available to perform the SPAN 
operation.

Explanation The system could not perform a SPAN operation because of lack of memory.

Recommended Action Reduce other system activity to ease the memory demands.

Error Message    SPAN-3-UNKN_ERR: An internal error occurred during a SPAN operation.

Explanation SPAN detected an error in its internal operation.

Recommended Action The error might be transient. Try the SPAN operation again. If a second attempt also fails, reload the switch by using the reload privileged EXEC command to complete the operation.

Error Message    SPAN-3-UNKN_ERR_PORT: An internal error occurred when configuring SPAN 
on port [chars].

Explanation SPAN detected an error in its internal operation. [chars] is the interface.

Recommended Action The error might be transient. Try the SPAN operation again. If the second attempt also fails, reload the switch by using the reload privileged EXEC command to complete the operation.

SPANTREE Messages

Error Message    SPANTREE-2-BLOCK_BPDUGUARD: Received BPDU on port [chars] with BPDU 
Guard enabled. Disabling port.

Explanation A bridge protocol data unit (BPDU) was received on an interface that has the spanning tree BPDU guard feature enabled. As a result, the interface was administratively shut down. [chars] is the interface name.

Recommended Action Either remove the device sending BPDUs, or disable the BPDU guard feature. The BPDU guard feature can be locally configured on the interface or globally configured on all ports that have PortFast enabled. To disable BPDU guard on an interface, use the no spanning-tree bpduguard enable interface configuration command. To disable BPDU guard globally, use the no spanning-tree portfast bpduguard default global configuration command. After you have removed the device or disabled BPDU guard, re-enable the interface by entering the no shutdown interface configuration command.

Error Message    SPANTREE-2-BLOCK_BPDUGUARD_VP: Received BPDU on port [chars], vlan 
[dec] with BPDU Guard enabled. Disabling vlan.

Explanation A BPDU was received on the interface and the VLAN specified in the error message. The spanning tree BPDU guard feature was enabled and configured to shut down the VLAN. The VLAN was error disabled. [chars] is the interface, and [dec] is the VLAN.

Recommended Action Either remove the device sending BPDUs, or disable the BPDU guard feature. The BPDU guard feature can be configured locally on the interface or configured globally on all ports that have Port Fast enabled. Re-enable the interface and VLAN by entering the clear errdisable privileged EXEC command.

Error Message    SPANTREE-2-BLOCK_PVID_LOCAL: Blocking [chars] on [chars]. Inconsistent 
local vlan.

Explanation The spanning-tree port associated with the listed spanning-tree instance and interface was held in the spanning-tree blocking state until the port VLAN ID (PVID) inconsistency is resolved. The listed spanning-tree instance is that of the native VLAN ID of the listed interface. The first [chars] is the interface, and the second [chars] is the spanning-tree instance.

Recommended Action Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. When corrected, spanning tree automatically unblocks the interfaces, as appropriate.

Error Message    SPANTREE-2-BLOCK_PVID_PEER: Blocking [chars] on [chars]. Inconsistent 
peer vlan.

Explanation The spanning-tree port associated with the listed spanning-tree instance and interface is held in the spanning-tree blocking state until the port VLAN ID (PVID) inconsistency is resolved. The listed spanning-tree instance is that of the native VLAN ID of the interface on the peer switch to which the listed interface is connected. The first [chars] is the interface, and the second [chars] is the spanning-tree instance.

Recommended Action Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. When interface inconsistencies are corrected, spanning tree automatically unblocks the interfaces.

Error Message    SPANTREE-2-CHNL_MISCFG: Detected loop due to etherchannel 
misconfiguration of [chars] [chars].

Explanation The system detected a misconfiguration of a channel group. For example, the ports on one side of the EtherChannel either are not configured to be in the channel or did not bundle into the channel, and the other side has successfully bundled the ports into the EtherChannel. The first [chars] is the port, and the second [chars] is the VLAN.

Recommended Action Identify the local ports by using the show interfaces status err-disabled privileged EXEC command, and then check the EtherChannel configuration on the remote device by using the show etherchannel summary privileged EXEC command on the remote device. After the configuration is correct, enter the shutdown and then no shutdown interface configuration commands on the associated port-channel interfaces.

Error Message    SPANTREE-2-LOOPGUARD_BLOCK: Loop guard blocking port [chars] on 
[chars].

Explanation The spanning-tree message age timer expired because no BPDUs were received from the designated bridge. Because this condition could be caused by a unidirectional-link failure, the interface is put into the blocking state and marked as loopguard-inconsistent to prevent possible loops from being created. The first [chars] is the port name, and the second [chars] is the spanning-tree mode displayed in the show spanning-tree privileged EXEC command.

Recommended Action Enter the show spanning-tree inconsistentports privileged EXEC command to review the list of interfaces with loopguard inconsistencies. Find out why devices connected to the listed ports are not sending BPDUs. One reason might be that they are not running the STP. If so, you should disable loop guard on the inconsistent interfaces by using the spanning-tree guard none interface configuration command or by starting the STP on the remote side of the links.

Error Message    SPANTREE-2-LOOPGUARD_CONFIG_CHANGE: Loop guard [chars] on port [chars] 
on [chars].

Explanation The spanning-tree loopguard configuration for the listed interface was changed. If enabled, the interface is placed into the blocking state. It is marked as loopguard-inconsistent when the message-age timer expires because no BPDUs were received from the designated bridge. This feature is mainly used to detect unidirectional links. The first [chars] is the loopguard state (enable or disable), the second [chars] is the interface name, and the third [chars] is the spanning-tree instance.

Recommended Action Verify that this is the desired configuration for the listed interface. Correct it if it is not.

Error Message    SPANTREE-2-LOOPGUARD_UNBLOCK: Loop guard unblocking port [chars] on 
[chars].

Explanation The listed interface received a BPDU. If the inconsistency was caused by a unidirectional link failure, the problem no longer exists. The loopguard-inconsistency is cleared for the interface, which is taken out of the blocking state, if appropriate. The first [chars] is the port name, and the second [chars] is the spanning-tree mode displayed in the show spanning-tree privileged EXEC command.

Recommended Action No action is required.

Error Message    SPANTREE-2-PVSTSIM_FAIL: Blocking [chars] port [chars]: Inconsistent 
[chars] PVST BPDU received on VLAN [dec], claiming root [dec]:[enet]

Explanation The specified port on the multiple spanning-tree (MST) switch was blocked. When a designated port on an MST switch is connected to a PVST+ switch, the CIST (MST00) information on the port of the MST switch must be consistently superior (lower bridge ID, lower path cost, and so forth) to the information in all the PVST+ messages. If the port is the root, the CIST (MST00) information on the MST switch must be consistently inferior to all the PVST+ messages. If this constraint is violated, the port on the MST switch is blocked to prevent a potential bridging loop. The first [chars] is the MST switch, the second [chars] is the port, and the third [chars] is the PVST+ switch. The first [dec] is the VLAN ID, the second [dec] is the MST switch, and [enet] is the MST-switch MAC address.

Recommended Action When STP is converging after a new switch or switch port is added to the topology, this condition might happen briefly. In such cases, the port unblocks automatically. If the port remains blocked, identify the root bridge as reported in the message, and configure the appropriate priority for the VLAN spanning tree, consistent with the CIST role on the port of the MST switch.

There could be additional inconsistencies not shown in the message, and the port does not recover until all these are cleared. To determine which other VLANs have inconsistencies, disable and re-enable the port. This message appears again and specifies another VLAN with inconsistencies to be fixed. Repeat this process until all inconsistencies on all VLANs are cleared.

Error Message    SPANTREE-2-PVSTSIM_OK: PVST Simulation inconsistency cleared on port 
[chars].

Explanation The specified interface was not receiving PVST BPDUs advertising information that was consistent with the CIST port information. The PVST simulation inconsistency was cleared, and the interface was returned to normal operation. [chars] is the port.

Recommended Action No action is required.

Error Message    SPANTREE-2-RECV_1Q_NON_1QTRUNK: Received 802.1Q BPDU on non 802.1Q 
trunk [chars] [chars].

Explanation The interface that received a Shared Spanning Tree Protocol (SSTP) BPDU was in trunk mode but was not using 802.1Q encapsulation. The first [chars] is the interface, and the second [chars] is the VLAN.

Recommended Action Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected are in the same mode (access or trunk). If the mode is trunk, verify that both interfaces have the same encapsulation (ISL or IEEE 802.1Q). If the encapsulation types are different, use the switchport trunk encapsulation interface configuration command to make them consistent. When the encapsulation is consistent, spanning tree automatically unblocks the interface.

Error Message    SPANTREE-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on [chars] 
[chars].

Explanation The listed interface received an SSTP BPDU without the VLAN ID tag. The BPDU is discarded. The first [chars] is the interface, and the second [chars] is the VLAN that received the SSTP BPDU.

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 error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

Error Message    SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 
[dec] on [chars] [chars].

Explanation The listed interface received an SSTP BPDU that is tagged with a VLAN ID that does not match the VLAN ID that received the BPDU. This occurs when the native VLAN is not consistently configured on both ends of an 802.1Q trunk. [dec] is the VLAN ID, the first [chars] is the port, and the second [chars] is the VLAN.

Recommended Action Verify that the configurations of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. When the configurations are consistent, spanning tree automatically unblocks the interfaces.

Error Message    SPANTREE-2-ROOTGUARD_BLOCK: Root guard blocking port [chars] on 
[chars].

Explanation The listed interface received a BPDU that advertises a superior spanning-tree root bridge (lower bridge ID, lower path cost, and so forth) than that in use. The interface is put into blocking state and marked as root-guard inconsistent to prevent a suboptimal spanning-tree topology from forming. The first [chars] is the port name, and the second [chars] is the spanning-tree mode displayed in the output of the show spanning-tree privileged EXEC command.

Recommended Action Enter the show spanning-tree inconsistentports privileged EXEC command to review the list of interfaces with root-guard inconsistencies. Find out why devices connected to the listed ports are sending BPDUs with a superior root bridge, and take action to prevent more occurrences. When the inaccurate BPDUs have been stopped, the interfaces automatically recover and resume normal operation. Check if it is appropriate to have root guard enabled on the interface.

Error Message    SPANTREE-2-ROOTGUARD_CONFIG_CHANGE: Root guard [chars] on port [chars] 
on [chars].

Explanation The spanning-tree root guard configuration for the listed interface changed. If enabled, any BPDU received on this interface that advertises a superior spanning-tree root bridge (lower bridge ID, lower path cost, and so forth) to that already in use causes the interface to be put into the blocking state and marked as root-guard inconsistent. The first [chars] is the root-guard state (enable or disable), the second [chars] is the interface, and the third [chars] is the spanning-tree instance.

Recommended Action Verify that this is the desired configuration for the listed interface. Correct it if it is not the desired configuration.

Error Message    SPANTREE-2-ROOTGUARD_UNBLOCK: Root guard unblocking port [chars] on 
[chars].

Explanation The listed interface was not receiving BPDUs advertising a superior root bridge (lower bridge ID, lower path cost, and so forth). The root-guard inconsistency was cleared for the interface, and the blocking state was removed from the interface. The first [chars] is the port name, and the second [chars] is the spanning-tree mode displayed in show spanning-tree privileged EXEC command.

Recommended Action No action is required.

Error Message    SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking [chars] on [chars]. Port 
consistency restored.

Explanation The port VLAN ID or port type inconsistencies were resolved, and spanning tree will unblock the listed interface of the listed spanning-tree instance. The first [chars] is the interface, and the second [chars] is the spanning-tree instance.

Recommended Action No action is required.

Error Message    SPANTREE-3-BAD_PORTNUM_SIZE: Rejected an attempt to set the port 
number field size to [dec] bits (valid range is [dec] to [dec] bits).

Explanation An error occurred in the platform-specific code that caused it to request more or less bits than are possible. The spanning-tree port identifier is a 16-bit field, which is divided evenly between the port priority and port number, with each subfield being 8 bits. This allows the port number field to represent port numbers between 1 and 255. However, on systems with more than 255 ports, the size of port number portion of the port ID must be increased to support the number of ports. This is performed by the spanning-tree subsystem at system initialization because the maximum number of ports on a particular platform will not change. This error occurs because of an error in the platform-specific code, which causes it to request more or less bits than are possible. The first [dec] is the number of bits for the port number, and the second and third [dec] describe the valid range.

Error Message    SPANTREE-3-PORT_SELF_LOOPED: [chars] disabled.- received BPDU src mac 
([enet]) same as that of interface.

Explanation A BPDU was received on the listed interface with a source MAC address that matches the one assigned to the listed interface. This means that a port might be looped back to itself, possibly because of an installed diagnostic cable. The interface will be administratively shut down. [chars] is the interface that received the BPDU, and [enet] is the source MAC address.

Recommended Action Verify the interface configuration and test any cable connected to the interface. When the problem is resolved, re-enable the interface by entering the no shutdown interface configuration command.

Error Message    SPANTREE-3-PRESTD_NEIGH: pre-standard MST interaction not configured 
([chars]).

Explanation The switch received a prestandard MST BPDU on an interface that was not configured to send prestandard MST BPDUs. The switch automatically adjusts its configuration on the interface and starts sending prestandard BPDUs. However, the switch does not automatically detect all prestandard neighbors, and we recommend that you configure the interface to send prestandard MST BPDUs by using the spanning-tree mst pre-standard interface configuration command. This warning message only appears once. [chars] is the interface.

Recommended Action Use the spanning-tree mst pre-standard interface configuration command on all the interfaces to which other switches running Cisco's prestandard MST version are connected. We recommend that you migrate all the switches in the network to the IEEE MST standard version.

Error Message    SPANTREE-4-PORT_NOT_FORWARDING: [chars] [chars] [chars] [chars].

Explanation A port-not-forwarding alarm was set or cleared. The first [chars] is the mode, and the second [chars] is the severity. The third [chars] is the interface name, and the fourth [chars] is the alarm string.

Error Message    SPANTREE-5-EXTENDED_SYSID: Extended SysId [chars] for type [chars].

Explanation The extended system ID feature was either enabled or disabled for the given type of spanning tree. If enabled, the spanning-tree instance identifier is stored in the lower portion of the bridge ID priority field and limits the allowed values for the bridge priority from 0 to 61440, in increments of 4096. If disabled, the bridge ID priority field consists only of the configured priority, but some spanning-tree features might not be available on a given platform (for example, support for 4096 VLANs). On some platforms, this feature might be mandatory. The first [chars] is the extended system ID state (enable or disable), and the second [chars] is the spanning-tree instance.

Recommended Action No action is required.

Error Message    SPANTREE-5-ROOTCHANGE: Root Changed for [chars] [dec]: New Root Port 
is [chars]. New Root Mac Address is [enet].

Explanation The root switch changed for a spanning-tree instance. The first [chars] and [dec] is the interface ID for the previous root port, the second [chars] is the interface ID for the new root port, and [enet] is the Ethernet address of the new root port.

Recommended Action No action is required.

Error Message    SPANTREE-5-TOPOTRAP: Topology Change Trap for [chars] [dec].

Explanation A trap was generated because of a topology change in the network.

Recommended Action No action is required.

Error Message    SPANTREE-6-PORTADD_ALL_VLANS: [chars] added to all Vlans

Explanation The interface was added to all VLANs. [chars] is the added interface.

Recommended Action No action is required.

Error Message    SPANTREE-6-PORTDEL_ALL_VLANS: [chars] deleted from all Vlans

Explanation The interface was deleted from all VLANs. [chars] is the deleted interface.

Recommended Action No action is required.

Error Message    SPANTREE-6-PORT_STATE: Port [chars] instance [dec] moving from [chars] 
to [chars].

Explanation The port state changed. The first [chars] is the interface name. [dec] is the spanning-tree instance ID. The second [chars] is the old state (such as listening, learning, or forwarding, and so forth), and the third [chars] is the new state.

Recommended Action No action is required.

Error Message    SPANTREE-7-BLOCK_PORT_TYPE: Blocking [chars] on [chars]. Inconsistent 
port type.

Explanation The listed interface is in the spanning-tree blocking state until the port-type inconsistency is resolved. The first [chars] is the interface, and the second [chars] is the spanning-tree instance.

Recommended Action Verify that the configuration and operational states of the listed interface and those of the interface to which it is connected are in the same mode (access or trunk). If the mode is trunk, verify that both interfaces have the same encapsulation (ISL or IEEE 802.1Q). When these parameters are consistent, spanning tree automatically unblocks the interface.

Error Message    SPANTREE-7-PORTDEL_SUCCESS: [chars] deleted from Vlan [dec].

Explanation The interface was deleted from VLAN. [chars] is the interface, and [dec] is the VLAN ID.

Recommended Action No action is required.

Error Message    SPANTREE-7-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk 
[chars] [chars].

Explanation The listed interface that received an STP BPDU was not an operational trunking interface. The first [chars] is the port name, and the second [chars] is the VLAN name.

Recommended Action Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected are in the same mode (access or trunk). If the mode is trunk, verify that both interfaces have the same encapsulation (none, ISL, or IEEE 802.1Q). When these parameters are consistent, spanning tree automatically unblocks the interface.

SPANTREE_FAST Messages

Error Message    SPANTREE_FAST-7-PORT_FWD_UPLINK: [chars] [chars] moved to Forwarding 
(UplinkFast).

Explanation The listed interface was selected as the new path to the root switch for the listed spanning-tree instance. The first [chars] is the spanning-tree instance, and the second [chars] is the interface.

Recommended Action No action is required.

SPANTREE_VLAN_SW Messages

Error Message    SPANTREE_VLAN_SW-2-MAX_INSTANCE: Platform limit of [dec] STP instances 
exceeded. No instance created for [chars] (port [chars]).

Explanation The number of currently active VLAN spanning-tree instances reached a platform-specific limit. No additional VLAN instances created until the existing number of instances drops below the platform limit. [dec] is the spanning-tree instance limit, the first [chars] is the smallest VLAN ID of those VLANs that cannot have spanning-tree instances created, and the second [chars] is the port number.

Recommended Action Reduce the number of currently active spanning-tree instances by either disabling some of the currently active spanning-tree instances or deleting the VLANs associated with them. You must manually enable the spanning trees that could not be created because of limited instances.

Error Message    SPANTREE_VLAN_SHIM-3-ADD_REGISTRY_FAILED: Subsystem [chars] fails to 
add callback function [chars]

Explanation A subsystem did not add its callback functions. Use this message only for debugging. The first [chars] is the subsystem name, and the second [chars] is the function name.

Recommended Action No action is required.

Error Message    SPANTREE_VLAN_SHIM-2-MAX_INSTANCE: Platform limit of [dec] STP 
instances exceeded. No instance created for [chars] (port [chars]).

Explanation The number of VLAN spanning-tree instances reached the maximum limit. No more VLAN instances are created until instances are less than the maximum. [dec] is the maximum, the first [chars] is the VLAN for which an STP instance is not created, and the second [chars] is the port number.

For example, when you are configuring spanning tree and the maximum is 128 instances:

–If the switch has already created 128 instances and you enter the vlan 200-1000 global interface configuration command, the first [chars] is 200, and an STP instance for VLAN 200 is not created. STP instances are also not created for the remainder of the VLANs in the range.

–If the switch has already created 100 instances and you enter the vlan 200-1000 global interface configuration command, the first [chars] is 228. The switch creates STP instances for VLAN 200 to VLAN 227, but not for VLAN 228. STP instances are also not created for the remainder of the VLANs in the range.

Recommended Action Reduce the number of active spanning-tree instances by either disabling some or deleting the VLANs associated with them. To create STP instances, create them manually. If you do not, the switch automatically creates an STP instance when a VLAN is created.

For example, if the switch has already created 128 instances and you want to create an STP instance for VLAN 200, remove a spanning-tree instance with one of the following commands:

–To delete one of the VLANs, enter the no vlan vlan-id global configuration command.

–To disable spanning tree on a per-VLAN basis, enter the no spanning-tree vlan-id global configuration command.

Enter the spanning-tree 200 global configuration command to create an instance for VLAN 200.

STORM_CONTROL Messages

Error Message    STORM_CONTROL-3-FILTERED: A [chars] storm detected on [chars]. A 
packet filter action has been applied on the interface.

Explanation The amount of traffic detected on the interface exceeded the configured threshold values. The system is filtering the excess traffic. The first [chars] is the traffic type, and the second [chars] is the interface.

Recommended Action Determine and fix the root cause of the excessive traffic on the interface.

Error Message    STORM_CONTROL-3-SHUTDOWN: A packet storm was detected on [chars]. The 
interface has been disabled.

Explanation The amount of traffic detected on the interface exceeded the configured threshold values. Because the interface is configured to shut down if a packet storm event is detected, it has been placed in an error disabled state. [chars] is the affected interface.

Recommended Action Use the errdisable recovery global configuration command to re-enable the interface. Determine and fix the root cause of the excessive traffic on the interface.

SUDI Messages

Error Message    SUDI-1-INTERNAL_ERROR: Secure UDI encountered an internal error

Explanation An internal error occurred that prevented the switch from authenticating itself.

Error Message    SUDI-1-VALIDATION_ERROR: Secure UDI validation failed

Explanation An error occurred in either retrieving the Unique Device Identifier (UDI) data, parsing the UDI data, or validating the UDI data through cryptographic checks; or a mismatch occurred in the UDI. This failure prevented the switch from authenticating itself.

SUPERVISOR Messages

Error Message    SUPERVISOR-3-FATAL: [chars].

Explanation An internal error occurred in the supervisor ASIC. [chars] is the detailed error message.

SUPQ Messages

Error Message    SUPQ-3-THROTTLE_CPU_QUEUE: Invalid application ID [dec] used for 
throttling.

Explanation An application passed an invalid application ID for throttle check. [dec] is the internal application identifier.

Error Message    SUPQ-4-CPUHB_RECV_STARVE: [chars].

Explanation The system detected that messages directed to the CPU are delayed. [chars] is the detailed error message.

Error Message    SUPQ-4-CPUHB_SLOW_TRANSMIT: [chars].

Explanation The system is warning you about a slowdown of the sending interface. [chars] is the detailed error message.

Error Message    SUPQ-4-CPUHB_TX_FAIL: [chars].

Explanation The system is warning you about the sending interface discarding the heartbeat message. [chars] is the detailed error message.

Error Message    SUPQ-4-PORT_QUEUE_STUCK: Port queue Stuck for asic [dec] port [dec] 
queue [dec].

Explanation The system detected that an interface queue was not being cleared in a reasonable time. The first [dec] is the ASIC, the second [dec] is the interface, and the third [dec] is the queue number.

Error Message    SUPQ-4-RECV_QUEUE_STUCK: Receive queue Stuck for asic [dec] queue 
[dec].

Explanation The system detected that the receiving queue was not being cleared in a reasonable time. The first [dec] is the ASIC, and the second [dec] is the queue number.

SW_MACAUTH Messages

Error Message    SW_MACAUTH-4-UNAUTH_MAC: Unauthenticated MAC [enet] on port [chars]

Explanation The switch received an unauthenticated MAC address on the specified port. [enet] is the unauthenticated MAC address, and [chars] is the port.

Recommended Action No action is required.

Error Message    SW_MACAUTH-5-CLEAR_TABLE: MAC Authentication Table Cleared

Explanation The MAC authentication table was cleared.

Recommended Action No action is required.

Error Message    SW_MACAUTH-5-MACAUTH_ENADSA: MAC Authentication [chars]

Explanation The MAC authentication was enabled or disabled. [chars] is the MAC authentication status, either enabled or disabled.

Recommended Action No action is required.

Error Message    SW_MACAUTH-5-MAC_AUTHENTICATED: MAC [enet] was authenticated

Explanation The switch received a command to authenticate a MAC address. [enet] is the MAC address.

Recommended Action No action is required.

SW_VLAN Messages

This section contains the VLAN manager messages. The VLAN manager receives information from the VTP and enables the VLAN membership on all interfaces through the port manager.

Error Message    SW_VLAN-3-MALLOC_FAIL: Failed to allocate [dec] bytes

Explanation Memory allocation failed. [dec] is the number of bytes.

Error Message    SW_VLAN-3-VLAN_DAT_CACHE_SEQUENCE: Out of sequence vlan.dat sync 
message. Expected: [dec]; received: [dec].

Explanation The vlan.dat file was synchronized to the STANDBY through one or more checkpoint messages from ACTIVE. The sequence number for each set of checkpoint messages starts with 1. These messages are cached at the STANDBY until the end-of-set indicator is received. The STANDBY received a checkpoint message with a sequence number that does not match the expected sequence number. The first [dec] is the expected checkpoint message sequence number, and the second [dec] is the received checkpoint message sequence number.

Error Message    SW_VLAN-3-VLAN_PM_NOTIFICATION_FAILURE: VLAN Manager synchronization 
failure with Port Manager over [chars].

Explanation The VLAN manager dropped a notification from the port manager because of lack of ready pool space. [chars] is the type of port manager notification.

Error Message    SW_VLAN-3-VTP_PROTOCOL_ERROR: VTP protocol code internal error 
[chars].

Explanation The VTP code encountered an unexpected error while processing a configuration request, a packet, or a timer expiration. [chars] is the internal error.

Error Message    SW_VLAN-4-BAD_PM_VLAN_COOKIE_RETURNED: VLAN manager unexpectedly 
received a bad PM VLAN cookie from the Port Manager, VLAN indicated [dec].

Explanation The VLAN manager received an upcall and a VLAN cookie from the port manager that translated to a bad VLAN ID. [dec] is the VLAN ID.

Recommended Action Find out more about the error by using the show tech-support privileged EXEC command. Copy the error message exactly as it appears on the console or system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

Error Message    SW_VLAN-4-BAD_STARTUP_VLAN_CONFIG_FILE: Failed to configure VLAN from 
startup-config. Fallback to use VLAN configuration file from non-volatile memory.

Explanation The VLAN software did not use the VLAN configuration from the startup-configuration file. It will use the binary VLAN configuration file in NVRAM.

Recommended Action No action is required.

Error Message    SW_VLAN-4-BAD_VLAN_CONFIGURATION_FILE: VLAN configuration file 
contained incorrect verification word [hex].

Explanation The VLAN configuration file read by the VLAN manager did not begin with the correct value. The VLAN configuration file is invalid, and it has been rejected. [hex] is the incorrect verification value.

Error Message    SW_VLAN-4-BAD_VLAN_CONFIGURATION_FILE_VERSION: VLAN configuration 
file contained unknown file version [dec].

Explanation The VLAN configuration file read by the VLAN manager contained an unrecognized file version number, which might mean an attempt to regress to an older version of the VLAN manager software. [dec] is the file version number.

Error Message    SW_VLAN-4-BAD_VLAN_TIMER_ACTIVE_VALUE: Encountered incorrect VLAN 
timer active value [chars].

Explanation A VLAN timer was detected as active when it should have been inactive or as inactive when it should have been active. [chars] is the VLAN timer active value.

Error Message    SW_VLAN-4-EXT_VLAN_INTERNAL_ERROR: Extended VLAN manager received an 
internal error [dec] from [chars] [chars].

Explanation An unexpected error code was received by the VLAN manager from the extended-range VLAN configuration software. [dec] is the error code. The first [chars] is the function, and the second [chars] describes the error code.

Error Message    SW_VLAN-4-EXT_VLAN_INVALID_DATABASE_DATA: Extended VLAN manager 
received bad data of type [chars] value [dec] from function [chars].

Explanation Invalid data was received by the extended-range VLAN manager from an extended-range VLAN configuration database routine. The first [chars] is the data type, [dec] is the number received, and the second [chars] is the function name.

Error Message    SW_VLAN-4-IFS_FAILURE: VLAN manager encountered file operation error 
call = [chars] / file = [chars] / code = [dec] ([chars]) / bytes transferred = 
[dec].

Explanation The VLAN manager received an unexpected error return from a Cisco IOS file system (IFS) call while reading the VLAN database. The first [chars] is the function call name, the second [chars] is the file name, the first [dec] is the error code, the third [chars] is the textual interpretation of the error code, and the second [dec] is the number of bytes transferred.

Error Message    SW_VLAN-4-NO_PM_COOKIE_RETURNED: VLAN manager unexpectedly received a 
null [chars] type cookie from the Port Manager, data reference [chars].

Explanation The VLAN manager queried the port manager for a reference cookie but received a NULL pointer instead. The first [chars] is the type of port manager cookie, and the second [chars] is the interface or VLAN that is the source of the problem.

Error Message    SW_VLAN-4-STARTUP_EXT_VLAN_CONFIG_FILE_FAILED: Failed to configure 
extended range VLAN from startup-config. Error [chars].

Explanation The VLAN software did not use an extended-range VLAN configuration from the startup configuration file. All extended-range VLAN configurations are lost after the system boots up. [chars] is a description of the error code.

Recommended Action No action is required.

Error Message    SW_VLAN-4-VLAN_CREATE_FAIL: Failed to create VLANs [chars]: [chars].

Explanation The specified VLANs could not be created. The port manager might not have completed the VLAN creation requests because the VLANs already exist as internal VLANs. The first [chars] is the VLAN ID, and the second [chars] describes the error.

Recommended Action Check the internal VLAN usage by using show vlan internal usage privileged EXEC command, reconfigure the feature that is using the internal VLANs, and create the VLANs again. If this message appears again, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

Error Message    SW_VLAN-4-VTP_INTERNAL_ERROR: VLAN manager received an internal error 
[dec] from vtp function [chars] [chars].

Explanation The VLAN manager received an unexpected error code from the VTP configuration software. [dec] is the error code, the first [chars] is the VTP function, and the second [chars] is the error-code description.

Error Message    SW_VLAN-4-VTP_INVALID_DATABASE_DATA: VLAN manager received bad data of 
type [chars] value [dec] from vtp database function [chars].

Explanation The VLAN manager received invalid data from a VTP configuration database routine. The first [chars] is the data type, [dec] is the inappropriate value that was received, and the second [chars] is the VTP database function.

Error Message    SW_VLAN-4-VTP_INVALID_EVENT_DATA: VLAN manager received bad data of 
type [chars] value [dec] while being called to handle a [chars] event.

Explanation The VLAN manager received invalid data from the VTP configuration software. The first [chars] is the data type, [dec] is the value of that data, and the second [chars] is the VTP event.

Error Message    SW_VLAN-4-VTP_SEM_BUSY: VTP semaphore is unavailable for function 
[chars]. Semaphore locked by [chars].

Explanation The VTP database is not available. You should access the VTP database later. The first [chars] is the function name that you want to configure, and the second [chars] is the function name that is using the VTP database.

Error Message    SW_VLAN-6-OLD_CONFIG_FILE_READ: Old version [dec] VLAN configuration 
file detected and read OK. Version [dec] files will be written in the future.

Explanation The VLAN software detected an old version of the VLAN configuration file format. It interpreted the file, but it will use the new format in the future. The first [dec] is the old version number, and the second [dec] is the new version number.

Recommended Action No action is required.

Error Message    SW_VLAN-6-VLAN_DAT_CACHE_EXISTS: Unexpected vlan.dat cache exists. 
Removing the cache and continuing the sync with new set.

Explanation This notification message means that the switch functionality is unaffected.

Recommended Action No action is required.

Error Message    SW_VLAN-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to [chars].

Explanation The VTP domain name was changed through the configuration to the name specified in the message. [chars] is the changed domain name.

Recommended Action No action is required.

Error Message    SW_VLAN-6-VTP_MODE_CHANGE: VLAN manager changing device mode from 
[chars] to [chars].

Explanation An automatic VTP-mode device-change occurred upon receipt of a VLAN configuration database message containing more than a set number of VLANs. The first [chars] is the previous mode, and the second [chars] is the current mode.

Recommended Action No action is required.

SWITCH_QOS_TB Messages

Error Message    SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: [chars] detected on port 
[chars], port's configured trust state is now operational.

Explanation A trusted boundary detected a device matching the trusted device setting for the port and has modified the port trust state. The first [chars] is the trusted device, and the second [chars] is the port.

Recommended Action No action is required.

Error Message    SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: [chars] no longer detected on port 
[chars], operational port trust state is now untrusted.

Explanation A trusted boundary lost contact with a trusted device and has set the port trust state to untrusted. The first [chars] is the trusted device, and the second [chars] is the port.

Recommended Action No action is required.

TCAMMGR Messages

Error Message    TCAMMGR-3-GROW_ERROR: cam region [dec] can not grow.

Explanation The specified CAM region was configured as a static region with a fixed number of entries, and a caller requested to add more CAM entries. [dec] is the CAM region.

Error Message    TCAMMGR-3-HANDLE_ERROR: cam handle [hex] is invalid.

Explanation The CAM handle used by the caller was invalid. [hex] is the handle value.

Error Message    TCAMMGR-3-INDEX_ERROR: cam value/mask index [dec] is invalid.

Explanation The CAM index used by the caller was invalid. [dec] is the index value.

Error Message    TCAMMGR-3-MOVE_ERROR: cam entry move from index [int] to index [int] 
failed.

Explanation Moving a CAM entry from one index to another failed. [int] is the index value.

Error Message    TCAMMGR-3-REGION_ERROR: cam region [dec] is invalid.

Explanation The CAM region was not valid. [dec] is the region.

Error Message    TCAMMGR-3-REGMASK_ERROR: invalid cam region [dec] mask [dec] pair.

Explanation A caller attempted to install an entry with an invalid mask for the region. Only a predetermined set of masks is allowed in a region. The first [dec] is the region, and the second [dec] is the mask.

UDLD Messages

Error Message    UDLD-0-STOPPED:UDLD process stopped:[chars].

Explanation The UDLD process stopped because it could not read the unique system identifier that was being used by UDLD. The system identifier is used to identify the device that is sending the UDLD packets. [chars] is the UDLD process name.

Recommended Action Reload the switch by using the reload privileged EXEC command. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.

VQPCLIENT Messages

Error Message    VQPCLIENT-2-INITFAIL: Platform-specific VQP initialization failed. 
Quitting.

Explanation An error occurred during initialization of the VQP client platform-specific code.

Error Message    VQPCLIENT-2-IPSOCK: Could not obtain IP socket.

Explanation An error occurred when the system attempted to open an IP socket to the VMPS.

Error Message    VQPCLIENT-2-PROCFAIL: Could not create process for VQP. Quitting.

Explanation An error occurred while creating a process for the VQP client.

Error Message    VQPCLIENT-2-SHUTDOWN: Interface [chars] shutdown by VMPS.

Explanation The VMPS directed that an interface be shut down. [chars] is the interface name.

Recommended Action No action is normally required. If you think that the port should not have been shut down, verify the configuration on the VMPS.

Error Message    VQPCLIENT-2-TOOMANY: Interface [chars] shutdown by active host limit.

Explanation The system shut down the specified interface because too many hosts requested access to that interface. [chars] is the interface name.

Recommended Action To enable the interface, remove the excess hosts, and enter the no shutdown interface configuration command.

Error Message    VQPCLIENT-3-THROTTLE: Throttling VLAN change on [chars].

Explanation An attempt was made to change the VLAN assignment for an interface more often than once every 10 seconds. The VLAN change is denied. [chars] is the interface name.

Recommended Action No action is normally required. If the message recurs, verify the VMPS configuration. Verify that unexpected hosts are not connected to the port.

Error Message    VQPCLIENT-3-VLANNAME: Invalid VLAN [chars] in response.

Explanation The VMPS specified an unknown VLAN name. [chars] is the VLAN name.

Recommended Action Check that the VLAN exists on the switch. Verify the VMPS configuration by entering the show vmps privileged EXEC command.

Error Message    VQPCLIENT-7-NEXTSERV: Trying next VMPS [IP_address].

Explanation The system lost connectivity with the current VMPS and was changing to the next server in its list. [IP_address] is the address of the next server in the list.

Recommended Action This is a debug message. No action is required.

Error Message    VQPCLIENT-7-PROBE: Probing primary server [IP_address].

Explanation The system was trying to reestablish connectivity with the primary VMPS at the given IP address.

Recommended Action This is a debug message. No action is required.

Error Message    VQPCLIENT-7-RECONF: Reconfirming VMPS responses.

Explanation The switch was reconfirming all responses with the VMPS.

Recommended Action This is a debug message. No action is required.

Bias-Free Language

Results

Chapter: Message and Recovery Procedures

Message and Recovery Procedures

ACLMGR Messages

AUTHMGR Messages

BACKUP_INTERFACE Messages

CMP Messages

DHCP_SNOOPING Messages

DOT1X Messages

DOT1X_SWITCH Messages

DTP Messages

DWL Messages

EC Messages

ENVIRONMENT Messages

EPM Messages

ETHCNTR Messages

EXPRESS_SETUP Messages

FLASH_DEVICE Messages

GBIC_SECURITY Messages

GBIC_SECURITY_CRYPT Messages

HARDWARE Messages

HLFM Messages

IDBMAN Messages

IFMGR Messages

IGMP_QUERIER Messages

ILET Messages

ILPOWER Messages

IP_DEVICE_TRACKING_HA Messages

KEYMAN Messages

MAC_LIMIT Messages

MAC_MOVE Messages

PHY Messages

PLATFORM Messages

PLATFORM_ENV Messages

PLATFORM FRULink 10G Service Module Messages

PLATFORM_IPv6 Messages

PLATFORM_PM Messages

PLATFORM_RPC Messages

PLATFORM_VLAN Messages

PM Messages

PORT_SECURITY Messages

QOSMGR Messages

REP Messages

RMON Messages

SCHED Messages

SESA Messages

SPAN Messages

SPANTREE Messages

SPANTREE_FAST Messages

SPANTREE_VLAN_SW Messages

STORM_CONTROL Messages

SUDI Messages

SUPERVISOR Messages

SUPQ Messages

SW_MACAUTH Messages

SW_VLAN Messages

SWITCH_QOS_TB Messages

TCAMMGR Messages

UDLD Messages

VQPCLIENT Messages

Was this Document Helpful?

Contact Cisco