cc/td/doc/product/lan/cat6000/sw_5_5
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Messages and Recovery Procedures

Messages and Recovery Procedures

This chapter lists the 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.


Note The messages listed in this chapter do not include the date/time stamp designation; the date/time stamp designation is displayed only if the software is configured for system log messaging.

ACL Messages

This section contains the Access Control Lists (ACL) messages.

ACL-2

ACL-2-TASKFAIL: ACL task exits

    Explanation   This message indicates that the ACL task cannot be created, so no security or QoS functions are available.

    Action Contact your technical support representative.

ACL-3

ACL-3-PVLAN_ADDPVLANFAIL: ACL-PVLAN inconsistency: a router ACL is mapped to secondary dynamic ACEs or policy routing are mapped to private VLAN, VLAN concerned:[dec] [dec]

    Explanation   This message is displayed when an existing VLAN becomes a secondary VLAN and there was a RACL or dynamic ACE mapped to the existijng VLAN, or if the primary VLAN has a policy routing ACL configured. [dec] [dec] are the primary and secondary VLAN numbers.

    Action Try setting the PVLAN to a regular VLAN.

ACL-3-PVLAN_ATTACHACLFAIL: Router ACLs cannot be mapped to secondary VLANs, dynamic ACEs and policy routing ACLs cannot be mapped to private VLANs, VLAN concerned is [dec]

    Explanation   This message is displayed when the router tries to download a RACL or dynamic ACEs on an existing secondary VLAN, or when a policy routing ACL is configured on a primary VLAN. [dec] is the VLAN number.

    Action Remove the ACL mapping from the specified VLAN.

ACL-3-PVLAN_DELETEACLFAIL: Removing router ACLs from secondary vlan [dec] not allowed

    Explanation   This message indicates that an attempt was made to remove router ACLs from a secondary VLAN. [dec] is the secondary VLAN number.

    Action This message is provided for information only.

ACL-3-PVLAN_PGATEDFLTACTION: Failed to propogate *router default action* to secondary to VLAN [dec]

    Explanation   This message indicats that the router set a default action on a primary VLAN, but this action did not get sent to the secondary VLANs. [dec] is the secondary VLAN number.

    Action Contact your technical support representative.

ACL-3-PVLAN_PGATEDTACLFAIL: Failed to propogate *router delete ACL* to secondary VLAN [dec]

    Explanation   This message is displayed when a delete operation on a primary VLAN doesn't succeed in removing the mapping of the same ACL from the secondary VLANs. [dec] is the secondary VLAN number.

    Action Contact your technical support representative.

ACL-3-PVLAN_PGATEMAPFAIL: Failed to propogate *route ACL map* to secondary VLAN [dec]

    Explanation   This message indicates that a RACL downloaded to a primary VLAN did not get propogated to the secondary VLANs. [dec] is the secondary VLAN number.

    Action Contact your technical support representative.

ACL-3-PVLAN_SETDFLTFAIL: Default action cannot be set on secondary vlan [dec]

    Explanation   This message is displayed when the router tries to set a default action on a secondary VLAN. [dec] is the secondary VLAN number.

    Action Contact your technical support representative.

ACL-3-VACLACLCOMMITFAIL: Failed to commit Security ACL [chars]

    Explanation   This message indicates that the Access Control List (ACL) was not committed to the hardware; [chars] is the name of the Access Control List.

    Action This message is provided for information only.

ACL-3-VACLACLNVRAMFAIL: Failed to commit Security ACL [chars] to NVRAM

    Explanation   This message indicates that the NVRAM and hardware are not working together. The ACL configuration was saved to the hardware but was not saved to NVRAM; [chars] is the name of the Access Control List.

    Action Either move the ACL configuration to Flash or create space in NVRAM and commit again. Contact your technical support representative.

ACL-3-VACLMAPCOMMITFAIL: Failed to Map Security ACL [chars] to Vlan [dec]

    Explanation   This message indicates that the mapping between the ACL and the VLAN has failed; [chars] is the Access Control List name and [dec] is the VLAN name.

    Action Contact your technical support representative.

ACL-5

ACL-5-NOLABEL: acl engine is out of label

    Explanation   This message indicates that the hardware cannot map ACL to the VLAN or to the port.

    Action Reduce the ACL to VLAN or port mapping or contact your technical support representative.

ACL-5-NOLOU: acl engine is out of logical operation unit

    Explanation   This message indicates that the hardware is out of logical operation units, which process the TCP/UDP port number operations.

    Action Reduce the number of different kinds of operations being run or contact your technical support representative.

ACL-5-RACLCONFLICTLDA: RACL conflicts with LDA on Vlan [dec]

    Explanation   This message indicates that the you are trying to configure IOS ACL on a VLAN that has LocalDirector Acceleration (LDA) configured. The switch fails the IOS ACL configuration. Vlan [dec] is the VLAN number.

    Action Contact your technical support representative.

ACL-5-TCAMFULL: acl engine TCAM table is full

ACL-5-VACLFINISHRESTORE: Finished restoring Security ACL configuration to hardware

    Explanation   This message is printed after the ACL configuration has been restored to the hardware. Traffic on VLANs with ACLs mapped will follow the ACL configuration rules.

    Action This message is provided for information only.

ACL-5-VACLSTARTRESTORE: Restoring Security ACL configuration to hardware

    Explanation   This message is printed at start up to notify the user that the ACL configuration is being restored to hardware. All traffic through VLANs which have ACLs mapped to them are denied until the next message (VACLFINISHRESTORE) is printed.

    Action This message is provided for information only.

CDP Messages

This section contains the Cisco Discovery Protocol (CDP) messages.

CDP-3

CDP-3-SENDFAIL: Transmit failure on port [dec]/[dec]

    Explanation   This message indicates a transmit failure occurred on port [dec]/[dec]; [dec]/[dec] is the module number/port number.

    Action Contact your technical support representative.

CDP-4

CDP-4-DUPLEXMISMATCH: Full/half duplex mismatch detected on port [dec]/[dec]

    Explanation   This message indicates that the duplex configuration of an Ethernet port is different from the configuration set on at least one of the neighboring ports; [dec]/[dec] is the module number/port number.

    Action Check the duplex settings. If the duplex configuration does not match, set it appropriately. If no apparent mismatch is found, contact your technical support representative.

CDP-4-NVLANMISMATCH: Native vlan mismatch detected on port [dec]/[dec]

    Explanation   This message indicates that the native VLAN is different from the one set on at least one of the neighboring ports; [dec]/[dec] is the module number/port number of the offending port.

    Action Check the native VLAN settings. If the VLAN configuration does not match, set it appropriately. If no apparent mismatch is found, contact your technical support representative.

CDP-7

CDP-7-PACKETRX: Packet Reception detected on port [dec]/[dec]

    Explanation   This message indicates that a packet has been detected on a module port; [dec]/[dec] is the module number and port number.

    Action This message is provided for information only.

CDP-7-PACKETTX: Packet Transmission detected on port [dec]/[dec]

    Explanation   This message indicates that a packet has been transmitted from a module port; [dec]/[dec] is the module number and port number.

    Action This message is provided for information only.

CDP-7-PKTDROP: Packet dropped as CDP is disabled on port [dec]/[dec]

COPS Messages

This section contains the Common Open Policy Service (COPS) messages.

COPS-3

COPS-3-APPLY_CAT5K_FAIL_COSTODSCP: Applying COPS policy failed since invalid mapping of cos to dscp found in CosToDscpMappingTable

    Explanation   This message indicates that the switch received an invalid CosToDscpMappingTable from the PDP. The switch always rewrites the COS to the same value as the ipPrecedence (upper three bits of the DSCP) for the outbound packet.

    Action Contact your technical support representative.

COPS-3-APPLY_CAT5K_FAIL_DSCP: Applying COPS policy failed since policy DSCP not multiple of 8

    Explanation   This message indicates that the DSCP value received in the policy from the PDP contained a value that is not a multiple of 8. QOS only rewrites the ipPrecedence part (upper three bits of DSCP) of the TOS.

    Action Contact your technical support representative.

COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy range is not set to full range.

    Explanation   This message indicates that QOS cannot classify packets based on incoming DSCP values.

    Action Contact your technical support representative.

COPS-3-APPLY_CAT5K_FAIL_INVALIDDIRECTION: Applying COPS policy failed since policy received contains an invalid direction field

    Explanation   This message indicates that policy was received where the direction was not input-based. QOS only supports input-based classification.

    Action Contact your technical support representative.

COPS-3-APPLY_CAT5K_FAIL_NUMACES: Applying COPS policy failed since maximum allowed number of ACEs was exceeded

    Explanation   This message indicates that COPS policy failed because COPS for Catalyst 5000 fmily switch allows a maximum of 128 ACEs.

    Action Contact your technical support representative.

COPS-3-APPLY_CAT5K_FAIL_TRUSTACL: Applying COPS policy failed since policy contains TRUST service types

    Explanation   This message indicates that the COPS policy failed because QoS for the Catalyst 5000 family does not support trust.

    Action This message is provided for information only.

COPS-3-DS-CLIENT_INIT_FAILED: Failed to intialize DsClient, error status [dec]

    Explanation   This message indicates that the COPS DsClient failed to initialize; [dec] is the error message.

    Action Contact your technical support representative.

COPS-3-TTL_TIMER_MALLOC_FAILED: Malloc Failed for Pib Ttl Timer

    Explanation   This message indicates that the COPS DsClient could not allocate memory for one of its internal objects because of insufficient memory.

    Action Contact your technical support representative.

COPS-6

COPS-6-CONN_ATTEMPT_FAILED: Connection attempt to COPS server [chars] (port: [dec]) failed

    Explanation   This message indicates that the COPS Connection Manager failed to make a connection to the COPS server; [chars] is the IP address and [dec] is the port number.

    Action This message is provided for information only.

COPS-6-CONN_LOST: Connection to COPS server [chars] (port: [dec]) lost

    Explanation   This message indicates that the COPS Connection Manager lost its connection to the COPS server; [chars] is the IP address and [dec] is the port number.

    Action This message is provided for information only.

COPS-6-CONN_MADE: New Connection made to COPS server [chars] (port: [dec])

    Explanation   This message indicates that the COPS Connection Manager has made a new connection to the COPS server; [chars] is the IP address and [dec] is the port number.

    Action This message is provided for information only.

COPS-6-DS_CLIENT_EXITING: COS Ds Client Exiting

    Explanation   This message indicates that the COPS DsClient has completely shut down after being disabled from the command line interface.

    Action This message is provided for information only.

COPS-6-KA_TIMER_EXPIRED: Keep Alive timer expired for connection to COPS

    Explanation   This message indicates that the keepalive timer has expired. The COPS Connection Manager considers the connection to the COPS server broken and will try to reconnect to the server.

    Action This message is provided for information only.

COPS-6-TTL_TIMER_EXPIRED: Ttl Timer expired, reverting to NVRAM policy

DRIP Messages

This section contains the Dual Ring Protocol (DRiP) messages.

DRIP-3

DRIP-3-DRIPALRINIT: Drip Already Initialized

    Explanation   This message indicates that DRiP was previously enabled and initialized, and a software module requested a reinitialization of the database.

    Action Contact your technical support representative.

DRIP-3-DRIPALRSHUT: Drip Already Shutdown

    Explanation   This message indicates that DRiP was previously shut down, and a software module has requested another shutdown.

    Action Contact your technical support representative.

DRIP-3-DRIPCONFMAC2: LOC: [chars], REM: [chars]

    Explanation   This message precedes each DRiP-3 level conflict message (for example, Invalid Change Request. Status [hex]); the first [chars] is the MAC address for the local switch, and the second [chars] is the MAC address for the remote switch.

    Action This message is provided for information only.

DRIP-3-DRIPCOREERROR: 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.

    Action Execute the show drip statistics command and provide the information to your technical support representative.

DRIP-3-DRIPINVCHG: 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; [hex] is the status byte.

    Action Contact your technical support representative.

DRIP-3-DRIPNOLCLBOX: 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; [dec] is the VLAN number, and [chars] is the MAC address.

    Action Contact your technical support representative.

DRIP-3-DRIPNOMAC: 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; [chars] is the MAC address, and [dec] is the VLAN number.

    Action Contact your technical support representative.

DRIP-3-DRIPNOVLAN: 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; [dec] is the VLAN number, and [chars] is the switch name.

    Action Contact your technical support representative.

DRIP-3-DRIPOUTRANGE: Vlanid [dec] out of range. MAC [chars]

    Explanation   This message indicates the DRiP database received a request to enter a VLAN ID [dec] that is out of range; [dec] is the VLAN number, and [chars] is the MAC address.

    Action Document the VLAN ID and the MAC address, and contact your technical support representative.

DRIP-4

DRIP-4-DRIPCONFLICTACT: 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 Concentrator Relay Function (CRF) VLAN; [dec] is the VLAN number, and [hex] is the returned status. The DRiP database has an invalid status indication for this VLAN.

    Action Contact your technical support representative.

DRIP-4-DRIPCONFLICTCON: 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 CRF VLAN; [dec] is the VLAN number. Port assignments are allowed only on a single switch for this VLAN.

    Action Reassign ports for this VLAN only to one switch. If this message reappears, contact your technical support representative.

DRIP-4-DRIPCONFLICTCONACT: 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; [dec] is the VLAN ID number. Port assignments are allowed only on a single switch for this VLAN.

    Action Reassign ports for this VLAN to one switch. If this message reappears, contact your technical support representative.

DRIP-4-DRIPCONFMAC1: LOC: [chars], REM: [chars]

    Explanation   This message precedes each DRiP-4 level conflict message (for example, Configuration conflict on vlan [dec]); the first [chars] is the MAC address for the local switch, and the second [chars] is the MAC address for the remote switch.

    Action This message is provided for information only.

DRIP-5

DRIP-5-DRIPFAILSCP: SCP Failure

DTP Messages

This section contains the Dynamic Trunking Protocol (DTP) messages.

DTP-1

DTP-1-ILGLCFG: Illegal config (on, isl--on,dot1q) on Port [dec]/[dec]

    Explanation   This message indicates that one end of the trunk is configured as ON, ISL and the other end is configured ON, dot1Q; [dec]/[dec] is the module number/port number where the syslog message is printed.

    Action This is an illegal configuration and you must change the encapsulation type so that both ends of the trunk match.

DTP-3

DTP-3-NONTRUNKPORTFAIL: Port [dec]/[chars] failed to become non-trunk

    Explanation   This message indicates that the port [dec]/[chars] failed to become nontrunked; [dec]/[chars] is the module number/port range.

    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 Serial Communications Protocol (SCP); 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.


DTP-3-TRUNKPORTFAIL: Port [dec]/[chars] failed to become trunk

    Explanation   This message indicates that the port [dec]/[chars] failed to become trunked; [dec]/[chars] is the module number/port range.

    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 SCP; 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.


DTP-4

DTP-4-PKTQFULL: DTP internal queue dtpPktQ full

    Explanation   This message indicates that an overflow occurred in the DTP internal packet queue due to an abnormal condition.

    Action Contact your technical support representative.

DTP-5

DTP-5-NONTRUNKPORTON: Port [dec]/[chars] has become non-trunk

    Explanation   This message indicates the port [dec]/[chars] is nontrunked; [dec]/[chars] is the module number/port range.

    Action This message is provided for information only.

DTP-5-TRUNKPORTCHG: Port [dec]/[chars] has changed from [chars] trunk to [chars] trunk.

    Explanation   This message indicates that the encapsulation type of the trunk has changed. [dec] is the module number, the first [chars] is the port number, the second [chars] is the original encapsulation type, and the third [chars] is the new encapsulation type.

    Action This message is provided for information only.

DTP-5-TRUNKPORTON: Port [dec]/[chars] has become trunk

    Explanation   This message indicates that the port [dec]/[chars] is trunked; [dec]/[chars] is the module number/port range.

    Action This message is provided for information only.

DTP-7

DTP-7-MULTIDROP: Port [dec]/[dec] detected multiple neighbors.

    Explanation   This message indicates that a trunk has detected multiple neighbors (shared environment). DTP turns off trunking to that port; [dec]/[dec] is the module number/port number.

    Action No action is necessary if you want the port to be nontrunking.

DTP-7-NODTP: Port [dec]/[dec] not recd DTP packet for 5m.

    Explanation   This message indicates that the port [dec]/[dec] is nontrunking because it has not received any DTP packet from its neighbor port for 5 minutes; [dec][dec] is the module number/port number.

    Action Contact your technical support representative.

DTP-7-PORTLINKDOWN: Port [dec]/[chars] Link down

    Explanation   This message indicates that DTP detects a broken link for port [dec]/[chars]; [dec]/[chars] is the module number/port range.

    Action Contact your technical support representative.

DTP-7-PORTLINKUP: Port [dec]/[chars] Link up

    Explanation   This message indicates that DTP detects a link-up for port [dec]/[chars]; [dec]/[chars] is the module number/port range.

    Action Contact your technical support representative.

DTP-7-SYNCUPMSG: Port [dec]/[dec] recd [chars] from 2.2x4.4x

DVLAN Messages

This section contains the switch Dynamic VLAN (DVLAN) messages.

DVLAN-1

DVLAN-1-DENYHOST: Host [chars] denied on port [dec]/[chars]

    Explanation   This message indicates the VLAN Membership Policy Server (VMPS) sent a response to deny connectivity to the host; [chars] is the host's MAC address, and [dec]/[chars] is the module number/port range.

    Action Check the VMPS database to see why it is denied. If the database information is correct, contact your technical support representative.

DVLAN-1-DENYHOSTVLAN: Host [chars] denied on port [dec]/[chars] by inactive vlan

    Explanation   This message indicates the VLAN assigned by the VMPS is not active in the switch; [chars] is the host's MAC address, and [dec]/[chars] is the module number/port range.

    Action Make sure the VLAN is active and retry operation. If this message reappears, contact your technical support representative.

DVLAN-1-NOVMPS: VMPS address not configured

    Explanation   This message indicates that the VMPS server address has not been configured.

    Action Configure the VMPS server address. If this message reappears, contact your technical support representative.

DVLAN-1-SHUTDOWNPORT1: Port [dec]/[chars] shutdown by VMPS

    Explanation   This message indicates that the VMPS detects an unknown MAC address on port [dec]/[chars] and shuts down the port; [dec]/[chars] is the module number/port range.

    Action Remove the unknown host and enable the port. Retry operation. If this message reappears, contact your technical support representative.

DVLAN-1-SHUTDOWNPORT2: Port [dec]/[chars] shutdown by EARL failure

    Explanation   This message indicates that a dynamic Enhanced Address Recognition Logic (EARL) entry for a new host cannot be set in EARL because all four pages for the hashed index are full; [dec]/[chars] is the module number/port range.

    Action Enable the port and retry operation. If this message reappears, contact your technical support representative.

DVLAN-1-SHUTDOWNPORT3: Port [dec]/[chars] shutdown by active host limit

    Explanation   This message indicates that more than 50 active hosts are detected on a dynamic port; [dec]/[chars] is the module number/port range.

    Action Reduce the active hosts. Enable the port and retry operation. If this message reappears, contact your technical support representative.

DVLAN-2

DVLAN-2-VMPSUNREACHABLE: VMPS server [chars] is not responding

    Explanation   This message indicates that the VMPS server is not responding; [chars] is the IP address of the VMPS server not responding.

    Action Check the VMPS configuration and the network connection to the server.

DVLAN-3

DVLAN-3-BINDFAIL: Failed to bind DVLAN socket

    Explanation   This message indicates that a failure to bind DVLAN socket has occurred.

    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-DOMAININVALID: Invalid-Management-Domain opcode in response

    Explanation   This message indicates that the management domain name in the VMPS response does not match the VLAN Trunk Protocol (VTP) domain name set in the system.

    Action Correct the domain name either in the database or in the system.

DVLAN-3-NOCOOKIE: Response has no Cookie

    Explanation   This message indicates that the VMPS response has no Cookie.

    Action Check the VMPS server, and then contact your technical support representative.

DVLAN-3-NORESOURCE: No-Resource opcode in response

    Explanation   This message indicates that the VMPS responds with no-resource.

    Action Contact your technical support representative.

DVLAN-3-NOVLAN: Response has no VLAN ID

    Explanation   This message indicates that the VMPS response has no VLAN name.

    Action Check the VMPS server, and then contact your technical support representative.

DVLAN-3-RECEIVEFAIL: Failed (err = [dec]) to receive response from VMPS [chars]

    Explanation   This message indicates that a failure to receive a response from the VMPS has occurred; [dec] is the error number, and [chars] is the VMPS server address.

    Action Contact your technical support representative about the error number displayed in the message.

DVLAN-3-SENDFAIL: Failed (err = [dec]) to send query to VMPS [chars]

    Explanation   This message indicates that a failure to send a query to the VMPS has occurred; [dec] is the error number, and [chars] is the VMPS address.

    Action Contact your technical support representative about the error number displayed in the message.

