Nortel 8300 Reference Manual
Nortel 8300 Reference Manual

Nortel 8300 Reference Manual

Ethernet routing switch system messaging platform
Hide thumbs Also See for 8300:

Advertisement

System Messaging Platform
Reference Guide
Ethernet Routing Switch 8300
Software Release 2.2
*316806-C*
Part No. 316806-C
June 2005
4655 Great America Parkway
Santa Clara, CA 95054

Advertisement

Table of Contents
loading

Summary of Contents for Nortel 8300

  • Page 1 Part No. 316806-C June 2005 4655 Great America Parkway Santa Clara, CA 95054 System Messaging Platform Reference Guide Ethernet Routing Switch 8300 Software Release 2.2 *316806-C*...
  • Page 2: Restricted Rights Legend

    In the interest of improving internal design, operational function, and/or reliability, Nortel Networks Inc. reserves the right to make changes to the products described in this document without notice. Nortel Networks Inc. does not assume any liability that may occur due to the use or application of the product(s) or circuit layout(s) described herein.
  • Page 3 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.
  • Page 4 12.212 (for non-DoD entities) and 48 C.F.R. 227.7202 (for DoD entities). 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.
  • Page 5 Contents Preface ............9 Before you begin .
  • Page 6 6 Contents Chapter 3: Setting up SMP logs using the NNCLI ....33 Displaying logs by file name, category, severity, and CPU ..... . 33 Defining transfer criteria for the log file .
  • Page 7 Tables Table 1 NNCLI command modes ........12 Table 2 SMP categories .
  • Page 8 8 Tables 316806-C...
  • Page 9: Preface

    Extensible Authentication Protocol over LAN (EAPoL), Simple Network Management Protocol, Version 3 (SNMP3), and Secure Shell (SSH). The Ethernet Routing Switch 8300 provides quality of service (QoS) for a high number of attached devices and supports future network requirements for QoS for critical applications, such as Voice over IP (VoIP).
  • Page 10: Before You Begin

    About the NNCLI This section describes the Nortel Networks Command Line Interface (NNCLI) command modes you use to configure the Ethernet Routing Switch 8300 and the commands you use to access the NNCLI. You can access the NNCLI using the following methods: •...
  • Page 11 Preface 11 The command modes are as follows: • User EXEC mode This is the initial mode of access. By default, the User Access Verification Password for this mode is empty, and password checking is disabled. The password can be changed (and password checking enabled) by the system administrator in Global configuration mode.
  • Page 12: Accessing The Nncli

    Accessing the NNCLI When you first power up the Ethernet Routing Switch 8300, the default interface is the Ethernet Routing Switch 8300 CLI. To switch from the CLI to the NNCLI, you must change the NNCLI boot flag to and save the boot configuration...
  • Page 13: Returning To The Cli

    • access Global configuration mode Login: xxxxx Password: xxxxx Passport-8310:5> enable Password: nortel Passport-8310:5# configure terminal Passport-8310:5(config)# Returning to the CLI Note: The config.cfg file for the CLI and the config.cfg file for the NNCLI are not compatible. If you decide to change the CLI mode to NNCLI, or the reverse, you must use the config.cfg file for the selected...
  • Page 14: Text Conventions

    Preface Text conventions This guide uses the following text conventions: angle brackets (< >) Indicate that you choose the text to enter based on the description inside the brackets. Do not type the brackets when entering the command. Example: If the command syntax is , you enter ping <ip_address>...
  • Page 15: Hard-Copy Technical Manuals

    Hard-copy technical manuals You can download current versions of technical documentation for your Ethernet Routing Switch 8300 from the Nortel customer support web site at www.nortel.com/support. If, for any reason, you cannot find a specific document, use the Search function: Click Search at the top right-hand side of the web page.
  • Page 16 URL to download a free copy of the Adobe Acrobat Reader. How to get help If you purchased a service contract for your Nortel product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance.
  • Page 17: Chapter 1: System Messaging Platform

    Log file modifications Transfer of a log file to remote machine Log message format The log messages for the Ethernet Routing Switch 8300 have a standardized format. Message tags All system messages are tagged with the following, as shown in “Message...
  • Page 18: Message Format

    18 Chapter 1 System Messaging Platform Message format The SMP message format is as follows: <Module ID><Task><NP info><CPU slot><Time stamp><Category><Severity> Example VLAN Task=tTrapd No-interface CPU5 [9/14/03 15:46:26] VLAN WARNING Link Down Note: The NP information, shown in italics, is encrypted before being written into the Syslog file.
  • Page 19: Crash Dump Information

    Both hardware and software messages are captured in the same, single log file. This log file is simultaneously saved to DRAM and the <value> (if available). Note: Nortel strongly recommends logging on to a PCMCIA and keeping a PCMCIA in each CPU at all times. The DRAM has limited memory allocated to SMP.
  • Page 20: Log File Naming Convention

    Transfer of a log file to remote machine The system logs contain important information for debugging and maintaining your Ethernet Routing Switch 8300. When logging to the PCMCIA, the log file is automatically transferred to a remote host when the size parameters you specified are met.
  • Page 21: Table 5 User-Configurable Parameters For Triggering Log File Transfers

    • File name – The name of the file that is to be stored in the remote host Note: Nortel recommends that you not set this option since it causes the syslog file to be overwritten on the remote server.
  • Page 22: Transfer Criteria

    SMP transfers the log and begins logging to DRAM until there is enough free space on the PCMCIA. Example 1 The Ethernet Routing Switch 8300 has been in operation for some time with an 8 MB (8192 KB) PCMCIA installed. 316806-C...
  • Page 23 SMP is so much greater than the parameter. maxsize Example 2 The Ethernet Routing Switch 8300 has been in operation for some time with an 8 MB (8192 KB) PCMCIA installed. The configured parameters are as follows: • minsize: 100 KB •...
  • Page 24 , whichever is reached first. maxoccuptPercentage Example 3 The Ethernet Routing Switch 8300 has been in operation for some time with an 8 MB (8192 KB) PCMCIA installed. The configured parameters are as follows: • minsize: 500 KB •...
  • Page 25 Chapter 1 System Messaging Platform 25 The allowed log file size is below the set parameter for the log. In this minsize scenario, the system transfers the log when it checks the available space on the PCMCIA before writing the next log message. After the transfer, there are only 410 KB free on the PCMCIA.
  • Page 26 26 Chapter 1 System Messaging Platform 316806-C...
  • Page 27: Chapter 2: Setting Up Smp Logs Using The Cli

    Chapter 2 Setting up SMP logs using the CLI This chapter includes the following topics that describe how to set up SMP logs using CLI: Topic Page Displaying logs by file name, category, severity, and CPU Defining transfer criteria for the log file Configuring the remote host address and file name for log transfer Logging system messages to the PCMCIA...
  • Page 28 28 Chapter 2 Setting up SMP logs using the CLI Table 6 SMP log information (Sheet 2 of 2) show log file followed by: Filters and lists the logs (individually or combined) [category <value>] according to category, severity, and the CPU that [severity <value>] generated it.
  • Page 29: Defining Transfer Criteria For The Log File

    Chapter 2 Setting up SMP logs using the CLI 29 Defining transfer criteria for the log file To define transfer criteria for log transfer, use the following CLI command: config bootconfig logfile <minsize> <maxsize> <maxcopyPercentage> Table 7 Transfer criteria for log transfer config bootconfig logfile followed by: Minimum size of the log file in KB.
  • Page 30: Configuring The Remote Host Address And File Name For Log Transfer

    If this option is set, the previously transferred log file is overwritten on the remote server. Note: Nortel recommends that you not set this option. info Shows the configured IP address and the file name for the remote host.
  • Page 31: Logging System Messages To The Pcmcia

    Chapter 2 Setting up SMP logs using the CLI 31 Configuration example This configuration example uses the commands in Table 8, “Configure the remote host address and file name for log transfer,” on page 30 to add an IP address for a new host.
  • Page 32 32 Chapter 2 Setting up SMP logs using the CLI The following message is returned: Logging to PCMCIA STOPPED Warning: Before removing the PCMCIA from your master CPU, you must use the command to stop config log logToPCCard false logging. Failure to do so can corrupt the file system on the PCMCIA and cause your log file to be permanently lost.
  • Page 33: Chapter 3: Setting Up Smp Logs Using The Nncli

    Chapter 3 Setting up SMP logs using the NNCLI This chapter includes the following topics that describe how to set up SMP logs using the NNCLI: Topic Page Displaying logs by file name, category, severity, and CPU Defining transfer criteria for the log file Configuring the remote host address and file name for log transfer Logging system messages to the PCMCIA Ending the logging of system messages on the PCMCIA...
  • Page 34 34 Chapter 3 Setting up SMP logs using the NNCLI Table 9 Display log information by file name, category, severity and CPU (Sheet 2 of 2) show logging file followed by: Filters and lists the logs (individually or combined) [category <value>] according to category, severity, and the CPU that [severity <value>] generated it.
  • Page 35: Defining Transfer Criteria For The Log File

    Chapter 3 Setting up SMP logs using the NNCLI 35 Defining transfer criteria for the log file To define transfer criteria for log transfer, use the following NNCLI command from the Global Config mode: bootconfig logfile <minsize>-<maxsize> <maxcopyPercentage> Table 10 Define transfer criteria for log transfer bootconfig logfile followed by:...
  • Page 36: Configuring The Remote Host Address And File Name For Log Transfer

    If this option is set, the previously transferred log file is overwritten on the remote server. Note: Nortel recommends that you do not set this option. Removes the IP address configured by the user. It is remove-IP then set to the default (0.0.0.0).
  • Page 37: Logging System Messages To The Pcmcia

    Chapter 3 Setting up SMP logs using the NNCLI 37 If the IP address you are attempting to configure is not reachable, the following message is displayed: Destination IP address not reachable !!! Could not configure. Logging system messages to the PCMCIA To begin logging system messages on the PCMCIA, use the following NNCLI command from the Global Config mode: logging logToPCMCIA...
  • Page 38 38 Chapter 3 Setting up SMP logs using the NNCLI 316806-C...
  • Page 39: Chapter 4: Smp Log Error Messages

    Chapter 4 SMP log 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 <value> card in slot <value> not communicating Severity WARNING Description This message specifies that a card failed because it has no communication with the master CPU.
  • Page 40: A Messages

    40 Chapter 4 SMP log error messages A Messages Message AAAG_init: failed to init user hash Severity ERROR Description Cannot allocate memory for TACACS+ client operation Synopsis Serious problem. TACACS+ will never be operable. Action Message AAAG_init: failed to spawn tTacacsTask Severity ERROR Description...
  • Page 41 Chapter 4 SMP log error messages 41 Message AAAP_inner_authenticate_user: user status - result given Severity ERROR Description Software state machine error. Synopsis A software error occurred, TACACS+ client should be operable. If proceeds, contact technical support. Action Message AAAP_inner_create_new_user: failed to add to hash Severity ERROR Description...
  • Page 42 42 Chapter 4 SMP log error messages Message AAAP_inner_delete_user: wrong user status = xyz Severity ERROR Description Software state machine error. Synopsis A software error occurred, TACACS+ client should be operable. If proceeds, contact technical support. Action Message AAAP_message_handler: unknown message Severity ERROR Description...
  • Page 43 Chapter 4 SMP log error messages 43 Message AAAP_tacacs_authorization_indication: unknown RESPONSE status = xyz Severity ERROR Description Unsupported packet was received from specific server Synopsis An unsupported packet was received for server. Cannot use this specific server for authentication purposes. Action Message AAAP_tacacs_authorization_indication: wrong tacacs status...
  • Page 44 44 Chapter 4 SMP log error messages Message AAAP_tacacs_task_message_handler: mutex id null Severity ERROR Description Error in communications with TACACS+ task Synopsis If proceeds, must restart switch, if need to use TACACS+. Action Message AceEntry Mode <value> is not recognizable Severity ERROR Description...
  • Page 45 Chapter 4 SMP log error messages 45 Message AcgId <value> ProfileId <value> cannot remove profile <value> Severity ERROR Description 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.
  • Page 46 46 Chapter 4 SMP log error messages Message aclAclTblAdd() malloc() SIZE <value> FAIL Severity ERROR Description This message indicates the system is low on resources. Synopsis Action Reduce the running configuration or reboot. Message aclActTblAdd() malloc() SIZE <value> FAIL Severity ERROR Description This message indicates the system is low on resources.
  • Page 47 Chapter 4 SMP log error messages 47 Message aclHwBuildPceParamBlock(): AclId <value> ProfileId <value> NOT FOUND <value> Severity ERROR Description The template is expected in the hardware, but is not found. Synopsis Action Try removing or enabling filters on the port. Try to delete or create for the ACG from the port.
  • Page 48 48 Chapter 4 SMP log error messages Message aclHwBuildProfileParamBlock(): ActEntry's AclType <value> is NOT SUPPORTED Severity WARNING Description 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. Synopsis Action Try removing or enabling filters on the port.
  • Page 49 Chapter 4 SMP log error messages 49 Message aclHwCreateAction: Policy Id <value> doesn't exist Severity ERROR Description 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. Synopsis Action Ensure that the policy exists with the specified policy ID.
  • Page 50 The map table for the template in the application and hardware is incorrect. Synopsis Action Try a reboot. Message addMrdiscNeighbor: cant allocate memory Severity ERROR Description MRDisc is not supported in the Passport 8300, so this errorshould not occur. Synopsis Action 316806-C...
  • Page 51 Chapter 4 SMP log error messages 51 Message AllocateCLIContext malloc failed Severity ERROR Description This message indicates the system is unable to allocate memory for the NNCLI context. Synopsis Action Message Allow Mac Address table full. Can't add more! Severity ERROR Description This message is generated when the learned MAC entries have exceeded the...
  • Page 52 52 Chapter 4 SMP log error messages Message APP_LOCK failed Severity ERROR Description This message indicates that the system cannot get the allowed MAC semaphore. Synopsis Action Message arpadd: move unresolved entry, but usrdata is NULL Severity ERROR Description This message is generated when resolving an ARP if the system finds a corresponding unresolved ARP entry.
  • Page 53: B Messages

    Message avpair_get Unknown attribute x Severity ERROR Description This message indicates that a RADIUS attribute unknown to the Passport 8300 is being looked-up. Synopsis An unknown attribute exists in the received RADIUS packet or sent packet. Action Verify that the sent and received RADIUS packets contain known attributes.
  • Page 54 54 Chapter 4 SMP log error messages Message Bkend state of Port -- - Recd accept from server Severity INFO Description This message is generated when 8021x Backend Authentication State Machine receives a Access-Accept message from RADIUS server. Synopsis RADIUS server sent Access-Accept message for the user on specified port. Action No action necessary Message...
  • Page 55 Chapter 4 SMP log error messages 55 Message Bkend state of Port -- - Recd Respose from supplicant Severity INFO Description This message is generated when 8021x Backend Authentication State Machine receives a response from supplicant. Synopsis Supplicant sent the EAP Response packet for the user on specified port. Action No action necessary Message...
  • Page 56: C Messages

    56 Chapter 4 SMP log error messages Message bootpSyncCallback: Invalid msgType <type> Severity ERROR Description This message specifies that an invalid argument exists for the bootp module sync callback function. Synopsis Action Message bootpSyncCallback: unsupported version <ver> Severity ERROR Description There is a synchronization issue between two CPUs, perhaps a bootp module version mismatch Synopsis...
  • Page 57 Chapter 4 SMP log error messages 57 Message Cannot add MAC range filter for EAP! Severity ERROR Description This message indicates the MAC filter for capturing EAP packets to the CPU is not created. Synopsis Action Message cannot allocate announce gt nexthop tbl link list object Severity ERROR Description...
  • Page 58 58 Chapter 4 SMP log error messages Message cannot allocate group index object Severity FATAL Description This message is generated while initializing the IGMP group list if the DRAM memory is exhausted. Synopsis DRAM memory unavailable for group link list. Action Increase DRAM memory size.
  • Page 59 Chapter 4 SMP log error messages 59 Message cannot allocate memory for tIGMP_QUERIER Severity FATAL Description This message indicates there is a memory allocation failure. Synopsis Action Message cannot allocate rcip_route_index object Severity FATAL Description This message is generated when the system is unable to allocate memory for the RCIP object.
  • Page 60 60 Chapter 4 SMP log error messages Message Cannot configure card. Please remove and insert again Severity ERROR Description This message is generated to specify that card should be removed and then re-inserted. Synopsis Cannot configure card. Action Contact Customer Support for further troubleshooting. Message Cannot create logSendFatalLogTask task Severity...
  • Page 61 Chapter 4 SMP log error messages 61 Message Cannot unbind vlanId <value> from stg <value>, err=<value>! Severity ERROR Description This message indicates the unbinding of STG from the BPDU VLAN failed in hardware during STG deletion. Synopsis Action Reboot the switch and contact the customer support team if the problem persists. Message cannot update nexthop tbl entry Severity...
  • Page 62 Severity INFO Description 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. Synopsis Action Please verify that the chassis is either a Passport 8600 or 8300.
  • Page 63 Chapter 4 SMP log error messages 63 Message chCardIn: Can't read SEEPROM on slot=<value>: <value> <value> Severity INFO Description This message indicates that the SEEPROM cannot be read for the card. Synopsis Action Re-insert or replace the card. Message chCOPListenTimerSet: global set, still setting <value> Severity INFO Description...
  • Page 64 64 Chapter 4 SMP log error messages Message Closed telnet connection from <ip-address> user <user-name> Severity INFO Description This message is generated when a telnet connection to the switch terminates. Synopsis Action Message Connection lost to slot <value> ... Severity ERROR Description IPC connection between the CP card and a given I/O slot is lost.
  • Page 65 Contact the customer support team if the problem persists. Message Could not create xlrclip for nncli Severity ERROR Description This message specifies the Passport 8300 is unable to create xlrclip for the NNCLI. Synopsis Action Reboot the switch and contact customer support if the problem persists. Message Could not delete software mirroring Entry <id>...
  • Page 66 66 Chapter 4 SMP log error messages Message Could not delete the hw mirroring Entry <id> Severity WARNING Description This message specifies that a mirroring hardware table entry cannot be deleted because of an incorrect ID or the lack of an OS resource. Synopsis Action Verify the correct command parameters in the documentation and try again.
  • Page 67 Chapter 4 SMP log error messages 67 Message Could not start portMgr Task , <value>, Severity FATAL Description This message indicates the portMgr task could not be created. Synopsis Action Reboot the switch and contact the customer support team if the problem persists. Message cpp2LargeFbufInit: Can't allocate memory! Severity...
  • Page 68 68 Chapter 4 SMP log error messages Message cppAddDefaultRouteHook: routeAdd failed! Severity ERROR Description This message is generated when registration of the CP interface with vxWorks fails. Any communication with the vxWorks IP stack also fails. Synopsis Action Reboot the switch and contact the customer service team if the problem persists. Message cppAllocFBufs: malllc(<value>) failed Severity...
  • Page 69 Chapter 4 SMP log error messages 69 Message cppInitFBufPool: Can't allocate memory! Severity FATAL 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.
  • Page 70 70 Chapter 4 SMP log error messages Message cppProcAuMsgBody: Vlan for MLT not found! Mac <mac> VlanId <id> MltId <mltid> Severity WARNING Description 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.
  • Page 71 Chapter 4 SMP log error messages 71 Message cppPutFBuf: netFreeRxGtbuf <value> failed!! Severity FATAL Description 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.
  • Page 72 72 Chapter 4 SMP log error messages Message cppStart: Can't create socket tx task Severity INFO Description 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.
  • Page 73: D Messages

    Chapter 4 SMP log error messages 73 Message cppTxFrameBody: could not free netFreeTxGtBuf Severity ERROR Description This message is generated when some type of pointer corruption has occurred, or if somewhere else the gtBuf has incorrectly been released (freed). Synopsis Action Message cppTxFrameBody: No room for the TxPH! (off=<value>)
  • Page 74 74 Chapter 4 SMP log error messages Message Deny/Permit setting update failed while updating next hop for Acl <value> Ace <value> with status Severity ERROR Description 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.
  • Page 75 Chapter 4 SMP log error messages 75 Message diagUpdatePortMirrorStructures_8300: Invalid Mode ID <value> Severity WARNING Description This message indicates that an incorrect mirroring mode parameter exists. Synopsis Action Verify the correct command parameters in the documentation and try again. Message DLD file <file>...
  • Page 76: E Messages

    76 Chapter 4 SMP log error messages E Messages Message EapApplyVlanAndPri: unable to add port -- to vlan -- Severity ERROR Description 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.
  • Page 77 Chapter 4 SMP log error messages 77 Message eapInitTx: malloc failed for buf Severity ERROR Description This message is generated when the system is out of memory while executing the software. Synopsis System is out of memory Action Report the problem Message eaplnitTx: malloc failed for buf Severity...
  • Page 78 78 Chapter 4 SMP log error messages Message EapTransmitEapolPkt: Can't send frame! Severity ERROR Description This message is generated when system encounters unexpected error while sending out an EAPOL frame out of a port. Synopsis System error Action Report the problem Message Enable Mirroring FAILED for Entry <id>...
  • Page 79 Chapter 4 SMP log error messages 79 Message Error - Fail to delete STG Severity ERROR Description This message is generated when the deletion of an STG fails. Synopsis Cannot delete an STG. Action Contact customer support for further troubleshooting. Message Error - Fail to delete VLAN Severity...
  • Page 80 80 Chapter 4 SMP log error messages Message error in reading data from the PCMCIA Severity INFO Description This message is generated when PCAP tries to do autosave to PCMCIA and it cannot read the PCMCIA. Synopsis Action Insert a PCMCIA card in the switch or set the autosave path to network. Message Error: ActId = <value>...
  • Page 81: F Messages

    Chapter 4 SMP log error messages 81 F Messages Message fail config STG for mgmt VLAN Severity ERROR Description This message is generated when an attempt to create an STG for the specified VLAN fails. Synopsis Cannot create STG. Action Contact customer support for further troubleshooting.
  • Page 82 82 Chapter 4 SMP log error messages Message Failed to create semaphore for authenticating with TACACS+ protocol Severity ERROR Description Cannot create a semaphore for sending messages to TACACS+ task. System resources might be low. Synopsis If this error proceeds, need to restart the switch. Action Message Failed to create semaphore for rcTacacsGlobalGrpConsistencyCheck...
  • Page 83 Chapter 4 SMP log error messages 83 Message Failed to create semaphore for rcTacacsServerTblSet Severity ERROR Description Cannot create a semaphore for sending configuration messages to TACACS+ task. System resources might be low. Synopsis If this error proceeds, need to restart the switch. Action Message Failed to create STG for IMC VLAN...
  • Page 84 84 Chapter 4 SMP log error messages Message FAILED To write mcast table to Xbar on slot <value> Severity ERROR Description This message indicates that the multicast table was not successfully written to the crossbar on the standby CPU. Synopsis Action Re-insert or replace the card.
  • Page 85 Chapter 4 SMP log error messages 85 Message Finished insertion for slot <value> Severity INFO Description This message indicates that the insertion process has finished. Synopsis Action Message Finished removal for slot <value> Severity WARNING Description This message indicates that the removal process has finished. Synopsis Action Message...
  • Page 86: G Messages

    86 Chapter 4 SMP log error messages Message free space <value> bytes is less than minimum <value> bytes Severity INFO Description This message indicates that the free space in PCMCIA is less than the configured value for SMP. Thus, logging to PCMCIA has stopped. Synopsis Action Free up some space in PCMCIA by moving or deleting files from PCMCIA.
  • Page 87 Chapter 4 SMP log error messages 87 Message gcntGetEgressCntrs: Failed, status = <value> Severity ERROR Description This message indicates a driver programming error. Specifically, an attempt to get egress counters failed. Synopsis Action Contact the customer support team if the problem persists. Message gcntSetEgressCntrMode: Failed, status = <value>...
  • Page 88 88 Chapter 4 SMP log error messages Message gcosSetMacEntryTcOverrideEnable: Failed, status = <value> Severity ERROR Description This message indicates a driver programming error. Specifically, an attempt to change the mac qos-level override option failed. Synopsis Action Contact the customer support team if the problem persists. Message gcosSetPortDefaultTc: Failed, status = <value>...
  • Page 89 Chapter 4 SMP log error messages 89 Message gen_valpair FATAL out of memory Severity ERROR Description This message indicates that the system is out of memory. Synopsis Insufficient memory. Action If the problem persists, contact customer support. Message gen_valpairs<string> Unknown Type Severity ERROR Description...
  • Page 90 90 Chapter 4 SMP log error messages Message GetDropPrecValueFromTapi: unexpected value Severity ERROR Description This message identifies an application programming error. Specifically, the conformance level is not in range. Synopsis Action Contact the customer support team if the problem persists. Message gprtPortOverrideTcEnable: Failed, status = <value>...
  • Page 91 Chapter 4 SMP log error messages 91 Message gtcmDeleteTcEntry: Failed, status = <value> Severity ERROR Description This message identifies a driver programming error. Specifically, an attempt to delete a policy entry in hardware failed. Synopsis Action Contact the customer support team if the problem persists. Message gtcmGetTrafficMeterCounters: Failed, status = <value>...
  • Page 92 92 Chapter 4 SMP log error messages Message gtcmSetTcEntryFlowAggrCounters FAIL TcId <value> Severity ERROR Description This message indicates that clear statistics/counters failed for the filter. Synopsis Action Try to enable/disable statistics on the filter. Message gtcmSetTcLengthType: Failed, status = <value> Severity ERROR Description...
  • Page 93 Chapter 4 SMP log error messages 93 Message gtN8300TapiCleanRemDevsVlan failed Severity ERROR Description This message indicates that a cleanup of VLANs information during a hot removal failed. Synopsis Action Message gtTxPort4TcGetDescNumber: Failed, status = <value> Severity ERROR Description This message identifies a driver programming error. Specifically, an attempt to obtain the Tx queue buffer size failed.
  • Page 94 94 Chapter 4 SMP log error messages Message gtTxPortDropMode: Failed, status = <value> Severity ERROR Description This message identifies a driver programming error. Specifically, an attempt to set a port drop mode failed. Synopsis Action Contact the customer support team if the problem persists. Message gtTxPortFlushQueues: Failed, status = <value>...
  • Page 95 Chapter 4 SMP log error messages 95 Message gtTxPortQSetShaperProfile: Failed, status = <value> Severity ERROR Description This message identifies a driver programming error. Specifically, an attempt to set the Tx queue shaper profile failed. Synopsis Action Contact the customer support team if the problem persists. Message gtTxPortQSetWrrProfile: Failed, status = <value>...
  • Page 96: H Messages

    96 Chapter 4 SMP log error messages Message gtTxPortShaperEnable: Failed, status = <value> Severity ERROR Description This message identifies a driver programming error. Specifically, an attempt to enable/disable the port shaper failed. Synopsis Action Contact the customer support team if the problem persists. H Messages Message HAL_Init: NPAL_GtNhopTblInit failed...
  • Page 97 Chapter 4 SMP log error messages 97 Message Hot Insert: boardAfterInitConfig failed for slot <value> Severity ERROR Description This message occurs when the system is unable to obtain the required logical initialization parameters. These parameters contain important system initialization information. Synopsis Action Reboot the switch and contact the customer support team if the problem persists.
  • Page 98 98 Chapter 4 SMP log error messages Message Hot Insert: trUpdateAppDemoPpConfigList failed for slot <value> Severity ERROR Description This message indicates that the updating of the ppDemo Configuration list failed. Synopsis Action Reboot the switch and contact the customer support team if the problem persists. Message Hot insertion failed for device <value>...
  • Page 99: I Messages

    Chapter 4 SMP log error messages 99 Message Hot Remove: hotSyncRemoveDev failed for slot <value> Severity ERROR Description This message indicates that a hot removal of a given slot failed. Synopsis Action Message Hot Remove: trDowndateAppDemoPpConfigList failed for slot <value> Severity ERROR Description...
  • Page 100 100 Chapter 4 SMP log error messages Message IfRec(ipaddr=<ipaddr>, index=<index>) - Exceeded NVRAM limit of <value> Severity WARNING Description This message is generated when the available NVRAM space for storing records is exhausted. Synopsis NVRAM limit exceeded. Action No action needs to be taken. Message igmpAddMltMap: could not allocate mem for p_entry Severity...
  • Page 101 Chapter 4 SMP log error messages 101 Message igmpGrpCreate: Error in imgpSetUpARRec Severity ERROR Description 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.
  • Page 102 102 Chapter 4 SMP log error messages Message igmpRxPkt: cannot send frame Severity ERROR Description This mesage indicates that the control packet could not be sent out. Synopsis Action Message igmpSrcLstDelete: arDeletePortFromGroup failed Severity FATAL Description This message is generated while trying to delete a port from a source/group pair. Synopsis Unable to delete port from group.
  • Page 103 Chapter 4 SMP log error messages 103 Message image programming done Severity INFO Description This message specifies that image programming was completed during the image upgrading process. Synopsis Action Message image programming started, ..Severity INFO Description This message specifies that image programming to the PoE DIMM controller module has started.
  • Page 104 104 Chapter 4 SMP log error messages Message Invalid Card Type fpr phyInit Slot <value> Severity WARNING Description This message indicates that an invalid card type has been detected. Synopsis Action Message Invalid configuration: network appears in two areas Severity INFO Description This message is generated when the same route appears for different areas.
  • Page 105 Chapter 4 SMP log error messages 105 Message invalid profile <value> Severity ERROR Description This message identifies an invalid task for profiling. Synopsis Action Reboot the switch and contact the customer support team if the problem persists. Message ip2GarbageList: Could not allocate mem for garbage!!! Severity ERROR Description...
  • Page 106 106 Chapter 4 SMP log error messages Message IpDoSpecial: ipNetToMediaPhysAddress_index arpadd failed! Severity ERROR Description This message is generated when you try to add a static ARP entry from JDM and the action fails. Synopsis Action Contact customer support for further troubleshooting. Message IpDoSpecial: ipNetToMediaPhysAddress_index Port %d not a member of vlan Severity...
  • Page 107 Chapter 4 SMP log error messages 107 Message ipmcRx: Can't find circuit for cid <cid>! Severity FATAL Description This message indicates that you cannot get the IP circuit. Synopsis Action Message ipNetToMediaPhysAddress_index NULL snmp_arp_circ Severity ERROR Description This message is generated when the physical address you have supplied is not associated with any circuit.
  • Page 108: K Messages

    108 Chapter 4 SMP log error messages Message ipReasmInit: Can't allocate ipNDBTbl! Severity ERROR Description This message is generated when system is not able to allocate memory for the Net data block table. Synopsis Cannot allocate memory dynamically. Action Close all CLI sessions to free up memory. Contact customer support if problem persists.
  • Page 109 Chapter 4 SMP log error messages 109 Message lbStart: NPAL_DeleteMacAddress failed Severity WARNING Description This message indicates the NPAL_DeleteMacAddress failed when doing a loopback test. Synopsis Action Contact the customer support team if the problem persists. Message lbStart: NPAL_RestoreVlanAfterLoopBack failed Severity WARNING Description...
  • Page 110 110 Chapter 4 SMP log error messages Message LogFileSize <value> bytes is exceeding allowed log file size Severity INFO Description This message specifies that the log file size exceeds the allowed file size. Synopsis Action Message LogFileSize <value> bytes is exceeding Maximum log file size Severity INFO Description...
  • Page 111: M Messages

    Chapter 4 SMP log error messages 111 M Messages Message Mac %s movement from port -- to -- Severity WARNING Description This message is generated when a non-EAP MAC moves from an EAP enabled port to another port. Synopsis MAC moves from an EAP enabled port to another port Action Verify that the movement happened only when the MAC is physically moved from an EAP port to another port.
  • Page 112 112 Chapter 4 SMP log error messages Message 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> Severity WARNING Description This message indicates that matching Layer4 fields is not possible with stateless filtering.
  • Page 113 The port is shut down. Initialize the port again. Message Message not sent for deleting msgQ for snmp accounting Severity ERROR Description This message indicates the Passport 8300 is unable to free software resources. Synopsis Software error. Action Contact customer support for assistance. System Messaging Platform Reference Guide...
  • Page 114 Mirroring Disable FAILED for Entry <id> Severity WARNING Description 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. Synopsis Action Verify the correct command parameters in the documentation and try again.
  • Page 115 This message indicates that on link-up of an MLT port, the hardware update failed. Synopsis Action 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. Message...
  • Page 116: N Messages

    Possible security threat. Action Re-initialize the port. Message nncli_commonCliInit : nnclip is still NULL Severity ERROR Description This message indicates that the Passport 8300 was unable to allocate memory for the NNCLIP. Synopsis Action Message nnclip init failed Severity ERROR Description This message indicates the Passport 8300 was unable to initialize NNCLIP.
  • Page 117 Chapter 4 SMP log error messages 117 Message No resource for mac <value> vlan <value> status <value> Severity WARNING Description This message indicates that record space is not available to add a new Mac Address. Synopsis Action Message Non Eap Intrusion (-- -- --) Severity INFO Description...
  • Page 118 Severity ERROR Description 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.
  • Page 119 Chapter 4 SMP log error messages 119 Message NPAL_AddIpRoute: Adding prefix failed entry <ip addr>/<value>, nhId <value> status <value> Severity WARNING Description This message indicates that an attempt to add the route to the hardware failed. Synopsis Action Contact the customer support team if the problem persists. Message NPAL_AddIpRouteToCreateBulkEntry: failed deleting UcPrefix <prefix>...
  • Page 120 <value> Severity INFO Description 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. Synopsis Action Contact the customer support team if the problem persists.
  • Page 121 Chapter 4 SMP log error messages 121 Message NPAL_DeleteArp: Failed deleting NextHop entry <ip addr> nhId <value> status <value> Severity WARNING Description 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. Synopsis Action Contact the customer support team if the problem persists.
  • Page 122 122 Chapter 4 SMP log error messages Message NPAL_EnableVrId: NPAL_SetDefaultIpRoute failed Severity WARNING Description This message indicates that an attempt to set the default route to either CPU or DROP in the hardware failed. Synopsis Action Contact the customer support team if the problem persists. Message NPAL_gstpSetMode(<value>, <value>) failure code: <value>! Severity...
  • Page 123 Chapter 4 SMP log error messages 123 Message NPAL_ReplaceArp: could not override host next hop <ip addr> for portNum <value> NhopId = <value> Status = <value> Severity WARNING Description This message indicates an attempt to override the next-hop with new information in hardware failed.
  • Page 124 124 Chapter 4 SMP log error messages Message ntp global event sync failed Severity ERROR Description HA-syncing NTP global configuration to secondary CPU failed. Synopsis Try using the same releases on both the boxes. Else, contact customer support Action Message ntp key event sync failed Severity ERROR...
  • Page 125 Chapter 4 SMP log error messages 125 Message ntpFetchAndAdjustTime: can't allocate serverList Severity ERROR Description Memory allocation failed. Synopsis Memory problem! Try factory defaulting the box & then use it. Action Message ntpFetchAndAdjustTime: Select Error Severity ERROR Description The select function returns a negative value. Synopsis Action Message...
  • Page 126 126 Chapter 4 SMP log error messages Message ntpInitIo: can't open UDP socket Severity ERROR Description The socket() function returned a negative value. Synopsis Try the command after some time. On persistence, contact customer support. Action Message ntpReadServers: can't allocate serverElement Severity ERROR Description...
  • Page 127: O Messages

    Chapter 4 SMP log error messages 127 Message ntpSyncCallback:corrupt msg Severity ERROR Description Syncing failed due to invalid module version in message. Synopsis Action Message number of index does not equal size of link list Severity ERROR Description This message indicates the index number of elements in the policy table differs from the size of the link list during the sanity check.
  • Page 128: P Messages

    128 Chapter 4 SMP log error messages Message os_init: failed init_avl Severity FATAL Description This message is generated if the system runs out of DRAM memory. Synopsis Insufficient DRAM memory. Action Increase the DRAM size. Message Out of power resource, redundant power admin remain disabled Severity ERROR Description...
  • Page 129 Chapter 4 SMP log error messages 129 Message Password modified for user-exec mode Severity INFO Description This message indicates the password has been successfully changed for user-exec mode. Synopsis Action Message PCAP File in PCMCIA is being over-written Severity INFO Description This message is generated when the PCAP autosave file in the PCMCIA is being overwritten.
  • Page 130 130 Chapter 4 SMP log error messages Message peGetPortMacStats: coreGetMacCounter : GT_EXCESSIVE_COLLISIONS, port <value> failed Severity WARNING Description This message indicates that the MAC counter cannot be read. Synopsis Action Contact the customer support team if the problem persists. Message PhyReadModeReg : Invalid Card Type Slot Severity WARNING...
  • Page 131 Chapter 4 SMP log error messages 131 Message PoE backup PSE is activated Severity WARNING Description 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. Synopsis Action Replace the bad power supply.
  • Page 132 132 Chapter 4 SMP log error messages Message PoE Slot <value> Main Power Usage On (above threshold), Power Consumption= <value> Severity ERROR Description This message indicates that power usage is from a PoE card. Synopsis Action Message POE_LOCK failed Severity ERROR Description This message specifies that the semaphore could not be obtained.
  • Page 133 Chapter 4 SMP log error messages 133 Message poePowerMgr: Could not start poePowerMgr task Severity ERROR Description This message indicates that the system was unable to execute the PoE task, so PoE operation stopped. Synopsis Action Reboot the switch. Message poePowerSourceScan: re-scan power profile Severity ERROR...
  • Page 134 134 Chapter 4 SMP log error messages Message poeTask: PoE power (48V ERROR PoE is disabled Severity ERROR Description This message identifies a PoE power 48V error. Synopsis Action Replace PoE card, PoE power supply, or PoE chassis. Message poeTask: PoE task ERROR PoE is disabled Severity ERROR Description...
  • Page 135 Chapter 4 SMP log error messages 135 Message Port -- aborting Severity INFO Description This message is generated when an 8021x controlled port enters the aborting state of Authenticator PAE State Machine Synopsis Port entered the aborting state of Authenticator PAE State Machine. Action No action necessary Message...
  • Page 136 136 Chapter 4 SMP log error messages Message Port -- forced authorized Severity INFO Description This message indicates that an 802.1X controlled port has entered the forced authorized state of the Authenticator PAE State Machine. Synopsis Port entered the forced authorized state of the Authenticator PAE State Machine. Action No action is necessary.
  • Page 137 Chapter 4 SMP log error messages 137 Message Port -- held Severity INFO Description This message is generated when an 8021x controlled port enters the held state of Authenticator PAE State Machine Synopsis Port entered the held state of Authenticator PAE State Machine. Action No action necessary Message...
  • Page 138 Verify the correct command parameters in the documentation and try again. Message portEnableFlowControl_8300 called for non-8300 port Severity INFO Description This message indicates there is a non-8300 port in the system. Synopsis Action Message portEnableFlowControl_8300: gprtPortFlowControlEnable Failed for port <value> Error <value>...
  • Page 139 Chapter 4 SMP log error messages 139 Message portEnableMirrorByPort_8300: gmirrSetRxAnalyzerPort port <#> failed Severity WARNING Description This message indicates that the system is unable to configure the Rx analyzer port in hardware. Synopsis Action Verify the correct command parameters in documentation and try again. Message portEnableMirrorByPort_8300: gmirrSetRxPort port <#>...
  • Page 140 140 Chapter 4 SMP log error messages Message portGetThrillRideSpeed: Non ThrilRide Card Type Slot <value> Severity INFO Description This message indicates that a non-8300 card is inserted in the specified slot. Synopsis Action Message portPollThrillRide: port=<value>, link is unstable! Severity...
  • Page 141 Chapter 4 SMP log error messages 141 Message portVctDoTest: Could not get the Result in WA. gtStatus not OK: <value> Severity ERROR Description This message indicates that the result could not be obtained from the VCT test. Synopsis Action Perform the test again. Message portVctDoTest: Could not get the Result.
  • Page 142 142 Chapter 4 SMP log error messages Message portVctDoTest: Could not write 0xa into Reg29) Severity ERROR Description This message indicates that the information could not be written into the register for the VCT test. Synopsis Action Perform the test again. Message portVctDoTest: Could not write back 0x0 into Reg30) Severity...
  • Page 143 Chapter 4 SMP log error messages 143 Message portVctInitOneRecord: Record #<record> greater than max <value> Severity ERROR Description This message indicates that the specified port number is not correct. Synopsis Action Check the port number and perform the test again. Message portVctPortConfigurable: Bogus port #<value>...
  • Page 144 144 Chapter 4 SMP log error messages Message ppeGetPortMacStats: coreGetMacCounter : GT_COLLSIONS, port <value> failed Severity WARNING Description This message indicates that the MAC counter cannot be read. Synopsis Action Contact the customer support team if the problem persists. Message ppeGetPortMacStats: coreGetMacCounter : GT_DROP_EVENTS, port <value>...
  • Page 145 Chapter 4 SMP log error messages 145 Message ppeGetPortMacStats: coreGetMacCounter : GT_GOOD_OCTETS_SENT, port <value> failed Severity WARNING Description This message indicates that the MAC counter cannot be read. Synopsis Action Contact the customer support team if the problem persists. Message ppeGetPortMacStats: coreGetMacCounter : GT_GOOD_PKTS_RCV, port <value>...
  • Page 146 146 Chapter 4 SMP log error messages Message ppeGetPortMacStats: coreGetMacCounter : GT_MAC_RCV_ERROR, port <value> failed Severity WARNING Description This message indicates that the MAC counter cannot be read. Synopsis Action Contact the customer support team if the problem persists. Message ppeGetPortMacStats: coreGetMacCounter : GT_MAC_TRANSMIT_ERR, port <value>...
  • Page 147 Chapter 4 SMP log error messages 147 Message ppeGetPortMacStats: coreGetMacCounter : GT_PKTS_1024TOMAX_OCTETS, port <value> failed Severity WARNING Description This message indicates that the MAC counter cannot be read. Synopsis Action Contact the customer support team if the problem persists. Message ppeGetPortMacStats: coreGetMacCounter : GT_PKTS_128TO255_OCTETS, port <value>...
  • Page 148 148 Chapter 4 SMP log error messages Message ppeGetPortMacStats: coreGetMacCounter : GT_PKTS_65TO127_OCTETS, port <value> failed Severity WARNING Description This message indicates that the MAC counter cannot be read. Synopsis Action Contact the customer support team if the problem persists. Message ppeGetPortMacStats: coreGetMacCounter : GT_UNDERSIZE_PKTS, port <value>...
  • Page 149 Chapter 4 SMP log error messages 149 Message ppePhyInit: coreWrite to Reg 0x0 FAILED Slot <value> ppPort <value> retVal <value> Severity WARNING Description This message indicates that an attempt to write to a port physical register failed. Synopsis Action Contact the customer support team if the problem persists. Message ppePhyInit: coreWrite to Reg 0x14 FAILED Slot <value>...
  • Page 150 150 Chapter 4 SMP log error messages Message ppePhyInit: coreWrite to Reg 0x1E FAILED Slot <value> ppPort <value> retVal <value> Severity WARNING Description This message indicates that an attempt to write to a port physical register failed. Synopsis Action Contact the customer support team if the problem persists. Message ppePoLDownloadImage: create ppePoLFwUpgradeTask task failed Severity...
  • Page 151 Chapter 4 SMP log error messages 151 Message ppePoLDownloadImage: invalid packet received Severity INFO Description This message indicates that an invalid packet ID was detected during image download. Synopsis Action Reset the PoE card using admin disable, re-enable the card, and restart the image upgrade process again.
  • Page 152 152 Chapter 4 SMP log error messages Message ppeSetMltPort: return status = <value> Add = <value> PortNum = <value> Severity ERROR Description This message indicates that an addition/deletion of the port to and from the MLT failed during the hardware configuration. Synopsis Action The switch maybe usable, but further MLT operations may fail.
  • Page 153: Q Messages

    Chapter 4 SMP log error messages 153 Message PreConfigTask: PreConfig will be re-tried!! Severity INFO Description This message is generated when you specify that PreConfig will be re-tried. Synopsis Action Message PreConfigTask: Slot <value> NO pre-configured Severity ERROR Description This message is generated when a slot is not pre-configured due to insufficient MLTs.
  • Page 154 154 Chapter 4 SMP log error messages Message qosHwGetPortDefaultSize: unexpected card type Severity ERROR Description This message identifies an application programming error. Specifically, an invalid card type is present. Synopsis Action File a bug report. Message qosHwGetPortLineRate: port not present Severity ERROR Description...
  • Page 155 Chapter 4 SMP log error messages 155 Message qosInitMap8021pToClassTbl: # of class not in range Severity ERROR Description This message identifies an application programming error. Specifically, a traffic class parameter is out of range when passed to the function. Synopsis Action File a bug report.
  • Page 156 156 Chapter 4 SMP log error messages Message qosPolicyIdxTblAdd: - failed adding Severity ERROR Description This message indicates that the switch failed to add an entry to the policy table. Synopsis Action Contact the customer support team if the problem persists. Message qosPolicyIdxTblAdd: index tbl not init Severity...
  • Page 157: R Messages

    Chapter 4 SMP log error messages 157 Message qosPolicyIdxTblRemove: index tbl not init Severity WARNING Description This message identifies an application programming error. Specifically, the policy index table is not initialized. Synopsis Action File a bug report. Message qosPolicyTblAddEntry: malloc failed Id <value> Severity WARNING Description...
  • Page 158 158 Chapter 4 SMP log error messages Message rad_changeRequestPkt unknown code <> in radius packet Severity ERROR Description This message identifies an erroneous code in the header of the received RADIUS packet. Synopsis RADIUS response packet must have the correct code. Action Verify that the RADIUS server is functioning correctly and then contact customer support.
  • Page 159 Chapter 4 SMP log error messages 159 Message rad_handleServerResponse select failed<num> Severity ERROR Description This message identifies an internal error in the software Synopsis Software error. Action If the problem persists, contact customer support. Message rad_incrIgapEnabledVlanCnt failed to allocate memory Severity ERROR Description...
  • Page 160 160 Chapter 4 SMP log error messages Message rad_newSocket failed to allocate memory Severity ERROR Description This message indicates that the system is out of memory. Synopsis Insufficient memory. Action If the problem persists, contact customer support. Message rad_receiveResponse received response with bad length recvd<num> Severity ERROR Description...
  • Page 161 Chapter 4 SMP log error messages 161 Message rad_sendRequest unable to send a UDP packet error<num> Severity ERROR Description This message indicates that the switch is unable to send a UDP packet. Synopsis Software error. Action If the problem persists, contact customer support. Message rad_sendRequest unknown code<num>...
  • Page 162 162 Chapter 4 SMP log error messages Message radAcctOff failed to allocate memory Severity ERROR Description This message indicates that the system is out of memory. Synopsis Insufficient memory. Action If the problem persists, contact customer support. Message radAcctOn failed to allocate memory Severity ERROR Description...
  • Page 163 Chapter 4 SMP log error messages 163 Message radAcctSendToServer failed to allocate memory Severity ERROR Description This message indicates that the system is out of memory. Synopsis Insufficient memory. Action If the problem persists, contact customer support. Message radAcctSendToServer socket recvfrom error Severity ERROR Description...
  • Page 164 164 Chapter 4 SMP log error messages Message radAcctSnmpStop failed to allocate memory Severity ERROR Description This message indicates that the system is out of memory. Synopsis Insufficient memory. Action If the problem persists, contact customer support. Message radAcctStart failed to allocate memory Severity ERROR Description...
  • Page 165 Chapter 4 SMP log error messages 165 Message RadAuthNonEapMacAddr: no radius server configured Severity INFO Description This message is generated when no radius server is configured while building the authentication request packet for the non-EAP client. Synopsis No radius server is configured Action Configure the radius server for EAP.
  • Page 166 166 Chapter 4 SMP log error messages Message radDictAttrSet Can't set value for attribute<string> Severity ERROR Description This message indicates that a RADIUS attribute unknown to the switch is being looked-up. Synopsis Unknown attribute in received RADIUS or sent packet. Action Verify that the sent and received RADIUS packets contain known attributes.
  • Page 167 Chapter 4 SMP log error messages 167 Message RADIUS server returned invalid mac qos for -- MAC address Severity WARNING Description This message is generated when the radius server sends the QoS attribute but with a invalid MAC QoS value. Synopsis Invalid QoS value received from the radius server for the non-eap client Action...
  • Page 168 168 Chapter 4 SMP log error messages Message radSendServer can't lock mutex Severity ERROR Description This message indicates that the switch is unable to acquire a software resource. Synopsis Software error. Action Contact customer support. Message radSnmpAcctNwData_Add Can't allocate memory for SNMP Session Severity ERROR Description...
  • Page 169 Chapter 4 SMP log error messages 169 Message rccExtendAggrNetList failed: no memory Severity WARNING Description This message is generated when system is not able to allocate memory for a block of size 1024. Synopsis Cannot allocate memory dynamically. Action Close all CLI sessions to free up memory. Contact customer support if problem persists.
  • Page 170 170 Chapter 4 SMP log error messages Message rcIpAddPortToVlan: Bad PortNum <value> Severity ERROR Description This message is generated if the port number is out of range of valid values. Synopsis Invalid port number. Action Provide a valid port number. Message rcIpAddReplaceStaticRoute: rcIpStaticRouteActive failed Severity...
  • Page 171 Chapter 4 SMP log error messages 171 Message rcIpAddRoute: rcIpAddArp failed with <value> Status. Severity ERROR Description This message is generated if the system is unable to add the ARP entry to the table. Synopsis Addition of the ARP is unsuccessful. Action Enter a valid IP and next-hop.
  • Page 172 172 Chapter 4 SMP log error messages Message rcIpAddrTblSet: unable to allocate an IpRec for IfIndex <value> Severity ERROR Description 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.
  • Page 173 Chapter 4 SMP log error messages 173 Message rcIpAddStaticArp: arpadd failed for failed Severity ERROR Description This message is generated if the addition of a static ARP entry in the ARP table failed. Synopsis Addition of static ARP table entry failed. Action Contact customer support for further troubleshooting.
  • Page 174 174 Chapter 4 SMP log error messages Message rcIpArpLock: Can't take semaphore, rcIpArpLockSemId! Severity ERROR Description This message indicates that the software ARP lock could not be accepted. Synopsis Action Contact the customer support team if the problem persists. Message rcIpArpUnlock: semGive failed! Severity ERROR...
  • Page 175 Chapter 4 SMP log error messages 175 Message rcIpConfigureCid: ipCircAddIPA failed for <value> on IfIndex <value> Severity FATAL Description This message is generated if the addition of an IP address to a circuit fails. Synopsis Cannot add an IP address. Action Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and...
  • Page 176 176 Chapter 4 SMP log error messages Message rcIpDelArpByIfIndexAll: Can't create <value> task Severity ERROR Description This message is generated when an attempt to spawn a task fails. Synopsis Unable to create the task. Action Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology.
  • Page 177 Chapter 4 SMP log error messages 177 Message rcIpDhcpForwardTbIGet invalid get option Severity ERROR Description This message indicates that an invalid SNMP GET is selected. Synopsis SNMP GET option invalid. Action More troubleshooting is required. Message rcIpGetDhcpPortStatsRec: Bad PortNum Severity ERROR Description This message indicates that a port number is not within its specified range.
  • Page 178 178 Chapter 4 SMP log error messages Message rcIpGetInEchos: m2IcmpGroupInfoGet failed Severity ERROR Description This message is generated if the ICMP group information fetching operation failed while receiving the echoes. Synopsis ICMP group information fetching operation failed. Action No action required. Contact customer support for further troubleshooting. Message rcIpGetInEchosReps: m2IcmpGroupInfoGet failed Severity...
  • Page 179 Chapter 4 SMP log error messages 179 Message rcIpGo: NPAL_EnableVrId failed Severity FATAL Description This message is generated when the system couldn't create the virtual router in hardware. Synopsis Action Reboot the switch and contact the customer service team if the problem persists. Message rcipIgmpGroupTblEntryAdd: Can't malloc Severity...
  • Page 180 180 Chapter 4 SMP log error messages Message rcIpModifyNextHop: Arp pointer is NULL for route: <ipaddr> mask: <mask> Severity ERROR Description 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.
  • Page 181 Chapter 4 SMP log error messages 181 Message rcIpModifyNextHop: trying to replace local route for route: <ipaddr> mask: <mask> Severity ERROR Description Never try to replace the local route, but here it indicates it is doing so. You should only delete and add local route. Synopsis Action Message...
  • Page 182 182 Chapter 4 SMP log error messages Message rcipRouteIndexRemove() - failed removing <ipaddr>, Mask= <mask> Severity WARNING Description This message is generated when removing a route index failed. Synopsis Freeing of route index failed. Action Contact customer support for further troubleshooting. Message rcIpRxFrame: can't signal semaphore Severity...
  • Page 183 Chapter 4 SMP log error messages 183 Message rcIpStaticRtSyncCallback: unsupported msg type <value> Severity ERROR Description This message is generated when an invalid message type is encountered. Synopsis Invalid message type encountered. Action This is an internal error. Contact customer support for further troubleshooting. Message rcIpSuperNetAddRoute: rarAddIpRoute failed with <value>:<ipaddr>...
  • Page 184 184 Chapter 4 SMP log error messages Message rcIpTask: Can't take semaphore Severity FATAL Description This message is generated when the semaphore was not available. Synopsis Semaphore unavailable. Action Contact customer service and have the following information available for further analysis: system logs including any memory dumps, switch configuration, and network topology.
  • Page 185 Chapter 4 SMP log error messages 185 Message rcIpVlanSetIpAddress: ipCircCreate failed for <value> IfIndex <value> Severity ERROR Description This message is generated if an IP interface could not be created with the given index. Synopsis Unable to create an IP interface. Action This is an internal software error.
  • Page 186 186 Chapter 4 SMP log error messages Message rcMcastLoadIfRec: unable to find an IpIfRec for IfIndex <value> Severity ERROR Description This message is generated if the interface for multicast is not found because the IP record is not found. Synopsis IP record not found for the given index.
  • Page 187 Chapter 4 SMP log error messages 187 Message Releasing allocated MLTs Severity INFO Description This message specifies that allocated MLTs are being released. Synopsis Action Message resetting all I/O cards Severity INFO Description This message is generated when, during system boot up, all I/O cards are reset by the master CPU.
  • Page 188 188 Chapter 4 SMP log error messages Message RMON not init before RmonEventCreate Severity WARNING Description This message indicates that the RMON event configuration is not loaded. Synopsis RMON module is not initialized. Action Reload RMON event configuration. Message Rmon not yet started, further RMON config may not be loaded Severity WARNING Description...
  • Page 189: S Messages

    Chapter 4 SMP log error messages 189 S Messages Message Save config to file <file-name> failed. Severity INFO Description This message is generated when the switch is unable to save the PCAP configuration. Synopsis Action Message Save config to file <file-name> successful. Severity INFO Description...
  • Page 190 190 Chapter 4 SMP log error messages Message setDiagMirrorByPort: Failed Id <id> Severity WARNING Description 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. Synopsis Action Verify the correct command parameters in the documentation and try again.
  • Page 191 Chapter 4 SMP log error messages 191 Message Slot <value> out of PoE power resource Severity INFO Description This message is generated when there is not enough PoE power available for target slot allocation. Synopsis Action Message Slot <value> PoE power admin disabled Severity INFO Description...
  • Page 192 192 Chapter 4 SMP log error messages Message Slot <value> PoE power usage exceed threshold limit Severity INFO Description This message is generated when the PoE card consumed more power than the threshold set. Synopsis Action Monitor the overall power consumption to prevent PoE power overload. If necessary, disable PoE port power administratively.
  • Page 193 Chapter 4 SMP log error messages 193 Message Slot <value> Xbar has invalid Multicast Table. Failed to rewrite <value> times Severity ERROR Description This message is generated when the multicast table on the slave CPU crossbar is corrupted and cannot be corrected. Synopsis Action Re-insert or replace the card.
  • Page 194 194 Chapter 4 SMP log error messages Message source <src filename> and destination <dst filename> Severity INFO Description This message is generated when the source file is <src filename> and destination file is <dst filename>. Synopsis Action Message STG <value> HAS ALREADY BEEN USED Severity INFO Description...
  • Page 195: T Messages

    Chapter 4 SMP log error messages 195 Message syncTaskDelete: IPC semDelete <value> currentId <value> Severity FATAL Description This message is generated when the IPC semaphore semId from the current Id fails. Synopsis Action Reboot the switch and contact the customer service team if the problem persists. Message System Arp Table Full Severity...
  • Page 196 196 Chapter 4 SMP log error messages Message Table syncing failed for ntp server entries Severity ERROR Description HA-syncing for NTP server table failed. Synopsis Try using the same releases on both the boxes. Else, contact customer support Action Message TACACS+ authentication failed Severity INFO...
  • Page 197 Chapter 4 SMP log error messages 197 Message TACACSG_authenticate_user: no user found Severity ERROR Description Software state machine error. Synopsis A software error occurred, TACACS+ client should be operable. If proceeds, contact technical support. Action Message TACACSG_authenticate_user: session not finished Severity ERROR Description...
  • Page 198 198 Chapter 4 SMP log error messages Message TACACSG_create_user: Cannot get user memory Severity ERROR Description Software error - cannot reserve a buffer memory for user. Synopsis A software error occurred, TACACS+ client should be operable. If proceeds, contact technical support. Action Message TACACSG_create_user: failed to add user to hash...
  • Page 199 Chapter 4 SMP log error messages 199 Message TACACSP_tcp_create_con: can't get socket Severity ERROR Description Cannot create socket for authenticating with TACACS+. Synopsis If the problem persists, must restart switch. Action Message TACACSP_tcp_create_con: failed to set ioctl FIONBIO Severity ERROR Description Cannot configure socket for authenticating with TACACS+ Synopsis...
  • Page 200 200 Chapter 4 SMP log error messages Message tapiCreateTc: Policy Id <value> doesn't exist Severity ERROR Description This message is generated when there is an application programming error. Specifically, the policy with the specified ID cannot be found. Synopsis Action File a bug report.
  • Page 201 Chapter 4 SMP log error messages 201 Message tdpInit: Can't create MAC Range Filter! Severity ERROR Description This message is generated when the MAC filter for capturing TDP control packets to the CPU is not created. Synopsis Action Message The card in slot -- is resetting. Try the command later. Severity WARNING Description...
  • Page 202 202 Chapter 4 SMP log error messages Message traceDumpBkTr: failed to get CP slot number Severity ERROR Description This message is generated when the system fails to get the CP slot number when sending trace info from the coprocessor. Synopsis Action Message traceStart: Cannot create CopTraceLockSemId semaphore...
  • Page 203 Chapter 4 SMP log error messages 203 Message trCardSendTraceCmd: malloc of message parameter failed Severity ERROR Description This message is generated when the system runs out of memory. Synopsis Action Reboot the switch and contact the customer service team if the problem persists. Message trCardSendTraceCmd: malloc of message parameter failed Severity...
  • Page 204 204 Chapter 4 SMP log error messages Message trMsgAlloc failed Severity FATAL Description This message is generated when the system runs of out memory. Synopsis Action Reboot the switch and contact the customer service team if the problem persists. Message trReportBmErrors: devNum= <value>, errType= <value>, errCause= <value>...
  • Page 205 Chapter 4 SMP log error messages 205 Message trTracePrint: malloc failed Severity ERROR Description This message is generated when the system runs out of memory. Synopsis Action Reboot the switch and contact the customer service team if the problem persists. Message trTraceStart: malloc failed Severity...
  • Page 206: U Messages

    206 Chapter 4 SMP log error messages U Messages Message Unable to Allocate memory for log filter entry Severity INFO Description This message is generated when the system is unable to allocate memory for the log filter entry. Synopsis Action Message Unable to Allocate memory for log filter string Severity...
  • Page 207 Chapter 4 SMP log error messages 207 Message Unable to restore port -- to Vlan -- Severity ERROR Description 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.
  • Page 208 208 Chapter 4 SMP log error messages Message unknown speed <value> Severity ERROR Description This message is generated when the gprtGetPortSpeed returns an unknown port speed. Synopsis Action Contact the customer service team if the problem persists. Message UnSupported card type in Slot <value>! Severity INFO Description...
  • Page 209 Chapter 4 SMP log error messages 209 Message User -- on Port -- is authenticated Severity INFO Description This message is generated when a user successfully logs in to a 8021x controlled port. Synopsis User session begins Action No action necessary Message User -- on Port -- is disconnected Severity...
  • Page 210: V Messages

    210 Chapter 4 SMP log error messages Message user <user-name> logged out from console port Severity INFO Description This message is generated when the user logs out from a console connection. Synopsis The user logs out from a console connection. Action Message user connected via console port...
  • Page 211 Chapter 4 SMP log error messages 211 Message VCT Task Semaphore Creation Failed Severity ERROR Description This message is generated when creating the VCT semaphore failed. Synopsis Action Message VCT Test DONE. Get the VCT results for port <portnum> Severity INFO Description This message is generated when the process of obtaining the VCT results...
  • Page 212 212 Chapter 4 SMP log error messages Message VLAN -- returned by RADIUS server for port -- does not exist Severity ERROR Description This message is generated when the VLAN returned by RADIUS server for 8021x authorized port does not exist on the system. Synopsis RADIUS returned invalid VLAN Action...
  • Page 213 Chapter 4 SMP log error messages 213 Message Vlan id -- returned from RADIUS server cannot be used for tagged port -- Severity INFO Description 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. Synopsis System attempts to move 8021x authorized tagged port to VLAN returned by RADIUS server...
  • Page 214 214 Chapter 4 SMP log error messages Message vlanCreateVirtualLan: VLAN Table was damaged!Index <value> vid <value> NumVlans <value>, Index, VlanId, NumVlans Severity ERROR Description This message is generated when there is no more Free entries in the VLAN table. Synopsis Action Suggests memory corruption.
  • Page 215 Chapter 4 SMP log error messages 215 Message vlanFdbUpdMsg: malloc failed! Severity ERROR Description This message is generated when the system is out of memory. Synopsis Action Free up some space. Message vlanGo: NPAL_DisableAutoAging return fail! Severity ERROR Description This message is generated when the disabling of auto aging in the hardware failed.
  • Page 216 216 Chapter 4 SMP log error messages Message vlanMacInit: indexAlloc failed for pRarStaticMacAddressIndex! Severity ERROR Description This message is generated when the system is out of memory. Synopsis Action Free up memory. Message vlanMacInit: msgQCreate failed Severity FATAL Description This message is generated when there is no memory for message Q. Synopsis Action Message...
  • Page 217: W Messages

    Chapter 4 SMP log error messages 217 Message vlanSyncCallback: unsupported version <value> Severity ERROR Description This message is generated if an unsupported version of the static route is encountered during sync call back. Synopsis Invalid version. Action This is an internal error. Contact customer support for further troubleshooting. W Messages Message WDT TASK: Warning System DRAM usage at <#>...
  • Page 218 218 Chapter 4 SMP log error messages Message write failed to location 0x4001800c on dev <value> Severity WARNING Description This message is generated when the write PP register fails. Synopsis Action Contact the customer service team if the problem persists. Message Wrong order in received TCP chunks from xyz TACACS+ server Severity...
  • Page 219: Index

    NNCLI Log file show log file command with CLI defining transfer criteria with CLI defining transfer criteria with NNCLI show logging file with NNCLI displaying with CLI 27, support, Nortel displaying with NNCLI switching merging to CLI modifications to NNCLI...
  • Page 220 Index logging to PCMCIA with CLI logging to PCMCIA with NNCLI stop logging to PCMCIA with CLI stop logging to PCMCIA with NNCLI technical publications technical support text conventions 316806-C...

Table of Contents