Table Of Contents
Message and Recovery Procedures
DHCP_SNOOPING_CAT3550 Messages
IP_DEVICE_TRACKING_HA Messages
NETWORK_PORT_SATELLITE Messages
Message and Recovery Procedures
This chapter describes the Catalyst 3750, 3560, 3550, 2970, and 2960 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.
The messages listed in this chapter do not include the hostname or the date/time stamp designation that displays only if the software is configured for system log messaging.
The chapter includes these message facilities:
•
AUTOQOS Messages (only Catalyst 3550 switches)
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
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].
Note
Explanation The ACL manager could not allocate the data structures needed to describe a VLAN map in a form that can be loaded into hardware. This error 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].
Note
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 create VMR data structures for access list [chars].
Note
Explanation The ACL manager was unable to allocate the value-mask result (VMR) data structures needed to describe an ACL in a form that can be loaded into hardware. This error is most likely caused by lack of available memory. [chars] is the access-list name.
Recommended Action Use a less complicated configuration that requires less memory.
Error Message ACLMGR-3-ACLTCAMFULL: Acl Tcam Full. Drop packets on Output Acl label [dec] on [chars] [chars].
Note
Explanation There are too many ACLs configured for the platform-specific ACL TCAM table to support. [dec] is the label number, and [chars] represents the layer. The first [chars] is for Layer 3; the second for 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.
Note
Explanation The system ran out of CPU DRAM when attempting 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].
Note
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.
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.
Error Message ACLMGR-3-INSERTFAIL: Insert of access-map [chars] #[dec] into [chars] label [dec] failed.
Note
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 are not now 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].
Note
Explanation An unrecoverable software error occurred while trying to merge the configured input features. [dec] are internal action codes.
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. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error. 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 ACLMGR-3-MAXRECURSION: Too many ([dec]) levels of recursion while merging ACLs (code [dec]).
Note
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].
Note
Explanation The ACL manager was unable to 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 instead. 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].
Note
Explanation The ACL manager was unable to 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); 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].
Note
Explanation An unrecoverable software error occurred while trying to merge the configured output features. [dec] are internal action codes.
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. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error. 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 ACLMGR-3-PACLTTABLE: Not in truth table: IPSrcGrd [dec] PACL [dec].
Note
Explanation An unrecoverable software error occurred while trying to merge the configured port ACL features. The first [dec] is the action specified by IP source guard, and the second [dec] is the action specified by the port ACL.
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. Enter the show running-config user EXEC command to gather data that might help identify the nature of the error. 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 ACLMGR-3-QOSTTABLE: Not in truth table: ACL [dec] in map, action [dec].
Note
Explanation A software error occurred while trying to merge a QoS policy map. The first [dec] is the ACL number, and the second [dec] is the action corresponding to the specified ACL number.
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.
Error Message ACLMGR-3-RELOADED: Reloading [chars] label [dec] feature.
Note
Explanation The ACL manager is now able to 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].
Note
Explanation An internal software error has occurred. [hex] is an internal action code.
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.
Error Message ACLMGR-3-UNLOADING: Unloading [chars] label [dec] feature.
Note
Explanation The ACL manager was unable to fit the complete configuration into the hardware, so some features will be applied in software. This prevents some or all of the packets in a VLAN from being forwarded in hardware and requires them to be 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.
AUTOQOS Messages
This section contains the automatic quality of service (auto-QoS) messages on Catalyst 3550 switches.
Error Message AUTOQOS-3-FEATURE_UNINITIALIZED: Feature not initialized in the platform, [chars].
Note
Explanation The feature did not initialize and is not enabled on any interface. [chars] is the feature name, which is auto-QoS.
Recommended Action If this feature does not operate, reboot the system by using the reload privileged EXEC command. Verify that this feature is supported on your switch by checking the software configuration guide for this software release.
BACKUP_INTERFACE Messages
This section contains the Flex Link messages.
Error Message BACKUP_INTERFACE-5-PREEMPT: Preempting interface [chars] in backup pair ([chars], [chars]), preemption mode is [chars]
Note
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 VLB detects a nontrunk port. [chars] is the interface name.
Recommended Action Configure the interface to operate in trunking mode.
BADTRANSCEIVER Messages
This section contains the BADTRANSCEIVER message.
Error Message BADTRANSCEIVER, PHY, LOG_WARNING: An innapropriate transceiver has been inserted in interface [chars].
Note
Explanation A defective module is installed in the specified interface. [chars] is the interface.
Recommended Action Remove the transceiver. If it was purchased from Cisco, contact your Cisco representative to have the transceiver replaced.
BSPATCH Messages
This section contains boot loader patch messages.
Error Message BSPATCH-1-RELOAD: System will reboot to activate newly patched Boot Loader.
Note
Explanation The switch will automatically reboot after the boot loader is patched.
Recommended Action If this message recurs, copy it 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 BSPATCH-1-PATCHED: Boot Loader patch ([chars]) installed.
Note
Explanation A boot loader patch is installed successfully. [chars] is the SDRAM refresh timer register setting.
Recommended Action If this message recurs, copy it 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 BSPATCH-3-FAILED: Failed to install Boot Loader patch ([chars]).
Note
Explanation The switch failed to apply a boot loader patch. [chars] is the SDRAM refresh timer register setting.
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.
CFGMGR Messages
This section contains the configuration manager messages on Catalyst 3750 switches.
Error Message CFGMGR-1-UNABLE_TO_SEND_RUN_CFG: unable to send running-cfg, bits: [hex], retrying...
Note
Explanation The system is unsuccessfully attempting to distribute the running configuration to the stack member switches. [hex] is the bit representation of the switch number.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message CFGMGR-1-UNABLE_TO_SEND_STARTUP_CFG: unable to send startup-cfg, bits: [hex], retrying...
Note
Explanation The system is unsuccessfully attempting to distribute the startup configuration file to the stack member switches. [hex] is the bit representation of the switch number.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message CFGMGR-3-ERROR_APPLYING_STARTUP_CFG: Error Applying Startup Config to Running Config.
Note
Explanation The system encountered an error when it was automatically applying the startup configuration to the running configuration.
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.
Error Message CFGMGR-4-MEMBER_WRITING_STARTUP_CFG: only master can do that.
Note
Explanation A stack member switch attempted to write to the startup configuration file; only the stack master can write to the startup configuration file.
Recommended Action No action is required.
Error Message CFGMGR-5-UNABLE_TO_USE_PROVISIONED_CFG: Switch [dec] will receive the default configuration.
Note
Explanation The switch type of the specified switch does not match the provisioned configuration for its switch number; therefore, the default configuration is applied to this switch. [dec] is the stack member number.
Recommended Action No action is required.
Error Message CFGMGR-6-APPLYING_RUNNING_CFG: as new master.
Note
Explanation A new stack master is applying the backed-up running configuration.
Recommended Action No action is required.
Error Message CFGMGR-6-SPURIOUS_MEMBER_ADD: CFG MGR Recvd Spurious New Member Notification: [int].
Note
Explanation The configuration manager received a notification about adding a stack member switch that already exists in the stack. [int] is the switch number.
Recommended Action If this message recurs, copy it 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 CFGMGR-6-UNABLE_TO_NVGEN_BUSY_RUNNING_CFG: config file busy, retrying...
Note
Explanation The stack master is temporarily unable to generate the stack running configuration because another process is generating the configuration file.
Recommended Action No action is required. The action will be tried again.
Error Message CFGMGR-6-UNABLE_TO_NVGEN_RUNNING_CFG: config file too large...
Note
Explanation The stack master is unable to generate the stack running configuration because the configuration file is too large.
Recommended Action Remove some configuration commands.
CMP Messages
This section contains the Cluster Membership Protocol (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]
Note
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]).
Note
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].
Note
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].
Note
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].
Note
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]).
Note
Explanation The device is removed from the cluster. [chars] is the cluster name.
Recommended Action No action is required.
DHCP_SNOOPING Messages
This section contains the DHCP snooping messages.
Error Message DHCP_SNOOPING-3-DHCP_SNOOPING_INTERNAL_ERROR: DHCP Snooping internal error, [chars].
Note
Explanation A software sanity check failed in the DHCP snooping process. [chars] is the error.
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.
Error Message DHCP_SNOOPING-4-AGENT_OPERATION_FAILED: DHCP snooping binding transfer failed. [chars].
Note
Explanation The DHCP snooping binding transfer process failed because of the specified reason for failure. [chars] is the reason for failure.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-4-AGENT_OPERATION_FAILED_N: DHCP snooping binding transfer failed ([dec]). [chars].
Note
Explanation The DHCP snooping binding transfer process failed because of the specified reason for failure [dec] is the number of failures, and [chars] is the reason for the failure. This message is rate-limited.
Recommended Action No action is required.
Error Message DHCP_SNOOPING-4-DHCP_SNOOPING_ERRDISABLE_WARNING: DHCP Snooping received [dec] DHCP packets on interface [chars].
Note
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]
Note
Explanation 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].
Note
Explanation The message means that 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].
Note
Explanation 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.
Note
Explanation If the DHCP snooping database agent loads the DHCP snooping bindings and 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.
Note
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].
Note
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.
Note
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.
Note
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.
Note
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.
Note
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.
Note
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.
Note
Explanation The specified number of bindings were ignored when the switch read the database file because the VLAN is no longer configured on the switch. [dec] is the number of bindings that the switch ignores.
Recommended Action No action required.
DHCP_SNOOPING_CAT3550 Messages
This section contains the DHCP snooping messages on Catalyst 3550 switches.
Error Message DHCP_SNOOPING_CAT3550-3-MVR_INSTALL: Cannot install [chars] ACLs for DHCP Snooping, probably no TCAM space.
Note
Explanation When DHCP snooping is enabled, access control lists (ACLs) need to be installed in the ternary content addressable memory (TCAM). DHCP snooping fails if there is insufficient space in the TCAM.
Recommended Action Reduce the number of input or output port ACLs (PACLs) and VLAN maps to make space in the TCAM.
Error Message DHCP_SNOOPING_CAT3550-3-UNEXPECTED_EVENT: Process received unknown event (major [hex], minor [hex]).
Note
Explanation A process received an event it was unable to handle.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section for more information.
DOT1Q_TUNNELLING Messages
This section contains the IEEE 802.1Q tunneling message on Catalyst 3550 switches. An incorrect maximum transmission unit (MTU) setting causes these messages.
Error Message DOT1Q_TUNNELLING-4-MTU_WARNING: System MTU of [dec] might be insufficient for 802.1Q tunnelling. 802.1Q tunnelling requires system MTU size of [dec] to handle maximum size ethernet frames.
Note
Explanation The switch MTU setting might not be sufficient for IEEE 802.1Q tunneling. The MTU needs to include the 4-byte overhead associated with the additional IEEE 802.1Q tag. The first [dec] is the current system MTU setting in bytes, and the second [dec] is the required MTU size in bytes.
Recommended Action Adjust the system MTU for the additional IEEE 802.1Q tag by using the system mtu global configuration command, and reload the switch by using the reload privileged EXEC command.
DOT1X Messages
This section contains the IEEE 802.1x messages.
Error Message DOT1X-4-MEM_UNAVAIL: Memory was not available to perform the 802.1X action.
Note
Explanation The system memory is not sufficient to perform the IEEE 802.1x authentication.
Recommended Action Reduce other system activity to reduce memory demands.
Error Message DOT1X-4-PROC_START_ERR: Dot1x unable to start.
Note
Explanation The system failed to start the IEEE 802.1x process.
Recommended Action Restart the IEEE 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.
Note
Explanation The IEEE 802.1x process cannot operate because of an internal system error.
Recommended Action Reload the device.
Error Message DOT1X-5-INVALID_INPUT: Dot1x Interface parameter is Invalid on interface [chars].Explanation The IEEE 802.1x interface parameter is out of the specified range or is invalid. [chars] is the interface.
Recommended Action Refer to the CLI help documentation to determine the valid IEEE 802.1x parameters.
Error Message DOT1X-5-SECURITY_VIOLATION: Security violation on interface [chars], New MAC address [enet] is seen.
Note
Explanation A host on the specified interface is trying to access the network or to authenticate in a host mode that does not support the number of hosts attached to the interface. This is a security violation, and the port is put in the error-disabled state.
Recommended Action Ensure that the interface is configured to support the number of attached hosts. Enter the shutdown interface configuration command and then the no shutdown interface configuration command to restart the port.
DOT1X_SWITCH Messages
This section contains the IEEE 802.1x messages for switches.
Error Message DOT1X_SWITCH-5-ERR_INVALID_PRIMARY_VLAN: Attempt to assign primary VLAN [dec] to 802.1x port [chars]
Note
Explanation An attempt was made to assign a primary VLAN to an IEEE 802.1x port, which is not allowed. [dec] is the VLAN, and [chars] is the port.
Recommended Action Update the configuration to use a different VLAN.
Error Message DOT1X_SWITCH-5-ERR_INVALID_SEC_VLAN: Attempt to assign invalid secondary VLAN [dec] to PVLAN host 802.1x port [chars]
Note
Explanation An attempt was made to assign a nonsecondary VLAN to a private VLAN host IEEE 802.1x port. [dec] is the VLAN, and [chars] is the port.
Recommended Action Change the mode of the port so that it is no longer a private VLAN host port, or use a valid secondary VLAN.
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]
Note
Explanation An attempt was made to assign a private VLAN whose primary VLAN does not exist or is shut down. [dec] is the VLAN, and [chars] is the port.
Recommended Action Make sure the primary VLAN exists and is not shut down. Verify that the private VLAN is associated with a primary VLAN.
Error Message DOT1X_SWITCH-5-ERR_RADIUS_VLAN_NOT_FOUND: Attempt to assign non-existent VLAN [chars] to dot1x port [chars]
Note
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 Make sure a VLAN with the specified name/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]
Note
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, and [chars] is the port.
Recommended Action Change the mode of the port 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
Note
Explanation An attempt was made to assign a VLAN to an IEEE 802.1x port that is configured as a SPAN destination port. [dec] is the VLAN, and [chars] is the port.
Recommended Action Change the SPAN configuration so that the port is no longer 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 [chars]
Note
Explanation Multi-Domain Authentication host mode cannot start if the configured data VLAN on a port is the same as the voice VLAN. [chars] is the port.
Recommended Action Change either the voice VLAN or the access VLAN on the interface so that they are not equal. This causes Multi-Domain authentication to start.
Error Message DOT1X_SWITCH-5-ERR_VLAN_EQ_VVLAN: Data VLAN [dec] on port [chars] cannot be equivalent to the Voice VLAN.
Note
Explanation An attempt was made to assign a data VLAN to an IEEE 802.1x port that is the same as the voice VLAN. [dec] is the VLAN, and [chars] is the port.
Recommended Action Change either the voice VLAN or the access/IEEE 802.1x-assigned VLAN on the interface so that they are not equal. This causes the authentication to proceed normally on the next retry.
Error Message DOT1X_SWITCH-5-ERR_VLAN_INTERNAL: Attempt to assign internal VLAN [dec] to 802.1x port [chars]
Note
Explanation An attempt was made to assign an invalid VLAN to an IEEE 802.1x port. The VLAN specified is used internally and cannot be assigned to this port. [dec] is the VLAN, and [chars] is the port.
Recommended Action Update the configuration to not use this VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_INVALID: Attempt to assign invalid VLAN [dec] to 802.1x port [chars]
Note
Explanation An attempt was made to assign an invalid VLAN to an IEEE 802.1x port. The VLAN specified is out of range and cannot be assigned to this port.[dec] is the VLAN, and [chars] is the port.
Recommended Action Update the configuration to use a valid VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND: Attempt to assign non-existent or shutdown VLAN [dec] to 802.1x port [chars]
Note
Explanation An attempt was made to assign a VLAN to an IEEE 802.1x port, but the VLAN was not found in the VTP database. [dec] is the VLAN, and [chars] is the port.
Recommended Action Make sure that the VLAN exists and is not shut down, or use another VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_ON_ROUTED_PORT: Dot1x cannot assign a VLAN [dec] to a routed port [chars]
Note
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 and [chars] is the port.
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]
Note
Explanation An attempt was made to assign a VLAN to a promiscuous IEEE 802.1x port, which is not allowed. [dec] is the VLAN, and [chars] is the port.
Recommended Action Change the mode of the port so that it is no longer 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]
Note
Explanation An attempt was made to assign an invalid VLAN to an IEEE 802.1x port. The VLAN specified is a reserved VLAN and cannot be assigned to this port. [dec] is the VLAN, and [chars] is the port.
Recommended Action Update the configuration to not use this VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_ROUTED_PORT: Attempt to assign VLAN [dec] to routed 802.1x port [chars]
Note
Explanation An attempt was made to assign a VLAN to a routed IEEE 802.1x port, which is not allowed. [dec] is the VLAN, and [chars] is the port.
Recommended Action Change the mode of the port so that it is no longer a routed port, or change the configuration so that no VLAN is assigned.
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
Note
Explanation An attempt was made to assign a remote SPAN VLAN to an IEEE 802.1x port. Remote SPAN should not be enabled on a VLAN in which ports are configured with IEEE 802.1x enabled. [dec] is the VLAN, and [chars] is the port.
Recommended Action Either disable remote SPAN configuration on the VLAN, or disable IEEE 802.1x on all the ports in this VLAN.
DTP Messages
This section contains the Dynamic Trunking Protocol (DTP) messages.
Error Message DTP-4-MEM_UNAVAIL: Memory was not available to perform the trunk negotiation action.
Note
Explanation The system is unable to negotiate trunks because of a 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].
Note
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.
Note
Explanation The system is unable to negotiate trunks because an internal operation generated an unexpected error.
Recommended Action
