|
|
This chapter lists the Catalyst 5000 series switch system messages by facility. Within each facility, the messages are listed by severity levels 0 to 7, with 0 being the highest severity level, and 7, the lowest severity level. Each message is followed by an explanation and a recommended action.
This section contains the Catalyst 5000 series switch system messages, including system semaphore messages.
SYS-0: Temp Critical OkayExplanation This message indicates the internal temperature has dropped below 70° C (158° F); this message applies only to the redundant supervisor engine in the switch.
Recommended Action This message is provided for information only.
SYS-0: Temp Critical FailureExplanation This message indicates the internal temperature has risen above 70° C (158° F). If the temperature remains above 70° C (158° F), the system automatically powers down after 5 minutes; this message applies only to the redundant supervisor engine in the switch.
Recommended Action Power down the system and contact your technical support representative.
SYS-0: Temp Critical RecoveredExplanation This message indicates the internal temperature dropped below 70° C (158° F), and the automatic power down was canceled; this message applies only to the redundant supervisor engine in the switch.
Recommended Action This message is provided for information only.
SYS-0: Exceeded max limit of ATM/RSM card in the systemExplanation This message indicates that more than seven ATM or RSM modules have been installed in one chassis.
Recommended Action Remove the extra ATM or RSM modules.
SYS-1: Path Test Failure received from Module [dec]Explanation This message indicates the test of the local data path from module [dec] failed, where [dec] is the module number.
Recommended Action Enter the show log [mod_num] command to display path test failure information and then contact your technical support representative.
SYS-1: Module [dec] has invalid MAC address, [chars]Explanation This message indicates the supervisor engine module [dec] has an invalid Media Access Control (MAC) address, [chars], where [dec] is the module number and [chars] could be one of the following: remains offline or bypass enabled.
Recommended Action This message is provided for information only, but could indicate the MAC address of the supervisor engine module is the same as the default MAC address (00-40-4b-ff-00-00). Enter the show mac [mod_num/port_num] command to check the module's MAC address. If the listed MAC address is the default MAC address, contact your technical support representative.
SYS-1: Chassis has invalid MAC address, [chars]Explanation This message indicates the chassis has an invalid MAC address, where [chars] could be one of the following remains offline or bypass enabled.
Recommended Action This message is provided for information only, but could indicate the MAC address of the chassis is the same as the default MAC address (00-40-4b-ff-00-00). Enter the show module [mod_num/port_num] command to check the chassis's MAC address. If the listed MAC address is the default MAC address, contact your technical support representative.
SYS-1: Chassis Serial EEPROM data invalidExplanation This message indicates the chassis serial electrically erasable programmable read-only memory (EEPROM) data is invalid.
Recommended Action Contact your technical support representative.
SYS-1: Warning: bootflash size mismatch with file system.Explanation This message indicates that the bootflash has been checked and is less than 8 MB.
Recommended Action Upgrade the bootflash memory to 8 MB.
SYS-1: Bootflash (size): #[hex], size show in file system: #[hex]Explanation This message indicates that the bootflash has been checked and is less than 8 MB, where the first [hex] is the actual size of bootflash and the second [hex] is what the file system thinks it is.
Recommended Action Upgrade the bootflash memory to 8 MB.
SYS-1: REFORMAT Bootflash NEEDED!!!!Explanation This message indicates that the bootflash has been checked and is less than 8 MB.
Recommended Action Upgrade the bootflash memory to 8 MB.
SYS-1: Re-format bootflash.Explanation This message indicates that, during a format bootflash operation, the bootflash size was detected as less than 8 MB.
Recommended Action Upgrade the bootflash memory to 8 MB.
SYS-2: Power Supply [dec] OkayExplanation This message indicates the power supply has been turned on or has returned to a proper state, where [dec] is the power supply number.
Recommended Action This message is provided for information only.
SYS-2: Power Supply [dec] FailedExplanation This message indicates the power supply [dec] failed, where [dec] is the power supply number.
Recommended Action Replace the indicated power supply.
SYS-2: Power Supply [dec] Fan FailedExplanation This message indicates the power supply [dec] fan failed, where [dec] is the power supply number.
Recommended Action Replace the indicated power supply fan.
SYS-2: Power Supply [dec] and Fan FailedExplanation This message indicates the power supply [dec] and power supply fan failed, where [dec] is the power supply number.
Recommended Action Replace the indicated power supply and fan.
SYS-2: Fan OkayExplanation This message indicates the chassis fan tray was plugged back in or returned to a proper state.
Recommended Action This message is provided for information only.
SYS-2: Fan FailedExplanation This message indicates the chassis fan failed.
Recommended Action Replace the fan.
SYS-2: Temp high OkayExplanation This message indicates the internal temperature has dropped below 50° C (122° F).
Recommended Action This message is provided for information only.
SYS-2: Temp high FailureExplanation This message indicates the internal temperature has risen above 50° C (122° F).; this message applies only to the redundant supervisor engine in the switch.
Recommended Action This message is provided for information only. If the temperature exceeds 70° C (158° F), the Temp Critical Failure message appears and the system automatically powers down after five minutes.
SYS-3: WARNING: ACTIVE AND STANDBY SUPERVISORS ARE OF DIFFERENT CARD TYPESExplanation This message indicates that the redundant supervisor engine modules in a chassis do not have the same type of Enhanced Address Recognition Logic (EARL) or Supervisor II engine modules.
Recommended Action Make sure the redundant supervisor engine modules have the same type of EARL board, and the redundant Supervisor Engine II modules are the same type.
SYS-3: WARNING: DUPLICATE FLASH SYNCHRONIZATION WILL NOT HAPPENExplanation This message indicates that the redundant supervisor engine modules in the chassis do not have the same type of EARL or Supervisor Engine II modules.
Recommended Action Make sure the redundant supervisor engine modules have the same type of EARL board, and the redundant Supervisor Engine II modules are the same type.
SYS-3: WARNING: NVRAM SYNCHRONIZATION WILL NOT HAPPENExplanation This message indicates that redundant supervisor engine modules in the chassis do not have the same type of EARL or Supervisor Engine II modules.
Recommended Action Make sure the redundant supervisor engine modules have the same type of EARL board, and the redundant Supervisor Engine II modules are the same type.
SYS-3: WARNING: ACTIVE AND STANDBY SUPERVISORS ARE OF DIFFERENT EARL CARD TYPESExplanation This message occurs when the system is configured with two supervisors, one with an EARL1 or EARL1+ and the other supervisor with an EARL2 or greater. The redundancy feature (Flash and NVRAM sync) is disabled in this case.
Recommended Action Upgrade the EARL1 or EARL1+ to an EARL2.
SYS-3: Active supervisor card is running a different version of NMP image.Explanation This message indicates that the active supervisor module is running a different Network Management Processor (NMP) image version than the standby supervisor.
Recommended Action Check the versions of NMP software being run on the active and standby supervisor modules. This message is provided for information only.
SYS-3: Default Gateway switching from [chars]Explanation This message indicates that the default IP gateway has failed, where [chars] is the name of the IP gateway.
Recommended Action This message is provided for information only.
SYS-3: Default Gateway switching to [chars]Explanation This message indicates that the IP gateway, where [chars] is the name of the gateway, is the new default IP gateway.
Recommended Action This message is provided for information only.
SYS-3: Bad MII status: Port [dec]/[dec], [chars]Explanation This message indicates the bad status of a media-independent interface (MII) transceiver. The [dec] / [dec] indicates the [mod_num]/[port_num]; [chars] indicates if diagnostics have failed or communication has failed.
Recommended Action Install a new MII transceiver; if this message reappears, contact your technical support representative.
SYS-3: Module [dec] is in offline diag modeExplanation This message indicates module [dec] is in offline diagnostics mode, where [dec] is the module number.
Recommended Action This message is provided for information only, but could indicate a problem exists with the diagnostic testing. If this is the case, contact your technical support representative.
SYS-3: Module [dec] waiting for downloadExplanation This message indicates the module [dec] is waiting for download, where [dec] is the module number.
Recommended Action This message is provided for information only, but could indicate a problem exists with the download task. If this is the case, contact your technical support representative.
SYS-3: [chars] unable to connect with standby supExplanation This message indicates [chars] is unable to establish a Transmission Control Protocol/Internet Protocol (TCP/IP) connection with the standby supervisor, where [chars] is the active supervisor. This problem can be due to a faulty supervisor module or some other problem in the system.
Recommended Action Perform a system reset. If this message reappears, contact your technical support representative.
SYS-3: Module [dec] runtime image differs from flash image.Explanation This message indicates the following: the runtime image of module [dec] differs from the Flash image; where [dec] is the module number. The nonvolatile random-access memory (NVRAM) update task is not running; and a system reset must be performed to correct the problem.
Recommended Action Perform a system reset. If this message reappears, contact your technical support representative.
SYS-3: [chars] unable to copy flash into DRAMExplanation This message indicates [chars] is unable to uncompress the Flash code and download into dynamic random-access memory (DRAM), where [chars] is the task name.
Recommended Action This condition is possibly due to a bad or corrupted Flash; contact your technical support representative.
SYS-3: [chars] can't send data to standbyExplanation This message indicates an error occurred during Flash code copy from the [chars] active to the standby supervisor, where [chars] is the active supervisor module.
Recommended Action The TCP/IP connection might be broken due to a problem in the system. Contact your technical support representative.
SYS-3: [chars] can't receive data from standbyExplanation This message indicates an error occurred during Flash code copy from the [chars] standby to the active supervisor, where [chars] is the active supervisor module.
Recommended Action The TCP/IP connection might be broken due to a problem in the system. Contact your technical support representative.
SYS-3: [chars] standby is out of syncExplanation This message indicates the duplicate Flash synchronization process between the active and standby supervisor is not working due to some problems in the system, where [chars] is the task name.
Recommended Action Contact your technical support representative.
SYS-3: [chars] status failed received from standbyExplanation This message indicates the standby supervisor was unable to process a TCP/IP request sent by the active supervisor, where [chars] is the task name.
Recommended Action There might be a problem with the standby supervisor; contact your technical support representative.
SYS-3: [chars] standby task SOCKET call failedExplanation This message indicates the TCP/IP "socket" call failed, where [chars] is the standby supervisor. In this case, the duplicate Flash and NVRAM synchronization tasks do not run.
Recommended Action Contact your technical support representative.
SYS-3: [chars] standby task BIND call failedExplanation This message indicates the TCP/IP "bind" call failed, where [chars] is the standby supervisor. In this case, the duplicate Flash and NVRAM synchronization tasks do not run.
Recommended Action Contact your technical support representative.
SYS-3: [chars] standby sup task LISTEN call failedExplanation This message indicates the TCP/IP "listen" call failed, where [chars] is the standby supervisor. In this case, the duplicate Flash and NVRAM synchronization tasks do not run.
Recommended Action Contact your technical support representative.
SYS-3: [chars] standby task ACCEPT call failedExplanation This message indicates the TCP/IP "accept" call failed, where [chars] is the standby supervisor. In this case, the duplicate Flash and NVRAM synchronization tasks do not run.
Recommended Action Contact your technical support representative.
SYS-3: [chars] unknown message receivedExplanation This message indicates the standby supervisor received an unknown TCP/IP message from the active supervisor, where [chars] is the standby supervisor.
Recommended Action Contact your technical support representative.
SYS-3: [chars] can't send data to activeExplanation This message indicates the standby supervisor cannot send data to the active supervisor due to a problem in the system, where [chars] is the task name.
Recommended Action Contact your technical support representative.
SYS-3: [chars] can't receive data from activeExplanation This message indicates the standby supervisor cannot receive data from the active supervisor due to a problem in the system, where [chars] is the task name.
Recommended Action Contact your technical support representative.
SYS-3: [chars] standby is out of syncExplanation This message indicates the standby supervisor cannot receive or send data from the active supervisor due to a problem in the system, where [chars] is the task name.
Recommended Action Contact your technical support representative.
SYS-3: [chars] standby FLASH programming failedExplanation This message indicates the Flash programming of the standby supervisor failed, where [chars] is the task name.
Recommended Action Contact your technical support representative.
SYS-3: [chars] unknown ERROR message receivedExplanation This message indicates an unknown error message was received, where [chars] is the task name.
Recommended Action Contact your technical support representative.
SYS-3: Download connection failed on module [dec]Explanation This message indicates a failed download connection occurred on [dec] block, where [dec] is the module number.
Recommended Action Contact your technical support representative.
Explanation These messages resulted from a module being inserted into a slot that had been configured for another module type, where module [dec] is the module number; [chars] is either an empty field or Ports disabled; Config [chars] is the description of the module configured in NVRAM; Actual [chars] is the description of the module inserted in the slot; and clear config [dec] is the number of the module on which you want to clear the configuration.
Recommended Action Insert a module that matches the slot configuration, or enter the clear config [mod_num/port_num] command to clear the slot; if this message reappears, contact your technical support representative.
SYS-3: Standby Supervisor Module [dec] is running BOOT codeExplanation This message indicates the standby supervisor module [dec] is running BOOT code, where [dec] is the module number.
Recommended Action This message is provided for information only, but could indicate either the boot jumper is ON or the supervisor's Flash is corrupted. If the boot jumper is ON, remove the boot jumper for the module to execute Flash image. If you suspect the supervisor's Flash is corrupted, wait for the active supervisor to reprogram the Flash. If this message reappears, contact your technical support representative.
SYS-3: SEMAPHORE: inv sem_id:[hex] ([chars],[chars])Explanation This message indicates an invalid semaphore is being requested by the specified task's function, where [hex] is the semaphore ID value, the first [chars] is the task name, and the second [chars] is the function name.
Recommended Action The system has an internal error if this message is shown; contact your technical support representative.
SYS-3: SEMAPHORE: inv magic number:[hex] ([chars],[chars])Explanation This message indicates the magic number for a semaphore being requested by the specified task's function is invalid, where [hex] is the magic number, the first [chars] is the task name, and the second [chars] is the function name.
Recommended Action The system has an internal error if this message is shown; contact your technical support representative.
SYS-3: SEMAPHORE: dequeued pid([dec]) not foundExplanation This message indicates the task being removed from a semaphore's waiting list does not exist, where [dec] is the task ID number.
Recommended Action The system has an internal error if this message is shown; contact your technical support representative.
SYS-3: SEMAPHORE: no waiting task to dequeueExplanation This message indicates the semaphore could not find its waiting list while a task is to be removed from it.
Recommended Action The system has an internal error if this message is shown; contact your technical support representative.
SYS-3: SEMAPHORE: [chars] holds too many semaphoresExplanation This message indicates that a task is holding too many semaphores, where [chars] is the name of the task.
Recommended Action This is an internal error. Contact your technical support representative.
SYS-3: SEMAPHORE: [chars] waits the same semaphore [chars]Explanation This message indicates that a task was trying to request the same semaphore it already holds, where [chars] is the name of the task and semaphore [chars] is the name of the semaphore.
Recommended Action This is an internal error. Contact your technical support representative.
SYS-3: SEMAPHORE: kernel wait for semaphore [chars]Explanation This message indicates that the kernel task requests a semaphore, where [chars] is the semaphore name.
Recommended Action This is an internal error. Contact your technical support representative.
SYS-3: FCP Exception received from Module [dec]Explanation This message indicates a Fiber Distributed Data Interface (FDDI) Control Processor (FCP) Exception was received from module [dec], where [dec] is the module number.
Recommended Action Enter the show log [mod_num] command to display FCP information. Contact your technical support representative.
SYS-3: DMP Exception received from Module [dec]Explanation This message indicates a Data Movement Processor (DMP) Exception was received from module [dec], where [dec] is the module number.
Recommended Action Enter the show log [mod_num] command to display DMP information. Contact your technical support representative.
SYS-3: Module [dec] failed due to [chars]Explanation This message indicates module [dec] has failed due to [chars], where [dec] is the module number and [chars] is one of the following: LTL0, LTL1, or LTL2 Error, CBL0, CBL1, or CBL2 Error, or diagnostics. LTLn Error is a local target logic (LTL) error; CBLn Error is the color blocking logic (CBL) error; and diagnostics is the FDDI self-test. The diagnostics designation is only displayed for the FDDI module.
Recommended Action Try resetting the module. If this message reappears, insert a new module; if this message appears again, contact your technical support representative.
SYS-3: Minor problem in Module [dec]Explanation This message indicates a module [dec] failed the self-test, where [dec] is the module number.
Recommended Action Try resetting the module. If this message reappears, insert a new module; if this message reappears, contact your technical support representative.
SYS-3: The NVRAM update tasks will not be running.Explanation This message indicates the NVRAM update task is not running.
Recommended Action Perform a system reset. If the message reappears, contact your technical support representative.
SYS-3: Please reset the system to rectify the problem.Explanation This message indicates a system reset must be performed to correct a problem.
Recommended Action Perform a system reset. If the message reappears, contact your technical support representative.
SYS-3: SWPoll64bCnt task exits: failed to malloc scp queue buffersExplanation This message indicates that you may be out of memory and that the 64-bit counters have not been polled. You may need to increase DRAM size.
Recommended Action Contact your technical support representative.
SYS-3: Memory allocation fail: no 64 bit counters of module [dec] is availableExplanation This message indicates that you may be out of memory and that the 64-bit counters have not been polled. You may need to increase DRAM size.
Recommended Action Contact your technical support representative.
SYS-3: Module [dec] failed to come onlineExplanation This message indicates that module [dec] failed to come online, where [dec] is the module number.
Recommended Action This message is provided for information only.
SYS-5: Please wait while active supervisor is [chars] the NMP imageExplanation This message indicates that the active supervisor is [chars] the NMP image, where [chars] is copying or synchronizing.
Recommended Action This message is provided for information only.
SYS-5: The active supervisor has [chars] the NMP image.Explanation This message indicates that the active supervisor has [chars] the NMP image, where [chars] is copied or synchronized.
Recommended Action This message is provided for information only.
SYS-5:Please wait while standby supervisor is [chars] the NMP image.Explanation This message indicates that the standby supervisor is [chars] the NMP image, where [chars] is copying or synchronizing.
Recommended Action This message is provided for information only.
SYS-5: The supervisor's BOOT images are synchronizedExplanation This message indicates that the supervisor completed synchronizing the BOOT images.
Recommended Action This message is provided for information only.
SYS-5: Module [dec] is in standby modeExplanation This message indicates module [dec] is in standby mode, where [dec] is the module number.
Recommended Action This message is provided for information only.
SYS-5: Module [dec] FLASH programming [chars]Explanation This message applies to intelligent modules only, and indicates the Flash programming condition of the module [dec], where [dec] is the module number, and [chars] could be complete or failed.
Recommended Action This message is provided for information only, but could indicate Flash programming has failed. If this is the case, contact your technical support representative.
Explanation This message indicates that module [dec] was inserted, where [dec] is the module number.
Recommended Action This message is provided for information only. If a module is inserted and the message does not appear, this could indicate a problem. Enter the show module or show port [mod_num/port_num] command to verify the system has acknowledged the module and brought it online. If not, contact your technical support representative.
Explanation This message indicates that module [dec] was removed, where [dec] is the module number.
Recommended Action This message is provided for information only. If a module is removed and the message does not appear, this could indicate a problem. Enter the show port [mod_num/port_num] command to query the module. The system should respond as follows: Module n is not installed. If not, contact your technical support representative.
SYS-5: Module [dec] reset from [chars]\nExplanation This message indicates that module [dec] was reset from [chars]\n, where [dec] is the module number and [chars]\n could be a console number if the request is from a console session, or an IP address if the request is from a Telnet session or Simple Network Management Protocol (SNMP).
Recommended Action This message is provided for information only.
SYS-5: [chars]Explanation This message is informational; examples are listed below:
Sample message: Module 10 onlineNo more messages comingException data: xxxException data: yyyRecommended Action This message is provided for information only.
SYS-5: System reset from [chars]\nExplanation This message indicates the system was reset from [chars]\n, where [chars]\n could be a console number if the request is from a console session, or IP address if the request is from a Telnet session or SNMP.
Recommended Action This message is provided for information only.
SYS-5: System reset from [chars] by [chars]\nExplanation This message indicates the system was reset from [chars] by [chars]\n, where [chars] could be a console number if the request is from a console session, or IP address if the request is from a Telnet session or SNMP; [chars]\n could be the login username, if required.
Recommended Action This message is provided for information only.
SYS-5: Module [dec] reset from [chars] by [chars]\nExplanation This message indicates module [dec] has been reset from [chars] by [chars]\n, where [dec] is the module number and [chars] could be a console number if the request is from a console session, or an IP address if the request is from a Telnet session or SNMP; [chars]\n could be the login username, if required.
Recommended Action This message is provided for information only.
SYS-5: Module [dec] is onlineExplanation This message indicates module [dec] passed diagnostic self-test and is online, where [dec] is the module number.
Recommended Action This message is provided for information only.
SYS-5: Module [dec] is present but not in standby modeExplanation This message appears only when using Supervisor Engine III modules and only on the active Supervisor Engine III module. It occurs in a redundant supervisor system when one of the Supervisor Engine III modules has a problem booting up and gets kicked back out to the ROM-based monitor (ROMMON). Module [dec] indicates the module number.
Recommended Action From the standby supervisor console, manually boot the standby supervisor. If the message reappears, contact your technical support representative.
SYS-5: SPAN_MONITOR message failed to configure source port [dec/dec]Explanation This message indicates that the span feature is not supported on the source module, where [dec/dec] is the [mod_num/port_num].
Recommended Action This message is provided for information only.
SYS-5: Ports on standby supervisor (Module [dec]) are UPExplanation This message indicates that the ports on the standby supervisor are up on systems equipped with redundant supervisor modules. This message occurs when the system is powered up or reset.
Recommended Action This message is provided for information only.
SYS-5: Module [dec] not responding...resetting moduleExplanation This message indicates that the supervisor or the NMP did not receive an acknowledgement from the module after it began executing its boot code, where [dec] is the module number. This message is displayed every three minutes. The module is reset each time. At the end of nine minutes, a failure is declared.
Recommended Action This message is provided for information only.
SYS-5: Module [dec] not responding after download...resetting moduleExplanation This message indicates that the supervisor or the NMP did not receive an acknowledgement from the module after it began executing its runtime code, where [dec] is the module number. This message is displayed every three minutes. The module is reset each time. At the end of nine minutes, a failure is declared.
Recommended Action This message is provided for information only.
SYS-5: Module [dec] failed to respondExplanation This message indicates that, after three resets, the module failed to send a reset acknowledgement to the NMP, where [dec] is the module number. A failure is declared for the module.
Recommended Action Contact your technical support representative.
SYS-5: Download terminated for module [dec]: module removedExplanation This message indicates that during a code download, the module was removed, where [dec] is the module number.
Recommended Action This message is provided for information only.
SYS-5: Download failed for module [dec]Explanation This message indicates that the code download failed for a particular module, where [dec] is the module number.
Recommended Action You can reset the module and try reloading the code. Contact your technical support representative.
This section contains the Catalyst 5000 series switch Cisco Discovery Protocol (CDP) messages.
CDP-3: Transmit failure on port [dec]/[dec]Explanation This message indicates a transmit failure occurred on port [dec]/[dec], where [dec]/[dec] is the [mod_num]/[port_num].
Recommended Action Contact your technical support representative.
CDP-7: Packet dropped as CDP is disabled on port [dec]/[dec]Explanation This message indicates a packet dropped as CDP was disabled on port [dec]/[dec], where [dec]/[dec] is the [mod_num]/[port_num].
Recommended Action Check the CDP port status; if the port is disabled, enable it; if the port is enabled, contact your technical support representative.
This section contains the Catalyst 5000 series switch Cisco Group Management Protocol (CGMP)/Internet Group Management Protocol (IGMP) messages.
MCAST-2: No. of Multicast entries has reached the max [dec]Explanation This message indicates that the number of multicast entries has reached the maximum limit, where [dec] is 3072, the maximum number of multicast entries. No new entries will be created.
Recommended Action Make sure that there are not more than 3072 groups being used. Contact your technical support representative.
MCAST-2: IGMP: Address Aliasing for [hex-hex-hex-hex-hex-hex]
Explanation This message indicates that the NMP detects a multicast data stream that is being aliased to a special multicast address, where [hex-hex-hex-hex-hex-hex] is one of the following multicast addresses causing the aliasing to occur:
01-00-5e-00-00-01
01-00-5e-00-00-04
01-00-5e-00-00-05
01-00-5e-00-00-06
01-00-5e-00-00-0d
Recommended Action Check and isolate the host that is generating this type of multicast traffic. Verify which address is getting aliased and try not to use it for the multicast data feed.
MCAST-2: IGMP: Running in FALL BACK mode
Explanation This message indicates that the NMP detects a multicast data stream that disabled the protocol redirection escape logic and that is being aliased to one of the following special multicast addresses:
01-00-5e-00-00-01
01-00-5e-00-00-04
01-00-5e-00-00-05
01-00-5e-00-00-06
01-00-5e-00-00-0d
Recommended Action Check and isolate the host that is generating this type of multicast traffic. Verify which address is getting aliased and try not to use it for the multicast data feed.
MCAST-2: IGMP: Changed to FALL BACK mode permanently
Explanation This message indicates that the NMP has detected a multicast data stream that disabled the protocol redirection escape logic and that is being aliased to one of the following special multicast addresses:
01-00-5e-00-00-01
01-00-5e-00-00-04
01-00-5e-00-00-05
01-00-5e-00-00-06
01-00-5e-00-00-0d
Recommended Action Check and isolate the host that is generating this type of multicast traffic. Reset the switch or disable and reenable the IGMP snooping feature.
MCAST-4: IGMP: Rcvd IGMP Report GDA [chars] in the range of 01-00-5e-00-00-xxExplanation This message indicates that the switch received an IGMP report from a host for the group address in the range of 01-00-5e-00-00-xx, where [chars] is the host name. This range is normally used for control packets and should not be used for general multicast data traffic.
Recommended Action Contact your technical support representative.
MCAST-4: IGMP: Rcvd IGMP Leave GDA [chars] in the range of 0-00-5e-00-00-xxExplanation This message indicates that the switch received an IGMP leave from a host for the group address in the range of 01-00-5e-00-00-xx, where [chars] is the name of the host. This range is normally used for control packets and should not be used for general multicast data traffic.
Recommended Action Contact your technical support representative.
MCASR-4: Deleting Router Port [dec/dec] in vlan [dec] - TimeoutExplanation This message indicates that the router port timer has timed out and the router port entry has been removed, where [dec/dec] is the router [mod_num/port_num] and [dec] is the VLAN number. This problem might be due to the switch not receiving any router specific packets (IGMP general queries, PIMV1 queries, DVMRP probes, PIMV2 hellos, or MOSPF hellos).
Recommended Action Check to see that a router is on that port and verify that IGMP is enabled.
MCAST-5: IGMP Snooping Feature is [chars]abledExplanation This message indicates that the IGMP snooping feature is either enabled or disabled, where [chars] is either [en] abled or [dis] abled.
Recommended Action This message is provided for information only.
MCAST-5: CGMP Feature is [chars]abledExplanation This message indicates that the CGMP feature is either enabled or disabled, where [chars] is either [en] abled or [dis] abled.
Recommended Action This message is provided for information only.
MCAST-5: IGMP: Running in NORMAL modeExplanation This message indicates that NMP has recovered from address aliasing and has reenabled redirection escape logic for the following multicast addresses:
01-00-5e-00-00-01Recommended Action This message is provided for information only.
MCAST-6: Deleting a GDA [chars] in vlan [dec]Explanation This message indicates that a multicast entry in the given VLAN is being deleted because of an IGMP leave from the last host for this GDA was received, where [chars] is the group destination address and [dec] is the VLAN number.
Recommended Action Contact your technical support representative.
MCAST-6: Recvd Topology Change Notification in vlan [dec]Explanation This message indicates that the NMP received a topology change notification in a VLAN, where [dec] is the VLAN number.
Recommended Action This message is provided for information only.
MCAST-6: Adding Router Port [dec/dec] in vlan [dec] - User ConfigdExplanation This message indicates that the user has used the set multicast router command to set a user-configured multicast router, where [dec/dec] is the [mod_num/port_num] and [dec] is the VLAN number.
Recommended Action This message is provided for information only.
MCAST-6: Adding Router Port [dec/dec] in vlan [dec]Explanation This message indicates that CGMP/IGMP has learned a new router port, where [dec]/[dec] is the [mod_num/port_num] and vlan [dec] is the VLAN number.
Recommended Action This message is provided for information only.
MCAST-6: Adding Router Port [dec]/[dec] in vlan [dec] - PIM mesgExplanation This message indicates that CGMP/IGMP snooping has learned a router port via PIM messages, where [dec]/[dec] is the [mod_num/port_num] and vlan [dec] is the VLAN number.
Recommended Action This message is provided for information only.
MCAST-6: Adding Router Port [dec/dec] in vlan [dec] - HSRP mesgExplanation This message indicates that CGMP/IGMP snooping has learned a router port via Hot Standby Router Protocol (HSRP) messages, where [dec]/[dec] is the [mod_num/port_num] and vlan [dec] is the VLAN number.
Recommended Action This message is provided for information only.
MCAST-6: CGMP: Rcvd CGMP Leave Mesg [dec/dec] vlan [dec]Explanation This message indicates that a CGMP leave message was received on a VLAN port, where [dec/dec] is the [mod_num/port_num] where the message was received, and VLAN [dec] is the VLAN number.
Recommended Action This message is provided for information only.
MCAST-6: CGMP: Rcvd CGMP Join Mesg GDA [chars] in vlan [dec]Explanation This message indicates that a CGMP join message was received by a VLAN, where [chars] is the group destination address and [dec] is the VLAN number.
Recommended Action This message is provided for information only.
MCAST-6: CGMP: GDA: [chars] USA: [chars]Explanation This message indicates that the system has received a CGMP join message for the GDA from the router for the host whose source address is USA, where [chars] is the group destination address and [chars] is the unicast source address.
Recommended Action This message is provided for information only.
This section contains the Catalyst 5000 series switch Dual Ring Protocol (DRiP) messages.
DRIP-3: Drip Already Initialized.Explanation This message indicates that DRiP was previously enabled and initialized, and a software module requested a reinitialization of the database.
Recommended Action Contact your technical support representative.
DRIP-3: Drip Already Shutdown.Explanation This message indicates that DRiP was previously shut down, and a software module has requested another shutdown.
Recommended Action Contact your technical support representative.
DRIP-3: Vlanid [dec] out of range. MAC [chars].Explanation This message indicates the DRiP database received a request to enter a vlanid [dec] that is out of range, where [dec] is the VLAN number and [chars] is the MAC address.
Recommended Action Document the Vlanid [dec] and the MAC address [chars], and contact your technical support representative.
DRIP-3: No Local Box. Vlanid [dec], MAC [chars].Explanation This message indicates the DRiP database was called, but no entry exists for the local MAC address and VLAN, where [dec] is the VLAN number and [chars] is the MAC address.
Recommended Action Contact your technical support representative.
DRIP-3: No Mac [chars] Match. Vlanid [dec]Explanation This message indicates the DRiP database was called, but no entry exists for this MAC address on the VLAN, where [chars] is the MAC address and [dec] is the VLAN number.
Recommended Action Contact your technical support representative.
DRIP-3: No Vlanid [dec] Match. MAC [chars].Explanation This message indicates that the DRiP database was called, but no entry exists for the VLAN for this switch, where [dec] is the VLAN number and [chars] is the switch name.
Recommended Action Contact your technical support representative.
DRIP-3: Invalid Change Request. Status [hex].Explanation This message indicates that the DRiP database was called to update the database for status byte [hex], which is invalid, where [hex] is the status byte.
Recommended Action Contact your technical support representative.
DRIP-3: Drip Core Error.Explanation This message indicates that the DRiP code has detected an internal error, and it is an unreliable process at this point.
Recommended Action Execute the show drip statistics command and provide the information to your technical support representative.
DRIP-3: LOC: [chars], REM: [chars].Explanation This message precedes each DRiP-3 level conflict message (for example, Invalid Change Request. Status [hex]), where the first [chars] is the MAC address for the local switch and the second [chars] is the MAC address for the remote switch.
Recommended Action This message is provided for information only.
DRIP-4: Vlanid [dec] Configuration conflict.Explanation This message indicates that a Token Ring Concentrator Relay Function (TrCRF) VLAN has ports assigned on multiple switches that distribute the Concentrator Relay Function (CRF) VLAN, where [dec] is the VLAN number. Port assignments are only allowed on a single switch for this VLAN.
Recommended Action Reassign ports for this VLAN only to one switch. If this message reappears, contact your technical support representative.
DRIP-4: Vlanid [dec] Active Conflict. Status [hex]Explanation This message indicates that a TrCRF VLAN has ports assigned and active on multiple switches that distribute the CRF VLAN, where [dec] is the VLAN number and [hex] is the returned status. The DRiP database has an invalid status indication for this VLAN.
Recommended Action Contact your technical support representative.
DRIP-4: Vlanid [dec] Configuration/Active Conflict.Explanation This message indicates that a TRCRF VLAN has ports assigned and active on multiple switches that distribute the CRF VLAN, where [dec] is the VLAN ID number. Port assignments are allowed only on a single switch for this VLAN.
Recommended Action Reassign ports for this VLAN to one switch. If this message reappears, contact your technical support representative.
DRIP-4: LOC: [chars], REM: [chars].Explanation This message precedes each DRiP-4 level conflict message (for example, Configuration conflict on vlan [dec]), where the first [chars] is the MAC address for the local switch, and the second [chars] is the MAC address for the remote switch.
Recommended Action This message is provided for information only.
DRIP-5: SCP Failure.Explanation This message indicates that DRiP tried to send a Serial Communications Protocol (SCP) message to a module and failed.
Recommended Action Contact your technical support representative.
This section contains the Catalyst 5000 series switch Dynamic VLAN (DVLAN) messages.
DVLAN-1: Port [dec]/[chars] shutdown by VMPSExplanation This message indicates the VLAN Membership Policy Server (VMPS) detects an unknown MAC address on port [dec]/[chars] and shuts down the port, where [dec]/[chars] is the [mod_num]/[port_range].
Recommended Action Remove the unknown host and enable the port. Retry operation. If this message reappears, contact your technical support representative.
DVLAN-1: Port [dec]/[chars] shutdown by EARL failureExplanation This message indicates a dynamic EARL entry for a new host cannot be set in EARL because all four pages for the hashed index are full, where [dec]/[chars] is the [mod_num]/[port_range].
Recommended Action Enable the port and retry operation. If this message reappears, contact your technical support representative.
DVLAN-1: Port [dec]/[chars] shutdown by active host limitExplanation This message indicates more than 50 active hosts are detected on a dynamic port, where [dec]/[chars] is the [mod_num]/[port_range].
Recommended Action Reduce the active hosts. Enable the port and retry operation. If this message reappears, contact your technical support representative.
DVLAN-1: Host [chars] denied on port [dec]/[chars]
Explanation This message indicates the VMPS sent a response to deny connectivity to the host, where [chars] is the host's MAC address and [dec]/[chars] is the
[mod_num]/[port_range].
Recommended Action Check the VMPS database to see why it is denied. If the database information is correct, contact your technical support representative.
DVLAN-1: Host [chars] denied on port [dec]/[chars] by inactive vlanExplanation This message indicates the VLAN assigned by the VMPS is not active in the switch, where [chars] is the host's MAC address and [dec]/[chars] is the [mod_num]/[port_range].
Recommended Action Make sure the VLAN is active and retry operation. If this message reappears, contact your technical support representative.
DVLAN-1: VMPS address not configuredExplanation This message indicates the VMPS server address has not been configured.
Recommended Action Configure the VMPS server address. If this message reappears, contact your technical support representative.
DVLAN-3: Failed to open socket for DVLANExplanation This message indicates a failure to open a socket for DVLAN has occurred.
Recommended Action Set all the dynamic ports to static and then try to set them back to dynamic. If unsuccessful, contact your technical support representative.
DVLAN-3: Failed to bind DVLAN socketExplanation This message indicates a failure to bind DVLAN socket has occurred.
Recommended Action Set all the dynamic ports to static and then try to set them back to dynamic. If unsuccessful, contact your technical support representative.
DVLAN-3: Failed (err = [dec]) to send query to VMPS [chars]Explanation This message indicates a failure to send a query to the VMPS has occurred, where [dec] is the error number and [chars] is the VMPS address.
Recommended Action Contact your technical support representative about the error number displayed in the message.
DVLAN-3: Failed (err = [dec]) to receive response from VMPS [chars]Explanation This message indicates a failure to receive a response from the VMPS has occurred, where [dec] is the error number and [chars] is the VMPS server address.
Recommended Action Contact your technical support representative about the error number displayed in the message.
DVLAN-3: EARL trap diag failed on supervisor moduleExplanation This message indicates the EARL trap diagnostics have failed. If the EARL trap diagnostics have failed, the ports cannot be set to dynamic.
Recommended Action Enter the show test command to check for trap failures. Reset the system. If this message reappears, contact your technical support representative.
DVLAN-3: EARL trap not supported in supervisor moduleExplanation This message indicates an older supervisor module was installed (hardware version 1.3 or lower) that does not support the trap feature in EARL. Ports cannot be set to dynamic in these modules.
Recommended Action Contact your technical support representative.
DVLAN-3: Invalid-Version opcode in responseExplanation This message indicates the VMPS response has an invalid version number. The VMPS version should be 1.
Recommended Action Contact your technical support representative.
DVLAN-3: Invalid-Management-Domain opcode in responseExplanation This message indicates the management domain name in the VMPS response does not match the VLAN Trunking Protocol (VTP) domain name set in the system.
Recommended Action Correct the domain name either in the database or in the system.
DVLAN-3: Invalid VLAN ID ([chars]) in responseExplanation This message indicates the VLAN name in the VMPS response is not available in the system, where ([chars]) is the VLAN name.
Recommended Action Create a VLAN with the proper VLAN name.
DVLAN-3: No-Resource opcode in responseExplanation This message indicates the VMPS responds with no-resource.
Recommended Action Contact your technical support representative.
DVLAN-3: Response has no VLAN IDExplanation This message indicates the VMPS response has no VLAN name.
Recommended Action Check the VMPS server, and then contact your technical support representative.
DVLAN-3: Response has no CookieExplanation This message indicates the VMPS response has no Cookie.
Recommended Action Check the VMPS server, and then contact your technical support representative.
DVLAN-4: No dynamic ports configuredExplanation This message indicates a reconfirm VMPS command was executed and no dynamic ports were configured.
Recommended Action No action is necessary.
DVLAN-4: No host on dynamic portsExplanation This message indicates the reconfirm VMPS command was executed and no active host is connected to the dynamic ports.
Recommended Action No action is necessary.
DVLAN-7: VLAN [dec] assigned to Port [dec]/[chars]Explanation This message appears only during debugging; it indicates a VLAN was assigned to a dynamic port, where [dec] is the VLAN number and [dec]/[chars] is the [mod_num]/[port_range].
Recommended Action No action is necessary.
DVLAN-7: Primary VMPS [chars] is aliveExplanation This message appears only during debugging; it indicates the switch can talk to the VMPS server, where [chars] is the name of the server.
Recommended Action No action is necessary.
This section contains the Catalyst 5000 series switch Dynamic Inter-switch Link (DISL) messages.
DISL-3: Port [dec]/[chars] failed to become trunkExplanation This message indicates the port [dec]/[chars] failed to become trunked, where [dec]/[chars] is the [mod_num]/[port_range].
Recommended Action Perform these steps, retrying the connection after each step:
Step 1 Check the total memory available. If the total memory is close to 0, this might be the cause of the failure; contact your technical support representative. If total memory available is not close to 0, proceed to the next step.
Step 2 Check the status of the Serial Communications Protocol (SCP) and observe the count field. If the count rises, this might be the cause of the failure; contact your technical support representative. If the count does not rise, contact your technical support representative.
DISL-3: Port [dec]/[chars] failed to become non-trunk
Explanation This message indicates the port [dec]/[chars] failed to become nontrunked, where [dec]/[chars] is the [mod_num]/[port_range].
Recommended Action Perform these steps, retrying the connection after each step:
Step 1 Check the total memory available. If the total memory is close to 0, this might be the cause of the failure; contact your technical support representative. If the total memory available is not close to 0, proceed to the next step.
Step 2 Check the status of the SCP and observe the count field; repeat several times. If the count rises, this might be the cause of the failure; contact your technical support representative. If the count does not rise, contact your technical support representative.
DISL-5: Port [dec]/[chars] has become trunkExplanation This message indicates the port [dec]/[chars] is trunked, where [dec]/[chars] is the [mod_num]/[port_range].
Recommended Action This message is provided for information only.
DISL-5: Port [dec]/[chars] has become non-trunkExplanation This message indicates the port [dec]/[chars] is nontrunked, where [dec]/[chars] is the [mod_num]/[port_range].
Recommended Action This message is provided for information only.
DISL-7: Port [dec]/[dec] Link upExplanation This message indicates that DISL detects a link-up for port [dec]/[dec], where [dec]/[dec] is the [mod_num]/[port_num].
Recommended Action Contact your technical support representative.
DISL-7: Port [dec]/[dec] Link downExplanation This message indicates that DISL detects a broken link for port [dec]/[dec], where [dec]/[dec] is the [mod_num]/[port_num].
Recommended Action Contact your technical support representative.
DISL-7: Port [dec]/[dec] recd [chars], [chars] from [chars]Explanation This message displays the DISL status received by port [dec]/[dec] and the MAC address of the neighbor port, where [dec][dec] is the [mod_num]/[port_num], recd [chars] is the received status, and [chars] from [chars] is the MAC address of the neighboring port.
Recommended Action Contact your technical support representative.
DISL-7: Port [dec]/[dec] not recd DISL packet for 5m.Explanation This message indicates that the port [dec]/[dec] is nontrunking because it has not received any DISL packet from its neighbor port for five minutes, where [dec][dec] is the [mod_num]/[port_num].
Recommended Action Contact your technical support representative.
This section contains the Catalyst 5000 series switch EARL messages.
EARL-3: Earl delete errorExplanation An attempt to delete an EARL entry failed.
Recommended Action Contact your technical support representative.
EARL-3: Bad color [dec] read from [hex] for a [chars] entryExplanation This message indicates that the system has learned a MAC address on an invalid VLAN, where [dec] is the VLAN number, [hex] is the location, and [chars] is either the message static or dynamic.
Recommended Action This message is provided for information only.
EARL-3: Can't remove timer [dec] from vlan [dec]Explanation This message indicates the EARL cannot remove the aging timer for this VLAN, where timer [dec] is the timer number and vlan [dec] is the VLAN number.
Recommended Action Contact your technical support representative.
EARL-3: Can't set timer [dec] from vlan [dec]Explanation This message indicates the EARL cannot set the aging timer for this VLAN, where timer [dec] is the timer number and vlan [dec] is the VLAN number.
Recommended Action Contact your technical support representative.
EARL-3: LTL : Failure with module [dec]Explanation This message indicates the EARL cannot program the LTL of the module, where [dec] is the module number.
Recommended Action Contact your technical support representative.
EARL-5: FDDI failureExplanation This message indicates the EARL cannot program the Fiber Distributed Data Interface (FDDI).
Recommended Action Contact your technical support representative.
This section contains the Catalyst 5000 series switch Flash file system (FILESYS) messages.
FILESYS-1: PCMCIA flash card inserted into [chars]Explanation This message indicates that a Flash card ws inserted into [chars], where [chars] could be slot0 or slot1.
Recommended Action This message is provided for information only.
FILESYS-1: PCMCIA flash card removed from [chars]Explanation This message indicates that a Flash card was removed from [chars], where [chars] could be slot0 or slot1.
Recommended Action This message is provided for information only.
This section contains the Catalyst 5000 series switch IP Permit List messages.
IP-4: Unauthorized [chars] access attempt from [chars]Explanation This message indicates an unauthorized access was attempted, where the first [chars] is the access type, currently Telnet or SNMP, and the second [chars] is the IP address where the unauthorized attempt was made.
Recommended Action Retry access. If this message reappears, contact your technical support representative.
This section contains the Catalyst 5000 series switch KERNEL messages.
Explanation This is a debug message for Cisco development purposes.
Recommended Action Contact your technical support representative.
KERNEL-0: sleep() called from Kernel context.Explanation This is a debug message for Cisco development purposes.
Recommended Action Contact your technical support representative.
KERNEL-1: stk-alrt [chars],sp: %08x size: 0x%04xExplanation This is a debug message for Cisco development purposes, where [chars] is the stk-alrt message.
Recommended Action Contact your technical support representative.
KERNEL-4: yield_cpu() called from Kernel context.Explanation This is a debug message for Cisco development purposes.
Recommended Action Contact your technical support representative.
KERNEL-4: pdelay () called from Kernel context.Explanation This message indicates that a function is calling a kernel utility from the kernel context.
Recommended Action Call your technical support representative.
KERNEL-5: Alignment correction made at 0x%08X [chars]ing 0x%08XExplanation This is a debug message for Cisco development purposes.
Recommended Action Ignore this message.
This section contains the Catalyst 5000 series switch Logical Link Control (LLC) massages.
LOG_ERROR-3: LLC failed to register to Ibipc2.Explanation This message indicates that the supervisor cannot communicate with the module for Layer 2 protocol packets.
Recommended Action Contact your technical support representative.
LOG_ERROR-3: LLC send scp message failed.Explanation This is a debug message for Cisco development purposes.
Recommended Action Ignore this message.
LOG_ERROR-3: entry exists in LLC registration table.Explanation This is a debug message for Cisco development purposes.
Recommended Action Ignore this message.
LOG_ERROR-3: entry not exists in LLC registration table.Explanation This is a debug message for Cisco development purposes.
Recommended Action Ignore this message.
LOG_ERROR-3: LLC registration table full.Explanation This message indicates that a Layer 2 protocol cannot be registered. The supervisor is unable to receive this protocol's packets.
Recommended Action Contact your technical support representative.
LOG_ERROR-3: LLC send scp message command status not SCPSTAT_OK.Explanation This is a debug message for Cisco development purposes.
Recommended Action Ignore this message.
This section contains the Catalyst 5000 series switch MGMT messages for TopN.
MGMT-5: TopN report [dec] available.Explanation This message indicates the TopN report running in background is ready, where [dec] is the TopN report number.
Recommended Action This message is provided for information only.
MGMT-5: TopN report [dec] started by [chars].Explanation This message indicates that the TopN message [dec] running with the background option [chars] is generating the report, where [dec] is the TopN report number and [chars] is the process that started the report. A second message is generated when the report is available.
Recommended Action This message is provided for information only.
MGMT-5: TopN report [dec] killed by [chars].Explanation This message indicates that the TopN message [dec] was terminated by [chars], where [dec] is the TopN report number and [chars] is the process that stopped the report generation.
Recommended Action This message is provided for information only.
MGMT-5: TopN report [dec] aborted due to configuration changes.Explanation This message indicates the TopN report was aborted due to a configuration change, where [dec] is the number of the TopN report.
Recommended Action This message is provided for information only.
MGMT-5: TopN report [dec] dropped module [dec] data due to module reset.Explanation This message indicates that the TopN report [dec] will not contain any ports from module [dec] because the module was reset during the report generation, where report [dec] is the TopN report number and module [dec] is the module number.
Recommended Action This message is provided for information only.
This section contains the Catalyst 5000 series switch Multilayer Switching (MLS) messages.
MLS-2: Whistler parity error. MLS stopped.Explanation This message indicates that a parity error occurred in the EARL2 Whistler ASIC.
Recommended Action This is a hardware defect. Contact your technical support representative.
MLS-2: Whistler MI error exceeded threshold. MLS stopped.Explanation This message indicates that the number of memory interface errors exceeded the threshold. MLS is disabled.
Recommended Action This is a hardware defect. Contact yout technical support representative.
MLS-3: Get new learn mac notification [hex].Explanation This message indicates that MLS is not supposed to get any new source address learned notification, where [hex] is the new source address. This message indicates an internal error.
Recommended Action Contact your technical support representative.
MLS-3: Whistler xtag error.Explanation This message indicates that an xtag error occurred in the EARL2 Whistler ASIC. This error does not affect the MLS functionality.
Recommended Action This message is provided for information only.
MLS-3: Whistler MI error. MI hard reset.Explanation This message indicates that a memory interface error occurred in the EARL2 Whistler ASIC. The memory interface is hard reset.
Recommended Action This message is provided for information only.
MLS-4: Event loss, purge all entries!Explanation This message indicates an internal MLS event loss due to insufficient system resources. All MLS entries are purged.
Recommended Action This message is provided for information only.
MLS-4: Resume MLS after detecting too many moves.Explanation This message indicates that MLS has resumed after being stopped due to too many Layer 2 source address changes being detected in a short period of time.
Recommended Action This message is provided for information only.
MLS-4: Too many moves, stop MLS for [dec] sec! ([hex])Explanation This message indicates that there have been too many Layer 2 source address changes during a short period of time. This message might be caused by topology changes or spanning tree loops. MLS is stopped for [dec] seconds and all entries are purged, where [dec] is the number of seconds and [hex] indicates the event code for moves.
Recommended Action Check the topology for any loops. Call your technical support representative.
MLS-5: Multilayer switching is disabled.Explanation This message indicates that MLS is disabled.
Recommended Action This message is provided for information only.
MLS-5: Multilayer switching is enabled.Explanation This message indicates that MLS is enabled.
Recommended Action This message is provided for information only.
MLS-5: NetFlow Data Export enabled.Explanation This message indicates that flow statistics for all aged flows are being sent to the configured host in a UDP datagram.
Recommended Action This message is provided for information only.
MLS-5: NetFlow data export disabled.Explanation This message indicates that flow statistics for all aged flows have stopped being sent.
Recommended Action This message is provided for information only.
This section contains the Catalyst 5000 series switch Port Aggregation Protocol (PAgP) and Fast EtherChannel (FEC) messages.
PAGP-3: Failure = [dec] in configPortChannel for mNo/pNo = [dec]/[dec].Explanation This message indicates the system was unable to configure the channel properly, where [dec] is the return status and [dec]/[dec] is the [mod_num]/[port_num].
Recommended Action Try to reset the failing ports. If the message reappears, contact your technical support representative.
PAGP-3: [chars] queue is full.Explanation This message indicates the message buffer between two processors is full, where [chars] identifies the buffer.
Recommended Action Reset the system. If the message reappears, contact your technical support representative.
PAGP-5: Port [dec]/[dec] joined bridge port [dec]/[chars].Explanation This message indicates the physical port joined the logical port, where [dec]/[dec] is the [mod_num]/[port_num] and [dec]/[chars] is the [mod_num]/[port_range].
Recommended Action Contact your technical support representative.
PAGP-5: Port [dec]/[dec] left bridge port [dec]/[chars].Explanation This message indicates the physical port disconnected from the logical port, where [dec]/[dec] is the [mod_num/port_num] and [dec]/[chars] is the [mod_num]/[port_range].
Recommended Action Contact your technical support representative.
PAGP-7: Unknown message in queue [chars].Explanation This message indicates the processor received a message it cannot identify, where [chars] is the message's character string.
Recommended Action This message is provided for information only.
PAGP-7: Failed to transmit info pdu --- no active vlan ([dec]/[dec]).Explanation This message indicates the system tried to transmit a packet through a VLAN that was not active, where [dec]/[dec] is the [mod_num]/[port_num].
Recommended Action Contact your technical support representative.
PAGP-7: Failed to transmit info pdu --- disabled STP ([dec]/[dec]).Explanation This message indicates spanning tree is disabled and cannot transmit a packet, where [dec]/[dec] is the [mod_num]/[port_range].
Recommended Action Contact your technical support representative.
PAGP-7: ([dec]/[dec]) vlan inactive.Explanation This message indicates the system tried to transmit a packet to a VLAN but the VLAN is not active, where [dec]/[dec] is the [mod_num/port_num].
Recommended Action Contact your technical support representative.
PAGP-7: Invalid agportIndex = [dec] (mNo/aNo = [dec]/[dec]).Explanation This message indicates the agportIndex is out of range (the logical port is invalid), where [dec] is the index and [dec]/[dec] is the logical port.
Recommended Action Contact your technical support representative.
PAGP-7: Failed to get port from portList.Explanation This message indicates the logical port list did not contain at least one physical port.
Recommended Action Contact your technical support representative.
PAGP-7: Wait for successful memory allocation.Explanation This message indicates the system is trying to dynamically allocate more memory for an operation, but there is insufficient memory left.
Recommended Action Contact your technical support representative.
PAGP-7: Failed to create PAgP_Group_Rx process.Explanation This message indicates the PAgP_Group_Rx process was not created, so channeling is not allowed.
Recommended Action Contact your technical support representative.
PAGP-7: No (SCP) memory for PAgP_Group_Rx process.Explanation This message indicates that the processor is trying to send a message to a module to configure a channel, but the buffer is unexpectedly full.
Recommended Action Try resetting the system. If the message reoccurs, contact your technical support representative.
This section contains the Catalyst 5000 series switch protocol filter messages.
PROTFILT-5: Port [dec]/[dec] is set to AUTO-ON for [chars]Explanation This message indicates the port is set to auto-on for a protocol group, where [dec]/[dec] is the [mod_num/port_num] and [chars] is the protocol group.
Recommended Action This message is provided for information only.
PROTFILT-5: Port [dec]/[dec] is set to AUTO-OFF for [chars]Explanation This message indicates the port is set to auto-off for a protocol group, where [dec]/[dec] is the [mod_num/port_num] and [chars] is the protocol group.
Recommended Action This message is provided for information only.
This section contains the Catalyst 5000 series switch SNMP messages for Remote Monitoring (RMON).
SNMP-5: [chars] Table is FullExplanation This message indicates the [chars] Table is full, where [chars] is the history, alarm, or event Table.
Recommended Action Release some memory by deleting some of the existing RMON entries. If the message reappears, contact your technical support representative.
SNMP-5: Out of RMON ScpUsageExplanation This message indicates that the scpUsage for RMON is full.
Recommended Action Contact your technical support representative.
SNMP-5: No memory for ControlEntryExplanation This message indicates that memory is full; no new RMON Tables can be installed.
Recommended Action Release some memory by deleting some of the existing RMON entries. If the message reappears, contact your technical support representative.
SNMP-5: Alarm Index [dec] is Not SavedExplanation This message indicates that the Alarm Entry with [dec] Index is not saved in NVRAM, where [dec] is the index of the alarmEntry.
Recommended Action Set the alarmVariable of the entry to an object whose Management Information Base (MIB) object identifier (OID) length is less than or equal to 18. If the message reappears, contact your technical support representative.
SNMP-5: UpdateNvram() failed: blockno is [dec]Explanation This message indicates that updating the NVRAM configuration for [dec] block failed, where [dec] is the NVRAM block.
Recommended Action You might be out of memory. Enter the show version command to ensure you are running the correct version. Free some memory if necessary. If the message reappears, contact your technical support representative.
SNMP-5: Rmon Enable is progress, In another sessionExplanation This message indicates that in one Telnet session, an RMON enable is in progress, and at the same time, another Telnet session user is trying to enable RMON.
Recommended Action Try to enable RMON at a later time. If the message reappears after numerous tries, contact your technical support representative.
SNMP-5: Rmon Disable is progress, In another sessionExplanation This message indicates that in one Telnet session, an RMON disable is in progress, and at the same time, another Telnet session user is trying to disable RMON.
Recommended Action Try to disable RMON at a later time. If the message reappears after numerous tries, contact your technical support representative.
This section contains the Catalyst 5000 series switch SNMP messages.
SNMP-2 Can't open TCP socket for [dec]Explanation This message indicates the TCP socket for [dec] cannot be opened, where [dec] is the TCP port number.
Recommended Action Reboot the system.
SNMP-3: Can't open UDP socket for [dec]Explanation This message indicates the User Datagram Protocol (UDP) socket for [dec] cannot be opened, where [dec] is the UDP port number.
Recommended Action Reboot the system.
SNMP-5: Repeater health trap:rptrOperStatus([dec],[dec])=[chars]Explanation This message indicates the repeater health trap:rptrOperStatus status, where [dec],[dec] is the [mod_num], [port_num], and [chars] is one of the following: other, ok, rptrFailure, groupFailure, portFailure, or generalFailure.
Recommended Action This message is provided for information only.
SNMP-5: Repeater reset trap:rptrOperStatus([dec],[dec])=[chars]Explanation This message indicates the repeater reset trap:rptrOperStatus status, where [dec],[dec] is the [mod_num], [port_num], and [chars] is one of the following: other, ok, rptrFailure, groupFailure, portFailure, or generalFailure.
Recommended Action This message is provided for information only.
SNMP-5: Module [dec] [[chars]] TrapExplanation This message indicates the type of module [dec] [[chars]] Trap, where [dec] is the module number and [[chars]] is up or down.
Recommended Action This message is provided for information only.
SNMP-5: FDDI Ler Alarm [[chars]] Trap for [[dec]/[dec]]Recommended Action This message is provided for information only.
SNMP-5: Chassis Alarm Trap: tmpAlarm([chars]), minorAlarm([chars]), and/or majorAlarm([chars])Explanation This message indicates the on/off condition of the Chassis Alarm Trap: tmpAlarm([chars]), minorAlarm([chars]), and/or majorAlarm([chars]), where [chars] could be ON or OFF.
Recommended Action This message is provided for information only.
SNMP-5: Cold Start TrapExplanation This message indicates the sending protocol entity is reinitializing itself so the agent's configuration or the protocol entity implementation might be altered.
Recommended Action This message is provided for information only.
SNMP-5: New Root Trap for VLAN [[dec]]Explanation This message indicates that there is a new root of the spanning tree, where [[dec]] is a VLAN number.
Recommended Action This message is provided for information only.
SNMP-5: Topology Change Trap for VLAN [[dec]]Explanation This message indicates a configured port changed from the learning state to the forwarding state, or from the forwarding state to the blocking state, where [[dec]] is a VLAN number.
Recommended Action This message is provided for information only.
SNMP-5: Link [chars] Trap -- ifName=[chars]Explanation This message indicates the type of Link [chars] Trap if the name is [chars], where the first [chars] is up or down and the second [chars] is sc0/sl0/mNo-pNo.
Recommended Action This message is provided for information only.
SNMP-5: Entity Mib last change time [dec] ticks.Explanation This message indicates that the value of entLastChangeTime MIB object was changed, where [dec] is the value of sysUpTime at the time this event occurs.
Recommended Action This message is provided for information only.
SNMP-5: Warm Start Trap.Explanation This message indicates that the standby supervisor module has taken control.
Recommended Action This message is provided for information only.
SNMP-5: STP Extension Inconsistency vlan [dec] port [[dec/dec]] ([chars]).Explanation This message indicates that the Spanning-Tree Protocol (STP) has detected an inconsistency in the VLAN, where [dec] is the VLAN number, [[dec/dec]] is the [mod_num/port_num], and ([chars]) is the inconsistency detected.
Recommended Action This message is provided for information only.
SNMP-6: UDP socket [[dec]] openedExplanation This message indicates the UDP socket [[dec]] opened, where [[dec]] is the UDP port number.
Recommended Action This message is provided for information only.
SNMP-6: UDP socket [[dec]] closedExplanation This message indicates the UDP socket [[dec]] closed, where [[dec]] is the UDP port number.
Recommended Action This message is provided for information only.
SNMP-6: TCP socket [[dec]] openedExplanation This message indicates the TCP socket [[dec]] opened, where [[dec]] is the TCP port number.
Recommended Action This message is provided for information only.
SNMP-6: TCP socket [[dec]] closedExplanation This message indicates the TCP socket [[dec]] closed, where [[dec]] is the TCP port number.
Recommended Action This message is provided for information only.
SNMP-6: Subagent [dec] [chars]Explanation This message indicates the connection status of the subagent [dec], where [dec] is the subagent number and [chars] is disconnected or connected.
Recommended Action This message is provided for information only.
SNMP-6: Subagent [dec] Timeout, drop connectionExplanation This message indicates that the subagent has been disconnected when the master agent times out during communications with the subagent, where [dec] is the subagent index.
Recommended Action This message is provided for information only
SNMP-6: Disconnect Subagent [dec], [chars]Explanation This message indicates that the subagent has been disconnected, where [dec] is the subagent index and [chars] is the reason for the disconnection.
Recommended Action This message is provided for information only.
This section contains the Catalyst 5000 series switch Spanning-Tree Protocol messages.
SPANTREE-2: Channel misconfig - [dec]/[chars] will be disabled.Explanation This message indicates that a port channel misconfiguration has been detected and the channel ports will be disabled to avoid a broadcast storm in the network, where [dec] is the module number and [chars] is a list of ports in that channel. (For channel configuration guidelines, refer to the Catalyst 5000 Series Software Configuration Guide.)
Recommended Action Enter the set port channel command to reconfigure the ports. Then reenable the ports. (For more information about the set port channel command, refer to the Catalyst 5000 Series Software Configuration Guide.) If this message reappears, contact your technical support representative.
SPANTREE-2: Rcved 1Q-BPDU on non-trunk port [dec]/[chars] vlan [dec]Explanation This message indicates that the nontrunking port has received at least one 1Q-tagged spantree bridge protocol data unit (BPDU) frame on the receiving VLAN, where [dec] is the module number, [chars] is the port number, and the second [dec] is the VLAN number.
Recommended Action Either reconfigure the nontrunking port into a 1Q-trunking port, or reconfigure the peer 1Q-trunking port into a nontrunking port.
SPANTREE-2: Rcved 1Q-BPDU on non-1Q-trunk port [dec]/[chars] vlan [dec].Explanation This message indicates that the non-1Q-trunking (ISL) port has received at least one 1Q-tagged spantree BPDU frame on the receiving VLAN, where [dec] is the module number, [chars] is the port number, and the second [dec] is the VLAN number.
Recommended Action Either reconfigure the non-1Q-trunking port into a 1Q-trunking, or reconfigure the peer 1Q-trunking port into the corresponding non-1Q-trunking port.
SPANTREE-2: Rcved pvid_inc BPDU on 1Q port [dec]/[chars] vlan [dec].Explanation This message indicates that the 1Q-trunking port has received at least one 1Q-tagged spantree BPDU frame with an inconsistent transmitting VLAN ID to the receiving port VLAN ID, where [dec] is the module number, [chars] is the port number, and the second [dec] is the VLAN number.
Recommended Action Either reconfigure the receiving port VLAN ID to the same VLAN ID of the peer port, or reconfigure the peer port VLAN ID to the same VLAN ID of the receiving port.
SPANNTREE-2: Block [dec]/[chars] on rcving vlan [dec] for inc trunk port.Explanation This message indicates that the system is blocking the port from receiving traffic on the receiving VLAN, where [dec] is the module number, [chars] is the port number, and the second [dec] is the VLAN number. This prevents traffic looping, which might be caused by the peer port type inconsistency. The port is set to type-inconsistent state.
Recommended Action Either reconfigure the receiving port VLAN ID to the same VLAN ID of the peer port, or reconfigure the peer port VLAN ID to the same VLAN ID as the receiving port VLAN ID.
SPANTREE-2: Block [dec]/[chars] on xmtting vlan [dec] for inc peer vlan.Explanation This message indicates that the system is blocking the port from receiving traffic from the transmitting VLAN by the BPDU, where [dec] is the module number, [chars] is the port number, and the second [dec] is the VLAN number. This prevents traffic looping, which might be caused by the peer port VLAN inconsistency. The port is set to pvid-inconsistent state.
Recommended Action Either reconfigure the receiving port VLAN ID to the same VLAN ID of the peer port, or reconfigure the peer port VLAN ID to the same VLAN ID as the receiving port. The port is set to pvide-inconsistent state.
SPANTREE-2: Block [dec]/[chars] on rcving vlan [dec] for inc peer vlan [dec].Explanation This message indicates that the system is blocking the port from receiving traffic on the receiving VLAN of the BPDU, where [dec] is the module number, [chars] is the port number, and the second [dec] is the VLAN number. This prevents traffic looping, which might be caused by the peer port VLAN inconsistency.
Recommended Action Either reconfigure the receiving port VLAN ID to the same VLAN ID of the peer port, or reconfigure the peer port VLAN ID to the same VLAN ID of the receiving port.
SPANTREE-2: Unblock previously inc port [dec]/[chars] on vlan [dec].Explanation This message indicates that the previously blocked port caused by port type or VLAN inconsistency is now unblocked, where [dec] is the module number, [chars] is the port number, and the second [dec] is the VLAN number. This also indicates that the previous inconsistency has been cleared and no more inconsistencies have been detected on the port.
Recommended Action The port should have a normal spantree state.
SPANTREE-4: Uplinkfast unable to register Ibipc port.Explanation This message indicates that the Uplinkfast feature might not work with some Gigabit Ethernet modules.
Recommended Action Contact your technical service representative
SPANTREE-6: port [dec]/[chars] state in vlan [dec] changed to blocking.Explanation This message indicates the port [dec]/[chars] state in VLAN [dec] changed to blocking, where [dec]/[chars] is the [mod_num]/[port_num] and [dec] is the VLAN number.
Recommended Action This message is provided for information only.
SPANTREE-6: port [dec]/[chars] state in vlan [dec] changed to forwarding.Explanation This message indicates the port [dec]/[chars] state in VLAN [dec] changed to forwarding, where [dec]/[chars] is the [mod_num]/[port_num] and [dec] is the VLAN number.
Recommended Action This message is provided for information only.
SPANTREE-6: trcrf [dec] in trbrf [dec] changed to blocking.Explanation This message indicates that the TRCRF port corresponding to the TRBRF VLAN has changed to blocking, where trcrf [dec] is the TRCRF port number and trbrf [dec] is the TRBRF VLAN number.
Recommended Action This message is provided for information only.
SPANTREE-6: trcrf [dec] in trbrf [dec] changed to forwarding.Explanation This message indicates that the TRCRF port corresponding to the TRBRF VLAN has changed to forwarding, where trcrf [dec] is the TRCRF port number and trbrf [dec] is the TRBRF VLAN number.
Recommended Action This message is provided for information only.
SPANTREE-6: port [dec]/[chars] state in vlan [dec] changed to Listening.Explanation This message indicates that the port [dec]/[chars] in vlan [dec] state has changed to listening, where [dec]/[chars] is the [mod_num]/[port_num] and [dec] is the VLAN number.
Recommended Action This message is provided for information only.
SPANTREE-6: port [dec]/[chars] state in vlan [dec] changed to Learning.Explanation This message indicates that the port [dec]/[chars] in VLAN [dec] state has changed to learning, where [dec]/[chars] is the [mod_num]/[port_num] and [dec] is the VLAN number.
Recommended Action This message is provided for information only.
SPANTREE-6: port [dec]/[chars] in vlan [dec] moved to Fwding (UplinkFast).Explanation This message indicates that the port [dec]/[chars] in vlan [dec] has directly moved to the forwarding state via the UplinkFast feature, where [dec]/[chars] is the [mod_num]/[port_num] and [dec] is the VLAN number.
Recommended Action This message is provided for information only.
SPANTREE-6: Received inferior BPDU on port [dec]/[chars] in vlan [dec].Explanation This message indicates that the port is receiving BPDUs, where [dec]/[chars] is the [mod_num]/[port_num] and [dec] is the VLAN number. This indicates that the designated switch has lost connectivity to the root switch. This message appears only if you enable the BackboneFast feature.
Recommended Action This message is provided for information only.
SPANTREE-6: Received RLQ request PDU on port [dec]/[chars] in vlan [dec].Explanation This message indicates that the BackboneFast feature is attempting to fast converge, which means that a link has failed somewhere in the network, most likely at port [dec]/[chars] in vlan [dec], where [dec]/[chars] is the [mod_num]/[port_num] and vlan [dec] is the VLAN number.
Recommended Action This message is provided for information only.
SPANTREE-6: Received RLQ response PDU on port [dec/chars] in vlan [dec].Explanation This message indicates that the BackboneFast feature is attempting to fast converge, which means that a link has failed somewhere in the network, most likely at port [dec]/[chars] in vlan [dec], where [dec]/[chars] is the [mod_num]/[port_num] and vlan [dec] is the VLAN number.
Recommended Action This message is provided for information only.
SPANTREE-6: Msg Age timer expired on port [dec/chars] in vlan [dec].Explanation This message indicates that a BPDU was not received by the port for 20 seconds (assuming a default value of max_age), where [dec]/[chars] designates the port, and [dec] is the VLAN number. The port is made a designated port.
Recommended Action An occasional message of this type is acceptable, however if multiple errors occur within a short period of time for a specific VLAN, a fault is indicated. Since this message is per VLAN, multiple messages for different VLANS are normal. Contact your technical support representative.
This section contains the Catalyst 5000 series switch Terminal Access Controller Access Control System (TACACS) messages.
TAC-2: No TACACS server definedExplanation This message indicates a TACACS server was not defined.
Recommended Action Define a TACACS server. If this message reappears, contact your technical support representative.
TAC-7: Error sending continue packet.Explanation This message indicates that the system is unable to send TACACS packets to the server.
Recommended Action Verify the TACACS server is online. If not, bring the TACACS server online. If the TACACS server is online, contact your technical support representative.
TAC-7: Address not configured as a ServerExplanation This message appears during debugging only and indicates the TACACS address is not configured as a server.
Recommended Action Configure the TACACS address as a TACACS server.
TAC-7: Socket creation errorExplanation This message appears during debugging only and indicates a bad network connection error occurred.
Recommended Action Retry the connection. If this message reappears, perform these steps, retrying the connection after each step:
Step 1 Check the interface setup. If the interface is bad, reconfigure the interface setup and retry the connection; if the interface is good, proceed to the next step.
Step 2 Check the network connection. If the connection is bad, repair it. If the connection is good, contact your technical support representative.
Step 3 Check server operation; if the server is bad, contact your technical support representative. If the server is good, contact your technical support representative.
TAC-7: Socket connection error to [integer]Explanation This message appears during debugging only; it indicates a bad network connection error occurred to [integer], where [integer] is the server address.
Recommended Action Retry the connection. If this message reappears, perform these steps, retrying the connection after each step:
Step 1 Check the interface setup. If the interface is bad, reconfigure the interface setup and retry the connection; if the interface is good, proceed to the next step.
Step 2 Check the network connection. If the connection is bad, repair it. If the connection is good, contact your technical support representative.
Step 3 Check server operation; if the server is bad, contact your technical support representative. If the server is good, contact your technical support representative.
TAC-7: Received unsane data from server.
Explanation This message appears during debugging only; it indicates data received from the server is not recognized.
Recommended Action Retry connection. If this message reappears, contact your technical support representative.
TAC-7: decrypt: no key for encrypted pakExplanation This message appears during debugging only; it indicates the packet is encrypted but a key is not available.
Recommended Action Configure the correct key.
TAC-7: decrypt: pak is unencrypted but we have a keyExplanation This message appears during debugging only; it indicates the packet is unencrypted but a key is available.
Recommended Action Remove the key.
TAC-7: Received pak with bad version.Explanation This message appears during debugging only; it indicates a packet with a bad version was received.
Recommended Action Check the version of server software; upgrade if necessary.
TAC-7: Received pak with bad session id.Explanation This message appears during debugging only; it indicates a packet with a bad session ID was received.
Recommended Action Retry operation. If this message reappears, contact your technical support representative.
TAC-7: Received bad pak: length = [dec]Explanation This message appears during debugging only; it indicates a bad packet was received, where the length = [dec] is the bad packet length.
Recommended Action Retry operation. If this message reappears, contact your technical support representative.
TAC-7: Received bad pak: length = [dec], expected [dec]Explanation This message appears during debugging only; it indicates a bad packet was received, where the length = [dec] is the bad packet length, and the second [dec] is the expected length.
Recommended Action Retry operation. If this message reappears, contact your technical support representative.
This section contains the Catalyst 5000 series switch VTP messages.
VTP-2: LLC couldn't parse received vtp packet.Explanation This message indicates an internal error in logical link control.
Recommended Action Contact your technical support representative.
VTP-4: domain [chars] not foundExplanation This message indicates domain [chars] cannot be found, where [chars] is the domain name.
Recommended Action Contact your technical support representative.
VTP-4: Cannot configure a VLAN in client modeExplanation This message indicates that you are trying to configure a VLAN in client mode, which is unacceptable.
Recommended Action This message is intended as an informational warning only.
VTP-4: Database for domain [chars] locked, giving up.Explanation This message indicates the database for domain [chars] is locked, where [chars] is the domain name, and will not permit entry.
Recommended Action Contact your technical support representative.
VTP-4: vlan [dec] not found (mode = [dec])Explanation This message indicates that the VLAN cannot be found while trying to modify or delete it, where vlan [dec] is the VLAN number and mode= [dec] is the mode value.
Recommended Action This message is intended as an informational warning only.
VTP-6: VLAN [dec] [chars]edExplanation This message indicates that VLAN [dec] is [chars]ed, where [dec] is the VLAN number, and [chars]ed is added, modified, or deleted.
Recommended Action This message is provided for information only.
VTP-6: Domain [chars] modifiedExplanation This message indicates domain [chars] was modified, where [chars] is the domain name.
Recommended Action This message is provided for information only.
This section contains the Catalyst 5000 series switch VTP pruning messages.
PRUNING-2: semaphore (hex) not null at vtp_initialization!Explanation This message indicates an internal error, where [hex] is the semaphore value.
Recommended Action Contact your technical support representative.
PRUNING-2: no vlan string for trunk [dec]/[dec] ([chars])Explanation This message indicates an internal error, where [dec]/[dec] is the trunk [mod_num]/[port_num] and [chars] is the domain name.
Recommended Action Contact your technical support representative.
PRUNING-2: FATAL- inv vlan [dec] status [hex]Explanation This message indicates an internal error, where [dec] is the VLAN number and [hex] is the status value.
Recommended Action Contact your technical support representative.
PRUNING-2: SCP failed to write LTL on module [dec]Explanation This message indicates an internal error for the module [dec].
Recommended Action Contact your technical support representative.
PRUNING-2: update: lost trunk [dec]/[dec]([dec]) vlan [dec] state [dec]Explanation This message indicates that the attempt to save the VLAN spanning state change on the trunk was lost while updating, where [dec] / [dec]([dec]) is the [mod_num]/[port_num] ([port_num stored internally]); vlan [dec] is the VLAN number, and state [dec] is the lost spanning-tree state (0=disabled, 1=listening, 2=learning, 3=forwarding, 4=blocking).
Recommended Action Contact your technical support representative.
PRUNING-2: set: lost trunk [dec]/[dec]([dec]) vlan [dec] state [dec]Explanation This message indicates that the attempt to save the VLAN spanning state change on the trunk was lost while setting, where [dec] / [dec]([dec]) is the [mod_num]/[port_num] ([port_num stored internally]); vlan [dec] is the VLAN number, and state [dec] is the lost spanning-tree state (0=disabled, 1=listening, 2=learning, 3=forwarding, 4=blocking).
Recommended Action Contact your technical support representative.
PRUNING-2: vlan state change: can't find trunk (index=[hex])Explanation This message indicates the trunk could not be found while the VLAN pruning state changed, where [hex] is the index for the lost trunk.
Recommended Action Contact your technical support representative.
PRUNING-3: SCP send error: [chars] [dec]Explanation This message indicates an internal error when the supervisor engine communicates with the module(s), where [chars] is the last logged debug message and [dec] is the last logged debug value.
Recommended Action Contact your technical support representative.
PRUNING-3: no memory to build trunk [dec]/[dec] info for dependent codeExplanation This message indicates no system memory is available and the internal status for trunk [dec]/[dec] will be lost.
Recommended Action Upgrade the system memory (RAM) size.
PRUNING-3: Join rx on trunk [chars]-invalid first vlan: [dec]Explanation This message indicates some other VTP device has internal errors, where [chars] is the trunk [mod_num]/[port_num] and [dec] is the invalid first VLAN number.
Recommended Action Locate the VTP device with the internal error. Disable and then enable the trunk port. If the message reappears, contact your technical support representative.
PRUNING-3: Join rx on trunk [chars]-invalid last vlan: [dec]Explanation This message indicates some other VTP device has internal errors, where [chars] is the trunk [mod_num]/[port_num] and [dec] is the invalid last VLAN number.
Recommended Action Locate the VTP device with the internal error. Disable and then enable the trunk port. If the message reappears, contact your technical support representative.
PRUNING-3: Join rx on trunk [chars]-invalid len: [dec] ([dec])Explanation This message indicates some other VTP device has internal errors, where [chars] is the trunk [mod_num]/[port_num], [dec] is the number of the actual packet length, and ([dec]) is the valid packet length.
Recommended Action Locate the VTP device with the internal error. Disable and then enable the trunk port. If the message reappears, contact your technical support representative.
PRUNING-3: rx summary on trunk [chars] with invalid TLV value:[hex]Explanation This message indicates some other VTP device has internal errors, where [chars] is the trunk [mod_num]/[port_num] and [hex] is the invalid value.
Recommended Action Locate the VTP device with the internal error. Disable and then enable the trunk port. If the message reappears, contact your technical support representative.
PRUNING-4: domain [chars]([dec]) not foundExplanation This message indicates an intermediate configuration mismatch, but will recover, where [chars] is the domain name and ([dec]) is the domain name length.
Recommended Action Contact your technical support representative if the message appears repeatedly.
PRUNING-4: trunk [dec]/[dec] not found ([chars])
Explanation This message indicates an intermediate error occurred and VTP pruning might or might not work on that trunk, where [dec]/[dec] is the trunk
[mod_num]/[port_num] and ([chars]) is the domain name.
Recommended Action Enter the show trunk command to verify VTP pruning is working for that trunk. If it is not working, disable and then enable the trunk port. If the message reappears, contact your technical support representative.
PRUNING-4: invalid SPT state: [hex]Explanation This message indicates an intermediate spanning-tree (SPT) error occurred and VTP pruning might or might not work on that trunk, where [hex] could be one of the following:
invalid link state: link state valuevlan [vlan no] not found [domain name]invalid SPT state: [spt state value]Recommended Action Enter the show trunk command to verify VTP pruning is working for that trunk. If it is not working, disable and then enable the trunk port. If the message reappears, contact your technical support representative.
PRUNING-4: invalid vlan local assoc: [hex] ([chars])Explanation This message indicates an intermediate error has occurred and VTP pruning might or might not work on that trunk, where [hex] is the VLAN local association value and ([chars]) is the domain name.
Recommended Action Enter the show trunk command to verify VTP pruning is working for that trunk. If it is not working, disable and then enable the trunk port. If the message reappears, contact your technical support representative.
PRUNING-4: no mbuf to build joinExplanation This message indicates no buffer memory is available for VTP pruning.
Recommended Action Contact your technical support representative.
PRUNING-4: lost vlan local assoc event (vlan=[dec],assoc=[dec])Explanation This message indicates an internal event lost due to insufficient buffer memory, where vlan=[dec] is the VLAN number and assoc=[dec] is the local association status.
Recommended Action No action needs to be taken, recovery is automatic.
PRUNING-4: lost spt state event (trunk=[dec]/[dec],vlan=[dec],state=[dec])Explanation This message indicates an internal event lost due to insufficient buffer memory, where trunk=[dec]/[dec] is the [mod_num/port_num], vlan=[dec] is the VLAN number, and state=[dec] is the SPT status.
Recommended Action No action needs to be taken, recovery is automatic.
PRUNING-4: invalid pruning mode: [hex]Explanation This message indicates an intermediate error occurred and VTP pruning may or may not work on that trunk, where [hex] is the pruning mode value.
Recommended Action Disable and then enable the trunk port. If the message reappears, contact your technical support representative.
PRUNING-4: vlan [dec] not found ([chars])Explanation This message indicates that VLAN [dec] was not found, where [dec] is the VLAN number and ([chars]) is the domain name.
Recommended Action Contact your technical support representative.
PRUNING-4: invalid link state: [hex]Explanation This message indicates a trunk link is set to an invalid state, where [hex] is the invalid state value.
Recommended Action Contact your technical support representative.
PRUNING-5: no domain name in rx Join (trunk [dec]/[dec])Explanation This message indicates some other VTP device may have internal errors, where trunk=[dec]/[dec] is the [mod_num]/[port_num].
Recommended Action Check other VTP device(s) for internal errors. If no errors are found, contact your technical support representative.
PRUNING-5: domain [chars] not found in rx Join (trunk [dec]/[dec])Explanation This message indicates some other VTP device is assigned to a different domain, where [chars] is the domain name and trunk=[dec]/[dec] is the [mod_num]/[port_num].
Recommended Action Check other VTP device(s) assigned to a different domain. Enter the clear config all command for that device(s), and then assign the correct domain name.
PRUNING-5: trunk [dec]/[dec] not found for rx JoinExplanation This message indicates an intermediate error, where trunk=[dec]/[dec] is the [mod_num]/[port_num].
Recommended Action No action is required.
PRUNING-5: rx Join on trunk [dec]/[dec] when pruning disabledExplanation This message indicates VTP inconsistency exists in the network, where trunk=[dec]/[dec] is the [mod_num]/[port_num].
Recommended Action Check other devices to find out where the inconsistency exists and correct.
PRUNING-5: bogus timeout for trunk [chars]Explanation This message indicates an internal notification occurred on trunk=[chars], where [chars] is the [mod_num/port_num].
Recommended Action No action is required.
PRUNING-5: Joined-trunk [dec]/[dec] vlan [dec]Explanation This message indicates the VLAN on the trunk is not pruned, where [dec]/[dec] is the [mod_num]/[port_num] and vlan [dec] is the VLAN number.
Recommended Action This message is provided for information only.
PRUNING-5: Pruned-trunk [dec]/[dec] vlan [dec]Explanation This message indicates the VLAN on the trunk is pruned, where [dec]/[dec] is the [mod_num]/[port_num] and vlan [dec] is the VLAN number.
Recommended Action This message is provided for information only.
PRUNING-5: recover from spt event loss for trunk [dec]/[dec]Explanation This message indicates the software recovers automatically from an internal event loss, where [dec]/[dec] is the [mod_num]/[port_num].
Recommended Action This message is provided for information only.
PRUNING-5: Recover from local assoc event lossExplanation This message indicates the software recovers automatically from an internal event loss.
Recommended Action This message is provided for information only.
PRUNING-5: learn domain [chars] from networkExplanation This message indicates the VTP domain is learned from another VTP device, where [chars] is the domain name.
Recommended Action This message is provided for information only.
PRUNING-5: change [chars] pruning mode to [chars]Explanation This message indicates a change to the VTP pruning mode, where the first [chars] is the domain name and the second [chars] is enabled or disabled.
Recommended Action This message is provided for information only.
PRUNING-6: T[chars],V[dec]:st=[chars],event=[chars],new st=[chars]Explanation This message indicates the state change of a VLAN on a trunk, where the following applies:
T[chars] is Trunk [mod_num/port_num].V[dec] is the VLAN [vlan_id].st=[chars] is the current state [state], where [chars] could be Null, Disable, NoPrune, Joined, or Pruned.
event=[chars] is the event [event], where [event] could be: Null, RxVer1, RxJ1, RxJ0, Fwd, NonFwd, Tick, Tmo, LnkDn, LnkUp, Inelig, Eligi, Trans, NoTran, AddTrk, or Refrsh.
new st=[chars] is the new state [state], where [state] can be: Null, Disable, NoPrune, Joined, or Pruned.
Recommended Action This message is provided for information only.
PRUNING-6: trunk [chars]- send trig JoinExplanation This message indicates a VTP pruning message is triggered on the trunk due to a VLAN status change, where [chars] is the [mod_num/port_num].
Recommended Action This message is provided for information only.
This section contains the Catalyst 5000 series switch VMPS messages.
VMPS-2: PARSER: Invalid File Format, syntax error at line [dec]Explanation This message indicates a syntax error exists at line number [dec] in the configuration file, where [dec] is the line number in the configuration file.
Recommended Action Correct the error in the configuration file. If the message reappears, contact your technical support representative.
VMPS-2: PARSER: [dec] lines parsed, Errors [dec]Explanation This message indicates that the VMPS parsed a [dec] number of lines in the configuration file and found [dec] errors, where [dec] lines are the number of lines parsed and Errors [dec] are the number of errors found.
Recommended Action Correct the error in the configuration file. If the message reappears, contact your technical support representative.
VMPS-2: Out of memoryExplanation This message indicates insufficient DRAM to load the VMPS configuration database.
Recommended Action Increase the DRAM on the supervisor engine. If the message reappears, contact your technical support representative.
VMPS-2: Failed to create taskExplanation This message indicates the number of processes in the system reached the maximum limit.
Recommended Action Contact your technical support representative.
VMPS-2: Failed to create socketExplanation This message indicates insufficient system resources.
Recommended Action Contact your technical support representative.
VMPS-2: Failed to bind socketExplanation This message indicates insufficient system resources.
Recommended Action Contact your technical support representative.
VMPS-2: Another download in progress, try laterExplanation This message indicates another download process is currently in progress.
Recommended Action Try to download after the other process completes. If this message reappears, contact your technical support representative.
VMPS-2: Unable to download file [chars]Explanation This message indicates either the TFTP server is not online or the file does not exist on the server, where [chars] is the VMPS filename.
Recommended Action Make sure the server is online and the filename and the pathname are correct and exist on the server. If any of these conditions have not been met, correct and put in place. If correct and in place, contact your technical support representative.
VMPS-2: Insufficient resources to build databaseExplanation This message indicates there is not enough DRAM to load the VMPS configuration database.
Recommended Action Increase the DRAM on the supervisor engine. If this message reappears, contact your technical support representative.
VMPS-2: Management Domain not defined in configuration fileExplanation This message indicates the management domain is not defined in the configuration file.
Recommended Action Configure the management domain name in the configuration file. If this message reappears, contact your technical support representative.
VMPS-2: VMPS Enable FailedExplanation This message indicates the attempt to enable VMPS failed.
Recommended Action This message is provided for information only.
VMPS-2: VMPS is using the previous configurationExplanation This message indicates VMPS is using a previous configuration.
Recommended Action This message is provided for information only.
VMPS-2: Download Failed. VMPS is now inactiveExplanation This message indicates the attempt to download failed and VMPS is inactive.
Recommended Action This message is provided for information only.
VMPS-3: PARSER: Invalid no. of args at line [dec]Explanation This message indicates a parsing error in the configuration file, where [dec] is the line number in the configuration file.
Recommended Action Correct the error in the configuration file.
VMPS-3: PARSER: Unknown keyword [chars] at line [dec]Explanation This message indicates an unknown keyword [chars] exists at line number [dec] in the configuration file, where [chars] is the keyword and [dec] is the line number in the configuration file.
Recommended Action Correct the error in the configuration file. If this message reappears, contact your technical support representative.
VMPS-3: PARSER: Invalid syntax at line [dec]Explanation This message indicates an invalid syntax exists at line [dec] in the configuration file, where [dec] is the line number in the configuration file.
Recommended Action Correct the error in the configuration file. If this message reappears, contact your technical support representative.
VMPS-3: PARSER: Invalid IP addr [chars] at line [dec]Explanation This message indicates an invalid IP address [chars] at line [dec] exists in the configuration file, where [chars] is the IP address and [dec] is the line number in the configuration file.
Recommended Action Correct the error in the configuration file. If this message reappears, contact your technical support representative.
VMPS-3: PARSER: Invalid VLAN [chars] at line [dec]Explanation This message indicates an invalid VLAN [chars] at line [dec] exists in the configuration file, where [chars] is the VLAN number and [dec] is the line number in the configuration file.
Recommended Action Correct the error in the configuration file. If this message reappears, contact your technical support representative.
VMPS-3: PARSER: Invalid MAC addr [chars] at line [dec]Explanation This message indicates an invalid MAC address [chars] at line [dec] exists in the configuration file, where [chars] is the MAC address and [dec] is the line number in the configuration file.
Recommended Action Correct the error in the configuration file. If this message reappears, contact your technical support representative.
VMPS-3: PARSER: Unknown VLAN group [chars] at line [dec]Explanation This message indicates an unknown VLAN group [chars] at line [dec] exists in the configuration file, where [chars] is the VLAN group number and [dec] is the line number in the configuration file.
Recommended Action Correct the error in the configuration file. If this message reappears, contact your technical support representative.
VMPS-3: PARSER: Unknown port group [chars] at line [dec]Explanation This message indicates an unknown port group [chars] at line [dec] exists in the configuration file, where [chars] is the port group number and [dec] is the line number in the configuration file.
Recommended Action Correct the error in the configuration file. If this message reappears, contact your technical support representative.
VMPS-7: Invalid version 0x[hex] in packetExplanation This message appears during debugging only and indicates the server is running an older version of VMPS, where 0x[hex] is the version the client is running.
Recommended Action Upgrade the server to a newer version.
VMPS-7: Invalid opcode 0x[hex] in packetExplanation This message appears during debugging only and indicates the server received an invalid request from the client, where 0x[hex] is the invalid request number.
Recommended Action Contact your technical support representative.
VMPS-7: Invalid length [dec] for IP addressExplanation This message appears during debugging only and indicates the server received an invalid request from the client, where [dec] is the length of invalid data in the request.
Recommended Action Contact your technical support representative.
VMPS-7: Invalid TLV type 0x[hex]Explanation This message appears during debugging only and indicates the server received an invalid request from the client, where 0x[hex] is the invalid data in the request.
Recommended Action Contact your technical support representative.
Posted: Wed Aug 11 11:30:04 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.