NN46200-706 01.01 FAULT Logs Reference

Nortel Ethernet Routing Switch 8300
Logs Reference
Release: 4.1 Document Revision: 01.01
www.nortel.com
NN46200-706 .
324408-A Rev 01
Nortel Ethernet Routing Switch 8300 Release: 4.1 Publication: NN46200-706 Document status: Standard Document release date: 16 June 2008 Copyright 2008, Nortel Networks All Rights Reserved. Printed in Canada and the United States of America LEGAL NOTICE While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing, NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESSED OR IMPLIED. The information and/or products described in this document are subject to change without notice. Nortel, the Nortel logo, the Globemark, and Passport are trademarks of Nortel Networks. All other trademarks are the property of their respective owners.
ATTENTION For information about the software license, read "Software license" in this guide.
Contents
Software license New in this release
Features 9 Other changes 9 New system messages 9
5 9
Introduction SMP error messages

Numeric Messages A Messages 13 B Messages 25 C Messages 35 D Messages 54 E Messages 57 F Messages 61 G Messages 68 H Messages 75 I Messages 79 K Messages 91 L Messages 91 M Messages 97 N Messages 104 O Messages 117 P Messages 127 Q Messages 149 R Messages 152 S Messages 197 T Messages 216 U Messages 224 V Messages 229 W Messages 235 13
11 13
Nortel Ethernet Routing Switch 8300 Logs Reference NN46200-706 01.01 Standard 16 June 2008
Copyright 2008, Nortel Networks
Software license
This section contains the Nortel Networks software license.
Nortel Networks Inc. software license agreement

This Software License Agreement ("License Agreement") is between you, the end-user ("Customer") and Nortel Networks Corporation and its subsidiaries and affiliates ("Nortel Networks"). PLEASE READ THE FOLLOWING CAREFULLY. YOU MUST ACCEPT THESE LICENSE TERMS IN ORDER TO DOWNLOAD AND/OR USE THE SOFTWARE. USE OF THE SOFTWARE CONSTITUTES YOUR ACCEPTANCE OF THIS LICENSE AGREEMENT. If you do not accept these terms and conditions, return the Software, unused and in the original shipping container, within 30 days of purchase to obtain a credit for the full purchase price. "Software" is owned or licensed by Nortel Networks, its parent or one of its subsidiaries or affiliates, and is copyrighted and licensed, not sold. Software consists of machine-readable instructions, its components, data, audio-visual content (such as images, text, recordings or pictures) and related licensed materials including all whole or partial copies. Nortel Networks grants you a license to use the Software only in the country where you acquired the Software. You obtain no rights other than those granted to you under this License Agreement. You are responsible for the selection of the Software and for the installation of, use of, and results obtained from the Software. 1. Licensed Use of Software. Nortel Networks grants Customer a nonexclusive license to use a copy of the Software on only one machine at any one time or to the extent of the activation or authorized usage level, whichever is applicable. To the extent Software is furnished for use with designated hardware or Customer furnished equipment ("CFE"), Customer is granted a nonexclusive license to use Software only on such hardware or CFE, as applicable. Software contains trade secrets and Customer agrees to treat Software as confidential information using the same care and discretion Customer uses with its own similar information that it does not wish to disclose, publish or disseminate. Customer will ensure that anyone who uses the Software does so only in compliance with the terms
6 Software license
of this Agreement. Customer shall not a) use, copy, modify, transfer or distribute the Software except as expressly authorized; b) reverse assemble, reverse compile, reverse engineer or otherwise translate the Software; c) create derivative works or modifications unless expressly authorized; or d) sublicense, rent or lease the Software. Licensors of intellectual property to Nortel Networks are beneficiaries of this provision. Upon termination or breach of the license by Customer or in the event designated hardware or CFE is no longer in use, Customer will promptly return the Software to Nortel Networks or certify its destruction. Nortel Networks may audit by remote polling or other reasonable means to determine Customers Software activation or usage levels. If suppliers of third party software included in Software require Nortel Networks to include additional or different terms, Customer agrees to abide by such terms provided by Nortel Networks with respect to such third party software. 2. Warranty. Except as may be otherwise expressly agreed to in writing between Nortel Networks and Customer, Software is provided "AS IS" without any warranties (conditions) of any kind. NORTEL NETWORKS DISCLAIMS ALL WARRANTIES (CONDITIONS) FOR THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OF NON-INFRINGEMENT. Nortel Networks is not obligated to provide support of any kind for the Software. Some jurisdictions do not allow exclusion of implied warranties, and, in such event, the above exclusions may not apply. 3. Limitation of Remedies. IN NO EVENT SHALL NORTEL NETWORKS OR ITS AGENTS OR SUPPLIERS BE LIABLE FOR ANY OF THE FOLLOWING: a) DAMAGES BASED ON ANY THIRD PARTY CLAIM; b) LOSS OF, OR DAMAGE TO, CUSTOMERS RECORDS, FILES OR DATA; OR c) DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), WHETHER IN CONTRACT, TORT OR OTHERWISE (INCLUDING NEGLIGENCE) ARISING OUT OF YOUR USE OF THE SOFTWARE, EVEN IF NORTEL NETWORKS, ITS AGENTS OR SUPPLIERS HAVE BEEN ADVISED OF THEIR POSSIBILITY. The forgoing limitations of remedies also apply to any developer and/or supplier of the Software. Such developer and/or supplier is an intended beneficiary of this Section. Some jurisdictions do not allow these limitations or exclusions and, in such event, they may not apply. 4. General shall apply: All Nortel Networks Software available under this License Agreement is commercial computer software and commercial computer
1. If Customer is the United States Government, the following paragraph
Nortel Networks Inc. software license agreement
software documentation and, in the event Software is licensed for or on behalf of the United States Government, the respective rights to the software and software documentation are governed by Nortel Networks standard commercial license in accordance with U.S. Federal Regulations at 48 C.F.R. Sections 12.212 (for non-DoD entities) and 48 C.F.R. 227.7202 (for DoD entities).
2. Customer may terminate the license at any time. Nortel Networks

may terminate the license if Customer fails to comply with the terms and conditions of this license. In either event, upon termination, Customer must either return the Software to Nortel Networks or certify its destruction.
3. Customer is responsible for payment of any taxes, including personal

property taxes, resulting from Customers use of the Software. Customer agrees to comply with all applicable laws including all applicable export and import laws and regulations.
4. Neither party may bring an action, regardless of form, more than two
years after the cause of the action arose.
5. The terms and conditions of this License Agreement form the complete
and exclusive agreement between Customer and Nortel Networks.
6. This License Agreement is governed by the laws of the country in

which Customer acquires the Software. If the Software is acquired in the United States, then this License Agreement is governed by the laws of the state of New York.
8 Software license
New in this release

The following sections detail what is new in Nortel Ethernet Routing Switch 8300 Logs Reference (NN46200-701) for release 4.1.
Features
Features (page 9) Other changes (page 9)
There are no new features in the document for this release.
Other changes
For information about changes that are not feature-related, see the following sections:
New system messages (page 9)
New system messages

System messages added in Release 4.1 are listed in the document.
10 New in this release
11
Introduction
This guide is a reference for the log messages generated by the Ethernet Routing Switch 8300 System Messaging Platform (SMP).
12 Introduction
13
SMP error messages

This chapter lists SMP error messages in alphabetical order. Each message has a severity level, description, synopsis, and a recommended action.
Numeric Messages
Message Severity Description Action Message Severity Description Action <value> card in slot <value> not communicating WARNING This message specifies that a card failed because it has no communication with the master CPU. Re-insert or replace the card. <value> failed FATAL for CP Card, ERROR for IO Card The string provides the message that results in failure during the chassis initialization. System initialization failed for some reason. Please reboot and try again. If the problem persists, try it with a different set of cards. <value> failed for <value> FATAL for CP Card, ERROR for IO Card The string provides the message that results in failure during chassis initialization for a particular device number. System initialization failed for some reason. Please reboot and try again. If the problem persists, try it with a different set of cards.
Message Severity Description Action
A Messages
Message Severity Description AAAG_init: failed to init user hash ERROR Cannot allocate memory for TACACS+ client operation
14 SMP error messages
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity
N/A AAAG_init: failed to spawn tTacacsTask ERROR Cannot launch TACACS+ client task. N/A AAAP_inner_authenticate_user: expected state for TACACS must not be aborted ERROR Software state machine error. N/A AAAP_inner_authenticate_user: tried to begin without aborting or completing previous authentication ERROR Software state machine error. N/A AAAP_inner_authenticate_user: user status - aborted ERROR Software state machine error. N/A AAAP_inner_authenticate_user: user status - result given ERROR Software state machine error. N/A AAAP_inner_create_new_user: failed to add to hash ERROR Memory problem N/A AAAP_inner_delete_user: failed to delete from hash ERROR
A Messages
15
Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description
Cannot free memory N/A AAAP_inner_delete_user: user entry does not exist ERROR Attempted to delete nonexistent entry N/A AAAP_inner_delete_user: wrong user state (inBegin) ERROR Software state machine error. N/A AAAP_inner_delete_user: wrong user status = xyz ERROR Software state machine error. N/A AAAP_message_handler: unknown message ERROR Software state machine error. N/A AAAP_tacacs_authentication_indication: no data received ERROR Empty tacacs packet was received from server. N/A AAAP_tacacs_authentication_indication: unknown REPLY status = xyz ERROR Unknown packet was received from specific server N/A AAAP_tacacs_authorization_indication: no data ERROR Unsupported packet was received from specific server
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
N/A AAAP_tacacs_authorization_indication: unknown RESPONSE status = xyz ERROR Unsupported packet was received from specific server N/A AAAP_tacacs_authorization_indication: wrong tacacs status ERROR Software state machine error. N/A AAAP_tacacs_task_message_handler: failed to open pipe ERROR Cannot open TACACS+ task message pipe. TACACS+ client application will not be operable. N/A AAAP_tacacs_task_message_handler: failure on select xyz ERROR TACACS+ task socket select operation failed N/A AAAP_tacacs_task_message_handler: invalid message type = xyz ERROR Software state machine error. N/A AAAP_tacacs_task_message_handler: mutex id null ERROR Error in communications with TACACS+ task N/A accept failed for sscp task Error This message is generated when an SSCP socket open error has occurred. Check the network connection.
A Messages
17
Message Severity Description
accept failed for sscp task Fault When you enable NSNA globally, the system initiates an SSCP task and uses a socket to connect the task to the NSNAS. This message indicates that the system failed to accept the socket. Confirm that a socket is available or verify the NSNAS configuration. AceEntry Mode <value> is not recognizable ERROR The ACE has modes for permit, deny, redirect, inactive. An unrecognized mode is not expected from user. This could be the result of corruption or missing/insufficient consistency check. Try removing/enabling filters on the port. Try a delete/create for the ACG from the port. Check dump using aclDumpAclTbl() or aclDumpAceList(). Acg Reference Count is <value> cannot be decremented for Acl Id <value> ERROR The filter modules table management keeps dependency between the ACL and ACG in order to allow/prevent ACL modification or deletion. Check the dump using aclDumpAclTbl(). Delete all the ACGs, ACLs, and recreate them. AcgId <value> PclId <value> cannot remove Pcl <value> ERROR This message indicates that filter configuration in hardware could not be cleared. Possible reasons for this are: A.) It is enabled on other ports B.) It does not exist in the hardware. Try removing or enabling filters on the port. AcgId <value> ProfileId <value> cannot remove profile <value> ERROR This message indicates that the template configuration in hardware could not be cleared, Possible reasons for this are: A.) The template does not exist in hardware. B.) Template is still needed in the hardware. Try removing or enabling filters on the port. AcgId <value> ProfileId <value> cannot UnBind ifIndex <value> <value>
Action Message Severity Description
Action
Action Message
Severity Description Action Message Severity Description Action
ERROR This message indicates that the template configuration in hardware could not be cleared for this port. Try removing or enabling filters on the port. Acl Reference Count is <value> cannot be decremented for Act Id <value> acl type <value> ERROR Filter modules table management keeps dependency between ACL and ACT to allow or prevent ACT modification or deletion. Check the dump using aclDumpActTbl(). Delete all the ACLs, ACTs and recreate them. aclAceListAdd() malloc() SIZE <value> FAIL ERROR This message indicates that the system is low on resources. Reduce the running configuration or reboot. aclAcgTblAdd() malloc() SIZE <value> FAIL ERROR This message indicates the system is low on resources. Reduce the running configuration or reboot. aclAclTblAdd() malloc() SIZE <value> FAIL ERROR This message indicates the system is low on resources. Reduce the running configuration or reboot. aclActTblAdd() malloc() SIZE <value> FAIL ERROR This message indicates the system is low on resources. Reduce the running configuration or reboot. aclHwBuildPceParamBlock(): AclEntry <value> AclType <value> does not have field selection in Profile for pkt type <value> ERROR
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity
A Messages
19
Description
The template associated with the ACL does not have the fields configured for rules in the ACL. A missing or incomplete consistency check or corruption could cause this. Try removing or enabling filters on the port. Try to delete or create the ACG from the port. Check dump using aclDumpAclTbl() or aclDumpAceList(). aclHwBuildPceParamBlock(): AclEntrys AclType is NOT SUPPORTED WARNING Two possible ACL types are IP, Non-IP. Any other value for type field indicates a corruption or incorrect information in the instrumentation table. Try removing or enabling filters on the port. Try to delete or create the ACG from the port. Check dump using aclDumpAclTbl() or aclDumpAceList(). aclHwBuildPceParamBlock(): AclId <value> ProfileId <value> NOT FOUND <value> ERROR The template is expected in the hardware, but is not found. Try removing or enabling filters on the port. Try to delete or create for the ACG from the port. Check dump using aclDumpAclTbl() or aclDumpAceList(). aclHwBuildPceParamBlock(): Pcl size <value> exceeding Max Pcl size <value> for AclId <value> ERROR Specified ACG required more than 128 filters in the hardware. This could result from an attempt to use rules with conditional matching such as greater, less, range, not-equal. Try to minimize the operators. If that does not help, remove some ACEs from the ACLs. aclHwBuildPceParamBlock(): Profile is corrupted # of Match fields exceeding limit per Pce <value> WARNING The hardware cannot support more than 16 bytes for each ACL type. A missing or incomplete consistency check or corruption can cause this. Try removing or enabling filters on the port. Try to delete or create the Acg from the port. Check dump using aclDumpAclTbl() or aclDumpAceList(). aclHwBuildPceParamBlock(): ProfileEntrys MatchInfo has unsupported field <value> at index <value> WARNING
Action
Action
Message Severity
Description Action
A rule in the ACL has a match field that could not be handled correctly. Try removing or enabling filters on the port. Try to delete or the ACG from the port. Check dump using aclDumpAclTbl() or aclDumpAceList(). aclHwBuildProfileParamBlock(): ActEntrys AclType <value> is NOT SUPPORTED WARNING Two possible ACL types are IP, Non-IP. Any other value for the type field indicates a corruption or incorrect information in the instrumentation table. Try removing or enabling filters on the port. Try a delete or create for the ACT. If the ACT entry cannot be deleted, try a reboot. Check dump using aclDumpActTbl(). aclHwBuildProfileParamBlock(): ActEntrys MatchInfo has unsupported field <value> at index <value> WARNING This message indicates the ACT entry has a field selection that could not be handled correctly. Try removing or enabling filters on the port. Try a delete or create for the ACT. If ACT entry cannot be deleted, try a reboot. Check dump using aclDumpActTbl(). aclHwBuildProfileParamBlock(): ActEntrys size <value> is corrupted/invalid WARNING The size of the ACT entry is determined by the number of fields selected for each ACL-type. Try removing or enabling filters on the port. Try a delete or create for the ACT. If the ACT entry cannot be deleted, try a reboot. Check dump using aclDumpActTbl(). aclHwCreateAction: Bridged/routed is NOT specified with remarking DSCP and 802.1p INFO Remarking DSCP and 802.1p is supported for only one of the routed/bridged traffic types in one rule. Thus, you must be sure to specify the routed/bridged traffic-type in the rule. Try removing or enabling filters on the port. Try a delete or create for the ACG from the port. Check remarking configuration. Dump using aclDumpAclTbl() or aclDumpAceList(). aclHwCreateAction: Policy Id <value> doesnt exist
Action
Message
A Messages
21
Severity Description Action
ERROR The policy entry for policing is managed in the QoS configuration. The policy entry specified in the ACE is not found in the QoS tables. Ensure that the policy exists with the specified policy ID. Try removing or enabling filters on the port. Try to delete or create for the ACG from the port. Check policy ID in the filter. Dump using aclDumpAclTbl() or aclDumpAceList(). aclHwCreateAction: unexpected DP value <value> ERROR The QoS map table lookup returned an invalid Drop precedence value. Ensure QoS map tables are correct. Try removing or enabling filters on the port. Try a delete or create for the ACG from the port. Check remarking configuration. Dump using aclDumpAclTbl() or aclDumpAceList(). aclHwInit(): Create Action FAIL with gt status <value> ERROR During filter initialization some hardware resources are required. A default action is required to create a template. This default action is applicable for the types of traffic which do not have any filters configured. Try a reboot. aclHwModifyActionStats(): tapiBindTcToAction() failed AceId <value> ActionId <value> WARNING Statistics/counters resources could not be released from the filter. Try to enable or disable statistics on the filter. aclHwModifyActionStats(): Tc Id <value> tapiUnBindTcToAction() FAIL WARNING The statistics/counters resources could not be released from the filter. Try to enable or disable statistics on the filter. aclIfIndexTblAdd() malloc() SIZE <value> FAIL ERROR This message indicates the system is low on resources. Reduce the running configuration or reboot.
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
Message Severity Description Action Message Severity Description Action
aclNhopTblAdd() malloc() SIZE <value> FAIL ERROR This message indicates the system is low on resources. Reduce the running configuration or reboot. ActProfileIdMap unexpected NumIf count for ActId <value> ProfileId <value> WARNING The map table for the template in the application and hardware is incorrect. Try a reboot.
Add ARP <IP Address/MAC Address> for RSMLT PEER. IP RSMLT is not working properly. Warning This message indicates an error when you attempt to modify ARP records used by RSMLT. This error may impact RSMLT backup functionality. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. addMrdiscNeighbor: cant allocate memory ERROR MRDisc is not supported in the Passport 8300, so this error should not occur. N/A
Add Smlt Id Failed as Vlan <Vlan ID> not found Error This message indicates that a valid VLAN is not found when RSMLT attempts to update the SMLT and SLT IDs in a Vlan. Record the error message and configuration, and reboot the chassis. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. Add IP RSMLT temporary default route failed for vrf <Vrf ID> when IST up Error This message is generated when RSMLT does not add a temporary default route for a VRF instance.
A Messages
23
Action
You can continue to operate the chassis, but contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. add_virtual_nbr : Malloc Failed. Error A malloc failure occurs when a virtual Nbr is added. Reduce the running configuration file size or reboot the switch. Adding port <> to vlan <> failed Fault This message is generated when the system cannot change the VLAN membership of the specified NSNA port. Disable and enable the NSNA port. AllocateCLIContext malloc failed ERROR This message indicates the system is unable to allocate memory for the NNCLI context. N/A Allow Mac Address table full. Cant add more! ERROR This message is generated when the learned MAC entries have exceeded the Max MAC allowed count of 2048. N/A Allow Mac Address table is full. Cant learn Mac <value>! ERROR This message is generated when the learned MAC entries have exceeded the Max MAC allowed count of 2048. N/A alwMacAddrAgeoutAutolearn: cant take semaphore! ERROR This message is generated when the system cannot obtain the allowMac semaphore. N/A
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
alwMacTblCheckAndLearn: cant take semaphore! ERROR This message is generated when the system cannot obtain the allowMac semaphore. N/A
Message Severity Description Action Message Severity Description
APP_LOCK failed ERROR This message indicates that the system cannot get the allowed MAC semaphore. N/A arpadd: move unresolved entry, but usrdata is NULL ERROR This message is generated when resolving an ARP if the system finds a corresponding unresolved ARP entry. The unresolved ARP entry is then changed to resolved. To update this entry in hardware, the system uses the usrdata to find the hardware information. Contact the customer support team if the problem persists. ArpReqGen: arpaddUnres failed for <ip> ERROR This message is generated when the system cannot add to the software ARP unresolved table. N/A ArpRspProc: Out of memory! ERROR This message is generated when the system could not allocate memory for a temporary ARP entry to be added in the ARP table. Contact the customer support team if the problem persists. ArpTic: failed to get arp activity from hardware. Going to refresh the arp anyway ERROR This message is generated when failing to get the activity status from hardware for this ARP entry results in ARP aging not taking place. The ARP entry is refreshed.
Action Message Severity Description Action Message Severity Description Action Message Severity Description
B Messages
25
N/A Authentication failed for mac <mac addr> on port <> vlan <> Information This message indicates that MAC authentication failed for the specified MAC address. Accept the portal authentication or confirm NSNAS configuration. autoSavePcapData: Memory not available to save all packets. Saving only <number-of-packets-saved> of <total-number-of-packets> packets INFO This message is generated when PCAP tries to do an autosave and finds that not enough memory is in the PCMCIA to store all packets. Free up some memory in the PCMCIA. avpair_get Unknown attribute x ERROR This message indicates that a RADIUS attribute unknown to the Passport 8300 is being looked-up. Verify that the sent and received RADIUS packets contain known attributes.
B Messages
Message Severity Description Action bind failed ERROR This message specifies that a socket cannot be bound for the bootp daemon. Reboot the switch and contact the customer support team if the problem persists. Bind failed for SSCP socket Error This message is generated when an attempt to bind the SSCP socket has failed. Check the network connection. Bind failed for SSCP socket Fault
Message Severity Description Action Message Severity
Description Action
This message indicates that the system cannot bind the SSCP socket to the loopback IP address. Verify the operation of the loopback address, disable and enable NSNA globally, or confirm NSANS configuration. Bkend state of Port -- - Recd accept from server INFO This messages indicates that an 802.1X Backend Authentication State Machine received an Access-Accept message from the RADIUS server. No action is necessary. Bkend state of Port -- - Recd accept from server INFO This message is generated when 8021x Backend Authentication State Machine receives a Access-Accept message from RADIUS server. No action necessary Bkend state of Port -- - Recd EAP request from Server INFO This message is generated when 8021x Backend Authentication State Machine receives EAP request from RADIUS server. No action necessary Bkend state of Port -- - Recd Reject from server INFO This message indicates that an 802.1X Backend Authentication State Machine received an Access-Reject message from the RADIUS server. No action is necessary. Bkend state of Port -- - Recd Reject from server INFO This message is generated when 8021x Backend Authentication State Machine receives a Access-Reject message from RADIUS server. No action necessary Bkend state of Port -- - Recd Response from supplicant INFO
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity
B Messages
27
Description Action Message Severity Description Action Message Severity Description Action Message Severity Description
This message indicates that an 802.1X Backend Authentication State Machine received a response from a supplicant. No action is necessary. Bkend state of Port -- - Recd Respose from supplicant INFO This message is generated when 8021x Backend Authentication State Machine receives a response from supplicant. No action necessary Bkend state of Port -- Recd EAP request from Server INFO This message indicates that an 802.1X Backend Authentication State Machine received an EAP request from the RADIUS server. No action is necessary. blocked DHCP packet for possible DOS attack on port <x/y> from <mac_address> Warning This message indicates that the source MAC address in an Ethernet header differs from the client hardware address in the DHCP packet or for DHCP release/decline packets, clients do not exist in NSNA client info. Check for a virus on the specified port or for an attack on the system by an illegal user. Blocked unauthorized nncli access WARNING This message indicates that unauthorized NNCLI access has been blocked. N/A Blocked unauthorized nncli enable access INFO This message indicates that unauthorized NNCLI enable access has been blocked N/A bootpdGo: Cant create Bootp Server task! INFO
Action
Message Severity Description Action Message Severity Description Action Message Severity
Description Action
This message indicates a Bootp Server task cannot be created. Reboot the switch and contact the customer support team if the problem persists. bootpSyncCallback: Invalid msgType <type> ERROR This message specifies that an invalid argument exists for the bootp module sync callback function. N/A bootpSyncCallback: unsupported version <ver> ERROR There is a synchronization issue between two CPUs, perhaps a bootp module version mismatch N/A bootpSyncNotify: malloc failed FATAL This message indicates the system has run out of memory Reboot the switch and contact the customer support team if the problem persists. brdgSetSmltBridgeId: cant take semaphore! ERROR This message is generated when a semaphore cannot be taken while setting the smlt bridge ID. N/A brdgStart: Cant create mutex semaphore! Fault This message is generated when there is insufficient system memory or a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgStart: StgPortTable exists!
Message Severity Description Action Message Severity Description Action Message Severity Description Action
Message
B Messages
29
Fault This message indicates that data variations exist before the switch creates an STG port table. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgStart: StgPortTable calloc Failed! Fault This message indicates that there is insufficient memory available for the system to allocate memory for data variation. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgLoad: cant setup default configuration! Fault This message indicates that the system failed to run the default bridge configuration. Verify the default STG configuration. brdgProcessBpdu: pStg is NULL stg X port A/B Fault This message indicates that the bridge cannot retrieve STG information when processing a BPDU. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgProcessBpdu: cant take semaphore Fault This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgReceiveBpdu: cant take semaphore
Message
Fault This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgReceiveNonNtBpdu: cant take semaphore Fault This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgLoad: cant lock mutex!! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgPortConfigurable: cant take semaphore! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgPortConfigurable: Cant add port to the Default STG! Error This message indicates the system failed to add a port to the default STG. Verify the STG configuration. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis.
B Messages
31
brdgPortNotConfigurable: cant take semaphore! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgPortNotConfigurable: cant remove port from STG!! Error This message indicates that the system failed to remove a port from an STG. Verify the STG configuration. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgPortPresent: cant take semaphore! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgLinkUp: cant lock mutex! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgLinkDown: cant lock mutex! Error This message is generated when there is insufficient system memory or there is a conflict in data access.
Action
Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgCreateSpanTreeGroup: Cant create BPDU MAC Address record! Error This message is generated when the system fails to create a BPDU MAC address. Verify the STG configuration. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgCreateSpanTreeGroup: Cant create IEEE VLAN ID record! Error This message indicates that the system failed to create a IEEE VLAN ID for an STG. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgCreateSpanTreeGroup: Cant create mutex semaphore! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgEnableTrunk: cant lock mutex! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgEnableUni: cant lock mutex!
Message
B Messages
33
Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgTick: cant lock mutex Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgGetStpPortStats: cant take semaphore! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgClearStats: cant take semaphore! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgLock: task=%s cant lock mutex! Error This message is generated when there is insufficient system memory or there is a conflict in data access.
Action
Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgUnlock: task=%s cant unlock mutex! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgDisablePortinAllStg: cant lock mutex! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgSetMltStp: cant lock mutex! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. brdgSetPortStpOff : cant lock mutex! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis.
C Messages
35
brdgSetPortStpOnOff : cant lock mutex! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis.
C Messages
Message Severity Description Action Message Severity Description Action Message Severity Description Cannot add an ARP entry to a non-existing port INFO This message is generated when a port is not found to add an entry to the ARP table. Check the configuration for the port. Cannot add MAC range filter for EAP! ERROR This message indicates the MAC filter for capturing EAP packets to the CPU is not created. N/A can not add multicast route for group <group address>, errorno=<value>. Fault When you create a multicast group for MVR, the system creates a hardware multicast route. This message is generated when the system cannot create the hardware multicast route Disable and enable MVR. If the error does not clear, restart the switch. Cannot add MAC range filter for LLDP! ERROR This message is generated when the Std MAC address, 01:80:c2:00:00:0e, caould not be added to the MAC range filter during LLDP initialization. Reboot required. cannot allocate announce gt nexthop tbl link list object ERROR
Action Message Severity Description Action Message Severity
Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description
This message is generated when the system cannot allocate memory for the list used by the software next-hop table. Contact the customer service team if the problem persists. Cannot allocate announce gt nexthop tbl link list object ERROR This message indicates that memory cannot be allocated for the list used by the software next-hop table. Contact the customer support team if the problem persists. Cannot allocate filter index object ERROR This is a fatal error message indicating the switch is unable to allocate the access filter list element due to the lack of available memory. N/A cannot allocate filter link list ERROR This message indicates that a fatal error occurred during the allocation of the filter index due to the lack of available memory. N/A cannot allocate group index object FATAL This message is generated while initializing the IGMP group list if the DRAM memory is exhausted. Increase DRAM memory size. cannot allocate group link list object FATAL This message is generated while initializing the IGMP group list and the DRAM memory is exhausted. Increase DRAM memory size. cannot allocate id stack object for Udp PortFwd tbl FATAL This message is generated when allocation and initialization of the stack with a given stack size fails.
C Messages
37
Action
Close all CLI sessions to free up memory.
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description
cannot allocate igmp interface index object Fatal A failure has occurred in allocating memory for igmp interface index object. Reduce the running configuration file size or reboot the switch. cannot allocate PIM interface index object Fatal A malloc memory failure for the PIM interface index has occurred. Reduce the running configuration file size or reboot the switch. cannot allocate PIM link list object Fatal A malloc memory failure for the PIM link list has occurred. Reduce the running configuration file size or reboot the switch. cannot allocate rps node Fatal This message indicates that there is insufficient system memory for the RPS module to initiate VRFs. Wait for system memory to become available or reboot the chassis. cannot allocate policy prefix object/ Fatal This message indicates that there is insufficient memory available for the system to allocate a policy prefix list. Wait for system memory to become available or reboot the chassis. cannot allocate policy prefix avl head object Fatal This message indicates that there is insufficient memory available for the system to allocate a policy prefix list. Wait for system memory to become available or reboot the chassis. cannot allocate memory for packet, length=<value>. Fault This message is generated when the system cannot allocate enough memory for an IGMP packet.
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
Check for a possible memory leak or restart the switch. Cannot Allocate Memory for SNMP EngineId String ERROR This message is generated when the system is out of memory while executing the software. Report the problem Cannot Allocate Memory for SNMP Engineld String ERROR This message indicates that the system ran out of memory while executing the software. Report the problem. cannot allocate memory for tIGMP_QUERIER FATAL This message indicates there is a memory allocation failure. N/A cannot allocate memory for tMVRENTRY Fault This message indicates that there is insufficient system memory for the system to operate. Check for a memory leak or reboot the switch. cannot allocate memory for tMVRMEMBER Fault This message indicates that there is insufficient system memory for the system to operate. Check for a memory leak or reboot the switch. cannot allocate memory for tMVRVLAN Fault This message indicates that there is insufficient system memory for the system to operate. Check for a memory leak or reboot the switch.
C Messages
39
cannot allocate OSPF access head FATAL This message is generated when the system runs out of DRAM memory. Close all CLI sessions to free memory. cannot allocate OSPF access head avl head object FATAL This message is generated when the system runs out of DRAM memory. Close all CLI sessions to free memory. cannot allocate rcip_route_index object FATAL This message is generated when the system is unable to allocate memory for the RCIP object. Increase DRAM size and contact customer support for further troubleshooting. Cannot bind BpduVlanId <value> to stg <value>, err=<value> ERROR The binding of the Spanning Tree Group (STG) to the BPDU VLAN failed in hardware during STG creation. Reboot the switch and contact the customer support team if the problem persists. Cannot bind Vlan <value> to stg <value>, err=<value> ERROR The binding of the STG to the BPDU VLAN failed in hardware during STG creation. Reboot the switch and contact the customer support team if the problem persists. Cannot config card due to condition specified INFO This message is generated when a card cannot be configured because of the specified conditions. N/A
Message Severity
Cannot configure card. Please remove and insert again ERROR
Description Action Message Severity Description Action
This message is generated to specify that card should be removed and then re-inserted. Contact Customer Support for further troubleshooting. Cannot create logSendFatalLogTask task FATAL The logSendFatalLogTask task cannot be created. Reboot the switch and contact the customer support team if the problem persists. Cannot create message queue for radius snmp accounting Radius Snmp acoounting not enabled ERROR This message indicates the software resource for handling accounting messages cannot be acquired. Contact customer support. can not create linkLayer interface for vid <value> vidx <value>, group=<group address>, errorno=<value> Fault When you create an IGMP snoop group in MVR, the system creates a hardware link layer interface. This message is generated when the system cannot create the hardware link layer interface. Disable and enable MVR. If the error does not clear, restart the switch. can not create MLL for vid <value> vidx <value>, group=<group address>, errorno=<value>d Fault When you create an IGMP snoop group in MVR, the system creates a hardware record. This message is generated when the system cannot create the hardware record. Disable and enable MVR. If the error does not clear, restart the switch. Cannot create TACACS+ client, maximum users reached ERROR Software state machine error. N/A
Action Message Severity Description Action
C Messages
41
Cannot delete ARP entry < IP Address/MAC Address> of IP RSMLT Peer when forwarding for peer stop Warning This message indicates that ARP entries used by an IP RSMLT peer are not deleted when RSMLT discontinues backup forwarding for that peer. Record the error message and configuration, and reboot the chassis. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. Cannot delete ARP entry <IP Address/MAC Address> of IP RSMLT Peer when holdup forward to forward Warning This message indicates that an error occurred when you attempted to clear an ARP record used by RSMLT. Delete the ARP entry added by RSMLT from the ARP table and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. can not delete multicast route for group <group address>, errorno=<value>. Fault When you remove a multicast group from MVR, the system removes a hardware record. This message is generated when the system cannot remove the hardware record. Disable and enable MVR. If the error does not clear, restart the switch. can not delete MLL for vid <value> vidx <value> group=<group address>, errorno=<value> Fault When you remove an IGMP snoop group from MVR, the system removes a hardware record. This message is generated when the system cannot remove the hardware record. Disable and enable MVR. If the error does not clear, restart the switch. can not delete linkLayer interface for vid <value> vidx <value>, group=<group address>, if_index=<value>, errorno=<value> Fault When you remove an IGMP snoop group from MVR, the system removes a hardware record. This message is generated when the system cannot remove the hardware record.
Action Message Severity Description Action Message Severity Description Action
Disable and enable MVR. If the error does not clear, restart the switch. Cannot set max ecmp paths number without enabling ECMP feature first! ERROR This message indicates that you did not enable ECMP to change the maximum ECMP path number. You must enable ECMP prior to changing the maximum ECMP path number. Cannot turn on IP routing on MAC addr = < MAC Address> of IP RSMLT Peer when forwarding for peer. Warning This message is generated when a Mac Address cannot be set as routable when RSMLT is backing up for the IST peer. Check the forwarding database table to verify MAC addresses are synchronized successfully between IST peers. If the Mac addresses are synchronized successfully, disable and enable RSMLT on the IST peer. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. Cannot turn off IP routing on MAC addr = <MAC Address> of IP RSMLT Peer when forwarding for peer Warning This message is generated when IP routing is not disabled for an IP RSMLT peer Mac address when RSMLT is backing up for that peer. You can continue to operate the chassis. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. Cannot turn off IP routing on MAC addr = <MAC Address> of IP RSMLT Peer when Stop Forwarding for Peer Warning This message is generated when IP routing is not disabled for an IP RSMLT peer Mac address when RSMLT discontinues backing up for that peer. You can continue to operate the chassis. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. Cannot unbind BpduVlanId <value> from stg <value>, err=<value>! ERROR
Message Severity
C Messages
43
Description Action
This message indicates the unbinding of the STG from the BPDU VLAN failed in hardware during STG deletion. Reboot the switch and contact the customer support team if the problem persists. Cannot unbind vlanId <value> from stg <value>, err=<value>! ERROR This message indicates the unbinding of STG from the BPDU VLAN failed in hardware during STG deletion. Reboot the switch and contact the customer support team if the problem persists. cannot update nexthop tbl entry ERROR This message is generated when the system is trying to update the software next-hop entry, but finds the pointer to the next hop entry is NULL. Contact the customer service team if the problem persists. Cannot update nexthop tbl entry ERROR When trying to update the software next-hop entry, it was discovered that the pointer to the next hop entry is NULL. Contact the customer support team if the problem persists. cant unbind BpduVlanId %d from stg %d, err=%d! Error This message is generated when the system fails to unbind a VLAN from an STG. Verify the STG configuration. Card configured OffLine: Slot=<value> Type=<value FATAL This message indicates the card was configured off-line. N/A Card Failed: Slot=<value> Type=<value>, ERROR This message specifies the card failed.
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description
Re-insert or replace the card. card_portInit: Out of memory: <value> FATAL This message indicates memory cannot be allocated. Reboot the switch and contact the customer support team if the problem persists. cfgXbarOnCpsfCard: cannot use cpu <value> card as relay card ERROR This message indicates the CPU card cannot be used as a relay card. Contact the customer support team if the problem persists. cfgXbarOnCpsfCard: gtXbarSetUcRoute failed - <value> ERROR This message indicatest the set XBAR unicast table failed. Contact the customer support team if the problem persists. Chassis type cannot be determined INFO The chassis type cannot be determined because the value read from the backplane SEEPROM is bad, or the Passport 8300 card is inserted in a chassis that is not supported by this software. Please verify that the chassis is either a Passport 8600 or 8300. Chassis type unknown ERROR The SEEPROM information about chassis type is wrong or unsupported Contact the customer support team for assistance. chCardIn: Cant read SEEPROM on slot=<value>: <value> <value> INFO This message indicates that the SEEPROM cannot be read for the card. Re-insert or replace the card. chCOPListenTimerSet: global set, still setting <value> INFO
Message Severity Description Action Message Severity Description Action Message Severity Description
Action Message Severity Description Action Message Severity Description Action Message Severity
C Messages
45
Description Action
This message indicates the coprocessor listen timer is being set before it expires. This should not happen in a normal scenario. N/A
chGetFrontPortFromLport: Error to get front port WARNING This message is generated when a software error occurs. Contact the customer support team if the problem persists. chProcHelloFromProc:NPAL_SetDevMac: failed for slot <value> ERROR This message indicates a hardware write failed to set the device MAC. Try re-inserting the card. chRxHelloFromCOP: problem making port <value> present on slot <value> ERROR This message indicates the port present failed for a certain port. Try re-inserting the card. If the problem persists, contact the customer support team. Closed rlogin connection from <ip-address> user <user-name> INFO This message is generated when an rlogin connection to the switch terminates. N/A Closed telnet connection from <ip-address> user <user-name> INFO This message is generated when a telnet connection to the switch terminates. N/A cl_ULink: unlinking x twice/ Fault This message indicates that when you added a static route, the internal route was corrupted and the system operation is unstable. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis.
cl_Link: linking x twice/ Fault This message indicates that when you added a static route, the internal route was corrupted and the system operation is unstable. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. cl_LinkGen: linking x twice Fault This message indicates that when you added a static route, the internal route was corrupted and the system operation is unstable. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. Connection lost to slot <value> ... ERROR IPC connection between the CP card and a given I/O slot is lost. Reboot the switch and contact the customer support team if the problem persists. Connection not found for connection Id <value> ERROR IPC connection between the CP card and I/O card cannot be found in software database. This is caused by the IPC connection setup, or a corruption of the software data structures. Connection rejected with NSNAS IP <IPAddr> status subCode <reason> Error This message is generated when connection with NSNAS IP has been rejected, with the status subCode <reason>:=[Version mismatch|NSNAS subnet mismatch|NSNAS invalid hello or inactivity interval| <protocol version>] Check for version, NSNAS mismatches or invalid NSNAS hello, inactivity interval. Connection rejected with NSNAS IP <> status subCode <reject reason>
Action
Message
C Messages
47
Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message
Fault This message is generated when the switch rejects an SSCP connection. Refer to reject reason included in the message for the action required. Consistency check failed for Bootp table syncing RED_BOOTP_INFO ERROR This message indicates a consistency check for the bootp table failed. N/A Consistency check failed for table syncing tSmltInfoSyncEntry ERROR This message is generated when the message length is not correct for SMLT synchronization. N/A cosLibInit: failed ERROR This message specifies the CoS library initialization failed. Reboot the switch if you wish to use CoS functions. Could not allocate context ERROR This message indicates that context for the NNCLI could not be allocated. Reboot the switch and contact customer support if the problem persists. Could not allocate memory for bufLog! WARNING This message indicates the Passport 8300 is unable to allocate memory. N/A Could not allocate memory for new next-hop entry ERROR Memory cannot be allocated for the new software next-hop entry. Contact the customer support team if the problem persists. Could not create xlrclip for nncli
Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity
ERROR This message specifies the Passport 8300 is unable to create xlrclip for the NNCLI. Reboot the switch and contact customer support if the problem persists. Could not delete software mirroring Entry <id> WARNING This message specifies that a mirroring software table entry cannot be deleted because the table is empty or the ID cannot be found. Verify correct command parameters in documentation and retry. Could not delete the hw mirroring Entry <id> WARNING This message specifies that a mirroring hardware table entry cannot be deleted because of an incorrect ID or the lack of an OS resource. Verify the correct command parameters in the documentation and try again. Could not delete the sw mirroring Entry <id> WARNING This message specifies that a mirroring software table entry cannot be deleted because the table is empty or an ID cannot be found. Verify the correct command parameters in the documentation and try again. Could not enable the hw mirroring Entry <id> WARNING This message specifies that a mirroring hardware table entry cannot be added because of an incorrect ID or the lack of an OS resource Verify the correct command parameters in the documentation and try again. Could not find the Ip Rec forIndex ERROR This message is generated when the system tries to read the memory location of an existing IP record. Contact customer support for further troubleshooting. Could not get the area structure for aId= _._._._ WARNING
C Messages
49
This message is generated when you attempt to pass an invalid or null area to de-couple OSPF. The area is not present so no action is required. Could not start AuCacheAging Task, <errno> FATAL This message indicates the task could not be created. Reboot the switch and contact the customer support team if the problem persists. Could not start portMgr Task, <value>, FATAL This message indicates the portMgr task could not be created. Reboot the switch and contact the customer support team if the problem persists. cpp2LargeFbufInit: Cant allocate memory! FATAL This message is generated when the system could not allocate memory for FBUF which is used to either transmit or process large received packets. This means the system will not be able to perform receive or transmit functions. Reboot the switch and contact the customer service team if the problem persists. cppAddDefaultRouteHook: ifAddrSet failed! ERROR This message is generated when the registration of the CP interface with vxWorks has failed. Any communication with the vxWorks IP stack will also fail. Reboot the switch and contact the customer support team if the problem persists. cppAddDefaultRouteHook: ifFlagChange failed! ERROR This message is generated when registration of the CP interface with vxWorks fails. Any communication with the vxWorks IP stack will also fail. Reboot the switch and contact the customer support team if the problem persists.
Action
Action
cppAddDefaultRouteHook: ifMaskSet failed! ERROR This message is generated when registration of the CP interface with vxWorks fails. Any communication with the vxWorks IP stack will also fail. Reboot the switch and contact the customer support team if the problem persists. cppAddDefaultRouteHook: routeAdd failed! ERROR This message is generated when registration of the CP interface with vxWorks fails. Any communication with the vxWorks IP stack also fails. Reboot the switch and contact the customer service team if the problem persists. cppAllocFBufs: malllc(<value>) failed ERROR This message is generated when the system could not allocate memory for FBUF which is used to either transmit or process a received packet. This system is not able to perform receive or transmit functions. N/A cppGetFBuf: bdInUse <value> bdGptr <value> bdGptr <value> ERROR This message is generated when the buffer that has been allocated by the system is already is in use. It either means there has been an error during the cleanup or some other software issue has arisen. Depending on the cause of the problem, it may have serious consequences. N/A cppGetFBuf: netFreeRxGtbuf <value> failed!! ERROR This message is generated when some type of pointer corruption has happened, or if somewhere else the gtBuf has incorrectly been released (freed). N/A cppInitFBufPool: Cant allocate memory! FATAL
Action Message Severity
C Messages
51
Description
This message is generated when the system could not allocate memory for FBUF which is used to either transmit or to process a received packet. This means system is not able to perform receive or transmit functions. Reboot the switch and contact the customer support team if the problem persists. cppProcAuMsgBody: Port not in Vlan! Mac <mac> VlanId <id> Port <portnum> WARNING This message is generated when some mismatch has occurred in terms of receiving a packet, or when software information regarding the port/VLAN and driver/hardware information is out of sync. N/A cppProcAuMsgBody: STG Vlan for MLT not found! Mac <mac> VlanId <id> MltId <mltid> WARNING This message is generated when the MLT is not a member of the Spanning Tree Group (STG) that the VLAN belongs to. N/A cppProcAuMsgBody: STG Vlan for Port not found! Mac <mac> VlanId <id> Port <portnum> WARNING This message is generated when the port does not seem to be a member of the STG that the VLAN is configured for. N/A cppProcAuMsgBody: Vlan for MLT not found! Mac <mac> VlanId <id> MltId <mltid> WARNING This message is generated when the MLT does not seem to be a member of the expected VLAN. This indicates that the software information regarding the port/VLAN and driver/hardware information is not synchronized. N/A cppProcAuMsgBody: Vlan for Port not found! Mac <mac> VlanId <id> Port <portnum> ERROR
Action
Description
This message is generated when port does not seem to be member of the expected VLAN. This indicates that the software information regarding the port/VLAN and driver/hardware information is out of sync. N/A cppProcAuMsgBody:Port Corrupted! Port <portnum> ERROR This message is generated when some inconsistencies are seen in the given address update message. N/A cppProcTxFrame: cppTxFrame failed! ERROR This message is generated when processing the request to send the packet from the TX_QUEUE of the main Task fails. The packet is not sent out. However, the application may not be aware of this. N/A cppPutFBuf: netFreeRxGtbuf <value> failed!! FATAL This message is generated when the buffer that is being allocated by the system is already is in use. It either means some error has occurred during the cleanup, or indicates some other software issue has arisen. Reboot the switch and contact the customer support team if the problem persists. cppPutFBuf: NULL address! FATAL This message is generated when the memory allocated for FBUF has been corrupted. Reboot the switch and contact the customer service team if the problem persists. cppPutFBuf: Trying to put a free BD! ERROR This message is generated when FBUF has already been freed or the FBUF chain is corrupted. N/A
Action Message Severity Description Action Message Severity Description
Action
C Messages
53
cppSchedule is invoked not from tMainTask FATAL This message indicates that according to the software design, this function is being incorrectly invoked. It should only be called by tMainTask. Reboot the switch and contact the customer service team if the problem persists. cppStart: Cant create CP Port receive task! FATAL This message is generated when a drastic situation arises and the system ceases bringing up an operation. For example, during system start-up, it could not create tMainTask to perform the majority of the switch functions. Reboot the switch and contact the customer support team if the problem persists. cppStart: Cant create socket tx task INFO This message is generated when a drastic situation arises and the system ceases bringing up an operation. For example, during system start-up, it could not create a task used to process the request to send packets. N/A cppStart: Inconsistent value of the CP physical port number! INFO This message is generated when a drastic situation arises and the system ceases bringing up an operation. For example, during the system start-up, the physical port representation does not match the expected value. N/A cppTxFrameBody: cant take semaphore! FATAL This message is generated when the system could not obtain the semaphore needed to transmit packet. Reboot the switch and contact the customer support team if the problem persists. cppTxFrameBody: could not create gtBuf for transmit vlan=<vlanid> WARNING
Action
Message Severity
Description
This message is generated during the packet transmit from the system gtBuf buffer when the driver is not available. Thus, the packet that needs to be sent for the VLAN will not be sent. N/A cppTxFrameBody: could not free netFreeTxGtBuf ERROR This message is generated when some type of pointer corruption has occurred, or if somewhere else the gtBuf has incorrectly been released (freed). N/A cppTxFrameBody: No room for the TxPH! (off=<value>) ERROR This message is generated when the packet is not transmitted. N/A cpu is hotstandby ERROR or INFO+B360 This is an informational message indicating that the CPU is the standby CPU. N/A Creation of temporary vlan failed for loopback WARNING This message indicates that the creation of the temporary VLAN failed for loopback. Contact the customer support team if the problem persists.
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
D Messages
Message Severity Description Action Message Severity Dead interval <value> is not a multiple of <value> WARNING This message indicates that the dead interval entered is not a multiple of the OSPF hello interval. Enter a valid dead interval multiple of the OSPF hello interval. delete MAC record < MAC Address> of IP RSMLT Peer Failed when Stop Forwarding for Peer Warning
D Messages
55
Description Action
This message is generated when IP routing is not disabled for an IP RSMLT peer Mac address when RSMLT discontinues backup forwarding for that peer. You can continue to operate the chassis, but contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. Deny/Permit setting update failed while updating next hop for Acl <value> Ace <value> with status ERROR This message indicates the ACE is in redirect mode and the specified next-hop became available/unavailable. However, the filter could not be updated in hardware. Check the ARP and hardware next-hop tables. Deny/Permit setting update for for filter action FAIL with status: <value> ERROR This message indicates the ACE is in redirect mode and the specified next-hop became available/unavailable. However, the filter could not be updated in hardware. Check the ARP and hardware next-hop tables. detected bad timer_cum logic ERROR This message is generated when there is no OSPF timer to link or a timer is faulty. Rerun OSPF. If the problem is not resolved, contact customer service with the following information available for further analysis:

