1. Manuals
  2. Brands
  3. Lucent Manuals
  4. Server
  5. Stinger FS
  6. Administration manual

Lucent Stinger FS Administration Manual

Dsl access concentrators
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Stinger®
Administration Guide
Part Number: 363-217-010R9.8.1
For software version 9.8.1
November, 2005

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Stinger FS and is the answer not in the manual?

Questions and answers

Summary of Contents for Lucent Stinger FS

  • Page 1 Stinger® Administration Guide Part Number: 363-217-010R9.8.1 For software version 9.8.1 November, 2005...
  • Page 2 Hereby, Lucent Technologies, declares that the equipment documented in this publication is in compliance with the essential require- ments and other relevant provisions of the Radio and Telecommunications Technical Equipment (RTTE) Directive 1999/5/EC. To view the official Declaration of Conformity certificate for this equipment, according to EN 45014, access the Lucent INS online documentation library at http://www.lucentdocs.com/ins.

  • Page 3: Customer Service

    United States. Alternatively, call 1-866-LUCENT8 (1-866-582-3688) from any location in North America for a menu of Lucent services. Or call +1 510-747-2000 for an operator. If you do not have an active services agreement or contract, you will be charged for time and materials.

  • Page 5: Table Of Contents

    Contents Chapter 1 Administering a Stinger System ............1-1 About standalone and hosted Stinger systems............1-1 Logging into a Stinger unit..................1-2 Enabling basic security measures ................1-3 Changing the default Admin password ............... 1-3 Securing the serial port of each control module..........1-3 Specifying a management-only Ethernet interface ...........
  • Page 6 Contents Specifying group permissions for commands and profile access ....1-24 1-24 Specifying a time-out for user logins ............... 1-29 1-29 Setting the command-line prompt ..............1-29 1-29 Setting log levels for each login ............... 1-29 1-29 Logging in as a different user................1-30 1-30 Displaying the current user ................
  • Page 7 Contents Configuring the Syslog daemon ..............2-12 2-12 Configuring call logging ..................2-12 2-12 Overview of call logging .................. 2-12 2-12 Enabling call logging..................2-12 2-12 Chapter 3 Working with Stinger Shelves and Modules ........3-1 Understanding physical addressing on Stinger units..........3-1 Viewing system components..................
  • Page 8 Contents Displaying IMA groups................4-10 4-10 Reinitializing out-of-service IMA groups ..........4-10 4-10 Monitoring remote shelves ..................4-11 4-11 Using the remote-shelf-stat profile ..............4-11 4-11 Displaying information about enabled remote shelves........4-13 4-13 Displaying Gigabit Ethernet OLIM (GE-OLIM) line status ......4-14 4-14 Displaying DSL performance settings..............
  • Page 9 Contents Maintaining ASIC Integrity ..................5-22 5-22 Checking the defaults for control module self-tests ........5-22 5-22 Enabling centralized integrity checks .............. 5-25 5-25 Chapter 6 Managing System Configuration and Memory ......6-1 Saving system configuration ..................6-1 Saving the configuration to a local file .............. 6-2 Saving the configuration to a network host ............
  • Page 10 Contents Optional firmware (Centillium-based LIMs)............6-21 6-21 Using optional firmware .................. 6-21 6-21 Verifying firmware version of a LIM ............... 6-22 6-22 Caveats with current implementation ............. 6-22 6-22 Log messages for firmware download events ..........6-23 6-23 Upgrading bootprom on GE-COP, GE-OLIM, and IP RLIMs........6-23 6-23 Command syntax.....................
  • Page 11 Specifying the dsl-threshold profile ............8-23 8-23 Overview of the dsl-threshold profile settings ........8-24 8-24 Lucent-specific ADSL threshold traps ............8-25 8-25 Enabling the system to generate ADSL threshold traps ......8-26 8-26 Configuring link-state traps for LIM and trunk ports ........8-26 8-26 Changing the setting for the desired-trap-state parameter systemwide..
  • Page 12 Contents Configuring traps for CDR device failure ............... 8-34 8-34 Configuring alarms for CDR failure ..............8-34 8-34 Configuring traps for events related to CDR failure ........8-35 8-35 Displaying alarms caused by CDR failure ............8-35 8-35 Chapter 9 Working with IP Traffic ..............9-1 Testing IP connectivity .....................
  • Page 13 Contents Displaying the status of ATM trunk modules and their connections ....11-5 11-5 Checking the status of a VCC interface............11-5 11-5 Checking the status of a terminating PVC ............11-6 11-6 Displaying ATM VCC information and packet statistics ........11-6 11-6 Displaying ATM virtual link information ............
  • Page 14 Contents Running an external diagnostic test (EDT) feature ........12-23 12-23 Digital loopback..................12-24 12-24 Analog loopback..................12-24 12-24 Running built-in self tests (BISTs) on DSL ports ........... 12-25 12-25 Supported LIMs ..................12-25 12-25 Enabling the built-in self test using the command-line interface ... 12-25 12-25 Relay alarm testing....................
  • Page 15 Contents Displaying RADIUS accounting session status ..........A-20 A-20 Displaying RADIUS authentication and accounting statistics......A-21 A-21 Interface debugging....................A-22 A-22 Displaying network interface mappings ............A-23 A-23 Using the EOC command on ADSL interfaces..........A-23 A-23 Control module debugging..................A-24 A-24 Displaying the status of redundant control modules ........A-25 A-25 Displaying interface management information ..........A-26 A-26...
  • Page 17 Tables Table 1-1 Authentication keys generated by the system ........1-6 Table 1-2 Syslog messages reported for secure shell error conditions ....1-9 Table 1-3 Administrative access available on a system ........1-12 1-12 Table 1-4 Permissions and associated commands ........... 1-23 1-23 Table 1-5 Message levels .................

  • Page 19: About This Guide

    About This Guide This guide explains how to administer a Stinger unit and manage its operations. To use this guide, you must have set up the Stinger system as described in the Getting Started Guide for your Stinger unit and configured it for network connectivity as described in the Stinger ATM Configuration Guide.
  • Page 20 About This Guide Documentation conventions Following are all the special characters and typographical conventions used in this manual: Convention Meaning Monospace text Represents text that appears on your computer’s screen, or that could appear on your computer’s screen. Boldface Represents characters that you enter exactly as shown (unless monospace text the characters are also in italics—see Italics, below).
  • Page 21 About This Guide Stinger documentation set The Stinger documentation set consists of the following manuals, which can be found at http://www.lucent.com/support and http://www.lucentdocs.com/ins. Read me first: ■ – Edge Access and Broadband Access Safety and Compliance Guide. Contains important safety instructions and country-specific information that you must read before installing a Stinger unit.
  • Page 22 About This Guide RADIUS: TAOS RADIUS Guide and Reference. Describes how to set up a unit to use ■ the Remote Authentication Dial-In User Service (RADIUS) server and contains a complete reference to RADIUS attributes. Administration and troubleshooting: Stinger Administration Guide (this guide). ■...

  • Page 23: Administering A Stinger System

    Stinger MRT and not to physical modules. About standalone and hosted Stinger systems In this document, a Stinger FS, Stinger FS+, Stinger LS, Stinger RT, Stinger MS+ or Stinger MRT unit that does not provide host functions to other Stinger units is referred to as a standalone unit.

  • Page 24: Logging Into A Stinger Unit

    ID. For more information about the hosted operations of Stinger MRT units, see the Getting Started Guide for your unit. Stinger FS+, Stinger LS, and Stinger RT units with revision 2.0, revision 2.1, and IP control modules also support host functions to Stinger Compact Remote units. The Stinger Compact Remote unit is a small temperature-hardened unit that extends the reach of host Stinger units located in the central office.

  • Page 25: Enabling Basic Security Measures

    Administering a Stinger System Enabling basic security measures Enabling basic security measures The Stinger unit is shipped with certain default parameters set to allow easy access for the initial configuration. After you have initially logged in as administrator, ensure that the following three basic security tasks have been completed: ■...

  • Page 26: Specifying A Management-Only Ethernet Interface

    Administering a Stinger System Enabling basic security measures With this setting, the system automatically logs off the current user profile if the Data Terminal Ready (DTR) signal is lost on the serial port. Write the profile. admin> write -f If your Stinger unit is operating with two control modules, both are working in parallel.

  • Page 27: Managing Administrative Access To The Unit

    The ssh program can replace Telnet, which is a less secure method of administrative access. Lucent recommends that you use ssh for administrative access to a TAOS unit. For information about how to disable Telnet access, see “Disabling telnet access” on page 1-10.

  • Page 28: User Authentication

    Administering a Stinger System Managing administrative access to the unit User authentication: user password ■ ■ Encryption: Triple data encryption standard-cypher block chaining (3DES-CBC) Message authentication code (MAC) Algorithm: HMAC-SHA1 ■ Key Exchange Algorithm: Diffie-Hellman key exchange (ediffie-hellman-group1- ■ sha1) Server-Host Key Algorithm: ssh-dss ■...

  • Page 29: Encryption And Mac Key Re-Exchange

    Administering a Stinger System Managing administrative access to the unit Encryption and MAC key re-exchange The SSHv2 draft recommends that the encryption and MAC keys be changed after each gigabyte of transmitted data or after each hour of connection time, whichever occurs sooner.
  • Page 30 Administering a Stinger System Managing administrative access to the unit Parameter Specifies Version of the SSH protocol that the system negotiates. Valid ssh-version settings are as follows: ■ any-ssh-version (the default)—SSHv1 and SSHv2 ssh-version-1—Only SSHv1 is negotiated. ■ ssh-version-2—Only SSHv2 is negotiated. ■...

  • Page 31: Logging Into A System Using Secure Shell

    Administering a Stinger System Managing administrative access to the unit -Socket- Local Port InQLen InQMax InQDrops Total Rx Service 1023 Syslog 1022 0 ASyslog 1021 0 ASyslog 0 EchoSer Sntp 5150 Atmp 1020 0 RadAuth Snmp tcp: -Socket- Local Remote Service State 1/c 131073 *.22 LISTEN...

  • Page 32: Telnet Access

    Administering a Stinger System Managing administrative access to the unit Telnet access The secure shell program is more secure method for administering the Stinger system remotely. You can disable Telnet access on a system, but if you must use Telnet, consider the additional security measures described below.
  • Page 33 Administering a Stinger System Managing administrative access to the unit [in TACL:permit-list[1]] valid-entry = no source-address = 0.0.0.0/0 source-address-mask = 0.0.0.0 Parameter Setting enable-permit Enables or disables control over telnet access to the system on the basis of the permit-list settings in the tacl profile.

  • Page 34: Summary Of Administrative Access Available

    Administering a Stinger System Creating user profiles for administrative access Escape character is '^]'. Connection closed by foreign host. Summary of administrative access available Table 1-3 shows the type of access available on the system based on the settings of the ssh-enabled and telnet-enabled parameters.

  • Page 35: Creating A New Administrative Profile

    Administering a Stinger System Creating user profiles for administrative access If you are already logged into the Stinger unit, make sure you are at the highest level by entering the list .. command (possibly more than once), as in the following example: admin>...

  • Page 36: Enabling Two Level Authentication

    Administering a Stinger System Creating user profiles for administrative access Enabling two level authentication You can configure the system to require a second level of authentication for the following types of access to a Stinger unit or for any combination of the following: Telnet access using a system IP address ■...
  • Page 37 Administering a Stinger System Creating user profiles for administrative access Command-line RADIUS attribute Specifies interface parameter Ascend-User-Login- login-level Login level for this user profile. Specify one of the Level following values: ■ first-level (the default)—This user profile is to be used for first level authentication. second-level—This user profile is to be used for ■...

  • Page 38: Settings In The System Profile

    Administering a Stinger System Creating user profiles for administrative access Settings in the system profile To configure second-level authentication for a Stinger system, in the system profile, set the user-second-level-authentication parameter. The user-second-level- authentication parameter is defined as follows: Parameter Specifies Enables/disables two-level user authentication for the different user-second-...

  • Page 39: Sample Configuration

    Administering a Stinger System Creating user profiles for administrative access Sample configuration Suppose you have an existing user profile called admin. To require two levels of authentication for the user admin, create a new user john and configure it as a first- level login.

  • Page 40: Authentication From A Remote Shelf To A Host Stinger Unit

    Administering a Stinger System Creating user profiles for administrative access The system generates a log message whenever a login attempt fails. The log message indicates whether the level of authentication failure is at the first level or second level. For example: LOG critical, Shelf 1, Controller, Time: 16:46:32-- login failure: user 'john', source '135.17.134.39' on first level access LOG critical, Shelf 1, Controller, Time: 16:47:17--...

  • Page 41: User Account And User Password Expiration

    Administering a Stinger System Creating user profiles for administrative access shelf-router-1/8> When a user has successfully logged in, the host generates a log message, such as the one shown below: LOG info, Shelf 1, Controller, Time: 19:57:03-- login success : user 'admin', source 'control bus'on first level access LOG info, Shelf 1, Controller, Time: 19:57:08-- login success : user 'user1', source 'control bus'on second level access User account and user password expiration...

  • Page 42: Setting Expiration Dates For User Accounts And Passwords

    Administering a Stinger System Creating user profiles for administrative access Setting expiration dates for user accounts and passwords The following parameters in the user profile enable you to view the last login date for a user account and specify an expiration date for a user account and user password. Only user account expiration is supported by RADIUS.

  • Page 43: Enforcing A Password Check

    Administering a Stinger System Creating user profiles for administrative access Enforcing a password check To configure the system to validate that any new password created is unique and that it is at least 8 characters in length, with at least two numbers and four alphabetical characters, set the enforce-password-check parameter in user profile to yes.

  • Page 44: Assigning Permissions

    Administering a Stinger System Creating user profiles for administrative access The following sample session shows a user changing an expired password: bash-2.05$ telnet 135.17.134.28 Trying 135.17.134.28... Connected to 135.17.134.28. Escape character is '^]'. User: user1 Old Password: New Password: ReEnter New Password: SECOND LEVEL ACCESS User: user2 Old II Level Password:...

  • Page 45: Table 1-4 Permissions And Associated Commands

    Administering a Stinger System Creating user profiles for administrative access example: admin> ? ( user ) acct-failsafe ( debug ) agsh ( debug ) alarm ( system ) aliasTable ( debug ) annexType ( debug ) apsMgr ( debug ) arptable ( system ) atmcacstat...

  • Page 46: Specifying Group Permissions For Commands And Profile Access

    Administering a Stinger System Creating user profiles for administrative access Table 1-4. Permissions and associated commands (Continued) Permission Command class Allow-Password N/A. The Allow-Password permission enables a user to view passwords. If the permission is set to no, the user sees a row of asterisks instead of the actual configured password.
  • Page 47 Administering a Stinger System Creating user profiles for administrative access assign a user group to a user by specifying a valid user-group profile for the user- group parameter in the user profile. Creating a user group To define a command user group, set the following parameters in the user-group profile.
  • Page 48 Administering a Stinger System Creating user profiles for administrative access Parameter Setting Enable/disable permission for the users in the group to exclude-listed-commands use the commands designated by the command parameter. With the default no setting, users have permission to use the designated commands. Specify yes to disable permission to use the designated commands.
  • Page 49 Administering a Stinger System Creating user profiles for administrative access admin> read user ted admin> set allow-update = yes admin> set allow-system = yes admin> set allow-termserv = yes admin> set allow-diagnostic = yes admin> set allow-password = yes admin> set allow-code = yes admin>...
  • Page 50 Administering a Stinger System Creating user profiles for administrative access Verifying user group settings The system does not prohibit you from entering a command user group or a user that does not exist, nor from entering an invalid list of commands. Use the usergroupcheck command to verify that your specifications are valid.

  • Page 51: Specifying A Time-Out For User Logins

    Administering a Stinger System Creating user profiles for administrative access contents of the ARP cache, and is protected by the system level in both the user and user-group profiles. In addition, the option to add entries to the table is protected by the diagnostic or update level.

  • Page 52: Logging In As A Different User

    Administering a Stinger System Creating user profiles for administrative access going on at the prompt. For example, the following commands cause messages at the critical, alert, and emergency levels to be displayed: admin> read user test admin> set log-display-level = critical admin>...

  • Page 53: Basic System Settings

    Administering a Stinger System Basic system settings Basic system settings The following sections describe how to set the system name, time, date and system clock source. Setting the system name The Stinger system name is used only during Point-to-Point Protocol (PPP) negotiations.

  • Page 54: Configuring System Clocking

    Administering a Stinger System Basic system settings admin> set date day = 06 admin> set date year = 2002 admin> write Configuring system clocking The Stinger unit requires a clock source for its timing subsystem. By default, the system uses the a built-in 8kHz clock on the single or primary control module as its timing source.

  • Page 55: Displaying Basic System Information

    Administering a Stinger System Displaying basic system information sources of equal priority are present, the system selects the first valid clock source. (A clock source is valid if the clock-source parameter is set to eligible and the OC12, DS3, OC3, or E3 interface is synchronized.) Once it has selected a clock source, the system uses that source until the source becomes unavailable or a higher-priority source becomes available.

  • Page 56: System And Module Uptime

    Lucent Stinger CRT COP ■ On a redundant system, if you enter the info command from the secondary control module, this field shows Lucent Stinger. System name Name of the system as configured in the system profile. This field reports not configured if no value is specified in the system profile.

  • Page 57: Using The Status Window

    Administering a Stinger System Displaying basic system information If you specify a slot and shelf number, the uptime command displays the current time; identifies the module installed in the slot, and the length of time that the module installed in the slot has been operating. The following example shows that an SDSL LIM in slot 3 has been operating for 48 minutes and 38 seconds: admin>...

  • Page 58: Understanding The Status Window

    Administering a Stinger System Displaying basic system information Figure 1-6. Sample contents of a status window Left: Connections Top: General 12 Connections ScootersStngr Status 0008 c9 ATM 04/09/ 0 7616K Serial number: 123456 Version: 9.5.206 0007 c7 ATM 04/07/ 0 7616K 0006 c11 ATM 04/11/ 0 7616K Rx Pkt: 998004...

  • Page 59: General Status Information

    Administering a Stinger System Displaying basic system information If the status window is not already visible, the connection command opens it with the connection-status information displayed: admin> connection 2 Connections | Status 0003 test1 A 02/01/01/ 0 8000 | Serial number: 11XYZ90A7 Version: 9.7 0002 test2 A 01/17/01/ 1 155M | | Rx Pkt: 184381...

  • Page 60: Log Message Information

    Administering a Stinger System Displaying basic system information admin> line Or, you can use the following command to specify that the line-status information appears in the top of the window, replacing the general status information: admin> line top You can display information about all lines installed in the system if you wish, but the default is to show information only about enabled lines.

  • Page 61: Customizing The Status Window Display

    Administering a Stinger System Displaying basic system information This message indicates the key sequences you can use for displaying additional information in the Log area: The Down Arrow and Up Arrow keys display the next and previous messages in ■ the buffer, respectively.

  • Page 62: Viewing The Factory Configuration And Software Licenses

    Administering a Stinger System Displaying administrative connections Viewing the factory configuration and software licenses The read-only base profile displays software version, enabled features (software licenses), network interfaces, and other system information that is not modified across resets. These values are read from the system ROM, security program array logic (PAL), and the hardware assembly itself.

  • Page 63: Customizing The Output Of The Userstat Command

    Administering a Stinger System Displaying administrative connections Field Description Slot:Item Shelf:slot:item/logical-item of the host port to which the call was routed. Tx/Rx Rate Transmit and receive rate. Type of service in use for the session. Following are the possible values: --- The service is being negotiated.

  • Page 64: Displaying Information Related To A Known Username

    Administering a Stinger System Displaying administrative connections To display only the relevant username, include the -o option as follows: admin> userstat -a 1.1.1.238 -o %u Username net1 <end user list> 1 active user(s) Displaying information related to a known username Use the userstat -u command to display information related to a known username.

  • Page 65: Displaying Administrative Users

    Administering a Stinger System Displaying administrative connections Displaying administrative users The who command displays names of administrative users, user profiles, and IP addresses of administrative users from Telnet sessions. An asterisk (*) denotes the current session. For example: admin> who user profile from...

  • Page 66: Resetting A Stinger System

    Administering a Stinger System Resetting a Stinger system Resetting a Stinger system When you reset the Stinger system, it restarts and terminates all active connections. All users are logged out, and the default security level is reactivated. In addition, a system reset can cause a WAN line to temporarily shut down due to momentary loss of signaling or framing information.

  • Page 67: Configuring Logging, Syslog, And Call Logging Services

    Configuring logging, Syslog, and call logging services Configuring system logging and Syslog services ......2-1 Configuring call logging ......... . . 2-12 2-12 The Stinger unit monitors itself continuously and generates error and event messages related to its operations.
  • Page 68 Configuring logging, Syslog, and call logging services Configuring system logging and Syslog services auxiliary-syslog[1] = { no info 0.0.0.0 514 local0 } auxiliary-syslog[2] = { no info 0.0.0.0 514 local0 } admin> list 1 [in LOG:auxiliary-syslog[1]] syslog-enabled = no syslog-level = info host = 0.0.0.0 port = 514 facility = local0...
  • Page 69 Configuring logging, Syslog, and call logging services Configuring system logging and Syslog services Parameter Setting port Destination port of the syslog host that receives the first data stream. In the auxiliary-syslog [1] subprofile, the port value specifies the destination port of the syslog host that receives the second data stream.

  • Page 70: Configuring System Logging

    Configuring logging, Syslog, and call logging services Configuring system logging and Syslog services Parameter Setting syslog-level Lowest level of log messages that the Stinger unit sends to the syslog server. All levels above the level you indicate are included in syslog messages. For example, if alert is specified, messages at the emergency and alert levels are included.

  • Page 71: Viewing Command Logs

    Configuring logging, Syslog, and call logging services Configuring system logging and Syslog services no user commands). To enable command logging, set this parameter to a value greater than zero. For example, the following commands configure the system to save up to 100 commands: admin>...

  • Page 72: Viewing The Cmd-Log Profile

    Configuring logging, Syslog, and call logging services Configuring system logging and Syslog services Field Indicates User session ID number. Card Shelf and slot number from which the command was entered. Command Command entered by the user. Viewing the cmd-log profile If command logging is enabled, the system creates a cmd-log profile for every command entered by a user.

  • Page 73: Saving Command Logs

    Configuring logging, Syslog, and call logging services Configuring system logging and Syslog services Saving command logs You can save command log profiles to a file in the flash card or to a remote system using the save command. For example: admin>...
  • Page 74 Configuring logging, Syslog, and call logging services Configuring system logging and Syslog services Enabling the system to save log messages as profiles The following parameters in the log profile enable the saving of a log message as a profile. These parameters are visible only if in the user profile, allow-debug is set to yes.
  • Page 75 Configuring logging, Syslog, and call logging services Configuring system logging and Syslog services If you restore a saved configuration in which log saving enabled, the system will ignore the restored setting and will continue to use the existing setting. Viewing log-entry profiles You can save log-entry profiles to a file in the system flash card or to another device on the network.

  • Page 76: Configuring The Stinger Unit Syslog Facility

    Configuring logging, Syslog, and call logging services Configuring system logging and Syslog services Parameter Specifies Instance of a particular type of log entry (boot or runtime). This index value is incremented by 1 every time an instance of the type of log occurs.

  • Page 77: Enabling The Syslog Facility On The Stinger Unit

    Configuring logging, Syslog, and call logging services Configuring system logging and Syslog services Enabling the Syslog facility on the Stinger unit The following sample commands enable syslog reporting admin> read log admin> set syslog-enabled = yes admin> write Configuring Syslog streams The stream of records sent by the Stinger unit to a syslog server is called a syslog stream.

  • Page 78: Configuring The Syslog Daemon

    NavisAccess™ 5.1 and later releases to monitor, report, and send alarms on various performance and failure information for the Stinger unit. For additional information, go to http://www.lucent.com/products/ and search on NavisAccess. Overview of call logging The main purpose of Stinger call logging is to provide details about physical-layer line statistics to a management station for all active DSL OC3, DS3, and E3 trunk lines in a Stinger unit.
  • Page 79 Configuring logging, Syslog, and call logging services Configuring call logging admin> set call-log-enable = yes admin> set call-log-host-1 = 10.2.3.4 admin> set call-log-timeout = 10 admin> set call-log-stop-only = yes admin> set call-log-limit-retry = 3 admin> write Stinger® Administration Guide 2-13...
  • Page 81 Stinger MRT refers to the 19” and 23” versions of the Stinger MRT and Stinger MRT-2 units. The chassis of Stinger FS, Stinger FS+, Stinger LS, Stinger RT, or Compact Remote units have slots that accept plug-in modules with different functions. The smaller...

  • Page 82: Working With Stinger Shelves And Modules

    The show command lists the address of all modules installed in a Stinger system including those installed in remote shelves, their required operating states and current operating states, and the type of module installed. Following is a sample output from a standalone Stinger FS, Stinger FS+, Stinger LS, or Stinger RT, admin> show...

  • Page 83: Field Description From The Output Of The Show Command

    Working with Stinger Shelves and Modules Viewing system components { shelf-3 slot-1 0 } mrt-36-adsl-card { shelf-3 first-control-mod+ UP mrt-cm { shelf-4 slot-1 0 } mrt-36-shdsl-card { shelf-4 first-control-mod+ UP mrt-cm { shelf-5 slot-1 0 } mrt-36-adsl-card { shelf-5 first-control-mod+ UP mrt-cm { shelf-6 slot-1 0 } mrt-36-adsl-card...

  • Page 84: Displaying The Status Of Lpms, Psms, And Clt Modules

    Working with Stinger Shelves and Modules Viewing system components Displaying the status of LPMs, PSMs, and CLT modules The rearslotshow command shows the status of all slots used for LPMs, path selector modules (PSMs), and copper loop test (CLT) modules. It also reports on the status of the midplane sparing bus.

  • Page 85: Displaying A Picture Of The Topology

    Working with Stinger Shelves and Modules Viewing system components Port connected to - On Master Port connected to - On Slave For an explanation about the output of the toplogy command, see the Stinger MRT Getting Started Guide for your unit or the Stinger Reference. Displaying a picture of the topology For a picture of the topology, use the topology -p command.

  • Page 86: Table 3-1 Statistics Displayed For A Remote Shelf

    Working with Stinger Shelves and Modules Viewing system components Number of Nack Sent Number of Reset Sent : 0 Number of Init Sent Table 3-1 shows details displayed by this command: Table 3-1. Statistics displayed for a remote shelf Output field Description of value discovery restart Number of times autodiscovery has been restarted.

  • Page 87: Sending An Init Packet To A Remote Shelf

    Working with Stinger Shelves and Modules Viewing system components Output field Description of value Request Rcvd with Invalid Autodiscovery received from with invalid shelf ID (a ShelfID shelf ID outside the range from 2 to 7). If you execute this command on the remote shelf, statistics are displayed for that shelf only.

  • Page 88: Using The Show Command With The Shelf And Slot Numbers

    Working with Stinger Shelves and Modules Viewing system components Using the show command with the shelf and slot numbers To use the show command for information about a particular module, add the shelf and slot numbers as arguments. For example: admin>...

  • Page 89: Opening A Session With A Module

    1 9 shelf-router-1/9> The following command opens a session to the LIM located in shelf 1, slot 4 of a Stinger FS, Stinger LS, or Stinger RT unit: admin> open 1 4 dmtadsl-atm-1/4> The following command opens a session with virtual slot 1 on a Stinger MRT: admin>...

  • Page 90: Changing The State Of A Module

    Working with Stinger Shelves and Modules Changing the state of a module Changing the state of a module You can temporarily start or stop the operation of a module, put it in maintenance mode, or reset it by using the slot command or by setting the reqd-state parameter in the slot-admin profile.

  • Page 91: Changing The State Of A Module's Interface

    Working with Stinger Shelves and Modules Changing the state of a module’s interface slot-address* = { shelf-1 slot-1 0 } reqd-state = reqd-state-up Parameter Setting slot-address Address of the slot. Required operational state of the slot. The setting, reqd-state nonoperational, temporarily disables a slot and its module. The change in status is complete when the setting of current- state parameter has changed to match the setting of the reqd- state parameter.

  • Page 92: Using The Device-State Profile

    Working with Stinger Shelves and Modules Changing the state of a module’s interface To reenable port 24, use the device command with the -u option as follows: admin> device -u {{1 3 24} 0} device { { 1 3 24 } 0 } state change forced Using the device-state profile Every host interface or network interface on a Stinger unit has a device-state profile, which stores the current state of an interface and allows you to change it.

  • Page 93: Removing A Module And Its Configuration

    Removing a module and its configuration Removing a module and its configuration Stinger FS, Stinger FS+, Stinger LS, Stinger RT and Compact Remote modules are hot-swappable. When you remove a module, by default, the system retains its configuration. You can reinstall a module or install another of the same type in the same slot without reconfiguring the system or uploading a backup configuration.

  • Page 94: When A New Module Does Not Match A Slot Type

    Working with Stinger Shelves and Modules Removing a module and its configuration When a new module does not match a slot type When the system detects that a newly installed module does not match existing slot configuration and the slot-type-check parameter is set to yes, the module remains inactive and the condition is reported in the output of the show command, the slot- status profile for the slot, and chassis.mib.

  • Page 95: Activating A Lim In A Mismatched State

    Working with Stinger Shelves and Modules Removing a module and its configuration If the operating state of a LIM or trunk module is MISMATCH, you can activate the newly installed LIM or trunk module or you can install a module type that matches the existing configuration for the slot.

  • Page 96: Activating A Trunk Module

    Working with Stinger Shelves and Modules Removing a module and its configuration { shelf-1 slot-5 0 } ep-72-gs-adsl2plus { shelf-1 trunk-module-2 0 } UP e3-atm-trunk-daughter-card Activating a trunk module To activate a trunk module in the mismatched state, set the slot-type-check parameter to no and then reset the trunk using the atmtrunkreset trunknum command.

  • Page 97: Replacing A Lim And Retaining The Existing Atm Addresses On The Slot

    SPVCs. Recovering from a failed module installation If you installed a new module in a Stinger FS, Stinger FS+, Stinger LS, or Stinger RT unit before upgrading the system software, and the module does not begin operating properly, you can attempt to recover by clearing NVRAM or removing the module.

  • Page 98: Using The Nvram Command

    Working with Stinger Shelves and Modules Recovering from a failed module installation Using the nvram command Before clearing NVRAM, see “Retaining configuration information after clearing NVRAM” on page 6-3. To recover from a failed module installation using the nvram command, proceed as follows: Save the current system configuration.

  • Page 99: Enabling Lim Self-Testing

    Working with Stinger Shelves and Modules Enabling LIM self-testing Enabling LIM self-testing You can configure the system to periodically audit Ripper-based LIMs to detect lockups at the DSL or SONET interface. When a lockup occurs, the system resets the Ripper device, which prevents cells from being dropped. This capability is supported on Ripper-based LIMs, listed below: 24-port ADSL LIMs (dadsl-atm-24-card) ■...

  • Page 101: Table 4-1 Where To Find Additional Information

    Monitoring Interfaces on LIMs and Trunk Modules Where to find related information ........4-1 Monitoring trunk module interfaces .

  • Page 102: Monitoring Interfaces On Lims And Trunk Modules

    Monitoring Interfaces on LIMs and Trunk Modules Monitoring trunk module interfaces Monitoring trunk module interfaces Table 4-2 summarizes the status profiles and commands that you use to monitor the physical interfaces of Stinger trunks modules. Table 4-2. Summary of profiles and commands for monitoring interfaces Device Commands Status profile...

  • Page 103: Displaying The Status Of Trunk Interfaces

    Monitoring Interfaces on LIMs and Trunk Modules Monitoring trunk module interfaces The ds3-atm-stat, e3-atm-stat, and oc3-atm-stat profiles show the physical address of the device, state of the line, redundancy settings, and error and statistic information specific to that trunk module. The following sample commands display the ds3-atm-stat profile for one of the DS3 interfaces of a DS3-ATM trunk module installed in slot 17: admin>...

  • Page 104: Displaying Trunk Port Status

    Monitoring Interfaces on LIMs and Trunk Modules Monitoring trunk module interfaces Displaying trunk port status To display the status of the all trunk ports of a Stinger unit, use the -a option: admin> atmtrunks -a All OC3 ATM trunks: OC3 Lines (dvOp dvUpSt dvRq sAdm...

  • Page 105: Resetting Trunk Statistics

    Monitoring Interfaces on LIMs and Trunk Modules Monitoring DSL interfaces Line 1 18 4 } (Down Idle DOWN DOWN 00854) Line 1 18 5 } (Down Idle DOWN DOWN 00855) Line 1 18 6 } (Down Idle DOWN DOWN 00856) Disabled E3 ATM trunks: E3 Lines (dvOp...

  • Page 106: Displaying Dsl Interface Profiles

    Monitoring Interfaces on LIMs and Trunk Modules Monitoring DSL interfaces Table 4-3. Summary of profiles and commands for monitoring interfaces (Continued) Device Commands Status profile ADSL LIMs and Stinger MRT ADSL dmtaldsllines al-dmt-stat ports 32-port SHDSL/HDSL2 LIM hdsl2lines hdsl2-stat 48-port and 72-port SHDSL LIMs shdsllines shdsl-stat Stinger MRT SHDSL ports...

  • Page 107: Displaying Dsl Interface Status

    Monitoring Interfaces on LIMs and Trunk Modules Monitoring DSL interfaces [in AL-DMT-STAT/{ shelf-1 slot-2 5 }] physical-address* = { shelf-1 slot-2 5 } line-state = active spare-physical-address = { any-shelf any-slot 0 } sparing-state = sparing-none sparing-change-reason = unknown sparing-change-time = 0 sparing-change-counter = 0 vpi-vci-range = vpi-0-15-vci-32-127 vp-switching-vpi = 15...

  • Page 108: Displaying Adsl Lim Interfaces

    Monitoring Interfaces on LIMs and Trunk Modules Monitoring DSL interfaces sdsllines, shdsllines, and imagroups commands display information about interfaces of a specific type in a Stinger unit. You use these commands with one of the following options: Option Specifies Displays information about all DSL interfaces. Displays all disabled interfaces of a particular type.
  • Page 109 Monitoring Interfaces on LIMs and Trunk Modules Monitoring DSL interfaces admin> dmtaldsllines -a (dvOp dvUpSt dvRq sAdm nailg) Line 1 3 1 } (Down Idle DOWN DOWN 00101) Line 1 3 2 } (Down Idle DOWN DOWN 00102) Line 1 3 3 } (Down Idle DOWN...

  • Page 110: Displaying T1 And E1 Interfaces

    Monitoring Interfaces on LIMs and Trunk Modules Monitoring DSL interfaces Displaying T1 and E1 interfaces The following sample command displays information about the T1 modules installed in slot 4 and slot 6: admin> imalines -a All IMA lines: (dvOp dvUpSt dvRq sAdm lMode Nailg) Line { 1 4 1 }...

  • Page 111: Monitoring Remote Shelves

    Monitoring Interfaces on LIMs and Trunk Modules Monitoring remote shelves You can enable this feature for an IMA group by setting the ima-auto-restart parameter in the imagroup profile to yes. For example: [in IMAGROUP/ima1] admin> ima-auto-restart = yes Monitoring remote shelves Table 4-5 summarizes the profile and command that you can use to display information about Compact Remote shelves and its components.
  • Page 112 Monitoring Interfaces on LIMs and Trunk Modules Monitoring remote shelves Parameter Specifies remote-shelf-id Shelf ID of the remote shelf represented in this profile. host-port Gigabit uplink to the host, in the format {{shelf ID, slot number, interface} logical item Number}. The second Gigabit Ethernet uplink to the host, if host-port-2 applicable.

  • Page 113: Displaying Information About Enabled Remote Shelves

    Monitoring Interfaces on LIMs and Trunk Modules Monitoring remote shelves Parameter Specifies topology:port-2-shelf Shelf ID of the remote shelf directly connected to the second cascade port on the host. Not meaningful for Stinger CR units. validation-status:id- Indicates whether the validation-id setting in the valid remote-shelf-config profile matches the validation ID specified by the remote shelf’s DIP-switch setting.

  • Page 114: Displaying Gigabit Ethernet Olim (Ge-Olim) Line Status

    Monitoring Interfaces on LIMs and Trunk Modules Displaying DSL performance settings Field Indicates Shelf number Shelf Name Shelf name Shelf Name Shelf Location Location of the remote shelf Shelf Type Stinger MRT or Compact Remote Host Port Link to the host. Shelf Enabled Administrative state of the remote shelf Oper State...

  • Page 115: Displaying The Current Time

    Monitoring Interfaces on LIMs and Trunk Modules Displaying DSL performance settings Displaying the current time The adslmib t port command displays the current time retrieved from the active control module. For example: gs-72-1/3> adslmib t 1 Date: 06/04/2004 Time: 21:06:56 Displaying ADSL physical entries The adslmib a port command displays basic ATU-C and ATU-R information.

  • Page 116: Displaying Interval Statistics For Disruption Of Service Events

    Monitoring Interfaces on LIMs and Trunk Modules Displaying DSL performance settings Displaying interval statistics for disruption of service events The adslmibmgr c port command displays interval statistics for disruption of service events. For example: gs-72-1/3> adslmib c 1 Lofs: 0 Loss: 0 Lols: 0 Lprs: 0...

  • Page 117: Displaying Adsl Block Counts

    Monitoring Interfaces on LIMs and Trunk Modules Displaying DSL performance settings Prev1DayMoniSecs: 0 sec Prev1DayLofs: 0 sec Prev1DayLoss: 0 sec Prev1DayLols: 0 sec Prev1DayLprs: 0 sec Prev1DayESs: 0 sec Prev1DayInits: 0 <<< ATU-R Performance Data Entry >>> Lofs: 0 Loss: 0 Lols: 0 Lprs: 0 ESs: 0...

  • Page 118: Displaying Performance Data Interval

    Monitoring Interfaces on LIMs and Trunk Modules Displaying DSL performance settings Curr15MinTxBlks: 7991 Curr15MinCorrBlks: 0 Curr15MinUcorBlks: 0 Curr1DayTimeElapsed: 12754 Curr1DayRxBlks: 675786 Curr1DayTxBlks: 698694 Curr1DayCorrBlks: 60 Curr1DayUcorBlks: 0 Prev1DayMoniSecs: 0 Prev1DayRxBlks: 0 Prev1DayTxBlks: 0 Prev1DayCorrBlks: 0 Prev1DayUcorBlks: 0 <<< ATU-R Channel Performance Data Entry >>> RxBlks: 698694 TxBlks: 675786 CorrBlks: 869...

  • Page 119: Displaying Adsl Block Statistics (Channel Performance) Intervals

    Monitoring Interfaces on LIMs and Trunk Modules Displaying DSL performance settings Number: 13 Lofs: 0 sec Loss: 0 sec Lols: 0 sec Lprs: 0 sec ESs: 0 sec Inits: 0 ValidData: 1 gs-72-1/3> adslmib i 1 2 <<< ATU-C Interval Performance Data Entry >>> Number: 12 Lofs: 0 sec Loss: 0 sec...

  • Page 120: Displaying Service Traps Sent

    Monitoring Interfaces on LIMs and Trunk Modules Displaying DSL performance settings The following sample command shows ADSL block statistics for the second to last completed 15-minute interval: gs-72-1/3> adslmib j 1 2 <<< ATU-C Interval Channel Performance Data Entry >>> Number: 13 recvBlks: 50445 txBlks: 52155...

  • Page 121: Redundancy Support For Stinger Services

    Monitoring Interfaces on LIMs and Trunk Modules Redundancy support for Stinger services Redundancy support for Stinger services Table 4-6 describes the type of redundancy support provided for Stinger services, based on the type of control module installed in the system. Table 4-6.

  • Page 122: Monitoring Lim And Lim Port Redundancy

    Monitoring Interfaces on LIMs and Trunk Modules Monitoring LIM and LIM port redundancy To determine the duration of service interruption (in seconds), use the following formula: 120 seconds + (number_of_connections divided by 6) For best case scenarios, the following formula applies: 120 seconds + number_of_connections divided by 8 Monitoring LIM and LIM port redundancy You can configure a redundant line interface module (LIM) that you can manually...

  • Page 123: Verifying Port Redundancy Status

    It also reports on the status of the midplane sparing bus. For example, suppose that a Stinger FS is equipped with ADSL LIMs and SDSL LIMs. The 24-port ADSL LIM in slot 1 has failed and is being replaced by the 24-port ADSL LIM in slot 14.

  • Page 124: Displaying Redundancy Or Ignore-Lineup Settings For Lim Ports

    Monitoring Interfaces on LIMs and Trunk Modules Monitoring LIM and LIM port redundancy [ 12 ] 0 Empty ( IRM, LPM ) [ 13 ] 0 Empty ( IRM, LPM ) [ 14 ] 93 Path Selector Module ( PSM ) [ 15 ] 0 Empty ( IRM, LPM ) [ 16 ] 94 Copper Loop Tester ( CLT ) Midplane sparing bus usage :...

  • Page 125: Monitoring Redundant Trunk Groups

    Monitoring Interfaces on LIMs and Trunk Modules Monitoring redundant trunk groups 1-7-4 ADSL 1-7-5 ADSL 1-7-6 ADSL 1-7-9 ADSL 1-7-14 ADSL 1-16-21 HDSL2 1-16-22 HDSL2 1-16-23 HDSL2 The following sample command displays all ports that are configured for automatic or manual redundancy: admin>...

  • Page 127: Monitoring Network Processor Operations

    Monitoring Network Processor operations Monitoring network processor operations ......5-1 Optimizing system performance ........5-19 5-19 Maintaining ASIC Integrity .
  • Page 128 Monitoring Network Processor operations Monitoring network processor operations Parameter Setting Fixed-rate bandwidth that has been allocated for the interface. allocated-fixed- bandwidth bandwidth- Indicates whether the system was able to fully allocate the allocation- status requested fixed-rate bandwidth. bandwidth-serviced The requested fixed-rate bandwidth is fully allocated.

  • Page 129: Displaying Cac Data For The Gigabit Ethernet Olim

    Monitoring Network Processor operations Monitoring network processor operations {1 16 0} 152576 152576 BW SERVICED {1 17 1} 41408 41377 BW SERVICED {1 17 2} 41408 41377 BW SERVICED {1 18 1} 152576 152576 BW SERVICED {1 18 2} 152576 152576 BW SERVICED {1 0 2}...

  • Page 130: Monitoring Network Processor Operations On Ip Control Modules

    Monitoring Network Processor operations Monitoring network processor operations 1000000 1000000 0 1000000 PORT {1 5 4} (stngr-golim-card) (ACTIVE) Stream Total BW Gtd BW Gtd Allocated Gtd Available 1000000 1000000 0 1000000 1000000 1000000 0 1000000 PORT {1 5 5} (stngr-golim-card) (ACTIVE) Stream Total BW Gtd BW Gtd Allocated Gtd Available...

  • Page 131: Enabling And Disabling Statistics Collection

    Monitoring Network Processor operations Monitoring network processor operations Enabling and disabling statistics collection The stats enable/disable command is applicable only for IP QoS statistics. For all other network processor operations, statistics monitoring is always enabled. Monitoring IP QoS To collect IP QoS statistics, determine the WAN interface number for the connection for which you would like to monitor IP QoS.
  • Page 132 Monitoring Network Processor operations Monitoring network processor operations PRIORITIES Number of priority Lowest priority Mapping priority/COS :P[0]=6 P[1]=x P[2]=x P[3]=5 P[4]=4 P[5]=3 P[6]=x P[7]=2 SCHEDULING Line Rate :150015 Data queue Id :8276 Scheduler ID PDU type :cell Number of COS queues ATM service category :VBR non real time PCR (cell per sec)
  • Page 133 Monitoring Network Processor operations Monitoring network processor operations Number of priority Lowest priority Mapping priority/COS :P[0]=3 P[1]=2 P[2]=x P[3]=x P[4]=x P[5]=x P[6]=x P[7]=x SCHEDULING Line Rate :1000000 Data queue Id :8286 Scheduler ID PDU type :packet Number of COS queues Scheduling priority Peak Rate (Kbps) :49997...

  • Page 134: Monitoring Statistics For A Connection

    Monitoring Network Processor operations Monitoring network processor operations Disabling IP QoS monitoring To disable IP QoS monitoring, enter the stats disable np ipqos command. For example: admin> stats disable np ipqos 15 IP QOS monitoring. display counter for IF 15 QoS monitoring direction: downstream Counter COS 2 :917 Counter COS 3 :0...

  • Page 135: Monitoring Fpp Statistics

    Monitoring Network Processor operations Monitoring network processor operations ---------------- Discard for Queue 291 :0x0000 Discard for Queue 293 :0x0000 Discard for Queue 294 :0x0000 Discard for Queue 295 :0x0000 Clearing statistics for a connection To clear statistics for a connection, enter the stats clear np conn slot ifnum command.

  • Page 136: Global Rsp Statistics

    Monitoring Network Processor operations Monitoring network processor operations IP TTL expiry count: 0 IP Header version error count: 0 GE IP Header checksum error count: 0 Unrecognized Tag error count: 0 P2 Framer error count: 0 P2 VLAN error count: 0 IN Filter Discard: 0 OUT Filter Discard: 0 Ethernet Filter Discard: 0...
  • Page 137 Monitoring Network Processor operations Monitoring network processor operations to monitor logical port traffic and error statistics.Logical port statistics. lportNum is the logical port number, a value from 1 through 16. count specifies the number of entries to display. Valid values are from 1 through 16. If you specify 3 for lport and 4 for count, the output shows entries for logical ports 3, 4, 5, and 6.

  • Page 138: Scheduler Traffic And Error Statistics

    Monitoring Network Processor operations Monitoring network processor operations Scheduler traffic and error statistics You can use the stats traffic|error np sch sid [count|count rspslot] command to report scheduler traffic and error information. The traffic and error options report the same output. sid is the scheduler ID.

  • Page 139: Enabling, Disabling, And Clearing Statistics Collection

    Monitoring Network Processor operations Monitoring network processor operations Enabling, disabling, and clearing statistics collection To enable statistics collection on Ethernet ports, use the stats enable ether command, and then specify if you would like statistics on all ports or for a specific Ethernet port.

  • Page 140: Displaying Ethernet Traffic And Error Statistics And Traffic Rates

    Monitoring Network Processor operations Monitoring network processor operations Displaying Ethernet traffic and error statistics and traffic rates You can display Ethernet traffic and error statistics and traffic rates for all Ethernet ports or for a specific port. When you display statistics for all ports, the output is summarized.
  • Page 141 Monitoring Network Processor operations Monitoring network processor operations Rx error overrun Tx underrun Rx Error code Tx defer Rx false carrier Tx excess defer Rx error max SDU Rx IW overrun Rx error MRU Displaying Ethernet traffic rates You can display Ethernet rates for all Ethernet ports by entering the stats rate ether command and specifying a port number(s).

  • Page 142: Displaying Atm Statistics-Fast Ethernet Trunk Module

    Monitoring Network Processor operations Monitoring network processor operations 5760 6052 5696 6120 5760 6120 5696 6052 Displaying ATM statistics—Fast Ethernet Trunk module You can use the stats traffic|error|rate atm command to display ATM statistics for the interface of the Fast Ethernet Trunk module. In this release, the system is always enabled to collect ATM statistics.

  • Page 143: Obtaining Aal5 Statistics

    Monitoring Network Processor operations Monitoring network processor operations Clearing ATM statistics You can clear ATM statistics for all ports by using the stats clear atm all command or for a specific port by using appending the port number to the stats clear atm command.
  • Page 144 Monitoring Network Processor operations Monitoring network processor operations Statistics collection enabled : connection 22 With the following command, the system collects AAL5 statistics only for a specific connection, in this example, channel 22: fet-1/17> stats enable aal5 22 Statistics collection enabled : connection 22 Similarly, if you disable the system from collecting AAL5 statistics on all connections, statistics collection will also be disabled for any newly created channel.

  • Page 145: Optimizing System Performance

    Monitoring Network Processor operations Optimizing system performance To display AAL5 error statistics only for a specific connection, append the connection ID to the stats error aal5 command. For example: fet-1/17> stats error aal5 22 ConnID CRC SIZE-ERR UNDERFLOW MAXSDU IWUNDRUN IW MAXMRU Clearing AAL5 statistics The stats clear aal5 command clears AAL5 statistics.

  • Page 146: Overview Of System Profile Settings

    Monitoring Network Processor operations Optimizing system performance overall performance of the system (system performance) and to control the rate at which connections or service is restored to end-users (call performance). If only ATM PVC or SPVC connections are configured on the system, or if the system does not support an IP control module, the batch processing parameters are of no consequence.

  • Page 147: Adjusting Network Processor Fpp Memory Compaction

    Monitoring Network Processor operations Optimizing system performance performance are noticeably impacted when many updates must be communicated to the underlying hardware, as would occur, for example, after a system reset. A setting between 10-20 seconds allows a greater number of configuration changes to be batched together, which results in improved overall system and call performance.

  • Page 148: Configuring Queue Size From Controller To Lim

    LIM ASICs. The default system-integrity profile configuration for control modules enables continuous background testing of the control module ASIC. Lucent Technologies recommends that you do not disable this default. The default system-integrity configuration for LIM testing is a periodic integrity test for those LIMs that support it, and a periodic reset for earlier LIMs that are not equipped for integrity testing (STGR-LIM-AD-12 and STGR-LIM-SH-48).
  • Page 149 Monitoring Network Processor operations Maintaining ASIC Integrity [in SYSTEM-INTEGRITY:integrity-config[8]] enable-continuous-detection = yes detection-interval = 100 only-one-correction = yes correction-factor = 5 auto-correction-enable = yes interval-auto-correction = 600000 Parameter Setting enable-continuous- Enable/disable detection and correction in continuous detection mode. The default of yes is recommended for the control modules.
  • Page 150 Monitoring Network Processor operations Maintaining ASIC Integrity auto-correction-enable = yes interval-auto-correction = 600000 Parameter Setting Enable/disable detection and correction in continuous enable-continuous- mode. The default value is no for LIM slots, which detection allows sufficient correction for most LIMs while conserving system resources.

  • Page 151: Enabling Centralized Integrity Checks

    Monitoring Network Processor operations Maintaining ASIC Integrity Enabling centralized integrity checks In addition to the periodic automatic correction performed by the LIMs, you can enable centralized detection, which causes the control module to perform integrity tests on every LIM in the unit that is equipped for ASIC testing. If a LIM requires correction, the control module sends a message causing the LIM to reset its ASIC.
  • Page 153 Managing System Configuration and Memory Saving system configuration ........6-1 Displaying NVRAM usage statistics .

  • Page 154: Managing System Configuration And Memory

    Managing System Configuration and Memory Saving system configuration configuration on the secondary control module. For syntax information, see the Stinger Reference. Note To save passwords, you must have sufficient permissions to view password fields. (For a discussion of permissions, see “Understanding command permissions” on page 1-22.) Without this permission, passwords are not properly saved.

  • Page 155: Displaying Nvram Usage Statistics

    Managing System Configuration and Memory Displaying NVRAM usage statistics The sleep command specifies the number of seconds the system pauses before it executes the next command. You can specify a value between 0 and 60 seconds. The default setting is 5 seconds. NavisAccess™ management software users can introduce this command in a configuration file sent to a Stinger unit to time the saving of configuration profiles.

  • Page 156: How It Works

    Managing System Configuration and Memory Retaining configuration information after clearing NVRAM How it works You save the system IP address and other basic configuration that you would like to be restored for your system to the default.cfg file. You must save the default.cfg file to root directory or to root directory/current in flash memory.
  • Page 157 Managing System Configuration and Memory Retaining configuration information after clearing NVRAM Reqd Oper Slot Type { second-control-module } ( PRIMARY ) Slot state information is not available for secondary controller admin> ls ls Flash card 1: current/ 0 Tue Sep 24 22:27:14 2002 /current: stngrima.ffs 872522 Wed Jun 30 9:39:18 2004 Version 9.7.1...

  • Page 158: Issuing The Nvram Command On A System With A Default.cfg File

    Managing System Configuration and Memory Restoring or updating system configuration Enter the ls command from the secondary control module to verify that the default.cfg file has been saved to the desired directories on the secondary module. Issuing the nvram command on a system with a default.cfg file On a system configured with a default.cfg file, after you issue the nvram command, the system undergoes two reboot cycles.

  • Page 159: Updating The Configuration

    Managing System Configuration and Memory Extended profiling on control modules v2 or higher For example, to load a configuration file named unit.cfg from network host 10.8.7.2 to the PCMCIA flash card in slot 1, proceed as follows: admin> load config network 10.8.7.2 /unit.cfg To load the unitrel.tar file from a network host named host1, proceed as follows: admin>...

  • Page 160: When To Enable Extended Profiling

    Managing System Configuration and Memory Extended profiling on control modules v2 or higher versions v2 or higher. You can use the version command to display a control module’s version number. When to enable extended profiling Extended profiling is required on hosted Stinger systems with 4000 or more connections (PVCs).
  • Page 161 Managing System Configuration and Memory Extended profiling on control modules v2 or higher Enter the nvram -e command from the primary control module. For example: admin> nvram -e The system displays the following messages and a prompt: Warning 1, Note this command will RESET THE SYSTEM. Warning 2, if your boot load does not support extended profiles, you WILL Lose your configuration! Warning 3, once you switch to extended segments...

  • Page 162: Restoring Default Nvram Configuration

    Restore the saved configuration. Transferring code images between control modules On a Stinger FS, Stinger FS+, Stinger LS, or Stinger RT unit with dual control modules, you can transfer code images from one control module to the other using the loadmate command. Both control modules must be running TAOS 7.11.2 or later releases.

  • Page 163: Troubleshooting The Restore Process

    Managing System Configuration and Memory Troubleshooting the restore process admin> loadmate 1 2 You cannot run a load and loadmate operation or two loadmate operations simultaneously. Troubleshooting the restore process If the system terminates the process of loading a tar file, one of the following messages might appear: load aborted: not a tar image load aborted: a tar image, inconsistent with the specified load-type.

  • Page 164: Ftp Client Command-Line Interface

    Managing System Configuration and Memory Using FTP to transfer files To use the FTP client capability, your unit must have a file allocation table (FAT)- formatted flash memory card in its PCMCIA slot. The FTP client supports active connections only. In addition, you cannot cancel an FTP download or upload that is already in progress.

  • Page 165: Ftp Client Url Interface

    Managing System Configuration and Memory Using FTP to transfer files (149.52.26.125,7018) (2258239 bytes). 2258239 bytes recieved in 30 seconds 226 Binary Transfer complete. ftp> quit 221 Goodbye. The following command shows how to connect to an FTP server and specify a source IP address of 1.1.1.1: admin>...

  • Page 166: Username And Password Details

    Managing System Configuration and Memory Using FTP to transfer files Username and password details If a username or password includes any of the following characters, you must encode them using the hex values listed in the table that follows. Character Hex value Slash (/) At sign (@)

  • Page 167: Sample Ftp Url With No Url Path Or Local Directory

    Managing System Configuration and Memory Using FTP to transfer files Changes the directory on the Stinger unit to current in the first PCMCIA slot with a FAT-formatted flash card Opens an FTP session with host 135.254.196.191 Logs in with username foo and password bar Changes the remote system’s directory to /home/test/ Switches to ASCII mode Downloads file ftptest.txt to current...

  • Page 168: Using A Script To Configure A Stinger Unit

    Managing System Configuration and Memory Using a script to configure a Stinger unit Using a script to configure a Stinger unit The TAOS command-line interface allows you to create configuration scripts with a simple text editor and a Telnet client program with a Text Upload feature. This section briefly describes how you can use a script to make changes to the Stinger configuration.

  • Page 169: Loading Specific Module Images

    If the Stinger FS, Stinger FS+, Stinger LS, or Stinger RT unit contains two control modules, you must always load the same version of software to both control modules.

  • Page 170: Loading An Extracted Code Image

    Managing System Configuration and Memory Loading specific module images can cause an overflow in the PCMCIA flash card or built-in flash memory. To prevent a flash overflow, use the following procedure: Set the unknown-cards parameter in the load-select profile to skip. admin>...

  • Page 171: Managing Pcmcia Flash Cards

    Managing PCMCIA flash cards Managing PCMCIA flash cards Each control module on a Stinger FS, Stinger FS+, Stinger LS, and Stinger RT unit supports up to two PCMCIA flash memory cards. The Stinger MRT chassis contains built-in flash memory. Currently, the flash cards contain code for the modules and the control module.

  • Page 172: Compressing And Uncompressing Files On A Flash Card

    If necessary, download the code file again from the Lucent Technologies FTP server. To check the file system on the flash card in PCMCIA slot 1, or built-in flash memory, use the fsck command as shown in the following example: admin>...

  • Page 173: Optional Firmware (Centillium-Based Lims)

    Managing System Configuration and Memory Optional firmware (Centillium-based LIMs) Block Size: 512 (typical: 512) Blocks Per Cluster: 4 (typical: 1, may be powers of 2 up to 16) Reserved Blocks: 1 (typical: 1, but may be 0 - hundreds) Number of FATs: 2 (must be 2) Number of Root Directory Entries: 128 (typically betwn 32 and 224) Total Blocks: 13824 Media Descriptor: f0 (ignored)

  • Page 174: Verifying Firmware Version Of A Lim

    Managing System Configuration and Memory Optional firmware (Centillium-based LIMs) Reset the LIM to force the system to load optional firmware onto the LIM. For example: admin> reset After resetting the LIM, as the LIM initializes, the system checks the flash device first for any firmware binary.

  • Page 175: Log Messages For Firmware Download Events

    Managing System Configuration and Memory Upgrading bootprom on GE-COP, GE-OLIM, and IP RLIMs Log messages for firmware download events The following log messages report events related to the download of optional firmware: Event Log message LOG notice, Shelf 1, Slot 2, Time: 12:40:18-- Optional firmware was Firmware 0278 loaded successfully successfully loaded onto...

  • Page 176: Updating Bootprom On A Ge-Cop

    Managing System Configuration and Memory Upgrading bootprom on GE-COP, GE-OLIM, and IP RLIMs Updating bootprom on a GE-COP Once you have downloaded the GE-COP bootprom image onto the local file system, use the following instructions to update the GE-COP bootprom. Note the checksum of the bootprom before the update.

  • Page 177: Updating Bootprom On An Ip Rlim

    Managing System Configuration and Memory Upgrading bootprom on GE-COP, GE-OLIM, and IP RLIMs Do not power off or bounce this card while the programming is in progress or the pack will have to be sent back to the factory for repairs!!! !! WARNING !! !! WARNING !! existing Checksum CF73...

  • Page 178: Verifying Vendor Information

    Managing System Configuration and Memory Upgrading bootprom on GE-COP, GE-OLIM, and IP RLIMs Verifying vendor information The romupdate -v command displays bootprom vendor information. For example: golim-1/4> romupdate -v Flash Vendor 20 Flash ID E3 6-26 Stinger® Administration Guide...

  • Page 179: Administering The Snmp Agent

    Administering the SNMP Agent Overview of Stinger SNMP support ........7-1 Overview of the snmp profile .

  • Page 180: Requirement For A Soft Ip Address

    For an SNMP manager to access the Stinger SNMP agent, you must configure the Stinger unit with an IP address in the ip-global profile. For Stinger FS, Stinger FS+, Stinger LS, and Stinger RT units with redundant control modules, if you are using NavisAccess™...
  • Page 181 Administering the SNMP Agent Overview of the snmp profile Table 7-1. SNMP parameters and associated tasks (Continued) Parameter Task snmp-message-type Specifying the version of SNMP used by the Stinger SNMP agent. Specify one of the following values: ■ (the default)—The SNMP agent uses v1-and-v3 both SNMPv1 and SNMPv3 protocols.

  • Page 182: Activating The Snmp Agent

    Enabling read-write access and setting community strings Caution For security reasons, Lucent Technologies recommends that when you enable read-write access, you change the read-write community string from the well- known write value. By default, read-write access is disabled.

  • Page 183: Configuring Host Address Security

    Administering the SNMP Agent Securing the SNMP agent admin> set read-write-enabled = yes admin> set read-write-community = @456test! admin> write Configuring host address security You can also enforce host address authentication before the agent accepts SNMP requests. Address security is optional but recommended. By enabling the enforce- address-security parameter in the SNMP profile, you exclude SNMP access from host SNMP manager addresses other than those you have specified.

  • Page 184: Example Of Configuring Host Address Security

    Administering the SNMP Agent Securing the SNMP agent Parameter Setting Whether the unit accepts SNMPv1 messages only, SNMPv3 snmp-message- type messages only, or both SNMPv1 and SNMPv3 messages. This parameter applies only if the active parameter is set to yes in the same snmp-manager profile.

  • Page 185: Verifying The Snmpv3 License Is Enabled

    If the network-management license is not enabled, the Stinger unit silently discards incoming queries if the SNMP message is version 3. For information about software licenses, contact your Lucent Technologies sales representative. SNMPv3 USM features SNMPv3 security management provides Stinger units with the following features: Authentication—Provides data integrity and data origin authentication.
  • Page 186 Administering the SNMP Agent Securing the SNMP agent active-enabled = no read-write-access = no auth-protocol = md5-auth priv-protocol = no-priv auth-key = priv-key = Parameter Setting name Username of an SNMP management station. Messages sent to or from the SNMP station on behalf of this name use the security parameters specified in this profile.

  • Page 187: Generating Authentication Keys

    Administering the SNMP Agent Securing the SNMP agent Parameter Setting priv-protocol Enable/disable encryption of messages sent on behalf of the user to or from the SNMP engine, and if enabled, the type of privacy protocol to be used. Specify one of the following values: no-priv (the default)—No encryption is required and ■...

  • Page 188: Generating Privacy Keys

    Administering the SNMP Agent Securing the SNMP agent Generating privacy keys The snmpprivpass command automatically generates a privacy key for an SNMPv3 USM user. The command uses the following syntax: snmpprivpass username password Replace username with the SNMPv3 USM user for whom a privacy key is being generated, and password with the password used for generating the privacy key.

  • Page 189: Snmpv3 Notifications

    Administering the SNMP Agent Securing the SNMP agent admin> set security-level = auth-nopriv admin> write SNMPv3 notifications The Stinger unit authenticates and encrypts protocol data units (PDUs) as required by SNMPv3, and generates traps in SNMP version 2 (SNMPv2) Trap2 format. Depending on your configuration, a Stinger unit can send PDUs in SNMPv2 format or formats supported by TAOS 9.0-126 and earlier releases.
  • Page 190 Administering the SNMP Agent Securing the SNMP agent Configuring an snmpv3-notification profile Following are the snmpv3-notification parameters and their default settings: [in SNMPV3-NOTIFICATION/"" (new)] name* = "" active-enabled = no tag = "" type = Parameter Setting name Unique name for the profile, up to 16 characters. active-enabled Enable/disable generation of notifications.

  • Page 191: Configuring View-Based Access Control

    Administering the SNMP Agent Securing the SNMP agent Parameter Setting security-model Security model to use when generating SNMP messages. Specify one of the following values: v1 (the default)—SNMPv1 security model. This setting is ■ valid only if msg-proc-model is set to v1. v3-usm—SNMPv3 USM.

  • Page 192: Enabling Vacm

    Administering the SNMP Agent Securing the SNMP agent Enabling VACM To enable VACM, set the enable-vacm parameter to yes in the snmp profile. With this setting, each object in each incoming request (GET/SET/GETNEXT/GETBULK) and each object in the sysTrapOID of each outgoing trap (TRAP2) is verified for VACM access.

  • Page 193: Specifying View Names For Different Types Of Access

    Administering the SNMP Agent Securing the SNMP agent Specifying view names for different types of access To map a group name, context prefix, context name, security model, and security level to a view name, set parameters in the vacm-access profile. Following is a listing of the profile’s default values: [in VACM-ACCESS/{""...

  • Page 194: Defining Views

    Administering the SNMP Agent Securing the SNMP agent admin> list [in VACM-ACCESS/{ "" "" v1 no+ } (new)] access-properties* = { "" "" v1 no+ } active = no match-method = exact-match read-view-name = "" write-view-name = "" notify-view-name = "" admin>...

  • Page 195: Managing Snmp Interfaces

    Administering the SNMP Agent Managing SNMP interfaces Parameter Setting OID in dotted decimal format. The default is null. tree- properties: view-tree-oid For example, to define a view called view1 with an OID of 1.3.6.1.4.1.529, enter the following commands: admin> new vacm-view-tree admin>...

  • Page 196: Using The Admin-State-Perm-If Profile

    Administering the SNMP Agent Managing SNMP interfaces Using the admin-state-perm-if profile The admin-state-perm-if profile holds information about Stinger unit nailed interfaces. The system creates a profile for an active nailed interface and assigns it an interface index. For example: admin> dir admin-state-perm 20 06/10/1999 14:25:32 con4-1 20 06/10/1999 14:25:32 con4-2 20 06/10/1999 14:25:32 con4-3...
  • Page 197 Administering the SNMP Agent Managing SNMP interfaces 25 04/17/2003 13:35:21 { shelf-1 slot-7 70 } 25 04/17/2003 13:35:21 { shelf-1 slot-7 71 } 25 04/17/2003 13:35:21 { shelf-1 slot-7 72 } 25 04/17/2003 13:19:25 { shelf-1 first-control-module 32768 } 24 04/17/2003 13:19:25 { shelf-1 first-control-module 1 } 25 04/17/2003 13:19:25 { shelf-1 first-control-module 32769 } 24 04/17/2003 13:19:25 { shelf-1 first-control-module 2 } 25 04/17/2003 13:19:25 { shelf-1 first-control-module 32770 }...

  • Page 198: Viewing Snmp Interface Numbers

    Administering the SNMP Agent Managing SNMP interfaces Parameter Setting modem-table-index Modem table index assigned to the device whose state is stored in this profile. The system assigns a numeric value. Because the Stinger unit does not support modems, the value is always 0. desired-state Desired administrative state of the addressed device.

  • Page 199: Initiating Interface State Changes

    Administering the SNMP Agent Naming convention for SNMP-configured profiles { 1 18 3 } active { 1 18 4 } active { 1 18 5 } active Initiating interface state changes To enable or disable an SNMP interface, use the if-admin command with the -d option, and specify the interface number.

  • Page 200: Default Naming Convention

    Administering the SNMP Agent Naming convention for SNMP-configured profiles atmVcCrossConnectRowStatus = createAndGo Default naming convention For each cross-connect entry you create via SNMP, the system creates a connection profile and assigns the profile a name that specifies the slot and port with the low ifIndex value first, followed by the slot and port with the higher ifIndex value.

  • Page 201: Watchdogs, Alarms, And Traps

    Watchdogs, Alarms, and Traps Configuring SNMP watchdogs ........8-1 Defining alarms .
  • Page 202 Watchdogs, Alarms, and Traps Configuring SNMP watchdogs 28 11/19/2001 23:26:39 { fan fantray 3 } 36 11/19/2001 23:26:46 { relay cm-input-relay 1 } 36 11/19/2001 23:26:46 { relay cm-input-relay 2 } 36 11/19/2001 23:26:46 { relay cm-input-relay 3 } 36 11/19/2001 23:26:46 { relay cm-input-relay 4 } 36 11/19/2001 23:26:46 { relay cm-input-relay 5 } 36 11/19/2001 23:26:46 { relay cm-input-relay 6 } 36 11/19/2001 23:26:46 { relay cm-input-relay 7 }...

  • Page 203: Settings In A Watchdog-Config Profile

    Enabling a watchdog to monitor fan failure Stinger systems create watchdog-config profiles for each fantray assembly. On standalone Stinger FS, Stinger FS+, Stinger LS, or Stinger RT units the system creates three. On Stinger MRT units, a single watchdog-config profile is created.

  • Page 204: Watchdog Routines For Input Relays

    Watchdogs, Alarms, and Traps Defining alarms admin> set watchdog-name = fan1 Watchdog routines for input relays Stinger units installed with revision 2 control modules A, B, A-J, or C can monitor the status of up to seven devices. A Stinger MRT unit can monitor up to four remote devices.
  • Page 205 Watchdogs, Alarms, and Traps Defining alarms physical-address = { any-shelf any-slot 0 } action = { off off off 0 off 0 } [in ALARM/"":action (new)] alarm-led-minor = off alarm-led-major = off alarm-relay-minor = off alarm-relay-minor-duration = 0 alarm-relay-major = off alarm-relay-major-duration = 0 Parameter Setting...

  • Page 206: Sample Alarm Profile Configuration

    Watchdogs, Alarms, and Traps Defining alarms Parameter Setting physical-address Physical address of the entity that is being monitored by this alarm, as defined by its shelf, slot number, or item- number. The physical-address parameter applies only to line-state-change or slot-state-change events. Subprofile that specifies the actions that the Stinger unit action performs when it detects the event specified by the event...

  • Page 207: Working With Alarms

    Watchdogs, Alarms, and Traps Defining alarms admin> set action alarm-relay-major = on admin> set action alarm-relay-major-duration = 600 admin> set action alarm-relay-minor = off admin> set action alarm-relay-minor-duration = 0 admin> write -f By setting the physical-address parameter in an alarm profile to 0 0 0 (any shelf, any slot, any item), you can apply an alarm profile to the entire Stinger unit.

  • Page 208: Monitoring And Changing The Status Of Alarms (Alarm-Stat Profile)

    Watchdogs, Alarms, and Traps Defining alarms To display only the alarms for a particular line, specify the shelf, slot, and item number, as shown in the following example: admin> alarm -s 1 17 1 Type Address State Line Down { 1 17 1 } Active Monitoring and changing the status of alarms (alarm-stat profile) The alarm-stat profile enables you to monitor and change the status of alarms.

  • Page 209: Clearing Alarms

    Watchdogs, Alarms, and Traps Defining alarms Line Down { 1 17 1 } Acknowledged Line Down { 1 17 2 } Active Line Down { 1 18 1 } Active Line Down { 1 18 2 } Active Clearing alarms You can use the alarm command or the alarm-state parameter to clear an alarm.

  • Page 210: Table 8-1 Hosted Mrt Alarm Events

    Watchdogs, Alarms, and Traps Defining alarms HOST> set physical-address shelf = shelf-2 An alarm profile specific to a remote shelf is deleted if the remote-shelf-config profile for that shelf is deleted, and the corresponding alarms are cleared. Table 8-1 lists alarm events related to MRT shelves: Table 8-1.
  • Page 211 Watchdogs, Alarms, and Traps Defining alarms Table 8-2. Compact Remote alarm events Alarm event definition Event on remote shelf that triggers alarm over-temperature-relay A temperature sensor on the remote shelf indicates an over-temperature condition. The status is shown in the over-temperature setting of the remote-shelf- stat profile.

  • Page 212: Monitoring Environmental Conditions

    Watchdogs, Alarms, and Traps Defining alarms HOST> set enabled = yes HOST> set event = input-relay-open HOST> write -f If one of the alarms is triggered, the alarm action takes effect, and the remote-shelf- stat profile is updated. In addition, the status is accessible in the output of the alarm -s command.

  • Page 213: Clearing Alarms From Alarmactivetable And Alarmclearedtable

    Watchdogs, Alarms, and Traps Configuring SNMP traps Clearing alarms from alarmActiveTable and alarmClearedTable To clear the alarms in alarmActiveTable and alarmClearTable of the alarm MIB, disable the associated trap profile by setting the active-enabled parameter in the trap profile to no. If the trap profile is disabled, the alarm model table reports RowStatus as NOT_IN_SERVICE.

  • Page 214: Configuring The Trap Profile

    Watchdogs, Alarms, and Traps Configuring SNMP traps Configuring the trap profile You must also activate a trap and specify a destination host and host port. The following parameters in the trap profile configure these settings: Parameter Setting active-enabled Enable/disable the system to send traps to the host specified by this profile: yes—The system sends traps defined by this profile.

  • Page 215: Alarm Class Traps

    Watchdogs, Alarms, and Traps Configuring SNMP traps The following parameters in the trap profile represent the trap classes, shown with their default settings: [in TRAP/""] alarm-enabled = yes security-enabled = no port-enabled = no slot-enabled = no ospf-enabled Parameter Setting alarm-enabled Enable/disable an alarm class events.
  • Page 216 Watchdogs, Alarms, and Traps Configuring SNMP traps Table 8-3. Parameters that enable or disable traps in the alarm class (Continued) Event Parameter Trap Failure in a communication link between linkdown-enabled LinkDown the unit and the SNMP manager. Communication link between the unit and linkup-enabled LinkUp the SNMP manager came back up.
  • Page 217 Watchdogs, Alarms, and Traps Configuring SNMP traps Table 8-3. Parameters that enable or disable traps in the alarm class (Continued) Event Parameter Trap The value of the call-log-dropped- CallLogDroppedPkt callLoggingDroppedPacketCount variable pkt-enabled changed from 0 to 1 (which indicates that packets are being dropped) or from 1 to 0 (which indicates that packets are no longer being dropped) in the call-logging MIB.

  • Page 218: Security Class Traps

    Watchdogs, Alarms, and Traps Configuring SNMP traps Table 8-3. Parameters that enable or disable traps in the alarm class (Continued) Event Parameter Trap ascend-multicast- multicastLinkDownTrap A multicast group leave activity has link-trap-enabled occurred. ascend-cac-fail- cacfail Connection admission control (CAC) trap-enabled failure for an ATM connection has occurred.

  • Page 219: Port Class Trap

    Watchdogs, Alarms, and Traps Configuring SNMP traps Table 8-4. Parameters that enable or disable traps in the security class (Continued) Event Parameter Trap Specific port has exceeded the number of use-exceeded- useexceeded DS0 minutes allocated to it. enabled Maximum number of login attempts for a password-enabled password Telnet session has been exceeded.

  • Page 220: Ospf Class Traps

    Watchdogs, Alarms, and Traps Configuring SNMP traps If the slot-enabled parameter is set to no, the unit does not send the trap listed in Table 8-6. Table 8-6. Parameter that enables or disables traps in the slot class Event Parameter Trap slot-profile-change- Change of state in a host interface.
  • Page 221 Watchdogs, Alarms, and Traps Configuring SNMP traps Table 8-7. Parameters that enable or disable traps in the OSPF class (Continued) Event Parameter Trap ospf-if-rx-bad-packet OSPF packet has been received on a nonvirtual OSPF Trap 8 interface that cannot be parsed ospf-tx-retransmit-enabled OSPF packet has been retransmitted on a OSPF Trap 10...

  • Page 222: Traps Not Belonging To Any Class

    Watchdogs, Alarms, and Traps Configuring SNMP traps Table 8-7. Parameters that enable or disable traps in the OSPF class (Continued) Event Parameter Trap ospf-maxagelsa-enabled An LSA in the Stinger unit’s link-state database OSPF Trap 13 has reached its maximum age. ospf-lsdb-overflow-enabled The number of LSAs in the Stinger unit’s link- OSPF Trap 14...

  • Page 223: Monitoring Adsl Threshold Values

    Watchdogs, Alarms, and Traps Configuring SNMP traps In the following example, the host-name value is used only as a profile index, not to locate the actual host on the network. A community name is specified, security-class traps are added to the default alarm-class traps, and this host receives a trap if the link fails.

  • Page 224: Overview Of The Dsl-Threshold Profile Settings

    Watchdogs, Alarms, and Traps Configuring SNMP traps Overview of the dsl-threshold profile settings Following are the parameters for the dsl-threshold profile: Parameter Setting name Name of the dsl-threshold profile. To set the threshold times for an ADSL line, specify the name of a dsl-threshold profile in the thresh-profile parameter of the al-dmt profile.

  • Page 225: Lucent-Specific Adsl Threshold Traps

    Enable/disable InitFailureTrap. trap Lucent-specific ADSL threshold traps Lucent-specific versions of the ADSL threshold traps are listed below. If enabled, the system sends these traps in addition to the generic ADSL traps defined in RFC 2662. Trap Event Loss of Framing 15-minute interval...

  • Page 226: Enabling The System To Generate Adsl Threshold Traps

    Lucent-specific traps for the events listed in “Lucent-specific ADSL threshold traps” on page 8-25 (the ascend-adsl-threshold-traps-enabled parameter is set to no). You cannot configure the system to send only Lucent-specific ADSL traps. The following sample commands enable the system to generate generic ADSL threshold traps and Lucent-specific traps: admin>...

  • Page 227: Changing The Setting For The Desired-Trap-State Parameter Systemwide

    Watchdogs, Alarms, and Traps Configuring SNMP traps The system creates the following profiles for each LIM or trunk port present on the system: admin-state-phys-if—contains information about a port’s physical layer. ■ admin-state-perm-if—contains information about a port’s ATM layer--that is, ■ the dedicated (nailed) interfaces.

  • Page 228: Configuring Trap Sequencing And Heartbeat Traps

    Watchdogs, Alarms, and Traps Configuring SNMP traps [in system] link-phys-trap-state = trap-state-enabled Configuring trap sequencing and heartbeat traps Traps, like any other SNMP protocol data unit (PDU), use User Datagram Protocol (UDP) for transport. UDP by its nature does not guarantee delivery. In certain situations of network congestion and link failures, traps sent from a Stinger unit might be lost in transit and never reach the target element management system (EMS).

  • Page 229: Enabling Traps For Events On Remote Shelves

    Watchdogs, Alarms, and Traps Configuring SNMP traps heart-beat-trap-enabled = no Parameter Specifies notification-log- Whether SNMP traps (notifications) for this profile are logged. enable Specify yes to enable logging or no (the default) to disable it. notification-log- Maximum number of notification entries that can be held in limit the SNMP notification log.

  • Page 230: Stinger Trap Optimization

    Watchdogs, Alarms, and Traps Configuring SNMP traps Remote shelf watchdog profiles are created and deleted on the host depending on the operational state of the remote-shelf-stat profile for that shelf. HOST> dir watchdog 68 11/06/2003 11:59:46 { thermal shelf-controller 1 } 41 11/06/2003 11:59:53 { relay cm-input-relay 1 } 41 11/06/2003 11:59:53 { relay cm-input-relay 2 } 41 11/06/2003 11:59:53 { relay cm-input-relay 3 }...

  • Page 231: Optimizing The Number Of Traps Generated By The System

    Watchdogs, Alarms, and Traps Configuring SNMP traps Optimizing the number of traps generated by the system To configure a Stinger system to optimize the number of traps generated for slot status change, set the trap-optimization-enabled parameter in the trap profile to yes.

  • Page 232: Displaying Information About Notification Logs

    Watchdogs, Alarms, and Traps Configuring SNMP traps The following trap optimizations are made: ■ LinkUp and LinkDown traps are not generated unless ascend-link-down-trap- enabled and ascend-link-up-trap-enabled are set to no. AscendLinkUp traps are not generated when slots are initializing or during a ■...
  • Page 233 Watchdogs, Alarms, and Traps Configuring SNMP traps Table 8-9. Description of fields for the output of the nlmstat command (Continued) Field Specifies Replay Status of the replay function. Indicates whether replay is active (active) or not (idle). To display information about traps logged for a specific trap profile, enter the nlmstat command with the name of that trap profile.

  • Page 234: Configuring Traps For Cdr Device Failure

    Watchdogs, Alarms, and Traps Configuring traps for CDR device failure Table 8-10. Additional fields reported with the Ipaddress argument (Continued) Field Specifies Spec-trap Specific trap type. Version Trap version. Reported values can be v1 (SNMPv1) or v3 (SNMPv3). Configuring traps for CDR device failure In certain LIMs, data path failure sometimes occurs because of Clock and Data Recovery (CDR) device failure.

  • Page 235: Configuring Traps For Events Related To Cdr Failure

    Watchdogs, Alarms, and Traps Configuring traps for CDR device failure Configuring traps for events related to CDR failure To generate a trap for CDR failure, set the cdr-failure-trap-enabled parameter in the trap profile. By default, the sending of traps for CDR failure is disabled. For example: admin>...

  • Page 237: Working With Ip Traffic

    Working with IP Traffic Testing IP connectivity ..........9-1 Displaying the IP interface table.

  • Page 238: Displaying The Ip Interface Table

    Working with IP Traffic Displaying the IP interface table 64 bytes from 10.65.212.19: icmp_seq=0 ttl=255 time=0 ms 64 bytes from 10.65.212.19: icmp_seq=3 ttl=255 time=0 ms --- techpubs ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 0/0/0 ms To terminate the ping exchange at any time, press Ctrl-C.

  • Page 239: Displaying And Modifying Ip Routes

    Working with IP Traffic Displaying and modifying IP routes 1500 127.0.0.2/32 127.0.0.2 1500 127.0.0.3/32 127.0.0.3 wanabe 1500 127.0.0.3/32 127.0.0.3 local 65535 127.0.0.1/32 127.0.0.1 295498 295498 mcast 65535 224.0.0.0/4 224.0.0.0 134037 134037 tunnel0 1500 134.112.26.0/24 134.112.26.201 vr0_main 1500 134.112.26.201/32 134.112.26.201 sip0 65535 - ie1-2-1 1500 -...

  • Page 240: Modifying The Ip Routing Table

    Working with IP Traffic Displaying and modifying IP routes 127.0.0.0/8 669778 127.0.0.1/32 local 669778 127.0.0.2/32 669778 134.112.26.0/24 52758 669778 134.112.26.201/32 - local 18312 669778 222.222.222.1/32 local 507191 222.222.222.2/32 222.222.222.2 wan26 507191 224.0.0.0/4 mcast 2837 669778 224.0.0.1/32 local 669778 224.0.0.2/32 local 669778 224.0.0.9/32 local...

  • Page 241: Adding A Static Ip Route To The Routing Table

    Working with IP Traffic Tracing IP routes to the unit. RIP updates can add back any route that you remove using the iproute delete command. Also, the Stinger unit restores all routes listed in the ip-route profile after you reset the unit. For syntax information, see the Stinger Reference.

  • Page 242: Displaying Ip Protocol Statistics

    Working with IP Traffic Displaying IP protocol statistics The TTL value reaches the maximum value. (By default, the maximum TTL is set ■ to 30.) You can use the -m option to specify a different TTL. For example: admin> traceroute -m 60 techpubs traceroute to techpubs (10.65.212.19), 60 hops max, 0 byte packets 1 techpubs.abc.com (10.65.212.19) 0 ms 0 ms 0 ms The traceroute command sends three probes at each TTL setting.

  • Page 243: Displaying Ip Protocol Statistics

    Working with IP Traffic Displaying IP protocol statistics tcp: -Socket- Local Remote State 0 192.168.7.135.79 LISTEN 1 192.168.7.135.1723 LISTEN 2 192.168.7.135.23 LISTEN 4 192.168.7.135.23 172.20.32.137.42863 ESTABLISHED 9 192.168.7.135.23 206.65.212.10.1991 ESTABLISHED The output shows the queue depth of various UDP ports, as well as the total packets received and total packets dropped on each port.

  • Page 244: Displaying Ip Route Cache Information

    Working with IP Traffic Displaying IP route cache information 0 packets received forwarded 0 packets received with unknown protocols 0 inbound packets discarded 17310 packets delivered to upper layers 2084 transmit requests 0 discarded transmit packets 49 outbound packets with no route 0 reassemblies timeout 268 reassemblies required 12 reassemblies succeeded...

  • Page 245: Verifying Name Service Settings

    Working with IP Traffic Verifying name service settings The following example shows command output on the control module: admin> ipcache cache Address Gateway Ifname Sh/Sl/T 50.0.0.20 10.168.26.74 wan392 1/14/D 1524 20.0.0.40 20.0.0.40 ie1-3-1 1/3 /S 1500 Cache Limit 0 Cache Count 2 Cache over limit 0 No.packets 9 Mem Usage: Allocated 1k bytes Free block count 22 The following sample commands display output on a module:...

  • Page 246: Displaying The Dns Host Table

    Working with IP Traffic Displaying the DNS host table 10.103.0.2 00:C0:7B:7A:AC:54 DYN 0 0/0/599 23351 10.103.0.220 00:C0:7B:71:83:02 DYN 0 0/0/2843 23301 10.103.0.1 08:00:30:7B:24:27 DYN 0 0/0/4406 23352 10.103.0.8 00:00:0C:06:B3:A2 DYN 0 0/0/6640 23599 10.103.0.7 00:00:0C:56:57:4C DYN 0 0/0/6690 23676 10.103.0.49 00:B0:80:89:19:95 DYN 0 0/0/398 23674 The ARP table displays the following information:...

  • Page 247: Displaying The Ethernet Information

    Working with IP Traffic Displaying the Ethernet information 2: "rafael" 200.65.212.23 Feb 10 9:30:00 01 3: "donatello" 200.65.212.67 Feb 11 11:41:33 01 4: "wheelers" 200.65.212.9 Feb 12 8:35:22 01 The output of this commands contains the following fields: Field Indicates Local DNS Table Whether enabled is set to yes in the ip-global:dns- local-table subprofile.

  • Page 248: Displaying Ethernet Statistics And Error Counters

    Working with IP Traffic Displaying the Ethernet information {k.. ETHER XMIT: 12 of 161 octets 107E1350: 00 c0 80 89 03 d7 00 c0 7b 6b 9f d6 ..{k.. ETHER RECV: 12 of 60 octets To stop displaying the Ethernet statistics, specify 0 (zero) octets or use the debug off command, as shown in the following examples: admin>...

  • Page 249: Displaying Information About Igmp

    Working with IP Traffic Displaying information about IGMP Displaying information about IGMP The igmp command displays multicast information about Internet Group Membership Protocol (IGMP) groups and clients, if the Stinger unit is enabled for IP multicast forwarding. For syntax information, see the Stinger Reference. To display information about active multicast client group addresses and interfaces, use the -group option.
  • Page 250 Working with IP Traffic Displaying information about IGMP Field Indicates Counts Number of packets forwarded to the client, the number of packets dropped due to lack of resources, and the state of the membership. The state is displayed for debugging purposes. To list all active multicast clients, use the client argument.

  • Page 251: Displaying Wan Ip Interface Information

    Working with IP Traffic Displaying WAN IP interface information Displaying WAN IP interface information The following commands provide information about WAN IP interfaces. Displaying packets on WAN IP interfaces The wandisplay command displays all packets received from, or sent to any of the IP WAN interfaces.

  • Page 252: Displaying Wan Data During Connection Establishment For Users

    Working with IP Traffic Displaying WAN IP interface information You must first open a session with a LIM. The following sample commands open session with the module in slot 7 and activate the display of 7 octets of data per packet for the user tim: admin>...

  • Page 253: Overview Of The Ospf Command

    Monitoring OSPF routing Overview of the OSPF command ........10-1 10-1 Displaying general information about OSPF routing .

  • Page 254: Displaying General Information About Ospf Routing

    Monitoring OSPF routing Displaying general information about OSPF routing Option Displays internal OSPF internal routes. See “Displaying OSPF internal advertisements” on page 10-7. lsdb [area] OSPF link-state database summary for an area. If you do not specify the area option, the summary for the first configured area (or for the only defined area) is displayed.
  • Page 255 Monitoring OSPF routing Displaying general information about OSPF routing OSPF version: OSPF Router ID: 10.103.0.254 AS boundary capability: Attached areas: Estimated # ext. (5) routes: 65536 OSPF packets rcvd: 71788 OSPF packets rcvd w/errs: Transit nodes allocated: 812 Transit nodes freed: LS adv.

  • Page 256: Displaying The Ospf Database

    Monitoring OSPF routing Displaying the OSPF database Field Indicates Queue headers avail Available memory for queue headers. To prevent memory fragmentation, the Stinger unit allocates memory in blocks. The Stinger unit allocates queue headers from the memory blocks. When the Stinger unit frees all queue headers from a specific memory block, the unit returns the block to the pool of available memory blocks.
  • Page 257 Monitoring OSPF routing Displaying the OSPF database RTR 10.103.0.254 10.103.0.254 0x80000301 534 0x7066 RTR 10.104.0.1 10.104.0.1 0x800002ad 777 0xb98e RTR 10.104.0.2 10.104.0.2 0x80000193 1258 0x265a RTR 10.105.0.2 10.105.0.2 0x80000299 865 0x4295 RTR 10.105.0.3 10.105.0.3 0x800002e5 1057 0x4449 RTR 10.105.0.4 10.105.0.4 0x80000310 1585 0x5775 RTR 10.105.0.61 10.105.0.61...

  • Page 258: Displaying Ospf External Advertisements

    Monitoring OSPF routing Displaying the OSPF database The fields in the output contain the following information: Field Indicates Type Type of link as defined in RFC 2328, OSPF Version 2: Type 1 (RTR) are router LSAs that describe the collected ■...

  • Page 259: Displaying Ospf Internal Advertisements

    Monitoring OSPF routing Displaying the OSPF link-state database The output of this command is the same as for the ospf database command, with the exception of the type. The ospf ext command shows only type 5 LSAs. Displaying OSPF internal advertisements To display OSPF internal LSAs, include the internal option with the ospf command.
  • Page 260 Monitoring OSPF routing Displaying the OSPF link-state database RTR 10.105.0.3 10.105.0.3 0x800002e3 1032 0x4847 RTR 10.105.0.4 10.105.0.4 0x8000030e 1560 0x5b73 RTR 10.105.0.61 10.105.0.61 0x800002ac 1178 0xd32c RTR 10.105.0.200 10.105.0.200 0x80000261 194 0x4f23 RTR 10.123.0.8 10.123.0.8 0x800003ff 1045 0xf1ef RTR 10.123.0.254 10.123.0.254 0x800003ff 1149 0xb236 RTR 12.151.0.2...

  • Page 261: Displaying Ospf Lsas

    Monitoring OSPF routing Displaying OSPF LSAs Displaying OSPF LSAs To view detailed information about a link state advertisement (LSA), use the following syntax for the ospf command: ospf lsa area ls-type ls-id ls-orig The command requires that you include the first four fields of the LSA as listed in the database.

  • Page 262: Displaying The Ospf Routing Table

    Monitoring OSPF routing Displaying the OSPF routing table LS checksum: 0x8f32 LS length: Network mask: 255.255.0.0 Attached Router: 10.103.0.204 Attached Router: 10.103.0.254 Attached Router: 10.123.0.254 For information about the fields in the output of these commands, see RFC 2328. Displaying the OSPF routing table To display the OSPF routing table, include the rtab option with the ospf command.

  • Page 263: Displaying Information About Ospf Areas

    Monitoring OSPF routing Displaying information about OSPF areas Displaying information about OSPF areas To display information about OSPF areas, include the areas option with the OSPF command. For example: admin> ospf areas Area ID Authentication Area Type #ifcs #nets #rtrs #brdrs #intnr 0.0.0.0 Simple-passwd Normal The fields in the output contain the following information:...

  • Page 264: Displaying Ospf Interfaces

    Monitoring OSPF routing Displaying OSPF interfaces The fields in the output contain the following information: Field Specifies Internal route type. DType displays one of the following values: DType RTE (generic route), ASBR (AS border route), or BR (area border route). RType Internal router type.

  • Page 265: Displaying Information About A Specific Interface

    Monitoring OSPF routing Displaying OSPF interfaces Field Setting #adjs Number of adjacencies on the interface. DInt Number of seconds that the Stinger unit waits for a router update before removing the router’s entry from its table. The interval is called the dead interval. Displaying information about a specific interface To display detailed information for a specific interface, enter the ospf command with the intf option along with the interface IP address in dotted decimal notation.

  • Page 266: Displaying Ospf Neighbors

    Monitoring OSPF routing Displaying OSPF neighbors Field Setting Remote Address IP address of the remote end of a point-to-point (WAN) link. DR Priority Priority of the designated router. Hello interval Interval in seconds that the Stinger unit sends Hello packets (as defined in RFC 2328). Rxmt interval Retransmission interval (as described in RFC 2328).
  • Page 267 Monitoring OSPF routing Displaying OSPF neighbors 10.103.0.204 100.103.100.204 Full/DR ie1-7-4 10.123.0.254 100.103.100.123 Full/BDR ie1-7-4 10.102.0.2 10.102.0.2 Init/- 10.101.0.2 10.101.0.2 Full/- The fields in the output contain the following information: Field Setting Neighbor ID Address assigned to the interface. In the Stinger unit, the IP address is always the address assigned to the Ethernet interface.

  • Page 269: Monitoring Atm Networks

    Monitoring ATM and PNNI Monitoring ATM networks......... 11-1 11-1 Monitoring PNNI nodes .

  • Page 270: Using The Atm Status Window

    Monitoring ATM and PNNI Monitoring ATM networks Table 11-1. Profiles and commands for monitoring ATM networks (Continued) For information about See the profile or command Displaying ATM virtual link information atmvcl command atmvpl command on page 11-7 Displaying ATM virtual link cross-connect atmvcx command information atmvpx command on page 11-11...

  • Page 271: Determining Atm Line Status

    Monitoring ATM and PNNI Monitoring ATM networks Figure 11-1. Status window for ATM VCCs 6 Connections Status 0006 ADSL6-8 ATM 06/08 0 8000K Serial number: 10018000 Version 9.0-126.0 0005 15-0-18 ATM 18/01 0 45M Rx Pkt: 274505 0004 12-0-5 ATM 17/02 1 155M Tx Pkt: 239618 0003 11-0-5 ATM 17/01 1 155M...

  • Page 272: Displaying The Status Of Atm Internal Lines

    Monitoring ATM and PNNI Monitoring ATM networks Displaying the status of ATM internal lines The atminternallines command displays the status of ATM lines. For command options, see the Stinger Reference. To display statistics for all ATM lines, use the atminternallines -a command. For example: admin>...

  • Page 273: Displaying The Status Of Atm Trunk Modules And Their Connections

    Monitoring ATM and PNNI Monitoring ATM networks Displaying the status of ATM trunk modules and their connections The atmtrunkmgr -g connection-profile-name nailed-group display status of dedicated (nailed) groups. If the code is 1, there is an active nailed group to connect to. If the interface is not operational, the return code is 0 (zero).

  • Page 274: Checking The Status Of A Terminating Pvc

    Monitoring ATM and PNNI Monitoring ATM networks current-state = pvc-data-transfer vcc-members = [ { shelf-1 slot-10 47 0 35 } { shelf-1 slot-2 1 0 77 } ] Parameter Setting circuit-name Name of the PVC, which is the value of the station parameter in a local profile or the User-Name attribute in a RADIUS profile.

  • Page 275: Displaying Atm Virtual Link Information

    Monitoring ATM and PNNI Monitoring ATM networks debug privileges. For information on enabling debug privileges see “Enabling debug permissions” on page A-1. Note You cannot enter the atmvccmgr command from the secondary control module. To display status information for all ATM connections, use the -a option: admin>...
  • Page 276 Monitoring ATM and PNNI Monitoring ATM networks With the -a option, both commands display information about all configured ATM VCLs or VPLs and their status. The -s and -p options display the same information as the -a option, but restrict the output to links on a specific slot or slot-port combination.
  • Page 277 Monitoring ATM and PNNI Monitoring ATM networks Conn Kind = pvc Cast Type = p2p AAL Type = aal5 AAL5 Rx SDU Size = 9188 AAL5 Tx SDU Size = 9188 AAL5 Encap Type = llcEncapsulation The following sample command shows information about a VPL on slot 18, port 1 that is cross-connected to another VPL in the system: admin>...

  • Page 278: Displaying Routed And Bridged Connections On A Port

    Monitoring ATM and PNNI Monitoring ATM networks Field Indicates AAL5 Encap Type Type of encapsulation used for the AAL5 terminating link. This field is not displayed for a cross-connected link. The following sample command shows VCL information for the Stinger unit. The output shows the number of terminating PVCs, PVC segments without cross- connections (created by SNMP), and PVC segments with cross-connections.

  • Page 279: Sample Commands Displaying Cross-Connected Links

    Monitoring ATM and PNNI Monitoring ATM networks termqwertyuiopa down termzxcvbnmlkj Totals: Down PVC Terminate The following command displays information about a terminating VPL on port 9 of slot 3: admin> atmvpl -t 1 3 9 Intf Shelf Slot Port Vpi Kind OStatus CircuitName down termvp...

  • Page 280: Displaying Spvc Information

    Monitoring ATM and PNNI Monitoring ATM networks The following examples show the output of the atmvcx -a and atmvpx -a commands if the shelf-controller-type parameter in the system profile is set to standalone: admin> atmvcx -a High Profile Kind Intf|Slot|Port|VPI|VCI|Oper Intf|Slot|Port|VPI|VCI|Oper Permanent VC X-Connects: 13456789-123 pvc 19...
  • Page 281 Monitoring ATM and PNNI Monitoring ATM networks With no options on the command line, the commands display the usage statement. With the -a option, they display information about all configured virtual-channel- switching or virtual-path-switching SPVCs and their status. The -s and -p options enable you to display the same information as the -a option, but to restrict the output to links on a specific slot or slot-port combination.

  • Page 282: Displaying Spvc Target Atm Addresses

    Displaying SPVC target ATM addresses Each trunk port and LIM port that supports ATM has an associated ATM interface. On a Stinger unit enabled with the Lucent Technologies, Inc. Private Network-to- Network Interface (PNNI) license, the system assigns each ATM interface with a unique soft PVC (SPVC) target address.

  • Page 283: Monitoring Failing Spvcs

    Monitoring ATM and PNNI Monitoring ATM networks With the -a option, the system shows all target SPVC addresses of all ATM interfaces. For example: admin> spvcshow -a Slot/Port Stat SPVC ATM address 2 / 1 up 39:84:0f:80:01:bc:72:00:01:09:7c:9e:00:ff:7c:92:b7:3d:01:00 2 / 2 down 39:84:0f:80:01:bc:72:00:01:09:7c:9e:00:ff:7c:92:b7:3d:02:00 2 / 3 down 39:84:0f:80:01:bc:72:00:01:09:7c:9e:00:ff:7c:92:b7:3d:03:00 2 / 4 down 39:84:0f:80:01:bc:72:00:01:09:7c:9e:00:ff:7c:92:b7:3d:04:00 2 / 5 down 39:84:0f:80:01:bc:72:00:01:09:7c:9e:00:ff:7c:92:b7:3d:05:00...

  • Page 284: Displaying Cac Bandwidth Allocation Statistics

    Monitoring ATM and PNNI Monitoring ATM networks The following sample command displays ATM statistics for interface 11: admin> atmsig -i 11 Physical Address = { 1 17 1 } Interface = 11 SSCOP Connections Events = 0 SSCOP Errored PDUs = 0 Received Call Setup Attempts = 0 Transmitted Call Setup Attempts = 7 Received Unavailable Routes = 0...
  • Page 285 Monitoring ATM and PNNI Monitoring ATM networks Available Guaranteed B/W : 4000 DN STREAM Total B/W Kbits/sec : 155520 Guaranteed B/W Kbits/sec : 155520 Allocated Guaranteed B/W : 40000 Available Guaranteed B/W : 115520 BANDWIDTH INFORMATION FOR SLOT 2 UP STREAM Total B/W Kbits/sec : 70000 Guaranteed B/W Kbits/sec...
  • Page 286 Monitoring ATM and PNNI Monitoring ATM networks spvc-1-1-1-1.2 lim-1-1-ckt-5 lim-1-1-ckt-5 spvc-1-1-1-1.3 spvc-1-1-1-1.3 lim-1-1-ckt-6 lim-1-1-ckt-6 spvc-1-1-1-1.4 spvc-1-1-1-1.4 lim-1-1-ckt-7 lim-1-1-ckt-7 lim-1-1-ckt-8 lim-1-1-ckt-8 To display bandwidth allocation for a specific service category, use the -c option with one of the following values for service category: 0 for constant bit rate (CBR), 1 for real-time variable bit rate (RT-VBR), 2 for Nonreal-time variable bit rate (NRT-VBR), or 3 for unspecified bit rate (UBR).

  • Page 287: Displaying Atm Connection Failures

    Monitoring ATM and PNNI Monitoring ATM networks admin> atmcacstat -a Connection Stream Peak Rate Sustainable Rate Count rcc-17-1-0-18 NRT-VBR NRT-VBR rcc-18-2-0-18 NRT-VBR NRT-VBR sig-17-1-0-5 NRT-VBR NRT-VBR sig-17-2-0-5 NRT-VBR NRT-VBR sig-18-1-0-5 NRT-VBR NRT-VBR sig-18-2-0-5 NRT-VBR NRT-VBR rcc-17-2-0-18 NRT-VBR NRT-VBR rcc-18-1-0-18 NRT-VBR NRT-VBR Displaying ATM connection failures To display information about ATM connection failures, use the...

  • Page 288: Monitoring Pnni Nodes

    Monitoring ATM and PNNI Monitoring PNNI nodes ATMQOS416 RT_VBR 1000 1000 For details about the output of this command, see the Stinger Reference. To display all connections that use a specified QoS name, use the -c option. For example: admin> atmqos -c atmqos416 vc-11-1-0-35 Total Number Of Connections : 1 To display QoS statistics for a specific QoS name, use the -d option.

  • Page 289: Verifying The Pnni Link

    Monitoring ATM and PNNI Monitoring PNNI nodes Table 11-3. Commands and profiles for monitoring PNNI operations (Continued) Command or profile Used for pnniptsestatus command “Displaying the PNNI routing table” on page 11-35 pnnirouteBase command “Displaying PNNI interface information” on pnnireachableaddr command page 11-23 pnnirouteBase command “Displaying PNNI interface information”...
  • Page 290 Monitoring ATM and PNNI Monitoring PNNI nodes LowestVersion = Version1point0 DtlCountOriginator DtlCountBorder CrankbackCountOriginator = 0 CrankbackCountBorder AltRteCountOriginator AltRteCountBorder RteFailCountOriginator = 148 RteFailCountBorder RteFailUnreachOrg = 148 RteFailUnreachBrdr Field Indicates HighestVersion Highest version of the PNNI protocols supported in the unit. LowestVersion Lowest version of the PNNI protocols supported in the unit.

  • Page 291: Displaying Pnni Interface Information

    Monitoring ATM and PNNI Monitoring PNNI nodes Field Indicates RteFailUnreachBrdr Number of times the unit failed to compute a viable partial DTL stack as entry border node because the target of the path calculation was unreachable. This value indicates those calls that were cleared or cranked back with cause 2 (specified transit network unreachable) or cause 3 (destination unreachable) in the cause information element.

  • Page 292: Displaying Information About Pnni Logical Links

    Monitoring ATM and PNNI Monitoring PNNI nodes Displaying information about PNNI logical links A PNNI logical link is a logical representation of the connectivity between two logical nodes, including the physical link and virtual path connection. The pnnilinkdisplay command displays information about the operation of logical links attached to the local PNNI node and the relationship to nodes on the other end of the links.
  • Page 293 Monitoring ATM and PNNI Monitoring PNNI nodes Field Indicates IntIndex Entry number in the interface table for the interface to which the logical link corresponds. The value is valid only for LinkType values of Unknown, Lowest Level Horizontal Link, and Lowest Level Outside Link. All other link types display a zero value.
  • Page 294 Monitoring ATM and PNNI Monitoring PNNI nodes Field Indicates CommonPeerGroupId Peer group ID of the lowest-level common peer group in the hierarchy of the neighboring node and the local node. For horizontal links, or when the link type or common peer group is not yet known, the field displays zero.
  • Page 295 Monitoring ATM and PNNI Monitoring PNNI nodes RemoteNodeId RmtPortId 60:a0:39:84:0f:80:01:bc:72:00:01:31:a3:99:38:ff:b6:ca:99:00:00:00 MapType PeerGroupId HorizontalLink 60:39:84:0f:80:01:bc:72:00:01:31:a3:99:00 AggrToken VpCap PtseId MTag 1118482 AdmWt CLR0 CLR0+1 5040 366792 366792 6890 Unused Rtvbr Out 5040 366792 366792 6890 Unused NrtVbr Out 5040 366792 366792 6890 Unused 5040 366792...

  • Page 296: Displaying Details About Neighbor Nodes

    Monitoring ATM and PNNI Monitoring PNNI nodes Field Indicates VPCap A value of 1 indicates that virtual path connections (VPCs) can be established across the PNNI entity. A value of zero indicates that VPCs cannot be established. PtseId PNNI state topology element (PTSE) ID for the PTSE that contains the information group(s) describing the PNNI entity.

  • Page 297: Displaying Local Node Information

    Monitoring ATM and PNNI Monitoring PNNI nodes Full PeerNodeId 60:a0:39:84:0f:80:01:bc:72:00:01:31:a3:99:38:ff:b6:ca:99:00:00:00 PeerSvcRccIdx PeerRcvDbSums PeerXmtDbSums PeerRcvPtsps PeerXmtPtsps PeerRcvPtseReq PeerXmtPtseReq PeerRcvPtseAck PeerXmtPtseAck Field Indicates Node PNNI node index. Only node index 1 is currently supported. PeerState State of the local node’s neighboring peer state machine associated with PeerNodeId field.
  • Page 298 Monitoring ATM and PNNI Monitoring PNNI nodes With no options on the command line, the command identifies the node and displays some state information. Following is some sample output: admin> pnninodedisplay Node NodeId 60:a0:39:84:0f:80:01:bc:72:00:01:31:a3:99:30:ff:18:dd:98:00:00:00 OperStat DBOverload Ptses With the -d option, the command displays many additional fields about the configuration and current state of the logical node.

  • Page 299: Displaying Information About Other Nodes

    Monitoring ATM and PNNI Monitoring PNNI nodes Field Indicates AdminStatus Administrative status of the node. Up indicates that the node is allowed to become active. Down means the node is inactive and is not allowed to become active. DomainName Name of the node’s PNNI routing domain. All lowest-level nodes with the same domain name are presumed to be connected.
  • Page 300 Monitoring ATM and PNNI Monitoring PNNI nodes RestrictedTransit NodeComplexRep RestrictedBranching NodeDatabaseOverload IAMLeader LeadershipPriority PreferredPgl 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 ParentNodeId 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 ParentAtmAddress 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 NodeParentPeerGroupId 00:00:00:00:00:00:00:00:00:00:00:00:00:00 ParentPglNodeId 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 Node MapNodeId 60:a0:39:84:0f:80:01:bc:72:00:01:31:a3:99:38:ff:b6:ca:99:00:00:00 PeerGroupId 60:39:84:0f:80:01:bc:72:00:01:31:a3:99:00 NodeAtmAddress 39:84:0f:80:01:bc:72:00:01:31:a3:99:38:ff:b6:ca:99:00:00:00 RestrictedTransit NodeComplexRep RestrictedBranching NodeDatabaseOverload IAMLeader LeadershipPriority PreferredPgl 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 ParentNodeId 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 ParentAtmAddress 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 NodeParentPeerGroupId...

  • Page 301: Displaying The Pnni Topology Database

    Monitoring ATM and PNNI Monitoring PNNI nodes ParentPglNodeId 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 Field Indicates Node PNNI node index. Only node index 1 is currently supported. MapNodeId PNNI node ID of the node being represented. PeerGroupId PNNI peer group ID of the node being represented. NodeAtmAddress ATM address of the node being represented.
  • Page 302 Monitoring ATM and PNNI Monitoring PNNI nodes Node PtseId (hex) SeqNum LifeTime CheckSum PtseType 3600 11143 NodalInfo 3600 51918 InternalAddr 3600 46441 HorizontalLink 3600 7165 InternalAddr 3600 52636 InternalAddr 3600 15160 InternalAddr 3600 61997 InternalAddr 3600 62930 InternalAddr 3600 25143 InternalAddr 3600 12231...

  • Page 303: Displaying The Pnni Routing Table

    Monitoring ATM and PNNI Monitoring PNNI nodes Field Indicates PtseId Hexadecimal value of the PTSE identifier assigned to the PTSE by the originating node. SeqNum Sequence of the entry in the local topology database. LifeTime Remaining lifetime in seconds, for the given PTSE as stated in the topology database.
  • Page 304 Monitoring ATM and PNNI Monitoring PNNI nodes ReachableAddr 39:84:0f:80:01:bc:72:00:01:18:dd:98:00:ff:18:dd:98:00:f2 AdvertisedNodeId 60:a0:39:84:0f:80:01:bc:72:00:01:31:a3:99:30:ff:18:dd:98:00:00:00 PortId Index PrefixLength (bits) 36610 ReachableAddr 39:84:0f:80:01:bc:72:00:01:18:dd:98:00:ff:f7:48:cf:3b:01 You can use a command option to display reachable addresses from a specified node or ATM address. For example, the following output shows addresses that are reachable from the specified ATM prefix: admin>...

  • Page 305: Chapter 12 Diagnostic Testing

    Diagnostic Testing OAM testing ........... . 12-1 12-1 Internal and external diagnostic tests .

  • Page 306: Using The Oam Command And Atm-Oam Profile To Run Oam Tests

    Diagnostic Testing OAM testing control module forwards the F4 response to the incoming port on the trunk module or line interface module (LIM). Note The Stinger unit does not support F4 OAM end-point tests for virtual path connections (VPCs) because the connection does not terminate on the Stinger unit. OAM F5 cells operate at the virtual circuit level and use the payload type indicator (PTI) field to distinguish between data and OAM cells.

  • Page 307: Overview Of The Oam Command

    Diagnostic Testing OAM testing Overview of the oam command You can use the oam command to run F4 and F5 OAM loopback and continuity check tests and to display OAM entries. You use the command as follows: To run loopback tests, use the following command syntax: ■...

  • Page 308: Overview Of The Atm-Oam Profile

    Diagnostic Testing OAM testing Option Description Displays OAM entries generating CC cells. cc generating Displays OAM entries monitoring CC cells. cc monitoring Displays OAM entries in activating state. cc activating Displays OAM entries in deactivating state. deactivating Overview of the atm-oam profile Running an OAM test using the atm-oam profile has the following capabilities and limitations: ■...
  • Page 309 Diagnostic Testing OAM testing This combination causes the unit to test all the VPI-VCI pairs configured on the specified slot. If vci is set to 32769, the test is an F4 loopback. Otherwise, the test is an F5 loopback. shelf=number, slot=number, port=number, vpi=32768, vci=32769 or vci=32768 ■...
  • Page 310 Diagnostic Testing OAM testing Parameter Setting error-threshold Threshold for the number of loopback cells that can be lost. If the number of cells lost becomes equal to or greater than this value, a trap is generated. Specify a number from 0 through 10. The default, 0 (zero), disables this trap.

  • Page 311: Enabling F4 Oam On A Lim

    Diagnostic Testing OAM testing Following is the parameter description for vc-oamf4-support: Parameter Description Enables/disables specific F4 segment and end-to-end OAM vc-oamf4- processing on a Stinger VC-switching VPI. With the default yes support N setting, F4 segment and end-to-end processing for the specified VC-switching VPI is enabled.
  • Page 312 Diagnostic Testing OAM testing If the lim-vc-f4oam-support parameter is set to yes, F4 OAM entries are created on the LIM port for the VP-switching VPI. The Total Active Oam Channels field in the output of the oam -e shows the F4 OAM entries. admin>...

  • Page 313: Continuity Check And Monitoring

    Diagnostic Testing OAM testing Total Active Oam Channels=1 Continuity check and monitoring F4 and F5 OAM continuity tests can be initiated as follows: Locally, using the command-line interface (CLI). ■ Remotely, a network peer can send activation/deactivation requests to initiate a ■...

  • Page 314: Deactivating A Continuity Check Test

    Diagnostic Testing OAM testing Table 12-1 lists the possible directions that the remote peer can specify and the resulting action that the Stinger takes. Table 12-1. Direction specified by the remote peer and the results Remote request Result direction A-to-B From the Stinger perspective, the B-to-A direction.

  • Page 315: Running F4 And F5 Continuity Tests Using The Oam Command

    Diagnostic Testing OAM testing OAM: CC was activated or is being stopped by another application use oam -e 18 2 0 4 for more information F4-E2E(83b99ba0:3505.0.4) loop(Tx=0, Rx=0) 83b99ba0:F=NORMAL CC(R=NONE:G=ACTIVE M=STOP A=DEACTG D=MON) In the preceding example, the activation/deactivation status reported by the A field shows that the status is deactivating.

  • Page 316: Running F5 Continuity Tests Using The Atm-Oam Profile

    Diagnostic Testing OAM testing The following command stops the preceding test: admin> oam -C 17 2 0 35 e - To instruct the Stinger unit to perform an F5 segment continuity test from a T1000 module in slot 3, over VCI 36, proceed as follows: admin>...
  • Page 317 Diagnostic Testing OAM testing The following sample commands run an F5 OAM segment loopback test from a Stinger MRT unit to the CPE connected to it on port 12. admin> open 1 1 mrtdmt-1/1> oam -e OAM Entry list Entry=3f0ca0, Linear Port=12 vpi=8, vci=3 state=Up loopTx=0 loopRx=0 Segment Continuity=READY End2End Continuity=READY isVpc=No Entry=3f0de0, Linear Port=12 vpi=8, vci=4 state=Up loopTx=0 loopRx=0 Segment Continuity=READY End2End Continuity=READY isVpc=No...

  • Page 318: Running F4 And F5 Loopback Tests Using The Atm-Oam Profile

    Diagnostic Testing OAM testing Entry=478d60, Linear Port=28 vpi=0, vci=35 state=Up loopTx=0 loopRx=0 Segment Continuity=READY End2End Continuity=READY isVpc=No hdsl2-1/4> oam -l 25 0 35 s 1 hdsl2-1/4> Sending F5 OAM segment loopback cell, Id=0 Received our F5 OAM segment loopback cell, Id=0 OAM: received our F5 OAM segment loopback #0 Running F4 and F5 loopback tests using the atm-oam profile To run an F4 or F5 loopback test, you set the parameters in the loopback-config...

  • Page 319: Specifying That A Trap Is Sent

    Note Running several prolonged concurrent OAM test sessions using the oamloop command sometimes causes inaccurate test results. To prevent this situation, Lucent Technologies strongly recommends that you conduct only one OAM test session at a time using this software version. If you must conduct simultaneous OAM test sessions, limit them to no more than eight.

  • Page 320: Configuring Loopback On Oc3, E3, And Ds3 Interfaces

    Diagnostic Testing OAM testing cells. You can optionally specify the number of cells and the transmission interval. For details about oamloop syntax, see the Stinger Reference. For example, the following command sends 10 end-to-end loopback cells to a trunk module in slot 2 on VPI 1, VCI 32: admin>...

  • Page 321: Displaying Oam Entries

    Diagnostic Testing OAM testing Displaying OAM entries You can use the oam -e and oam -q commands enable you to display OAM entries in a Stinger system. The oam -e command displays details about OAM entries that exist in the system. You can display OAM entries, for a specific slot, port, VPI, or VCI.
  • Page 322 Diagnostic Testing OAM testing Element Indicates Continuity check monitoring state. Possible states are stopped, normal, and LOC. Continuity check activation/deactivation state. Possible states are ready, active, activating (ACTG), and deactivating (DEACTG). Provisioned direction. Using the oam -e command The syntax of the oam -e command is as follows: oam -e [slot] [port] [vpi] [vci]|-p Following is an example of an F4 segment flow.
  • Page 323 Diagnostic Testing OAM testing Displaying entries with no defects To display entries with no defects, use the oam -q fault normal command. For example: admin> oam -q fault normal OAM Entry list F: fault state CC: continuity information R: Continuity requester G: CC generation state M: CC monitoring state A: CC Activation/Deactivation state...
  • Page 324 Diagnostic Testing OAM testing R: Continuity requester G: CC generation state M: CC monitoring state A: CC Activation/Deactivation state D: Direction. P: provisioned direction. C: current direction F4-E2E(836999e0:3505.0.4) loop(Tx=0, Rx=0) 836999e0:F=RDI CC(R=NONE:G=STOP M=STOP A=READY D(P=DEF C=DEF)) Total matching Oam Channels=1 Displaying LOC defects To display entries with LOC defects, use the oam -q fault loc command.

  • Page 325: Fault Reporting And Alarms

    Diagnostic Testing OAM testing F: fault state CC: continuity information R: Continuity requester G: CC generation state M: CC monitoring state A: CC Activation/Deactivation state D: Direction. P: provisioned direction. C: current direction F5(82048320:3505.0.100) E2E=FALSE loop(Tx=0, Rx=0) SEG:82048320:F=LOC CC(R=NONE:G=ACTIVE M=LOC A=ACTIVE:D(P=DEF C=2WAY)) Total matching Oam Channels=1 Fault reporting and alarms Stinger systems use SNMP traps to report OAM changes for an OAM end point.

  • Page 326: Internal And External Diagnostic Tests

    Diagnostic Testing Internal and external diagnostic tests Internal and external diagnostic tests You can use an internal diagnostic test (IDT) to identify problems that might occur during data transfer between the control module and LIMs. If you activate an IDT for a line, the control module generates a data stream internally and sends it to that line.

  • Page 327: Running An External Diagnostic Test (Edt) Feature

    Diagnostic Testing Internal and external diagnostic tests Parameter Setting Status of an internal diagnostic test on the line. (This idt-operation- parameter is read-only.) By default, this parameter shows state stopped (the test is inactive). When the line is undergoing internal diagnostic testing, this parameter shows active. Number of messages sent from the LIM to the control module.

  • Page 328: Digital Loopback

    Diagnostic Testing Internal and external diagnostic tests [in HDSL2/{ shelf-1 slot-2 1 }:line-config] loop-back = none Parameter Setting loop-back Whether the line passes normal data or is in loopback mode. Specify one of the following values: none (default)—The line is not used for loopback testing and ■...

  • Page 329: Running Built-In Self Tests (Bists) On Dsl Ports

    Diagnostic Testing Internal and external diagnostic tests The following sample commands put a line into analog loopback mode: admin> read hdsl2 {1 1 1} HDSL2/{ shelf-1 slot-1 1 } read admin> set loop-back = analog admin> write Running built-in self tests (BISTs) on DSL ports This test verifies proper operation of a specific DSL port.

  • Page 330: Relay Alarm Testing

    Diagnostic Testing Relay alarm testing Relay alarm testing You can use the debug-level inputrelaytest command to simulate the status of relays to generate relay alarm and trap conditions for testing. When you use the inputrelaytest command, actual alarms on the system associated with relays are overwritten by this command and are not restored until you reset the system.
  • Page 331 Diagnostic Testing Relay alarm testing admin> write The following commands create the trap profile for the specified events: admin> new trap relay admin> community-name = public admin> host-address = 135.17.134.31 admin> host-port = 2345 The following commands enable the test mode. During the test, the system generates a warning log message every minute.

  • Page 332: Displaying The Status Of Input Relays

    Diagnostic Testing Configuring a bit-error rate test (BERT) LOG emergency, Shelf 1, Controller-1, Time: 10:45:36-- Fri May 23 10:45:36 2003 - ALARM: Input Relay No. 5 CLOSED LOG emergency, Shelf 1, Controller-1, Time: 10:45:36-- Fri May 23 10:45:36 2003 - ALARM: Input Relay No. 6 CLOSED LOG emergency, Shelf 1, Controller-1, Time: 10:45:36-- Fri May 23 10:45:36 2003 - ALARM: Input Relay No.

  • Page 333: Testing Dsl Copper Loops

    Diagnostic Testing Testing DSL copper loops If the CPE and Stinger unit are connected and both are enabled for bit-error rate testing, the test runs between the two systems. If the test is enabled, the Stinger unit initiates the test by sending an embedded operations channel (EOC) message to the CPE to place its port into loopback mode.

  • Page 334: Using The Line-Tests Profile

    Diagnostic Testing Testing DSL copper loops generation feature, you can send a trace tone to up to 48 ports simultaneously. The tone is obtained from an external generator connected to the external test terminal on a path selector module (PSM) or copper loop test (CLT) module. You can use the line-tests profile or the isolate and gen-tone commands to perform these tests.

  • Page 335: Galvanic Isolation Test

    Diagnostic Testing Testing DSL copper loops Parameter Heading test-terminal CLT module or PSM terminal where the test tone is applied. Specify external-tester-terminal or aux- tester-terminal. activate-test Enable/disable a test. A value of yes disconnects any existing calls and begins the test. A value of no reconnects any disconnected calls and stops the test.

  • Page 336: Using The Isolate Command

    Diagnostic Testing Testing DSL copper loops Using the isolate command You use the isolate command to isolate either a range of ports or a list of individual ports. Its syntax is as follows: For a range of ports: ■ isolate shelf slot start-port - end-port For individual ports: ■...

  • Page 337: Using The Gen-Tone Command

    Diagnostic Testing Testing DSL copper loops admin> write Using the gen-tone command You can use the gen-tone command to apply test tones on either a range of ports or a list of individual ports. Its syntax is as follows: ■ For a range of ports: gen-tone shelf slot ext|aux startport - endport For individual ports:...

  • Page 339: Enabling Debug Permissions

    Lucent Technologies development engineers. For this reason, Lucent does not guarantee the completeness of the list of debug commands published for a given release, or descriptions of their functionality.

  • Page 340: Enabling Debug Output

    When you are logged into a Stinger unit with debug privileges, the interface might display normally unavailable parameters and commands, some of which are not configurable in certain situations. Therefore, Lucent Technologies recommends that you create a special profile for debugging purposes, and use that profile only when you are debugging the Stinger unit.

  • Page 341: Summary Of Common Debug Commands

    Using Debug Commands Summary of common debug commands ifmgr [up|down] [ifNum|ifName] Summary of common debug commands Debug commands allow you to monitor and diagnose different areas of Stinger functionality. Table A-1 lists common debug commands. To use any of these commands, you must have debug permissions and the debug facility enabled.

  • Page 342: Displaying Ip Control Module Network Processor Information

    Using Debug Commands System and devices debugging Displaying IP control module network processor information The syntax for the info np command is as follows: info np option Setting for option Kind of information to display addr Payload and address information. [vrtr-name] ARP entries.

  • Page 343: Displaying Network Processor Connection Information

    Using Debug Commands System and devices debugging Setting for option Kind of information to display Scheduler information. rspslot is the RSP slot number—1 sid sid [rspslot] or 2. If you do not specify a value for rspslot, the system uses the default RSP slot number.

  • Page 344: Obtaining Information About Routes On The Network Processor

    Using Debug Commands System and devices debugging 065665 0x0206 0/125 3072 000130 0x0206 0/124 3072 VLAN Configuration : Vlan is not enabled Packet Flow configuration: No Packet Flow is attached Multicast Configuration : Multicast is not enabled Bridge Configuration : Bridging is not enabled Filter Configuration : No Filters applied QOS Configuration...

  • Page 345: Obtaining Detailed Information For A Did

    Using Debug Commands System and devices debugging Total 20 routes <end> To display detailed information for a specific router, append the router name to the info np route command. For example: admin> info np route main Local If Routes for vrouter:main Destination Gateway needArp...

  • Page 346: Displaying Arp Entries

    Using Debug Commands System and devices debugging Did 43514 is not initialized Displaying ARP entries The info np arp command displays all ARP entries on the network processor. For example: admin> info np arp ARP Table for vrouter: destIp 1.1.1.3 00:00:07:b0:01:00 wan-16 40956 To display ARP entries only for a specific VRouter, append the VRouter name to the info np arp command.

  • Page 347: Displaying Bridge Group Information

    Using Debug Commands System and devices debugging Type 43516 ucast 43518 ucast 43520 ucast Displaying bridge group information The info np brige group command displays information about a bridge group or bridge table information for a bridge group. Its syntax is as follows: info np brige group grp|table grp [ifnum] Replace grp with a bridge group number and ifnum with an interface number.

  • Page 348: Displaying Scheduler Ids Associated With A Logical Port

    Using Debug Commands System and devices debugging Table has 5 entries. Displaying scheduler IDs associated with a logical port The info np psl lport [count] [rspslot] command displays scheduler IDs associated with a logical port. For example: admin> info np psl 0 16 LPortId SchedId SchedId SchedId SchedId In the following example, entry 16 shows information for the Gigabit Ethernet interface:...

  • Page 349: Displaying Details For A Specific Scheduler

    Using Debug Commands System and devices debugging TM parameters: --------------- : 0x064b Queue Threshold : 0x00c8 Scheduler Threshold : 0x01f4 Bridge Port : 0x0000 TS parameters: --------------- PCR configured : 0x0000 SCR configured : 0x0000 PCR/SCR limit : 0x00000000 Last Schedule Time : 00:00:00:00 Displaying details for a specific scheduler The info np sid sid [rspslot] command displays information about a specific...

  • Page 350: Displaying Atm Information

    Using Debug Commands System and devices debugging Without any arguments, the info conn command reports information on all connections on the Fast Ethernet trunk module. For example: fet-1/18> info conn slot if type vpi/vci IW -------------------------- ATM 0/131 CTL 0/123 CTL 0/124 65534 ETH 0/0 65535 ETH 0/0...

  • Page 351: Displaying Aal5 Channel Information

    Using Debug Commands System and devices debugging Port UPIMode EXT STATS RxAddr TxAddr RxPHY MD TxPHY MD Rx M/S Tx M/S UTOPIA ENABLED Multi PHY Multi PHY SLAVE SLAVE To display detailed information about a specific ATM port, append the port number to the info atm command.

  • Page 352: Displaying Ethernet Device Information

    Using Debug Commands System and devices debugging To display detailed information about a specific ATM port, append the port number to the info aal5 command. For example: fet-1/17> info aal5 22 ConnectionID : 22 Magic : 2152507936 : 131 Interrupts : Enable Channel Mode : Enable...
  • Page 353 Using Debug Commands System and devices debugging Rx Flow Control : Enabled Tx Flow Control : Enabled Tx Queue Mode : FAST Iw Back ground : UNUSED Tx Statistics : ENABLED Tx Max SDU : 1500 Rx Statistics : ENABLED Rx Addr Mode : PROMISCUOS MAC Look up mode...

  • Page 354: Nebs Testing And Loopback (Sar Command

    Using Debug Commands NEBs testing and loopback (sar command) NEBs testing and loopback (sar command) You can use the sar command to verify the data path between the control module and Ripper-based LIMs when connections are established on the LIM. In this software version, this capability is not supported on IP2100 control modules.

  • Page 355: Displaying Stinger Port Information

    Using Debug Commands NEBs testing and loopback (sar command) 4: Loopback entered. 5: Loopback entered. 6: Loopback entered. 7: Loopback entered. 8: Loopback entered. The following command executes NEBs testing: admin> sar -t d 2 NEBS-1/1: received 10 of 10 with 0 errors @1c6ed504 NEBS-1/2: Loopback test count:10 size:100 NEBS-1/2: received 10 of 10 with 0 errors @1c6ed505 NEBS-1/3: Loopback test count:10 size:100...

  • Page 356: Resetting Tcp Port 23

    The update debug command modifies optional functionality of the Stinger unit. To enable some options, you must obtain one or more software licenses (supplied by a Lucent representative) that enable the functionality in your Stinger. After each string is entered, the word complete appears, indicating that the Stinger accepted the license.

  • Page 357: Radius Debugging

    Using Debug Commands RADIUS debugging If you enter update without a text string modifier, the Stinger unit displays a list of current configuration information, as shown in the following example: admin> update Host interfaces: 4 Net interfaces: 0 Field features 1: 0 Field features 2: 32 Field features 3: 0 Field features 4: 28...

  • Page 358: Verifying Settings In The External-Auth Profile

    Using Debug Commands RADIUS debugging HashTable @ 10542160, bucketCount: 192, callCount: 23, hashName <afs-1:8> Slot 2/5: HashTable @ 10585730, bucketCount: 48, callCount: 7, hashName <afs-2:5> The following sample command displays the same information for a single module in shelf 1, slot 8: admin>...

  • Page 359: Displaying Radius Authentication And Accounting Statistics

    Using Debug Commands RADIUS debugging loadd 00227 252355493 012032 local 370610 loadd 00226 252355492 012032 local 370611 loadd 00225 252355491 012032 local 370608 loadd 00224 252355490 012032 local 370609 loadd 00004 252332182 012032 none loadd 00003 252332181 012032 none loadd 00002 252332180 012032 none loadd 00001 252332179 012032 none The radsessdump command displays the following information: Field...

  • Page 360: Interface Debugging

    Using Debug Commands Interface debugging Of connections attempts, 602 were authenticated successfully, and 18 were not: timout[A,O]=[0,6], unexp=0, bad=18, authOK=602 In the next sample message, the IP address of the RADIUS server is 1.1.1.1, and the curServerFlag indicates whether or not this RADIUS server is the current authentication server.

  • Page 361: Displaying Network Interface Mappings

    Using Debug Commands Interface debugging Displaying network interface mappings The netif debug command displays the Stinger network interface mappings. This command has the following syntax: netif -m | -q | -v |? Syntax element Description Displays mappings for the specified map type. Displays the queue for a map.

  • Page 362: Control Module Debugging

    Using Debug Commands Control module debugging You must first open a session with the LIM, or with logical slot 1 on a Stinger MRT to use this command. The eoc command has the following syntax: eoc -p [-r|-w reg slot port [data]] Syntax Element Description Enable/disable module debug.

  • Page 363: Displaying The Status Of Redundant Control Modules

    Using Debug Commands Control module debugging Displaying the status of redundant control modules The controller-redundancy debug command displays the status of the primary and secondary control modules in a Stinger unit with redundant control modules. To enable controller-redundancy debugging, proceed as shown in the following example: admin>...

  • Page 364: Displaying Interface Management Information

    Using Debug Commands Control module debugging Field Indicates My function Function of the primary control module. Following are valid functions: No_Function Primary Secondary State of the secondary control module. See My state for Remote’s state valid values. Remotes’s function Function of the secondary control module. See My function for valid values.
  • Page 365 Using Debug Commands Control module debugging To display the interface table entries, use the -d option. (The netstat command also displays a hyphen to indicate a disabled Ethernet interface.) For example: admin> ifmgr -d bif slot sif u m p ifname host-name remote-addr local-addr ---------------------------------------------------------------------------...
  • Page 366 Using Debug Commands Control module debugging Field Indicates Whether the interface is permanent. A P indicates a permanent interface. A hyphen (-) or a blank indicates that the interface is not permanent. A permanent interface is an interface that is configured in the command-line interface and stored in Stinger NVRAM.
  • Page 367 Using Debug Commands Control module debugging nexthop: 0.0.0.0 proxy_arp_mode: 0 proxy_arp_head: 0 No associated connection profile SNMP ifType: The icmp-reply-directed-bcast parameter in the ip-global profile specifies whether the Stinger unit responds to directed-broadcast ICMP echo requests. If this parameter is set to no, the system does not respond to any directed-broadcast ICMP requests.

  • Page 369: Appendix B Stinger Log Messages

    Stinger Log Messages Fatal and warning error messages ........B-1 Definitions of fatal errors .

  • Page 370: Clearing The Fatal Error Log

    Definitions of fatal errors Following are definitions, by index number, of the fatal errors that the Stinger unit can report. If you experience a fatal error, contact Lucent OnLine Customer Support at http://www.lucent.com/support. Index...
  • Page 371 Stinger Log Messages Definitions of fatal errors Index Definition No mail descriptor (EXEC) This reset occurs if the Stinger tries to allocate a mail message when there are none left. The cause is usually a memory leak. No mail buffer memory (EXEC) No task to run (EXEC) No timer memory (EXEC) No timer pool (EXEC)

  • Page 372: Definitions Of Warning Messages

    Stinger unit can report. Warning messages, by themselves, are not necessarily cause for concern. They are used by development engineers to determine the cause of fatal errors. Contact Lucent OnLine Customer Support at http://www.lucent.com/support if warning messages are accompanied by fatal errors. Index...
  • Page 373 Stinger Log Messages Definitions of warning messages Index Definition Buffer belongs to wrong pool Buffer belongs to wrong heap Buffer not previously allocated This warning can be logged under different conditions. For example, double freeing of memory and low-memory conditions can both generate a warning 104.
  • Page 374 Stinger Log Messages Definitions of warning messages Index Definition Error no timers LCD memory allocation failure Indicates that a memory-copy routine was called, but the source buffer was much larger than expected. Invalid state Error memory copy too large Error memory copy magic missing Error memory copy wrong magic Error memory copy bad start address WAN buffer leak...

  • Page 375: Fatal Crash Information On The Console

    Stinger Log Messages Fatal crash information on the console Index Definition TCP sequence gap TCP too much data TCP write attempt too large TCP options bad Modem message parsing failed TACACS+ pointer inconsistency TACACS+ index inconsistency TACACS+ TCP inconsistency TACACS+ TCP out-of-range socket TACACS+ socket mismatch TACACS+ unexpected authentication state Error in filter list...

  • Page 376: Syslog Messages

    RADIUS clients file or the TACACS+ configuration file. ■ You are using a Lucent RADIUS server instead of an Ascend RADIUS server. PCMCIA flash card error messages When a load, format, or dircode command fails, the Stinger unit logs the messages described in this section.

  • Page 377: Load Command Messages

    Stinger Log Messages PCMCIA flash card error messages load command messages Table B-1 lists the error messages that might appear if the system terminates while in the process of loading a tar file. Table B-1. Load command error messages (loading a tar file) Error message Description load aborted: not a tar image...

  • Page 378: Format Command Messages

    Stinger Log Messages PCMCIA flash card error messages Table B-2. Load command error messages (uploading to PCMCIA flash cards) (Continued) Error message Description load: error: specified flash card is The flash card’s write-protect write-protected switch is set. load: error: specified flash image is A control module in the LOAD currently in use state is currently accessing the...
  • Page 379 Stinger Log Messages PCMCIA flash card error messages Table B-4. Dircode command error messages (Continued) Error message Description Card N is temporarily unavailable The flash card is currently coming up or is being formatted. Card N is unavailable The flash card experienced an error and is inaccessible.
  • Page 381 Index table, viewing 9-9 arptable command, using 9-9 accounting cross-connects, displaying 11-11 RADIUS session, displaying status of session statistics A-21 failures, displaying 11-19 See also RADIUS how affected by LIM removal 3-16 line status, determining 11-3 acct-failsafe command A-19 packet statistics, displaying 11-6 Admin user QoS statistics, displaying 11-19 changing password 1-3...
  • Page 382 binaries, loading specific for modules 6-17 logging 2-4 netif A-23 bit-error rate test (BERT) 12-28 netstat 9-2 built-in self tests (BISTs) 12-25 new 1-13 nslookup 9-9 nvram 6-3 oamloop 12-15 open 3-9 ospf 10-1 displaying for Gigabit Ethernet OLIMs 5-3 permissions for 1-22 ping 9-1 CAC bandwidth allocation statistics, displaying...
  • Page 383 connections displaying 11-3 status, displaying 1-36 E1 interfaces, displaying status 4-10 terminating user session 1-43 errors console, fatal crash information on B-7 fatal, displaying B-2 logged by Syslog B-8 continuity tests OAM F4 tests 12-11 Ethernet interface 4-1 OAM F5 tests 12-11 12-12 interface, specifying for management only 1-4 control modules...
  • Page 384 gunzip command 6-20 displaying with netstat command 9-2 Ethernet A-28 gzip command 6-20 Ethernet, enabling and disabling A-26 gzip compressed format, saving in 6-2 how the system creates 9-2 interface table (ifmgr) A-26 IP 4-1 IP interface table 9-2 line and trunk status 4-7 hash codes, using update command with A-18 network mappings, displaying A-23 PNNI, displaying 11-23...
  • Page 385 line command 1-37 memory, NVRAM 6-1 line protection modules. See LPMs messages fatal and warning B-1 line-tests profile 12-30 12-31 12-32 fatal error definitions B-2 link state advertisements. See LSAs levels of debug, specifying A-2 link-state database, displaying 10-7 log messages in status window 1-38 load command 6-18 Syslog B-8 loadmate command 6-10...
  • Page 386 LSAs, displaying 10-9 neighbor nodes (PNNI), displaying details about 11-28 neighbors, displaying 10-14 routers, displaying 10-11 netif command, using A-23 routing table, displaying 10-10 netstat command routing, displaying information about 10-2 displaying interface table with 9-2 summarized information, displaying 10-12 displaying routing table with 9-3 traps 8-22 network processor, monitoring 5-1...
  • Page 387 ports displaying information about A-17 running built-in self tests on 12-25 RADIUS specifying for Syslog, 2-11 radservdump command A-20 TCP and UDP, information about 9-6 radsessdump command A-20 See also interfaces radstats command A-21 power failures, setting an alarm for 8-5 refreshing configuration 6-16 refreshing nailed profiles from 6-16 reloading profiles 6-16...
  • Page 388 SDSL interfaces, displaying 4-9 profiles created by 7-22 read-write access, enabling 7-4 security state changes, initiating 7-21 serial port, securing 1-3 state, verifying 7-17 SNMP host address, configuring 7-5 Stinger support, overview 7-1 self-testing, enabling on LIMs 3-19 table, resetting 7-21 SELT 12-29 trap classes, enabling 8-22 serial number, viewing A-18...
  • Page 389 connection status 1-36 TCP/IP 9-1 contents, defining 1-35 system profile default size 1-39 session ID base, setting 2-11 described 1-36 system name, setting 1-31 displaying 1-35 system-integrity profile 5-22 general 1-37 information for user profile 1-39 length 1-39 line status 1-37 log 1-38 navigating 1-35 line clock source, displaying 1-32...
  • Page 390 clearing statistics for 4-5 view-based access control (VACM) 7-13 displaying port status 4-4 virtual channel connection. See VCC displaying status of 3-2 virtual link information, displaying 11-7 interfaces, monitoring 4-2 VP-switching VPI, enabling OAM 12-6 numbering for Stinger MRT 3-1 required status, displaying 3-2 displaying status 1-37 packets during connection setup, displaying...

This manual is also suitable for:

Stinger mrtStinger fs+Stinger lsStinger rtStinger ms+

Table of Contents