|
|
This chapter lists the switch system messages 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 date/time stamp designation; the date/time stamp designation is displayed only if the software is configured for system log messaging. |
This section contains the access control list (ACL) merge messages.
ACLMERGE-3-CUDDERROR: A CUDD Library error was detected in [chars]
Explanation This message indicates that the CUDD Library detected an error, and that the ACL-merge for this invocation has failed and could result in more traffic being switched by the software. The interface where the merge failed may experience lower performance; [chars] represents a function.
Action Copy the error message exactly as it appears on the console or in the system log, and call your technical support representative.
ACLMERGE-3-CUDDWARN: A CUDD Library warning message for interest in this even in [chars]
Explanation This represents a debug message; [chars] represents a function.
Action Copy the error message exactly as it appears on the console or in the system log, and call your technical support representative.
This section contains the Dynamic Trunk Protocol (DTP) messages.
DTP-4-MEM_UNAVAIL: Memory not available to perform the trunk negotiation action
Explanation This message indicates that the system is unable to negotiate trunks because of a lack of memory.
Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
DTP-4-UNKN_ERR: An unknown operational error occurred
Explanation This message indicates that the system is unable to negotiate trunks because an internal operation generated an unexpected error.
Action Reload the device.
DTP-1-ILGLCFG: Illegal config (on, isl--on,dot1q) on Port [module]/[number]
Explanation This message indicates that one end of the trunk is configured as ON, ISL and the other end is configured ON, 802.1Q.
Action This is an illegal configuration and you must change the encapsulation type so that both ends of the trunk match.
DTP-5-TRUNKPORTON: Port [dec]/[chars] has become trunk
Explanation This message indicates that the interface [dec] / [chars] is trunked; [dec]/[chars] is the module number/interface range.
Action This message is provided for information only.
DTP-5-NONTRUNKPORTON: Port [dec]/[chars] has become non-trunk
Explanation This message indicates the interface [dec]/[chars] is nontrunked; [dec]/[chars] is the module number/interface range.
Action This message is provided for information only.
DTP-5-TRUNKPORTCHG: Port [dec]/[chars] has changed from [chars] trunk to [chars] trunk
Explanation This message indicates that the encapsulation type of the trunk has changed; [dec] is the module number, the first [chars] is the interface number, the second [chars] is the original encapsulation type, and the third [chars] is the new encapsulation type.
Action This message is provided for information only.
This section contains the Enhanced High System Availability (EHSA) messages.
EHSA-3-IPC: [chars]
Explanation This message indicates that an Interprocess Communication (IPC) error occurred. The nature of the error will be displayed; [chars] is a text explanation.
Action Copy the error message exactly as it appears and the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
EHSA-3-FSM: [char]
Explanation This message indicates that an EHSA Finite State Machine (FSM) error occurred. The nature of the error will be displayed; [chars] is a text explanation.
Action Copy the error message exactly as it appears and the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
EHSA-3-CONFIG_SYS: [char]
Explanation This message indicates that an EHSA configuration sync error occurred. The nature of the error will be displayed; [chars] is a text explanation.
Action Copy the error message exactly as it appears and the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
EHSA-3-GENERAL: [char]
Explanation This message indicates that an EHSA error occurred. The nature of the error will be displayed; [chars] is a text explanation.
Action Copy the error message exactly as it appears and the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
This section contains the environmental messages.
C6KENV-4-FANTRAYFAILED: fan tray failed
Explanation This message indicates that one or more fans in the system fan tray have failed. Although this is a minor alarm, system components could overheat and be shut down.
Action Replace the system tray.
C6KENV-4-FANTRAYOK: fan tray OK
Explanation This message indicates that all fans in the fan tray are operating.
Action No action is required.
C6KENV-4-PSFANFAIL: the fan in power supply [dec] has failed
Explanation This message indicates that the fan in power supply [dec] has failed; [dec] is the number of the power supply 1 or 2. The power supply could overheat and shut down.
Action Replace the power supply.
C6KENV-4-PSFANOK: the fan in power supply [dec] is OK
Explanation This message indicates that the fan in the power supply [dec] is operating; [dec] is the number of the power supply 1 or 2.
Action No action is required.
C6KENV-2-MAJORTEMPALARM: [chars] has exceeded allowed operating temperature range
Explanation This message indicates that the component will power off. For shared components, this requires powering off the system; [chars] is the system component and slot.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
C6KENV-4-MAJORTEMPALARMRECOVER: [chars] has returned to allowed operating temperature range
Explanation This message indicates that the component has returned to the allowed temperature range, so the scheduled shutdown is canceled and the system will continue operating; [chars] is the system component and slot.
Action No action is required.
C6KENV-4-MINORTEMPALARM: [chars] has exceeded normal operating temperature range
Explanation This message may indicate a trend for the component and for other components in the system; [chars] is the system component and slot.
Action Inspect the indicated component closely to determine why it is operating out of normal operating temperature range and whether it will eventually exceed the allowed operating temperature range.
C6KENV-4-MINORTEMPALARMRECOVER: [chars] has returned to normal operating temperature range
Explanation This message indicates that the operating temperature range is normal; [chars] is the system component and slot.
Action No action is required.
C6KENV-4-VTTFAILED: VTT [dec] failed
Explanation This message indicates that the indicated voltage termination (VTT) module failed; [dec] is the VTT number 1, 2, or 3.
Action Replace the indicated VTT and/or the chassis as soon as possible.
C6KENV-4-VTTOK: VTT [dec] operational
Explanation This message indicates that the indicated VTT is operational; [dec] is the VTT number 1, 2, or 3.
Action No action is required.
C6KENV-0-VTTMAJFAILED: Too many VTT failures to continue system operation
Explanation This message indicates that the Catalyst 6000 family switch backplane data bus cannot operate without proper termination provided by the VTTs; [dec] is the VTT number 1, 2, or 3.
Action Replace the failed VTTs.
C6KENV-2-VTTMAJRECOVERED: enough VTTs operational to continue system operation
Explanation This message indicates that the failed VTTs began operating again.
Action 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.
C6KENV-4-CLOCKFAILED: clock [dec] failed
Explanation This message indicates that the indicated clock failed. The system will continue to operate using the redundant clock; [dec] is the clock number 1 or 2.
Action Replace the failed clock.
C6KENV-CLOCKOK: clock [dec] operational
Explanation This message indicates that a previously failed clock has declared itself operational; [dec] is the clock number 1 or 2.
Action No action is required.
C6KENV-0-CLOCKMAJFAILED: too many clocks failed to continue system operation
Explanation This message indicates that no clocks are operational. At least one clock must be operational so packets can be forwarded.
Action Replace the clocks, backplane, or chassis.
C6KENV-2-CLOCKMAJRECOVERED: enough clocks operational to continue system operation
Explanation This message indicates that the system can continue operating using the recovered clocks.
Action No action is required.
C6KENV-2-SHUTDOWN-SCHEDULED: shutdown for [chars] scheduled in [dec] seconds
Explanation This message indicates that a major alarm condition will be corrected by shutting down the affected component; [chars] is the component, and [dec] is the amount of time in seconds before shutdown.
Action Replace the component as soon as possible.
C6KENV-2-SHUTDOWN-CANCELLED: shutdown for [chars] cancelled
Explanation This message indicates that the situation that caused the shutdown to be scheduled was corrected and the shutdown was canceled; [chars] is the component.
Action No action is required.
C6KENV-2-SHUTDOWN: shutdown [chars] is now because of [chars]
Explanation This message indicates that the indicated component is being shut down.
Action Replace the component as soon as possible; the first [chars] is the component, and the second [chars] is the reason for shutdown.
C6KENV-1-SHUTDOWN-DISABLED: need to shutdown [chars] now but shutdown action is disabled!
Explanation This message indicates that the user disabled the shutdown action so the system could not shut down the indicated component; [chars] is the component.
Action Manually shut down or remove the indicated component immediately.
This section contains the EtherChannel (EC) messages.
EC-4-NOMEM: Not enough memory available for [chars]
Explanation This message indicates that the PAgP Shim/EC could not obtain the memory it needed; [chars] is the EtherChannel.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
EC-6-NOPAGP: Invalid EC mode, PAgP not enabled
Explanation This message indicates that PAgP is not included in the image and the EC mode cannot be set to desirable/auto.
Action Get an image with PAgP included or set mode to ON.
EC-6-L3PORTDOWN: Shutting down [chars] as its port-channel is admin-down
Explanation This message indicates that the Layer 3 interface administrative state is ruled by the administrative state of its EtherChannel. If the EtherChannel administrative state is down, the Layer 3 interface administrative state is forced down; [chars] is the Layer 3 interface.
EC-6-NOTINSYNC: [chars] suspended: Not in sync with other interfaces in the group
Explanation This message indicates that all Layer 2 interfaces in a group in the ON mode should be compatible, noncompatible Layer 2 interfaces will be suspended, all Layer 3 interfaces in the group should be compatible, and noncompatible Layer 3 interfaces will be suspended; [chars] is the Layer 3 interface.
Action Make the interface attributes compatible; either shut or no shut.
EC-6-L3DONTBNDL1: [chars] suspended: PAgP enabled locally, not enabled on the remote interface
Explanation This message indicates that PAgP is enabled on a Layer 3 interface, but the partner does not have PAgP enabled. In this mode, the interface is put in a suspended state; [chars] is the Layer 3 interface.
Action Enable PAgP on the remote side.
EC-6-L3DONTBNDL2: [chars] suspended: GC of partner port is different than some of the other ports
Explanation This message indicates that an interface cannot join a bundle unless the local group capability and the partner group capability are the same as that of the interfaces in the bundle. In this case, the partner interface global configuration is different than some of the other interfaces in the bundle; [chars] is the Layer 3 interface.
Action Make sure the partner group capability for all the interfaces in the group are the same.
EC-6-L3STAYDOWN: [chars] will remain down as its port-channel [chars] is admin-down
Explanation This message indicates that on Layer 3 interfaces and aggregation interfaces, the administrative state of the aggregation interface overrides the administrative state of the Layer 3 interface. If the aggregation interface is administratively down, all interfaces in the aggregation interface are down; [chars] is the Layer 3 interface.
Action Issue a no shutdown command on the aggregation interface.
EC-6-CANNOT_UNSUITABLE: [chars] will not join any port-channel. Unsuitable attribute configured
Explanation This message indicates that one of the interfaces cannot join the EtherChannel because it is configured for PortFast, VMPS, or Dest_SPAN. All of these are unsuitable configurations for EtherChannels; [chars] represents the interface name.
Action Remove the unsuitable configuration.
EC-6-CANNOT_BUNDLE1: Port-channel [chars]is admin-down, port [chars] will remain stand-alone.
Explanation This message indicates that the EtherChannel is administratively down. Unshut the EtherChannel to form a bundle; the first [chars] indicates the EtherChannel, and the second [chars] is the Layer 3 interface.
Action Unshut the EtherChannel.
EC-6-CANNOT_BUNDLE2: Port-channel [chars] is not compatible with port [chars], port will remain stand-alone.
Explanation This message indicates that the interface has different interface attributes than that of the EtherChannel. So the interface can join the bundle, change the interface attributes to match the EtherChannel attributes; the first [chars] indicates the EtherChannel, and the second [chars] is the Layer 3 interface.
Action Change the interface attributes to match the EtherChannel attributes.
EC-6-BUNDLE: Interface [chars] joined port-channel [dec]
Explanation This message indicates that the indicated interface joined the specified EtherChannel; [chars] is the Layer 3 interface, and [dec] is the EtherChannel.
Action No action is required.
EC-6-UNBUNDLE: Interface [chars] left the port-channel [dec]
Explanation This message indicates that the indicated interface left the specified EtherChannel; [chars] is the Layer 3 interface, and [dec] is the EtherChannel.
Action No action is required.
This section contains the feature manager (FM) messages.
FM-4-RACL-REDUCED: Interface [chars] routed traffic will be software switched in [chars] direction(s)
Explanation This message indicates that the configured ACLs are too large to fit all in the hardware TCAM. TCAM resource contention prevents ACLs from being applied in the TCAM for this interface. Traffic on this interface is sent to software so that the ACLs can be applied; the first [chars] represents the interface, and the second [chars] represents the direction.
Action Enter the mls tcam priority command to prioritize interfaces for hardware switching. Try and share the same ACLs across multiple interfaces in order to reduce TCAM resource contention.
FM-2-VACL-FAILURE: Interface [chars] traffic will not comply with VACLs in [chars] direction(s)
Explanation This message indicates that the configured ACLs are too large to fit in the hardware TCAM. VLAN access control lists (VACLs) will not be applied on traffic for this interface due to TCAM resource contention; the first [chars] represents the interface, and the second [chars] represents the direction.
Action Enter the mls tcam priority command to prioritize interfaces for switching. Try and share the same ACLs across multiple interfaces in order to reduce TCAM resource contention.
FM-2-ACL-FAILURE: Interface [chars] traffic will not comply with ACLs in [chars] direction(s)
Explanation This message indicates that the configured ACLs are too large to all fit in the hardware TCAM. ACLs will not be applied on traffic for this interface due to TCAM resource contention; the first [chars] represents the interface, and the second [chars] represents the direction.
Action Enter the mls tcam priority command to prioritize interfaces for switching. Try and share the same ACLs across multiple interfaces in order to reduce TCAM resource contention.
FM-4-ACL-CONFLICT: Interface [chars] configured ACLs conflict in [chars] direction(s)
Explanation This message indicates that the configured routed ACLs for this interface conflict with the VACLs on this interface. The traffic on this interface may not comply with either the routed ACLs or VACLs under this condition; the first [chars] represents the interface, and the second [chars] represents the direction.
Action Redefine either the VACLs or the routed ACLs, or remove one or the other to avoid the conflict.
FM-4-TCAM-ENTRY: Hardware TCAM entry capacity exceeded
Explanation This message indicates that the configured ACLs are too large to all fit in the hardware TCAM. The hardware TCAM does not have the capacity to handle all of the configured ACLs.
Action Enter the mls tcam priority command to prioritize interfaces for switching. Try and share the same ACLs across multiple interfaces in order to reduce TCAM resource contention.
FM-4-TCAM-LABEL: Hardware TCAM label capacity exceeded
Explanation This message indicates that the hardware TCAM can only handle 500 interfaces configured with ACLs. The hardware TCAM does not have the capacity to handle the number of interfaces configured with ACLs.
Action Enter the mls tcam priority command to prioritize interfaces for hardware switching. Remove ACLs from some of the interfaces.
FM-4-TCAM-LOU: Hardware TCAM LOU capacity exceeded
Explanation This message indicates that the hardware TCAM can only handle up to nine logical operations per interface and up to 64 logical operations in total. The hardware TCAM does not have the capacity to handle the number of logical operations used with the configured ACLs.
Action Reduce the use of logical operations in the ACLs.
FM-4-TCAM-CAPMAP: Interface [chars] hardware TCAM LOU usage capability exceeded
Explanation This message indicates that the hardware TCAM can only handle up to nine logical operations per interface and up to 64 logical operations in total. The hardware TCAM does not have the capacity to handle the number of logical operations used with the configured ACLs on this specific interface; [chars] represents the interface.
Action Reduce the use of logical operations in the ACLs.
FM-2-TCAM-BAD-LOU: Bad TCAM LOU operation in ACL
Explanation This message indicates that a software error caused a failure when programming ACLs into the TCAM.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
FM-2-TCAM-MEMORY: NMP processor memory low
Explanation This message indicates that inadequate memory caused a failure when programming ACLs into the TCAM.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
FM-2-TCAM-ERROR: TCAM programming error [dec]
Explanation This message indicates that a software error caused a failure when programming ACLs into the TCAM; [dec] represents the error code.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
FM-2-BAD-TLV: Error in internal messaging - bad tlv [dec]
Explanation This message indicates that a software error may have affected programming of ACLs into the TCAM; [dec] represents the invalid TLV.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
FM-2-BAD-MESSAGE: Error in internal message - bad result [dec]
Explanation This message indicates that a software error may have affected programming of ACLs into the TCAM; [dec] represents the invalid result.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
FM-2-SEQUENCE: Error in internal messaging - lost message (i/f [chars], dir [chars], type [dec])
Explanation This message indicates that a software error may have affected the programming of ACLs into the TCAM; the first [chars] represents the interface name, the second [chars] represents the ingress or egress direction, and the [dec] represents the request type.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
This section contains the heartbeat messages.
HEARTBEAT-6-NOT_HEARD: Heartbeat messages have not been heard for [dec] seconds
Explanation This messages indicates that heartbeats have not been heard for a significant amount of time. A timeout will likely occur, which will reset the system; [dec] represents the number of seconds.
Action No action is required.
Heartbeat-3-TIMED_OUT: Heartbeat messages have failed, resetting system
Explanation This message indicates that heartbeats have failed and the system is no longer operational.
Action No action is required.
This section contains the Layer 2 multicast log messages.
MCAST-6-IGMP-CGMP: IGMP snooping now is running in IGMP CGMP mode on VLAN [dec]
Explanation This message indicates that Internet Group Management Protocol (IGMP) snooping detected a switch or a router that uses the Cisco Group Management Protocol (CGMP) and that IGMP now runs in CGMP mode on the VLAN affected; [dec] is the VLAN number.
Action No action is required.
MCAST-6-IGMP-ONLY-MODE: IGMP snooping is now running in IGMP only mode on vlan [dec]
Explanation This message indicates that IGMP snooping is now running on a network where there are no devices that use CGMP; [dec] is the VLAN number.
Action No action is required.
This section contains the Layer 3 manager system log messages.
L3-MGR-3-REQ-SEND: L3 MGR SEND error: [chars]
Explanation This message indicates that the Layer 3 manager has problems sending out the request; [chars] is the error description.
Action If the message recurs, copy the 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.
L3-MGR-3-RSP-RCVD: L3 MGR RCVD error: [chars]
Explanation This message indicates that the Layer 3 manager has received an error packet; [chars] is the error description.
Action If the message recurs, copy the 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.
L3-MGR-3-FLUSH: L3 MGR flush error: [chars]
Explanation This message indicates that the Layer 3 manager has encountered a flush error; [chars] is the error description.
Action If the message recurs, copy the 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.
L3-MGR-3-NULL-VLAN: L3 MGR vlan allocation error: [chars]
Explanation This message indicates that the Layer 3 manager cannot allocate VLAN; [chars] is the error description.
Action If the message recurs, copy the 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.
L3-MGR-3-NULL-SVI: L3 MGR svi allocation error: [chars]
Explanation This message indicates that the Layer 3 Manager cannot allocate switch virtual interface (SVI); [chars] is the error description.
Action If the message recurs, copy the 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.
L3-MGR-3-ICC-ASYNC: L3 MGR async request failed: [chars]
Explanation This message indicates that the Layer 3 manager received a NULL pak; [chars] is the error description.
Action If the message recurs, copy the 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.
L3-MGR-3-SW-SHORTCUT: L3 MGR install sw shortcut: [chars]
Explanation This message indicates that the Layer 3 manager is receiving bad status information; [chars] is the error description.
Action If the message recurs, copy the 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.
L3-MGR-3-L2_FLUSH-ENTRY: L3 MGR install L2 flush entry: [chars]
Explanation This message indicates that the Layer 3 manager is receiving bad status information; [chars] is the error description.
Action If the message recurs, copy the 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.
This section contains the online insertion and removal (OIR) messages.
OIR-6-REMCARD: Card removed from slot [dec], interfaces disabled
Explanation This message indicates that the OIR facility detected the removal of a processor from slot [n]. The interfaces on that processor are administratively shut down and marked as removed, and the routing table is flushed of any routes through the removed interfaces; [dec] is the slot number.
Action No action is required.
OIR-6-INSCARD: Card inserted in slot [dec], interfaces administratively shut down
Explanation This message indicates that the OIR facility detected a newly inserted processor. The inserted interface is shut down until you configure it, or if an interface of that type was previously configured, it is restored to its previous state; [dec] is the slot number.
Action No action is required.
OIR-3-UNKNOWN: Unknown card in slot [dec], card is being disabled
Explanation This message indicates that the OIR facility detected a line card but could not determine the type; [dec] is the slot number.
Action Reset the card in the indicated slot.
OIR-3-NOTSUPPORTED: [char] card in slot [dec] is not supported and is being disabled
Explanation This message indicates that the OIR facility has detected a line card that is not supported; [chars] indicates the line card, and [dec] is the slot number.
Action Remove the card from the indicated slot.
OIR-6-CONSOLE: Changing console ownership to [char] processor\n\n\n
Explanation This message indicates that the OIR facility has switched the console to the specified processor; [char] indicates the route or switch processor.
Action No action is required.
This section contains the port manager messages.
PM-2-NOMEM: Not enough memory available for [char]
Explanation This message indicates that the port manager subsystem could not obtain the memory it needed for the specified operation; [char] is the port manager operation.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
PM-4-BAD_COOKIE: [char] was detected
Explanation This message indicates that the port manager detected an invalid request; [char] indicates the invalid request.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
PM-4-BAD_CARD_COOKIE: an invalid card cookie was detected
Explanation This message indicates that the port manager detected an invalid request.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
PM-4-BAD_PORT_COOKIE: an invalid port cookie was detected
Explanation This message indicates that the port manager detected an invalid request.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
PM-4-BAD_VLAN_COOKIE: an invalid vlan cookie was detected
Explanation This message indicates that the port manager detected an invalid request.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
PM-4-BAD_CARD_SLOT: an invalid card slot [dec] was detected
Explanation This message indicates that the port manager detected an invalid request; [dec] indicates the slot number.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
PM-4-BAD_PORT_NUMBER: an invalid port number [dec] was detected
Explanation This message indicates that the port manager detected an invalid request; [dec] indicates the interface number.
Action Contact your technical support representative.
PM-4-BAD_VLAN_ID: an invalid vlan id [dec] was detected
Explanation This message indicates that the port manager detected an invalid request; [dec] is the VLAN ID.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
PM-4-BAD_APP_ID: an invalid application id [dec] was detected
Explanation This message indicates that the port manager detected an invalid request; [dec] is the application ID.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
PM-4-BAD_APP_REQ: an invalid [char] request by the `[char]' application was detected
Explanation This message indicates that the port manager detected an invalid request; the first [char] indicates the invalid request, and the second [char] indicates the application making the request.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
PM-4-TOO_MANY_APP: application `[char]' exceeded registration limit
Explanation This message indicates that the port manager detected an invalid request; [char] indicates the application.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
This section contains the power messages.
C6KPWR-4-ENABLED: Power to module in slot [dec] set on
Explanation This message indicates that the module in the indicated slot was powered up; [dec] is the slot number.
Action No action is required.
C6KPWR-4-DISABLED: Power to module in slot [dec] set [chars]
Explanation This message indicates that the module in the indicated slot was powered off for the indicated reason; [dec] is the slot number, and [chars] indicates the power status.
Action Your recovery procedure depends on the reason indicated in the message.
C6KPWR-4-PSINSERTED: Power supply inserted in slot [dec]
Explanation This message indicates that a power supply was inserted in the indicated slot; [dec] is the slot number.
Action No action is required.
C6KPWR-4-PSREMOVED: Power supply removed from slot [dec]
Explanation This message indicates that a power supply was removed from the indicated slot; [dec] is the slot number.
Action No action is required.
C6KPWR-4-PSOK: Power supply [dec] turned on
Explanation This message indicates that the indicated power supply is turned on; [dec] is the power supply 1 or 2.
Action No action is required.
C6KPWR-4-PSFAIL: Power supply [dec] output failed
Explanation This message indicates that the indicated power supply failed; [dec] is the power supply 1 or 2.
Action Replace the power supply.
C6KPWR-4-PSREDUNDANTMODE: Power supplies set to redundant mode
Explanation This message indicates that the power supplies are set to redundant mode.
Action No action is required.
C6KPWR-4-PSCOMBINEMODE: Power supplies set to combined mode
Explanation This message indicates that the power supplies are set to combined mode.
Action No action is required.
C6KPWR-4-PSREDUNDANTMISMATCH: Power supplies rated outputs do not match
Explanation This message indicates that the rated outputs of the power supplies do not match.
Action Make sure that the rated outputs for the power supplies match.
C6KPWR-4-PSREDUNDANTONESUPPLY: In power redundancy mode, system is operating on one power supply
Explanation This message indicates that when in power redundancy mode, the system operates on one power supply only.
Action No action is required.
C6KPWR-4-PSREDUNDANTBOTHSUPPLY: In power redundancy mode, system is operating on both power supplies
Explanation This message indicates that when in power redundancy mode, the system operates on both power supplies.
Action No action is required.
C6KPWR-4-UNDERPOWERED: Insufficient power to operate all FRUs in system
Explanation This message indicates that there is insufficient power to operate all modules in the system.
Action Reconfigure the system or upgrade the power supplies.
C6KPWR-4-COULDNOTREPOWER: Wanted to re-power FRU (slot [dec]) but could not
Explanation This message indicates that the system was unable to repower the field replaceable unit in the indicated slot; [dec] is the slot number.
Action This message might display for a number of reasons. A unit cannot repower if the power supply does not meet that unit's power requirement. If a module is unable to repower due to overheating, allow sufficient time for the unit to cool down before attempting to repower the unit. If both power supplies are operational but a unit is not being repowered, contact your technical support representative.
C6KPWR-4-UNSUPPORTED: Unsupported module in slot [dec], power not allowed
Explanation This message indicates that power was not allocated to a slot containing an unsupported module; [dec] is the slot number.
Action Remove the unsupported module.
This section contains the protocol filtering messages.
PF-4-MEM_UNAVAIL: Memory was not available to perform the protocol filtering action
Explanation This message indicates that protocol filtering is unable to operate because of a lack of memory.
Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
PF-4-UNKN_ERR: An unknown operational error occurred
Explanation This message indicates that protocol filtering is unable to operate because an internal operation generated an unexpected error.
Action Because of the unexpected nature of the problem, the only recommended action is to reload the device.
PF-4-PROC_START_ERR: Protocol filtering unable to start
Explanation This message indicates that the protocol filtering process was unable to be created for unknown reasons.
Action Start protocol filtering again in the event the condition was transient. If protocol filtering still fails, perform a system reset.
This section contains quality of service (QoS) management messages.
QM-3-ERROR: [chars] in [chars]: [dec]
Explanation This message can indicate a range of software errors.
Action Copy this message exactly as it appears on the console or in the system log, call your technical support representative, and provide the representative with the gathered information.
QM-3-ERROR-STAT: [chars] stat: [dec] in [chars]: [dec]
Explanation This message can indicate a range of software errors.
Action Copy this message exactly as it appears on the console or in the system log, call your technical support representative, and provide the representative with the gathered information.
This section contains the remote procedure call (RPC) messages.
RCP-2-NOMEM: No memory available for [char]
Explanation This message indicates that the RPC subsystem could not obtain the memory it needed; [char] is the operation for which memory was insufficient.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
RCP-2-FAILED: Failed to send RPC request [char]
Explanation This message indicates that a communication error occurred during an RCP request; [char] indicates the RCP request.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
RCP-2-APPNOTREG: Remote application `[char]' not registered
Explanation This message indicates that the remote application has not registered itself with the RPC subsystem; [char] is the application.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
RCP-4-BADID: Application ID [dec] is invalid
Explanation This message indicates that the application ID used by the RPC subsystem is invalid; [dec] is the application ID.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
RPC_4-TOOMANY: Too many RPC applications, `[char]' not registered
Explanation This message indicates that there are too many applications registered with the RPC subsystem; [char] indicates the applications that are not registered.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
RPC-4-DUPREG: Application `[char]' is already registered
Explanation This message indicates that the application has already registered itself with the RPC subsystem; [char] indicates the application.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
This section contains the MultiLayer Switching Feature Card (MSFC) messages.
C6SUP-3-NOVLANMAC: Can't allocate MAC address for VLAN interface
Explanation This message indicates that MAC address allocation failed because the VLAN number exceeds that provided for by the chassis.
Action Copy the error message exactly as it appears on the console or in the system log, call your technical support representative, and provide the representative with the gathered information.
C6MSFC-3-INOT0: IO card discover in non-zero slot [dec]
Explanation This message indicates that an IO card was detected in a non-zero slot; [dec] is the slot number.
Action Copy the error message exactly as it appears on the console or in the system log, call your technical support representative, and provide the representative with the gathered information.
C6MSFC-3-NOMAC: Can't allocate MAC address for interface [num] / [num]
Explanation This message indicates that the MAC address allocation failed because of an incorrect slot and interface combination, which exceeds the maximum available hardware; [num] / [num] indicate the module and interface numbers.
Action Copy the error message exactly as it appears on the console or in the system log, call your technical support representative, and provide the representative with the gathered information.
C6MSFC-4-COOKIE: Corrupt or missing MAC address cookie\n using random base [enet]
Explanation This message indicates that the contents of the MAC address EEPROM is invalid. The system is providing a random MAC address; [enet] is the MAC address.
Action Copy the error message exactly as it appears on the console or in the system log, call your technical support representative, and provide the representative with the gathered information.
C6MSFC-4-MACBLKSIZE: Unknown MAC address block size
Explanation This message indicates that the data stored in CPU IDPROM is bad or incomplete.
Action Contact your technical support representative to update your system.
C6MSCF-3-CHASSIS: Unknown chassis model
Explanation This message indicates that data stored in CPU IDPROM is bad or incomplete.
Action Contact your technical support representative to update your system.
C6MSFC-3-NOCPUVER: Invalid CPU Revision [dec]
Explanation This message indicates that the CPU ID could not be read from EEPROM. This is probably due to a hardware failure; [dec] represents the invalid CPU revision.
Action Copy the error message exactly as it appears on the console or in the system log, call your technical support representative, and provide the representative with the gathered information.
C6MSFC-3-BADCPUTYPE: Invalid CPU Type [dec]
Explanation This message indicates that the software does not recognize the MSFC on which it is operating. This problem might be caused by a misprogrammed or bad IDPROM.
Action Contact your technical support representative to update your system.
C6MSFC-3-CONFIG: Recommended port adapter configuration exceeded
Explanation This message indicates that the total bandwidth of fast and medium bandwidth port adapters exceed the rated capacity of this system.
Action Refer to the configuration guidelines for the maximum allowed high and medium bandwidth port adapters for the system.
C6MSFC-4-BADFLASH: Unsupported flash type in the bootflash - [chars]
Explanation This message indicates that the Flash SIMM is not supported by the platform.
Action Contact your technical support representative to update your system.
This section contains the spanning-tree messages.
SPANTREE-3-PORT-SELF-LOOPED: [chars] disabled - received BPDU src mac 9%e) same as that of interface
Explanation This message indicates that a bridge protocol data unit (BPDU) was received on the listed interface with a source MAC address that matches that assigned to the listed interface. This indicates the possibility that a port is looped back to itself, possibly due to a diagnostic cable being plugged in. The interface will be administratively shutdown.
Action Check the interface configuration and any cable plugged into the interface. Once the problem is resolved, reenable the interface by issuing a no shutdown command on the interface.
SPANTREE-7-RECV-1Q-NON-TRUNK: Received 802.1Q BPDU on non trunk [chars] [chars]
Explanation This message indicates that a Shared Spanning-Tree Protocol (SSTP) BPDU was received on the listed interface, which is not an operational trunking interface.
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 802.1Q). Once these parameters are consistent, spanning tree automatically unblocks the interface as appropriate.
SPANTREE-2-RECV-1Q-NON-1QTRUNK: Received 802.1Q BPDU on non 802.1Q trunk [chars] [chars]
Explanation This message indicates that the listed interface, on which an SSTP BPDU was received, was in trunk mode but was not using 802.1Q encapsulation.
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 802.1Q). Once these parameters are consistent, spanning tree automatically unblocks the interface as appropriate.
SPANTREE-2-RECV-PVID-ERR: Received BPDU with inconsistent peer vlan id [dec] on [chars] [chars]
Explanation This message indicates that the listed interface received an SSTP BPDU that is tagged with a VLAN ID that does not match the VLAN ID on which the BPDU was received. This occurs when the native VLAN is not consistently configured on both ends of an 802.1Q trunk.
Action Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree automatically unblocks the interfaces as appropriate.
SPANTREE-2-RECV-BAD-TLV: Received SSTP BPDU with bad TLV on [chars] [chars]
Explanation This message indicates that the listed interface received an SSTP BPDU that was missing the VLAN ID tag. The BPDU is discarded.
Action If the message recurs, copy the 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.
SPANTREE-7-BLOCK-PORT-TYPE: Blocking [chars] on [chars]. Inconsistent port type
Explanation This message indicates that the listed interface is being held in spanning-tree blocking state until the port type inconsistency is resolved.
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 802.1Q). Once these parameters are consistent, spanning tree automatically unblocks the interface as appropriate.
SPANTREE-2-BLOCK-PVD-PEER: Blocking on [chars] [chars]. Inconsistent peer vlan
Explanation This message indicates that the spanning-tree port associated with the listed spanning-tree instance and interface will be held in 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.
Action Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree automatically unblocks the interfaces as appropriate.
SPANTREE-2-BLOCK-PVID-LOCAL: Blocking [chars] on [chars] Inconsistent local vlan
Explanation This message indicates that the spanning-tree port associated with the listed spanning-tree instance and interface will be held in 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.
Action Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree automatically unblocks the interfaces as appropriate.
SPANTREE-2-UNBLOCK-CONSIST-PORT: Unblocking [chars] on [chars]. Port consistency restored
Explanation This message indicates that the port VLAN ID and/or port type inconsistencies have been resolved and spanning tree will unblock the listed interface of the listed spanning-tree instance as appropriate.
Action No action is required.
SPANTREE-2-RX-PORTFAST: Received BPDU on PortFast enabled port. Disabling [chars]
Explanation This message indicates that a BPDU was received on the listed interface, which has spanning tree PortFast enabled. Since spanning-tree BPDU guard is also enabled, the interface is administratively shut down.
Action Verify PortFast configuration on the interface. If PortFast behavior is desired, verify that the interface is connected to only a host or router and not to a bridge or a switch. After resolving the conflict, reenable the interface by issuing a no shutdown command on the interface.
This section contains the spanning-tree fast convergence extensions messages.
SPANTREE-FAST-7-PORT-FWD-UPLINK: Port [chars] [chars] moved to Forwarding (UplinkFast)
Explanation This message indicates that the indicated interface has been selected as the new root interface for the listed spanning-tree instance.
Action No action is required.
This section contains the switch processor messages.
C6SUP_SP-3-IONOT0: IO card discovered in non-zero slot [dec]
Explanation This message indicates that an IO card was detected in a non-zero slot; [dec] is the slot number.
Action Copy the error message exactly as it appears on the console or in the system log, call your technical support representative, and provide the representative with the gathered information.
C6SUP_SP-3-NOMAC: Can't allocate MAC address for interface [dec] / [dec]
Explanation This message indicates that the MAC address allocation failed because of an incorrect slot and interface combination that exceeds the maximum available hardware; [dec] / [dec] indicate the module and interface numbers.
Action Copy the error message exactly as it appears on the console or in the system log, call your technical support representative, and provide the representative with the gathered information.
C6SUP_SP-3-NOVLANMAC: Can't allocate MAC address for VLAN interface [dec]
Explanation This message indicates that the MAC address allocation failed because the VLAN number exceeds that provided for by the chassis; [dec] is the VLAN number.
Action Copy the error message exactly as it appears on the console or in the system log, call your technical support representative, and provide the representative with the gathered information.
C6SUP_SP-4-COOKIE: Corrupt or missing MAC address cookie\n using random base [enet]
Explanation This message indicates that the contents of the MAC address EEPROM is invalid. The system is providing a random MAC address; [enet] is the MAC address.
Action Copy the error message exactly as it appears on the console or in the system log, call your technical support representative, and provide the representative with the gathered information.
C6SUP_SP-4-PCIVALID: PCI activation failed, bay [dec], 0x%0x
Explanation This message indicates that the system received an invalid PCI signal from the port adapter. This is probably due to a hardware failure.
Action Contact your technical support representative.
C6SUP_SP-4-NOCPUVER: Invalid CPU ID, assuming revision 1
Explanation This message indicates that the CPU ID could not be read from EEPROM. This is probably due to a hardware failure.
Action Copy the error message exactly as it appears on the console or in the system log, call your technical support representative, and provide the representative with the gathered information.
C6SUP_SP-2-NOMEM: No memory available for [chars]
Explanation This message indicates that the system did not have enough memory available; [chars] is the operation for which there was insufficient memory.
Action Copy the error message exactly as it appears on the console or in the system log, call your technical support representative, and provide the representative with the gathered information.
C6SUP_SP-4-HEARTBEAT: Internal inconsistency detected, heartbeats disabled
Explanation This message indicates that the system detected an inconsistency while sending internal heartbeat packets on the switching bus.
Action Copy the error message exactly as it appears on the console or in the system log, call your technical support representative, and provide the representative with the gathered information.
C6SUP_SP-3-CONFIG: Recommended port adapter configuration exceeded
Explanation This message indicates that the total bandwidth of fast and medium bandwidth port adapters exceed the rated capacity of this system.
Action Refer to the configuration guidelines for the maximum allowed high and medium bandwidth port adapters for the system.
C6SUP_SP-3-UNSUPPORTED: [chars] in slot [dec] is not supported on the [chars] chassis
Explanation This message indicates that the software identified and disabled the Forwarding Engine on the I/O card.
Action No action is required.
This section contains the Switch-Module Configuration Protocol (SCP) messages.
SCP-2-TOO_MANY_SAP: Not enough space to register process [dec]([char]) for SCP
Explanation This message indicates that the SCP application cannot register for a service access point (SAP) because all possible numbers have been assigned.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
SCP-2-NOTREG: Process [dec]([char]) not registered for SCP
Explanation This message indicates that the SCP application cannot send an SCP message because the SCP application has not registered for the SAP.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
SCP-2-NOMEM: No memory available for [char]
Explanation This message indicates that the SCP subsystem could not obtain the memory it needed; [char] is the operation for which there was insufficient memory.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
SCP-4-GET_PAK_MSG: Failed for message size=[dec]
Explanation This message indicates that the system is out of pak-type buffers of the required size; [dec] is the required size.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
SCP-4-DACK_TIMEOUT_MSG: SCP delivery ack timeout for opcode=[hex]
Explanation This message indicates that the route processor did not receive SCP delivery acknowledgements from the switch processor after two retries.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
This section contains the Switched Port Analyzer (SPAN) messages.
SPAN-4-SRC_ALREADY_DST: Interfac(s) [chars] already configured as monitor destinations
Explanation This message indicates that at least one interface being configured as a monitor source is ignored because it is already configured as a monitor destination in this or another monitor session. All other monitor sources being configured are applied; [chars] indicates the interface name(s).
Action Choose a SPAN source interface that is not a SPAN destination in any SPAN session, or remove the SPAN destination configuration from the interface before configuring it as a SPAN source interface.
SPAN-4-DSD_ALREADY_DST: Interfaces [dec] are already configured as monitor destinations in other monitor sessions
Explanation This message indicates that at least one interface being configured as a monitor destination is ignored because it is already configured as a monitor destination in another monitor session. All other monitor destinations being configured are applied; [dec] represents the listed interfaces.
Action Choose a SPAN destination interface that is not a SPAN destination in any SPAN session, or remove the prior SPAN destination configuration from the interface before configuring it as a SPAN destination interface for the current session.
SPAN-4-DSD_ALREADY_SRC: Interfaces [dec] are already configured as monitor sources
Explanation This message indicates that at least one interface being configured as a monitor destination is ignored because it is already configured as a monitor source in this or in another monitor session. All other monitor destinations being configured are applied; [dec] represents the listed interfaces.
Action Choose a SPAN destination interface that is not a SPAN source in any SPAN session, or remove the prior SPAN source configuration before configuring it as a SPAN destination interface.
SPAN-3-UNKN_ERR: An internal error occurred during a SPAN operation
Explanation This message indicates that SPAN detected an error in its internal operation.
Action The error might be transient. Try the SPAN operation again. If a second attempt also fails, try reloading the switch to complete the operation.
SPAN-3-UNKN_ERR_PORT: An internal error occurred when configuring SPAN on port [dec] / [chars]
Explanation This message indicates that SPAN detected an error in its internal operation; [dec] represents the slot, and [chars] represents the interface number.
Action The error might be transient. Try the SPAN operation again. If a second attempt also fails, try reloading the switch to complete the operation.
SPAN-3-MEM_UNAVAIL: Memory was not available to perform the SPAN operation
Explanation This message indicates that the system was unable to perform a SPAN operation because of a lack of memory.
Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
SPAN-4-RXOVFL: This platform allows a maximum of [dec] RX monitor interface(s)
Explanation This message indicates that the number of interfaces being monitored in the receive direction exceeds the maximum number allowed on this platform. All interfaces beyond the number allowed are ignored and will not be configured; [dec] indicates the maximum interfaces allowed for monitoring in the receive direction.
SPAN-4-TXOVFL: This platform allows a maximum of [dec] TX monitor interface(s)
Explanation This message indicates that the number of interfaces being monitored in the transmit direction exceeds the maximum number allowed on this platform. All interfaces beyond the number allowed are ignored; [dec] indicates the maximum interfaces allowed for monitoring in the transmit direction.
Action Enter the show monitor command from privileged EXEC mode to determine which interfaces were actually configured. Make necessary configuration changes so that the configured interfaces do not exceed the allowed maximum.
SPAN-4-FTR_ALREADY_SRC: Configuring filter VLANs, but there are already source VLANs configured
Explanation This message indicates that filter VLANs are being configured, but source VLANs have already been configured in the same monitoring session. Filter VLANs and source VLANs are not allowed to be configured during the same monitoring session.
Action Configure only one type of VLAN during a monitoring session.
SPAN-4-SRC_ALREADY_FTR: Configuring source VLANs, but there are already filter VLANs configured
Explanation This message indicates that source VLANs are being configured, but filter VLANs have already been configured in the same monitoring session. Filter VLANs and source VLANs are not allowed to be configured during the same monitoring session.
Action Configure only one type of VLAN during a monitoring session.
This section contains the VLAN manager messages.
SW-VLAN-6-VTP_MODE_CHANGE: VLAN manager changing device mode from [chars] to [chars]
Explanation This message indicates that some switch devices must automatically change VTP device modes upon receipt of a VLAN configuration database containing more than a set number of VLANs, depending on the device. This message indicates that such a spontaneous conversion has occurred, what the previous mode was, and what the current mode is; [chars] indicates the VTP device mode.
Action No action is required.
SW-VLAN-4-VTP-INTERNAL-ERROR: VLAN manager received an internal error [dec] from vtp function [chars]: [chars]
Explanation This message indicates that an unexpected error code was received by the VLAN manager from the VTP configuration software; [dec] is the error code, the first [chars] indicates the VTP function, and the second [chars] represents an error code description.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
SW-VLAN-4-VTP-INVALID-DATABASE-DATA: VLAN manager received bad data of type [chars]: value [dec] from vtp database function [chars]
Explanation This message indicates that invalid data was received by the VLAN manager from the VTP configuration database routine; the first [chars] indicates the data type, [dec] is the inappropriate value that was received, and the second [chars] indicates the VTP database function.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
SW-VLAN-4-NO-PM-COOKIE-RETURNED: VLAN manager unexpectedly received a null [chars] type cookie from the Port Manager, data reference: [chars]
Explanation This message indicates that the VLAN manager queried the port manager for a reference cookie but received a NULL pointer instead; the first [chars] represents the type of port manager cookie, and the second [chars] represents the interface or VLAN that is the source of the problem.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
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 This messages indicates that the VLAN manager received an upcall from the port manager containing a VLAN cookie which translated to a bad VLAN number; [dec] is the VLAN ID.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
SW-VLAN-4-VTP-INVALID-EVENT-DATA: VLAN manager received bad data of type [chars] while being called to handle a [chars] event
Explanation This message indicates that the VLAN manager received invalid data from the VTP configuration software; the first [chars] indicates the data type, and the second [chars] indicates the type of event.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
SW-VLAN-3-VTP-PROTOCOL-ERROR: VTP protocol code internal error: [chars]
Explanation This message indicates that the VTP code encountered an error while processing a configuration request, packet, or time expiration; [chars] indicates the error.
Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
SW-VLAN-4-IFS-FAILURE: VLAN manager encountered file operation error: call = [chars] / code = [dec] ([chars]) / bytes transferred = [dec]
Explanation This message indicates that the VLAN manager received an unexpected error return from an IOS file system call; the first [chars] represents the IFS operation that failed, the first [dec] represents the error code, the second [chars] represents the textual interpretation of the error code, and the second [dec] represents the number of bytes transferred.
Action 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.
SW-VLAN-3VLAN-PM-NOTIFICATION-FAILURE: VLAN manager synchronization failure with Port Manager over [chars]
Explanation This message indicates that due to a lack of ready pool space, the VLAN manager dropped a notification from the port manager as indicated by the message; [chars] represents the type of PM notification.
Action 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.
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 This message indicates that the VLAN software detected an old version of the VLAN configuration file format. The software was able to interpret the file with no problems but will create files using the new format in the future; the first [dec] represents the old version number, and the second [dec] represents the new version number.
Action No action is required.
Posted: Tue Aug 8 15:43:05 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.