DVLAN-3-SOCKFAIL: Failed to open socket for DVLAN

    Explanation   This message indicates that a failure to open a socket for DVLAN has occurred.

    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-TRAPDIAGFAIL: EARL trap diag failed on supervisor module

    Explanation   This message indicates that the EARL trap diagnostics have failed. If the EARL trap diagnostics have failed, you cannot set the ports to dynamic.

    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-TRAPUNSUPPORTED: EARL trap not supported in supervisor module

    Explanation   This message indicates that an older supervisor engine was installed (hardware version 1.3 or lower) that does not support the trap feature in EARL. You cannot set the ports to dynamic in these modules.

    Action Contact your technical support representative.

DVLAN-3-VERSIONINVALID: Invalid-Version opcode in response

    Explanation   This message indicates that the VMPS response has an invalid version number. The VMPS version should be 1.

    Action Contact your technical support representative.

DVLAN-3-VLANINVALID: Invalid VLAN ID ([chars]) in response

    Explanation   This message indicates that the VLAN name in the VMPS response is not available in the system; ([chars]) is the VLAN name.

    Action Contact your technical support representative.

DVLAN-4

DVLAN-4-NODYNPORT: No dynamic ports configured, reconfirm aborted

    Explanation   This message indicates that a reconfirm vmps command was executed, and no dynamic ports were configured.

    Action No action is necessary.

DVLAN-4-NOHOST: No host on dynamic ports, reconfirm aborted

    Explanation   This message indicates that the reconfirm vmps command was executed, and no active host is connected to the dynamic ports.

    Action No action is necessary.

DVLAN-6

DVLAN-6-MOVEDHOST: Host [chars] moved from static to dynamic port [dec]/[chars]

    Explanation   This message indicates that the host with the MAC address [chars] has moved from a static port to a dynamic port; [chars] is the host MAC address and [dec]/[chars] is the changed port module number/port number.

    Action This message is provided for information only.

DVLAN-7

DVLAN-7-ASSIGNVLAN: VLAN [dec] assigned to Port [dec]/[chars]

    Explanation   This message appears only during debugging. This message indicates that a VLAN was assigned to a dynamic port; [dec] is the VLAN number, and [dec]/[chars] is the module number/port range.

    Action No action is necessary.

DVLAN-7-PRIMARYVMPS: Primary VMPS [chars] is alive

EARL Messages

This section contains the Enhanced Address Recognition Logic (EARL) messages.

EARL-2

EARL-2-EARL2LOOKUPRAMERROR: Address [hex], data [hex]-[hex], count [dec]

    Explanation   This message indicates that a parity error has been detected; address [hex] is the lookup RAM location, data [hex]-[hex] is the error data, and count [dec] is the total error count.

    Action The system should recover from the error. If the error repeats frequently, contact your technical support representative.

EARL-2: EARL4LOOKUPRAMERROR: Address [hex], data [hex]-[hex]-[hex]-[hex], count [dec]

    Explanation   This message indicates that a look-up RAM parity error has been detected. The address [hex] field is the address in the forwarding table where the error was detected; the data [hex]-[hex]-[hex]-[hex] field is the word0, word1, word2, and word3 of RAM data that generated the parity error; and the count [dec] field is the total number of parity errors.

    Action Contact your technical support representative.

EARL-3

EARL-3-BADCOLOR: Bad color [dec] read from [hex] for a [chars] entry

    Explanation   This message indicates that the system has learned a MAC address on an invalid VLAN; [dec] is the VLAN number, [hex] is the location, and [chars] is either static or dynamic.

    Action This message is provided for information only.

EARL-3-DELETEVLANTIMER: Failure to remove timer [dec] from vlan [dec]

    Explanation   This message indicates that the EARL cannot remove the aging timer for this VLAN; timer [dec] is the timer number, and vlan [dec] is the VLAN number.

    Action Contact your technical support representative.

EARL-3-EARLDELETE: Earl delete error

    Explanation   An attempt to delete an EARL entry failed.

    Action Contact your technical support representative.

EARL-3-LTL: Failure to set LTL for module [dec]

    Explanation   This message indicates that the EARL cannot program the Local Targeting Logic (LTL) ASIC on the module; [dec] is the module number.

    Action Contact your technical support representative.

EARL-3-SETVLANTIMER: Failure to set timer [dec] from vlan [dec]

    Explanation   This message indicates that the EARL cannot set the aging timer for this VLAN; timer [dec] is the timer number, and vlan [dec] is the VLAN number.

    Action Contact your technical support representative.

EARL-5

EARL-5-FDDI: Failed to send CAM message to FDDI module [dec]

FILESYS Messages

This section contains the Flash file system (FILESYS) messages.

FILESYS-1

FILESYS-1-BT_REFMT: Bootflash size mismatch with file system

    Explanation   This message indicates that there was a boot flash file system configuration error.

    Action Format the boot flash.

FILESYS-1-PC_INSERT: PCMCIA flash card inserted into [chars]

    Explanation   This message indicates that a Flash PC card was inserted into [chars]; [chars] could be slot0 or slot1.

    Action This message is provided for information only.

FILESYS-1-PC_REMOVE: PCMCIA flash card removed from [chars]

    Explanation   This message indicates that a Flash PC card was removed from [chars]; [chars] could be slot0 or slot1.

    Action This message is provided for information only.

FILESYS-1-PCMCIA_INSERT: PCMCIA flash card inserted in [chars]

    Explanation   This message indicates that a Flash PC card was inserted into [chars]; [chars] could be slot0 or slot1.

    Action This message is provided for information only.

FILESYS-1-PCMCIA_REMOVE: PCMCIA flash card removed from [chars]

GVRP Messages

This section lists the GARP VLAN Registration Protocol (GVRP) messages.

GVRP-0

GVRP-0-NOMBUF: no mbuf to [chars]

    Explanation   This message indicates that GVRP failed to notify VTP when a VLAN was created or deleted. The problem occurred when VTP ran out of message buffer space; [chars] indicates the message body.

    Action Try reinitializing the VTP configuration by toggling between VTP server mode and transparent mode. If the problem persists, you might need to reset or power cycle the switch.

GVRP-2

GVRP-2-DISABLEDYNVLANCREATE: Disable dynamic VLAN creation temporarily since non-dot1q or non-GVRP trunk [dec]/[dec] exists

    Explanation   This message indicates that there is at least one non-dot1q or non-GVRP trunk existing on the switch. GVRP will temporarily disable the dynamic VLAN creation, even though the dynamic VLAN creation is configured as enabled; [dec]/[dec] is the first non-dot1q trunk module/port detected by GVRP.

    Action You should either disable dynamic VLAN creation or configure all trunk ports to dot1q.

GVRP-2-RESUMEDYNVLANCREATE: Resume dynamic vlan creation since the last non-dot1q or non-GVRP trunk [dec]/[dec] is removed

    Explanation   This message indicates that GVRP detects that all trunk ports are dot1q or GVRP. GVRP resumes dynamic VLAN creation if dynamic VLAN creation is enabled on the switch; [dec]/[dec] is the last disappearing non-dot1q trunk module and port detected by GVRP.

    Action This message is provided for information only.

GVRP-3

GVRP-3-CREATEPROCESSFAILED: failed to create GVRP process

    Explanation   This message indicates that the GVRP process was not completed successfully when the system was initialized or the GVRP was set to enabled. The switch may have encountered resource allocation problems.

    Action You should disable GVRP on the switch, and then retry it later when the system is more stable. If the problem recurs, you might need to reset or power cycle the switch.

GVRP-3-CREATEVLANNONETHERNET: can not create non-Ethernet VLAN [dec]

    Explanation   This message indicates that a received GVRP join message contains a new VLAN number that is not an Ethernet VLAN currently existing on the switch; [dec] is the non-Ethernet VLAN number.

    Action You must either reassign the VLAN number to an Ethernet, or correct the VLAN configuration on the peer side of the GVRP device for VLAN consistency.

GVRP-3-CREATEVLANNOTALLOWED: dynamically adding VLAN [dec] not allowed

    Explanation   This message indicates that a received GVRP join message contains a new VLAN number that is not allowed because dynamic VLAN creation is not enabled on the switch; [dec] is the new VLAN number.

    Action You must enable the dynamic VLAN creation so that the new VLAN can be added to the switch.

GVRP-3-CREATEVLANSUSPENDED: can not create suspended VLAN [dec]

    Explanation   This message indicates that a received GVRP join message contains a new VLAN number that is already suspended on the switch; [dec] indicates the suspended VLAN number.

    Action You can remove the suspended VLAN to allow it to be dynamically recreated or you can reactivate the suspended VLAN.

GVRP-3-DELETEVLANNONEXISTING: can't delete or withdraw non-existing VLAN [dec]

    Explanation   This message indicates that the VLAN to be deleted or withdrawn by the GVRP or VLAN configuration does not exist. No VLAN deletion is required for GVRP; [dec] is the non-existent VLAN number.

    Action You must specify a valid VLAN number.

GVRP-3-LOSTTRUNKEVT: TRUNK creation/deletion event lost for TRUNK [dec]/[dec]

    Explanation   This message indicates that VTP does not receive the request sent by GVRP because the VTP queue is full or the VTP task is not running; [dec]/[dec] is the module number/port number.

    Action Contact your technical support representative.

GVRP-3-LOSTVLANEVT: vlan creation/deletion event lost for vlan [dec]

    Explanation   This message indicates that a received GVRP join message contains a new VLAN number that needs to be created dynamically and GVRP failed to notify VTP for the VLAN creation. The error can also occur when GVRP wants to delete a VLAN and fails to notify VTP about the deletion. The problem occurs when the VTP message queue is full; [dec] is the new VLAN number.

    Action Try reinitializing the VTP configuration by toggling between VTP server mode and transparent mode. If the problem persists, you might need to reset or power cycle the switch.

GVRP-3-RECVNONGVRPTRUNK: drop GVRP PDU received on non-GVRP port [dec]/[dec]

    Explanation   This message indicates that a GVRP protocol data unit (PDU) frame received from a GVRP-disabled port was dropped because the port was not running GVRP; [dec]/[dec] is the module number/port number that received the GVRP PDU frame.

    Action You should check the peer side of the GVRP device for consistent GVRP configuration. Either the module/port should be set to GVRP enable or the peer side should be set to GVRP disabled.

GVRP-3-RECVVTPGVRPTRUNK: Drop VTP PDU received on GVRP port [dec]/[dec]

IP Permit List Messages

This section contains the IP Permit List messages.

IP-4

IP-4-PERMITFAIL: Unauthorized [chars] access attempt from [chars]

KERNEL Messages

This section contains the kernel (KERNEL) messages.


Note Kernel messages do not indicate a problem with system performance but should be reported to your technical support representative.

KERNEL-0

KERNEL-0-SLEEPFROMINT: sleep() called from Interrupt context.

    Explanation   This is a debug message for Cisco development purposes.

    Action Contact your technical support representative.

KERNEL-0-SLEEPFROMKER: sleep() called from Kernel context.

    Explanation   This is a debug message for Cisco development purposes.

    Action Contact your technical support representative.

KERNEL-1

KERNEL-1-CHECKSTACK: stk-alrt [chars],sp: %08x size: 0x%04x

    Explanation   This is a debug message for Cisco development purposes; [chars] is the stk-alrt message.

    Action Contact your technical support representative.

KERNEL-4

KERNEL-4-PDELAYFROMKER: pdelay () called from Kernel context.

    Explanation   This message indicates that a function is calling a kernel utility from the kernel context.

    Action Call your technical support representative.

KERNEL-4-YLDCPUFROMKER: yield_cpu() called from Kernel context.

    Explanation   This is a debug message for Cisco development purposes.

    Action Contact your technical support representative.

KERNEL-5

KERNEL-5-UNALIGNACCESS: Alignment correction made at 0x%08X [chars]ing 0x%08X

LD Messages

This section contains the Local Director (LD) messages.

LD-3

LD-3-LDACOMMITFAIL: Failed to Commit Local Director Accelerator

    Explanation   This message indicates that the Local Director Accelerator, which is Accelerated Server Load Balancing (ASLB), was not committed to the hardware. This message is displayed only at startup.

    Action This message is provided for information only.

LD-5

LD-5-LDHWDNORLSD: lda hardware resources not completely freed

MCAST Messages

This section contains the multicast (MCAST) messages including the Cisco Group Management Protocol (CGMP)/Internet Group Management Protocol (IGMP) messages and GARP Multicast Registration Protocol (GMRP) messages.

MCAST-2

MCAST-2-IGMP_ADDRAL: IGMP: Address Aliasing for [chars]

    Explanation   This message indicates that the Network Management Processor (NMP) detects a multicast data stream that is being aliased to a special multicast address; [chars] is one of the following multicast addresses, which is 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

    Action Check and isolate the host that is generating this type of multicast traffic. Verify which address is getting aliased; try not to use it for the multicast data feed.

MCAST-2-IGMP_FALLBACK: 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 is 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

    Action Check and isolate the host that is generating this type of multicast traffic. Verify which address is getting aliased; try not to use this address for the multicast data feed.

MCAST-2-IGMP_FALLBACKPERM: IGMP: Changed to FALL BACK permanently

    Explanation   This message indicates that the NMP detects a multicast stream that disabled the protocol redirection escape logic and is 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

    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-2-MAXGDALIMIT: No. of Multicast entries has reached the max [dec]

    Explanation   This message indicates that the number of multicast entries has reached the maximum limit; [dec] is 3072, the maximum number of multicast entries. No new entries will be created.

    Action Make sure no more than 3072 groups are used. Contact your technical support representative.

MCAST-4

MCAST-4-RTRDEL_TIMEOUT: Deleting Router Port [dec/dec] in vlan [dec] - Timeout

    Explanation   This message indicates that the router port timer has timed out and the router port entry has been removed; [dec/dec] is the router module number/port number, 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).

    Action Check if a router is on that port, and verify that IGMP is enabled.

MCAST-4-RX_IGMPLV: IGMP: Rcvd IGMP Leave [chars] on [dec]/[dec]

    Explanation   This message indicates that the switch has received an IGMP leave message for the group number on module number/port number; [chars] is the group number, and [dec]/[dec] is the module number/port number.

    Action This message is provided for information only.

MCAST-4-RX_IGMPREPORT: IGMP: Rcvd IGMP Report [chars] on [dec]/[dec]

    Explanation   This message indicates that the switch has received an IGMP report message for the group number on module number/port number; [chars] is the group number, and [dec]/[dec] is the module number/port number.

    Action This message is provided for information only.

MCAST-4-RX_JNRANGE: IGMP: Rcvd Report in the range of 01-00-5e-00-00-xx

    Explanation   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. This range is used normally for control packets and should not be used for general multicast data traffic.

    Action Contact your technical support representative.

MCAST-4-RX_LVRANGE: IGMP: Rcvd Leave in the range of 01-00-5e-00-00-xx

    Explanation   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. This range is used normally for control packets and should not be used for general multicast data traffic.

    Action Contact your technical support representative.

MCAST-5

MCAST-5-CGMPLV_ENABLE: CGMP Leave Feature is [chars]abled

    Explanation   This message indicates that the leave feature has either been enabled or disabled; [chars] is either [en]abled or [dis]abled.

    Action This message is provided for information only.

MCAST-5-GMRP_ADDGDA: GMRP: Add Multicast Group [chars]

    Explanation   This message indicates that a multicast group address has been added to the EARL table by GMRP. This occurs after a join message is received by that particular group address; [chars] is the group address.

    Action This message is provided for information only.

MCAST-5-GMRP_DELGDA: GMRP: Delete Multicast Group [chars]

    Explanation   This message indicates that a multicast group address has been deleted from the EARL table by GMRP. This occurs after a leave timer expires; [chars] is the group address.

    Action This message is provided for information only.

MCAST-5-GMRP_FWDALLEN: GMRP: ForwardAll [chars]abled on port [dec]/[dec]

    Explanation   This message indicates that the forward all feature is either enabled or disabled for this port; [chars] is either [en]abled or [dis]abled, and [dec]/[dec] is the module number/port number.

    Action This message is provided for information only.

MCAST-5-GMRP_PORTENABLE: GMRP [chars]abled on port [dec]/[dec]

    Explanation   This message indicates that the GMRP is disabled on the port; [chars]abled is [dis]abled, and port [dec]/[dec] is the module number and port number of the port where GMRP is disabled.

    Action This message is provided for information only.

MCAST-5-GMRP_REG: GMRP: Registration is set to [chars] on port [dec]/[dec]

    Explanation   This message indicates the type of registration for all the attributes registered on this port; [chars] can be either normal, fixed, or forbidden, and [dec]/[dec] is the module number/port number.

    Action This message is provided for information only.

MCAST-5-IGMP_NORMAL: IGMP: Running in NORMAL mode

    Explanation   This message indicates that the NMP has recovered from address aliasing and has reenabled redirection escape logic for the following 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

    Action This message is provided for information only.

MCAST-5-PROT_STATUS: [chars] Feature is [chars]abled

    Explanation   This message indicates whether the Layer 2 Multicast feature is enabled or disabled. The message displays whenever you execute CLI commands to enable or disable IGMP snooping or GMRP; the first [chars] is the feature either enabled or disabled, and the second [chars] is either enabled or disabled.

    Action This message is provided for information only.

MCAST-6

MCAST-6-CGMP_JOININFO: 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; [chars] is the group destination address, and [chars] is the unicast source address.

    Action This message is provided for information only.

MCAST-6-DELGDA: Deleting a GDA [chars] in vlan [dec]

    Explanation   This message indicates that a multicast entry in the given VLAN is being deleted because an IGMP leave from the last host for this GDA was received; [chars] is the group destination address, and vlan [dec] is the VLAN number.

    Action Contact your technical support representative.

MCAST-6-RGMP_JOIN: Rcvd RGMP Join Mesg [dec]/[dec] vlan [dec] for Group [chars]

    Explanation   This message indicates that the router has joined a multicast group, where [dec]/[dec] is the module number and port number, vlan [dec] is the VLAN number, and group [chars] is the group name.

    Action This message is provided for information only.

MCAST-6-RGMP_JOINRANGE: Rcvd RGMP Join Mesg in the range 01-00-5e-00-00-xx

    Explanation   This message indicates that the router has sent a message for an invalid (reserved) address. The address 01-00-5e-00-00-xx cannot be used by RGMP.

    Action This message is provided for information only.

MCAST-6-RGMP_LEAVE: Rcvd RGMP Leave Mesg [dec]/[dec] vlan [dec] for Group [chars]

    Explanation   This message indicates that the router has left a multicast group; [dec]/[dec] is the module number and port number, vlan [dec] is the VLAN number, and group [chars] is the group name.

    Action This message is provided for information only.

MCAST-6-RGMP_LVRANGE: Rcvd RGMP Leave Mesg in the range 01-00-5e-00-00-xx

    Explanation   This message indicates that the router has sent a message for an invalid (reserved) address. The address 01-00-5e-00-00-xx cannot be used by RGMP.

    Action This message is provided for information only.

MCAST-6-RTRADD_HSRP: Adding Router Port [dec/dec] in vlan [dec] - HSRP mesg

    Explanation   This message indicates that CGMP/IGMP snooping has learned a router port through Hot Standby Router Protocol (HSRP) messages; [dec]/[dec] is the module number/port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

MCAST-6-RTRADD_PIM: Adding Router Port [dec]/[dec] in vlan [dec] - PIM mesg

    Explanation   This message indicates that CGMP/IGMP snooping has learned a router port through PIM messages; [dec]/[dec] is the module number/port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

MCAST-6-RTRADD_PROT: Adding Router Port [dec/dec] in vlan [dec]

    Explanation   This message indicates that CGMP/IGMP has learned a new router port; [dec]/[dec] is the module number/port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

MCAST-6-RTRADD_USERCFG: Adding Router Port [dec/dec] in vlan [dec] - User Configd

    Explanation   This message indicates that the user has used the set multicast router command to set a user-configured multicast router; [dec/dec] is the module number/port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

MCAST-6-RTRRGMP_BYE: Router Port [dec]/[dec] in vlan [dec] has become nonRGMP-capable

    Explanation   This message indicates that an RGMP router port has changed to a non-RGMP router port, where [dec]/[dec] is the module number and port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

MCAST-6-RTRRGMP_HELLO: Router Port [dec]/[dec] in vlan [dec] has become RGMP-capable

    Explanation   This message indicates that a router port has changed to a RGMP-capable port; [dec]/[dec] is the module number/port number and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

MCAST-6-RTRRGMP_TIMEOUT: Router Port [dec]/[dec] in vlan [dec] is no longer RGMP capable-Timeout

    Explanation   This message indicates that the RGMP router has timed out and the port is no longer RGMP capable; [dec]/[dec] is the module number/port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