system logs, including any memory dumps switch configuration network topology
detected loop - 1: timer <value> TRYING TO LINK A TIMER THAT ALREADY EXISTS ERROR This message is generated when the system tries to link a timer that already exists. Internal protocol error, upgrade the software.
detected loop - 2: timer 0x%x TRYING TO LINK A TIMER THAT ALREADY EXISTS ERROR This message is generated when the system tries to link a timer that already exists. Internal protocol error, upgrade the software. detected loop in ospfLink ERROR This message is generated when the OSPF timer link runs more than the existing number of timers. Rerun OSPF. If the problem is not resolved, contact customer service with the following information available for further analysis due to insufficient MLTs:
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message
DHCP server is configured to offer VRRP IP address %s to DHCP client ERROR This message is generated when the VRRP virtual IP address on the switch is configured as a DHCP server. Verify the server IP is not configured as the VRRP virtual IP. DHCP server is configured to offer LOCAL IP address %s to DHCP client ERROR This message is generated when the local switch IP address is configured as the DHCP server. Verify the server IP is not configured as the local switch IP address. DHCP server is configured to offer Relay Agent IP address %s to DHCP client ERROR This message is generated when the current relay agent IP address is configured as DHCP server. Verify the server IP is not configured as the local relay agent. diagUpdatePortMirrorStructures_8300: Invalid Mode ID <value>
E Messages
57
Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
WARNING This message indicates that an incorrect mirroring mode parameter exists. Verify the correct command parameters in the documentation and try again. DLD file <file> is not found WARNING This message indicates that the DLD file is not found. Copy the DLD file to the flash. dmaStartupLoopback: Cant send frame! seq=<value> len=<value> ERROR This message identifies a cppTxFrame() return failure when doing the loopback test. Contact the customer support team if the problem persists. due to insufficient MLTs INFO The possible reason for this message is that the "PreConfigTask: Slot <value> NO pre-configured." N/A
E Messages
Message Severity Description EapApplyVlanAndPri: unable to add port -- to vlan -ERROR This message indicates that the system encountered an unexpected error while trying to add the 802.1X authorized port to the VLAN returned by the RADIUS server. Report the problem. EapApplyVlanAndPri: unable to add port -- to vlan -ERROR This message is generated when the system encounters unexpected error while trying to add the 8021x authorized port to VLAN returned by RADIUS server. Report the problem EapApplyVlanAndPri: Unable to set Qos priority -- for port --
Action Message
Severity Description
ERROR This message indicates that the system encountered an error while it tried to apply the QOS priority returned by the RADIUS server to the 802.1X authorized port. Verify that the QOS priority configured on the RADIUS server is valid. EapApplyVlanAndPri: Unable to set Qos priority -- for port -ERROR This message is generated when system encounters error while it tries to apply the QOS priority returned by RADIUS server to the 8021x authorized port. Verify that QOS priority configured on RADIUS server is valid eapInitTx: malloc failed for buf ERROR This message is generated when the system is out of memory while executing the software. Report the problem eaplnitTx: malloc failed for buf ERROR This message indicates that the system is out of memory while executing the software. Report the problem. EapProcessPktFromSupp: malloc failed! ERROR This message indicates that the system is out of memory while executing the software. Report the problem. EapProcessPktFromSupp: malloc failed! ERROR This message is generated when the system is out of memory while executing the software. Report the problem EapTransmitEapolPkt: Cant send frame!
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message
E Messages
59
Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
ERROR This message indicates that the system encountered an unexpected error while sending an EAPOL frame out of a port. Report the problem. EapTransmitEapolPkt: Cant send frame! ERROR This message is generated when system encounters unexpected error while sending out an EAPOL frame out of a port. Report the problem Enable Mirroring FAILED for Entry <id> Deleting the mirroring record WARNING This message specifies that a mirroring hardware table entry could not be added because of an incorrect ID or a lack of OS resources. Verify the correct command parameters in the documentation and try again. errmsg <msgcode> ERROR This message lists the error code when bootp cannot obtain the file name. Ensure that the file is on the flash. Error - Fail STG consistency check ERROR This message is generated when an STG consistency check fails. Contact customer support for further troubleshooting. Error - Fail to create STG <value> for mgmt VLAN ERROR This message is generated when the setting of a row on the STG table fails. Contact customer support for further troubleshooting. Error - Fail to delete STG ERROR This message is generated when the deletion of an STG fails. Contact customer support for further troubleshooting.
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity
Error - Fail to delete VLAN ERROR This message is generated when the deletion of a VLAN fails. Contact customer support for further troubleshooting. Error Could not enable radius SNMP accounting Task radSnmpAcct not spawned ERROR This message indicates the system is unable to create a task to handle RADIUS accounting requests. Contact customer support for further troubleshooting. Error in deleting task radSnmpAcct ERROR This message indicates the system is unable to delete the task created to handle RADIUS accounting requests. Contact customer support for further troubleshooting. Error in initializing FwdListId object ERROR This message is generated when allocation for the Fwd List Id object to store the Fwd List Ids fails. Close all CLI sessions to free up memory. error in reading data from the PCMCIA INFO This message is generated when PCAP tries to do autosave to PCMCIA and it cannot read the PCMCIA. Insert a PCMCIA card in the switch or set the autosave path to network. Error: ActId = <value> AclType = <value> Act create operation FAIL WARNING This message is generated when the default template cannot be created during filter module initialization. Try a manual configuration or reboot the switch. Error: port <port> is locked\n\n ERROR
F Messages
61
This message indicates that a VCT test cannot be run on a port that is locked. Unlock the port and run the test. ERROR: sysI2cWriteRepRead Failed WARNING This message indicates that an SFP SEEPROM cannot be read. Try replacing the SFP. If it still does not work, contact the customer support team. Error: There is no VRRP for Vrid ___ Info This message is generated when there is no VRRP instance of this Vrid. Confirm that a VRRP instance with this Vrid exists. Error: There is no VRRP configured Info This message is generated when there are no VRRP instances configured. Confirm the proper configuration of any VRRP instances. Error: There is no VRRP for Vlan ___ Info This message is generated when there are no VRRP instances configured in this vlan. Confirm that VRRP instances are configured in this Vlan.
F Messages
Message Severity Description Action Message Severity Description Action fail config STG for mgmt VLAN ERROR This message is generated when an attempt to create an STG for the specified VLAN fails. Contact customer support for further troubleshooting. failed deleting a route in rcIpRouteTblSet() ERROR This message is generated when the deletion of a route fails. Contact customer support for further troubleshooting.
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message
Failed to assign IP address to mgmt VLAN ERROR This message is generated when assigning an IP address to the management VLAN fails during the system initialization pre-configuration process. Contact Customer Support for further troubleshooting. Failed to connect TCP socket to server xyz port xyz, errno xyz ERROR Failed to set socket connect operation to specific TACACS+ server N/A Failed to create IMC VLAN ERROR This message is generated when creating an IMC VLAN fails during the system initialization pre-configuration process. Contact customer support for further troubleshooting. Failed to create semaphore for authenticating with TACACS+ protocol ERROR Cannot create a semaphore for sending messages to TACACS+ task. System resources might be low. N/A Failed to create semaphore for rcTacacsGlobalGrpConsistencyCheck ERROR Cannot create a semaphore for sending configuration messages to TACACS+ task. System resources might be low. N/A Failed to create semaphore for rcTacacsGlobalGrpGet ERROR Cannot create a semaphore for sending configuration messages to TACACS+ task. System resources might be low. N/A Failed to create semaphore for rcTacacsServerTblConsistencyCheck
F Messages
63
Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description
ERROR Cannot create a semaphore for sending configuration messages to TACACS+ task. System resources might be low. N/A Failed to create semaphore for rcTacacsServerTblGet ERROR Cannot create a semaphore for sending configuration messages to TACACS+ task. System resources might be low. N/A Failed to create semaphore for rcTacacsServerTblSet ERROR Cannot create a semaphore for sending configuration messages to TACACS+ task. System resources might be low. N/A Failed to create STG for IMC VLAN ERROR This message is generated when creating an STG for IMC fails during the system initialization pre-configuration process. Contact customer support for further troubleshooting. Failed to find a unused IP address ERROR This message is generated when an attempt to obtain an unused IP address fails. Contact customer support for further troubleshooting. FAILED To Initialize Xbar on slot <value> ERROR This message indicates that crossbar initialization was unsuccessful. Re-insert or replace the card. Failed to open TACACS+ protocol pipe ERROR TACACS+ client application is down. Cannot send messages to TACACS+ task.
N/A Failed to open socket Error This message is generated when the socket cannot be opened. Check the network connection. Failed to open socket Fault This message indicates that the system did not create the required socket when you started the SSCP server. Verify that a new socket is available, disable and enable NSNA globally, or confirm NSANS configuration. Failed to spawn sscp task Fault This message is created when the system fails to create an SSCP task. Disable and enable NSNA globally. Verify there are enough resources available to create a new SSCP task. Failed to spawn sscp task Error This message is generated when spawn sscp task has failed. Check the system status.
FAILED To write mcast table to Xbar on slot <value> ERROR This message indicates that the multicast table was not successfully written to the crossbar on the standby CPU. Re-insert or replace the card. -FATAL- null parameter to function ERROR This message is generated when there are no required parameters in the SMLT/SLT up message. N/A
F Messages
65
-FATAL- sltTblSync: malloc failed! ERROR This message is generated when a malloc SLT sync message has failed. Check memory usage. -FATAL- smltSmltInfoSync: malloc failed! ERROR This message is generated when a malloc smlt sync message has failed. Check memory usage -FATAL- vlanTblEntrySync: malloc failed! ERROR This message is generated when table-based synchronization of the IP address assigned to a VLAN occurs. This is caused by unavailable memory and thus, memory cannot be allocated for the entry. Increase the DRAM size. file <file> function <function> line <line> bitnum <bitnum> Software license violation <message> WARNING This message specifies a software license violation. There is no license to execute this command. Contact the customer support team. file already present in the PCMCIA INFO This message is generated when PCAP tries to save captured packets to the PCMCIA (autosave). The file is already present and PCMCIAWRAP is false. Set PCMCIAWRAP to TRUE or remove the file from the PCMCIA. Filter Attachment to port <port num> failed Error This message is generated when the system fails to attach a filter to an NSNA port. Disable and enable NSNA on the port. Filter could not be configured on interface <value> ERROR
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity
Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description
This message is generated when restoring a filter configuration for ports on the hot-inserted card is unsuccessful. Reconfigure the filters or source the configuration file. Finished insertion for slot <value> INFO This message indicates that the insertion process has finished. N/A Finished removal for slot <value> WARNING This message indicates that the removal process has finished. N/A First message received from NSNAS <messageType> is not connection initiation message Error This message is generated when the initial message is not recieved by the ERS8300. Check for possible mismatch of the ERS8300 and NSNAS versions. First message received from NSNAS <msg type> is not connection initiation message. Fault When you initiate an SSCP connection, the first message tyoe the system receives from NSNAS is a connection initiation message type. This fault message indicates that the first message type the system received is not the connection initiation message type. The system discards the received message type. No action required. FloodLSA: invalid - circuit null FATAL This message is generated when the interface for flooding the LSA is NULL.
F Messages
67
Action
Contact customer service with the following information available for further analysis:

for Entry <id> Deleting the mirroring record WARNING This message is generated when the system could not add a mirroring hardware table entry because of an incorrect ID, or the lack of an OS resource. Verify the correct command parameters in the documentation and try again. Forward-next-hop is available but bind FAIL with status: <value> ERROR This message indicates that ACE with redirect mode and reachable next-hop is not able to forward to the next-hop because the filter and next-hop cannot be bound together in hardware. Check the ARP and hardware next-hop tables. Forward-next-hop Update FAIL with status: <value> ERROR This message indicates ACE is in redirect mode and the specified next-hop is available/unavailable, but the filter cannot be updated in hardware. Check the ARP and hardware next-hop tables. free space <value> bytes is less than minimum <value> bytes INFO This message indicates that the free space in PCMCIA is less than the configured value for SMP. Thus, logging to PCMCIA has stopped. Free up some space in PCMCIA by moving or deleting files from PCMCIA. free space <value> bytes is less than minimum <value> bytes. Logging to PCMCIA stopped INFO This message indicates that the free space in PCMCIA is less than the configured value for SNP. N/A
Freeup MLT and re-insert card INFO This message provides a possible solution for "PreConfigTask: Slot <value> NO pre-configured." N/A
G Messages
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action gcntDeleteEgressCntrSet: Failed, status = <value> ERROR This message indicates a driver programming error. Specifically, an attempt to delete an egress counter set failed. Contact the customer support team if the problem persists. gcntGetEgressCntrs: Failed, status = <value> ERROR This message indicates a driver programming error. Specifically, an attempt to get egress counters failed. Contact the customer support team if the problem persists. gcntSetEgressCntrMode: Failed, status = <value> ERROR This message indicates a driver programming error. Specifically, an attempt to create an egress counter set failed. Contact the customer support team if the problem persists. gcosGetTc2UserPrio: Failed, status = <value> ERROR This message indicates a driver programming error. Specifically, an attempt to obtain a class-to-802.1p-map failed. Contact the customer support team if the problem persists. gcosGetUserPrio2Dp: Failed, status = <value> ERROR This message indicates a driver programming error. Specifically, an attempt to obtain an 802.1p-to-drop-precedence-map failed. Contact the customer support team if the problem persists.
G Messages
69
gcosGetUserPrio2Tc: Failed, status = <value> ERROR This message indicates a driver programming error. Specifically, an attempt to obtain an 802.1p-to-class-map failed. Contact the customer support team if the problem persists. gcosSetMacEntryTcOverrideEnable: Failed, status = <value> ERROR This message indicates a driver programming error. Specifically, an attempt to change the mac qos-level override option failed. Contact the customer support team if the problem persists. gcosSetPortDefaultTc: Failed, status = <value> ERROR This message indicates a driver programming error. Specifically, an attempt to port the default qos-level failed. Contact the customer support team if the problem persists. gcosSetTc2UserPrio: Failed, status = <value> ERROR This message indicates a driver programming error. Specifically, an attempt to set a class-to-802.1p-map failed. Contact the customer support team if the problem persists. gcosSetUserPrio2Dp: Failed, status = <value> ERROR This message indicates a driver programming error. Specifically, an attempt to set an 802.1p-to-drop-precedence-map failed. Contact the customer support team if the problem persists. gcosSetUserPrio2Tc: Failed, status = <value> ERROR This message indicates a driver programming error. Specifically, an attempt to set an 802.1p-to-class-map failed. Contact the customer support team if the problem persists. gen_valpair FATAL out of memory
ERROR This message indicates that the system is out of memory. If the problem persists, contact customer support. gen_valpairs<string> Unknown Type ERROR This message indicates that a RADIUS attribute unknown to the switch is being looked-up. Verify that the sent and received RADIUS packet contains known attributes. get_DevIdStart_from_Slot: Wrong Arg Slot <value> WARNING This message indicates that a wrong slot number has been passed to the function. N/A get_PPPort_For_FrontPort: WRONG Arg cardType <value>, frontPort <value> FATAL This message indicates that the port translation failed. N/A get_PPPort_For_FrontPort: WRONG CardType cardType <value>, frontPort <value> FATAL This message indicates that the port translation failed. N/A GetDropPrecValueFromTapi: unexpected value ERROR This message identifies an application programming error. Specifically, the conformance level is not in range. Contact the customer support team if the problem persists. gprtPortOverrideTcEnable: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to set the change port 802.1p override option failed.
G Messages
71
Contact the customer support team if the problem persists. Gratuitous Arp is not sent out for IP RSMLT node for IfIndex <Interface ID> Error This message indicates that RSMLT failed to transmit a gratuitous ARP for duplicate address detection. You can continue to operate the chassis, but note the scenario that results in the occurrence of this error message. Record the error message and configuration, and reboot the chassis. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. gtcmBindTrafficCondToAction: Failed, status = <value> ERROR This message specifies a driver programming error. Specifically, an attempt to bind a policy to a filter failed. Contact the customer support team if the problem persists. gtcmCntEn: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to enable/disable statistics on a policy or filter failed. Contact the customer support team if the problem persists. gtcmCreateTcEntry: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to create a policy entry in hardware failed. Contact the customer support team if the problem persists. gtcmDeleteTcEntry: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to delete a policy entry in hardware failed. Contact the customer support team if the problem persists. gtcmGetTrafficMeterCounters: Failed, status = <value> ERROR
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity
Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
This message identifies a driver programming error. Specifically, an attempt to obtain policing stats failed. Contact the customer support team if the problem persists. gtcmPolicingEn: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to enable/disable policing globally failed. Contact the customer support team if the problem persists. gtcmSetTcDefaultDscp: Failed, status = <value> ERROR This message identifies a driver programming error.Specifically, an attempt to set the default DSCP failed. Contact the customer support team if the problem persists. gtcmSetTcEntryConfCounters: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to obtain conformance counters failed. Contact the customer support team if the problem persists. gtcmSetTcEntryFlowAggrCounters FAIL TcId <value> ERROR This message indicates that clear statistics/counters failed for the filter. Try to enable/disable statistics on the filter. gtcmSetTcLengthType: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to set the length type for stats purpose failed. Contact the customer support team if the problem persists. gtN8300TapiCleanRemDevsmcGroup failed ERROR This message indicates that a cleanup of multicast information during a hot removal failed. N/A
G Messages
73
gtN8300TapiCleanRemDevsmirror failed ERROR This message indicates that a cleanup of mirroring info during a hot removal failed. N/A gtN8300TapiCleanRemDevsTrunk failed ERROR This message indicates that a cleanup of trunk info during a hot removal failed. N/A gtN8300TapiCleanRemDevsVlan failed ERROR This message indicates that a cleanup of VLANs information during a hot removal failed. N/A gtTxPort4TcGetDescNumber: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to obtain the Tx queue buffer size failed. Contact the customer support team if the problem persists. gtTxPort4TcMaxDescNumber: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to obtain the Tx queue buffer size failed. Contact the customer support team if the problem persists. gtTxPortBindPortToDropProfileSet: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to bind a drop profile to a port failed. Contact the customer support team if the problem persists. gtTxPortConfigTrafficClassDropProfileSet: Failed, status = <value>
ERROR This message identifies a driver programming error. Specifically, an attempt to set a drop profile failed. Contact the customer support team if the problem persists.
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity
gtTxPortDropMode: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to set a port drop mode failed. Contact the customer support team if the problem persists. gtTxPortFlushQueues: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to flush the Tx queue failed. Contact the customer support team if the problem persists. gtTxPortGetDescNumber: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to obtain the port buffer size failed. Contact the customer support team if the problem persists. gtTxPortMaxDescNumber: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to set the port buffer size failed. Contact the customer support team if the problem persists. gtTxPortQSetArbGroup: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to set the Tx queue scheduler group failed. Contact the customer support team if the problem persists. gtTxPortQSetShaperProfile: Failed, status = <value> ERROR
H Messages
75
Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
This message identifies a driver programming error. Specifically, an attempt to set the Tx queue shaper profile failed. Contact the customer support team if the problem persists. gtTxPortQSetWrrProfile: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to set the WRR profile failed. Contact the customer support team if the problem persists. gtTxPortQShaperEnable: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to enable/disable the Tx queue shaper failed. Contact the customer support team if the problem persists. gtTxPortQTxEnable: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to enable/disable the Tx queue failed. Contact the customer support team if the problem persists. gtTxPortSetShaperProfile: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to set the port shaper profile failed. Contact the customer support team if the problem persists. gtTxPortShaperEnable: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to enable/disable the port shaper failed. Contact the customer support team if the problem persists.
H Messages
Message Severity HAL_Init: NPAL_GtNhopTblInit failed ERROR
Description Action
This message identifies a failure in the software next hop table initialization process. Reboot the switch and contact the customer support team if the problem persists. Head pointer passed as NULL for adding an entry to SNMP Sessions LinkedList ERROR This message identifies a software error. Contact customer support for assistance. Head pointer passed as NULL for removing an entry from SNMP Sessions LinkedList ERROR This message identifies a software error. Contact customer support for assistance. HoldupForwardingForPeer: Cant add ARP and MAC for peer, IP RSMLT down on vlan <VLAN ID> Error This message is generated when RSMLT fails to include an ARP entry and MAC address during the RSMLT peer forwarding holdup time. This error may impact Rsmlt backup functionality. Record the error message and configuration, and reboot the chassis. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. HoldupForwardingForPeer: vlan <VLAN ID> is not existed, IP RSMLT down Error This message indicates that a valid Vlan is not found during the RSMLT peer forwarding holdup time. Record the error message and configuration, and reboot the chassis. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. Hot Insert: boardAfterInitConfig failed for slot <value> ERROR
Action
Message Severity
H Messages
77
Description
This message occurs when the system is unable to obtain the required logical initialization parameters. These parameters contain important system initialization information. Reboot the switch and contact the customer support team if the problem persists. Hot Insert: hotSyncInsertDev fail ERROR This message indicates that a hot insertion failed for a newly- inserted card in the system. Reboot the switch and contact the customer support team if the problem persists. Hot Insert: packetDevListTxDemoRevA failed for slot <value> ERROR This message indicates that the configuration of a particular device port failed. Reboot the switch and contact the customer support team if the problem persists. Hot Insert: sysDevListEnableTraffic failed for slot <value> ERROR This message identifies a problem in device port initialization since this function is responsible for preparing a device port to receive traffic. Reboot the switch and contact the customer support team if the problem persists. Hot Insert: trRegisterFunc failed for slot <value> ERROR This message indicates that the registration of functions required for hot insertion failed. Reboot the switch and contact the customer support team if the problem persists. Hot Insert: trUpdateAppDemoPpConfigList failed for slot <value> ERROR This message indicates that the updating of the ppDemo Configuration list failed. Reboot the switch and contact the customer support team if the problem persists.
Action
Hot insertion failed for device <value> ERROR This message indicates that a hot insertion failed for a newly- inserted card in the system for the given device. Reboot the switch and contact the customer support team if the problem persists. Hot removal failed for device <value> ERROR This message indicates that a hot removal of a given device for a particular slot failed. N/A Hot removal of slot <value> xbar failed ERROR This message indicates that crossbar removal/cleanup was unsuccessful. N/A Hot Remove: device <value> does not exist ERROR This message specifies that during hot removal, a given device on the hot removed slot does not exist. N/A Hot Remove: hotSyncRemoveDev failed for slot <value> ERROR This message indicates that a hot removal of a given slot failed. N/A Hot Remove: trDowndateAppDemoPpConfigList failed for slot <value> ERROR This message indicates that a hot removal of a given slot failed. N/A
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
I Messages
79
I Messages
Message Severity Description Action Message Severity Description iDLStart: rcIpGetIf returns NULL ERROR This message is generated if no IP record exists. The IfIndex may be out of range, or there is no IP record for the IfIndex. Contact customer support for further troubleshooting. If Index Count is <value> cannot be decremented for Acg Id <value> ERROR This message indicates a filter modules table management keeps a dependency between the ACG and Ifindex in order to allow/prevent ACG modification or deletion. Check the dump using aclDumpAcgTbl() and aclDumpIfIndexTbl(). Delete filter configuration from all ports, delete ACGs, and then recreate them. IfRec(ipaddr=<ipaddr>, index=<index>) - Exceeded NVRAM limit of <value> WARNING This message is generated when the available NVRAM space for storing records is exhausted. No action needs to be taken.
Action
igmp_event_handler : corrupt msg Error A corrupt message is received by the igmp event handler. N/A igmp_event_handler(): igmpGetInterface() FAIL for IfIdx <value> Warning An interface index cannot be obtained when an igmp event is handled. Contact technical support. igmpAddMltMap: could not allocate mem for p_entry ERROR memory allocation failure N/A
Message Severity
igmpCacheTblEntryAdd:Cant malloc. Error
Description Action Message Severity Description
A failure to allocate memory for igmp cache table has occurred. Reduce the running configuration file size or reboot the switch. igmpCacheUnsolData: unable to allocate IGMP_SRCGRP ERROR This message is generated if the source/group pair allocation is unsuccessful. This is because the memory allocation for the source/group pair failed due to low DRAM memory. Contact customer support for further troubleshooting. igmpCreateSrcRec: unable to allocate IGMP_SRC ERROR This message is generated when trying to allocate memory for the IGMP source group and the system finds that it is unable to do so due to low memory. Increase the DRAM size.
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description
igmpCreateTimer Cant allocate memory Error A failure to allocate memory for igmp timer has occurred. Reduce the running configuration file size or reboot the switch. igmpCreateTimer: Creating FINITE timer Error An igmp timer is not created because the timer type is FINITE. Contact technical support. IgmpGrpCreate : Error in igmpAlloc! ERROR This message is generated when you try to create a new IGMP group, but there is not enough memory to save it. This error can be caused by a lack of memory. Close all CLI sessions to free up memory. igmpGrpCreate: Error in imgpSetUpARRec ERROR This message is generated when trying to add a port to an MGID entry and add an AR record for any source/group pair. It can appear because the MGID cannot be created, or you are trying to add an invalid port to a group. Check validity of the port and contact customer support for further troubleshooting.
Action
I Messages
81
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
igmpL2Send: cannot send frame ERROR This message is generated when an attempt to send out control packets fails. If message does not stop, then cppTxFrame may have failed. igmpPresteraSessionIsActive: ipmGetMatrixCounter Could not get the Counter value WARNING This message identifies a failure to obtain a matrix counter for the multicast sender activity check. N/A igmpPresteraSessionIsActive: ipmSetMatrixCounter Could not set the counter ERROR This message identifies a failure to set the matrix counter for the multicast sender activity check. N/A igmpRxPkt: cannot send frame ERROR This mesage indicates that the control packet could not be sent out. N/A
igmpRxPkt(), igmpGetInterface IfIdx = <value> Warning A null interface index is generated when igmp receive packets are handled. Contact technical support. igmpSrcLstDelete: arDeletePortFromGroup failed FATAL This message is generated while trying to delete a port from a source/group pair. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology.
Message Severity
igmpInit: unable to allocate tSGBlock Error
Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
This message is generated when allocating buffers to store SG entries fails, when initiating an IGMP module. N/A igmpGrpCreate: Error in igmpAlloc Error This message is generated when allocating buffers to store group information fails, when creating an IGMP group. N/A igmpL2Send: cannot send frame Error This message is generated when layer 2 IGMP frames cannot be transmitted. N/A igmpGroupOifUpdate: failed to allocate memory Error This message is generated when allocating buffers to store outgoing interface information fails, when updating this information. N/A igmp_access_head alloc failed Error This message is generated when allocating buffers to store prefix list information fails, when initiating an IGMP access control module. N/A
igmpTurnAroundFrame: cannot send frame ERROR This message indicates that the control packet could not be sent out. N/A igmpUpdUnsolRec: Unsol rec for port <value> should have been deleted by now ERROR This message is generated if an unsolicited record is found. This is an internal error. Contact customer support for further troubleshooting.
I Messages
83
Message Severity Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
image download done INFO N/A image programming done INFO This message specifies that image programming was completed during the image upgrading process. N/A image programming started, .... INFO This message specifies that image programming to the PoE DIMM controller module has started. N/A Impossible Neighbor State FATAL This message is generated when an invalid neighbor state is encountered. Contact customer service with the following information available for further analysis:

Impossible returncode from ospfProcLsa() FATAL This message is generated when an invalid return code from an LSA procedure is encountered. Contact customer service with the following information available for further analysis:
indexAdd() - failed adding ERROR This message indicates that an error occurred when adding a policy entry in which the entry already exists. N/A indexAdd() - failed adding Error Adding a Pim table failed. N/A init_pim_mrt: malloc failed Error A malloc failure occurred. Reduce the running configuration file size or reboot the switch. init_pim : malloc failed Error A malloc failure has occurred. Reduce the running configuration file size or reboot the switch.
Insertion of card failed for Slot <value> ! WARNING This message indicates the card insertion process was unsuccessful. Re-insert or replace card. invalid action of changing SMLT or SLT ID in RSMLT Error This message indicates that the system received an invalid parameter when RSMLT attempted to update the SMLT and SLT IDs in a Vlan. You can continue to operate the chassis, but note the scenario that results in the occurrence of this error message. Record the error message and configuration, and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. Invalid Card Type WARNING This message specifies that an invalid card type was detected.
I Messages
85
N/A Invalid Card Type fpr phyInit Slot <value> WARNING This message indicates that an invalid card type has been detected. N/A invalid - circuit is null FATAL This message is generated when an invalid interface circuit (NULL) is encountered while trying to acknowledge LSA. Contact customer service with the following information available for further analysis:

Invalid configuration: network appears in two areas INFO This message is generated when the same route appears for different areas. Configure the network properly so there is no repetition. invalid interface index ERROR This message is generated when a VLAN ID is out of range. For example, if you enable or disable IGMP for the circuit using an invalid VLAN, then this error message occurs. Provide a valid VLAN ID. Check the instructions in the VLAN configuration command. If this error persists, then contact customer support for further information. invalid lsai ptr FATAL This message is generated when the system encounters an invalid pointer to the LSA identifier.
Action
Action

invalid page choice Error This message indicates the system receives an invalid parameter when you display RSMLT information. Note the scenario that results in the occurrence of this error message. Record the error message and configuration, and contact the Nortel Technical Solutions Center for assistance. Invalid Port <value> ERROR This message indicates that port translation failed. N/A invalid power supply configuration detected, PoE disabled and all PoE power removed ERROR This message indicates that mixed types of power supplies were installed in the chassis. Remove or replace power supplies to ensure that there are no mixed types of power supplies installed. invalid profile <value> ERROR This message identifies an invalid task for profiling. Reboot the switch and contact the customer support team if the problem persists. Invalid VR IP addresses %d.%d.%d.%d received for Vrid %d on IfIndex %d ERROR This message indicates that there is a mismatch between a VR IP received by the switch and the VR IP configured for the VRRP instance. Configure the VRRP instance to correct the VR IP mismatch.
I Messages
87
Invalid VR IP addresses ___ received for Vrid ___ on IfIndex ___ Warning This message is generated if the router receives an VRRP advertisement having an incorrect VRRP IP address for a VRID. Confirm that all the routers with the same VRID have the same VR IP address. IP Interface removed, Delete Rsmlt Node Failed on IfIndex <Interface ID> Error This message is generated when deleting an RSMLT Node fails, which can cause a memory leak. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. ip2GarbageList: Could not allocate mem for garbage!!! ERROR This message indicates memory allocation failed for garbage collection list. Close all CLI sessions to free up memory. Contact customer support if the problem persists. IPC timed out on <value> connections ERROR This message indicates that the connection between the CP and I/O cards timed out. Hot-remove and hot-insert the I/O card. IpCircEvent : Unable to find IpRec for IfIndex FATAL This message is generated when the circuit I/O channel is in an alive state and system tries to read the memory location to an existing IP record. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology.
ipCliSettPimdebugBootstrap: value is Invalid Error An invalid Bootstrap parameter is received.
Contact technical support. ipCliSettPimdebugHello: value is Invalid Error An invalid hello is received. Contact technical support. ipCliSetPimGlobMode: pimMode Invalid <value> Error Attempting to globally set an unsupported PIM mode. N/A ipCliSettPimdebugGraft: value is Invalid Error An invalid Graft parameter is received.
ipCliSettPimdebugJoinPrune: value is Invalid Error An invalid prune message is received. Contact technical support. IpDecrMaskCntr : negative # of intf with mask ERROR This message is generated when the route mask counter is less than zero for an IP circuit that has to be deleted. Contact customer support for further troubleshooting. IpDoSpecial: ipNetToMediaPhysAddress_index arpadd failed! ERROR This message is generated when you try to add a static ARP entry from JDM and the action fails. Contact customer support for further troubleshooting. IpDoSpecial: ipNetToMediaPhysAddress_index Port %d not a member of vlan ERROR This message is generated when the supplied Ifindex (Interface index which is unique for each port or VLAN) is not associated with any VLAN. Contact customer support for further troubleshooting.
I Messages
89
IpDoSpecial: ipNetToMediaPhysAddress_index rcIpLoadArpRecfailed ERROR This message is generated if an attempt to load the ARP entry into the static ARP table fails. The ARP table may be corrupted or the system is unable to allocate memory. ipForward: pP2IpBd == NULL ERROR This message is generated when the frame desc buffer passed is NULL. Contact customer support for further troubleshooting. ipLocAddrFind: Cant find IfIndex for cid FATAL This message is generated when the system tries to find the local IP address and no IP record exists for the given interface index. The system software IP table could be corrupted. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology. ipmcRx: Cant find circuit for cid <cid>! FATAL This message indicates that you cannot get the IP circuit. N/A
Action
IpmMltMcastDistributionGrpSet: Set Mcast Mlt Global Error This message is generated when attempts to globally set Mlt multicast distribution fail. N/A IpmMltMcastDistributionGrpSet: Set Mcast Software Forwarding Error This message is generated when attempts to set Ip multicast forwarding fail. N/A
ipNetToMediaPhysAddress_index NULL snmp_arp_circ ERROR This message is generated when the physical address you have supplied is not associated with any circuit. Contact customer support for further troubleshooting. ipNetToMediaPhysAddress_index vlanGetVlanIdFromIfIndex failed for IfIndex ERROR This message is generated if there is no VLAN associated with the interface index. Contact customer support for further troubleshooting. ipPktOut: ipCircFromId failed for cid ERROR This message is generated when the circuit pointer for a specific circuit ID is NULL. Contact customer support for further troubleshooting. ipPktOut: Unable to find IpRec for IfIndex ERROR This message is generated when the pointer to the framebuffer descriptor of the last IP packet received from the CPP module is null. Contact customer support for further troubleshooting. ipReasmInit: Cant allocate ipNDBTbl! ERROR This message is generated when system is not able to allocate memory for the Net data block table. Close all CLI sessions to free up memory. Contact customer support if problem persists. ipReasmInit: Cant allocate ipReasmTbl! ERROR This message is generated when the system is not able to allocate memory for the IP reassembly table. Close all CLI sessions to free up memory. Contact customer support if problem persists.
L Messages
91
IpRec does not exist for IfIndex <value> ERROR This message is generated when the IP record does not exist for the corresponding IP address when trying to update the OSPF. Contact customer service with the following information available for further analysis:

ipv4EnableVr <vrid> failed Fault When you enable MVR, the system enables VR 0. This message indicates that the system failed to enable VR 0 and MVR will not function. Disable and enable MVR. If the error does not clear, restart the switch.
K Messages
Message Severity Description Action Keepalive expired for <value> connection with Id <value> to Slot <value> ERROR This message indicates the connection between the CP and I/O card timed out. Hot remove and hot insert the I/O card.
L Messages
Message Severity Description Action LACP ERROR: HA-CPU: Unable to spawn HA LACP PortScan task Error This message is generated when the system is unable to initiate an HA LACP port scan task. High Availability (HA), is not supported in Ethernet Routing Switch 8300 Releases 4.1 and earlier. Ignore this message. LACP ERROR: rcLacpGlobalGrpSet: Set LACP Glob Error This message indicates that an error has occurred in the LACP global configuration. Reboot the switch.
LACP ERROR: lacpTxLacpdu: Cant get BD! Error This message is generated when the volume of protocol packets the system transmits in a short duration exceeds the maximum the allocated system buffer size can process. Reduce the number of system protocols running simultaneously. LACP ERROR: lacpTxLacpdu: Cant send frame! Error This message indicates that the system cannot transmit an LACP PDU. An LACP configured port has failed or there is insufficient system memory available. Check the status of LACP configured ports or confirm the availability of system memory. LACP ERROR: send_markerpdu: Cant get BD! Error This message is generated when the volume of protocol packets the system transmits in a short duration exceeds the maximum the allocated system buffer size can process. Reduce the number of system protocols running simultaneously. LACP ERROR: send_markerpdu: Cant send frame! Error This message indicates that the system cannot transmit a marker PDU. An LACP configured port has failed or there is insufficient system memory available. Check the status of LACP configured ports or confirm the availability of system memory. LACP ERROR: Cant add MAC range filter for EAP and LACP! Error This message indicates that you have exceeded the system limit for EAP or LACP MAC range filters. LACP and VLACP cannot function. No action required. The distribution of MAC range filters is software controlled. LACP ERROR: Cant del MAC range filter for EAP! Error
Action
Action
L Messages
93
Description Action
This message indicates that the system cannot delete an EAP MAC range filter. Enable and disable VLACP. If this fails to clear the error, there can be a MAC range filter hardware failure. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. LACP ERROR: Cant add MAC range filter for EAP ! Error This message indicates that the system cannot add an EAP MAC range filter. Enable and disable VLACP. If this fails to clear the error, there can be a MAC range filter hardware failure. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. LACP ERROR: Cant delete MAC range filter for EAP and LACP Error This message indicates that the system cannot delete an EAP and LACP MAC range filters. Enable and disable VLACP. If this fails to clear the error, there can be a MAC range filter hardware failure. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. LACP ERROR: lacpInitAggr: Cant allocate memory for aggregator! Fatal This message indicates that the system cannot allocate sufficient memory for the internal aggregator structure. Use the show sys info command to view the amount of unused memory. Adjust system function to decrease memory usage or add memory to your system. LACP ERROR: lacpInitPort: Cant allocate memory for port! Fatal This message indicates that the system cannot allocate sufficient memory for internal LACP port structure. Use the show sys info command to view the amount of unused memory. Adjust system function to decrease memory usage or add memory to your system. lbStart: NPAL_AddMacAddress failed with <value>
Message
Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
WARNING This message indicates the NPAL_AddMacAddress failed when doing a loopback test. Contact the customer support team if the problem persists. lbStart: NPAL_DeleteMacAddress failed WARNING This message indicates the NPAL_DeleteMacAddress failed when doing a loopback test. Contact the customer support team if the problem persists. lbStart: NPAL_RestoreVlanAfterLoopBack failed WARNING This message indicates the NPAL_RestoreVlanAfterLoopBack failed when doing loopback test. Contact the customer support team if the problem persists. Link Down <value>.Port is a trunk port WARNING This message specifies the link-down status for a trunk port. N/A Link Down <value>.Port is an access port ERROR This message specifies the link-down status for a VLAN access port. N/A LinkUp: NPAL_PortMacFltEnable FAILED ERROR This message indicates that a port MAC filter enable failed. Reboot the switch and contact the customer support team if the problem persists. listen failed for SSCP socket Error This message is generated when listen for SSCP socket has failed. Check the network connection.
L Messages
95
listen failed for SSCP socket Fault This message indicates that the system cannot perform the listen operation on the SSCP socket. Verify the operation of the socket, disable and enable NSNA globally, or confirm NSANS configuration. lldpInitTx: lldp_alloc failed for buf ERROR This message is generated when a memory related problem occurrs while initializing a transmission on LLDP. Reboot required. lldpduSend: Cant send frame! ERROR This message is generated when the CP card has failed to send an LLDP packet. Ignore message. LLDP:Unable to set Dot3 Power-via-MDI TLV on a non-power port x/y ERROR This message is generated when the Power-via-MDI TLV cannot be set on a non-POE port. No action required. LLDP:Unable to set extendedPSE TLV on a non-power port x/y ERROR This message is generated when the ExtendedPSE TLV cannot be set on a non-POE port. No action required. LLDP: Unable to set Port x/y LLDP Status Info This message is generated when the LLDP status of the port x/y is not set to default during initialzation. No action required. LogFileSize <value> bytes is exceeding allowed log file size
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message
INFO This message specifies that the log file size exceeds the allowed file size. N/A LogFileSize <value> bytes is exceeding Maximum log file size INFO This message specifies that the log file size exceeds the configured maximum log file size. N/A Logging to PCMCIA stopped INFO This message indicates that SMP logging to the PCMCIA has stopped. N/A logSendFatalLog: fail to malloc FATAL This message specifies a memory allocation failure. Reboot the switch and contact the customer support team if the problem persists. logSendFatalLog: fail to read <msg> ERROR This message indicates a failure to read a file. N/A lsai->i_ref_count is zero FATAL This message is generated if the reference count of a retransmit LSA is 0. Contact customer service with the following information available for further analysis:
M Messages
97
M Messages
Message Severity Description Action Mac %s movement from port -- to -WARNING This message is generated when a non-EAP MAC moves from an EAP enabled port to another port. Verify that the movement happened only when the MAC is physically moved from an EAP port to another port. Malloc failed ERROR This message indicates that the system has run out of memory. Reboot the switch and contact the customer support team if the problem persists. malloc failed for port vlan list <Slot/Port> Error This message is generated when an attempt to malloc the vlan list for a specified port has failed. Check the system memory. malloc failed switch->SAC message. msg Type <typeNum>, msg Len <size> Error This message is generated when malloc memory for the message has failed. Check the system memory malloc failed switch->SAC message. msg Type <>, msg Len <> Fault This message indicates that there is insufficient system memory for the switch to transmit an NSNAS message. Use the show sys perf command to view system memory utilization. Disable and enable NSNA globally. malloc failed for port vlan list <x/y> Fault This message indicates that the system failed to apply memory to record the VLAN type when you configured an NSNA port. Use the show sys perf command to view system memory utilization. If there is not enough available memory, reboot the switch.
malloc failed in ospfLinkToBERefreshed ERROR This message is generated when after completion of SPF, the system fails attempts to refresh the ospf link abd, due to the inability of the memory allocation. No action required. malloc of message parameter failed ERROR This message indicates that memory allocation has failed. Reboot the switch and contact the customer support team if the problem persists. Matching TCP, UDP and other L4 fields is not configured, Setting ipfragments option to any for Acl-Id <value> Ace-id <value> WARNING This message indicates that the filter is restored to match packets, irrespective of the fragmentation condition. This is true if the rule is not required to match Layer 4 fields. Specify the desired fragments match condition in the rule after clearing Layer 4 match fields in the rule. Matching TCP, UDP and other L4 fields is not supported for fragmented packets, Setting ipfragments option to non-fragments for Acl-Id <value> Ace-id <value> WARNING This message indicates that matching Layer4 fields is not possible with stateless filtering. Be aware of this limitation. Specify non-fragments in the rule before configuring Layer 4 match fields to avoid this message. Maximum number of allowed TACACS+ simultaneous logins reached, please try later INFO More then 8 users are trying to login simultaneously to the switch using TACACS+ authentication. N/A Maximum number of SNMP sessions are already running Access Denied
Action
Message
Message Severity Description Action Message
M Messages
99
Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
ERROR This message indicates that the number of SNMP connections has exceeded the maximum limit. Terminate unwanted SNMP connections. mcosGetCosByDscpDp: Failed, status = <value> ERROR This message identifies a driver programming error. Specifically, an attempt to get the dscp-to-cos-policed-map failed. Contact the customer support team if the problem persists. mcosSetCosByDscpDp:Marking Table Failed, status = <value> ERROR This message identifies a driver programming error. In this case, an attempt to set the dscp-to-cos-policed-map failed. Contact the customer support team if the problem persists. mcosSetCosByDscpDp:remarking Table Failed, status = <value> ERROR This message identifies a driver programming error. In this case, an attempt to set the dscp-to-cos-policed-map failed. Contact the customer support team if the problem persists. mcosSetCosByTcDp: Failed, status = <value> ERROR This message identifies a driver programming error. In this case, an attempt to set the class-to-802.1p-policed-map failed. Contact the customer support team if the problem persists.
Memory allocation Error for dmrtentry S <value> G <value> Warning A failure to allocate memory for snoop met entry has occurred. Reduce the running configuration file size or reboot the switch. the switch. Memory allocation Error for grpentry <value> Warning
100
SMP error messages
Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message
A memory allocation Error for grp has occurred. Reduce the running configuration file size or reboot the switch. Memory allocation Error for srcentry <value> Warning A memory allocation Error for src has occurred. Reduce the running configuration file size or reboot the switch. Message New Mac -- Old Mac -- - Port -- being shut down WARNING This message is generated when a new Mac Address is seen on an 8021x authorized port. The port is shut down. Initialize the port again. Message not sent for deleting msgQ for snmp accounting ERROR This message indicates the Passport 8300 is unable to free software resources. Contact customer support for assistance. Message not sent for sending interim accounting message for snmp accounting ERROR This specifies that a RADIUS accounting interim message was not sent due to a software error. If problem persists, contact customer support. Message not sent for sending on accounting message for snmp accounting ERROR This specifies that a RADIUS accounting ON message was not sent due to a software error. If the problem persists, contact customer support. Message not sent for sending stop accounting message for snmp accounting ERROR This specifies that a RADIUS accounting STOP message was not sent due to a software error. If the problem persists, contact customer support. Mirroring Disable FAILED for Entry <id>
M Messages
101
Severity Description
WARNING When a mirroring port is detected as not present, the Passport 8300 cannot delete a mirroring hardware table entry because of an incorrect ID or a lack of OS resources. Verify the correct command parameters in the documentation and try again. Mirroring Enable FAILED for Entry <id> WARNING When a mirroring port is detected as present, the Passport 8300 cannot enable a mirroring hardware table entry because of an incorrect ID or a lack of OS resources. Verify the correct command parameters in the documentation and try again. mltGo: Mlt Table Initialization failed ERROR This message indicates that the initialization of trunks in the hardware failed. Reboot the switch and contact the customer support team if the problem persists. mltHasNonDisabledActivePort: cant lock mutex! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. mltDesgPortDisabled: cant lock mutex! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. mltLinkDown:Del port from h/w failed for MLT Id <value> Mlt Port <value> ERROR
Message Severity
102
SMP error messages
Description Action
This message indicates that on link-down of an MLT port, the hardware clean-up failed. The switch may be usable, but further MLT operations can fail. It is recommended that you reboot the switch and contact the customer support team if the problem persists. mltLinkUp:Add port to h/w failed for MLT Id <value> Mlt Port <value> ERROR This message indicates that on link-up of an MLT port, the hardware update failed. The switch may be usable, but further MLT operations can fail. Nortel Networks recommends that you reboot the switch and contact the customer support team if the problem persists. Module id is wrong FATAL This message specifies that the wrong module is used. Reboot the switch and contact the customer support team if the problem persists. msgSendDbgMsg: failed to get CP slot number FATAL This message identifies a failure to get the CP slot number when sending a message from the coprocessor. Reboot the switch and contact the customer support team if the problem persists. MSTP INFO New CIST Root (self) Info This message indicates that the switch is configured as the new CIST root switch. No action required. MSTP INFO New CIST Root (<bridge-id of new CIST Root>) Info This message indicates that the switch you are accessing recognizes the network switch with the specified bridge ID as the new CIST root switch. No action required.
M Messages
103
MSTP INFO MSTP Region change (New Region <Selector:Name:RevLevel :ConfigDigest>) Info This message indicates a change in the switch MST configuration identification, which occurs when you create a new VLAN or MSTI, or there is a change in the region name, selector or revision level. This message appears at bootup and when there is a region change. No action required. MSTP INFO New CIST Regional Root (self) Info This message indicates that the switch you are accessing is the new CIST regional root switch for the region to which the switch belongs. No action required. MSTP INFO New CIST Regional Root (<bridge-id of new Regional Root>) Info This message indicates that the switch you are accessing recognizes the network switch with the specified bridge ID as the new CIST regional root switch for the region to which the switches belong. No action required. MSTP INFO New MSTI Root (self) for MSTI <msti-instance> Info This message indicates that the switch you are accessing is the new MSTI root switch for the MSTI instance of the region to which the switch belongs. No action required. MSTP INFO New MSTI Root (<bridge-id of new CIST Root>) for MSTI <msti-instance> Info This message indicates that the switch you are accessing recognizes the network switch with the specified bridge ID as the new MSTI root switch for the MSTI instance of the region to which the switch belongs. No action required. MSTP INFO MSTP Port Role Change (CIST, <port or MLT>, <new Port Role>) Info
104
SMP error messages
Description Action Message Severity Description Action Message Severity Description Action Message Severity Description
This message is generated when a CIST port role changes. No action required. MSTP INFO MSTP Port Role Change (MSTI <msti-instance>, <port or MLT>, <new Port Role>) Info This message is generated when a MSTI port role changes. No action required. MSTP INFO Port Protocol Migration (<port or MLT> <Mstp | StpCompatible>) Info This message is generated when port BPDUs change from STP to MSTP or from MSTP to STP. No action required. MSTP INFO OperEdge disabled on port <port or MLT> Info This message indicates that an MSTP port with edge-port administratively enabled receives a BPDU that changes the operational edge-port value to false (disabled). No action required. Must enable Multicast Distribution over MLT on peer INFO This message is generated when multicast distribution over MLT on a peer is not enabled, but it is required. Enable multicast distribution over MLT on peer. Must disable Multicast Distribution over MLT on peer INFO This message is generated when multicast distribution over MLT on a peer must be disabled. Disable multicast distribution over MLT on peer.
N Messages
Message Severity New connection from ip <IPAddr> port <remotePortNum> Info
N Messages
105
This message is generated when a new SSH connection from a specified IP/Port pair occurs. N/A New Filter <acgID> Attachment to port <PortNum> failed Error This message is generated when a new filter cannot be attached to a specified port. Confirm that the filter is valid and the NSNA service is disabled to attach the filter. New Mac -- Old Mac -- - Port -- being shut down WARNING This message indicates that a new Mac Address is seen on an 802.1X authorized port and the port is shut down. Re-initialize the port. New vlan <VlanID> is non SSA Error This message is generated when the vlan is not an NSNA vlan. Configure the vlan as an NSNA vlan. New vlan <> is non SSA Fault This message indicates that the new VLAN ID the system received in the ConfigPortExt or ConfigPort message from NSNAS, does not belong to an NSNA VLAN. Review and confirm switch and NSNAS configuration. nncli_commonCliInit : nnclip is still NULL ERROR This message indicates that the Passport 8300 was unable to allocate memory for the NNCLIP. N/A nnclip init failed ERROR This message indicates the Passport 8300 was unable to initialize NNCLIP.
106
SMP error messages
Reboot the switch and contact customer support if the problem persists. nnRstDot1dScalarsGrpSet: cant lock mutex! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. nnMstBridgeTblSetBody: cant lock mutex! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. nnRstDot1dScalarsGrpSet: cant lock mutex! Error This message is generated when there is insufficient system memory or there is a conflict in data access. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. No card Type for Slot <value> WARNING or ERROR This message indicates that card type information is not available. Re-insert or replace the card.
no memory for p_querier Error A failure to allocate memory for igmp querier has occurred. Reduce the running configuration file size or reboot the switch.
N Messages
107
No PoE power supply detected, total PoE power= 0 watts ERROR This message indicates that an invalid PoE power supply was installed. Check to see if a legal PoE power supply was installed and if necessary, replace the power supply. No rarMacAddress record of VR with BackupMasterState up Error This message indicates that a virtual MAC address record is not available when a switch is configured as a VRRP backup master. This is a result of VRRP timer process checking. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. No resource for mac <value> vlan <value> status <value> WARNING This message indicates that record space is not available to add a new Mac Address. N/A Non Eap Intrusion (-- -- --) INFO This message is generated on encountering a new MAC when already max number of non-EAP clients are seen and max number of EAP sesisons already exists. No action necessary due to a new MAC learn event on a port. Non-Eap client with Mac -- on Port -- is not authnticated by Radius Server INFO This message is generated when the radius server rejects the non-EAP-clients authentication request. No action necessary. Non-Eap host with Mac -- on Port -- is authenticated INFO This message is generated when the radius server authenticates the non-EAP-client. No action necessary.
Action
108
SMP error messages
not enough resources to create new profile ERROR This message indicates that there are not enough tasks to be profiled. Reboot the switch and contact the customer support team if the problem persists. NPAL_AddArp: could not create local host entry <ip addr> for ifindex <value> WARNING This message indicates that an attempt to add the 32-bit host route failed in the hardware. You need to add the 32-bit host route in hardware for each ARP entry. Contact the customer support team if the problem persists. NPAL_AddArp: IP address of the ARP is NULL ERROR This message indicates that you cannot add an ARP entry where the IP address equals 0. Even if you are setting the default route to CPU or DROP, you can bind the default route to special hardware next-hops without specifying the ARP IP equals 0. N/A NPAL_AddArp: ipv4CreateIpInterface failed for <ip addr> status <value> WARNING This message indicates that an attempt to create the IP interface in hardware for the local ARP failed. Contact the customer support team if the problem persists. NPAL_AddArp: No more hardware space available in system for the arp ERROR Currently, the Passport 8300 supports 2994 dynamic, static, and discard ARP entries. If you attempt to add a number beyond this limit, this message displays to show that the hardware has no more space for ARP entries. Either refrain from adding more ARP entries or delete some ARP entries to make room for the new one. NPAL_AddIpRoute: Adding prefix failed entry <ip addr>/<value>, nhId <value> status <value> WARNING This message indicates that an attempt to add the route to the hardware failed.
Action
N Messages
109
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description
Contact the customer support team if the problem persists. NPAL_AddIpRouteToCreateBulkEntry: failed deleting UcPrefix <prefix> prefixLen <value> status <value> WARNING This message indicates that an attempt to delete a unicast prefix entry in hardware failed. Contact the customer support team if the problem persists. NPAL_AddIpRouteToDelBulkEntry: failed adding UcPrefix <prefix> prefixLen <value> status <value> WARNING Failed to add a unicast prefix entry in hardware. Contact the customer support team if the problem persists. NPAL_CheckNextHopDelList: failed deleting UcnextHop <nextId> status <value> WARNING Failed to delete a next hop entry in hardware. Contact the customer support team if the problem persists. NPAL_CreateCpuandDropNhIds: failed creating CPU NH, Status <value> ERROR This message indicates that an attempt to create the special next-hop in hardware pointing to the CPU failed. This next-hop will be used by default route and will never be deleted. Contact the customer support team if the problem persists. NPAL_CreateCpuandDropNhIds: failed creating DROP NH Status <value> ERROR This message indicates that an attempt to create the special next- hop in hardware pointing to DROP failed. This next hop will be used by default route and will never be deleted. Contact the customer support team if the problem persists. NPAL_CreateNhId: could not create next hop <ip addr>, Status <value> WARNING This message indicates that an attempt to create the next-hop entry in hardware failed.
110
SMP error messages
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity
Contact the customer support team if the problem persists. NPAL_CreateSingleInlif: failed enabling Uc routing lifIfIndex: <value>, status: <value> INFO You need to enable routing for each port on the Passport 8300. This message indicates a failure in hardware when enabling IP routing for that interface. Contact the customer support team if the problem persists. NPAL_DeleteArp: Delete UcNextHop failed entry <ip addr> nhId <value> status <value> WARNING This message indicates that an attempt to delete the next hop in hardware failed. Contact the customer support team if the problem persists. NPAL_DeleteArp: Failed deleting NextHop entry <ip addr> nhId <value> status <value> WARNING This message indicates that an attempt to create the two next-hop entries in hardware, with one pointing to CPU and the other pointing to drop, failed. Contact the customer support team if the problem persists. NPAL_DeleteArp: failed deleting UcPrefix <ip addr> status <value> WARNING This message indicates that an attempt to delete the 32-bit host route that is associated with the ARP entry in hardware failed. Contact the customer support team if the problem persists. NPAL_DeleteIpRoute: delete route entry<ip addr>/<value> next-hop <ip addr> status <value> failed WARNING This message indicates that an attempt to delete the route entry in hardware failed. Contact the customer support team if the problem persists. NPAL_EnableVrId: ipv4EnableVr failed ERROR
N Messages
111
Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
This message indicates that an attempt to enable virtual route in hardware when the system comes up failed. Reboot the switch and contact the customer support team if the problem persists. NPAL_EnableVrId: NPAL_CreateAllInlifs failed ERROR This message should never appear. N/A NPAL_EnableVrId: NPAL_SetDefaultIpRoute failed WARNING This message indicates that an attempt to set the default route to either CPU or DROP in the hardware failed. Contact the customer support team if the problem persists. NPAL_gbrgSetControlPktTc(%d) failed! Error This message is generated when the system fails to configure the control packet traffic class. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. NPAL_gbrgSetArpIgmpTrapTc (%d) failed! Error This message indicates that the system failed to configure the ARP or IGMP traffic classes. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. NPAL_gstpSetMode(%u, %u) failure code: %d! Error This message indicates that the system failed to configure the STP mode. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. NPAL_gstpSetMode(<value>, <value>) failure code: <value>!
Message
112
SMP error messages
ERROR This message indicates that the setting of multiple Spanning Tree mode failed. Reboot the switch and contact the customer support team if the problem persists. NPAL_ProcCreateIpBulkListL Adding bulk prefix failed status <value> WARNING Failed to add bulk unicast prefix entries in hardware. Contact the customer support team if the problem persists. NPAL_ProcDeIIpBulkList: Delbulk prefix failed status <value> WARNING Failed to delete bulk unicast prefix entries in hardware. Contact the customer support team if the problem persists. NPAL_ProcDelArpBulkList: del bulk next hop failed status <value> WARNING Failed to delete bulk next hop entries in hardware. Contact the customer support team if the problem persists. NPAL_ReplaceArp: could not override host next hop <ip addr> for portNum <value> NhopId = <value> Status = <value> WARNING This message indicates an attempt to override the next-hop with new information in hardware failed. Contact the customer support team if the problem persists. NPAL_ReplaceIpRoute: replace rt entry <ip addr>/<value> failed WARNING This message indicates an attempt to override the route entry with new information in hardware failed. Contact the customer support team if the problem persists. NPAL_SetDefaultIpRoute: Failed to add prefix NHId=<value>, status <value> WARNING This message indicates an attempt to set the default route to either CPU or DROP in hardware failed. Contact the customer support team if the problem persists.
N Messages
113
NSNA blocking Mac <MAC> in vlan <VlanID> Error This message is generated when NSNA blocks a Mac address for a vlan, which can be caused by two PC clients in one port. Check the clients connection. NSNA blocking Mac <mac_address> in vlan <vid>. Warning This message indicates that the system blocked a MAC address in the specified VLAN. Use the show nsna client command to see if there is another client of the same type on the NSNA port. NSNA port <Slot/Port>: move to red VLAN failed, so shutting down Error This message is generated when a port cannot be moved to a red vlan. Disable NSNA, administratively shut the port down and re-enable NSNA. NSNA port <>: move to red VLAN failed, so shutting down Fault This message indicates that the new VLAN ID in the ConfigPortExt or ConfigPort message from NSNAS is a red VLAN, but the NSNA port failed change state. The port shuts down. For the action required to recover the system from the condition that caused this fault message, see the NSNA port <>: To recover, disable nsna and admin down the port message description. NSNA port <Slot/Port>: To recover, disable nsna and admin down the port Error This message is generated when a port cannot be moved to a red vlan. Disable NSNA, administratively shut the port down and re-enable NSNA. NSNA port <>: To recover, disable nsna and admin down the port Fault This message indicates that you disable NSNA and administratively shut down the specific port to recover the system from the condition that caused the NSNA port <>: move to red VLAN failed, so shutting down to appear.
Action
114
SMP error messages
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description
No action required. NSNA port <Slot/Port>: move vlan failed, so moving to red state Error This message is generated when an attempt to move a port to a specified vlan has failed. Disable NSNA, administratively shut the port down and re-enable NSNA. NSNA port <>: move vlan failed, so moving to red state Fault This message indicates that the system failed to move a VLAN, so the specified NSNA port is moving to a red VLAN and red filter. Review and confirm the NSNAS and switch configuration. NTP Disabled INFO An informational log message. N/A NTP Enabled INFO An informational log message. N/A ntp global event sync failed ERROR HA-syncing NTP global configuration to secondary CPU failed. N/A ntp key event sync failed ERROR HA-syncing NTP key configuration to secondary CPU failed. N/A ntpCreateIntervalTimer: Cant create interval timer! FATAL Memory allocation failed.
N Messages
115
N/A ntpCreateKey: Cant allocate Key Entry! FATAL Memory allocation failed. N/A ntpCreateServer: Cant allocate Server Entry! FATAL Memory allocation failed. N/A ntpCreateServer: cant lock mutex! ERROR Couldnt get the semaphore. N/A ntpFetchAndAdjustTime: cant allocate serverList ERROR Memory allocation failed. N/A ntpFetchAndAdjustTime: Select Error ERROR The select function returns a negative value. N/A ntpHandleInput: Select error ERROR The select function returned a negative value. N/A ntpInitIo: cant allocate recvElement ERROR Memory allocation failed. N/A
116
SMP error messages
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
ntpInitIo: cant allocate recvElement ERROR Memory allocation failed. N/A ntpInitIo: cant bind UDP socket to port 123 ERROR The socket bind failed. N/A ntpInitIo: cant open UDP socket ERROR The socket() function returned a negative value. N/A ntpReadServers: cant allocate serverElement ERROR Memory allocation failed. N/A ntps server event sync failed ERROR HA-syncing NTP server configuration to secondary CPU failed. N/A ntpSendPkt: unable to forward UDP packet ERROR The sendto() function returned a sentLength value == -1. N/A ntpStart: Cant create mutex semaphore! FATAL Semaphore creation failed. N/A
O Messages
117
ntpSyncCallback: Unrecognized message type INFO Unknown message type. N/A ntpSyncCallback:corrupt msg ERROR Syncing failed due to invalid module version in message. N/A number of index does not equal size of link list ERROR This message indicates the index number of elements in the policy table differs from the size of the link list during the sanity check. N/A number of ipmc mll <value> has exceeded maximum <value> INFO This message is generated when the number of IGMP snoop groups you create exceeds the maximum supported by the switch (2000). The IGMP group can function properly but system performance will deteriorate. Reduce the number of IGMP snoop groups. number of ipmc entry has reached maximum <value>, can not create for grp_addr <group address> Fault This message is generated when the number of IPMC groups you create exceeds the maximum supported by the switch (1024). Reduce the number of IPMC groups on the switch.
O Messages
Message Severity Description Action oframe_alloc: buffer length too long ERROR This message is generated when the length of the IP frame is more than the maximum allowed length of the frame buffer size. Contact customer support for further troubleshooting.
118
SMP error messages
Old Filter <acgID> removal from port <PortNum> failed Error This message is generated when an old filter cannot be removed from a specified port. Confirm that the filter is valid and the NSNA service is disabled to attach the filter. Operator type <value> is not supported will be treated as mask. INFO The operators supported for match fields are Equal, greater-than-or-equal, less-than-or-equal, not-equal, mask. This message indicates that an unrecognized operator has been detected. This may be the result of corruption or a missing/insufficient consistency check. Try removing or enabling filters on the port, try to delete or create the ACG from the port, and check the dump using aclDumpAclTbl() or aclDumpAceList(). os_init: failed init_avl FATAL This message is generated when the system runs out of DRAM memory. Contact customer service with the following information available for further analysis:
Action

ospf_do_kill_nbr: Impossible State FATAL This message is generated when the system encounters an invalid state for neighbors current state of conversation. Contact customer service with the following information available for further analysis:

Message
ospfAddLsai - lsa len <value> is > max_lsa_len
O Messages
119
ERROR This message is generated if the LSA length is out of range. Contact customer service with the following information available for further analysis:

ospfAddLsai lsa type <value> ERROR This message is generated when the LSA type is invalid. Contact customer service with the following information available for further analysis:

ospfAddTent: couldnt allocate memory for path entry in the list WARNING This message is generated when the system is unable to allocate memory for the path entry list. Contact customer service with the following information available for further analysis:

ospfAddToReqList FAILED! nbr <ip address> lsid <lsid> ERROR This message is generated when an attempt to append a list to the neighbors request list fails, as a result of a req being inserted that already exists in the list. Contact customer service with the following information available for further analysis:
Action
120
SMP error messages
ospfCopyIntfInfo: could not find the IpRec for <value> FATAL This message is generated when no IP interface is found for the given IP address. Contact customer service with the following information available for further analysis:

ospfExtLsaLink: calloc failed: could not link <lsid> ERROR This message is generated when trying to allocate memory for LSA index in a linked list. Contact customer service with the following information available for further analysis:

ospfFindLsai: invalid lsa type <value> ERROR This message is generated when an invalid type is passed to find the LSA. N/A ospfFindLsai: Wrong lsa-type <value> FATAL This message is generated if an LSA with unknown type is received. Contact customer service with the following information available for further analysis:

Message Severity
ospfFlood: debug info ClrRtxCnt=<value> LsRefCnt=<value> INFO
O Messages
121
This message, generated before a Fatal error occurs, is the result of an unclear LSA ID, Receive nbr state that the system is unable to identify. No action required. ospfFlood: rx_nbr=<routeId>, rx_nbr_st=<value> lsid=<lsid> old rtx <value> not clear FATAL This message, generated before a Fatal error occurs, is the result of an unclear LSA ID, Receive nbr state that the system is unable to identify. Contact customer service with the following information available for further analysis:

opsfLeak - invalid path type <value> FATAL This message is generated if an invalid path type is encountered when attempting to leak into OSPF intra area. Contact customer service with the following information available for further analysis:

ospfLsaRefresh netlinks - no circ for ipa=<ip address> FATAL This message is generated when the network links are being refreshed and no OSPF circuit is found for the IP address. Contact customer service with the following information available for further analysis:

ospfLsaTimeout: lsai is null FATAL This message is generated when an invalid LSA identity is obtained.
122
SMP error messages
Action

ospfNeighborRetransmit: nbr=<routeId>, nbr_st=<value> lsid=<lsid>, type<value> old rtx <value> not clear FATAL This message is generated when the system encounters an invalid reference count for the LSA. Contact customer service with the following information available for further analysis:

ospfProcDDP: interface is null FATAL This message is generated when you are processing DDP packets and discover that interface is null. Contact customer service with the following information available for further analysis:

ospfProcLSU: interface is null FATAL This message is generated when the system encounters an invalid OSPF interface while sending an LSU. Contact customer service with the following information available for further analysis:
O Messages
123
ospfProcLSR: invalid - circuit is NULL FATAL This message is generated if the interface is a null due to internal protocol error. Contact customer service with the following information available for further analysis:

ospfRetransDel count=<value> FATAL This message is generated when the reference count of the LSA to be deleted from the retransmit list is zero. Contact customer service with the following information available for further analysis:

ospfRTXLink: failed to add FATAL This message is generated when a new link could not be inserted in the nbr retransmission list. Contact customer service with the following information available for further analysis:

ospfRTXLink: NULL Retransmit Entry ERROR This message is generated if there is no retransmit entry.
124
SMP error messages
Action

ospfSetCircArea: unable to find an IpRec for IfIndex <value> WARNING This message is generated if an invalid index for an IP record is passed. Contact customer service with the following information available for further analysis:

ospfSpfExtern: Running Incremental SPF when it is turned off ERROR This message is generated when incremental SPF runs after being disabled. Contact customer service with the following information available for further analysis:

ospfSpfInter: Running Incremental SPF when it is turned off ERROR This message is generated when incremental SPF runs after being disabled. Contact customer service with the following information available for further analysis:

Message Severity
ospfTimerLink invalid timer value <address> ERROR
O Messages
125
Action

ospfTimerUnlink invalid timer value <address> ERROR This message is generated when the system encounters an invalid OSPF timer signature. Rerun OSPF. If the problem is not resolved, contact customer service with the following information available for further analysis due to insufficient MLTs:

ospfUpdateLsai: len <value> is > max_len <value> FATAL This message is generated when the length of the LSA packet is greater than the maximum length defined. Contact customer service with the following information available for further analysis:

ospfUpdateLsai lsa type FATAL This message is generated when the system encounters an invalid LSA type. Contact customer service with the following information available for further analysis:

Message
ospfUpdateLsai lsa type <value>
126
SMP error messages
FATAL This message is generated when the LSA is being updated and an undefined LSA type is encountered. Contact customer service with the following information available for further analysis:

ospfVCEvent FATAL This message is generated when the virtual circuit event is invalid. Contact customer service with the following information available for further analysis:

ospfVCEvent: could not find route for dst=<value> Error This message is generated when the system is unable to obtain the MAC address of the next hop to be used by the OSPF hello packet. N/A ospfVCEvent: could not find the arp info dst=<value> WARNING This message is generated when the system looks up the ARP entry for the destination IP address. N/A ospfVerLsaCsum: the length field in lsa seems to be invalid ERROR This message is generated when the system encounters an invalid value for the length of the LSA.
P Messages
127
Action

Out of power resource, redundant power admin remain disabled ERROR This message indicates that not enough extra PoE power is reserved for backup, so the status of the redundant power admin remains the same (disabled). N/A
Action
P Messages
Message Severity Description p2LargeFbufInit: Cant allocate memory! FATAL This message specifies that memory could not be allocated for FBUF which is used to either transmit a packet, or process large received packets. This means the system will be unable to perform receive or transmit functions. Reboot the switch and contact the customer support team if the problem persists. Parsing of received xyz packet from TACACS+ server xyz failed ERROR Basic parsing of received packet failed. N/A Password modified for user-exec mode INFO This message indicates the password has been successfully changed for user-exec mode. N/A PCAP File in PCMCIA is being over-written INFO This message is generated when the PCAP autosave file in the PCMCIA is being overwritten. Copy the file from the PCMCIA.
Action
128
SMP error messages
Pcl size is unexpectedly large <value> ERROR This message indicates that the specified ACG required more than 128 filters in the hardware. This may result from an attempt to use rules with conditional matching like greater, less, range, not-equal. Try to minimize the operators. If that does not hel, remove some ACEs from the ACLs. PCMCIA is removed, Logging resumes on DRAM ERROR This message indicates that the PCMCIA card is removed. N/A PD may be disconnected due to new power limit WARNING This message indicates that the power limit was reduced which may cause the PD to be disconnected due to lack of power. Check to see if any PD power has been disconnected and if necessary, re-assign the power limit. Peer RSMLT IP <IP Address> is not in Local RSMLT IP subnet <IP Address> on Vlan <Vlan ID> Warning This message indicates that an IST peer IP address received by RSMLT does not belong to the same RSMLT IP subnet. Verify the IST peer IP addresses belong to the same IP subnet. If this error message continues to appear, contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. peGetPortMacStats: coreGetMacCounter : GT_EXCESSIVE_COLLISIONS, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. PhyReadModeReg : Invalid Card Type Slot WARNING
Action
P Messages
129
This message indicates an invalid card type has been detected. N/A PhyReadSpeedReg: Invalid Card Type WARNING This message indicates an invalid card type has been detected. N/A
pimCandidateRpTblEntryAdd: Out of memory Error There is no memory available to be allocated. Reduce the running configuration file size or reboot the switch. PoE backup power failure detected ERROR This message indicates that a power supply failure has been detected. The remaining PoE power may still able to support current PoE operation. Replace the bad power supply or continue to operate without backup power support. PoE backup power FATAL failure detected ERROR This message indicates that a power supply failure has been detected. The remaining PoE power cannot support the current PoE operations. All PoE cards will be administratively power disabled and redistributed. Replace the bad power supply. PoE backup PSE is activated WARNING This message indicates the backup power supply has started supplying PoE power. Most likely, this will happen after a power supply failed or was removed. Replace the bad power supply. PoE backup PSE is present and on standby INFO This message indicates a backup power supply has been detected and is ready to supply POE power when a power supply failure occurs. N/A
130
SMP error messages
PoE is down INFO This message indicates PoE card power was turned off. N/A PoE is up and running INFO This message specifies that PoE starts operation. N/A PoE Slot <value> Main Power Usage Off (below threshold), Power Consumption= <value> INFO This message indicates that power usage is from a PoE card. N/A PoE Slot <value> Main Power Usage On (above threshold), Power Consumption= <value> ERROR This message indicates that power usage is from a PoE card. N/A POE_LOCK failed ERROR This message specifies that the semaphore could not be obtained. N/A poeAppDownloadConfiguration: malloc failed! INFO This message indicates the system is out of memory space for a configuration download. N/A poeAppDownloadImage: PoE IPC communication error! INFO This message indicates that communication between CP and I/O modules failed.
P Messages
131
N/A poeDbInit: Could not create mutex ERROR This message indicates the system could not obtain the semaphore. N/A Port (<port>) re-enabled by auto recovery INFO This message is generated when a port shut down by CP-limit, Linkflap or SLPP is re-enabled by auto recovery. N/A port stream limit alloc failed Error This message is generated when allocating buffers for IGMP stream limitation, based on port, fails. N/A
p_intf_stream_limit alloc failed Error This message is generated when allocating buffers for IGMP stream limitation, based on interface, fails. N/A
p_intf_stream_limit alloc failed Error A failure to allocate memory for stream-limit on an interface has occurred. Reduce the running configuration file size or reboot the switch. poePowerMgr: Could not start poePowerMgr task ERROR This message indicates that the system was unable to execute the PoE task, so PoE operation stopped. Reboot the switch.
132
SMP error messages
poePowerSourceScan: re-scan power profile ERROR This message indicates a PoE power supply configuration error has been detected. Re-scan the power supply and rebuild the PoE power profile. poeTask: PoE controller communication ERROR PoE is disabled ERROR This message indicates that PoE controller initialization and communication failed. Reset the PoE card using admin disable and then re-enable the card. poeTask: PoE local DB init ERROR PoE is disabled ERROR This message indicates that PoE local configuration database initialization failed. Reset the PoE card using admin disable and then re-enable the card. poeTask: PoE module init ERROR PoE is disabled ERROR This message indicates that PoE operational configuration initialization failed. Reset the PoE card using admin disable and then re-enable the card. poeTask: PoE power (48V ERROR PoE is disabled ERROR This message identifies a PoE power 48V error. Replace PoE card, PoE power supply, or PoE chassis. poeTask: PoE task ERROR PoE is disabled ERROR This message specifies that the system was unable to execute the PoE task, so PoE operation stopped. Reset the PoE card using admin disable and then re-enable the card. poeTask: PSE power error detected, PoE is disabled ERROR This message identifies a PoE power 48V error.
P Messages
133
Reset the PoE card using admin disable and then re-enable the card. Policy Prefix table not init ERROR This message indicates the policy prefix table has not been initialized. N/A Port -- aborting INFO This message indicates that an 802.1X controlled port entered the aborting state of the Authenticator PAE State machine. No action is necessary. Port -- aborting INFO This message is generated when an 8021x controlled port enters the aborting state of Authenticator PAE State Machine No action necessary Port -- authenticating INFO This message indicates that an 802.1X controlled port entered the authenticating state of the Authenticator PAE State Machine. No action is necessary. Port -- authenticating INFO This message is generated when an 8021x controlled port enters the authenticating state of Authenticator PAE State Machine No action necessary Port -- connecting INFO This message indicates that an 802.1X controlled port entered the connecting state of the Authenticator PAE State machine. No action is necessary.
134
SMP error messages
Port -- connecting INFO This message is generated when an 8021x controlled port enters the connecting state of Authenticator PAE State Machine. No action necessary Port -- forced authorized INFO This message indicates that an 802.1X controlled port has entered the forced authorized state of the Authenticator PAE State Machine. No action is necessary. Port -- forced authorized INFO This message is generated when an 8021x controlled port enters the forced authorized state of Authenticator PAE State Machine No action necessary Port -- forced unauthorized INFO This message indicates that an 802.1X controlled port has entered the forced unauthorized state of the Authenticator PAE State Machine. No action is necessary. Port -- forced unauthorized INFO This message is generated when an 8021x controlled port enters the force unauthorized state of Authenticator PAE State Machine No action necessary Port -- held INFO This message indicates that an 802.1X controlled port entered the held state of the Authenticator PAE State Machine. No action is necessary. Port -- held INFO
P Messages
135
This message is generated when an 8021x controlled port enters the held state of Authenticator PAE State Machine No action necessary Port <portnum> PoE power is Off INFO This message indicates that port PoE power was turned off. N/A Port <portnum> PoE power is On INFO This message indicates that port PoE power was turned on. N/A portDisableMirrorByPort_8300: Wrong Mode <mode> WARNING This message indicates that when disabling the mirroring port, the mode parameter is an incorrect value. Verify the correct command parameters in the documentation and try again. portDisableMirroring_8300: gmirrDelRxport port <#> failed WARNING This message specifies that an RX port hardware entry deletion fails. Verify the correct command parameters in the documentation and try again. portDisableMirroring_8300: gmirrDelTxport port <#> failed WARNING This message specifies that a Tx port hardware entry deletion failed. Verify the correct command parameters in the documentation and try again. portEnableFlowControl_8300 called for non-8300 port INFO This message indicates there is a non-8300 port in the system. N/A portEnableFlowControl_8300: gprtPortFlowControlEnable Failed for port <value> Error <value>
136
SMP error messages
WARNING This message indicates that a hardware write failed for port flow control. N/A portEnableFlowControl_8300: gtPortXoffLimitSet Failed for port <value> Error <value> INFO This message indicates that a hardware write failed for port flow control. N/A portEnableFlowControl_8300: gtPortXonLimitSet Failed for port <value> Error <value> INFO This message indicates that a hardware write failed for port flow control. N/A portEnableMirrorByPort_8300: gmirrSetRxAnalyzerPort port <#> failed WARNING This message indicates that the system is unable to configure the Rx analyzer port in hardware. Verify the correct command parameters in documentation and try again. portEnableMirrorByPort_8300: gmirrSetRxPort port <#> failed WARNING This message indicates the system is unable to configure an Rx mirrored port in hardware. Verify the correct command parameters in documentation and try again. portEnableMirrorByPort_8300: gmirrSetTxAnalyzerPort port <#> failed WARNING This message indicates the system is unable to configure a Tx analyzer port in hardware. Verify the correct command parameters in documentation and try again. portEnableMirrorByPort_8300: gmirrSetTxPort port <#> failed WARNING This message indicates the system is unable to configure a Tx mirrored Port in hardware.
P Messages
137
Verify the correct command parameters in the documentation and try again. portEnableMirrorByPort_8300: Wrong Mode <mode> WARNING This message indicates that when enabling the mirroring port, the mode parameter is an incorrect value. Verify the correct command parameters in documentation and try again. portGetThrillRideSpeed: Non ThrilRide Card Type Slot <value> INFO This message indicates that a non-8300 card is inserted in the specified slot. N/A portPollThrillRide: port=<value>, link is unstable! WARNING This message indicates that an unstable link has been detected. N/A portSendCounterInfoToCP: trMsgAlloc failed FATAL This message indicates that memory cannot be allocated. Reboot the switch and contact the customer support team if the problem persists. portSendLinkInfoToCP: trMsgAlloc failed FATAL This message indicates that memory cannot be allocated. Reboot the switch and contact the customer support team if the problem persists. portVctCableStatus: normals=<value>,fails=<value>, shorts=<value>, opens=<value>, not <value> pairs ERROR This message indicates that the number of cable statuses exceeds the number of cable pairs. N/A
138
SMP error messages
portVctDoTest: Could not get the Result in WA. gtStatus not OK: <value> ERROR This message indicates that the result could not be obtained from the VCT test. Perform the test again. portVctDoTest: Could not get the Result. gtStatus not OK: <value> ERROR This message indicates the result could not be obtained from the VCT test. Perform the test again. portVctDoTest: Could not start the test in the WA. gtStatus not OK: <value> ERROR This message indicates that the VCT test could not be performed. Perform the test again. portVctDoTest: Could not start the test. gtStatus no OK: <value> ERROR This message indicates the VCT test could not be performed. Perform the test again. portVctDoTest: Could not write 0x2 into Reg30) ERROR This message indicates that the information could not be written into the register for the VCT test. Perform the test again. portVctDoTest: Could not write 0xa into Reg29) ERROR This message indicates that the information could not be written into the register for the VCT test. Perform the test again. portVctDoTest: Could not write back 0x0 into Reg30) ERROR This message indicates that the information could not be written into the register for the VCT test.
P Messages
139
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity
Perform the test again. portVctDoTest: Could not write back 0xa into Reg29) ERROR This message indicates that the information could not be written into the register for the VCT test. Perform the test again. portVctDoTest: invalid portnum <port> ERROR This message indicates that the specified port number is not correct. Check the port number and perform the test again. portVctDoTest: port <portnum> over high water mark ERROR This message indicates that the specified port number is not correct. Check the port number and perform the test again. portVctInitOneRecord: Record #<record> greater than max <value> ERROR This message indicates that the specified port number is not correct. Check the port number and perform the test again. portVctPortConfigurable: Bogus port #<value> ERROR This message indicates that the specified port number is not correct. Check the port number and perform the test again. ppeGetPortMacStats: coreGetMacCounter : GT_BAD_CRC, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_BRDC_PKTS_RCV, port <value> failed WARNING
140
SMP error messages
This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_BRDC_PKTS_SENT, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_COLLSIONS, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_DROP_EVENTS, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_FC_SENT, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_FRAGMENTS_PKTS, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_GOOD_FC_RCV, port <value> failed, WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists.
P Messages
141
ppeGetPortMacStats: coreGetMacCounter : GT_GOOD_OCTETS_SENT, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_GOOD_PKTS_RCV, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_GOOD_PKTS_SENT, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_JABBER_PKTS, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_LATE_COLLISIONS, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_MAC_RCV_ERROR, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_MAC_TRANSMIT_ERR, port <value> failed
142
SMP error messages
WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_MC_PKTS_RCV, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_MC_PKTS_SENT, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_OVERSIZE_PKTS, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_PKTS_1024TOMAX_OCTET S, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_PKTS_128TO255_OCTETS, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_PKTS_256TO511_OCTETS, port <value> failed WARNING This message indicates that the MAC counter cannot be read.
P Messages
143
Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_PKTS_512TO1023_OCTET S, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_PKTS_64_OCTETS, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_PKTS_65TO127_OCTETS, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : GT_UNDERSIZE_PKTS, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter : RegNum <value>, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists. ppeGetPortMacStats: coreGetMacCounter: GT_GOOD_OCTETS_RCV, port <value> failed WARNING This message indicates that the MAC counter cannot be read. Contact the customer support team if the problem persists.
144
SMP error messages
ppeInitMlt: Initialization of empty trunk groups failed ERROR This message specifies a trunk initialization failure in the hardware during system boot-up. Reboot the switch and contact the customer support team if the problem persists. ppePhyInit: coreWrite to Reg 0x0 FAILED Slot <value> ppPort <value> retVal <value> WARNING This message indicates that an attempt to write to a port physical register failed. Contact the customer support team if the problem persists. ppePhyInit: coreWrite to Reg 0x14 FAILED Slot <value> ppPort <value> retVal <value> WARNING This message indicates that an attempt to write to a port physical register failed. Contact the customer support team if the problem persists. ppePhyInit: coreWrite to Reg 0x18 FAILED Slot <value> ppPort <value> retVal <value> WARNING This message indicates that an attempt to write to a port physical register failed. Contact the customer support team if the problem persists. ppePhyInit: coreWrite to Reg 0x19 FAILED Slot <value> ppPort <value> retVal <value> WARNING This message indicates that an attempt to write to a port physical register failed. Contact the customer support team if the problem persists. ppePhyInit: coreWrite to Reg 0x1D FAILED Slot <value> ppPort <value> retVal <value> WARNING This message indicates that an attempt to write to a port physical register failed.
P Messages
145
Contact the customer support team if the problem persists. ppePhyInit: coreWrite to Reg 0x1E FAILED Slot <value> ppPort <value> retVal <value> WARNING This message indicates that an attempt to write to a port physical register failed. Contact the customer support team if the problem persists. ppePoLDownloadImage: create ppePoLFwUpgradeTask task failed ERROR This message indicates that the PoE task was unable to execute. Thus, the PoE image upgrading operation stopped. Reset the PoE card using admin disable, re-enable the card, and then restart the image upgrade process again. ppePoLDownloadImage: image upgrade stopped INFO This message indicates that image upgrading was stopped per instructions from the CP. N/A ppePoLDownloadImage: invalid argument ERROR This message identifies an invalid argument in the image download command. Verify the correct command parameters in documentation and try again. ppePoLDownloadImage: invalid image file size ERROR This message indicates that a download image file size mismatch was detected. Reset the PoE card using admin disable, re-enable the card, and restart the image upgrade process again. ppePoLDownloadImage: invalid packet received INFO This message indicates that an invalid packet ID was detected during image download.
146
SMP error messages
Action
Reset the PoE card using admin disable, re-enable the card, and restart the image upgrade process again. ppePoLDownloadImage: malloc failed INFO This message specifies that the system is out of memory space for an image download. Reset the PoE card using admin disable, re-enable the card, and restart the image upgrade process again. ppePoLFwUpgradeTask: image programming failed ERROR This message indicates that an image upgrade failed. Reset PoE card using admin disable, re-enable the card, and restart the image upgrade process again. ppeSetMltPort: Logical Id for MLT <value> not initialized ERROR This message indicates that an attempted port addition/deletion on an MLT was not configured in the hardware. Reboot the switch and contact the customer support team if the problem persists ppeSetMltPort: return status = <value> Add = <value> PortNum = <value> ERROR This message indicates that an addition/deletion of the port to and from the MLT failed during the hardware configuration. The switch maybe usable, but further MLT operations may fail. It is recommended that you reboot the switch and contact the customer support team if the problem persists. pp8kMstPortTxSmTxMstp: out of cpp buffers Error This message indicates that insufficient system memory prevents the switch from transmitting an MSTP BPDU. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis.
P Messages
147
pp8kRstPortTxSmTxConfig: out of cpp buffers Error This message indicates that insufficient system memory prevents the switch from transmitting RSTP configuration. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. pp8kMstPortTxSmTxRstp: out of cpp buffers Error This message indicates that insufficient system memory prevents the switch from transmitting an RSTP BPDU, when in MSTP mode. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. pp8kRstPortTxSmTxTcn: out of cpp buffers Error This message indicates that insufficient system memory prevents the switch from transmitting an RSTP TCN. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. PreconfigTask Slot <value>: cont_bootp_config request INFO This message is generated when bootp requests a preconfig task to run the preconfig. N/A PreconfigTask: card inserted request INFO This message is generated when a card is inserted from a slot in non-hidden mode. N/A PreconfigTask: card removed request
Message Severity Description Action Message Severity Description Action Message
148
SMP error messages
INFO This message is generated when a card is removed from a slot in non-hidden mode. N/A PreconfigTask: illegal cont_bootp_config ERROR This message appears when bootp requests a preconfig task to run the preconfig and the card is not in the inserted stage. Contact customer support for further troubleshooting. PreConfigTask: PreConfig will be re-tried!! INFO This message is generated when you specify that PreConfig will be re-tried. N/A PreConfigTask: Slot <value> NO pre-configured ERROR This message is generated when a slot is not pre-configured due to insufficient MLTs. Free up MLT and re-insert the card. PreconfigTask: waiting for request INFO This message is generated when a task is waiting for a request to come in non-hidden mode. N/A ProcPendingRefresh <ipaddr> type <value> ERROR This message is generated if the LSA type is not a hashed type. N/A ProcPendingRefresh: lsid <lsid> type <value> ERROR This message is generated if an LSA type is summary or external.
Q Messages
149
Action
No action required.
Q Messages
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity qosHwGetPortDefaultSize: port not present ERROR This message identifies an application programming error. Specifically, the port is not present. File a bug report. qosHwGetPortDefaultSize: unexpected card type ERROR This message identifies an application programming error. Specifically, an invalid card type is present. File a bug report. qosHwGetPortLineRate: port not present ERROR This message identifies an application programming error. Specifically, the port is not present. File a bug report. qosHwGetPortLineRate: unexpected card type ERROR This message identifies an application programming error. Specifically, an invalid card type is present. File a bug report. qosHwGetTxQueueDefaultSize: port not present ERROR This message identifies an application programming error. Specifically, the port is not present. File a bug report. qosHwGetTxQueueDefaultSize: unexpected card type ERROR
150
SMP error messages
This message identifies an application programming error. Specifically, an invalid card type is present. File a bug report. qosInitMap8021pToClassTbl: # of class not in range ERROR This message identifies an application programming error. Specifically, a traffic class parameter is out of range when passed to the function. File a bug report. qosInitMapClassTo8021pTbl: # of class not in range ERROR This message identifies an application programming error. Specifically, a traffic class parameter is out of range when passed to the function. File a bug report. qosInitPolicedMapClassTo8021pTbl: # of class not in range ERROR This message identifies an application programming error. Specifically, a traffic class parameter is out of range when passed to the function. File a bug report. qosInitPolicedMapDscpToCosTbl: unexpected CL level ERROR This message identifies an application programming error. Specifically, the conformance level is not in range. File a bug report. qosPolicyIdxTableInit: indexAlloc failed FATAL The switch is out of memory and will reboot after the message. Contact the customer support team if the problem persists. qosPolicyIdxTblAdd: - failed adding ERROR This message indicates that the switch failed to add an entry to the policy table. Contact the customer support team if the problem persists.
Q Messages
151
qosPolicyIdxTblAdd: index tbl not init ERROR This message identifies an application programming error. Specifically, the policy index table is not initialized. File a bug report. qosPolicyIdxTblFind: index tbl not init ERROR This message identifies an application programming error. Specifically, the policy index table is not initialized. File a bug report. qosPolicyIdxTblFindNext: index tbl not init FATAL This message identifies an application programming error. Specifically, the policy index table is not initialized. File a bug report. qosPolicyIdxTblRemove: - failed adding ERROR This message indicates that an attempt to remove an entry from the policy table failed. Contact the customer support team if the problem persists. qosPolicyIdxTblRemove: index tbl not init WARNING This message identifies an application programming error. Specifically, the policy index table is not initialized. File a bug report. qosPolicyTblAddEntry: malloc failed Id <value> WARNING This message indicates that the switch is out of memory. Reboot the switch and contact the customer support team if the problem persists. qosShowConfigMapInfo: Out of Memory
Message
152
SMP error messages
ERROR This message identifies a driver programming error. Specifically, the switch is out of buffering in show config buffer. Contact the customer support team if the problem persists.
R Messages
Message Severity Description Action Message Severity Description Action rad_callBackResponse unknown request id ERROR This message identifies an internal error in the software. If the problem persists, contact customer support. rad_changeRequestPkt unknown code <> in radius packet ERROR This message identifies an erroneous code in the header of the received RADIUS packet. Verify that the RADIUS server is functioning correctly and then contact customer support. rad_changeRequestPkt: unknown code <value> in radius packet ERROR This message indicates that an unknown packet type is seen when trying to send a request to the RADIUS server. This message is for debug purposes only and should not be seen by users. N/A rad_deQPendingRequest cannot find the request for seq_no<num> ERROR This message indicates that a matching request to the sequence ID in the RADIUS response packet cannot be found. If problem persists contact customer support. rad_enQPendingRequest failed to allocate memory ERROR This message indicates that the system is out of memory. If the problem persists, contact customer support. rad_extractReplyMessage failed to allocate memory
Action Message Severity Description Action Message Severity Description Action Message
R Messages
153
Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
ERROR This message is generated when the system is out of memory. If the problem persists, contact customer service. rad_handleServerResponse select failed<num> ERROR This message identifies aninternal error in the software If the problem persists, contactcustomer support. rad_incrIgapEnabledVlanCnt failed toallocate memory ERROR This message indicates that thesystem is out of memory. If the problem persists, contactcustomer support. rad_NewRequest: no radius serverconfigured INFO This message indicates that noRADIUS server has been configured. Configure at least one RADIUS server. rad_newSocket cannot bind UDP socketto port<num> ERROR This message indicates that anattempt to bind to the specified UDP port failed. Ensure that no other UDP service is configured on the same port. If the problem persists, contact customer support. rad_newSocket cannot create UDP socket ERROR This message indicates that anattempt to create a UDP socket failed. Contact customer support rad_newSocket failed to allocatememory ERROR This message indicates that thesystem is out of memory. If the problem persists, contact customer support. rad_receiveResponse received responsewith bad length recvd<num>
154
SMP error messages
ERROR This message indicates an invalid length for the received RADIUS response packet. Verify that the RADIUS server is functioning correctly. If the problem persists, contact customer support. rad_receiveResponse recvfrom failed<num> ERROR This message indicates that the switch is unable to receive data on the UDP socket. Contact customer support. rad_Request failed to allocate memory ERROR This message indicates that the system is out of memory. If the problem persists, contact customer support rad_Request Unknown request type<num> ERROR This message identifies an internal error in the software. If the problem persists, contact customer support. rad_sendRequest unable to send a UDP packet error<num> ERROR This message indicates that the switch is unable to send a UDP packet. If the problem persists, contact customer support. rad_sendRequest unknown code<num> in radius send pkt ERROR This message identifies an internal mismatch in the software for the RADIUS packet code. If the problem persists, contact customer support. rad_writeLog invalid message size<num> ERROR This message indicates that the IGAP accounting log message size is invalid. If the problem persists, contact customer support.
R Messages
155
radAcctBuildStopInterimValuePair failed to allocate memory ERROR This message indicates that the system is out of memory. If the problem persists, contact customer support. radAcctInterim failed to allocate memory ERROR This message indicates that the system is out of memory. If the problem persists, contact customer support. radAcctOff failed to allocate memory ERROR This message indicates that the system is out of memory. If the problem persists, contact customer support. radAcctOn failed to allocate memory ERROR This message indicates that the system is out of memory. If the problem persists, contact customer support. radAcctSendToServer cant bind UDP socket to port ERROR This message indicates that an attempt to bind to the specified UDP port failed. Ensure that no other UDP service is configured on the same port. If problem persists, contact customer support. radAcctSendToServer cant send data on UDP socket ERROR This message indicates that the switch is unable to send a UDP packet. If the problem persists, contact customer support. radAcctSendToServer cannot open socket ERROR
156
SMP error messages
This message indicates the switch is unable to create a UDP socket. If the problem persists, contact customer support. radAcctSendToServer failed to allocate memory ERROR This message indicates that the system is out of memory. If the problem persists, contact customer support. radAcctSendToServer socket recvfrom error ERROR This message indicates that the switch is unable to receive data on the UDP socket. If the problem persists, contact customer support. radAcctSendToServer socket select error ERROR This message identifies a software error. If the problem persists, contact customer support. radAcctSnmpInterim failed to allocate memory ERROR This message indicatest that the system is out of memory. If the problem persists, contact customer support. radAcctSnmpStart failed to allocate memory ERROR This message indicates that the system is out of memory. If the problem persists, contact customer support. radAcctSnmpStop failed to allocate memory ERROR This message indicates that the system is out of memory. If the problem persists, contact customer support. radAcctStart failed to allocate memory ERROR This message indicates that the system is out of memory.
R Messages
157
If the problem persists, contact customer support. radAcctStop failed to allocate memory ERROR This message indicates that the system is out of memory. If the problem persists, contact customer support. radAddEtherHooks Cannot add Input hook ERROR This message indicates that the switch is unable to initialize the software to capture login session statistics for use in RADIUS accounting. Contact customer support. radAddEtherHooks Cannot add Output hook ERROR This message indicates that the switch is unable to initialize the software to capture login session statistics for use in RADIUS accounting. Contact customer support. RadAuthNonEapMacAddr: no radius server configured INFO This message is generated when no radius server is configured while building the authentication request packet for the non-EAP client. Configure the radius server for EAP. radClearStat cant lock mutex ERROR This message indicates that the switch is unable to acquire a software resource. Contact customer support. radCliClearStat: cant lock mutex! ERROR This message is generated when the system could not obtain the semaphore. Reboot the switch and contact the Customer Service team if the problem persists.
158
SMP error messages
radCreateServer Cant allocate Server Entry FATAL This message indicates that the switch is unable to create a RADIUS server due to memory not being available. If the problem persists, contact customer support. radDictAttrGetValue Cant get value for attribute<string> ERROR This message indicates that a RADIUS attribute unknown to the switch is being looked-up. Verify that the sent and received RADIUS packets contain known attributes. radDictAttrSet Cant set value for attribute<string> ERROR This message indicates that a RADIUS attribute unknown to the switch is being looked-up. Verify that the sent and received RADIUS packets contain known attributes. radInsertServer cant lock mutex ERROR This message indicates that the switch is unable to acquire a software resource. Contact customer support. radInsertVp FATAL value pair ERROR This message indicates that the system is out of memory. If the problem persists, contact customer support. RADIUS authentication failed at <addr> : <msg> INFO This message indicates that RADIUS authentication failed at server <addr>. Failure reason is given in <msg>. N/A RADIUS authentication failed at<string> s INFO
R Messages
159
This message indicates that authentication failed for the specified user on the specified server. N/A RADIUS server returned invalid mac qos for -- MAC address WARNING This message is generated when the radius server sends the QoS attribute but with a invalid MAC QoS value. Check the Radius Server configuration for this client on the radius server. Verify if the QoS value is a valid value. radiusStart Cant create mutex semaphore FATAL This message indicates that the switch is unable to acquire a software resource. Contact customer support. radLock cant lock mutex ERROR This message indicates that the switch is unable to acquire a software resource. Contact customer support. radMalloc Cant allocate memory ERROR This message indicates that the system is out of memory. If the problem persists, contact customer support. radRemoveServer cant lock mutex ERROR This message indicates that the switch is unable to acquire a software resource. Contact customer support. radSendServer cant lock mutex ERROR This message indicates that the switch is unable to acquire a software resource.
160
SMP error messages
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
Contact customer support. radSnmpAcctNwData_Add Cant allocate memory for SNMP Session ERROR This message indicates that the system is out of memory. If the problem persists, contact customer support. rcBridgePP8300FilterTblSet: indexAdd failed! ERROR This message indicates that adding a MAC filter failed. N/A rcBridgePP8300FilterTblSet: malloc failed! ERROR This message indicates that memory allocation failed. N/A rcBridgeStaticMulticastTblSet:cant take semaphore! ERROR This message indicates that the semaphore will not add a multicast MAC entry. N/A rccExtendAggrNetList failed: no memory WARNING This message is generated when system is not able to allocate memory for a block of size 1024. Close all CLI sessions to free up memory. Contact customer support if problem persists. rccOspfHelloTimerLink invalid timer value <address> ERROR This message is generated when an invalid timer is passed to the timer linking function rccOspfHelloTimerLink().
R Messages
161
Action
Rerun OSPF. If the problem is not resolved, contact customer service with the following information available for further analysis due to insufficient MLTs:

rccOspfTimerUnlink invalid timer value <address> ERROR This message is generated when an invalid timer value is passed to the unlinking function. Rerun OSPF. If the problem is not resolved, contact customer service with the following information available for further analysis due to insufficient MLTs:

rcDiagVctTblGetBody: invalid GetOptions <value> ERROR This message indicates that the option to obtain the result is not correct. N/A rcDiagVctTblSetBody:semGive failed ERROR This message indicates the process of obtaining the VCT semaphore failed. Perform the test again. rcDumpIgmp: rcIpGetIf returns NULL ERROR This message is generated when the search for the IP interface returns NULL. This is an internal error. Contact customer support for further troubleshooting.
rcIgmpAccessTblSet : malloc failed Error A failure to allocate memory for the igmp access record has occurred. Reduce the running configuration file size or reboot the switch.
162
SMP error messages
rcIpAddRoute: route pointer is null. Fault This message indicates that the system failed to add a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpAddRoute: ipCircFromId failed for cid %d! Fault This message indicates that the system failed to add a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpAddRoute: rcIpAddArp failed with x.x.x.x nh: x.x.x.x cid x Fault This message indicates that the system failed to add a route, which causes system instability. If this fault is caused by a full (16k) system MAC table or a full (3k) system ARP entry table, no action is required. If this fault is not caused by a full MAC table or a full ARP entry table, contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpAddRoute: makeNextHopRouter failed with x.x.x.x nh: x.x.x.x cid x Fault This message indicates that the system failed to add a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpAddRoute: addIpRoute failed with x: ipaddr: x.x.x.x mask:x.x.x.x cid %d pRent x Fault This message indicates that the system failed to add a route, which causes system instability.
R Messages
163
Action
Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpDeleteRoute: route pointer is null./ Fault This message indicates that the system failed to delete a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpDeleteRoute: ipCircFromId failed for cid %d!/ Fault This message indicates that the system failed to delete a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpModifyNextHop: Arp pointer is NULL for route: x.x.x.x mask: x. Fault This message indicates that the system failed to update a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpModifyNextHop: trying to replace local route for route: x.x.x.x mask: x. Fault This message indicates that the system failed to update a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpModifyNextHop: rcIpAddArp failed with %x Fault This message indicates that the system failed to update a route, which causes system instability.
164
SMP error messages
Action
If this fault is caused by a full (16k) system MAC table or a full (3k) system ARP entry table, no action is required. If this fault is not caused by a full MAC table or a full ARP entry table, contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpModifyNextHop: makeNextHopRouter failed with x Fault This message indicates that the system failed to update a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpModifyNextHop: trying to replace blackhole for route: x mask: x Fault This message indicates that the system failed to update a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpModifyNextHop: replaceIpRoute failed with %d for route: x mask: x NextHop x Fault This message indicates that the system failed to update a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpStaticRouteTblSet: rcIpLoadRouteRec failed Fault This message indicates that the system failed to add a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpLoadRouteRec: unable to allocate a StatRouteRec for IfIndex x
Message
R Messages
165
Fault This message indicates that the system failed to add a route, which causes system instability. Wait for system memory to become available or reboot the chassis. rcIpLoadRouteRec: Adding static route dest=x, mask=x, and next=x failed Fault This message indicates that the system failed to add a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpLoadRouteRec: Adding default route, ipAddStaticRoute failed Fault This message indicates that the system failed to add a route, which causes system instability. If this fault is caused by a full (8k) system routing table or unavailable system memory, no action is required. If this fault is not caused by a full system routing table or unavailable system memory, contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpAddReplaceStaticRoute: rcIpStaticRouteActive failed Fault This message indicates that the system failed to add a route, which causes system instability. f this fault is caused by a full (8k) system routing table or unavailable system memory, no action is required. If this fault is not caused by a full system routing table or unavailable system memory, contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpAddStaticRtsByArp: could not find the specified nexthop Fault This message indicates that the system failed to add a route, which causes system instability.
166
SMP error messages
Action
Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpNextHopExists: arpaddUnres returns NULL Fault This message indicates that the system failed to add a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpAddMgmtStaticRoute: arpaddUnres returns NULL Fault This message indicates that the system failed to add a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpAddMgmtStaticRoute: Couldnt find the static route that has been successfully added to static route link list. Fault This message indicates that the system failed to add a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpProcCreateIpBulkList: unable to create the next hop for Static ARP x.x.x.x! Fault This message indicates that the system failed to add a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpPimGlobalGrpSet: Set Pim Static RP Error This message is generated when an attempt to globally enable or disable PIM Static RP fails.
R Messages
167
Contact technical support. rcIpPimGlobalGrpSet: Set Pim Glob Error This message is generated when an attempt to globally set one or more PIM parameter fails. N/A rcIpPimTblSet: set Pim If Error This message is generated when an attempt to enable or disable PIM on an interface fails. N/A
rcIgmpStat: rcIpGetIf returns NULL ERROR This message is generated when the search for the IP interface returns NULL. This is an internal error. Contact customer support for further troubleshooting. rcIpAddPortToVlan: Bad PortNum <value> ERROR This message is generated if the port number is out of range of valid values. Provide a valid port number. rcIpAddReplaceStaticRoute: rcIpStaticRouteActive failed ERROR This message is generated when the static route whose state must be changed to active is not present. Check the configuration for IP static route entries. rcIpAddRoute: addIpRoute failed with <value>: ipaddr: <ipaddr> mask: <mask> cid <cid> ERROR This message indicates that an attempt to add the route entry in hardware failed. N/A
168
SMP error messages
rcIpAddRoute: Arp pointer is NULL for route FATAL This message indicates that while adding an IP route, the ARP pointer is found to be NULL. This is a Fatal error. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpAddRoute: ipCircFromId failed for cid ERROR This message is generated if getting a pointer to the circuit fails. No immediate action required.
rcIpAddRoute: rcIpAddArp failed with <value> Status. ERROR This message is generated if the system is unable to add the ARP entry to the table. Enter a valid IP and next-hop. rcIpAddRoute: rcIpAddArp failed with <value>: <ipaddr> nh: <nexthop> cid <cid> ERROR This message specifies a failure to add the ARP entry in hardware. N/A rcIpAddRoute: route pointer is null ERROR This message is generated when an invalid or null route entry is created in the CLI for adding an IP route. Provide a valid route entry in the CLI. rcIpAddrTblConsistencyCheck: unable to allocate an IpRec for IfIndex <value> ERROR This message is generated if the IP record is not a valid entry. It occurs while performing the table consistency check. This is an internal error. Contact customer support for further troubleshooting.
R Messages
169
rcIpAddrTblConsistencyCheck: unknown row status <value> ERROR This message is generated if an invalid row status is encountered during a consistency check on the table. This is an internal error. Contact customer support for further troubleshooting. rcIpAddrTblSet: unable to allocate an IpRec for IfIndex <value> ERROR This message is generated if the system is unable to find or allocate a new IP record for the provided index. This may be caused by the unavailability of memory. Memory exhausted. Contact customer support for further troubleshooting. rcIpAddrTblSet: unable to find an IpRec for ifindex <value> ERROR This message is generated if an invalid index for a IP record is passed. This is an internal error. Contact customer support for further troubleshooting. rcIpAddrTblSet: unknown row status <value> ERROR This message is generated if an invalid row status is encountered. This is an internal error. Contact customer support for further troubleshooting. rcIpAddrTblSet: vlanGetMcastGroupId failed for Vlan <value> IfIndex <value> ERROR This message is generated if the VLAN is invalid. This is an internal error. Contact customer support for further troubleshooting. rcIpAddrTblSynCallBack: unable to allocate an IpRec for IfIndex <value> ERROR This message is generated when it is unable to allocate an IP record. This is an internal error. Contact customer support for further troubleshooting. rcIpAddStaticArp: arpadd failed for failed ERROR This message is generated if the addition of a static ARP entry in the ARP table failed.
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description
170
SMP error messages
Contact customer support for further troubleshooting. rcIpAddStaticArp: ipCircFromIFID failed ERROR This message is generated when the circuit data is null for a given circuit ID. Contact customer support for further troubleshooting. rcIpAddStaticArpByPort: found an arp while adding the entry ERROR This message indicates that an existing ARP entry was discovered while trying to add the static ARP entry with the same IP address. Contact the customer support team if the problem persists. rcIpAddStaticRoute: arpaddUnres returns NULL FATAL This message is generated if system is not able to locate an entry in the unresolved table. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology. rcIpAddStaticRtsByArp: could not find the specified nexthop ERROR This message is generated when an ECMP path index for a non-local static route is not equal to its maximum value. Check the configuration for the maximum value of the ECMP path index. rcIpArpLock: Cant take semaphore, rcIpArpLockSemId! ERROR This message indicates that the software ARP lock could not be accepted. Contact the customer support team if the problem persists. rcIpArpUnlock: semGive failed! ERROR This message indicates that the software ARP lock could not be accepted. Contact the customer support team if the problem persists.
R Messages
171
rcIpBootPReply: cppTxFrame failed! ERROR This message indicates that the switch failed to transmit a bootp relay packet. If this is a frequent occurrence, use trace level 9 3 to capture the CPP trace level log and obtain more details about the problem. rcIpConfDhcpTbIGet invalid get option ERROR This message indicates that a valid SNMP GET is selected. More troubleshooting is required. rcIpConfDhcpTblGet invalid get option %d ERROR This message is generated when an invalid Get request value is used for retrieving the DHCP record. Review and correct the Get request value. rcIpConfDhcpTblGet invalid Mode %d ERROR This message is generated when an invalid DHCP record mode value is used for retrieving the DHCP record. Review and correct the DHCP record mode value. rcIpDhcpForwardTblGet invalid get option %d ERROR This message indicates that an invalid Get request option parameter is set in the code. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpConfDhcpTbIGet invalid Mode ERROR This message indicates that an invalid mode is selected. More troubleshooting is required. rcIpConfigureCid: ipCircAddIPA failed for <value> on IfIndex <value> FATAL
172
SMP error messages
Description Action
This message is generated if the addition of an IP address to a circuit fails. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology. rcIpConfigureCid: ipCircAddIPA failed for on IfIndex FATAL This message is generated when an attempt to add an IP address to a circuit fails. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology. rcIpConfigureCid: ipCircCreate failed for %s on IfIndex ERROR This message is generated if the creation of an IP circuit failed. Contact customer support for further troubleshooting. rcIpDelArpByIfIndex: Cant create <value> task ERROR This message is generated when an attempt to spawn a task fails. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology. rcIpDelArpByIfIndexAll: Cant create <value> task ERROR This message is generated when an attempt to spawn a task fails. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology. rcIpDeleteRoute: route pointer is null ERROR This message is generated when a pointer to a route entry is invalid or NULL. This occurs when the system tries to delete the IP route entry dynamically from the table and finds that the pointer passed is NULL. Contact customer support for further troubleshooting.
Action
R Messages
173
rcIpDeleteStaticArp: unable to find an IpRec for IfIndex ERROR This message is generated when the delete sequence is initiated for an ARP entry and the search returns NULL. This is an internal error. Contact customer support for further troubleshooting. rcIpDeleteStaticArp: unable to find Static Arp Rec for <value> IfIndex ERROR This message is generated when the delete sequence is initiated for an ARP entry and the search for a static ARP record fails. This is an internal error. Contact customer support for further troubleshooting. rcIpDeleteStaticRoute: unable to find Static Route Rec to <value> Next Hop <nexthop> ERROR This message indicates that the static route to be deleted could not be found. Contact the customer support team if the problem persists. rcIpDhcpForwardTbIGet invalid get option ERROR This message indicates that an invalid SNMP GET is selected. More troubleshooting is required. rcIpDhcpSnoopSendOutFrame: cppTxFrame failed! Error This message is generated when DHCP packets cannot be sent. Check the system status for a problem with the cpp function. rcIpGetDhcpPortStatsRec: Bad PortNum ERROR This message indicates that a port number is not within its specified range. Check the configuration for port number minimum and maximum values. rcIpGetDhcpPortStatsRec: unable to allocate a DhcpPortStatsRec for PortNum ERROR This message indicates failure of memory allocation.
174
SMP error messages
Close all CLI sessions to free the memory. rcIpGetIcmpInMsgs: m2IcmpGroupInfoGet failed ERROR This message is generated if the ICMP group information fetching operation failed while receiving the message. No action required. Contact customer support for further troubleshooting. rcIpGetIcmpOutMsgs: m2IcmpGroupInfoGet failed ERROR This message is generated if the ICMP group information fetching operation failed while sending the message. No action required. Contact customer support for further troubleshooting. rcIpGetInEchos: m2IcmpGroupInfoGet failed ERROR This message is generated if the ICMP group information fetching operation failed while receiving the echoes. No action required. Contact customer support for further troubleshooting. rcIpGetInEchosReps: m2IcmpGroupInfoGet failed ERROR This message is generated if the ICMP group information fetching operation failed while receiving Inward echoes repetitions. No action required, contact Customer Support for further troubleshooting. rcIpGetOutEchoReps: m2IcmpGroupInfoGet failed ERROR This message is generated if the ICMP group information fetching operation failed while sending out the repetition echoes message. No action required, contact Customer Support for further troubleshooting. rcIpGetOutEchos: m2IcmpGroupInfoGet failed ERROR This message is generated if the ICMP group information fetching operation failed while sending out the echoes message. No action required. Contact customer support for further troubleshooting.
R Messages
175
rcIpGo: Cant create rcIp task FATAL This message is generated when an attempt to start the IP stacks receive (rcIpTask) task fails. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology. rcIpGo: NPAL_EnableVrId failed FATAL This message is generated when the system couldnt create the virtual router in hardware. Reboot the switch and contact the customer service team if the problem persists. rcipIgmpGroupTblEntryAdd: Cant malloc ERROR This message is generated when the system is unable to allocate memory for the IGMP group table entry. Increase DRAM memory size. rcIpLoadArpRec: unable to allocate a StatArpRec for IfIndex <value> ERROR This message is generated when the allocation of a static ARP record fails due to a memory allocation problem. Contact customer support for further troubleshooting. rcIpLock: Cant take semaphore, rcIpRouteLockSemId ERROR This message is generated when an attempt to acquire this semaphore fails. Contact customer support for further troubleshooting. rcIpMakeVlanRoutable: ipFindRoute failed for IfIndex <value> FATAL This message is generated when making the VLAN routable and finding IP failed. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology.
176
SMP error messages
rcIpModifyNextHop: Arp pointer is NULL for route: <ipaddr> mask: <mask> ERROR When adding the route to the hardware, the next-hop information must be together with the route. This error indicated that there is no software ARP entry associated with the route. Contact the customer service team if the problem persists. rcIpModifyNextHop: rcIpAddArp failed with <value> Status ERROR This message is generated if the system is unable to add the ARP entry to the table. Enter valid IP and next-hop. rcIpModifyNextHop: replaceIpRoute failed with <value> for route: <ipaddr> mask: <mask> NextHop <ipaddr> ERROR This message is generated when an attempt to change the route with the new next-hop failed in hardware. Contact the customer service team if the problem persists. rcIpModifyNextHop: trying to replace blackhole for route: <ipaddr> mask: <mask> ERROR Never try to replace the black hole route, but here it indicates it is doing so. You should only delete and add black hole route. N/A rcIpModifyNextHop: trying to replace local route for route: <ipaddr> mask: <mask> ERROR Never try to replace the local route, but here it indicates it is doing so. You should only delete and add local route. N/A rcIpNextHopExists: arpaddUnres returns NULL FATAL This message is generated when an attempt to locate an ARP entry in the unresolved table fails.
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description
R Messages
177
Action
Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology. rcIpProcessFrame: pP2IpBd!= NULL after call to iprx ERROR This message is generated if the pointer to buffer for sending the IP packet is not freed after a call to the IP receiver. Contact customer service for further troubleshooting. rcIpRemovePortFromVlan: Bad Port Number <value> ERROR This message is generated if the port number is out of range of valid values. Provide a correct and valid port number. rcIpRsmltNodeAdd: no ip record for specified IfIndex <Interface ID> Error This message indicates that an IP record does not exist for the Interface ID index obtained by RSMLT when you add an RSMLT Node. Confirm that an IP Interface with that ID index exists. If not, create the index and disable and enable RSMLT on the IST peer. If this error message still appears, reboot your chassis. If this error message continues to appear, contact the Nortel Technical Solutions Center for assistance. rcIpRsmltNodeDelete: no ip record for specified IfIndex <Interface ID> Error This message indicates that an IP record does not exist for the Interface ID index obtained by RSMLT when you delete an RSMLT Node. This error can cause a memory leak. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpRsmltSetPeerRecord: rcv RSMLT msg from IST, but no circuit on IfIndex <Interface ID> Error This message is generated when RSMLT receives IST messages indicating there is an RSMLT Circuit, when none exists.
Action
178
SMP error messages
Action
Record the error message and configuration, and reboot the chassis. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcipRouteIndexAdd() - failed adding <ipaddr>, Mask= <mask> WARNING This message is generated when adding a new route index failed. N/A rcipRouteIndexRemove() - failed removing <ipaddr>, Mask= <mask> WARNING This message is generated when removing a route index failed. Contact customer support for further troubleshooting. rcIpRsmltOperTblGet invalid Error This message is generated when the get operation on rcIpRsmltOperTable receives an invalid operation parameter. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpRsmltPeerTblGet invalid Error This message is generated when the get operation on rcIpRsmltPeerTable receives an invalid operation parameter. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpRsmltAddMacRecordForPeer: add MacAddress <MAC> failed on MGID <MGID> for IfIndex <Interface Index> Error This message indicates errors exist when you add an IST peer MAC address to the FDB table. The switch failed to perform a backup for the IST peer. Confirm RsmltEdgeSupport is enabled on the switch. Reboot the switch to recover the backup function. Contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis.
R Messages
179
rcIpRxFrame: cant signal semaphore FATAL This is due to inability of the system to release the semaphore. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology. rcIpStart: Cant create cpu and drop next hop! ERROR This message is generated when the system could not create the two next hop entries in hardware- with one pointing to the CPU and the other to drop. Reboot the switch and contact the customer service team if the problem persists. rcIpStart: Cant create mutual-exclusion semaphore rcIpRouteLockSemId FATAL This message is generated when an attempt to create a semaphore, used to control re-entry to the routing process, fails. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology. rcIpStaticRouteTblSet: rcIpLoadRouteRec failed ERROR This message is generated when MIB2 static route table entries are added and memory is exhausted due to duplicate entries. Increase DRAM size and contact customer support for further troubleshooting. rcIpRsmltForwardingForPeer: Unable to find the Vlan <Vlan ID>. IP RSMLT feature failed on Macaddr = <MAC Address> Warning This message indicates that RSMLT failed to find a valid Vlan when backing up IST peer forwarding information. Verify the IST peers have the same Vlan IDs. If this error message continues to appear, contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpRsmltTempDefaultRouteAdd: cant replace one static route
Message
180
SMP error messages
Error This message is generated when RSMLT does not replace one of static routes with the temporary default route. You can continue to operate the chassis, but note the scenario that results in the occurrence of this error message. Record the error message and configuration, and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpRsmltTempDefaultRouteAdd: add temporary default route to IST peer <IP Address> failed Error This message is generated when RSMLT does not add the temporary default route to the IST peer static route table. You can continue to operate the chassis, but contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpRsmltTempDefaultRouteDelete: cant delete temporary default route for vrf <Vrf ID> Error This message is generated when RSMLT does not delete the temporary default route for a VRF instance from the static route table. Delete the RSMLT default route from the static route table and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpSetEcmp: could not allocate mem for saving delpath ERROR This message indicates that insufficient memory for the switch to allocate for saving ECMP delete route paths when you disabled ECMP. Use the show sys per command to check system memory resource utilization. rcIpStaticRtSyncCallback: unsupported msg type <value> ERROR This message is generated when an invalid message type is encountered. This is an internal error. Contact customer support for further troubleshooting.
R Messages
181
rcIpSuperNetAddRoute: rarAddIpRoute failed with <value>:<ipaddr> mask: <mask> nh:<ipaddr> pRent <value> ERROR This message is generated if adding an IP route fails while trying to add a supernet address. Contact customer support for further troubleshooting. rcIpSuperNetAddRoute: rarAddIpRoute failed with <value>:<ipaddr> mask:<ipaddr> nh: <ipaddr> ERROR This message is generated if adding an IP route fails while trying to add all supernet addresses. Contact customer support for further troubleshooting. rcIpSuperNetReplaceRoute: rarReplaceIpRoute failed with <value> for route: <ipaddr> mask: <mask> NextHop: <ipaddr> ERROR This message is generated if replacing an IP route fails while trying to replace a supernet address. Contact customer support for further troubleshooting. rcIpTask: Cant create <value> message queue FATAL This message is generated when the rcipTask is unable to create a new message queue. Increase the DRAM size and contact customer support for further troubleshooting. rcIpTask: Cant take semaphore FATAL This message is generated when the semaphore was not available. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology. rcIpVlanSetIpAddress: chAssignMacAddrVlan failed for IfIndex <value>! MacOffset <value> FATAL
Message Severity
182
SMP error messages
Description Action
This message is generated if the system is not able to allocate a Mac Address for the VLAN. This is a fatal error. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration and network topology. rcIpVlanSetIpAddress: chGetMacAddrVlan failed for IfIndex%d! \nNo mac address available WARNING This message is generated if the available pool of MAC Addresses is exhausted. This is a software error. Contact customer service for further troubleshooting. rcIpVlanSetIpAddress: ipCircAddIPA failed for <value> on IfIndex <value> FATAL This message is generated when an invalid IP record is encountered. Thus, the circuit is not set. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology. rcIpVlanSetIpAddress: ipCircCreate failed for <value> IfIndex <value> ERROR This message is generated if an IP interface could not be created with the given index. This is an internal software error. Contact customer support for further troubleshooting. rcIpVlanUp: cppAttach failed for IfIndex <value> cid <value> FATAL This message is generated when updating VLAN info. It is caused by the failure to attach the IP record to the vxworks due to either memory being unavailable, or the maximum number of devices being utilized. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology. rcIpVlanUp: ifAddrSet failed for IfIndex <value> cid <value> FATAL This message is generated when setting the interface address fails.
Action
R Messages
183
Action
Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology. rcIpVlanUp: ifMaskSet failed for IfIndex <value> cid <value> FATAL This message is generated when setting the mask for the IP address record fails. Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration and network topology. rcIpGetVrrpRec: Bad IfIndex Error This message is generated if IfIndex is not within its specified range. Confirm IfIndex configuration. rcIpGetVrrpRec: Bad Vrid Error This message is generated if Vrid is not within its specified range. Confirm Vrid configuration. rcIpVrrpBecomeBackup: Unable to find the IP Rec for Vrid %d on IfIndex %d ERROR This message indicates that a Vlan IP record for a VRRP instance is not available when a switch is configured as the VRRP backup. Enable the VRRP instance if required. rcIpVrrpBecomeBackup: Unable to find the IP Rec for Vrid ___ on IfIndex ___ Error This message is generated when pointer to a record returns NULL because of its non-existence. Contact customer service with the following information available for further analysis:
184
SMP error messages
rcIpVrrpShutdown: Unknown state %d for Vrid %d on IfIndex %d ERROR This message is generated when the VRRP instance state checking fails during a VRRP shutdown. Use the show ip vrrp info vrf <vrfId> command to view the VRRP instance state. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpVrrpBecomeBackUpMaster: Unable to find the IP Rec for Vrid ___ on IfIndex ___ Error This message is generated when pointer to a record returns NULL because of its non-existence. Contact customer service with the following information available for further analysis:

rcIpVrrpBecomeMaster: Unable to find the IP Rec for Vrid %d on IfIndex %d ERROR This message indicates that a VLAN IP is not available when a switch is configured as a VRRP master. Use the show ip vrrp info vrf <vrfId> command to view the VRRP instance VLAN ID. Enable the VLAN IP interface if required. rcIpVrrpBecomeMaster addVrrpMacAddress failed 1 with Status = %d for IfIndex %d %s ERROR This message is generated when the switch fails to add a virtual MAC address to the TAPI layer when the switch is configured as a VRRP master. Confirm that the MAC address exists and can be added to the TAPI layer. Use trace level 56 3 to capture and view the HAL trace log for more error messages. rcIpVrrpBecomeBackUpMaster: Unable to find the IP Rec for Vrid %d on IfIndex %d ERROR
Message Severity
R Messages
185
Description Action
This message indicates that a Vlan IP record is not available when a switch is configured as the VRRP backup master. Use the show ip vrrp info vrf <vrfId> command to view the VRRP instance VLAN ID. Enable the VLAN IP interface if required. rcIpVrrpBecomeBackupMaster: addVrrpMacAddress failed 1 with Status = %d for IfIndex %d %s ERROR This message is generated when the switch fails to add a virtual MAC address to the TAPI layer when the switch is configured as a VRRP backup master. Confirm that the MAC address exists and can be added to the TAPI layer. Use trace level 56 3 to capture and view the HAL trace log for more error messages. rcIpVrrpBecomeMaster rarAddVrrpMacAddress failed with Status __ for IfIndex __ Fatal This message is generated when pointer to a record returns NULL because of its non-existence. Contact customer service with the following information available for further analysis:

rcIpVrrpBecomeMaster: Unable to find the IP Rec for Vrid ___ on IfIndex ___ Error This message is generated when pointer to a record returns NULL because of its non-existence. Contact customer service with the following information available for further analysis:

Message Severity
rcIpVrrpIn: Misconfigured Advertisment interval ___ for Vrid ___ on IfIndex ___, Local adver-int ___ Error
186
SMP error messages
Description Action
This message is generated when advertisement interval is configured differently on VRRP routers with the same VRID. Ensure that all the routers with the same VRID have the same advertisement interval. rcIpVrrpIn: Unknown Vrrp Message Type (%d) for Vrid %d on IfIndex %d ERROR This message is generated when the switch receives an incorrect VRRP advertisement message from another network switch. There is no action required. You can ignore this incorrect advertisement message. rcIpVrrpIn: Misconfigured Advertisment interval (%d) for Vrid %d on IfIndex %d, Local adver-int %d ERROR This message indicates that there is a mismatch between a VRRP advertisement interval received by the switch and the advertisement interval configured for the VRRP instance. Configure the VRRP instance to correct the advertisement interval mismatch. rcIpVrrpIn: Unknown Vrrp Message Type ___ for Vrid ___ on IfIndex ___ Error This message is generated when a Vrrp message is received with incorrect version and type. Check for a chassis malfunction or a malicious attacker in the subnet. rcIpVrrpIn: VRRP source IP %d.%d.%d.%d equal to VRRP IP, but priority is less than 255 on Vrid %d on IfIndex %d WARNING This message is generated when an invalid VRRP prority configuration is included in a VRRP packet received in an advertisement from another network switch. The VRRP address owner sends a VRRP advertisement that is not 255. Locate the VRRP address owner switch and correct its VRRP priority and IP configuration if required. Disable and enable the VRRP address owner switch. If the error message continues to appear, disable the VRRP instance on that switch. rcIpVrrpIn: VRRP source IP ___ equal to VRRP IP, but priority is less than 255 on Vrid ___ on IfIndex ___. Error
Action
Message Severity
R Messages
187
Description Action Message Severity Description
This message is generated when a Vrrp message is received from the IP owner but the priority is not 255. Check for a chassis malfunction or a malicious attacker in the subnet. rcIpVrrpIn: Invalid VRRP source IP %d.%d.%d.%d received for Vrid %d on IfIndex %d, same as local primary IP WARNING This message is generated when an invalid VRRP source IP address is included in a VRRP packet received in an advertisement from another network switch. Locate the other switch, correct its VRRP IP configuration if required, and disable and enable the switch. If the error message continues to appear, disable the VRRP instance on that switch. rcIpVrrpIn: Invalid VRRP source IP ___ received for Vrid ___ on IfIndex ___, same as local primary IP. Error This message is generated when a Vrrp message is received from a local source IP. Check for a chassis malfunction or a malicious attacker in the subnet. rcIpVrrpBecomeBackupMaster addVrrpMacAddress failed 1 with Status = ___ for IfIndex ___ Error This message is generated when pointer to a nonexistent record results in a NULL return. Contact customer service with the following information available for further analysis:
Action

rcIpVrrpBecomeBackupMaster addVrrpMacAddress failed 2 with Status = ___ for IfIndex ___ Error This message is generated when pointer to a nonexistent record results in a NULL return.
188
SMP error messages
Action

rcIpVrrpProcessAdvt: Unknown state %d for Vrid %d on IfIndex %d ERROR This message indicates that the current VRRP state is not available when the switch processes received VRRP advertisements. Use the show ip vrrp info vrf <vrfId> command to view the VRRP instance state. rcIpVrrpProcessAdvt: Unknown state ___ for Vrid ___ on IfIndex ___ Error This message is generated when unknown state has been encountered for VRRP state. Contact customer service with the following information available for further analysis:

rcIpVrrpSendAdvertisement: Unable to find the IP Rec for Vrid %d on IfIndex %d ERROR This message indicates that the Vlan IP record is not available when the switch sends a VRRP advertisement. Use the show ip vrrp info vrf <vrfId> command to view the VRRP instance VLAN ID. Enable the VLAN IP interface if required. rcIpVrrpSendAdvertisement: Unable to allocate an output buffer for Vrid %d on IfIndex %d ERROR This message is generated when insufficient memory causes the switch to fail to assign an output buffer when sending a VRRP advertisement. Use the show sys per command to check system memory resource utilization.
R Messages
189
rcIpVrrpSendAdvertisement: Unable to allocate an output buffer for Vrid ___ on IfIndex Error This message is generated when the pointer to the statically allocated VRRP hello buffer is NULL. Contact customer service with the following information available for further analysis:

rcIpVrrpSendAdvertisement: Unable to find the IP Rec for Vrid ___ on IfIndex ___ Error This message is generated when the pointer to a nonexistant record results in a NULL return. Contact customer service with the following information available for further analysis:

rcIpVrrpShutdown: Unknown state ___ for Vrid ___ on IfIndex ___ Error This message is generated when unknown VRRP state has been encountered. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcIpVrrpTic: Unknown state %d for Vrid %d on IfIndex %d ERROR This message is generated when the VRRP tic function returns unknown VRRP state information. Use the show ip vrrp info vrf <vrfId> command to view the VRRP instance state. rcIpVrrpTic: Unknown state ___ for Vrid ___ on IfIndex ___ Error
Message Severity
190
SMP error messages
Description Action
This message is generated when unknown state has been encountered for VRRP state. Contact customer service with the following information available for further analysis:

rcMcastLoadIfRec: unable to find an IpIfRec for IfIndex <value> ERROR This message is generated if the interface for multicast is not found because the IP record is not found. Contact customer support for further troubleshooting.
rcPimScalarsGrpSet Error An IpRec for cid cannot be located. Contact technical support. rcRadiusGlobalGrpSet Unable to spawn tRadAct task ERROR This message is generated when the system is unable to acquire a software resource. Contact customer service. rcRadiusServerTblSet cant take semaphore ERROR This message is generated when the system is unable to acquire a software resource. Contact customer service. rcVrrpOperTblGet invalid get option ___ Error This message is generated when the SNMP get option cannot be recognized.
R Messages
191
Action

rcVrrpRouterStatsTblGet invalid get option ERROR This message is generated when the VRRP Get request for router statistics returns an invalid value. Contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rcVrrpRouterStatsTblGet invalid get option ___ Error This message is generated when the SNMP get option cannot be recognized. Contact customer service with the following information available for further analysis:

rcVrrpUpdateTimerTask: Cant alloc VRRP fbuf!! Error This message is generated when allocation for VRRP frame buffer fails. Close all CLI sessions to free the memory. recieved NULL vlan from SNAS for non-pc client Fault This message indicates that the system received a VLAN ID of 0 in the MAC authentication message for a non-PC client. Review and confirm NSNAS configuration. Received unknown BOOTP op code ERROR This message is generated when the system receives some wrong bootp operating code.
192
SMP error messages
N/A Redundant Power admin enabled without backup power ERROR This message is generated when a misconfiguration is detected. N/A Releasing allocated MLTs INFO This message specifies that allocated MLTs are being released. N/A Remotely authenticated device type <> mac addr <mac addr> ignored. Another device of same type exists on port <port num>. Warning This message indicates that the system ignores a MAC authentication message because another device of the same type exists on the specified port. Review and confirm NSNAS configuration. resetting all I/O cards INFO This message is generated when, during system boot up, all I/O cards are reset by the master CPU. N/A resetting card ERROR This message is generated when a card is being reset due to the loss of the IPC connection. Reboot the switch and contact the customer service team if the problem persists. Resetting config flag INFO This message specifies that resetting the config flag is taking place. N/A
R Messages
193
RMON not init before RmonAlarmCreate WARNING This message indicates that the RMON alarm configuration is not loaded. Reload RMON alarm configuration. RMON not init before RmonEventCreate WARNING This message indicates that the RMON event configuration is not loaded. Reload RMON event configuration. Rmon not yet started, further RMON config may not be loaded WARNING This message indicates that the RMON module initialization is delayed while the configuration file is loading. Reload RMON related configuration. Route x.x.x.x index N has null next hop pointer. Fault This message indicates that the system cannot match a policy to a route by using the next-hop because the next-hop value of the route is 0. This causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. Route x.x.x.x/x.x.x.x index N has null next hop pointer Fault This message is generated when the next-hop for a route in a route table is 0, which can be caused by a neighbor router reboot or by a port shutdown. If this fault is caused by a neighbor router reboot or a port shutdown, no action is required. If either of these is not the reason for the fault, contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. RstGetTimerPortNum: Invalid timer type Warning This message is generated when the RST GetTimer function receives an invalid input parameter for a port..
Action
194
SMP error messages
Action
Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. RstGetTimerPortNum: NULL pointer Warning This message is generated when the RstGetTimerPortNum() function receives a null input parameter. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. RSTP INFO RSTP Port Role Change (<port or MLT>, <new Port Role>) Info This message is generated when an RSTP port role changes. No action required. rstpmstpTxbpdu: Cant send frame! Error This message is generated when the system fails to transmit an RSTP or MSTP BPDU. Use the show sys per command to check system memory resource utilization. Reboot the switch and contact customer service with the following information available: trace level 5 4, any memory dumps, switch configuration, and network topology for further analysis. RSTP INFO New Root (self) Info This message indicates that the switch you are accessing is the new RSTP root switch. No action required. RSTP INFO New Root (<bridge-id of new Root>) Info This message indicates that the switch you are accessing recognizes the network switch with the specified bridge ID as the new RSTP root switch. No action required. RSTP INFO Port Protocol Migration (<port or MLT> <Rstp | StpCompatible>)
R Messages
195
Severity Description Action Message Severity Description
Info This message is generated when port BPDUs change from STP to RSTP or from RSTP to STP. No action required. RSTP INFO OperEdge disabled on port <port or MLT> Info This message indicates that an RSTP port with edge-port administratively enabled receives a BPDU that changes the operational edge-port value to false (disabled). No action required. RTC and system clock difference is more than 5 seconds. Problem fixed. WARNING This message is generated when the RTC and system clock difference is more than 5 seconds. N/A rtmAddAltRouteSortedVrf: invalid ECMP route! Fault This message is generated when a route other than a static route has an alternative route with the same cost value as the best route. This affects system stability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rtmModifyRoutePref(), Could not promote alternative route. Possible alternate route loss Warning When you modify route type preference the system can upgrade some existing alternative routes to best route. This message indicates that this upgrade failed. Wait for system memory to become available or reboot the chassis. You can open trace level 45 4 for detailed information about this warning message. rtmDelRoute: could not find static rtrec for x.x.x.x/x.x.x.x. Fatal This message indicates that when you deleted a static route, the internal route was corrupted.
Action
Action
196
SMP error messages
Action
Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rtmReplaceRoute: unable to allocate a rcForwEnt[x] Fault This message indicates that there is insufficient system memory to add a new route or replace an existing route. Wait for system memory to become available or reboot the chassis. You can open trace level 45 4 for detailed information about this warning message. rtmReplaceRoute: unable to allocate a rcForwEnt Fault This message indicates that there is insufficient system memory to add a new route or replace an existing route. Wait for system memory to become available or reboot the chassis. You can open trace level 45 4 for detailed information about this warning message. rtmAddRoute cannot do rtm_rtAlloc Fault This message indicates that there is insufficient system memory to add a new route or replace an existing route. Wait for system memory to become available or reboot the chassis. You can open trace level 45 4 for detailed information about this warning message. rtmAddRoute: unable to allocate a rcForwEnt[0] Fault This message indicates that there is insufficient system memory to add a new route or replace an existing route. Wait for system memory to become available or reboot the chassis. You can open trace level 45 4 for detailed information about this warning message. rtmAddRoute: failed nhpaddUnres Fault This message is generated when you add or replace a route, the ARP table is full and the system cannot learn a new route immediately. No action required. rtmModifyRoutePref: VRF_RTM_NODE->rn_routes changed = x/
Message Severity Description Action Message
S Messages
197
Fault This message indicates that a statistics error. Contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rtmModifyRoutePref: VRF_RTM_NODE->rn_alt_routes changed = x Fault This message indicates that a statistics error. Contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. rtmReplaceRoute: unable to addUnres Fault This message is generated when you add or replace a route, the ARP table is full and the system cannot learn a new route immediately. No action required. Rx unsupported arguments: xyz ERROR Unsupported packet was received from specific server N/A Rx: frame truncated from server xyz ERROR Bad packet was received from specific TACACS+ server. N/A
S Messages
Message Severity Description Action Message Save config to file <file-name> failed. INFO This message is generated when the switch is unable to save the PCAP configuration. N/A Save config to file <file-name> successful.
198
SMP error messages
INFO This message is generated when the PCAP configuration is saved successfully in the slave CPU. N/A Secondary CPU resetting...) INFO This message is generated when the standby CPU is going to reset shortly. N/A Select failed WARNING This message is generated when select function call fails. Contact customer service for further troubleshooting. semDelete failed <value> ERROR This message is generated when the semaphore deletion failed. Reboot the switch and contact the customer service team if the problem persists.
send_rp_adv_with_zero_holdtime : malloc failed Error A malloc failure occurred when rp holdtime was sent. Reduce the running configuration file size or reboot the switch. SendLSUPacket: invalid circuit FATAL This message is generated when the system encounters an invalid configuration of the interface when a request to send LSU is made. Contact customer service and have the following information available for further analysis:

Message
setDiagMirrorByPort: Failed Id <id>
S Messages
199
Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity
WARNING This message is generated when the system could not add a mirroring hardware table entry because of an incorrect ID or a lack of OS resources. Verify the correct command parameters in the documentation and try again. sfInit: remaining Xbar interrupt cause <value> cpldIntCause <value> cannot enable SF interrupt ERROR This message is generated when the system cannot enable XBAR interrupt. Contact the customer service team if the problem persists. Slot <value> Vlan <value> Rel_Port_Id <value> INFO This message specifies the slot, VLAN, and release port information for a previous log message. N/A Slot <value> image download. WARNING This message is generated when an image download completes during the image upgrade process. N/A Slot <value> insufficient PoE power resource INFO This message is generated when there is not enough PoE power available for target slot allocation. N/A Slot <value> out of PoE power resource INFO This message is generated when there is not enough PoE power available for target slot allocation. N/A Slot <value> PoE power admin disabled INFO
200
SMP error messages
Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
This message is generated when the PoE card power is administratively disabled. N/A Slot <value> PoE power admin enabled INFO This message is generated when the PoE card power is administratively enabled. N/A Slot <value> PoE power allocated INFO This message is generated when PoE card power is allocated. N/A Slot <value> PoE power removed INFO This message is generated when the allocated PoE card power is eliminated after a hot removal. N/A Slot <value> PoE power usage exceed threshold limit INFO This message is generated when the PoE card consumed more power than the threshold set. Monitor the overall power consumption to prevent PoE power overload. If necessary, disable PoE port power administratively. Slot <value> PoE power usage returns below threshold limit ERROR This message is generated when the PoE card consumes less power than the threshold set after exceeding it. N/A Slot <value>: <msg> INFO This message is generated when the system receives boot time information from a different slot. N/A
S Messages
201
Slot <value> cardPN is not programmed ERROR This message is generated when the card part number is missing in SEEPROM. Replace the card. slot <value> has no PartNumber in SEEPROM., WARNING This message is generated when the part number is missing in SEEPROM. Replace card. Slot <value> Xbar has invalid Multicast Table. Failed to rewrite <value> times ERROR This message is generated when the multicast table on the slave CPU crossbar is corrupted and cannot be corrected. Re-insert or replace the card. Slot <value> Xbar has invalid Multicast Table. Failed to rewrite <value> times FATAL This message is generated when the multicast table on Xbar on the master CPU is corrupted and cannot be corrected. Re-insert or replace the card. Slot%d - card not init yet ERROR This message is generated when card hardware has not yet been fully initialized by the chassis. Contact customer support for further troubleshooting. Slot: <value> Current State: <value> INFO This message is generated when a card is inserted from a slot in non-hidden mode. N/A Slpp: Cant create MAC Range Filter! ERROR This message is generated when the MAC range filter cannot be created.
202
SMP error messages
Reboot the switch and try again. Slpp: Cant create slpp polling task! ERROR This message is generated when the SLPP polling task is not created. Reboot the switch and try again. Slpp: Cant create peer MAC Range Filter! ERROR This message is generated when the peer switch MAC range filter cannot be created. Check to see if the image versions on the SMLT switch pair are the same.