MCAST-6-RX_CGMPJN: CGMP: Rcvd CGMP Join Mesg in vlan [dec]

    Explanation   This message indicates that a CGMP join message was received by a VLAN; vlan [dec] is the VLAN number.

    Action This message is provided for information only.

MCAST-6-RX_CGMPLV: CGMP: Rcvd CGMP Leave Mesg [dec/dec] vlan [dec]

    Explanation   This message indicates that a CGMP leave message was received on a VLAN port; [dec/dec] is the module number/port number where the message was received, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

MCAST-6-TOPOCHG: Recvd Topology Change Notification in vlan [dec]

MGMT Messages

This section contains the MGMT messages.

MGMT-1

MGMT-1-DHCP_EXPIRE: DHCP lease expired, relinquishing IP address [chars]

    Explanation   This message indicates that the DHCP lease has expired and that the NMP is about to clear the system IP address; [chars] is the system IP address being released.

    Action Contact your technical support representative.

MGMT-3

MGMT-3-TOPN_IOBYTE: Port [dec]/[dec] transmit receive byte count is excessive, 1st poll [chars], 2nd poll [chars]

    Explanation   This message indicates that the difference between the TX/RX bytes value obtained during the first poll and TX/RX bytes value obtained during the second poll is too great; [dec]/[dec] is the module number/port number, 1st poll [chars] is the first poll counter value, and 2nd poll [chars] is the second poll counter value.

    Action Check the TopN report for abnormal values in the Tx+Rx Bytes column. Contact your technical support representative.

MGMT-4

MGMT-4-DHCP_REBIND: DHCP lease will expire in [dec] minutes

    Explanation   This message indicates that the server is trying to renew the DHCP lease, but the DHCP lease time has nearly expired; [dec] is number of minutes remaining in the DHCP lease.

    Action You should resolve this issue as soon as possible before the DHCP lease expires, otherwise, the system IP address will be released by the software after the lease has expired. Contact your technical support representative.

MGMT-5

MGMT-5-CONFIG_START: Auto config started with [chars]

    Explanation   This message indicates that the startup configuration has started; [chars] is the configuration file that is being used.

    Action This message is provided for information only.

MGMT-5-TOPN_ABORT: Report [dec] aborted due to configuration changes

    Explanation   This message indicates that the TopN report was aborted due to a configuration change; [dec] is the number of the TopN report.

    Action This message is provided for information only.

MGMT-5-TOPN_AVAILABLE: Report [dec] available

    Explanation   This message indicates the TopN report running in background is ready; [dec] is the TopN report number.

    Action This message is provided for information only.

MGMT-5-TOPN_DROPMOD: 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; report [dec] is the TopN report number and module [dec] is the module number.

    Action This message is provided for information only.

MGMT-5-TOPN_START: Report [dec] started by [chars]

    Explanation   This message indicates that the TopN message [dec] running with the background option [chars] is generating the report; [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.

    Action This message is provided for information only.

MGMT-5-TOPN_TERMINATE: Report [dec] terminated by [chars]

    Explanation   This message indicates that the TopN message [dec] was terminated by [chars]; [dec] is the TopN report number, and [chars] is the process that stopped the report generation.

    Action This message is provided for information only.

MGMT-6

MGMT-5-CONFIG_END: Auto config ended

    Explanation   This message indicates that the startup configuration has ended.

    Action This message is provided for information only.

MGMT-6-ENABLEFAIL: User [chars] failed to enter enable mode from [chars]

    Explanation   This message indicates that the user was unsuccessful entering enable mode; [chars] is the login name if available, and the second [chars] is console or IP.

    Action This message is for information only.

MGMT-6-ENABLEPASS: User [chars] entered enable mode from [chars]

    Explanation   This message indicates that the user has entered privileged mode successfully; [chars] is the login name if available, and the second [chars] is console
    or IP.

    Action This message is for information only.

MGMT-6-LOGINFAIL: User [chars] failed to log in from [chars]

    Explanation   This message indicates that the login attempt failed; [chars] is the login name if available, and the second [chars] is console or IP.

    Action This message is for information only.

MGMT-6-LOGINPASS: User [chars] logged in from [chars]

This section contains the Multilayer Switching (MLS) messages.

MLS-1

MLS-1-MCAST_RTRADDRCHNG: MAC address of the MLS Route Processor [chars] changed from [chars] to [chars]

    Explanation   This message indicates that a change in the MLS route processor MAC address has been detected; the first [chars] identifies the route processor, the second [chars] is the old MAC address, and the third [chars] is the new MAC address.

    Action Contact your technical support representative.

MLS-1-MCAST_RTRDEL: MLS Route Processor [chars] deleted - Timeout

    Explanation   This message indicates that the Multilayer Switch Feature Card (MSFC) is not responding to MLS supervisor engine messages. The supervisor engine considers the route processor unavailable and cleans up all of the shortcuts downloaded by the route processor; [chars] is the name of the route processor.

    Action Contact your technical support representative.

MLS-2

MLS-2-BANFFLTLFAIL: Set BANFF LTL failed, new shortcuts disabled

    Explanation   This message indicates that creation of new MLS shortcuts is disabled because of a failure in the central rewrite engine configuration.

    Action Contact your technical support representative.

MLS-2-MCAST_ACCESSMET: [chars] MET while Banff [dec] in reset state

    Explanation   This message indicates that there is a racing condition in multiple multicast tasks when trying to access the Multicast Expansion Table (MET); [chars] is either reading or writing and [dec] is either 1, 2, or 3 representing switching bus A, B, or C.

    Action The system should recover from this condition without intervention. If the error continues to recur, contact your technical support representative.

MLS-2-MCAST_METFULL: Multicast Expansion Table full

    Explanation   This message indicates that the multicast expansion table used to store outgoing VLAN information is full.

    Action This message is provided for information only.

MLS-2-MCAST_TASKFAIL: Task creation failed

    Explanation   This message indicates that the Multicast Multilayer Switching (MMLS) feature could not start the process; the feature has been disabled by the switch.

    Action Contact your technical support representative.

MLS-2-WHISTLERMIERRORDIS: Whistler MI error exceeded threshold, MLS stopped

    Explanation   This message indicates that the number of memory interface errors exceeded the threshold. MLS is disabled.

    Action This is a hardware defect. Contact your technical support representative.

MLS-2-WHISTLERPARITYERROR: Whistler parity error, MLS stopped

    Explanation   This message indicates that a parity error occurred in the NetFlow Feature Card (NFFC) II Whistler ASIC.

    Action This is a hardware defect. Contact your technical support representative.

MLS-3

MLS-3-GETNEWLEARN: Get new learn mac notification [hex]

    Explanation   This message indicates that MLS is not supposed to get any new source address learned notification; [hex] is the new source address. This message indicates an internal error.

    Action Contact your technical support representative.

MLS-3-NEWSCCREATION: New MLS entries creation [chars]abled by [chars]

    Explanation   This message warns you that a problem with new MLS entries creation was detected during the process exit; [chars]abled can be either disabled or enabled, and the second [chars] is the task name.

    Action Contact your technical support representative.

MLS-3-WHISTLERMIERRORHRST: Whistler MI error, MI hard reset

    Explanation   This message indicates that a memory interface error occurred in the NFFC II Whistler ASIC. The memory interface is hard reset.

    Action This message is provided for information only.

MLS-4

MLS-4-LOSEEVENT: Event loss, purge all entries

    Explanation   This message indicates that an internal MLS event loss occurred due to insufficient system resources. All MLS entries are purged.

    Action This message is provided for information only.

MLS-4-MOVEOVERFLOW: 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; [dec] is the number of seconds, and [hex] is the event code for moves.

    Action Check the topology for any loops. Call your technical support representative.

MLS-4-RESUMESC: 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.

    Action This message is provided for information only.

MLS-5

MLS-5-FLOWMASKCHANGE: [chars] flowmask changed from [chars] to [chars]

    Explanation   This message indicates that the MLS flowmask for the switching engine identified by the first [chars] has been changed from [chars] to [chars]. The second [chars] is the original flowmask, and the third [chars] is the new flowmask. The flowmask can be DEST, DEST-SRC, or FULL.

    Action This message is provided for information only.

MLS-5-IPXMAXHOPCHANGE: IPX max hop count changed from [dec] to [dec]

    Explanation   This message indicates a change has been made to the maximum hop count value on the switch. The count is the minimum value requested by all the MLS route processors; from [dec] is the old maximum hop count and to [dec] is the new maximum hop count.

    Action This message is provided for information only.

MLS-5-MCAST_GLOBALPURGE: Purging All Multicast Flows due to [chars]

    Explanation   This message indicates that the MLS supervisor engine is purging all of the flows downloaded by the route processor; [chars] is the reason the purge is taking place.

    Action Contact your technical support representative.

MLS-5-MCAST_L3FLOW: Installed from the Route Processor [chars] for Source [chars] Group [chars] Vlan [dec]

    Explanation   This message indicates that a new multicast flow has been installed; the first [chars] is the route processor name, the second [chars] is the source name, the third [chars] is the group name, and Vlan [dec] is the VLAN number.

    Action Contact your technical support representative.

MLS-5-MCAST_ROUTERPURGE: Received Global Delete Message from [chars]. Purging all related Multicast Flows

    Explanation   This message indicates that the router has removed all the multicast flows which had been previously downloaded. This can occur when the multicast MLS feature is disabled on the router or a serious problem occurs disabling the feature.

    Action Contact your technical support representative.

MLS-5-MCAST_STATUS: IP Multicast L3 Multilayer Switching Feature is [chars]abled

    Explanation   This message indicates whether the multicast Layer 3 multilayer feature is enabled or disabled; [chars]abled can be either disabled or enabled.

    Action This message is provided for information only.

MLS-5-MLSDISABLED: Multilayer switching is disabled

    Explanation   This message indicates that MLS is disabled.

    Action This message is provided for information only.

MLS-5-MLSENABLED: Multilayer switching is enabled

    Explanation   This message indicates that MLS is enabled.

    Action This message is provided for information only.

MLS-5-NDEDISABLED: Netflow Data Export disabled

    Explanation   This message indicates that flow statistics for all aged flows have stopped being sent.

    Action This message is provided for information only.

MLS-5-NDEENABLED: Netflow Data Export enabled

    Explanation   This message indicates that flow statistics for all aged flows are being sent to the configured host in a User Datagram Protocol (UDP) datagram.

    Action This message is provided for information only.

MLS-5-ROUTERADD: Route processor [chars] added

    Explanation   This message indicates that an MLS route processor has been added by the MLS switching engine [chars]; [chars] is the ID of the MLS route processor. The MLS switching engine starts Layer 3 switching for the MLS route processor.

    Action This message is provided for information only.

MLS-5-ROUTERDEL: Route Processor [chars] deleted - [chars]

    Explanation   This message indicates that an MLS route processor [chars] has been deleted by the MLS switching engine; the first [chars] is the ID of the MLS route processor; the second [chars] is the deletion cause.

    Action This message is provided for information only.

MLS-6

MLS-6-WHISTLERXTAGERROR: Whistler error xtag=[dec]

PAGP and FEC Messages

This section contains the Port Aggregation Protocol (PAgP) and Fast EtherChannel (FEC) messages.

PAGP-3

PAGP-3-CONFPORTCHNLFAIL: Failure = [dec] in configPortChannel for mNo/pNo = [dec]/[dec]

    Explanation   This message indicates that the system was unable to configure the channel properly; [dec] is the return status, and [dec]/[dec] is the module number/port number.

    Action Try to reset the failing ports. If the message reappears, contact your technical support representative.

PAGP-3-QFULL: [chars] queue is full

    Explanation   This message indicates that the [chars] message buffer between two processors is full; [chars] identifies the buffer.

    Action Reset the system. If the message reappears, contact your technical support representative.

PAGP-5

PAGP-5-PORTFROMSTP: Port [dec]/[dec] left bridge port [dec]/[chars]

    Explanation   This message indicates that the physical port disconnected from the logical port; [dec]/[dec] is the module number/port number, and [dec]/[chars] is the module number/port range.

    Action Contact your technical support representative.

PAGP-5-PORTTOSTP: Port [dec]/[dec] joined bridge port [dec]/[chars]

    Explanation   This message indicates that the physical port joined the logical port; [dec]/[dec] is the module number/port number, and [dec]/[chars] is the module number/port range.

    Action Contact your technical support representative.

PAGP-7

PAGP-7-BADQUEUEMSG: Unknown message in queue [chars]

    Explanation   This message indicates that the processor received a message it cannot identify; [chars] is the message's character string.

    Action This message is provided for information only.

PAGP-7-GETAGPORTFAIL: Failed to get new channel-id for [dec]/[dec]

    Explanation   This message indicates that while trying to configure a module and port, the maximum number of channels has been reached (128); [dec]/[dec] is the module number/port number.

    Action Contact your technical suppport representative.

PAGP-7-GETPORTFAIL: Failed to get port from portList

    Explanation   This message indicates that the logical port list did not contain at least one physical port.

    Action Contact your technical support representative.

PAGP-7-INACTIVEVLAN: ([dec]/[dec]) vlan inactive

    Explanation   This message indicates that the system tried to transmit a packet to a VLAN but the VLAN is not active; ([dec]/[dec]) is the module number/port number.

    Action Contact your technical support representative.

PAGP-7-INVALIDPORT: Invalid agportIndex = [dec] (mNo/aNo = [dec]/[dec])

    Explanation   This message indicates that the agportIndex is out of range (the logical port is invalid); [dec] is the index, and ([dec]/[dec]) is the module number/port number.

    Action Contact your technical support representative.

PAGP-7-NOACTIVEVLAN: Failed to transmit info pdu --- no active vlan ([dec]/[dec])

    Explanation   This message indicates that the system tried to transmit a packet through a VLAN that was not active; ([dec]/[dec]) is the module number/port number.

    Action Contact your technical support representative.

PAGP-7-NOMEM: 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.

    Action Try resetting the system. If the message reoccurs, contact your technical support representative.

PAGP-7-PROCFAIL: Failed to create PAgP_Group_Rx process

    Explanation   This message indicates that the PAgP_Group_Rx process was not created, so channeling is not allowed.

    Action Contact your technical support representative.

PAGP-7-STPDISABLED: Failed to transmit info pdu --- disabled STP ([dec]/[dec])

    Explanation   This message indicates that spanning tree is disabled and cannot transmit a packet; ([dec]/[dec]) is the module number/port range.

    Action Contact your technical support representative.

PAGP-7-WAITFORMEM: Wait for successful memory allocation

PROTFILT Messages

This section contains the protocol filter (PROTFILT) messages.

PROTFILT-5

PROTFILT-5-AUTO_OFF: 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; [dec]/[dec] is the module number/port number, and [chars] is the protocol group.

    Action This message is provided for information only.

PROTFILT-5-AUTO_ON: Port [dec]/[dec] is set to AUTO-ON for [chars]

PRUNING Messages for VTP

This section contains the PRUNING messages for VLAN Trunking Protocol (VTP).

PRUNING-2

PRUNING-2-INITSEMERR: semaphore [hex] not null at vtp_initialization!

    Explanation   This message indicates that there was an initialization process error in creating a VTP semaphore; [hex] is the semaphore value.

    Action Try resetting the switch. If the error persists, contact your technical support representative.

PRUNING-2-INVSTS: FATAL- inv vlan [dec] status [hex]

    Explanation   This message indicates an internal error; [dec] is the VLAN number, and [hex] is the status value.

    Action Contact your technical support representative.

PRUNING-2-LOSTST1: update: lost trunk [dec]/[dec]([dec]) vlan [dec] state [dec]

    Explanation   This message indicates that the attempt to save the VLAN spanning-tree state change on the trunk was lost while updating; [dec] / [dec]([dec]) is the module number/port number (the port number is 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, and 4=blocking).

    Action Contact your technical support representative.

PRUNING-2-LOSTST2: set: lost trunk [dec]/[dec]([dec]) vlan [dec] state [dec]

    Explanation   This message indicates that the attempt to save the VLAN spanning-tree state change on the trunk was lost while setting; [dec] / [dec]([dec]) is the module number/port number (the port number is 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, and 4=blocking).

    Action Contact your technical support representative.

PRUNING-2-LOSTSTCHG: vlan state change: can't find trunk (index=[hex])

    Explanation   This message indicates that the trunk could not be found while the VLAN pruning state changed; [hex] is the index for the lost trunk.

    Action Contact your technical support representative.

PRUNING-2-NOVLANBITS: no vlan string for trunk [dec]/[dec] (domain [chars])

    Explanation   This message indicates an internal error; [dec]/[dec] is the trunk module number/port number, and [chars] is the domain name.

    Action Contact your technical support representative.

PRUNING-2-SCPWRERR: SCP failed to write LTL on module [dec]

    Explanation   This message indicates an internal error for the module [dec]; [dec] is the module number.

    Action Contact your technical support representative.

PRUNING-3

PRUNING-3-INVTLV: rx summary on trunk [chars] with invalid TLV value:[hex]

    Explanation   This message indicates that some other VTP device has internal errors; [chars] is the trunk module number/port number, and [hex] is the invalid value.

    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-JOININVFSTV: Join rx on trunk [chars]-invalid first vlan: [dec]

    Explanation   This message indicates that some other VTP device has internal errors; [chars] is the trunk module number/port number, and [dec] is the invalid first VLAN number.

    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-JOININVLEN: Join rx on trunk [chars]-invalid len: [dec] ([dec])

    Explanation   This message indicates that some other VTP device has internal errors; [chars] is the trunk module number/port number, [dec] is the number of the actual packet length, and the second ([dec]) is the invalid packet length.

    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-JOININVLSTV: Join rx on trunk [chars]-invalid last vlan: [dec]

    Explanation   This message indicates that some other VTP device has internal errors; [chars] is the trunk module number/port number, and [dec] is the invalid last VLAN number.

    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-NOMEM: no memory to build trunk [dec]/[dec] info for dependent code

    Explanation   This message indicates that no system memory is available and the internal status for trunk [dec]/[dec] will be lost; [dec]/[dec] is the module number/port number.

    Action Upgrade the system memory (RAM) size.

PRUNING-3-NOSCPMEM: failed to allocate scpmsg buffer vtp_dep_vlan_state_change-notification

    Explanation   This message occurs when VTP tries to allocate memory, but there is insufficient memory.

    Action Contact your technical support representative.

PRUNING-3-SCPSENDERR: SCP send error: [chars] [dec]

    Explanation   This message indicates an internal error when the supervisor engine communicates with the modules; [chars] is the last logged debug message, and [dec] is the last logged debug value.

    Action Contact your technical support representative.

PRUNING-4

PRUNING-4-INVASSOC: invalid vlan local assoc: [hex] (domain [chars])

    Explanation   This message indicates that an intermediate error has occurred and VTP pruning might or might not work on that trunk; [hex] is the VLAN local association value, and ([chars]) is the domain name.

    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-INVLNKST: invalid link state: [hex]

    Explanation   This message indicates a trunk link is set to an invalid state; [hex] is the invalid state value.

    Action Contact your technical support representative.

PRUNING-4-INVPMODE: invalid pruning mode: [hex]

    Explanation   This message indicates that an intermediate error occurred and VTP pruning may or may not work on that trunk; [hex] is the pruning mode value.

    Action Disable and then enable the trunk port. If the message reappears, contact your technical support representative.

PRUNING-4-INVSPTST: invalid SPT state: [hex]

    Explanation   This message indicates that an intermediate spanning-tree (SPT) error occurred and VTP pruning might or might not work on that trunk; [hex] could be one of the following errors:

invalid link state: link state valuevlan [vlan no] not found [domain name]invalid SPT state: [spt state value]

    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-LOSTASSOCEVT: lost vlan local assoc event (vlan=[dec],assoc=[dec])

    Explanation   This message indicates that an internal event was lost due to insufficient buffer memory; vlan=[dec] is the VLAN number, and assoc=[dec] is the local association status.

    Action No action needs to be taken, recovery is automatic.

PRUNING-4-LOSTGVRPEVT: lost gvrp trunk change event (vlan=[dec])

    Explanation   This message occurs when GVRP wants to send a join/leave request to VTP, but the VTP is either not running or the VTP queue is full; [dec] is the VLAN number.

    Action Contact your technical support representative.

PRUNING-4-LOSTSPTEVT: lost spt state event (trunk=[dec]/[dec],vlan=[dec],state=[dec])

    Explanation   This message indicates an internal event was lost due to insufficient buffer memory; trunk=[dec]/[dec] is the module number/port number, vlan=[dec] is the VLAN number, and state=[dec] is the Spanning-Tree Protocol status.

    Action No action needs to be taken, recovery is automatic.

PRUNING-4-NOBUF: no mbuf to build join

    Explanation   This message indicates that no buffer memory is available for VTP pruning.

    Action Contact your technical support representative.

PRUNING-4-NODOMAIN: domain [chars]([dec]) not found

    Explanation   This message indicates an intermediate configuration mismatch; [chars] is the domain name, and ([dec]) is the domain name length.

    Action Contact your technical support representative if the message appears repeatedly.

PRUNING-4-NOTRUNK: trunk [dec]/[dec] not found (domain [chars])

    Explanation   This message indicates that an intermediate error occurred and VTP pruning might or might not work on that trunk; [dec]/[dec] is the trunk module number/port number, and ([chars]) is the domain name.

    Action Enter the show trunk command to verify that 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-NOVLAN: vlan [dec] not found (domain [chars])

    Explanation   This message indicates that vlan [dec] was not found; [dec] is the VLAN number, and ([chars]) is the domain name.

    Action Contact your technical support representative.

PRUNING-5

PRUNING-5-BOGUSTIMEOUT: bogus timeout for trunk [chars]

    Explanation   This message indicates that an internal notification occurred on trunk [chars]; [chars] is the module number/port number.

    Action No action is required.

PRUNING-5-CHGPMODE: change domain [chars] pruning mode to [chars]

    Explanation   This message indicates a change to the VTP pruning mode; the first [chars] is the domain name, and the second [chars] is enabled or disabled.

    Action This message is provided for information only.

PRUNING-5-JOINDIFFDOMAIN: domain [chars] not found in rx Join (trunk [dec]/[dec])

    Explanation   This message indicates that some other VTP device is assigned to a different domain; [chars] is the domain name, and (trunk [dec]/[dec]) is the module number/port number.

    Action Check other VTP devices assigned to a different domain. Enter the clear config all command for the devices, and then assign the correct domain name.

PRUNING-5-JOINDISCARD: rx Join on trunk [dec]/[dec] when pruning disabled

    Explanation   This message indicates that VTP inconsistency exists in the network; trunk [dec]/[dec] is the module number/port number.

    Action Check other devices to find out where the inconsistency exists and correct.

PRUNING-5-JOINNONAME: no domain name in rx Join (trunk [dec]/[dec])

    Explanation   This message indicates that some other VTP device may have internal errors; (trunk [dec]/[dec]) is the module number/port number.

    Action Check other VTP devices for internal errors. If no errors are found, contact your technical support representative.

PRUNING-5-JOINNOTRUNK: trunk [dec]/[dec] not found for rx Join

    Explanation   This message indicates that an intermediate error occurred; trunk [dec]/[dec] is the module number/port number.

    Action No action is required.

PRUNING-5-LEARNDOMAIN: learn domain [chars] from network

    Explanation   This message indicates that the VTP domain is learned from another VTP device; [chars] is the domain name.

    Action This message is provided for information only.

PRUNING-5-RECOVASSOC: Recover from local assoc event loss

    Explanation   This message indicates that the software recovers automatically from an internal event loss.

    Action This message is provided for information only.

PRUNING-5-RECOVSPT: recover from spt event loss for trunk [dec]/[dec]

    Explanation   This message indicates that the software recovers automatically from an internal event loss; [dec]/[dec] is the module number/port number.

    Action This message is provided for information only.

PRUNING-5-VLANJOINED: Joined-trunk [dec]/[dec] vlan [dec]

    Explanation   This message indicates that the VLAN on the trunk is not pruned; [dec]/[dec] is the module number/port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

PRUNING-5-VLANPRUNED: Pruned-trunk [dec]/[dec] vlan [dec]

    Explanation   This message indicates that the VLAN on the trunk is pruned; [dec]/[dec] is the module number/port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

PRUNING-6

PRUNING-6-FSMSTCHG: 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 module number and port number.

    • V[dec] is the VLAN number [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] could be Null, Disable, NoPrune, Joined, or Pruned.

    Action This message is provided for information only.

PRUNING-6-TRIGJOIN: trunk [chars]- send trig Join

QOS Messages

This section contains the quality of service (QoS) messages.

QOS-3

QOS-3-ACLMAP_PORTFAIL: Unable to map ACL [chars] to port [dec]/[dec]. Error is [chars]

    Explanation   This message indicates that the ACL specified could not be mapped to the port; ACL [chars] is the access control list identifier, [dec]/[dec] is the module number/port number, and the second [chars] is the error message.

    Action Contact your technical support representative.

QOS-3-ACLMAP_VLANFAIL: Unable to map ACL [chars] to VLAN [dec]. Error is [chars]

    Explanation   This message indicates that the ACL specified could not be mapped to the VLAN; ACL [chars] is the access control list identifier, [dec] is the VLAN number, and the second [chars] is the error message.

    Action Contact your technical support representative.

QOS-3-ACLUNMAP_PORTFAIL: Unable to unmap ACL [chars] to port [dec]/[dec]. Error is [chars]

    Explanation   This message indicates that the QoS ACL map specified could not be cleared from the port; ACL [chars] is the access control list identifier, [dec]/[dec] is the module number/port number, and the second [chars] is the error message.

    Action Contact your technical support representative.

QOS-3-ACLUNMAP_VLANFAIL: Unable to unmap ACL [chars] to VLAN [dec]. Error is [chars]

    Explanation   This message indicates that the QoS ACL map specified could not be cleared from the VLAN; ACL [chars] is the access control list identifier, [dec] is the VLAN number, and the second [chars] is the error message.

    Action Contact your technical support representative.

QOS-3-GETCOSMAPFAIL: Unable to get CoS map on [dec]/[dec]

    Explanation   This message indicates a failure to read the class of service (CoS) map of a port; [dec]/[dec] is the module number/port number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-GETDEFCOSFAIL: Unable to get default CoS on port [dec]/[dec]

    Explanation   This message indicates a failure to read the module port default CoS; [dec]/[dec] is the module number/port number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-GETIPPRECMAPENFAIL: Unable to get enable/disable mapping of IP precedence to CoS

    Explanation   This message indicates a failure to read the enable or disable state of the IP precedence to CoS mapping from the forwarding engine.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-GETIPPRECMAPFAIL: Unable to get mapping of IP precedence to CoS

    Explanation   This message indicates a failure to read the IP precedence to CoS mapping from the forwarding engine.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-GETPORTERRSTATSFAIL: Unable to retrieve QoS error statistics for port [dec]/[dec]

    Explanation   This message indicates a failure to read the module port error statistics; [dec]/[dec] is the module number/port number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-GETRXTHRFAIL: Unable to get receive threshold on [dec]/[dec]

    Explanation   This message indicates a failure to read the receive thresholds of the module port; [dec]/[dec] is the module number/port number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-GETTRUSTFAIL: Unable to get trust type on [dec]/[dec]

    Explanation   This message indicates a failure to read the module port trust type; [dec]/[dec] is the module number/port number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-GETTXQSIZEFAIL: Unable to get transmit queue sizes on [dec]/[dec]

    Explanation   This message indicates a failure to read the transmit queue sizes on the module port; [dec]/[dec] is the module number/port number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-GETTXTHRFAIL: Unable to get transmit threshold on [dec]/[dec]

    Explanation   This message indicates a failure to read the transmit thresholds of the module port; [dec]/[dec] is the module number/port number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-GETWRRFAIL: Unable to get WRR on [dec]/[dec]

    Explanation   This message indicates a failure to read the weighted round-robin weights of the module port; [dec]/[dec] is the module number/port number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-NOMEM: QoS: ERROR - Unable to allocate memory for SCP message to [dec]/[dec]

    Explanation   This message indicates that there was insufficient memory for QoS to be configured; [dec]/[dec] is the module number/port number.

    Action Reset the system. If the message reappears, contact your technical support representative.

QOS-3-SCPERR: SCP failure on message with opcode 0x[hex], errcode=[dec]. Error Code [dec]

    Explanation   This message indicates that a module's QoS setting failed; opcode [hex] is the op code value and error code [dec] is the error code value.

    Action Contact your technical support representative. The technical support representative will request the op code and error code values reported by the message.

QOS-3-SETCOSMAPFAIL: Unable to set CoS map on module [dec]

    Explanation   This message indicates that the desired CoS map could not be set on the module; module [dec] is the module number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-SETDEFCOSFAIL: Unable to set default CoS on port [dec]/[dec]

    Explanation   This message indicates that the desired default CoS could not be set on the module port; port [dec]/[dec] is the module number/port number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-SETIPPRECMAPENFAIL: Unable to enable/disable mapping of IP precedence to CoS

    Explanation   This message indicates that the IP precedence to the CoS mapping function could not be enabled or disabled in the forwarding engine.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-SETIPPRECMAPFAIL: Unable to set mapping of IP precedence to CoS

    Explanation   This message indicates that the desired IP precedence to CoS mapping could not be set in the forwarding engine.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-SETRXTHRFAIL: Unable to set receive threshold on module [dec]

    Explanation   This message indicates that the desired receive thresholds on the module could not be set; module [dec] is the module number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-SETTRUSTFAIL: Unable to set trust type on [dec]/[dec]

    Explanation   This message indicates that the desired trust type could not be set on the module; [dec]/[dec] is the module number/port number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-SETTXQSIZEFAIL: Unable to set transmit queue sizes on module [dec]

    Explanation   This message indicates that the desired transmit queue sizes could not be set on the module; module [dec] is the module number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-SETTXTHRFAIL: Unable to set transmit threshold on module [dec]

    Explanation   This message indicates that the desired transmit thresholds on the module could not be set; module [dec] is the module number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-3-SETWRRFAIL: Unable to set WRR on module [dec]

    Explanation   This message indicates that the desired weight for the weighted round-robin (WRR) could not be set on the module; module [dec] is the module number.

    Action Check the module for hardware problems. If nothing is obvious, contact your technical support representative.

QOS-5

QOS-5-DISABLED: QoS has been disabled on switch

    Explanation   This message indicates that the QoS feature has been disabled.

    Action This message is provided for information only.

QOS-5-ENABLED: QoS has been enabled on switch

RADIUS Messages

This section lists the Remote Authentication Dial-In User Service (RADIUS) messages.

RADIUS-3

RADIUS-3-REQUESTSENDFAIL: Request send error, bytes sent [dec], expected [dec]

    Explanation   This message indicates that there was a packet transmit error; sent [dec] is the number of packets transmitted and expected [dec] is the number of packets expected to be sent.

    Action Contact your technical support representative.

RADIUS-3-RESPONSERECVFAIL: Response receive error, bytes received [dec], expected [dec]

    Explanation   This message indicates that there was a packet receive error; received [dec] is the number of packets received, and expected [dec] is the number of packets expected.

    Action Contact your technical support representative.

RADIUS-3-SENDACCTFAIL: Fail to send out accounting information to configured Radius server(s)

    Explanation   This message indicates that accounting information was not received from the RADIUS server or servers.

    Action Verify that the switch and the RADIUS server have the correct configurations. Contact your technical support representative.

RADIUS-3-SOCKETFAIL: Radius socket error

    Explanation   This message indicates that an attempt to open a socket failed possibly due to insufficient resources.

    Action Contact your technical support representative.

RADIUS-5

RADIUS-5-ALLDEADSERVER: All Radius servers dead: identification [dec]

    Explanation   This message indicates that the system is unable to establish connection with any of the RADIUS servers configured; [dec] is the identification number of the RADIUS request packet.

    Action Check network connectivity.

RADIUS-5-NOSERVERS: No Radius servers configured

    Explanation   This message indicates that RADIUS is enabled, but no servers are configured.

    Action Configure a RADIUS server.

RADIUS-5-SERVERALIVE: Radius server [dec] alive

RSVP Messages

This section contains Resource reSerVation Protocol (RSVP) messages.

RSVP-3

RSVP-3-ATTACHFAILED: Unable to attach RSVP Acl

    Explanation   This message indicates that RSVP is unable to attach an Access Control List (ACL) in the hardware in response to a Common Open Policy Service (COPS) decision to install the ACL. This situation can occur when a section of the TCAM allocated to dynamic ACLs is full, or because of some other error in the QoS module or ACL manager module. By enabling syslog messages for these two features, you can obtain additional information about the failure.

    Action Contact your technical support representative.

RSVP-3-DISCARDPATH: Input Path msg discarded

    Explanation   This message is generated when a received Path message is dicarded before processing. This can occur when a burst of RSVP messages is received and the RSVP event queue is almost full. Another possibility is that the COPS server is becoming overloaded and has not responded to requests regarding flows already in the database. New flows in the database are not accepted until the number of outstanding requests decreases.

    Action This message is provided for information only.

RSVP-3-MISSINGL2HOP: L2 HOP missing in Path msg - dropping

    Explanation   This message is generated when a received Path message to be forwarded downstream does not contain a properly filled NHOP_L2 object as required by the Subnet Bandwidth Manager (SBM) specifications. This means that the switch does not know the MAC addess of the next hop and cannot find the correct output port.

    Action Contact your technical support representative.

RSVP-6

RSVP-6-PDPCLOSEDCONN: PDP closed connection - flushing policy

    Explanation   This message is generated when a COPS Client Close message is received from the COPS server. When this occurs, the switch flushes its RSVP database and detaches all installed ACLs. A new connection to the COPS server is attempted.

    Action Contact your technical support representative.

RSVP-6-PDPUP: Established connection to PDP

    Explanation   This message is generated when the COPS server responds with a COPS Client Accept message to a Client Open message sent by the switch. This indicates that an active COPS connection is present.

    Action This message is provided for information only.

RSVP-6-POLICYTTLEXPIRED: Disconnected from PDP: Policy timer expired

    Explanation   This message is generated when connection to the COPS server is lost. The switch caches the downloaded policy and tries to reconnect for a preset amount of time. After the timer expires, the switch flushes the RSVP database, and continues trying to connect to the COPS server.

    Action This message is provided for information only.

RSVP-6-RSVPEXITING: RSVP Exiting

    Explanation   This message is generated when RSVP is disabled or when QoS is disabled.

    Action This message is provided for information only.

RSVP-6-UNKNOWNOUTPORT: Unknown output port for Path msg

SECURITY Messages

This section contains the security messages.

SECURITY-1

SECURITY-1-PORTSHUTDOWN: Port [dec]/[dec] shutdown due to [chars]

    Explanation   This message indicates that a port has been shut down due to an insecure host sourcing a packet into that port; [dec]/[dec] is the module number/port number of the port that has shut down and [chars] can be either security violation or no space in forwarding engine lookup table.

    Action Check why the host is sourcing a packet into that port.

SECURITY-5

SECURITY-5-CLEARADDRESS: [chars] cleared from secure address list for port [dec]/[dec] due to [chars]

    Explanation   This message indicates that an address has been cleared from the secure address list; [chars] is the address cleared, [dec]/[dec] is the module number/port number, and the second [chars] is the reason the address was cleared, either age out or conflict with online module.

    Action This message is provided for information only.

SECURITY-5-PORTREENABLED: Port [dec]/[dec] is re-enabled after shutdown timeout

SNMP Messages

This section contains the Simple Network Management Protocol (SNMP) messages.

SNMP-2

SNMP-2-TCPSKTOPENFAIL: Can't open TCP socket for [dec]

    Explanation   This message indicates that the TCP socket for [dec] cannot be opened; [dec] is the TCP port number.

    Action Reboot the system.

SNMP-3

SNMP-3-UDPSKTOPENFAIL: Can't open UDP socket for [dec]

    Explanation   This message indicates that the UDP socket for [dec] cannot be opened; [dec] is the UDP port number.

    Action Reboot the system.

SNMP-5

SNMP-5-CHASSISALARM: Chassis Alarm Trap: tmpAlarm([chars]), minorAlarm([chars]), and/or majorAlarm([chars])

    Explanation   This message indicates the on and off condition of the Chassis Alarm Trap: tmpAlarm([chars]), minorAlarm([chars]), and/or majorAlarm([chars]); [chars] could be on or off.

    Action This message is provided for information only.

SNMP-5-COLDSTART: Cold Start Trap

    Explanation   This message indicates that the sending protocol entity is reinitializing itself so the agent's configuration or the protocol entity implementation might be altered.

    Action This message is provided for information only.

SNMP-5-ENTITYTRAP: Entity Mib last change time [dec] ticks

    Explanation   This message indicates that the value of entLastChangeTime MIB object was changed; [dec] is the value of sysUpTime at the time this event occurs.

    Action This message is provided for information only.

SNMP-5-LERALARMTRAP: FDDI Ler Alarm [[chars]] Trap for [[dec]/[dec]]

    Explanation   The fddimibPORTLerFlag object in the FDDI-SMT73-MIB (RFC 1512) has turned on or off one of its ports; [[chars]] is on or off, and [[dec]/[dec]] is the module number/port number.

    Action This message is provided for information only.

SNMP-5-LINKTRAP: Link [chars] Trap -- ifName=[chars]

    Explanation   This message indicates the type of Link [chars] Trap if the name is [chars]; the first [chars] is up or down, and the second [chars] is sc0/sl0/mNo-pNo.

    Action This message is provided for information only.

SNMP-5-MODULETRAP: Module [dec] ([chars]) Trap

    Explanation   This message indicates the type of module trap; [dec] is the module number, and ([chars]) is up or down.

    Action This message is provided for information only.

SNMP-5-NEWROOTTRAP: New Root Trap for VLAN [[dec]]

    Explanation   This message indicates that there is a new root of the spanning tree; [[dec]] is a VLAN number.

    Action This message is provided for information only.

SNMP-5-RPTHEALTHTRAP: Repeater health trap:rptrOperStatus([dec],[dec])=[chars]

    Explanation   This message indicates the repeater health trap:rptrOperStatus status; [dec],[dec] is the module number, port number, and [chars] is one of the following: other, ok, rptrFailure, groupFailure, portFailure, or generalFailure.

    Action This message is provided for information only.

SNMP-5-RPTRESETTRAP: Repeater reset trap:rptrOperStatus([dec],[dec])=[chars]

    Explanation   This message indicates the repeater reset trap:rptrOperStatus status; [dec],[dec] is the module number, port number, and [chars] is one of the following: other, ok, rptrFailure, groupFailure, portFailure, or generalFailure.

    Action This message is provided for information only.

SNMP-5-STPXTRAP: 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; [dec] is the VLAN number, [[dec/dec]] is the module number/port number, and ([chars]) is the inconsistency detected.

    Action This message is provided for information only.

SNMP-5-TOPOTRAP: Topology Change Trap for VLAN [[dec]]

    Explanation   This message indicates that a configured port changed from the learning state to the forwarding state, or from the forwarding state to the blocking state; [[dec]] is a VLAN number.

    Action This message is provided for information only.

SNMP-5-WARMSTART: Warm Start Trap

    Explanation   This message indicates that the standby supervisor engine has taken control.

    Action This message is provided for information only.

SNMP-6

SNMP-6-SUBAGENTCONN: Subagent [dec] [chars]

    Explanation   This message indicates that the connection status of the subagent [dec]; [dec] is the subagent number, and [chars] could be other, OK, rptr Failure, group Failure, port Failure, or general Failure.

    Action This message is provided for information only.

SNMP-6-SUBAGENTDIS: Disconnect Subagent [dec], [chars]

    Explanation   This message indicates that the subagent [dec] has been disconnected; [dec] is the subagent index, and [chars] is the reason for the disconnection.

    Action This message is provided for information only.

SNMP-6-SUBAGENTTIMEOUT: Subagent [dec] Timeout, drop connection

    Explanation   This message indicates that the subagent [dec] has been disconnected when the master agent times out during communications with the subagent; [dec] is the subagent index.

    Action This message is provided for information only.

SNMP-6-TCPSKTCLOSE: TCP socket [[dec]] closed

    Explanation   This message indicates that the TCP socket [[dec]] closed; [[dec]] is the TCP port number.

    Action This message is provided for information only.

SNMP-6-TCPSKTOPEN: TCP socket [[dec]] opened

    Explanation   This message indicates that the TCP socket [[dec]] opened; [[dec]] is the TCP port number.

    Action This message is provided for information only.

SNMP-6-UDPSKTCLOSE: UDP socket [[dec]] closed

    Explanation   This message indicates that the UDP socket [[dec]] closed; [[dec]] is the UDP port number.

    Action This message is provided for information only.

SNMP-6-UDPSKTOPEN: UDP socket [[dec]] opened

SNMP RMON Messages

This section contains the Simple Network Management Protocol (SNMP) messages for Remote Monitoring (RMON).

SNMP-5

SNMP-5-RMONDISFAIL: Rmon Disable is progress, In another session

    Explanation   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.

    Action Try to disable RMON at a later time. If the message reappears after numerous tries, contact your technical support representative.

SNMP-5-RMONENFAIL: Rmon Enable is progress, In another session

    Explanation   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.

    Action Try to enable RMON at a later time. If the message reappears after numerous tries, contact your technical support representative.

SNMP-5-RMONNOALARM: Alarm Index [dec] is Not Saved

    Explanation   This message indicates that the Alarm Entry with [dec] Index is not saved in nonvolatile random-access memory (NVRAM); [dec] is the index of the alarmEntry.

    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-RMONNOMEM: No memory for ControlEntry

    Explanation   This message indicates that memory is full; no new RMON Tables can be installed.

    Action Release some memory by deleting some of the existing RMON entries. If the message reappears, contact your technical support representative.

SNMP-5-RMONNOSCP: Out of RMON ScpUsage

    Explanation   This message indicates that the ScpUsage for RMON is full.

    Action Contact your technical support representative.

SNMP-5-TABLEFULL: [chars] Table is Full

    Explanation   This message indicates that the [chars] Table is full; [chars] is the history, alarm, or event Table.

    Action Release some memory by deleting some of the existing RMON entries. If the message reappears, contact your technical support representative.

SNMP-5-UPDATENVRAM: UpdateNvram() failed: blockno is [dec]

SPANTREE Messages

This section contains the Spanning Tree Protocol messages.

SPANTREE-2

SPANTREE-2-CHNMISCFG: STP loop - channel [dec]/[chars] is disabled in vlan [dec]

    Explanation   This message indicates that there is a possible misconfiguration in the EtherChannel type setting (auto/desirable/on). A misconfigured channel formed, causing spanning tree loops; [dec] is the module number, [chars] is the port number, and vlan [dec] is the VLAN number.

    Action Contact your technical support representative.

SPANTREE-2-PORTADD_FAILNOMEM: [dec]/[dec] in [dec] malloc fail ([chars]) not add STP

    Explanation   This message indicates that adding a port to a given VLAN has failed because the system does not have enough memory. [dec]/[dec] is the module number/port number, [dec] is the VLAN number, and ([chars]) is the error message.

    Action Contact your technical support representative.

SPANTREE-2-PORTUNBLK: 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; [dec] is the module number, [chars] is the port number, and the second [dec] is the VLAN number. This message also indicates that the previous inconsistency has been cleared and no more inconsistencies have been detected on the port.

    Action The port should have a normal spantree state.

SPANTREE-2-RX_1QPVIDERR: Rcved pvid_inc BPDU on 1Q port [dec]/[dec] vlan [dec]

    Explanation   This message indicates that the 1Q-trunking port has received at least one 1Q-tagged spantree Bridge Protocol Data Unit (BPDU) frame with an inconsistent transmitting VLAN ID to the receiving port VLAN ID; [dec] is the module number, the second [dec] is the port number, and the third [dec] is the VLAN number.

    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-RX_BLKPORTPVID: Block [dec]/[dec] 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; [dec] is the module number, the second [dec] is the port number, the third [dec] is the receiving VLAN number, and the fourth [dec] is the peer VLAN number. This prevents traffic looping, which might be caused by the peer port VLAN inconsistency.

    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-TX_BLKPORTPVID: Block [dec]/[dec] 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; [dec] is the module number, the second [dec] is the port number, and the third [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.

    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 pvid-inconsistent state.

SPANTREE-3

SPANTREE-3-SWOVER_TOOLONG: Switchover took too much time. All STP ports restarted

    Explanation   This message indicates that the switchover process took longer than four seconds to complete. As a result, all of the STP ports are restarted.

    Action This message is provided for information only.

SPANTREE-4

SPANTREE-4-ROOTGUARDBLOCK: Port [chars] tries to become non-designated in [chars] [dec]. Moved to root-inconsistent state

    Explanation   This message is displayed whenever a rootguard-enabled port receives a superior BPDU, which moves the role of the port from designated to root or to blocking port. [chars] is the port number (a list for channel ports); the second [chars] is either VLAN when PVST+ is running, or instance when MI-STP is running; [dec] is the VLAN number or the instance number.

    Action Reconfigure STP on the switch at the other end of the link to receive inferior BPDUs on the port indicated by the first [chars].

SPANTREE-4-ROOTGUARDUNBLOCK: Port [chars] restored in [chars] [dec]

    Explanation   This message is displayed when a port that previously had an inconsistent root is moved back to a normal STP state because the switch on the other end of the link stopped sending superior BPDUs. The first [chars] is the port number (a list for channel ports); the second [chars] is either VLAN when PVST+ is running, or instance when MI-STP is running; [dec] is the VLAN number or the instance number.

    Action This message is provided for information only.

SPANTREE-4-UFAST_BRREGFAIL: Uplinkfast unable to register Ibipc port

    Explanation   This message indicates that the UplinkFast feature might not work with some Gigabit Ethernet modules.

    Action Contact your technical service representative.

SPANTREE-4-UFAST_MGETFAIL: Uplinkfast unable to get mbuf

    Explanation   This message indicates that the UplinkFast task was unable to get an memory buffer. Fast convergence may not occur for some or all stations.

    Action If this message is seen repeatedly, contact your technical support representative.

SPANTREE-4-UFAST_QFULL: Uplinkfast task does not exist or queue full

    Explanation   This message indicates that the notification of a change in a port's forwarding status failed. Fast convergence will not occur for all end stations in some VLANs.

    Action Contact your technical support representative.

SPANTREE-5

SPANTREE-5-PORTADD_FAILNONOPER: Port [dec]/[dec] in [dec] not up ([chars]) not added to STP

    Explanation   This message indicates that a port on a given VLAN has not been added to the spanning tree because the port is not active. [dec]/[dec] is the module number/port number, [dec] is the VLAN number, and ([chars]) is the error message.

    Action Try reenabling the port. Contact your technical support representative.

SPANTREE-5-PORTADD_FAILTRNONOPER: Port [dec] in [dec] not up - not added to STP

    Explanation   This message indicates that a port for a given VLAN was not added to STP because the port is not operational. Port [dec] is the failed port number, and [dec] is the VLAN number.

    Action Disable and reenable the port.

SPANTREE-5-PORTDEL_FAILNOTFOUND: [dec]/[dec] in vlan [dec] not found ([chars])

    Explanation   This message indicates that the port passed for deletion was not found in the spanning tree database; [dec]/[dec] is the module number/port number, vlan [dec] is the VLAN number, and ([chars]) is an identifier for the task that started the deletion.

    Action This message is for debugging purposes only.

SPANTREE-5-PORTDEL_FAILOUTRANGE: [dec]/[dec] - vlan [dec] out of range ([chars])

    Explanation   This message indicates that the port passed for deletion has not been deleted because the port VLAN is out of the valid range; [dec]/[dec] is the module number/port number, vlan [dec] is the VLAN number, and ([chars]) is an identifier for the task that started the deletion.

    Action This message is for debugging purposes only.

SPANTREE-5-PORTLISTEN: 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; [dec]/[chars] is the module number/port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

SPANTREE-5-TR_PORTLISTEN: trcrf [dec] in trbrf [dec] changed to Listening

    Explanation   This message indicates that the ports associated with the trcrf [dec] located in the trbrf [dec] has changed to listening; the first [dec] is the TrCRF number, and the second [dec] is the TrBRF number.

    Action This message is provided for information only.

SPANTREE-5-UFAST_PORTFWD: 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 through with the UplinkFast feature; [dec]/[chars] is the module number/port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

SPANTREE-6

SPANTREE-6-PORTBLK: 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; [dec]/[chars] is the module number/port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

SPANTREE-6-PORTFWD: 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; [dec]/[chars] is the module number/port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

SPANTREE-6-PORTLEARN: 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; [dec]/[chars] is the module number/port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

SPANTREE-6-RX_1QNON1QTRUNK: Rcved 1Q-BPDU on non-1Q-trunk port [dec]/[dec] 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; [dec] is the module number, the second [dec] is the port number, and the third [dec] is the VLAN number.

    Action Either reconfigure the non-1Q-trunking port into a 1Q-trunking port, or reconfigure the peer 1Q-trunking port into the corresponding non-1Q-trunking port.

SPANTREE-6-RX_1QNONTRUNK: Rcved 1Q-BPDU on non-trunk port [dec]/[dec] vlan [dec]

    Explanation   This message indicates that the nontrunking port has received at least one 1Q-tagged spantree BPDU frame on the receiving VLAN; [dec] is the module number, the second [dec] is the port number, and the third [dec] is the VLAN number.

    Action Either reconfigure the nontrunking port into a 1Q-trunking port, or reconfigure the peer 1Q-trunking port into a nontrunking port.

SPANTREE-6-RX_INFBPDU: Received inferior BPDU on port [dec]/[chars] in vlan [dec]

    Explanation   This message indicates that the port is receiving BPDUs; [dec]/[chars] is the module number/port number, and vlan [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.

    Action This message is provided for information only.

SPANTREE-6-RX_RLQREPLY: 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]; [dec]/[chars] is the module number/port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

SPANTREE-6-RX_RLQREQ: 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]; [dec]/[chars] is the module number/port number, and vlan [dec] is the VLAN number.

    Action This message is provided for information only.

SPANTREE-6-SSTP_PORTBLK: Block [dec]/[dec] 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; [dec] is the module number, the second [dec] is the port number, and the third [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.

    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-6-TR_MSGAGEEXPIRY: Msg Age timer expired on trcrf [dec] in trbrf [dec]

    Explanation   This message indicates that the trcrf [dec] in trbrf [dec] has not received BPDUs for message age time; the first [dec] is the port number, and the second [dec] is the VLAN number. The command show spantree for the VLAN should show the message age.

    Action If this message is seen too often for the same VLAN and port, a fault is indicated. Contact your technical support representative.

SPANTREE-6-TR_PORTBLK: trcrf [dec] in trbrf [dec] changed to blocking

    Explanation   This message indicates that the Token Ring Concentrator Relay Function (TrCRF) port corresponding to the Token Ring Bridge Relay Function (TrBRF) VLAN has changed to blocking; trcrf [dec] is the TrCRF port number, and trbrf [dec] is the TrBRF VLAN number.

    Action This message is provided for information only.

SPANTREE-6-TR_PORTFWD: 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; trcrf [dec] is the TrCRF port number, and trbrf [dec] is the TrBRF VLAN number.

    Action This message is provided for information only.

SPANTREE-6-TR_PORTLEARN: trcrf [dec] in trbrf [dec] changed to Learning

    Explanation   This message indicates that the TRCRF port located in the TRBRF VLAN has changed to learning; the first [dec] is the port number, and the second [dec] is the VLAN number.

    Action This message is provided for information only.

SPANTREE-7

SPANTREE-7-MSGAGEEXPIRY: 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 vlan [dec] is the VLAN number. The port is made a designated port.

    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. Because this message is per VLAN, multiple messages for different VLANs are normal. Contact your technical support representative.

SPANTREE-7-PORTADD_DISABLE: [dec]/[dec] in [dec] add stp - disable O[dec] E-[dec] S-[dec]

    Explanation   This message indicates that a port for a given VLAN has been added to the spanning tree in a disable state; [dec]/[dec] is the module number/port number, [dec] is the VLAN number, O[dec] is operational or nonoperational, E-[dec] is enabled or disabled, and S-[dec] is supported or nonsupported.

    Action Examine the condition of the port. Contact your technical support representative.

SPANTREE-7-PORTADD_FAILACTIVEVLAN: [dec]/[dec] in [dec] add fail A-[dec] ([chars])

    Explanation   This message indicates that a port on a given VLAN has not been added to STP because the addSTP flag is set to false; [dec]/[dec] is the module number/port number, [dec] is the VLAN number, A-[dec] is the addSTP flag value, and ([chars]) is the error message.

    Action This message is for debugging purposes only.

SPANTREE-7-PORTADD_FAILAGPORT: [dec]/[dec] in [dec] agport=0 ([chars]) not add STP

    Explanation   This message indicates that a port for a given VLAN has failed to add to STP because the corresponding AgPort number is 0; [dec]/[dec] is the module number/port number, [dec] is the VLAN number, and ([chars]) is the error message.

    Action Contact you technical support representative.

SPANTREE-7-PORTADD_FAILCLCFG: [dec]/[dec] in [dec] cl-cfg ([chars]) not add STP

    Explanation   This message indicates that adding a port for a given VLAN has failed because a clear configuration operation is running on the system. [dec]/[dec] is the module number/port number, [dec] is the VLAN number, and ([chars]) is the message.

    Action Disable and reenable the port. If that fails to resolve the problem, contact your technical support representative.

SPANTREE-7-PORTADD_FAILINACTIVEVLAN: [dec]/[dec] in [dec] add fail S-[dec] ([chars])

    Explanation   This message indicates that a port for a given VLAN has failed to be added to spanning tree because the VLAN is inactive; [dec]/[dec] is the module number/port number, [dec] is the VLAN number, S-[dec] is supported or nonsupported, and [chars] is the error message.

    Action Activate the VLAN to add the port. Contact your technical support representative.

SPANTREE-7-PORTDEL_FAILEMPTYVLAN: [dec]/[dec] - vlan [dec] empty ([chars])

    Explanation   This message indicates that the VLAN referred to for port deletion does not contain the ports; [dec]/[dec] is the module number/port number, vlan [dec] is the VLAN number, and ([chars]) is an identifier for the task that started the deletion.

    Action This message is for debugging purposes only.

SPANTREE-7-PORTDEL_SUCCESS: [dec]/[dec] removed from vlan [dec] ([chars])

    Explanation   This message indicates that the deletion has completed successfully; [dec]/[dec] is the module number/port number, vlan [dec] is the VLAN number, and ([chars]) is an identifier for the task that started the deletion.

    Action This message is for debugging purposes only.

SPANTREE-7-PORTDEL_SUCCESSFROMCHN: [dec]/[dec] in vlan [dec] deleted - channel still on ([chars])

SYS Messages

This section contains the system (SYS) messages, including system semaphore messages.

SYS-0

SYS-0-MOD_ATMEXCEED: Max limit of atm/rsm card in the system exceeded

    Explanation   This message indicates that Catalyst 5000 family switch has more than seven RSM and ATM modules installed.

    Action Remove ATM or RSM modules from the switch until there are a maximum of seven total.

SYS-0-MOD_TEMPMAJORFAIL: Module [dec] major temperature threshold exceeded

    Explanation   This message indicates that the module temperature sensor has detected a temperature exceeding the major temperature threshold. The module shuts down after a 5-minute time delay has expired. If the temperature drops below the major threshold level before the time delay expires, the shutdown is canceled; [dec] is the slot number of the module that detected the elevated temperature.

    Action This message is provided for information only.

SYS-0-MOD_TEMPMAJORRECOVER: Module [dec] major temperature threshold recovered

    Explanation   This message indicates that the module temperature has dropped below the major temperature threshold. The module shutdown has been canceled and the system returns to normal operation; [dec] is the module slot number.

    Action This message is provided for information only.

SYS-0-SUP_TEMPMAJORFAIL: Supervisor in slot [dec] [chars] major temperature threshold exceeded

    Explanation   This message indicates that the supervisor engine's temperature sensor has detected a temperature exceeding the major temperature threshold. The supervisor engine shuts down after a 5-minute time delay has expired. If the temperature drops below the major threshold level before the time delay expires, the shutdown is canceled; [dec] is the slot number of the supervisor engine that detected the elevated temperature, and [chars] is the name of the submodule on the supervisor engine.

    Action This message is provided for information only.

SYS-0-SUP_TEMPMAJORRECOVER: Supervisor in slot [dec] [chars] major temperature threshold recovered

    Explanation   This message indicates that the supervisor engine's temperature has dropped below the major temperature threshold. The supervisor engine shutdown has been canceled and the system returns to normal operation; [dec] is the supervisor engine slot number, and [chars] is the name of the submodule on the supervisor engine.

    Action This message is provided for information only.

SYS-0-SYS_SCHEDRESET: Schedule reset will happen in [chars]

    Explanation   This message indicates that a reset is scheduled to occur sometime in the future; [chars] is the amount of time left before the reset happens. The value can be 2 hours, 1 hour, 30 minutes, 5 minutes, or 1 minute.

    Action This message is provided for information only.

SYS-0-SYS_TEMPMAJORFAIL: Chassis major temperature threshold exceeded

    Explanation   This message indicates that the chassis temperature sensor has detected a temperature exceeding the major temperature threshold. The system shuts down after a 5-minute time delay has expired. If the temperature drops below the major threshold level before the time delay expires, the system shutdown is canceled.

    Action Contact your technical support representative.

SYS-0-SYS_TEMPMAJORRECOVER: Chassis major temperature threshold recovered

    Explanation   This message indicates that the chassis temperature has dropped below the major temperature threshold. The automatic system shutdown has been canceled and the system returns to normal operation.

    Action This message is provided for information only.

SYS-0-VTT_MAJORFAIL: VTT major alarm. Two VTT modules failed

    Explanation   This message indicates that at least two of the three voltage termination (VTT) modules have failed. A minimum of two VTT modules are required for the system to function properly. The switching bus is disabled, and the supervisor engine is accessible through the console port.

    Action Replace the bad VTT modules. Contact your technical support representative.

SYS-0-TEMP_CRITFAIL: Temp critical failure

    Explanation   This message indicates that 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.

    Action Power down the system and contact your technical support representative.

SYS-0-TEMP_CRITOK: Temp critical okay

    Explanation   This message indicates that the internal temperature has dropped below 70° C (158° F); this message applies only to the redundant supervisor engine in the switch.

    Action This message is provided for information only.

SYS-0-TEMP_CRITRECOVER: Temp critical recovered

    Explanation   This message indicates that 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.

    Action This message is provided for information only.

SYS-1

SYS-1-MOD_INVALIDSEQ: Bus asic invalid sequence occurred on module [dec] (asic=[dec], srcidx=0x[hex], seq=[dec])

    Explanation   This message is generated during system boot on systems with redundant supervisor engines. As the system boots up, the supervisor engine in slot 2 runs diagnostics on all of the modules to verify that it can be the standby supervisor engine. This supervisor engine then turns control over to the supervisor engine in slot 1.

    During the transition, there are no packet transfers on the backplane. There is a sequence number associated with each packet transferred on the backplane. The modules remember the last sequence number N sent. When the active supervisor engine takes over and begins sending packets, it does not start with sequence number N+1. The sequence error is detected by the modules that generate the error message. Module [dec] is the module number detecting the error, asic=[dec] is the asic number, srcidx=[hex] is the error string, and seq=[dec] is the sequence number.

    Action This message can occur in systems with redundant supervisor engines. It should not occur in systems with only one supervisor engine. This message is provided for information only.

SYS-1-MOD_MACBAD: Module [dec] has invalid MAC address, [chars]

    Explanation   This message indicates that the supervisor engine module [dec] has an invalid MAC address. [dec] is the module number and [chars] is one of the following text messages: remains offline or bypass enabled.

    Action This message is provided for information only, but might indicate the MAC address of the supervisor engine 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-MOD_PWRSPROMFAIL: Power mgmt sprom failure for module [dec]

    Explanation   This message indicates that a serial EPROM read on a module has failed; [dec] is the module number. The module is powered off.

    Action Contact your technical support representative.

SYS-1-SYS_IDPROMBAD: Chassis idprom data invalid

    Explanation   This message indicates the chassis serial EEPROM data is invalid.

    Action Contact your technical support representative.

SYS-1-SYS_MACBAD: Chassis has invalid MAC address, using module MAC address

    Explanation   This message indicates the chassis has an invalid MAC address.

    Action This message is provided for information only, but could indicate that the MAC address of the chassis is the same as the default MAC address (00-40-4b-ff-00-00). Contact your technical support representative.

SYS-1-SYS_NORMPWRMGMT: System in normal power management operation

    Explanation   This message indicates that the system is operating in normal power management mode; both active and standby supervisor engines have equal power requirements.

    Action This message is provided for information only.

SYS-1-SYS_OVERPWRRTNG: System drawing more power than the power supply rating

    Explanation   This message indicates that the system is drawing more power than the power supply rating. The power management LED is lit red. This condition can occur only when the system is fully configured and the supervisor engines are drawing unequal power.

    Action Contact your technical support representative.

SYS-1-SYS_SCHEDRESETCANCEL: Schedule reset cancelled by [chars]

    Explanation   This message indicates that a scheduled rest has been cancelled by either an internal error or by the user, where [chars] is user or internal error.

    Action This message is provided for information only.

SYS-2

SYS-2-DTP_MODDOWN: Module Down: cfg port trunk-hw failed [dec]/[dec]

    Explanation   This message indicates that the port trunk hardware failed to set because the module is not online; [dec]/[dec] is the module number/port number.

    Action Call your technical support representative.

SYS-2-DTP_MODEMPTY: Module Empty: cfg port trunk-hw failed [dec]/[dec]

    Explanation   This message indicates that the port trunk hardware failed to set because the module is empty; [dec]/[dec] is the module number/port number.

    Action Call your technical support representative.

SYS-2-DTP_MODSTBY: Module standby: cfg port trunk-hw failed [dec]/[dec]

    Explanation   This message indicates that trunk hardware on the port failed to set because the module is in standby; [dec]/[dec] is the module number/port number.

    Action Call your technical support representative.

SYS-2-DTP_SCPFAIL: SCP failure: cfg port trunk-hw failed [dec]/[dec]

    Explanation   This message indicates that the port trunk hardware failed to set because the SCP message was not sent successfully; [dec]/[dec] is the module number/port number.

    Action Call your technical support representative.

SYS-2-FAN_FAIL: Fan failed

    Explanation   This message indicates the chassis fan failed.

    Action Replace the fan.

SYS-2-FAN_OK: Fan okay

    Explanation   This message indicates the chassis fan tray was plugged back in or returned to a proper state.

    Action This message is provided for information only.

SYS-2-MOD_TEMPMINORFAIL: Module [dec] minor temperature threshold exceeded

    Explanation   This message indicates that the module temperature sensor has detected a temperature greater than the minor temperature threshold; [dec] is the slot number of the module that detected the elevated temperature.

    Action This message is provided for information only.

SYS-2-MOD_TEMPOK: Module [dec] temperature OK

    Explanation   This message indicates the module temperature has dropped below the minor temperature threshold.

    Action This message is provided for information only.

SYS-2-P2_LogGalInsufficientFansShutdown: Resetting linecards due to too few working fans

    Explanation   This message indicates that one or more fans in the fan tray or fans in the power supplies has failed. The line cards have been reset to reduce heat generation.

    Action This message is provided for information only.

SYS-2-P2_LogGalInsufficientPowerShutdown: Resetting linecards due to insufficient power

    Explanation   This message indicates that the system was running on less than the required number of power supplies for more than the allowed time. The line cards have been reset to reduce power consumption.

    Action This message is provided for information only.

SYS-2-P2_LogGalOverheatingShutdown: Resetting linecards due to critical temperature

    Explanation   This message indicates that the critical temperature for the system has been exceeded. The line cards have been reset to reduce heat generation.

    Action This message is provided for information only.

SYS-2-P2_LogGalSeepromInvalid: Module's serial eeprom is invalid, must manually program

    Explanation   This message indicates that the contents of the supervisor engine's serial EEPROM is invalid, and the switch cannot come up.

    Action This situation can happen if the read failed because the supervisor engine is not seated correctly in the slot. Try removing and reinserting the supervisor engine. If that action does not work, try cycling the power on the switch.

SYS-2-P2_LogStoreOutOfChunks: Out of chunks of memory

    Explanation   This message indicates that the system has run out of memory.

    Action Contact your technical support representative.

SYS-2-P2_LogVc5WatchdogTriggered: NMP Watchdog triggered, system will now reset, please wait...

    Explanation   This message indicates that the NMP management software has not reset the watchdog timer. An infinite loop might exist or the system might have crashed.

    Action Contact your technical support representative.

SYS-2-PS_FAIL: Power supply [dec] failed

    Explanation   This message indicates that the power supply failed; [dec] is the power supply number.

    Action Replace the indicated power supply.

SYS-2-PS_FANFAIL: Power supply [dec] fan failed

    Explanation   This message indicates the power supply [dec] fan failed; [dec] is the power supply number.

    Action Replace the indicated power supply fan.

SYS-2-PS_NFANFAIL: Power supply [dec] and power supply fan failed

    Explanation   This message indicates the power supply [dec] and power supply fan failed; [dec] is the power supply number.

    Action Replace the indicated power supply and fan.

SYS-2-PS_OK: Power supply [dec] okay

    Explanation   This message indicates the power supply has been turned on or has returned to a proper state; [dec] is the power supply number.

    Action This message is provided for information only.

SYS-2-SUP_TEMPMINORFAIL: Supervisor in slot [dec] [chars] minor temperature threshold exceeded

    Explanation   This message indicates that the supervisor engine's temperature sensor has detected a temperature greater than the minor temperature threshold; [dec] is the slot number of the supervisor engine that detected the elevated temperature, and [chars] is the name of the submodule on the supervisor engine.

    Action This message is provided for information only.

SYS-2-SUP_TEMPOK: Supervisor in slot [dec] [chars] temperature OK

    Explanation   This message indicates the supervisor engine's temperature has dropped below the minor temperature threshold.

    Action This message is provided for information only.

SYS-2-SYS_TEMPMINORFAIL: Chassis minor temperature threshold exceeded

    Explanation   This message indicates that the chassis temperature sensor has detected a temperature greater than the minor temperature threshold.

    Action This message is provided for information only.

SYS-2-SYS_TEMPOK: Chassis temperature OK

    Explanation   This message indicates that the chassis temperature has dropped below the minor temperature threshold.

    Action This message is provided for information only.

SYS-2-TEMP_HIGHFAIL: Temp high failure

    Explanation   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.

    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 5 minutes.

SYS-2-TEMP_HIGHOK: Temp high okay

    Explanation   This message indicates the internal temperature has dropped below 50° C (122° F).

    Action This message is provided for information only.

SYS-2-VTT_MINORFAIL: VTT minor alarm. A VTT module failed

    Explanation   This message indicates that one of the three VTT modules has failed. The system can function correctly with the remaining two VTT modules.

    Action This message is provide for information only.

SYS-2-VTT_OK: VTT modules recovered from failure

    Explanation   This message indicates that one or more VTT modules previously identified as failing are now operating correctly.

    Action Replace the bad VTT modules.

SYS-3

SYS-3-LLC_IPC2REGFAIL: Failed to register to Ibipc2

    Explanation   This message indicates that the supervisor engine cannot communicate with the module for Layer 2 protocol packets.

    Action Contact your technical support representative.

SYS-3-LLC_REGTBLEXIST: Entry exists in LLC registration table.

    Explanation   This is a debug message for Cisco development purposes.

    Action Ignore this message.

SYS-3-LLC_REGTBLFULL: Registration table full

    Explanation   This message indicates that a Layer 2 protocol cannot be registered. The supervisor engine is unable to receive this protocol's packets.

    Action Contact your technical support representative.

SYS-3-LLC_REGTBLNOTEXIST: Entry not exists in LLC registration table.

    Explanation   This is a debug message for Cisco development purposes.

    Action Ignore this message.

SYS-3-LLC_SCPSTATNOTOK: Send scp message to module [dec] status [dec]

    Explanation   This is a debug message for Cisco development purposes.

    Action Ignore this message.

SYS-3-LLC_SENDSCPFAIL: Send scp message to module [dec] failed

    Explanation   This is a debug message for Cisco development purposes.

    Action Ignore this message.


Note The next message appears as four lines.

SYS-3-MOD_CFGMISMATCH1: Module [dec] configuration mismatch [chars]

SYS-3-MOD_CFGMISMATCH2: *Config:[chars]

SYS-3-MOD_CFGMISMATCH3: *Actual:[chars]

SYS-3-MOD_CFGMISMATCH4: Insert config type module or do a 'clear config [dec]'

    Explanation   These messages resulted from a module being inserted into a slot that had been configured for another module type. Module [dec] is the module number; [chars] is either an empty field or disabled ports; 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.

    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-MOD_DIAG: Module [dec] is in offline diagnostic mode

    Explanation   This message indicates module [dec] is in offline diagnostics mode; [dec] is the module number.

    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-MOD_DNLDWAIT: Module [dec] waiting for download

    Explanation   This message indicates the module [dec] is waiting for download; [dec] is the module number.

    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-MOD_FAIL: Module [dec] failed to come online

    Explanation   This message indicates that module [dec] failed to come online; [dec] is the module number.

    Action This message is provided for information only.


Note The next message appears as four lines.

SYS-3-MOD_FAILREASON: Module [dec] failed due to [chars]

[chars]

[chars]

[chars]

    Explanation   This message indicates module [dec] has failed due to [chars]. [dec] is the module number and [chars] is one of the following: CPU Initialization Error, Memory Test Failed, Boot Checksum Verification Failed, SPROM Checksum Verification Failed, EOBC Loopback Test Failed, LTL-A Error, Flash Erase/Write Error, Pinnacle CBL Error, Pinnacle Packet Buffer Error, Pinnacle TLB Error, or Unknown or Undocumented Error.
    The first [chars] line is "Ports disabled" if the module is non-ATM/Route Switch Module (RSM) (non-IOS). The second [chars] line is a description of the module type configured in NVRAM. The third [chars] line is a description of the module type inserted in the slot.

    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-MOD_MINORFAIL: Minor problem in module [dec]

    Explanation   This message indicates a module [dec] failed the self-test; [dec] is the module number.

    Action Try resetting the module. If this message reappears, insert a new module; if this message reappears, contact your technical support representative.

SYS-3-P2_LogBrBadGbic: Port [chars]: Gbic's seeprom is bad, try reinserting: vendor: [chars], p/n: [chars], s/n: [chars]

    Explanation   This message indicates that a GBIC with a serial EEPROM has been detected and that an EEPROM contents read operation succeeded but the contents are not valid. The port [chars] is the location of the defective GBIC; the remaining three [chars] fields contain information from the read operation including GBIC vendor, GBIC part number, and GBIC serial number.

    Action Try reseating the GBIC in the port. If that action does not work, replace the GBIC.

SYS-3-P2_LogBrGbicSeepromReadFailed: Failed to read gbic serial eeprom on port [chars], try reinserting

    Explanation   This message indicates that a GBIC has been detected in port identified in by the [chars] field, but a serial EEPROM read operation failed. It is necessary to read the EEPROM to determine the type of GBIC installed.

    Action Try reseating the GBIC. If that action does not work, replace the GBIC.

SYS-3-P2_LogBrSeepromReadFailedAfterWrite: Wrote module's serial eeprom, but it read back incorrectly

    Explanation   This message indicates that after writing to a module's serial EEPROM in response to a CLI request, the wrong data was read back from the serial EEPROM.

    Action Try reseating the module. If that action does not work, contact your technical support representative.

SYS-3-P2_LogEbmCantAllocateEbmPort: No EbmPort memory to allocate EbmPort for PimPort [chars]

    Explanation   This message indicates that there is not sufficient memory to allocate space for information associated with the port; [chars] is the port number.

    Action Contact your technical support representative.

SYS-3-P2_LogEbmCantAllocateIeNode: No interposition table memory to add entry for addr [ether]

    Explanation   This message indicates that there is not sufficient memory to allocate space for the internal data structure; [ether] is the host address.

    Action Contact your technical support representative.

SYS-3-P2_LogEbmCantAllocatePortHostEntry: No port host table memory to add entry for addr [ether]

    Explanation   This message indicates that there is not sufficient memory to allocate space for the internal data structure; [ether] is the address that cannot be added to the host table.

    Action Contact your technical support representative.

SYS-3-P2_LogEbmCantAllocateVlanGroupEntry: No vlan group table memory to add entry for addr [ether]

    Explanation   This message indicates that there is not sufficient memory to support additional group entries; [ether] is the address that cannot be added to the group table.

    Action Contact your technical support representative.

SYS-3-P2_LogEbmCantAllocateVlanHostEntry: No vlan host table memory to add entry for addr [ether]

    Explanation   This message indicates that there is not sufficient memory to support additional host addresses; [ether] is the host address that could be entered into the table.

    Action Contact your technical support representative.

SYS-3-P2_LogGalBadGbic: Port [chars]: Gbic's seeprom is bad, try reinserting: vendor: [chars], p/n: [chars], s/n: [chars]

    Explanation   This message indicates that a GBIC with a serial EEPROM has been detected in the port; port [chars] is the port number. A read of the serial EEPROM contents was successful, but the contents were not valid. The vendor [chars], part number [chars], and the serial number [chars] contain information read from the serial EEPROM.

    Action Contact your technical support representative.

SYS-3-P2_LogGalBadMacRangeInSprom: Module [dec] serial eeprom contains [dec] mac addresses, but needs [dec]

    Explanation   This message indicates that the number of MAC addresses contained in the serial EEPROM does not correspond with the number of ports on the module front panel. The first [dec] is the module number, the second [dec] is the number of MAC addressses read from the serial EEPROM, and the third [dec] is the correct number of MAC addresses needed.

    Action Contact your technical support representative.

SYS-3-P2_LogGalDaughterCardSeepromReadFailed: Failed to read the serial eeprom on module [dec], daughter card [dec]

    Explanation   This message indicates that multiple attempts to read the serial EEPROM on a module daughter card have failed. Because the read operation has failed, the daughter card remains offline; module [dec] is the module number and the daughter [dec] is the daughter card number.

    Action Try removing and reinstalling the daughter card on the module.

SYS-3-P2_LogGalGbicSeepromReadFailed: Failed to read gbic serial eeprom on port [chars], try reinserting

    Explanation   This message indicates that a GBIC with a serial EEPROM has been detected, but reading the EEPROM has failed. The port [chars] field indicates the port the GBIC is installed in.

    Action Try removing and reinstalling the GBIC.

SYS-3-P2_LogGalIlcS2wCommunicationError: Communication with ILC over S2W failed, reason [dec]

    Explanation   This message indicates that the logical configuration protocol between the supervisor engine and an intelligent line card processor failed due to I2C failure; [dec] is the message number.

    Action Contact your technical support representative.

SYS-3-P2_LogGalLinecardSeepromReadFailed: Failed to read module [dec] serial eeprom, try reinserting module

    Explanation   This message indicates that the serial EEPROM read operation on the module failed; [dec] is the module number.

    Action Try reseating the module in the slot.

SYS-3-P2_LogGalLinecardSeepromWriteFailed: Failed to write module [dec] serial eeprom

    Explanation   This message indicates that the serial EEPROM write operation on the module failed; [dec] is the module number.

    Action Try reseating the module in the slot.

SYS-3-P2_LogGalUnknownLinecard: Unknown module (fru minor type [dec]) in slot [dec]

    Explanation   This message indicates that an unknown type of module has been detected in the system. The first [dec] is the FRU minor type number, and the second [dec] is the slot number that the unknown module occupies.

    Action A system software upgrade might be required for this module. Contact your technical service representative.

SYS-3-PKTBUFBAD: Port [dec]/[dec] failed packet buffer test. This port [chars] automatically disabled for future use.

    Explanation   This message indicates that the packet buffer test detected a corrupted packet buffer on a module port; [dec]/[dec] is the module number/port number where the test failed and [chars] is faulty.

    Action This message is provide for information only.

SYS-3-PORT_DEVICENOLINK: Device on port [dec]/[dec] powered but no link up

    Explanation   This message indicates that a device powered by a port using inline power does not give the expected link-up indication within the allotted amount of time; [dec]/[dec] is the module number/port number. The power to the port is turned off.

    Action This message is provided for information only.

SYS-3-PORT_NO64POLL1: SWPoll64bCnt task exits: failed to malloc scp queue buffers

    Explanation   This message indicates that your switch may be out of memory and that the 64-bit counters have not been polled. You may need to increase DRAM size.

    Action Contact your technical support representative.

SYS-3-PORT_NO64POLL2: Memory allocation fail: no 64 bit counters for module [dec] will be available

    Explanation   This message indicates that your switch may be out of memory and that the 64-bit counters have not been polled; [dec] is the module number. You may need to increase DRAM size.

    Action Contact your technical support representative.

SYS-3-PORT_NOPOWERAVAIL: Device on port [dec]/[dec] will remain unpowered

    Explanation   This message indicates that there is not enough system power available to power up a port; [dec]/[dec] is the module number/port number. The port remains unpowered until enough power becomes available to power up the port.

    Action This message is provided for information only.

SYS-3-PORT_SSUPFAIL: Failed to bring up ports on standby supervisor

    Explanation   This message indicates either the Serial Link Protocol (SLP) channel between the active and standby supervisor engines is broken or that one or more ports on the standby supervisor engine are broken.

    Action Reset the standby supervisor engine. If that does not work, reset the system or call your technical support representative.

SYS-3-SEM_HOLDMANY: Task [chars] holds too many semaphores

    Explanation   This message indicates that a task is holding too many semaphores; [chars] is the name of the task.

    Action This is an internal error. Contact your technical support representative.

SYS-3-SEM_IDBAD: Invalid sem_id:[hex] ([chars],[chars])

    Explanation   This message indicates an invalid semaphore is being requested by the specified task's function; [hex] is the semaphore ID value, the first [chars] is the task name, and the second [chars] is the function name.

    Action The system has an internal error if this message is shown; contact your technical support representative.

SYS-3-SEM_KERNELWAIT: Kernel wait for semaphore [chars]

    Explanation   This message indicates that the kernel task requests a semaphore; [chars] is the semaphore name.

    Action This is an internal error. Contact your technical support representative.

SYS-3-SEM_MAGICNUMBAD: Invalid 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; [hex] is the magic number, the first [chars] is the task name, and the second [chars] is the function name.

    Action The system has an internal error if this message is shown; contact your technical support representative.

SYS-3-SEM_NOPID: Dequeued pid([dec]) not found

    Explanation   This message indicates the task being removed from a semaphore's waiting list does not exist; [dec] is the task ID number.

    Action The system has an internal error if this message is shown; contact your technical support representative.

SYS-3-SEM_NOWAIT: No waiting task to dequeue

    Explanation   This message indicates the semaphore could not find its waiting list while a task is to be removed from it.

    Action The system has an internal error if this message is shown; contact your technical support representative.

SYS-3-SEM_REQBAD: Task [chars] waits for the same semaphore [chars]

    Explanation   This message indicates that a task was trying to request the same semaphore it already holds; [chars] is the name of the task, and semaphore [chars] is the name of the semaphore.

    Action This is an internal error. Contact your technical support representative.

SYS-3-SPAN_MEMALLOCFAIL: Failed to allocate memory in span [dec]

    Explanation   This message indicates that memory allocation failed in SPAN code; [dec] specifies a location marker in the code.

    Action This is an internal error. Contact your technical support representative.

SYS-3-SUP_ACONNFAIL: [chars] unable to connect with standby

    Explanation   This message indicates [chars] is unable to establish a TCP/IP connection with the standby supervisor engine; [chars] is the task name on the active supervisor engine.

    Action Perform a system reset. If this message reappears, contact your technical support representative.

SYS-3-SUP_AIMGCPYFAIL: [chars] unable to copy flash into DRAM

    Explanation   This message indicates [chars] is unable to uncompress the Flash code and download into DRAM; [chars] is the task name.

    Action This condition is possibly due to a bad or corrupted Flash; contact your technical support representative.

SYS-3-SUP_AIMGDIFF: The nvram update tasks will not be running

    Explanation   This message indicates the NVRAM update task is not running.

    Action Perform a system reset. If the message reappears, contact your technical support representative.

SYS-3-SUP_AIMGDIFF1: Module [dec] runtime image differs from flash image

    Explanation   This message indicates the runtime image of module [dec] differs from the Flash image; [dec] is the module number. This indicates that the NVRAM update task is not running and a system reset must be performed to correct the problem.

    Action Perform a system reset. If this message reappears, contact your technical support representative.

SYS-3-SUP_AIMGDIFF2: Please reset the system to rectify the problem

    Explanation   This message indicates a system reset must be performed to correct a problem.

    Action Perform a system reset. If the message reappears, contact your technical support representative.

SYS-3-SUP_AIMGTOOBIG: [chars] image is larger than reserved memory

    Explanation   This message indicates that the image file to synchronize is too large to fit into the active supervisor engine buffer; [chars] is the task name.

    Action Contact your technical support representative.

SYS-3-SUP_AOUTOFSYNC: [chars] standby is out of sync

    Explanation   This message indicates that the active supervisor engine and the standby supervisor engine communications are out of synchronization; [chars] is the task name.

    Action Contact your technical support representative.

SYS-3-SUP_APENDINGCLI: The command [chars] did not execute completely before the HA switchover

    Explanation   This message indicates that the supervisor engine command currently being executed did not finish executing before the High Availability (HA) switchover; [chars] is the command line that was not executed.

    Action Reexecute the failed command.

SYS-3-SUP_ARECVFAIL: [chars] unable to receive data from standby

    Explanation   This message indicates that an error occurred during Flash code copy from the [chars] standby to the active supervisor engine; [chars] is the active supervisor engine.

    Action The TCP/IP connection might be broken due to a problem in the system. Contact your technical support representative.

SYS-3-SUP_ASEARLDIFF: Active and standby supervisors are of different earl types

    Explanation   This message indicates that the redundant supervisor engines have incompatible forwarding engine types. With this condition, the synchronization of Flash and NVRAM configuration is disabled.

    Action Contact your technical support representative.

SYS-3-SUP_ASENDFAIL: [chars] unable to send data to standby

    Explanation   This message indicates that an error occurred during Flash code copy from the [chars] active to the standby supervisor engine; [chars] is the active supervisor engine.

    Action The TCP/IP connection might be broken due to a problem in the system. Contact your technical support representative.

SYS-3-SUP_ASIMGDIFF: Active supervisor card is running a different version of NMP image

    Explanation   This message indicates that the active supervisor engine is running a different Network Management Processor (NMP) image version than the standby supervisor engine.

    Action Check the versions of NMP software being run on the active and standby supervisor engines. This message is provided for information only.

SYS-3-SUP_ASMSGUNKNOWN: [chars] unknown message received

    Explanation   This message indicates the standby supervisor engine received an unknown TCP/IP message from the active supervisor engine; [chars] is the standby supervisor engine.

    Action Contact your technical support representative.

SYS-3-SUP_ASTATBAD: [chars] status failed received from standby

    Explanation   This message indicates the standby supervisor engine was unable to process a TCP/IP request sent by the active supervisor engine; [chars] is the task name.

    Action There might be a problem with the standby supervisor engine; contact your technical support representative.

SYS-3-SUP_ASTYPEDIFF: Active and standby supervisors are of different card types

    Explanation   This message indicates that the system has detected a difference between the active and standby supervisor engine types. This message can also mean that there is a difference between ASIC types on the active and standby supervisor engines.

    Action This message is provided for information only.

SYS-3-SUP_CFGNOSYNC: Nvram synchronization will not happen

    Explanation   This message indicates that the redundant supervisor engines in the chassis do not have the same type of EARL or supervisor engines.

    Action Make sure that the redundant supervisor engines have the same type of EARL board and the redundant supervisor engines are the same type.

SYS-3-SUP_DIFFBOOTIMAGE: Supervisor's boot images are not identical ([chars])

    Explanation   This message indicates that the boot versions of the active and standby supervisor engines are different; [chars] can be high version, low version, or timestamp indicating where the mismatch occured.

    Action Contact your technical support representative.

SYS-3-SUP_DNLDAREAEXCEED: Download aborted. File size larger than download buffer

    Explanation   This message indicates that the file size exceeds the buffer size. Check that the image is correct.

    Action Contact your technical support representative.

SYS-3-SUP_IMGNOSYNC: Flash synchronization will not happen

    Explanation   This message indicates that the redundant supervisor engines in the chassis do not have the same type of EARL or supervisor engines.

    Action Make sure the redundant supervisor engines have the same type of EARL board, and the redundant supervisor engines are the same type.

SYS-3-SUP_NOSTANDBYSUP: No standby supervisor in system

    Explanation   This message indicates that the task reset mindown could not be executed because the system does not have a standby supervisor engine installed. Reset mindown only works on systems with redundant supervisor engines.

    Action This message is provided for information only.

SYS-3-SUP_NVQUEUE: NVRAM Queue not empty

    Explanation   This message indicates that the NVRAM queue is not empty.

    Action This message is provided for information only.

SYS-3-SUP_RESETMINDOWNNOPROC: Unable to create reset mindown process

    Explanation   This message indicates that the create process failed to create the reset mindown task.

    Action This message is provided for information only.

SYS-3-SUP_RESETMINFAILED: Reset mindownload failed

    Explanation   This message indicates that the active supervisor engine failed to reset itself. Another error message might be generated before this message, which can provide additional information as to why the active supervisor engine failed to reset itself.

    Action This message is provided for information only.

SYS-3-SUP_SACCEPTFAIL: [chars] standby task accept call failed

    Explanation   This message indicates that the TCP/IP accept call failed; [chars] is the standby supervisor engine. In this case, the duplicate Flash and NVRAM synchronization tasks do not run.

    Action Contact your technical support representative.

SYS-3-SUP_SBINDFAIL: [chars] standby task bind call failed

    Explanation   This message indicates that the TCP/IP bind call failed; [chars] is the standby supervisor engine. In this case, the duplicate Flash and NVRAM synchronization tasks do not run.

    Action Contact your technical support representative.

SYS-3-SUP_SBYSUPNOTONLINE: Failed to bring standby supervisor online

    Explanation   This message indicates that the standby supervisor engine did not come online. The reset mindown task is aborted.

    Action This message is provided for information only.

SYS-3-SUP_SBYSUPSLPFAILED: Unable to communicate with standby using SLP

    Explanation   This message indicates that SLP communication failed between the active and standby supervisor engines.

    Action This messge is provided for information only.

SYS-3-SUP_SDNLDNOSPACE: [chars] image larger than standby supervisor reserved memory

    Explanation   This message indicates that the image file to synchronize is too large to fit into the standby supervisor engine buffer; [chars] is the task name.

    Action Contact your technical support representative.

SYS-3-SUP_SIMGPROGFAIL: [chars] standby flash programming failed

    Explanation   This message indicates the Flash programming of the standby supervisor engine failed; [chars] is the task name.

    Action Contact your technical support representative.

SYS-3-SUP_SINBOOT: Standby supervisor module [dec] is running boot code

    Explanation   This message indicates the standby supervisor engine module [dec] is running BOOT code; [dec] is the module number.

    Action This message is provided for information only, but could indicate that the supervisor engine's Flash is corrupted, the standby supervisor engine is not configured to boot up with a valid image, or the boot failed. If you suspect the supervisor engine's Flash is corrupted, wait for the active supervisor engine to reprogram the Flash. If this message reappears, contact your technical support representative.

SYS-3-SUP_SLISTENFAIL: [chars] standby task listen call failed

    Explanation   This message indicates the TCP/IP listen call failed; [chars] is the standby supervisor engine. In this case, the duplicate Flash and NVRAM synchronization tasks do not run.

    Action Contact your technical support representative.

SYS-3-SUP_SOUTOFSYNC: [chars] standby is out of sync

    Explanation   This message indicates the duplicate Flash synchronization process between the active and standby supervisor engines is not working due to some problems in the system; [chars] is the task name.

    Action Contact your technical support representative.

SYS-3-SUP_SRECVFAIL: [chars] unable receive data from active

    Explanation   This message indicates the standby supervisor engine cannot receive data from the active supervisor engine due to a problem in the system; [chars] is the task name.

    Action Contact your technical support representative.

SYS-3-SUP_SSENDFAIL: [chars] unable send data to active

    Explanation   This message indicates the standby supervisor engine cannot send data to the active supervisor engine due to a problem in the system; [chars] is the task name.

    Action Contact your technical support representative.

SYS-3-SUP_SSOCKFAIL: [chars] standby task socket call failed

    Explanation   This message indicates the TCP/IP socket call failed; [chars] is the standby supervisor engine. In this case, the duplicate Flash and NVRAM synchronization tasks do not run.

    Action Contact your technical support representative.

SYS-3-SUP_SYNCDIAGFAILED: Unable to sync diag info. Please reset manually

    Explanation   This message indicates that the diagnostic information between the active and standby supervisor engines was not synchronized, which prevents the active supervisor engine from transferring control to the standby supervisor engine.

    Action Contact your technical support representative.

SYS-3-SUP_THISSUPRESET: Resetting this supervisor .. standby supervisor will take over

    Explanation   This message indicates that reset mindown is resetting the active supervisor engine. The standby supervisor engine will take over.

    Action This message is provided for information only.

SYS-3-SUP_WAITSBYSUPONLINE: Wait for standby supervisor to come online

    Explanation   This message indicates that the reset mindown task is waiting for the standby supervisor engine to come online.

    Action This message is provided for information only.

SYS-4

SYS-4-P2_LogBrObsoleteGbicInserted: Port [chars]: Gbic serial eeprom date [chars] is earlier than 07/98; return to [chars] for reprogramming

    Explanation   This message indicates that a preproduction GBIC has been detected. The first [chars] is the port where the faulty GBIC is installed, the second [chars] is the serial EEPROM date, and the third [chars] is where the GBIC should be returned.

    Action Contact your technical support representative,

SYS-4-P2_LogEbmZeroEtherAddr: Filtering Ethernet MAC address of value zero from agent host table interface

    Explanation   This message indicates that a MAC address of 00:00:00:00:00:00 has been discovered.

    Action Contact your technical support representative.

SYS-4-P2_LogEpcHostAccessDenied: Host [ether] access denied on port [chars]

    Explanation   This message indicates that the specified host is seen as a source address on the specified port. However, the system has been configured to deny traffic from the host on the specified port. As a result, all traffic from this address on this port is dropped. The most common reason for this is that port security is enabled. If a different address is currently assigned to the secure port, traffic from any other address is dropped because it is a security violation. [ether] is the Ethernet host address and [chars] is the port number.

    Action Contact your technical support representative.

SYS-4-P2_LogEpcMulticastSource: Invalid traffic from multicast source address [ether] on port [chars]

    Explanation   This message indicates that traffic from a multicast source is being received on the specified port. This is not a standards-compliant operation, however, the information will be forwarded based on the destination address. [ether] is the source address and [chars] is the port where the data is being received.

    Action Contact your technical support representative.

SYS-4-P2_LogEpcPermanentHostWrongPort: Traffic from permanent host [ether] but seen on incorrect port [chars]

    Explanation   This message indicates that the host, having been configured to appear on a specific port only, is also being seen on another port. All host traffic on the incorrect port is dropped. [ether] is the host address and [chars] is the port where the host traffic is appearing.

    Action Contact your technical support representative.

SYS-4-P2_LogEpcVlanTagConflictsWithAccessPort: Tag [dec] on packet from [ether] port [chars], but port's native vlan is [dec]

    Explanation   This message indicates that an 802.1q tagged packet was received on a non-trunk port. The VLAN derived from the packet's tag is different from the port's native VLAN. The Tag [dec] is the VLAN identifier from the packet, [ether] is the host address, port [chars] is the port identifier, and the second [dec] is the native VLAN number.

    Action The local port may be incorrectly configured as an access port instead of a trunk port. Alternately, the remote side could be configured as a trunk port instead of an access port. Contact your technical support representative.

SYS-4-P2_LogGalLinecardCleanupTooLong: Module [dec] is taking an unusual amount of time to come online

    Explanation   This message indicates that the powering-up process for a hot-swapped module is taking too long. During the new module's powering-up process, a clean-up process is performed to remove conditions associated with the old module. [dec] is the module number.

    Action Do not immediately remove and reinsert the module. Doing so causes the clean-up process to begin again. Wait ten minutes and if the module does not come online, reset the switch.

SYS-4-P2_LogNicerManDiagsFailed: [chars] failed diags

    Explanation   This message indicates that the NiceR ASIC has failed diagnostics; [chars] is the ASIC name.

    Action Contact your technical support representative.

SYS-4-P2_LogNicerManFailedToSendLoopbackTries: [chars] port [dec] failed to send packet in [dec] tries

    Explanation   This message indicates that the NiceR ASIC was unable to send a loopback packet on the NiceR port identified; [chars] is the ASIC, [dec] is the port number, and the second [dec] is the number of tries and failures. The loopback packet is sent only three times.

    Action Contact your technical support representative.

SYS-4-P2_LogNicerManNotifySuicide: Online diags [chars] received suicide event while in state [dec]

    Explanation   This message indicates that the time limit for completion of the NiceR diagnostics has expired; [chars] identifies which NiceR ASIC exceeded its time limit and [dec] identifies what state the ASIC was in when time expired.

    Action Contact your technical support representative.

SYS-4-P2_LogNicerManResettingNicer: Warning-resetting Nicer [chars] due to loss of all communications

    Explanation   This message indicates that the NiceR manager has done ten consecutive retransmissions of a packet to the NiceR ASIC without receiving a response; [chars] is the NiceR ASIC. The NiceR manager attempts to reset the NiceR ASIC.

    Action Contact your technical support representative.

Sys-4-P2_LogNicerManUnexpectedLoopback: [chars] sent out a loopback packet on port [dec], but it came back on port [dec]

    Explanation   This message indicates that the NiceR diagnostics for the NiceR ASIC sent a loopback packet out of one port and received the loopback packet on another port; [chars] is the name of the NiceR ASIC, the first [dec] is the first port number, and the second [dec] is the second port number.

    Action Contact your technical support representative.

Sys-4-P2_LogScxManOutOfMcis: Out of multicast table entries

    Explanation   This message indicates that the system has run out of resources required to forward multicast traffic and unknown destination traffic.

    Action This is usually a transient condition seen during periods of heavy traffic. If the problem persists, try disabling CGMP/IGMP.

Sys-4-P2_LogScxSingleK1ManOutOfMcis: Out of multicast table entries

    Explanation   This message indicates that the system has run out of resources required to forward multicast traffic and unknown destination traffic.

    Action This is usually a transient condition seen during periods of heavy traffic. If the problem persists, try disabling CGMP/IGMP.

Sys-4-P2_LogScxTripleK1ManOutOfMcis:Out of multicast table entries

    Explanation   This message indicates that the system has run out of resources required to forward multicast traffic and unknown destination traffic.

    Action This is usually a transient condition seen during periods of heavy traffic. If the problem persists, try disabling CGMP/IGMP.

Sys-4-P2_LogSknmpInvalidVlanDropPacket: Invalid vlanId [dec], dropping packet DA [ether] SA [ether]

    Explanation   This message indicates that an index-directed packet from the supervisor engine was received with an invalid VLAN number; [dec] is the invalid VLAN number, DA [ether] is the destination address of the packet, and SA [ether] is the source address of the packet.

    Action Contact your technical support representative.

SYS-4-PORT_GBICNOTSUPP: Port [dec]/[dec] GBIC is unsupported

    Explanation   This message indicates that an installed Gigabit Interface Converter (GBIC) could not be identified because either the GBIC serial EPROM is bad or the GBIC is an unsupported version; [dec]/[dec] is the module number/port number of the faulty GBIC.

    Action If you are using a Cisco-supported GBIC, contact your technical support representative. Otherwise, either replace the unsupported GBIC with a supported GBIC or disregard the message.

SYS-5

SYS-5-ERRBRDPRES: Erroneous Boards Present message has been received

    Explanation   This message indicates that the NMP received an invalid "board present" message from the MCP. The NMP ignores the message, so there is no effect to the system.

    Action This message is provided for information only. You can perform a show log command to obtain a dump of the erroneous message.

SYS-5-MOD_DCPWRMISMATCH: Module [dec] DC power failure detected during polling

    Explanation   This message indicates that during normal polling, the supervisor engine has detected a problem in the power management circuitry on one of the modules, where [dec] is the module number. The module will not be polled again after the failure is detected.

    Action Contact your technical support representative.

SYS-5-MOD_DNLDFAIL: Download failed for module [dec]

    Explanation   This message indicates that the code download failed for a particular module; [dec] is the module number.

    Action Reset the module and try to reload the code. Contact your technical support representative.

SYS-5-MOD_INSERT: Module [dec] has been inserted

    Explanation   This message indicates that module [dec] was inserted; [dec] is the module number.

    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.

SYS-5-MOD_NOREGISTRATION: No registration received from module [dec]... resetting module

    Explanation   This message indicates that a registration message from the module to the supervisor engine did not occur within 30 seconds after the supervisor engine detected the module in the chassis; [dec] is the module number. The supervisor engine resets the module.

    Action This message is provided for information only.

SYS-5-MOD_NORESETACK: Module [dec] not responding... resetting module

    Explanation   This message indicates that the supervisor engine or the NMP did not receive an acknowledgment from the module after it began executing its runtime code; [dec] is the module number. This message is displayed every 3 minutes. The module is reset each time. At the end of 9 minutes, a failure is declared.

    Action This message is provided for information only.

SYS-5-MOD_NORESPONSE: Module [dec] failed to respond

    Explanation   This message indicates that after three resets, the module failed to send a reset acknowledgment to the NMP; [dec] is the module number. A failure is declared for the module.

    Action Contact your technical support representative.

SYS-5-MOD_NOSCPPINGRESPONSE: Module [dec] not responding... resetting module

    Explanation   This message indicates that after three attempts to poll a module, the module has failed to respond back to the supervisor engine; [dec] is the module number.

    Action This message is provided for information only.

SYS-5-MOD_OK: Module [dec] is online

    Explanation   This message indicates that the module passed the diagnostic self-test and is online; [dec] is the module number.

    Action This message is provided for information only.

SYS-5-MOD_PWRDENY: Power denied to module [dec]

    Explanation   This message indicates that a module cannot be powered up because there is insufficient power supply capacity available. The supervisor engine monitors the power consumption of the modules during boot. As the supervisor engine attempts to power up a module, it compares the module's power needs with the remaining capacity of the power supply. If there is not enough power supply capacity remaining, the supervisor engine will not power up the module. [dec] is the module number.

    Action This message is provided for information only.

SYS-5-MOD_PWRMISMATCH: Module [dec] SW/HW power status mismatch

    Explanation   This message indicates that a mismatch has been detected by the supervisor engine between the power management hardware registers and the software registers. Every 300 milliseconds the supervisor engine software performs a power management check between the software and the hardware. When a mismatch is detected, this message is generated. [dec] is the module number.

    Action This message is provided for information only.

SYS-5-MOD_REMOVE: Module [dec] has been removed

    Explanation   This message indicates that module was removed; [dec] is the module number.

    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 you do not see this response, contact your technical support representative.

SYS-5-MOD_RESET: Module [dec] reset from [chars]

    Explanation   This message indicates that module [dec] was reset from [chars]; [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.

    Action This message is provided for information only.

SYS-5-MOD_RMVDNLDSTOP: Download terminated for module [dec]. Module removed

    Explanation   This message indicates that during a code download, the module was removed; [dec] is the module number.

    Action This message is provided for information only.

SYS-5-P2_LogGalOverheatingOver: Resuming normal operation after return to acceptable temperatures

    Explanation   This message indicates that the system line cards have been reset to reduce heat generation because the unit was exceeding critical temperature. The unit temperature has returned to an acceptable level and normal operation is resuming.

    Action This message is provided for information only.

SYS-5-P2_LogGalSufficientFansRestored: Resuming normal operation after restoration of adequate fan cooling

    Explanation   This message indicates that the system line cards have been reset to reduce heat generation due to an insufficent number of operational fans. Adequate fan cooling has been restored and normal operation is resuming.

    Action This message is provided for information only.

SYS-5-P2_LogGalSufficientPowerRestored: Resuming normal operation after restoration of adequate power

    Explanation   This message indicates that the system line cards have been reset to save power due to the lack of the required number of power supplies. Adequate power has been restored and normal operation is resuming.

    Action This message is provided for information only.

SYS-5-P2_LogPimFlapShutdown: Temporarily disabling port [chars] due to flap

    Explanation   This message indicates that the port link is alternately going up and down in rapid succession. This is usually the result of a bad connection or problems with the link-level hardware. To prevent this from impacting performance, the problem port is shut down. Every five seconds the port is reenabled to see if the problem has gone away. If not, the port is shut down until the problem is corrected. [chars] is the number of the port.

    Action This message is provided for information only.

SYS-5-PKTTESTDONE: Packetbuffer test done. Use 'show test' to see test results

    Explanation   This message indicates that the packet buffer test is complete. Use the show test command to display the test results.

    Action This message is provide for information only.

SYS-5-PORT_SSUPOK: Ports on standby supervisor (module [dec]) are up

    Explanation   This message indicates that the ports on the standby supervisor engine are up on systems equipped with redundant supervisor engines; [dec] is the module number. This message occurs when the system is powered up or reset.

    Action This message is provided for information only.

SYS-5-REDUNDANTCLOCK_FAIL: Redundant clock failed

    Explanation   This message indicates that the redundant (standby) clock has failed. Clock switchover from the primary clock to the standby clock is prevented.

    Action Contact your technical support representative.

SYS-5-REDUNDANTCLOCK_OK: Redundant clock recovered

    Explanation   This message indicates that the redundant (standby) clock has recovered from an error. Clock switchover from the primary clock to the standby clock can occur.

    Action This message is provided for information only.

SYS-5-RTE_DEFGATEFROM: Default Gateway switching from [chars]

    Explanation   This message indicates that the default IP gateway has failed; [chars] is the name of the IP gateway.

    Action This message is provided for information only.

SYS-5-RTE_DEFGATETO: Default Gateway switching to [chars]

    Explanation   This message indicates that the IP gateway is the new default IP gateway; [chars] is the name of the gateway.

    Action This message is provided for information only.

SYS-5-SPAN_ADMINPORTDEL: Admin ports delteded for [chars] session for [chars]

    Explanation   This message indicates that one or more ports are being removed from the admin ports list of a session; the first [chars] specifies the local or remote SPAN session, the second [chars] specifies the destination port or RSPAN VLAN. This error might occur when a module is removed and replaced with a module of a different type.

    Action This message is provide for information only.

SYS-5-SPAN_CFGFAIL: Failed to configure source port [dec/dec]

    Explanation   This message indicates that the span feature is not supported on the source module; [dec/dec] is the module number/port number.

    Action This message is provided for information only.

SYS-5-SPAN_CFGSTATECHG: [chars] session [chars]active for [chars]

    Explanation   This message indicates that a session has been active or inactive; the first [chars] specifies local or remote SPAN session, the second [chars] is for active or inactive, and the third [chars] specifies the destination port or RSPAN VLAN.

    Action This message is provided for information only.

SYS-5-SPAN_NOADMINPORTS: No admin ports: [chars] session disabled for [chars]

    Explanation   This message indicates that a session has been disabled as the admin port list becomes empty; the first [chars] specifies the local or remote SPAN session and the second [chars] specifies the destination port or the RSPAN VLAN. This error might occur when a module is removed and replaced with a module of a different type.

    Action This mesage is provided for information only.

SYS-5-SPAN_NOADMINVLANS: No admin vlans: [chars] session disabled for [chars]

    Explanation   This message indicates that a session has been disabled as the admin VLAN list becomes empty; the first [chars] specifies the local or remote SPAN session and the second [chars] specifies the destination port or RSPAN VLAN. This error might occur when a module is removed and replaced with a module of a different type.

    Action This message is provided for information only.

SYS-5-SPAN_NOFILTERVLANS: No filter vlans: [chars] session disabled for [chars]

    Explanation   This message indicates that a session has been disabled as filter VLAN list became empty; the first [chars] specifies either local or remote SPAN session, the second [chars] specifies the destination port or RSPAN VLAN. This error might occur when one or more VLANs are cleared.

    Action This message is provided for information only.

SYS-5-SPAN_SRCMODCFGFAIL:Failed to configure source module [dec]

    Explanation   This message indicates that ports on the module could not be configured as SPAN source ports; [dec] is the module number.

    Action Verify whether the module specified in the message supports the SPAN feature or not. Contact your technical support representative.

SYS-5-SPAN_SRCPORTCFGFAIL: Failed to configure source port [dec]/[dec]

    Explanation   This message indicates that the port could not be configured as a SPAN source port; [dec]/[dec] is the module number/port number.

    Action Verify whether the module specified in the message supports the SPAN feature or not. Contact your technical support representative.

SYS-5-SUP_BOOTSYNCFINISH: Supervisor's boot images are synchronized

    Explanation   This message indicates that the supervisor engine completed synchronizing the BOOT images.

    Action This message is provided for information only.

SYS-5-SUP_IMGSYNCFINISH: Active supervisor has [chars] the NMP image

    Explanation   This message indicates that the active supervisor engine has [chars] the NMP image; [chars] is copied or synchronized.

    Action This message is provided for information only.

SYS-5-SUP_IMGSYNCSTART:Standby supervisor is [chars] the NMP image

    Explanation   This message indicates that the standby supervisor engine is [chars] the NMP image; [chars] is copying or synchronizing.

    Action This message is provided for information only.

SYS-5-SUP_MODNONSBY: Module [dec] is present but not in standby mode

    Explanation   This message appears only when using Supervisor Engine III modules and only on the active Supervisor Engine III module; [dec] is the module number. This message occurs only with systems containing redundant supervisor engines when one of the Supervisor Engine III modules has a problem booting up and gets kicked back out to the ROM-based monitor (ROMMON).

    Action From the standby supervisor engine console, boot the standby supervisor engine manually. If the message reappears, contact your technical support representative.

SYS-5-SUP_MODSBY: Module [dec] is in standby mode

    Explanation   This message indicates module [dec] is in standby mode; [dec] is the module number.

    Action This message is provided for information only.

SYS-5-SUP_SBYHIGHPWR: Standby drawing more power. System may run over power budget

    Explanation   This message indicates that the active supervisor engine is drawing less power than the standby supervisor engine. A fully configured system could draw more power than the power supply rating. Normally, the active supervisor engine reserves the same amount of power that is reserved for the standby supervisor engine. If the standby supervisor engine draws more power than this, the power requirement could exceed the rated power available.

    Action Contact your technical support representative.

SYS-5-SUP_SBYLOWPWR: Standby drawing less power. Potential power budget violation at switchover

    Explanation   This message indicates that the standby supervisor engine is drawing less power than the active supervisor engine. If the system is fully configured and a switchover from active to standby supervisor engine occurs, there is a possibility that the power requirements might exceed the power supply ratings.

    Action This message is provided for information only.

SYS-5-SYS_RESET: System reset from [chars]

    Explanation   This message indicates that the system was reset from [chars]; [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.

    Action This message is provided for information only.

SYS-7

SYS-7-LLC_TUNNEL: Tunnel-[chars]([dec]) ([chars], vlan [dec],proto [hex])

TAC Messages

This section contains the Catalyst 6000 family switch TACACS+ messages.

TAC-7-BADADDR: Address not configured as a Server

    Explanation   This message appears during debugging only and indicates that the TACACS+ address is not configured as a server.

    Action Configure the TACACS+ address as a TACACS+ server.

TAC-7-BADDATA: Received unsane data from server

    Explanation   This message appears during debugging only; it indicates that data received from the server is not recognized.

    Action Retry connection. If this message reappears, contact your technical support representative.

TAC-7-BADLEN1: Received bad packet: length = [dec]

    Explanation   This message appears during debugging only. This message indicates that a bad packet was received; the length = [dec] is the bad packet length.

    Action Retry operation. If this message reappears, contact your technical support representative.

TAC-7-BADLEN2: Received bad packet: length = [dec], expected [dec]

    Explanation   This message appears during debugging only. This message indicates that a bad packet was received; the length = [dec] is the bad packet length, and the second [dec] is the expected length.

    Action Retry operation. If this message reappears, contact your technical support representative.

TAC-7-BADSESS: Received packet with bad session id

    Explanation   This message appears during debugging only; it indicates that a packet with a bad session ID was received.

    Action Retry operation. If this message reappears, contact your technical support representative.

TAC-7-BADVER: Received packet with bad version

    Explanation   This message appears during debugging only; it indicates that a packet with a bad version was received.

    Action Check the version of server software; upgrade if necessary.

TAC-7-CONNERR: Socket connection error to [integer]

    Explanation   This message appears during debugging only. This message indicates that a bad network connection error occurred to [integer]; [integer] is the server address.

    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-DECRYPTERR1: Decrypt: no key for encrypted packet

    Explanation   This message appears during debugging only; it indicates that the packet is encrypted but a key is not available.

    Action Configure the correct key.

TAC-7-DECRYPTERR2: Decrypt: packet is unencrypted but we have a key

    Explanation   This message appears during debugging only; it indicates that the packet is unencrypted but a key is available.

    Action Remove the key.

TAC-7-PAKSENDERR: Error sending continue packet

    Explanation   This message indicates that the system is unable to send TACACS+ packets to the server.

    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-SOCKERR: Socket creation error

    Explanation   This message appears during debugging only and indicates that a bad network connection error occurred.

    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.


UDLD Protocol Messages

This section lists the UniDirectional Link Detection (UDLD) Protocol messages.

UDLD-3

UDLD-3-AGGRDISABLE: Neighbor(s) of port [dec]/[dec] disappeared on bidirectional link. Port disabled

    Explanation   This message indicates that a fault has been detected in an Ethernet port connection and that the port has been disabled to prevent other protocols from malfunctioning. The heartbeat packets on a bidirectional link have stopped and, as a precaution, the port has been shutdown to prevent a spanning tree loop. [dec]/[dec] is the module number/port number

    Action Verify that all of the fiber strand pairs or copper wire pairs are correctly connected and that the fiber Tx and Rx connectors are bundled together. Also check that the port is functioning normally and that the hardware counters are okay. If no apparent misconnection or malfunction is found, try reenabling the port and disabling the aggressive mode. Make sure that the port is not connected to a hub, media converter, or similar device.

UDLD-3-AGGRDISABLEFAIL: Neighbor(s) of port [dec]/[dec] disappeared on bidirectional link, failed to disable port

    Explanation   This message indicates that a fault was detected in the wiring on an Ethernet port, but UDLD could not disable the port; [dec]/[dec] is the module number/port number.

    Action Verify that all fiber strand pairs or copper wire pairs are correctly connected and that the fiber Tx and Rx connectors are bundled together. Also check that the port is functioning correctly and that the hardware counters are okay. If no apparent misconnection or malfunction is found, try disabling the aggressive mode. Make sure that the port is not connected to a hub, media converter, or similar device. Contact your technical support representative.

UDLD-3-DISABLE: Unidirectional link detected on port [dec]/[dec]. Port disabled

    Explanation   This message indicates that a fault has been detected in an Ethernet port connection and that the port has been disabled to prevent other protocols from malfunctioning; [dec]/[dec] is the module number/port number.

    Action Verify that all of the fiber strand pairs or copper wire pairs are correctly connected and that the Tx and Rx connectors are bundled together. Also check that the port is functioning normally. If no apparent misconnection or malfunction is found, try reenabling the port.

UDLD-3-DISABLEFAIL: Unidirectional link detected on port [dec]/[dec], failed to disable port

    Explanation   This message indicates that a fault was detected in the wiring on an Ethernet port, but UDLD could not disable the port; [dec]/[dec] is the module number/port number.

    Action Verify that all of the fiber strand pairs or copper wire pairs are correctly connected and that the Tx and Rx connectors are bundled together. Also check that the port is functioning correctly. Contact your technical support representative.

UDLD-3-SENDFAIL: Transmit failure on port [dec]/[dec]

    Explanation   This message indicates that a transmit failure occurred on port [dec]/[dec]; [dec]/[dec] is the module number/port number.

    Action Contact your technical support representative.

UDLD-4

UDLD-4-ONEWAYPATH: A unidirectional link from port [dec]/[dec] to port [dec]/[dec] of device [chars] was detected

    Explanation   This message indicates that a fault has been detected in an Ethernet connection in a shared media environment and that the connection may cause a possible malfunction; [dec]/[dec] are the module numbers/port numbers, and [chars] is the CDP name of the neighbor. To find the name, enter show cdp neighbor.

    Action Verify that all of the fiber strand pairs or copper wire pairs are correctly connected (both on the local device and on the neighboring devices) and that the Tx and Rx connectors are bundled together. Also check that the ports are functioning normally. If no apparent misconnection or malfunction is found, contact your technical support representative.

UDLD-7

UDLD-7-PKTDROP: Packet dropped as UDLD is disabled on port [dec]/[dec]

VMPS Messages

This section contains the VLAN Membership Policy Server (VMPS) messages.

VMPS-2

VMPS-2-BINDFAIL: Failed to bind socket

    Explanation   This message indicates insufficient system resources.

    Action Contact your technical support representative.

VMPS-2-DNLDFAIL: Download Failed. VMPS is now inactive

    Explanation   This message indicates that the attempt to download failed and VMPS
    is inactive.

    Action This message is provided for information only.

VMPS-2-DOWNLOADFAIL1: Another download in progress, try later

    Explanation   This message indicates that another download process is currently in progress.

    Action Try to download after the other process completes. If this message reappears, contact your technical support representative.

VMPS-2-DOWNLOADFAIL2: Unable to download file [chars]

    Explanation   This message indicates that either the Trivial File Transfer Protocol (TFTP) server is not online, or the file does not exist on the server; [chars] is the VMPS filename.

    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-ENABLEFAIL: VMPS Enable Failed

    Explanation   This message indicates that the attempt to enable VMPS failed.

    Action This message is provided for information only.

VMPS-2-INVFILE: PARSER: Invalid File Format, syntax error at line [dec]

    Explanation   This message indicates that a syntax error exists at line number [dec] in the configuration file; [dec] is the line number in the configuration file.

    Action Correct the error in the configuration file. If the message reappears, contact your technical support representative.

VMPS-2-NOMEM: Out of memory

    Explanation   This message indicates insufficient DRAM to load the VMPS configuration database.

    Action Increase the DRAM on the supervisor engine. If the message reappears, contact your technical support representative.

VMPS-2-NOMGTDOM: Management Domain not defined in configuration file

    Explanation   This message indicates that the management domain is not defined in the configuration file.

    Action Configure the management domain name in the configuration file. If this message reappears, contact your technical support representative.

VMPS-2-NORES: Insufficient resources to build database

    Explanation   This message indicates that there is not enough DRAM to load the VMPS configuration database.

    Action Increase the DRAM on the supervisor engine. If this message reappears, contact your technical support representative.

VMPS-2-PARSEMSG: 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; [dec] lines are the number of lines parsed, and Errors [dec] are the number of errors found.

    Action Correct the error in the configuration file. If the message reappears, contact your technical support representative.

VMPS-2-PREVCONF: VMPS is using the previous configuration

    Explanation   This message indicates that VMPS is using a previous configuration.

    Action This message is provided for information only.

VMPS-2-SOCFAIL: Failed to create socket

    Explanation   This message indicates insufficient system resources.

    Action Contact your technical support representative.

VMPS-2-TASKCREATFAIL: Failed to create task

    Explanation   This message indicates the number of processes in the system reached the maximum limit.

    Action Contact your technical support representative.

VMPS-3

VMPS-3-BADKEYWD: PARSER: Unknown keyword [chars] at line [dec]

    Explanation   This message indicates that an unknown keyword [chars] exists at line number [dec] in the configuration file; [chars] is the keyword, and [dec] is the line number in the configuration file.

    Action Correct the error in the configuration file. If this message reappears, contact your technical support representative.

VMPS-3-INVARGS: PARSER: Invalid no. of args at line [dec]

    Explanation   This message indicates a parsing error in the configuration file; [dec] is the line number in the configuration file.

    Action Correct the error in the configuration file.

VMPS-3-INVIP: PARSER: Invalid IP addr [chars] at line [dec]

    Explanation   This message indicates that an invalid IP address [chars] at line [dec] exists in the configuration file; [chars] is the IP address, and [dec] is the line number in the configuration file.

    Action Correct the error in the configuration file. If this message reappears, contact your technical support representative.

VMPS-3-INVMAC: PARSER: Invalid MAC addr [chars] at line [dec]

    Explanation   This message indicates that an invalid MAC address [chars] at line [dec] exists in the configuration file; [chars] is the MAC address, and [dec] is the line number in the configuration file.

    Action Correct the error in the configuration file. If this message reappears, contact your technical support representative.

VMPS-3-INVPORTGRP: PARSER: Unknown port group [chars] at line [dec]

    Explanation   This message indicates that an unknown port group [chars] at line [dec] exists in the configuration file; [chars] is the port group number, and [dec] is the line number in the configuration file.

    Action Correct the error in the configuration file. If this message reappears, contact your technical support representative.

VMPS-3-INVSYNTAX: PARSER: Invalid syntax at line [dec]

    Explanation   This message indicates that an invalid syntax exists at line [dec] in the configuration file; [dec] is the line number in the configuration file.

    Action Correct the error in the configuration file. If this message reappears, contact your technical support representative.

VMPS-3-INVVLAN: PARSER: Invalid VLAN [chars] at line [dec]

    Explanation   This message indicates that an invalid VLAN [chars] at line [dec] exists in the configuration file; [chars] is the VLAN number, and [dec] is the line number in the configuration file.

    Action Correct the error in the configuration file. If this message reappears, contact your technical support representative.

VMPS-3-INVVLANGRP: PARSER: Unknown VLAN group [chars] at line [dec]

    Explanation   This message indicates that an unknown VLAN group [chars] at line [dec] exists in the configuration file; [chars] is the VLAN group number, and [dec] is the line number in the configuration file.

    Action Correct the error in the configuration file. If this message reappears, contact your technical support representative.

VMPS-7-INVLEN: Invalid length [dec] for IP address

    Explanation   This message appears during debugging only and indicates that the server received an invalid request from the client; [dec] is the length of invalid data in the request.

    Action Contact your technical support representative.

VMPS-7

VMPS-7-INVOPCODE: Invalid opcode 0x[hex] in packet

    Explanation   This message appears during debugging only and indicates that the server received an invalid request from the client; 0x[hex] is the invalid request number.

    Action Contact your technical support representative.

VMPS-7-INVTLV: Invalid TLV type 0x[hex]

    Explanation   This message appears during debugging only and indicates that the server received an invalid request from the client; 0x[hex] is the invalid data in the request.

    Action Contact your technical support representative.

VMPS-7-INVVER: Invalid version 0x[hex] in packet

VTP Messages

This section contains the VLAN Trunking Protocol (VTP) messages.

VTP-1

VTP-1-GVRPDYNVLANCREATE: Can't get out of transparent mode when dynamic vlan creation is enabled

    Explanation   This message indicates that you can only enable dynamic VLAN creation when VTP is in transparent mode.

    Action This message is provided for information only.

VTP-2

VTP-2-INBANDINRSPANVLAN: Rspan vlan [dec] assigned to inband port

    Explanation   This message indicates that a Remote SPAN (RSPAN) VLAN has been assigned to the inband port; [dec] is the RSPAN VLAN number.

    Action Contact your technical support representative.

VTP-2-ISL1QMAPMALLOCFAIL: Malloc failed [chars]

    Explanation   This message indicates that memory allocation failed; [chars] is the action.

    Action This message is provided for information only.

VTP-2-ISL1QMAPSCPSENDFAIL: Send [chars] via scp failed to module [dec]

    Explanation   This message indicates that an SCP message failed to reach the module; [chars] is the information sent and [dec] is the module number to which the message
    was sent.

    Action This message is provided for information only.

VTP-2-ISL1QMAPSCPSTATUSNOTSUPPORTED: Module [dec] does not support vlan mapping - upgrade module software if vlan mapping is required

    Explanation   This message occurs when the switch sends all of the isl-1q vlan mapping to all of the 1q-capable line cards. If a line card returns status of SCPSTAT_NOTSUPPORTED to the switch, the above message is generated; [dec] is the module number.

    Action Contact your technical support representative.

VTP-2-LLCRXFAIL: LLC couldn't parse received vtp packet.

    Explanation   This message indicates an internal error in LLC.

    Action Contact your technical support representative.

VTP-2-RXINVSUMMARY: rx invalid summary from [chars], len=[dec], rev=[dec]

    Explanation   This message indicates that the sanity check in VTP detects a received VTP message with an invalid length; [chars] is the module/port where the message was received, the first [dec] is the message length, and the second [dec] is the configuration revision number.

    Action Contact your technical support representative.

VTP-2-TXINVSUMMARY: tx invalid summary to [dec]/[dec], len=[dec]

    Explanation   This message indicates that the sanity check in VTP detects a VTP message with an invalid length to be transmitted; [dec]/[dec] is the destination module/port, and [dec] is the message length.

    Action Contact your customer service representative.

VTP-4

VTP-4-DBLOCKED: Database for domain [chars] locked, giving up

    Explanation   This message indicates that the database for domain [chars] is locked; [chars] is the domain name and will not permit entry.

    Action Contact your technical support representative.

VTP-4-ISL1QMAPSCPSTATUSNOTOK: Send [chars] via scp to Module [dec] result no OK, status = [dec]

    Explanation   This message indicates that the information sent to the module through SCP was not transmitted successfully; [chars] is the message sent, Module [dec] is the module number where the message was sent, and status = [dec] is the error message.

    Action This message is provided for information only.

VTP-4-NODOMAIN: domain [chars] not found

    Explanation   This message indicates that domain [chars] cannot be found; [chars] is the domain name.

    Action Contact your technical support representative.

VTP-4-NOTSERVER: Cannot configure a VLAN in client mode

    Explanation   This message indicates that you tried to create a VLAN when VTP is in client mode.

    Action You can change VTP to server or transparent mode to create
    the VLAN.

VTP-4-NOVLAN: vlan [dec] not found (mode = [dec])

    Explanation   This message indicates that the VLAN cannot be found while trying to modify or delete it; vlan [dec] is the VLAN number, and (mode= [dec]) is the mode value.

    Action This message is intended as an informational warning only.

VTP-4-PORTSINRSPANVLAN:Port [dec]/[dec] inactive in rspan vlan [dec]

    Explanation   This message indicates that a port has become inactive for RSPAN; [dec]/[dec] is the module number and port number, and vlan [dec] is the RSPAN VLAN number.

    Action This message is provided for information only.

VTP-5

VTP-5-DYNCREATEVLAN: Vlan [dec] dynamically created successful

    Explanation   This message indicates that a dynamic VLAN has been created; [dec] is the number of the VLAN created.

    Action This message is provided for information only.

VTP-5-DYNDELETEVLAN: Vlan [dec] dynamically deleted successful

    Explanation   This message indicates that a dynamic VLAN has been deleted; [dec] is the number of the VLAN deleted.

    Action This message is provided for information only.

VTP-5-PVLANMODECONFLICT: VTP has to be in Transparent mode if Private Vlans are configured

    Explanation   This message indicates that an attempt was made to set VTP to client or server mode while private VLANs are configured on the switch. Private VLANs cannot be configured if VTP is not in transparent mode.

    Action Set the VTP mode to transparent.

VTP-5-RSPANVLANCHG: Rspan vlan [dec] [chars]ed

    Explanation   This message indicates that a RSPAN VLAN has been created or deleted; [dec] is the RSPAN VLAN number and [chars]ed is either created or deleted.

    Action This message is provided for information only.

VTP-5-RSPVLAN_NOHWSUPP: Rspan vlan not supported: hardware upgrade required

    Explanation   This message indicates that a hardware upgrade is required to use the RSPAN VLAN feature.

    Action Contact your technical support representative.

VTP-6

VTP-6-DOMAINCHG: Domain [chars] modified

    Explanation   This message indicates that domain [chars] was modified; [chars] is the domain name.

    Action This message is provided for information only.

VTP-6-VLANCHG: VLAN [dec] [chars]ed


hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Jul 20 17:51:33 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.