If yes, reboot the SMLT pair and try again. If no, reconfigure the SMLT switch pair to have the same image versions.
Slpp: Cant remove peer MAC Range Filter! ERROR This message is generated when the peer switch MAC range filter cannot be removed. Reboot the switch the SMLT pair and try again slppClearCopSACounter: malloc of message parameter failed ERROR This message is generated when the allocation of new memory fails. Reboot the switch and try again. slppRx: SLPP packet was received on Port <port> on VLAN <vlan>, but the packet is originated on VLAN <vlan> from SRC-Mac <MAC address> WARNING This message is generated when an SLPP packet is not received on the expected port or vlan. Verify the vlan and port configuration is correct. There can be network wiring problems between different vlans. slppRx: SLPP packet received Rx-Vlan <vlan>, Rx-Port <port>, PDU-Vlan <vlan>, SRC-Mac <MAC address> WARNING
Message Severity
S Messages
203
This message is generated when a SLPP packet is received and the corresponding ports are shutdown. Verify switch configuration and network wiring. Remove the loop. slppSetCopMacAddress: malloc of message parameter failed ERROR This message indicates that the allocation of new memory fails. Reboot the switch and try again. slppTxSlppPdu: Cant get BD! ERROR This message is generated when the transmit buffer cannot be located. Reboot the switch and try again. slppTxSlppPdu: Cant send frame! ERROR This message specifies that the transmission of SLPP packet failed. Several SLPP transmission failures do not indicate a serious problem. If this message appears continuously, reboot the switch and try again. sltInstrDeleteByPort: cant lock mutex! ERROR This message is generated when a semaphore cannot be taken while deleting an SLT port. N/A smltEnable: Cant set McGrpId! ERROR This message is generated when an IST multicast group ID cannot be set. N/A smltEnable: Cant get new mgid ERROR This message is generated when a new mgid is unavailable while enabling smlt. N/A smltGo: taskSpawn() failed
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message
204
SMP error messages
FATAL This message is generated when the start smlt master/slave task has failed. N/A Smlt Id array overflow in Rsmlt Circ on Vlan <Vlan ID> Error This message is generated when the number of SMLT IDs in a Vlan exceeds the RSMLT maximum. Confirm the SMLT ID limitations for an RSMLT and decrease the number of SMLT IDs in the VLAN as required. If this error message continues to appear, contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. smltProcessMsgs: message too long readLen (Actual Length) maxLen (Maxium Length) type (message type) ERROR This message is generated when an oversized SMLT message is received. N/A smlt_port_unlock_timeout_notify: malloc failed! ERROR This message is generated when a malloc message buffer has failed. Check memory usage. smltProcessMsgs: out of resource! ERROR This message is generated when you cannot malloc memory for the SMLT message buffer. Check memory usage. smltSendIgmpV3Msg: Cant alloc buffer ERROR This message is generated when it is not possible to malloc the message buffer for SMLT IGMP V3 message. Check memory usage. smltSendMsgs: out of resource!
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message
S Messages
205
Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action
ERROR This message is generated when there is no memory available for allocating an SMLT message buffer. Check memory usage smltStart: Cant create mutex semaphore! FATAL This message is generated when a semaphore cannot be created while an SMLT task is starting. N/A smltStgPortDisabled: cant lock mutex! ERROR This message is generated when a semaphore cannot be taken while disabling an smlt STG port. NA smltSyncCallback: unsupported version version-number ERROR This message is generated when only SMLT version 1 is supported. NA smltSyncCallback: Invalid msgType MsgTypeId Error This message is generated when an unsupported message buffer for smlt Synchronization routine is encountered. NA SmltType number is overflow, IfIndex=<Interface Index>, vlan Id=<Vlan ID>, type SMLT, Smlt Id=<Smlt ID> Error This message is generated when the number of SMLT IDs exceeds the RSMLT maximum. Confirm the SMLT ID limitations for an RSMLT and decrease the number of SMLT IDs in the VLAN as required. If this error message continues to appear, contact the Nortel Technical Solutions Center for assistance.
206
SMP error messages
SmltType number is overflow, IfIndex=<Interface Index>, vlan Id=<Vlan ID>, type SLT, Smlt Id=<Smlt ID> Error This message is generated when the number of SLT IDs exceeds the RSMLT maximum. Confirm the SLT ID limitations for an RSMLT and decrease the number of SLT IDs in the VLAN as required. If this error message continues to appear, contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. smltUpdateAruMcGroupReg: NPAL_NewMgid failed ERROR This message is generated when a MG ID is not available when updating the ARU MGID register. N/A Socket failed INFO This message is generated when the system cannot create a new socket. Reboot the switch and contact the customer service team if the problem persists. source <src filename> and destination <dst filename> INFO This message is generated when the source file is <src filename> and destination file is <dst filename>. N/A ssaFilterCreateModAce: invalid type <Type> Error This message is generated when an invalid ace type number is encountered when creating a filter for NSNA. Check the corresponding ace. ssaFilterCreateIpACL: rcFilterAclTblSet failed <>. Fault
Message Severity Description Action Message Severity Description Action Message Severity
S Messages
207
Description
This message indicates that you did not specify a VLAN filter ID when you configured an NSNA VLAN. The system failed to automatically create the filter and the IP ACL table could not be set. Configure the filter manually. If this does not clear the error, contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. ssaFilterCreateIpACL: ssaFilterCreateModAce failed for DHCP <>. Fault When you create an NSNA VLAN, the system automatically creates an IP ACL and a non-IP ACL. This message indicates that the system failed to create an ACE for the IP ACL. Configure the ACE manually. If this does not clear the error, contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. ssaFilterCreateIpACL: ssaFilterCreateModAce failed for yellow-subnet <>. Fault When you create an NSNA VLAN, the system automatically creates an IP ACL and a non-IP ACL. This message indicates that the system failed to create an ACE for the IP ACL. Configure the ACE manually. If this does not clear the error, contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. ssaFilterCreateIpACL: ssaFilterCreateModAce failed for DNS <>. Fault When you create an NSNA VLAN, the system automatically creates an IP ACL and a non-IP ACL. This message indicates that the system failed to create an ACE for the IP ACL. Configure the ACE manually. If this does not clear the error, contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. ssaFilterCreateIpACL: ssaFilterCreateModAce failed for ICMP <>. Fault When you create an NSNA VLAN, the system automatically creates an IP ACL and a non-IP ACL. This message indicates that the system failed to create an ACE for the IP ACL. Configure the ACE manually. If this does not clear the error, contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis.
Action
Action
Action
Action
Action
208
SMP error messages
ssaFilterCreateIpACL: ssaFilterCreateModAce failed for VOIP vid <vlan id> <>. Fault When you create an NSNA VLAN, the system automatically creates an IP ACL and a non-IP ACL. This message indicates that the system failed to create an ACE for the IP ACL. Configure the ACE manually. If this does not clear the error, contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. ssaFilterCreateIpACL: ssaFilterCreateModAce failed for HTTP <>. Fault When you create an NSNA VLAN, the system automatically creates an IP ACL and a non-IP ACL. This message indicates that the system failed to create an ACE for the IP ACL. Configure the ACE manually. If this does not clear the error, contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. ssaFilterCreateIpACL: ssaFilterCreateModAce failed for HTTPS<>. Fault When you create an NSNA VLAN, the system automatically creates an IP ACL and a non-IP ACL. This message indicates that the system failed to create an ACE for the IP ACL. Configure the ACE manually. If this does not clear the error, contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. ssaFilterCreateIpACL: ssaFilterCreateModAce failed for default<>. Fault When you create an NSNA VLAN, the system automatically creates an IP ACL and a non-IP ACL. This message indicates that the system failed to create an ACE for the IP ACL. Configure the ACE manually. If this does not clear the error, contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. ssaFilterCreateIpACL: rcFilterAclTblSet failed <ErrorNum> Error This message is generated when the acl set has failed. Check the corresponding acl.
Action
Action
Action
Action
S Messages
209
ssaFilterCreateIpACL: ssaFilterCreateModAce failed for DHCP <ErrorNum> Error This message is generated when AttemptCreate ace of IP acl for DHCP has failed. Check the corresponding ace. ssaFilterCreateIpACL: ssaFilterCreateModAce failed for yellow- subnet <ErrorNum> Error This message is generated when an attempt to create an ace of IP acl for yellow-subnet has failed. Check the corresponding ace. ssaFilterCreateIpACL: ssaFilterCreateModAce failed for ICMP <ErrorNum> Error This message is generated when an attempt to create an ace of IP acl for ICMP has failed. Check the corresponding ace. ssaFilterCreateIpACL: ssaFilterCreateModAce failed for DNS <ErrorNum> Error This message is generated when an attempt to create an ace of IP acl for DNS has failed. Check the corresponding ace. ssaFilterCreateIpACL: ssaFilterCreateModAce failed for HTTP <ErrorNum> Error This message is generated when an attempt to create an ace of IP acl for HTTP has failed. Check the corresponding ace. ssaFilterCreateIpACL: ssaFilterCreateModAce failed for HTTPS <ErrorNum> Error This message is generated when an attempt to create an ace of IP acl for HTTPS has failed. Check the corresponding ace.
210
SMP error messages
ssaFilterCreateIpACL: ssaFilterCreateModAce failed for default <ErrorNum> Error This message is generated when an attempt to create an ace of IP acl for the default filter has failed. Check the corresponding ace. ssaFilterCreateIpACL: ssaFilterCreateModAce failed for VOIP vid <VID> <ErrorNum> Error This message is generated when an attempt to create an ace of IP acl for VoIP Vlan <vid> has failed. Check the corresponding ace. ssaFilterCreateIpACL: ssaFilterCreateModAce failed for SMB [tcp|udp]: <Portnum> <ErrorNum> Error This message is generated when an attempt to create an ace of IP acl for tcp/udp port <Portnum> has failed. Check the corresponding ace. ssaFilterCreateModAce: invalid type <>. Fault If you do not specify a filter ID when you configure an NSNA VLAN, the system automatically creates a filter. This message indicates that an invalid ACE type was generated when the system created the filter. Configure the filter manually. If this does not clear the error, contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. ssaFilterCreateNonIpACL : rcFilterAclTblSet failed<>. Fault This message indicates that the system failed to create the default non-IP ACL. Configure the non-IP ACL manually. ssaFilterCreateNonIpACL: ssaFilterCreateModAce failed for tag ARP<>. Fault This message indicates that the system failed to create an ACE for a non-IP ACL. Configure the non-IP ACEs manually.
Action
S Messages
211
ssaFilterCreateNonIpACL: ssaFilterCreateModAce failed for untag ARP<>. Fault This message indicates that the system failed to create an ACE for a non-IP ACL. Configure the non-IP ACEs manually. ssaFilterCreateNonIpACL: ssaFilterCreateModAce failed for default<>. Fault This message indicates that the system failed to create an ACE for a non-IP ACL. Configure the non-IP ACEs manually. ssaFilterCreateNonIpACL: rcFilterAclTblSet failed <ErrorNum> Error This message is generated when an attempt to create a non-IP acl has failed. Check the corresponding acl. ssaFilterCreateNonIpACL: ssaFilterCreateModAce failed for tag arp <ErrorNum> Error This message is generated when an attempt to create a non-IP acl for tag arp has failed. Check the corresponding ace. ssaFilterCreateNonIpACL: ssaFilterCreateModAce failed for untag ARP <ErrorNum> Error This message is generated when an attempt to create non-IP acl for untag arp has failed. Check the corresponding ace. ssaFilterCreateNonIpACL: ssaFilterCreateModAce failed for default <ErrorNum> Error This message is generated when an attempt to create non-IP acl for default filter has failed. Check the corresponding ace.
212
SMP error messages
ssaPortMovedToVlan port <Slot/Port> moved to vlan <vlanID> with invalid color <color> Error This message is generated when the vlan color selected to move the port into is invalid. Confirm that the vlan color is in red/yellow/greep/voip. ssaPortMovedToVlan port <x/y> moved to vlan vid> with invalid color <num>. Fault This message is generated when you move an NSNA port to a VLAN with an NSNA color that is not red, yellow, or green. Verify that the NSNA color for the VLAN is Red, Green, or Yellow. ssaVlanConfigPortBody: Filter Attachment to port <> failed Fault This message indicates that the system cannot attach a new filter to the specified port when it receives a ConfigPortExt or ConfigPort message from NSNAS. Disable and enable NSNA on the port specified in the fault message. SSCP inactivity+statusQuo TimeOut : cleaning up Information This message indicates that an SSCP connection failed and the system is changing all NSNA ports to red state. Check the SSCP connection and confirm the NSNAS is accessible. SSCP connection <> with NSNAS IP <ip address> Information This message indicates that the specified SSCP connection is active. No action required. SSCP connection hello interval <> inactivity interval <> status-quo interval <> Information This message displays SSCP connection parameters. No action required. sscp msg type <type> is greater than max number of supported messages <maxnum>
Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message
S Messages
213
Severity Description Action Message Severity Description Action Message Severity Description Action
Error This message is generated when the SSCP message type is invalid. Check for a possible mismatch of the ERS8300 and NSNAS versions. sscpProcessMsg : Malloc failed ! Error This message is generated when a failure of malloc memory for the message has occurred. Check the system memory. sscpProcessMsg : Malloc failed ! Fault This message indicates that there is insufficient memory for the system to allocate to processing SSCP messages. Use the show sys perf command to view system memory utilization. Disable and enable NSNA globally. sscpProcessMsg : realloc failed Error This message is generated when the realloc memory for the message has failed. Check the system memory. sscpProcessMsg : realloc failed Fault This message indicates that there is insufficient system memory to process an SSCP message. Use the show sys perf command to view system memory utilization. Disable and enable NSNA globally. sscpProcessMsg : Problem while reading data from socket Fault This message indicates that the system cannot read the message from the socket. Verify the function of the physical link or socket. If they function properly, disable and enable NSNA globally. SSCP inactivity+statusQuo TimeOut : cleaning up
Message
214
SMP error messages
Info This message is generated when the SSCP inactivity+statusQuo has timed out. Check the network connection to NSNAS. sscpProcessMsg : Problem while reading data from socket Error This message is generated when it is not possible to read from the socket. Check the network connection. SSCP connection [Rejected|Accepted|Re-established] with NSNAS IP <IPAddr> Error This message is generated when the SSCP connection with NSNAS has been rejected, accepted or re-established. Check the network connection to NSNAS. SSCP connection hello interval <seconds> inactivity interval <seconds> status-quo interval <seconds> Info This message is generated when the SSCP connection hello interval has exceeded the allowable inactivity or status-quo intervals. N/A sshd_shutdown_client: failed to send message for session <SessionID> Error This message is generated when the ssh message is not sent while the client is shutting down. N/A SSH authentication timeout session <SessionID> from <RemoteIPAddr> Info This message is generated when SSH authentication has timed out. N/A STG <value> HAS ALREADY BEEN USED INFO This message is generated when the maximum number of supported STGs has already been taken.
S Messages
215
Change the configuration to free STGs. stg_event_handler: Unrecognized message type %d Warning This message is generated when the system receives an unrecognized STG message type. No action required. stgMakePortForwarding: Port %s is already forwarding Warning This message indicates that the specified STG port is already configured as forwarding. No action required. Supported IP addresses is 1 SNAS sent <number of IP> in auth notify message Error This message is generated when SNAS has sent more than one IP to the switch. Check the NSNAS server. syncTaskAdd: failed to create <taskId> ERROR This message is generated when the system fails to create the semaphore. Reboot the switch and contact the customer service team if the problem persists. syncTaskAdd: taskVarAdd <value> failed, ERROR This message is generated when the system fails to add a task variable. Reboot the switch and contact the customer service team if the problem persists. syncTaskAdd: taskVarSet <value> <value> semId <value> ERROR This message is generated when the system fails to set the task variable semId. Reboot the switch and contact the customer service team if the problem persists.
216
SMP error messages
syncTaskDelete: IPC semDelete <value> currentId <value> FATAL This message is generated when the IPC semaphore semId from the current Id fails. Reboot the switch and contact the customer service team if the problem persists. System Arp Table Full ERROR This message is generated when an entry is about to be added to the ARP table and there is no empty slot available. Delete unwanted ARP entries from the table. System clock faster than real-time clock. Problem fixed. ERROR This message is generated when the system clock is faster than a real-time clock. N/A System out of memory FATAL This message is generated when the system is out of memory. If the problem persists, contact customer service.
T Messages
Message Severity Description Action Message Severity Description Action Message Severity Table syncing failed for ntp key entries ERROR HA-syncing for NTPkey table failed. N/A Table syncing failed for ntp server entries ERROR HA-syncing for NTP server table failed. N/A TACACS+ authentication failed INFO
T Messages
217
TACACS+ authentication failed N/A TACACS+ authentication succeeded INFO TACACS+ authentication succeeded N/A TACACSG_authenticate_user: failed to send CONTINUE ERROR Software state machine error. N/A TACACSG_authenticate_user: keep server - server not found ERROR Software state machine error. N/A TACACSG_authenticate_user: no user found ERROR Software state machine error. N/A TACACSG_authenticate_user: session not finished ERROR Software state machine error. N/A TACACSG_authorize_user: session not finished ERROR Software state machine error. N/A TACACSG_authorize_user: user not found ERROR Software state machine error.
218
SMP error messages
N/A TACACSG_conf_message_handler: invalid message type ERROR Invalid configuration message was received by TACACS+ task. N/A TACACSG_create_user: Cannot get user memory ERROR Software error - cannot reserve a buffer memory for user. N/A TACACSG_create_user: failed to add user to hash ERROR Software error - failed to add user info to hash table. N/A TACACSG_delete_user: failed to delete user from hash ERROR Software error - failed to delete user info from hash table. N/A TACACSG_reset_user: user not found ERROR Software state mechine error. N/A TACACSP_set_srv: failed to delete server record from hash ERROR Software error - failed to delete server info from hash table. N/A TACACSP_tcp_create_con: cant get socket ERROR Cannot create socket for authenticating with TACACS+. N/A
T Messages
219
TACACSP_tcp_create_con: failed to set ioctl FIONBIO ERROR Cannot configure socket for authenticating with TACACS+ N/A TACACSP_tcp_create_con: failed to set setsockopt SO_REUSEADDR ERROR Cannot configure socket for authenticating with TACACS+ N/A tacacsStart: failed to init TACACS ERROR Cannot launch TACACS+ application N/A tapiBindPortToDropProfile: Failed, status = <value> ERROR This message is generated when there is a driver programming error. Specifically, an attempt to bind drop the profile to a port failed. Contact the customer service team if the problem persists. tapiCreateTc: Policy Id <value> doesnt exist ERROR This message is generated when there is an application programming error. Specifically, the policy with the specified ID cannot be found. File a bug report. tapiSetDropProfileByClass: Failed, status = <value> ERROR This message is generated when there is a driver programming error. Specifically, an attempt to bind drop the profile to a Tx queue failed. Contact the customer service team if the problem persists. tapiUpdateTc: Policy Id <value> doesnt exist ERROR
220
SMP error messages
Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity
This message is generated when there is an application programming error. Specifically, the policy with the specified ID cannot be found. File a bug report. tcLibInit: failed INFO This message is generated when a policing library initialization fails. Reboot the switch if you want to enable policing. TCP socket to server xyz port xyz, already connected ERROR TCP socket to server xyz port xyz, already connected N/A tdpInit: Cant create MAC Range Filter! ERROR This message is generated when the MAC filter for capturing TDP control packets to the CPU is not created. N/A The card in slot -- is resetting. Try the command later. WARNING This message is generated when a card is in BOOTING state and there is a command for that card. Try the command after the card is online. The username and the password for standard users are set to default value. It is highly recommended you change the password once the switch boots up. ERROR This message is generated when a warning message indicates it is unable to open the engboot file which store the number of SNMP engines booted. N/A This vlan is also the BPDU vlan for stg <id>. Stg <id> cannot have any other vlans at the presence of vlan <id> WARNING
T Messages
221
Description
This message is generated when the VLAN is used to send out tagged BPDUs for an STG. If the VLAN is created for another purpose, no other VLAN can be created here. Remove the VLAN from the other STG. traceDumpBkTr: failed to get CP slot number ERROR This message is generated when the system fails to get the CP slot number when sending trace info from the coprocessor. N/A traceStart: Cannot create CopTraceLockSemId semaphore FATAL This message is generated when the system cannot create the semaphore. Reboot the switch and contact the customer service team if the problem persists. traceStart: malloc failed FATAL This message is generated when the system runs out of memory. Reboot the switch and contact the customer service team if the problem persists. trBmErrorHandler: resetting slot <value> ERROR This message is generated when there are buffer management errors on a given slot and the card is being reset to recover from the error condition. N/A trBmErrorHandler: send reset request to secondary CP ERROR This message is generated when there are buffer management errors on the secondary CPU and a message is being sent asking it to reset itself. N/A trCardSendTraceCmd: malloc of message parameter failed ERROR This message is generated when the system runs out of memory.
222
SMP error messages
Action
Reboot the switch and contact the customer service team if the problem persists. trCardSendTraceCmd: malloc of message parameter failed FATAL This message is generated when the system runs out of memory. Reboot the switch and contact the customer service team if the problem persists. trChMsgProc - invalid appModCmd <value> WARNING This message is generated when an invalid IPC message is received. N/A trChMsgProc - Null message ptr received INFO This message is generated when an invalid IPC message is received. N/A trCopGo: malloc of message parameter failed ERROR This message is generated when the system runs out of memory. Reboot the switch and contact the customer service team if the problem persists. tree depth <value> should not be zero INFO This message is generated when the depth of the RTX tree is not zero. No action required, this scenario is correct . trMsgAlloc failed FATAL This message is generated when the system runs of out memory. Reboot the switch and contact the customer service team if the problem persists. trReportBmErrors: devNum= <value>, errType= <value>, errCause= <value>
Message
T Messages
223
ERROR This message is generated when there are buffer management errors on a given device and the error type is being reported. N/A trReportBmErrors: trMsgAlloc failed ERROR This message is generated when the malloc failed. Reboot the switch and contact the customer service team if the problem persists. trSetCopStatusLed: malloc of message parameter failed ERROR This message is generated when the malloc failed. Reboot the switch and contact the customer service team if the problem persists. trSetHwPartsDevRev: trMsgAlloc failed ERROR This message is generated when the malloc failed. Reboot the switch and contact the customer service team if the problem persists. trTracePrint: malloc failed ERROR This message is generated when the system runs out of memory. Reboot the switch and contact the customer service team if the problem persists. trTraceStart: malloc failed ERROR This message is generated when the trTraceStart: malloc failed. Reboot the switch and contact the customer service team if the problem persists. trXbarUpdateMsgSend: failed to send msg INFO
Message Severity
224
SMP error messages
Description Action Message Severity Description Action Message Severity Description Action
This message is generated when the system fails to send a message to the I/O cards about crossbar insertion removal. Re-insert or replace the card. trXbarUpdateMsgSend: malloc of message parameter failed FATAL This message is generated when the system fails to send a message to the I/O cards about crossbar insertion/removal. Re-insert or replace the card. trXbarUpdateMsgSend: msg is null FATAL This message is generated when the system fails to send a message to the I/O cards about crossbar insertion/removal. Re-insert or replace the card.
U Messages
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Unable to Allocate memory for log filter entry INFO This message is generated when the system is unable to allocate memory for the log filter entry. N/A Unable to Allocate memory for log filter string INFO This message is generated when the system is unable to allocate memory for the log filter string. N/A unable to create file: <filename> WARNING This message is generated when the system is unable to open the engboot file which stores the number of the booted SNMP engine. N/A unable to create profile semaphore ERROR
U Messages
225
Description Action
This message is generated when the system is unable to create binary semaphore. Reboot the switch and contact the customer service team if the problem persists.
Unable to find vlan rec for IfIndex n ERROR This message is generated when a software error occurs. Contact the customer support team if the problem persists. unable to get the IpRec for Addr <ipaddr> ERROR This message is generated if IP interface cannot be obtained from the IP address. Contact customer support for further troubleshooting. Unable to restore port -- to Vlan -ERROR The system encountered an error while moving the 802.1X controlled port back to its original VLAN after the user session was terminated. When the port received 802.1X authentication, it should have been assigned to the VLAN returned by the RADIUS server. Report the problem. Unable to restore port -- to Vlan -ERROR System encountered error while moving back the 8021x controlled port to its original VLAN after the user session is terminated. [ the port should have been assigned to VLAN returned by RADIUS server when it got 8021x authenticated.] Report the problem Unable to use any TACACS+ server for authentication INFO TACACS+ authentication is enabled, but either no server is configured, or no server accessible, or no server with not valid responses. N/A Unknown Card Type!
Action Message Severity Description Action Message
226
SMP error messages
INFO This message is generated when the card type information is not available. Re-insert or replace the card. Unknown code in request pkt<num> ERROR This message is generated when there is an internal mismatch in the software for the RADIUS packet code. If the problem persists, contact customer service.
unknown IP RSMLT node for IfIndex <Interface ID> Error This message indicates that the system received an invalid parameter when RSMLT attempted to transmit a gratuitous ARP. You can continue to operate the chassis, but note the scenario that results in the occurrence of this error message. Record the error message and configuration, and contact the Nortel Technical Solutions Center for assistance. Unknown message type <value> Error An unknown type of igmp message is received. N/A unknown speed <value> ERROR This message is generated when the gprtGetPortSpeed returns an unknown port speed. Contact the customer service team if the problem persists.
Unrecognized message type <value> Warning An unknown type of igmp message is received when an igmp event is handled. N/A UnSupported card type in Slot <value>! INFO This message is generated when an unsupported card is inserted in the system. Remove card.
U Messages
227
Unsupported TACACS+ REPLY status (xyz) received: xyz ERROR Unsupported packet was received from specific server N/A Unsupported TACACS+ RESPONSE status (xyz) received xyz ERROR Unsupported packet was received from specific server N/A Updating default vlan for port <Slot/Port> failed Error This message is generated when an attempt to update a default vlan for a port has failed. Disable NSNA, administratively shut the port down and re-enable NSNA. Updating default vlan for port <> failed Fault This message indicates that the system cannot reset the default VLAN ID for the specified NSNA port, when you change the NSNA port VLAN membership. Disable and enable the NSNA port. UpdateSumm: gUpdateYieldSh = <address> sfwd = <address> ERROR This message is generated when a summary lsa is forwarded during a summary lsa update, resulting in the UpdateYield not being equal to sfwd. No action required. User -- on Port -- is authenticated INFO This message is generated when a user has successfully logged in to an 802.1X controlled port. No action necessary. User -- on Port -- is authenticated INFO
228
SMP error messages
This message is generated when a user successfully logs in to a 8021x controlled port. No action necessary User -- on Port -- is disconnected INFO This message indicates that an 802.1X authorized user logged out. No action necessary. User -- on Port -- is disconnected INFO This message is generated when an 8021x authorized user logs out. No action necessary user <UserName> connected from <IP Addr> via rlogin INFO This message is logged when a user rlogins to the switch. N/A user <UserName> connected from <IP Addr> via telnet INFO This message is logged when a user telnets to the switch. N/A user <user-name> logged out from console port INFO This message is generated when the user logs out from a console connection. N/A user connected via console port INFO This message is logged when a user connects to the switch through the console port. N/A user connected via modem port
V Messages
229
INFO This message is logged when a user connects to the switch through the modem port. N/A UTAL_LookupProtocolId: gbrgClassperPortSearchProtocolEntry failed ERROR This message is generated when the system fails to find a Protocol ID record. N/A
V Messages
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description VCT Task Creation Failed ERROR This message is generated when creating the VCT task failed. N/A VCT Task Semaphore Creation Failed ERROR This message is generated when creating the VCT semaphore failed. N/A VCT Test DONE. Get the VCT results for port <portnum> INFO This message is generated when the process of obtaining the VCT results finished. Get the results. VCT Test FAILED for Port = <portnum> ERROR This message is generated when the VCT test failed. Perform the test again. verify_ospf_packet: auth failure ipa ERROR This message indicates that the IP address is not authenticated because the key in the packet does not match the key in the OSPF area.
230
SMP error messages
Enter a valid key for authentication. VLAN -- returned by RADIUS server for port -- does not exist ERROR This message indicates that the VLAN returned by the RADIUS server for the 802.1X authorized port does not exist on the system. Do one of the following: create the VLAN returned by the RADIUS server or configure the RADIUS server to return a valid VLAN. VLAN -- returned by RADIUS server for port -- does not exist ERROR This message is generated when the VLAN returned by RADIUS server for 8021x authorized port does not exist on the system. Either create the VLAN returned by RADIUS server or configure RADIUS server to return a valid VLAN Vlan id -- returned from RADIUS server cannot be used for port -- belonging to MLT INFO This message indicates that the system tried to move the 802.1X authorized port to the VLAN returned by the RADIUS server and the port belongs to an MLT. Remove the port from MLT. Vlan id -- returned from RADIUS server cannot be used for port -- belonging to MLT INFO This messages is generated when the system tries to move the 8021x authorized port to VLAN returned by RADIUS server and the port belongs to a MLT Remove the port from MLT Vlan id -- returned from RADIUS server cannot be used for tagged port -INFO This message indicates that the system tried to move the 802.1X authorized port to the VLAN returned by the RADIUS server and the port is tagged. Untag the port. Vlan id -- returned from RADIUS server cannot be used for tagged port --
Action Message Severity Description Action Message
V Messages
231
Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description Action Message
INFO This messages is generated when the system tries to move the 8021x authorized port to VLAN returned by RADIUS server and the port is tagged. Make the port untagged Vlan Table synch consistency check failed, expected_size:<value>, given_size:<value>\n,868, sizeof(tVlanTblSyncEntry) INFO This message is generated when the consistency check failed. Received message size from the Master is different than expected. N/A Vlan Table synch size from master CPU incorrect, expected_size:<size>, given_size: <given size> ERROR This message is generated when the statistics received from the master are different than expected. N/A vlanCreateVirtualLan: Out of memory! for Vid <value> NumVlans <value>,VlanId,NumVlans ERROR This message is generated when the system is out of memory. Free some space. vlanCreateVirtualLan: VLAN Table was damaged!Index <value> vid <value> NumVlans <value>, Index, VlanId, NumVlans ERROR This message is generated when there is no more Free entries in the VLAN table. Suggests memory corruption. vlanDelMac: malloc failed ERROR This message is generated when the system is out of memory. Free up some space. vlanDelMac: msgQSend failed
232
SMP error messages
ERROR This message is generated when the VLANMacMsgQid is full. Check to see if messages are dequeued. vlanDelMacTask: unknown type <value>, masg.Type ERROR This message is generated when the VLAN Del Mac Task has received an unknown message type. Invalid message is received by vlanMacMsgQid. vlanEnableIgmpSnooping: gegrSetVlanUnRegMcFilterCmd FAILED!! FATAL This message is generated when the vlanUnregisteredMulticastCommand in the hardware failed. N/A vlanFdbUpdMsg: malloc failed! ERROR This message is generated when the system is out of memory. Free up some space. vlanGo: NPAL_DisableAutoAging return fail! ERROR This message is generated when the disabling of auto aging in the hardware failed. N/A vlanGo: NPAL_SetUnregisterMacFilter FAILED!! ERROR This message is generated when the unregistered MAC filter command in the hardware failed. N/A vlanMacInit: Cant create mutex semaphore! FATAL This message is generated when semaphore creation failed. N/A
V Messages
233
vlanMacInit: indexAlloc failed for pRarMacAddressIndex! ERROR This message is generated when the system is out of memory. Free up some space. vlanMacInit: indexAlloc failed for pRarStaticMacAddressIndex! ERROR This message is generated when the system is out of memory. Free up memory. vlanMacInit: msgQCreate failed FATAL This message is generated when there is no memory for message Q. N/A vlanMacInit: taskSpawn failed FATAL This message is generated when the taskSpawn fails. N/A vlanProcessFrame: cannot send frame ERROR Control packet could not be sent out. N/A vlanProcessFrame: RSMLT Holdup Forward to Forward state is failed on vlan <VLAN ID>, mac <MAC Address> Error This message is generated when RSMLT fails to change from hold forwarding state to forwarding state. Disable and enable RSMLT on the IST peer to restore RSMLT functionality. Contact customer service and have the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. vlanRarAddMltToMgid: failed for MltId <value>\n, MltId ERROR
Message Severity
234
SMP error messages
This message is generated when adding an MLT port to vidx fails. N/A vlanStart: Fail to initialize Mac Index List! FATAL This message is generated when the vlanMacInit fails. N/A vlanSyncCallback: unsupported version <value> ERROR This message is generated if an unsupported version of the static route is encountered during sync call back. This is an internal error. Contact customer support for further troubleshooting. vrrpAssoIpAddrTblGet invalid get option ERROR This message is generated when the VRRP Get request for an IP address returns an invalid value. Contact customer service with the following information available: trace log 15 3, any memory dumps, switch configuration, and network topology for further analysis. vrrpAssoIpAddrTblGet invalid get option ___ Error This message is generated when the SNMP get option cannot be recognized. Contact customer service and have the following information available for further analysis:

vrrpOperTblGet invalid get option ___ Error This message is generated when wrong option has been encountered.
W Messages
235
Action

vrrpRouterStatsTblGet invalid get option ___ Error This message is generated when wrong option has been encountered. Contact customer service with the following information available for further analysis:
W Messages
Message Severity Description Action Message Severity Description Action Message Severity Description Action Message Severity Description WDT TASK: Warning System DRAM usage at <#> percent WARNING This message is generated when the system DRAM usage reaches a threshold of 95%. N/A write failed to location 0x40018000 on dev <value> WARNING This message is generated when the write PP register fails. Contact the customer service team if the problem persists. write failed to location 0x40018004 on dev <value> WARNING This message is generated when the write PP register fails. Contact the customer service team if the problem persists. write failed to location 0x40018008 on dev <value> WARNING This message is generated when the write PP register fails.
236
SMP error messages
Contact the customer service team if the problem persists. write failed to location 0x4001800c on dev <value> WARNING This message is generated when the write PP register fails. Contact the customer service team if the problem persists. Wrong order in received TCP chunks from xyz TACACS+ server ERROR Bad packet was received from specific TACACS+ server. N/A Wrong logic: Couldnt find the static route that has been successfully added to static route linklist. Fault This message indicates that the system failed to add a route, which causes system instability. Reboot the switch and contact customer service with the following information available: system logs including any memory dumps, switch configuration, and network topology for further analysis. Wrong state in rcTacacsAuthenticate ERROR Software state machine error. N/A Wrong VRRP adver msg received with auth-type %d for Vrid %d Virtual IP %d.%d.%d.%d WARNING This message is generated when an invalid VRRP auth-type is included in a VRRP packet received in an advertisement from another switch. Locate the other switch, correct its VRRP auth-type configuration if required, and disable and enable the switch. If the error message continues to appear, disable the VRRP instance on that switch. Wrong VRRP adver msg received with auth-type ___ for Vrid ___ Virtual IP ___ Error
Message Severity
W Messages
237
This message is generated when a Vrrp message is received with an invalid Authentication type. Check for a chassis malfunction or a malicious attacker in the subnet. Wrong VRRP adver msg received with unknown auth-type ___ for Vrid ___ Virtual IP ___ Error This message is generated when a Vrrp message is received with an unsupported Authentication type. Check for a different version of VRRP in the subnet.
238
SMP error messages
239
Index
240
Nortel Ethernet Routing Switch 8300
Logs Reference
Copyright 2008, Nortel Networks All Rights Reserved. Printed in Canada and the United States of America Release: 4.1 Publication: NN46200-706 Document status: Standard Document revision: 01.01 Document release date: 16 June 2008 To provide feedback or to report a problem in this document, go to www.nortel.com/documentfeedback. www.nortel.com LEGAL NOTICE While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing, NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESSED OR IMPLIED. The information and/or products described in this document are subject to change without notice. Nortel, the Nortel logo, the Globemark, and Passport are trademarks of Nortel Networks. All other trademarks are the property of their respective owners.
ATTENTION For information about the software license, read "Software license" in this guide.

NN46200-706 01.01 FAULT Logs Reference

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

NN46200-706 01.01 FAULT Logs Reference

Загружено:

Авторское право:

Доступные форматы

Nortel Ethernet Routing Switch 8300

Introduction SMP error messages

Nortel Networks Inc. software license agreement

1. If Customer is the United States Government, the following paragraph

Nortel Networks Inc. software license agreement

2. Customer may terminate the license at any time. Nortel Networks

3. Customer is responsible for payment of any taxes, including personal

6. This License Agreement is governed by the laws of the country in

New in this release

Features (page 9) Other changes (page 9)

There are no new features in the document for this release.

New system messages (page 9)

New system messages

10 New in this release

SMP error messages

Message Severity Description Action

14 SMP error messages

16 SMP error messages

Message Severity Description

Action Message Severity Description

Message Severity Description Action

Message Severity Description

Action Message Severity Description

18 SMP error messages

Severity Description Action Message Severity Description Action

Message Severity Description Action

Message Severity Description Action

Message Severity Description

Message Severity Description Action

20 SMP error messages

Message Severity Description Action

Message Severity Description Action

Message Severity Description Action

Message Severity Description

Severity Description Action

Message Severity Description Action

Message Severity Description

22 SMP error messages

Message Severity Description Action Message Severity Description Action

Message Severity Description Action

Message Severity Description Action

Message Severity Description Action

Message Severity Description

24 SMP error messages

Message Severity Description Action

Message Severity Description Action Message Severity Description

Message Severity Description Action Message Severity

26 SMP error messages

28 SMP error messages

Message Severity Description Action Message Severity Description Action

Severity Description Action

Message Severity Description Action

Message Severity Description Action Message Severity Description Action

Message Severity Description Action

Copyright 2008, Nortel Networks

30 SMP error messages

Severity Description Action

Message Severity Description Action

Message Severity Description Action

Message Severity Description Action

Message Severity Description Action

Message Severity Description Action

Message Severity Description Action