Lucent Technologies Stinger Administration Manual
  1. Manuals
  2. Brands
  3. Lucent Technologies Manuals
  4. Network Hardware
  5. Stinger
  6. Administration manual
Lucent Technologies Stinger Administration Manual

Lucent Technologies Stinger Administration Manual

Hide thumbs Also See for Stinger:
Table of Contents

Advertisement

Quick Links

Download this manual
Stinger®
Administration Guide
Part Number: 7820-0712-008
For software version 9.7.0
August, 2004

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for Lucent Technologies Stinger

Summary of Contents for Lucent Technologies Stinger

  • Page 1 Stinger® Administration Guide Part Number: 7820-0712-008 For software version 9.7.0 August, 2004...
  • Page 2 In rare instances, unauthorized individuals make connections to the telecommunications network through the use of access features. Trademarks Lucent, the Lucent logo, and all Lucent brand and product names are trademarks or registered trademarks of Lucent Technologies Inc. Other brand and product names are trademarks of their respective holders.

  • Page 3: Customer Service

    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. Stinger® Administration Guide...

  • Page 5: Table Of Contents

    Enabling two level authentication..............1-7 Specifying the maximum number of login attempts ........1-11 Authentication from a remote shelf to a host Stinger unit......1-11 User account and user password expiration ............ 1-12 What happens when a user account or user password expires ....1-12 RADIUS support for account and password expiration ......
  • Page 6 Terminating a user connection ................ 1-38 Disconnecting an idle connection..............1-38 Resetting a Stinger system..................1-39 Chapter 2 Working with Stinger Shelves and Modules ........2-1 Understanding physical addressing on Stinger units..........2-1 Viewing system components..................2-3 Using the show command................... 2-3 Field description from the output of the show command ......
  • Page 7 Saving command logs.................. 3-7 Storing log messages across system resets ........... 3-7 Configuring the Stinger unit Syslog facility............ 3-10 Enabling the Syslog facility on the Stinger unit ........3-11 Specifying a session ID base ..............3-12 Configuring the Syslog daemon ..............3-12 Configuring call logging ..................
  • Page 8 How it works ..................... 6-3 Loading a default.cfg file from the TFTP server ..........6-4 Verifying that the default.cfg is saved to the desired directories ....6-4 Issuing the nvram command on a system with a default.cfg file..... 6-5 viii Stinger® Administration Guide...
  • Page 9 Requirements and limitations................6-13 Enabling extended profiling................6-13 Restoring an earlier configuration after enabling extended profiling....6-13 Using a script to configure a Stinger unit ............... 6-14 Timing the saving of profiles .................. 6-15 Reloading profiles from RADIUS................6-15 Loading specific module images ................6-15 Using the load-select profile................
  • Page 10 Deleting an alarm model table ..............8-13 Configuring SNMP traps..................8-13 Creating a trap profile ..................8-13 Configuring the trap profile ................8-14 Trap classes ...................... 8-15 Alarm class traps ..................8-15 Security class traps ..................8-18 Port class trap .................... 8-19 Stinger® Administration Guide...
  • Page 11 Configuring trap sequencing and the sending of heartbeat traps ..... 8-29 Enabling traps for events on remote shelves ........... 8-30 Stinger trap optimization ................. 8-31 Optimizing the number of traps generated by the system ......8-31 Trap optimization ..................8-32 Displaying information about notification logs ..........
  • Page 12 Continuity check implementation ............12-9 Deactivating a continuity check test ............12-10 Running F4 and F5 continuity tests using the oam command....12-11 Running F5 continuity tests using the atm-oam profile ......12-12 OAM loopback tests ..................12-12 Stinger® Administration Guide...
  • Page 13 Displaying scheduler IDs associated with a logical port ......A-10 Displaying information for a specific queue..........A-11 Displaying details for a specific scheduler ..........A-11 Displaying Fast Ethernet trunk protocol and connection information....A-11 Displaying connection information............A-12 Displaying ATM information..............A-13 Stinger® Administration Guide xiii...
  • Page 14 Using the EOC command on ADSL interfaces..........A-22 Control module debugging..................A-23 Displaying the status of redundant control modules ........A-23 Displaying interface management information ..........A-24 Appendix B Stinger Log Messages..............B-1 Fatal and warning error messages................B-1 Reviewing the fatal error log ................B-1 Clearing the fatal error log.................B-2 Definitions of fatal errors ..................B-2...
  • Page 15 Figures Figure Sample contents of a status window 1-31 Figure Front panel of a Stinger FS unit 2-2 Figure Status window for ATM VCCs 11-3 Figure Data passing through a modem’s digital circuitry 12-25 Figure Data passing through a modem’s digital and analog circuitry 12-25...
  • Page 17 Permissions and associated commands ........... 1-18 Table 1-2 .Message levels ................1-25 Table 2-1 How TAOS organizes Stinger module functions ....... 2-2 Table 2-2 Description of Reqd, Oper, and Slot Type fields........ 2-4 Table 2-3 Statistics displayed for a remote shelf ..........2-9 Table 2-4 Statistics displayed for the host shelf..........

  • Page 19: 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: Documentation Conventions

    Warns that a failure to follow the recommended procedure could result in loss of data or damage to equipment. Caution Warns that a failure to take appropriate safety precautions could result in physical injury. Warning Warns of danger of electric shock. Warning Stinger® Administration Guide...

  • Page 21: Stinger Documentation Set

    About This Guide Stinger documentation set 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 RADIUS attributes. Administration and troubleshooting: Stinger Administration Guide (this guide). Describes how to administer the Stinger unit and manage its operations. Each chapter focuses on a particular aspect of Stinger administration and operations. The chapters describe tools for system management, network management, and Simple Network Management Protocol (SNMP) management.

  • Page 23: Administering A Stinger System

    Resetting a Stinger system ........

  • Page 24: Logging Into A Stinger Unit

    “Understanding physical addressing on Stinger units” on page 2-1. Logging into a Stinger unit When you log into a Stinger unit, you actually connect to its control module. If the Stinger unit contains two control modules, you can connect to either control module.

  • Page 25: Changing The Default Admin Password

    Stinger unit. See “Managing administrative access to the unit” on page 1-5. If the Stinger unit will be configured for SNMP, see also “Securing the SNMP agent” on page 7-4. Changing the default Admin password Because the admin login has superuser privileges, you must change the default password immediately.

  • Page 26: Specifying A Management-Only Ethernet Interface

    Administering a Stinger System Enabling basic security measures If your Stinger unit is operating with two control modules, both are working in parallel. As a result, the primary control module does not copy over this configuration to the secondary control module. You must secure both serial ports manually.

  • Page 27: Securing Telnet Access

    Stinger command-line interface to monitor or configure the unit. In contrast, connection profiles contain authentication and configuration information for a remote device or user and allow the remote user to connect to the Stinger unit for WAN or LAN access.

  • Page 28: Logging Into The Stinger Unit

    User: admin Password: mypassword admin> 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> list ..

  • Page 29: Enabling Two Level Authentication

    USER/test read admin> set active-enabled = yes admin> write USER/test2 written If you are connected to the Stinger unit as a different user, use the auth command to log in as the administrator: admin> auth user Password: Enabling two level authentication...
  • Page 30 For all telnet user accounts, first and second level, the attribute Ascend-Telnet- Profile must be set to a valid Stinger user profile. For a second level user, the attribute Ascend-First-Level-User must specify a first-level user account.
  • Page 31 Administering a Stinger System Managing administrative access to the unit 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 definition of the user- second-level-authentication parameter is as follows:...
  • Page 32 Administering a Stinger System Managing administrative access to the unit 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 33: Specifying The Maximum Number Of Login Attempts

    Stinger unit using the open shelf slot command, the systems creates a terminal session using the control bus. The host Stinger unit authenticates a user by prompting the user for a user name and password. The user name and password must be defined in a user profile in the host Stinger system.

  • Page 34: User Account And User Password Expiration

    All password administration must be performed by the RADIUS server system administrator. After successful authentication, the RADIUS server returns the name of the Stinger user profile that is linked to the external user account. The system authenticates users as defined in the user profile for user terminal session.

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

    User password expiration date. Complex field. expiration-date Note Stinger systems do not audit RADIUS server user accounts. If a Stinger system is configured for external authentication and the audit-user-profiles parameter in the system profile is enabled, for the users to be authenticated, the RADIUS server administrator must ensure that for all system telnet user accounts, the attribute Ascend-User-Acct-Expiration is set to the correct date.

  • Page 36: Enforcing A Password Check

    Administering a Stinger System Managing administrative access to the unit 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 profileto yes.

  • Page 37: Creating Telnet Access Control Lists

    ReEnter New Password: user2> Creating Telnet access control lists You can restrict telnet access to the Stinger system by configuring a tacl (telnet access control list) profile. You must have system authorization to create, read, or modify the profile. You can configure up to 20 entries in the tacl profile, each of which specifies a source IP address that is explicitly allowed telnet access to the system.

  • Page 38: Assigning Permissions

    Escape character is '^]'. User: admin Password: An attempt to telnet to the Stinger system from an IP address that is not on the specified subnet will fail. For example, the following sequence is displayed: (sys10-27-45-45) telnet 210.210.210.99 Trying 210.210.210.99...

  • Page 39: Understanding Command Permissions

    Permissions control the actions that a user who logs in with a particular profile can perform on a Stinger unit. Each permission enables the use of a particular command class. When you use the help command to display available commands, the left column shows command names, and the right column shows the command class.

  • Page 40: Table 1-1 Permissions And Associated Commands

    Allow- Diagnostic Diagnostic Allow-Termserv Termserv (Does not apply to the Stinger unit.) N/A. The Allow-Password permission enables a user to view Allow-Password passwords. If the permission is set to no, the user sees a row of asterisks instead of the actual configured password. If the...

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

    Administering a Stinger System Managing administrative access to the unit admin> new user admin USER/admin read admin> set name = test admin> set password = test-pw admin> set allow-update = no admin> set allow-code = no admin> write USER/admin written...
  • Page 42 Administering a Stinger System Managing administrative access to the unit Parameter Setting allow-termserv Enable/disable permission for the users in the group to use terminal-server commands. With the default no setting, users do not have terminal-server permission. Specify yes to enable users to have terminal-server permission.
  • Page 43 In this example, the existing user bill is given permission to use the six commands that he needs to provision new users. The existing user ted can use all the Stinger commands except reset, slot, and read: admin>...
  • Page 44 Use the usergroupcheck command to verify that your specifications are valid. For syntax information, see the Stinger Reference. To verify that all the user-group profiles specify valid lists of commands and that all user-group profiles specified by user profiles are valid, use the usergroupcheck command with the -a option.
  • Page 45 Administering a Stinger System Managing administrative access to the unit To verify that the user-group profile specified in the user profile enter the usergroupcheck command with the -u option. For example: admin> usergroupcheck -u bill Group provisioning: Commands all valid.

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

    The default command-line prompt is an asterisk followed by a right angle bracket (*>). An asterisk in this setting causes the Stinger system to substitute the value of the profile’s name parameter after a successful login. For example, for the admin profile, the following prompt appears: admin>...

  • Page 47: Logging In As A Different User

    Basic system settings Table 1-2. .Message levels Message Indicates level emergency Error condition in the Stinger unit. The unit is probably not operating normally. alert Error condition in the unit. However, the unit is still operating normally. critical Inoperative interface or a security error.

  • Page 48: Setting The System Time And Date

    Administering a Stinger System Basic system settings The system name is specified in the system profile. For example, to set the Stinger unit’s system name to Stinger01, proceed as follows: admin> read system SYSTEM read admin> set name = Stinger01 admin>...

  • Page 49: Configuring System Clocking

    The system-8k-clock parameter in the system profile specifies the clock source for the Stinger system. You can configure the system to take its clock source from a line interface module (LIM), trunk port, or from an external building integrated timing supply (BITS) clock connected to the unit’s alarm relay.

  • Page 50: Displaying Basic System Information

    For information about see displaying system components, see “Working with Stinger Shelves and Modules” on page 2-1 Displaying system hardware information and software version...

  • Page 51: System And Module Uptime

    Lucent Stinger FS+ 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. If the system profile has not been configured, the command displays (not configured).

  • Page 52: Using The Status Window

    Stinger unit generates about its activities. For example, one status window displays up to 100 of the most recent system events that have occurred since the Stinger unit was started up, and another displays statistics about the currently active session. A VT100 window that can accommodate an image of at least 80 columns by 24 rows is required for displaying the status screens.

  • Page 53: Understanding The Status Window

    Administering a Stinger System Displaying basic system information Figure 1-1. 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...

  • Page 54: General Status Information

    With the default settings in a user profile, the top area of the status window initially displays general status information about the Stinger unit, including its serial number, the version of system software that the unit is running, and the number of packets transmitted and received.

  • Page 55: Log Message Information

    With the default settings in a user profile, the bottom area of the status window initially displays the most recent message from the Stinger log buffer. The number of system event messages stored in the log is set by the save-number parameter in the log profile.

  • Page 56: Customizing The Status Window Display

    Changing current status window sizes The screen command enables you to change the size of the terminal emulator and status windows for the current session. For syntax information, see the Stinger Reference. The following example changes the current display size to 55 lines long and 100 characters wide: admin>...

  • Page 57: Viewing The Factory Configuration And Software Licenses

    These values are read from the system ROM, security program array logic (PAL), and the hardware assembly itself. For information about the parameters in the base profile, see the Stinger Reference. To view the base profile, use the get command. For example: admin>...

  • Page 58: Customizing The Output Of The Userstat Command

    288532030 1.01.01/012 <end user list> 1 active user(s) For definitions of the available specifiers, see the Stinger Reference. Displaying information related to a known IP address Use the userstat -a command to display information related to a known IP address.

  • Page 59: Displaying Information Related To A Known Username

    Administering a Stinger System Managing administrative connections SessionID Line/Chan Slot:Item Tx/Rx Rate Svc Address Username 288532030 1.01.01/012 1:03:01/002 56000/56000 PPP 1.1.1.238 net1 <end user list> 1 active user(s) To display only the relevant username, include the -o option as follows: admin>...

  • Page 60: Displaying Administrative Users

    Disconnecting an idle connection You can configure a Stinger unit to disconnect a modem connection after a specified period of inactivity. To configure a timeout value, set the inactivity-time parameter in the modem profile with a value from 0 through 255 seconds. With the default setting of 0, the timer is disabled and an inactive modem connection is not disconnected after any period of inactivity.

  • Page 61: Resetting A Stinger System

    MODEM/{ shelf-1 first-control-module 3 } written 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 63: Working With Stinger Shelves And Modules

    Modules Understanding physical addressing on Stinger units ..... . 2-1 Viewing system components ........2-3 Opening a session with a module .

  • Page 64: Table 2-1 How Taos Organizes Stinger Module Functions

    On a Stinger MRT, because control module and LIM functions are incorporated into the unit’s chassis, the terms control module and LIM in this guide refer to the control module and LIM functions on the Stinger MRT, and not to physical modules.

  • Page 65: Viewing System Components

    On a hosted system, the show command displays information about all shelves with an active control link to the host. For example, on a hosted Stinger MRT system, the following command output shows that in addition to the host shelf (shelf ID 1), shelves 3, 4, 5, and 6 have an active link to the host.

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

    Working with Stinger Shelves and Modules Viewing system components { 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 { shelf-6 first-control-mod+ UP mrt-cm Note All configuration profiles reside on and are accessible only on the host system.

  • Page 67: Monitoring The Status Of Remote Shelves

    Working with Stinger Shelves and Modules Viewing system components Monitoring the status of remote shelves The remote-shelf-stat profile resides on the host for monitoring remote shelves. The remoteshelf command displays information about enabled remote shelves in the hosted system. You can set alarms and traps to notify an SNMP management station when certain conditions occur on a remote shelf.
  • Page 68 An array of indexed parameters that indicate the contact-closure[n] contact closure state (yes if contact closure is detected) on the corresponding remote shelf. Only the first two contact closure values are meaningful for Stinger MRT units. host-port:physical- Physical address of the remote shelf. The address address...

  • Page 69: Displaying Information About Enabled Remote Shelves

    Working with Stinger Shelves and Modules Viewing system components Displaying information about enabled remote shelves The remoteshelf command displays information about enabled remote shelves. It uses the following syntax on a hosted system: HOST> help remoteshelf usage: remoteShelf -[s|o] <param>...

  • Page 70: Displaying A Picture Of The Topology

    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 71: Table 2-3 Statistics Displayed For A Remote Shelf

    Working with Stinger Shelves and Modules Viewing system components MrtType : STINGER_MRT_23INCH_PLATFORM MRT Connected to Exp1 : 2 MRT Connected to Exp2 : 16 Port connected to - On Master : 1 Port connected to - On Slave : 0...

  • Page 72: Table 2-4 Statistics Displayed For The Host Shelf

    Working with Stinger Shelves and Modules Viewing system components Table 2-3. Statistics displayed for a remote shelf (Continued) Output field Description of value Number of Nack Sent Number of Nacks sent to the shelf. Number of Reset Sent Number of Resets sent to the shelf.

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

    Working with Stinger Shelves and Modules Viewing system components Table 2-5. Statistics displayed in an open session on the remote shelf Output field Description of value Discovery restart Number of times Auto Discovery has been restarted. Number of Req Sent Number of Auto Discovery Request sent.

  • Page 74: Using The Slot-Info Profile

    Reference. Opening a session with a module Each installed and operating LIM or T1 or E1 module on a Stinger FS, Stinger FS+, Stinger LS, or Stinger RT unit has its own processor and is running its own operating system. You can use the open command to connect to a module directly and run commands.

  • Page 75: Sample Open Commands

    Terminated from far-end Module-level commands When you are connected to a module, only a subset of the Stinger commands are available. To list the commands available on the module, enter a question mark (?) or help, as in the following example: dmtadsl-atm-1/4>...

  • Page 76: Changing A Module's State

    ( debug ) [More? <ret>=next entry, <sp>=next page, <^C>=abort] For information about module-level commands, see the Stinger Reference. Changing a module’s state 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 77: Changing The State Of A Module's Interface

    Working with Stinger Shelves and Modules Changing the state of a module’s interface admin> list [in SLOT-ADMIN/{ shelf-1 slot-1 0 }] 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. If you change the value...

  • Page 78: Using The Device-State Profile

    { { 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 79: Removing A Module And Its Configuration

    NVRAM used to store configuration information is not cleared until you explicitly clear the configuration. When you remove a module from a Stinger system, the show command reports a value of NONE for the empty slot. For example: admin>...

  • Page 80: Moving A Lim That Uses System-Generated Atm Addresses

    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 using one of the following methods: Use the nvram command.

  • Page 81: Removing The Module

    971001 This command saves the configuration to a file named 971001 in the TFTP home directory on a host named bonzo. Clear the system configuration and restart the Stinger unit by entering the nvram command: admin> nvram Restore the saved system configuration.

  • Page 83: Chapter 3 Configuring Logging, Syslog, And Call Logging Services

    “Administering the SNMP Agent” on page 7-1. Configuring system logging and Syslog services The Stinger unit generates error and event messages related to its operations. You can use the log profile to perform the following tasks: Configure how the system handles log messages that are displayed on a status window.
  • Page 84 Lowest level of log messages that the Stinger unit displays in the log status window. The unit logs all messages that are at the specified level or higher. For example, if alert is specified, all messages at the alert and emergency levels are logged.
  • Page 85 Syslog daemon facility code for messages logged from the Stinger unit. For detailed information, see the syslog.conf manual page entry on the UNIX syslog server. Specify one of the following settings:...

  • Page 86: Configuring System Logging

    Configuring system logging The Stinger unit records system events in its status window event log. (For additional information, see “Log message information” on page 1-33.) The save-level parameter specifies the lowest level of message to be saved for status display.

  • Page 87: Viewing Command Logs

    Configuring logging, Syslog, and call logging services Configuring system logging and Syslog services setting of zero (0), command logging is disabled for a Stinger system (the system logs no user commands). To enable command logging, set this parameter to a value greater than zero.

  • Page 88: Viewing The Cmd-Log Profile

    Time the command was entered, in the format { Hour Minute Second }. information Command-line interface command entered by the user. shelf Shelf number on which the command issued. slot Slot number on which the CLI command issued. index Index number of the command log. Stinger® Administration Guide...

  • Page 89: Saving Command Logs

    Note You cannot save cmd-log profiles with other system profiles. For more information about using the save command, see the Stinger Reference. Storing log messages across system resets You can store log messages across system resets by saving log messages as profiles.
  • Page 90 To disable the saving of log messages, set the parameters to none. Saved log messages are not erased when you disable this feature. The system automatically disables the saving of log messages 24 hours from the time you set the boot-level or run-time-level parameter to a value other than none. Stinger® Administration Guide...
  • Page 91 06/04/2004 03:23:39 shelf-3/first-contro alert Saving of system logs as profile is disabled For more information about the log command, see the Stinger Reference. Overview of the log-entry profile The contents of the log-entry profile have read-only access. Following is a sample...

  • Page 92: Configuring The Stinger Unit Syslog Facility

    Configuring the Stinger unit Syslog facility By configuring the Stinger unit to report events to a syslog host on the local IP network, you can maintain a permanent log of events and send Call Detail Reporting (CDR) reports to a host that can record and process them.

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

    = yes Configuring Syslog streams The stream of records sent by the Stinger unit to a syslog server is called a syslog stream. The Stinger unit supports up to three syslog servers and define an independent syslog stream for each server.

  • Page 94: Specifying A Session Id Base

    ID for each session. The system uses this value to identify the session to SNMP, RADIUS, or other external entities. If this parameter is set to zero, the Stinger unit sets the initial base for session IDs to the absolute clock. For details about this parameter, see the Stinger Reference.

  • Page 95: Enabling Call Logging

    = yes Specify the IP address of a call-logging host: admin> set call-log-host-1 = 10.2.3.4 Specify the number of seconds that the Stinger unit waits for a response to a call- logging request: admin> set call-log-timeout = 10 Specify that the unit can send a stop packet without a username: admin>...

  • Page 97: Chapter 4 Monitoring System And Network Processor Operations

    Monitoring network processor operations ......4-7 Maintaining ASIC Integrity A Stinger unit includes mechanisms for maintaining the integrity of ATM cell- processing application-specific integrated circuits (ASICs) for control modules and line-interface modules (LIMs).
  • Page 98 Following are the integrity-config settings for LIM ASIC integrity testing, shown with default values for a LIM in slot 1: [in SYSTEM-INTEGRITY:integrity-config[1]] enable-continuous-detection = no detection-interval = 100 only-one-correction = yes correction-factor = 5 Stinger® Administration Guide...
  • Page 99 { shelf-1 slot-14 0 } sdsl-atm-card { shelf-1 trunk-module-1 0 } UP ds3-atm-trunk-daughter-card { shelf-1 trunk-module-2 0 } UP oc3-atm-trunk-daughter-card admin> read system-integrity SYSTEM-INTEGRITY read admin> set integrity-config 14 interval-auto-correction = 3600000 admin> write SYSTEM-INTEGRITY written Stinger® Administration Guide...

  • Page 100: Enabling Centralized Integrity Checks

    SYSTEM-INTEGRITY read admin> set enable-centralized-detection = yes admin> set ratio-centralized-detection = 100 admin> write SYSTEM-INTEGRITY written Optimizing system performance The following sections describe recommendations for optimizing performance on systems installed with an IP2000 module. Stinger® Administration Guide...

  • Page 101: Optimizing Performance With Filters And Flow Classification

    IP2000 controller, the batch processing parameters are of no consequence. For IP traffic that terminates in the Stinger system, filters are applied to the interface are active as soon as the interface is active. Overview of system profile settings...

  • Page 102: Configuration Recommendations

    (The debug command pmem sta fppmem displays the current FPP memory.) Valid settings for the np-fpp-compact-timer parameter are from 0 to 86400 seconds. For example admin> set np-fpp-compact-timer = 1800 Stinger® Administration Guide...

  • Page 103: Configuring Queue Size From Controller To Lim

    Configuring queue size from controller to LIM On Stinger systems installed with an IP2000 control module, you can modify the per- queue thresholds for traffic from the controller to a LIM. This adjustment might be helpful in situations where the there is bursty traffic for a connection.

  • Page 104: Enabling And Disabling Statistics Collection

    You can then use the debug command info np to display information about IP QoS monitoring and the stats command to display various statistics. For examples on how to use monitor IP QoS, see the Stinger IP2000 Configuration Guide. Enabling the system to start monitoring IP QoS traffic The following sample command enables the system to start monitoring IP QoS for the VLAN circuit.
  • Page 105 Number of classified DID Number of class rules Number of multicast IP flow :1 Multicast IP flow 1 Group matching the flow :0 Destination IP address :224.0.0.0 Destination IP netmask :224.0.0.0 Priority Number of unicast IP flow PRIORITIES Stinger® Administration Guide...
  • Page 106 Port drop Clearing IP QoS monitoring statistics To clear the IP QoS monitoring counters, enter the stats clear np ipqos command. For example: admin> stats clear np ipqos 15 IP QOS monitoring. Counter cleared for IF 15 4-10 Stinger® Administration Guide...

  • Page 107: Monitoring Statistics For A Connection

    7 21 Interface Statistics for IF 21: -------------------------------- Input Packet discarded Output packet discarded Input errored packet Output errored packet Input unknown protocol Statistics for Spoof: ---------------------- Spoof Discard Count: 0 Queue Discard: Stinger® Administration Guide 4-11...

  • Page 108: Monitoring Fpp Statistics

    P1 Framer error count: 0 P1 error cells count: 0 Pass#2 Error: -------------- Discarded ATM (mcast not configed): 0 Discarded Ether (mcast not configed): 0 AAL5 CRC error count: 0 IP header checksum error count: 0 4-12 Stinger® Administration Guide...

  • Page 109: Global Rsp Statistics

    To clear global RSP statistics, enter the stats clear np rspglobal command. For example: admin> stats clear np rspglobal Rsp Global stats cleared Monitoring logical port traffic You can use the stats traffic|error lport lport [count|count rspslot] command Stinger® Administration Guide 4-13...
  • Page 110 1. The value specified for count is 3. Because no RSP slot is specified, the system uses the default RSP slot. admin> stats error np lport 1 3 lportID blkRemain tttPass tttDiscard pduPass pduDiscard Thresh 8170 8170 To determine the default RSP slot, use the debug command nphw rspslot [rspslot]. 4-14 Stinger® Administration Guide...

  • Page 111: Scheduler Traffic And Error Statistics

    Monitoring network operations on the the Fast Ethernet Trunk module The stats command enables you to collect and display AAL5, ATM, or Ethernet statistics for the Fast Ethernet Trunk module. The syntax for the stats command is as follows: stats enable|disable|traffic|rate|error|clear aal5|atm|ether [port|conn-id|all] Stinger® Administration Guide 4-15...

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

    For example, the following command clears statistics for all Ethernet ports: fet-1/17> stats clear ether all Port 1 Cleared Port 2 Cleared The following sample command clears statistics only for Ethernet port 1: fet-1/17> stats clear ether 1 4-16 Stinger® Administration Guide...

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

    Rx MAC address error Tx single collision Rx MAC control Tx multi collision Rx Error alignment Tx late collision Rx Error length Tx excess collision Rx under size Tx under size Rx over size Tx over size Stinger® Administration Guide 4-17...
  • Page 114 The following sample command displays the rate only for Ethernet port 1: fet-1/17> stats rate ether 1 Port Rx Pkts Tx Pkts Rx Mcs Tx Mcs Rx Bytes Tx Bytes 5696 6052 5760 6120 5760 6052 5696 6120 5760 6120 5760 6052 5696 6120 5760 6120 4-18 Stinger® Administration Guide...

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

    Port Rx Err Len Rx Addr Miss 40932 To display the error statistics of a particular ATM port, enter the stats error atm command with the port number. For example: fet-1/17> stats error atm 0 Port Rx Err Len Rx Addr Miss Stinger® Administration Guide 4-19...

  • Page 116: Obtaining Aal5 Statistics

    If statistics collection is enabled for all AAL5 channels, it will also be enabled for any newly created channel. For example, the following command enables the system to collect statistics from all AAL5 channels: fet-1/17> stats enable aal5 all Statistics collection enabled : connection 0 4-20 Stinger® Administration Guide...
  • Page 117 The stats error aal5 command displays AAL5 error statistics for the Fast Ethernet Trunk module. Without any arguments, the stats error aal5 command displays statistics for all connections. For example: fet-1/17> stats error aal5 ConnID CRC SIZE-ERR UNDERFLOW MAXSDU IWUNDRUN IW MAXMRU Stinger® Administration Guide 4-21...
  • Page 118 For example, the following command displays statistics for connection 22: fet-1/17> stats rate aal5 22 ConId Rx Frames Tx Frames Aborts CLP Frms Iw Frames Rx CLP0 Rx CLP1 ConId Rx Frames Tx Frames Aborts CLP Frms Iw Frames Rx CLP0 Rx CLP1 4-22 Stinger® Administration Guide...

  • Page 119: Chapter 5 Monitoring Interfaces On Lims And Trunk Modules

    Monitoring redundant trunk groups ....... . . 5-20 TAOS includes profiles and commands that enable you to gather data specific to each interface or port on a Stinger line-interface module (LIM) or trunk module and each line interface on a Stinger MRT chassis.

  • Page 120: Summary Of Profiles And Commands For Monitoring Interfaces

    Summary of profiles and commands for monitoring interfaces Table 5-2 summarizes the status profiles and commands that you use to monitor the physical interfaces of Stinger LIMs, trunks, and interfaces on the Stinger MRT chassis. Table 5-2. Summary of profiles and commands for monitoring interfaces Device...

  • Page 121: Using Profiles To Monitor Lim And Trunk Interfaces

    Stinger Reference. For example, a Stinger unit with a dual-port DS3-ATM trunk module and two 8-port T1 modules enabled for inverse multiplexing over ATM (IMA) has a status profile for each DS3 port and 16 status profiles for its T1 ports, as shown in the following examples.

  • Page 122: Monitoring Lim Interfaces

    = False yellow-receive = False ais-receive = False For additional information about these parameters, see the Stinger Reference. Monitoring LIM interfaces The LIM status profiles shown in Table 5-2 include parameters and subprofiles that report the following information for the line or port: Physical address.
  • Page 123 = { 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 } utopia-address = 4294967295 pattern-test-status = none status-change-time-stamp = 0 For a discussion about the values reported by the parameters in the status profiles, see the module configuration guide for your device or the Stinger Reference. Stinger® Administration Guide...

  • Page 124: Displaying Interface Information

    You can use commands to display status information for the interfaces of the LIMs and trunks on a Stinger unit. The dmtaldsllines, hdsl2lines, imalines, sdsllines, shdsllines, imagroups, and atmtrunks commands display information about interfaces of a specific type in a Stinger unit. You use these commands with one of the following options: Option Description Displays information about all interfaces of a particular type.

  • Page 125: Displaying Trunk Port Status

    Monitoring Interfaces on LIMs and Trunk Modules Displaying interface information 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...

  • Page 126: Resetting Trunk Statistics

    Displaying ADSL LIM interfaces The following sample dmtaldsllines commands shows information about the ADSL interfaces of a Stinger unit with a 48-port ADSL LIM in slot 3 and slot 11, and a 24- port ADSL LIM in slot 5. The dmtaldsllines -a command displays the status and nailed group information for all ADSL ports in the Stinger unit.
  • Page 127 00547) Line 1 11 48 } (Down Idle DOWN DOWN 00548) The following sample command displays all available ADSL lines in the Stinger unit: admin> dmtaldsllines -f Free DMT ADSL lines: (dvOp dvUpSt dvRq sAdm nailg) Line 1 3 5 }...

  • Page 128: Displaying T1 And E1 Interfaces

    00258) Displaying IMAgroups The imagroups command displays the status of IMA groups that have been created, or those that are in use, free, or disabled on T1 or E1 modules in a Stinger unit. For example: admin> imagroups -a All IMA groups:...

  • Page 129: Displaying The Current Time

    The adslmib b port command displays ATU-C and ATU-R train-up data. For example: gs-72-1/3> adslmib b 1 <<< ATU-C Channel Entry >>> InterleaveDelay: 16 CurrTxRate: 20297000 PrevTxRate: 0 CrcBlkLength: 43131 <<< ATU-R Channel Entry >>> InterleaveDelay: 16 CurrTxRate: 1018300 PrevTxRate: 0 CrcBlkLength: 2163 Stinger® Administration Guide 5-11...

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

    Curr15MinLofs: 0 sec Curr15MinLoss: 0 sec Curr15MinLols: 0 sec Curr15MinLprs: 0 sec Curr15MinESs: 0 sec Curr15MinInits: 0 Curr1DayTimeElapsed: 12597 sec Curr1DayLofs: 0 sec Curr1DayLoss: 0 sec Curr1DayLols: 0 sec Curr1DayLprs: 0 sec Curr1DayESs: 0 sec Curr1DayInits: 1 5-12 Stinger® Administration Guide...

  • Page 131: Displaying Adsl Block Counts

    For example: gs-72-1/3> adslmib q 1 <<< ATU-C Channel Performance Data Entry >>> RxBlks: 675786 TxBlks: 698694 CorrBlks: 60 UcorBlks: 0 ValidIntervals: 14 InvalidIntervals: 0 Curr15MinTimeElapsed: 154 Curr15MinRxBlks: 7729 Stinger® Administration Guide 5-13...

  • Page 132: Displaying Performance Data Interval

    1 1 <<< ATU-C Interval Performance Data Entry >>> Number: 13 Lofs: 0 sec Loss: 0 sec Lols: 0 sec Lprs: 0 sec ESs: 0 sec Inits: 0 ValidData: 1 <<< ATU-R Interval Performance Data Entry >>> 5-14 Stinger® Administration Guide...

  • Page 133: Displaying Channel Performance Intervals

    <<< ATU-C Interval Channel Performance Data Entry >>> Number: 14 recvBlks: 49560 txBlks: 51240 corrBlks: 3 uncorrBlks: 0 ValidData: 1 <<< ATU-R Interval Channel Performance Data Entry >>> Number: 14 recvBlks: 51240 txBlks: 49560 corrBlks: 63 uncorrBlks: 0 ValidData: 1 Stinger® Administration Guide 5-15...

  • Page 134: Displaying Monitor Parameters

    Adjusted One Second: 1000 Displaying initialization failure statistics The adslmib f port command displays initialization failure counts. For example: gs-72-1/3> adslmib f 1 Data Init Fail: 0 Config Init Fail: 0 Protocol Init Fail: 0 No Peer Seconds: 0 5-16 Stinger® Administration Guide...

  • Page 135: Monitoring Lim And Lim Port Redundancy

    Stinger unit to automatically activate—when a previously active LIM or LIM port goes offline. A fast-restore capability enables Stinger units with redundant control modules to restore the data path of cross-connections within about 10 seconds following a failover of the primary control module.

  • Page 136: 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 137: Displaying Redundancy Or Ignore-Lineup Settings For Lim Ports

    (LPM-Rs) in older Stinger units are reported as Empty by the rearslotshow command. Note When a copper loop is being tested on a Stinger LS with a PSM or a CLT module, the rearslotshow command does not display any midplane sparing bus usage.

  • Page 138: Monitoring Redundant Trunk Groups

    Auto Monitoring redundant trunk groups To display information about the Stinger unit’s trunk port redundancy operations, use the -s option with the atmtrunks command. The following sample command shows the output of the atmtrunks -s command, followed by field descriptions.
  • Page 139 Using extended profiling ......... . 6-13 Using a script to configure a Stinger unit ......6-14 Timing the saving of profiles .

  • Page 140: Chapter 6 Managing System Configuration And Memory

    Displaying NVRAM usage statistics Saving the configuration to a local file To save the Stinger configuration to a file on the system you are using to access the Stinger unit, enable the capture function in your VT100 emulation software, and enter the save command as follows: admin>...

  • Page 141: Clearing System Configuration

    On a redundant Stinger unit, the system looks for the default.cfg file only in the primary control module. If the system finds a default.cfg file, it loads the saved configuration to NVRAM and then restarts with the configuration information that was saved to the default.cfg file.

  • Page 142: Loading A Default.cfg File From The Tftp Server

    Managing System Configuration and Memory Retaining configuration information after clearing NVRAM On Stinger units with dual control modules, you can issue the nvram command from the primary control module only. Note You must upgrade both the control module boot code and the control module software to the current software version to use the default.cfg feature.

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

    System Integrity checking in restoring from default.cfg will take a few minutes. User must not make changes to system profile(s) at this time. ****** WARNING ***** WARNING ****** WARNING ****** WARNING ******* WARNING configuration being restored from flash file 1/current/default.cfg... configuration loaded from flash. Stinger® Administration Guide...

  • Page 144: Restoring Or Updating System Configuration

    The code image or script can be located on the disk of the PC you are using for the terminal session with the Stinger unit, on a network host that supports TFTP, or on the PCMCIA flash card file system of the control module.

  • Page 145: Transferring Code Images Between Control Modules

    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 146 Finally, the following error messages can also appear when you use the load command to upload an image to a PCMCIA flash card on a Stinger unit: Message Explanation...

  • Page 147: Using Ftp To Transfer Files

    At this prompt, you can enter the FTP service command open to connect to a particular FTP host. For a description of open and the other FTP service commands, see the Stinger Reference. Typical command-line FTP file transfer The following example shows a File Transfer Protocol connecting to a FTP server,...

  • Page 148: Ftp Client Url Interface

    URLs in file transfer scripts. To use the FTP protocol to transfer a file, place a URL with the following syntax in your Stinger command line: ftp [options] //username:password@hostname:port/url-path/filename;type=a|i local-dir For details about the preceding syntax, see the Stinger Reference. 6-10 Stinger® Administration Guide...

  • Page 149: Username And Password Details

    //host.com/%2Fetc/motd Typical FTP URLs The following examples show how to transfer files by means of URLs. Sample FTP URL with complete syntax The following URL performs the following tasks: ftp //foo:bar@135.254.196.191/%2Fhome%2Ftest/ftptest.txt;type=a current Stinger® Administration Guide 6-11...

  • Page 150: 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/...

  • Page 151: Using Extended Profiling

    Restoring an earlier configuration after enabling extended profiling Because software releases are not necessarily backward compatible, Lucent Technologies recommends that you restore a backup configuration made under the earlier software version or one of its predecessors. Stinger® Administration Guide 6-13...

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

    TAOS command-line interface. Log into the Stinger unit with sufficient permissions to change the configuration. To upload the file to the Stinger unit, use the upload file feature of your Telnet terminal software. Following is an example of a text file that configures an SDSL line in shelf 1, slot 7:...

  • Page 153: Timing The Saving Of Profiles

    Item-Number, as required. Carefully review your text file to make sure it is correct. Use an ASCII text upload to upload the text file directly to the Stinger unit prompt. Carefully review your changes through the console.

  • Page 154: Using The Load-Select Profile

    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 155: Loading An Extracted Code Image

    If there is no difference between the profiles, then no special action is needed. 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 Stinger® Administration Guide...

  • Page 156: Formatting A Flash Card

    Formatting a flash card Before using a PCMCIA flash card in the Stinger unit, you must format it. First insert the card into slot 1 or slot 2 in the control module, then use the format command.

  • Page 157: Checking The File System

    Managing PCMCIA flash cards gunzip command. The system-level gzip and gunzip commands function just like the UNIX gzip and gunzip commands. For syntax information, see the Stinger Reference. Note Due to differences in implementation, files compressed with the TAOS gzip command may not be identical to files compressed with the UNIX gzip command.
  • Page 158 Number of Clusters: 3448 FAT Type: Fat12 Cluster Usage Usable Clusters: 3446 Free Clusters: 3446 Clusters lost during interrupted writes: 0 Other reserved clusters: 0 For details of the command-line options for the fsck command, see the Stinger Reference. 6-20 Stinger® Administration Guide...

  • Page 159: Administering The Snmp Agent

    Overview of Stinger SNMP support ........

  • Page 160: 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 161: Activating The Snmp Agent

    Parameter Task csm-modem-diag Does not apply to the Stinger unit. 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. —The SNMP agent uses only the SNMPv1 v1-only protocol and discards any other types of messages.

  • Page 162: Securing The Snmp Agent

    SNMP written Securing the SNMP agent TAOS provides the following means to secure the SNMP agent in the Stinger unit against unwanted access from remote SNMP managers, to specify the type of access granted to SNMP managers, and to configure encryption and authentication for the communications between the agent and managers: Ability to specify community strings when you enable read-write access.

  • Page 163: Configuring The Snmp-Manager Profile

    Name (up to 31 characters) or IP address (in dotted decimal notation) of the host SNMP manager that sends SNMP requests to the Stinger SNMP agent. If the Domain Name System (DNS) or Network Information Service (NIS) is supported, the system uses this name to look up the LAN address.

  • Page 164: Example Of Configuring Host Address Security

    SNMPv3 USM is described in RFC 2574, User-based Security Model for SNMPv3. Enabling privacy causes the Stinger unit to accept encrypted requests from an SNMP manager and send responses in encrypted format. The encryption uses a 64-bit Data Encryption Standard (DES) algorithm. The system uses your privacy password to generate a private key for the encryption.

  • Page 165: Enabling Snmpv3 Usm Privacy

    Timeliness—Protects against message delay or replay. Discovery—Allows an SNMP manager to obtain sufficient information about the Stinger units’ SNMP agent to establish communication between an SNMP manager station and the Stinger units. GetBulkRequest—Added from SNMPv2 to allow the SNMPv3 manager to minimize the number of protocol exchanges required to retrieve a large amount of management information.
  • Page 166 Enable/disable SNMPv3 user-based security model (USM) features for this user. The default value is no. read-write-access Enable/disable read-write access to the Stinger unit’s MIBs for this user. With the default value no, the user has read access only, which enables viewing but not modification of the MIBs.

  • Page 167: Generating Authentication Keys

    Otherwise, the authentication key appears as a row of asterisks. The default is null. For more information, see the Stinger Reference. Privacy key for SNMPv3 USM users. In most cases, you do priv-key not set this string directly.

  • Page 168: Example Of Snmpv3 Usm Configuration

    The following commands specify the use of MD5 authentication for messages sent on behalf of a user named testv3 to or from the SNMP engine. The user is assigned read-write access to the Stinger unit’s MIBs. admin> new snmpv3-usm-user testv3 SNMPV3-USM-USER/testv3 read admin>...

  • Page 169: 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. You can specify the destinations for traps and the format of outgoing trap PDUs.
  • Page 170 The default value, no, specifies that the profile is not used to generate notifications. msg-proc-model Message-processing model to use when generating SNMP messages. The default setting, v1, specifies SNMP version 1. Specify v3 for SNMPv3 notifications support. 7-12 Stinger® Administration Guide...

  • Page 171: Configuring View-Based Access Control

    Specify view names for different kinds of access (read, write, notify) by setting parameters in the vacm-access profile. A view specifies whether a given OID is accessible. Define views by setting parameters in the vacm-view-tree profile. Stinger® Administration Guide 7-13...

  • Page 172: Enabling Vacm

    [in VACM-SECURITY-GROUP/{ v1 "" } (new)] security-properties* = { v1 "" } active = no group-name = "" admin> set active = yes admin> set group-name = groupNY admin> list security-properties [in VACM-SECURITY-GROUP/{ v1 "" }:security-properties (new) (changed)] 7-14 Stinger® Administration Guide...

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

    Security model in use. properties: v1 (the default)—The SNMPv1 security model. security-model v3-usm—SNMPv3 USM. For VACM support, specify v3-usm. Stinger® Administration Guide 7-15...

  • Page 174: Defining Views

    To define a view, set parameters in the vacm-view-tree profile. Following is a listing of the profile’s default values: [in VACM-VIEW-TREE/{ "" "" }] tree-properties* = { "" "" } active = no tree-mask = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff tree-type = included view-name = "" view-tree-oid = "" 7-16 Stinger® Administration Guide...

  • Page 175: Managing Snmp Interfaces

    VACM-VIEW-TREE/{ view1 1.3.6.1.4.1.529 } written Managing SNMP interfaces The Stinger unit supports the Interface MIB based on RFC 2233, which supersedes the interfaces group of the SNMP MIB-II, defined in RFC 1213. The interface table contains only the system’s physical interfaces and dedicated (nailed) interfaces.

  • Page 176: Verifying Snmp State

    Stinger unit deletes that profile and creates a new one, with a new SNMP interface number. However, the previous device’s SNMP interface number does not become available until next time the system is reset or power to the unit is turned off and then turned back on, the old device’s SNMP interface number becomes available...

  • Page 177: Using The Admin-State-Phys-If Profile

    26 04/17/2003 14:19:42 { shelf-1 first-control-module 32774 } 25 04/17/2003 13:19:25 { shelf-1 first-control-module 32775 } 25 04/17/2003 13:19:26 { shelf-1 slot-16 22 } 25 04/17/2003 13:19:26 { shelf-1 slot-16 23 } 25 04/17/2003 13:19:26 { shelf-1 slot-16 24 } Stinger® Administration Guide 7-19...
  • Page 178 24 04/17/2003 13:19:25 { shelf-1 trunk-module-2 5 } 24 04/23/2003 21:03:28 { shelf-1 trunk-module-2 6 } The Stinger unit creates a profile for each of its physical interfaces. The admin-state- phys-if profile contains the following parameters, shown here with sample values:...

  • Page 179: Viewing Snmp Interface Numbers

    -d 2 interface 2 state change forced To reenable a disabled device, use the if-admin command with the -u option, and specify the interface number. For example: admin> if-admin -u 2 interface 2 state change forced Stinger® Administration Guide 7-21...

  • Page 180: Resetting The Snmp Interface Table Sequentially

    Naming convention for SNMP-configured profiles Resetting the SNMP interface table sequentially By default, the SNMP interface table is built as modules are installed in the Stinger unit. The if-admin command -r option enables you to reset the order of the table to be sequential based on slot number.

  • Page 181: Configurable Naming Convention

    147 11/25/2001 18:28:05 1:1-0-50x17:1-0-50 146 11/25/2001 18:36:25 1:1-15x17:1-15 Selecting the naming convention for connection profiles Following is the parameter, shown with its default value, for configuring the naming convention for connection profiles: [in SYSTEM] connection-profile-auto-naming-convention = lower-interface-number-first Stinger® Administration Guide 7-23...

  • Page 183: Chapter 8 Watchdogs, Alarms, And Traps

    An SNMP watchdog is a software routine that monitors the status of a particular aspect of a Stinger unit—for example, the temperature of a module. You can enable or disable the warning trap for each individual watchdog and specify a watchdog name by means of the TAOS command-line interface or SNMP.
  • Page 184 34 11/06/2003 00:22:27 { external-fan cm-input-relay 4001 } 26 11/06/2003 00:22:27 { door cm-input-relay 4001 } Profiles corresponding to a remote shelf are created or deleted on the host Stinger unit depending on the operational state of the remote-shelf-stat profile for that remote shelf.

  • Page 185: 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 186: 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. To verify that your system supports this capability, see the Getting Started Guide for your unit at http://www.lucentdocs.com/ins.

  • Page 187: Overview Of Alarm Profile Settings

    You can define an alarm profile for every event that you would like to monitor. Following is a listing of the alarm profile contents, shown with default settings. For additional information about these parameters, see the Stinger Reference. [in ALARM/"" (new)] name* = ""...
  • Page 188 Number of seconds that the Stinger unit leaves alarm- duration relay-minor in the position specified in the alarm-relay- minor action. The default value 0 (zero) directs the Stinger unit to leave the alarm set indefinitely. Stinger® Administration Guide...

  • Page 189: Sample Alarm Profile Configuration

    You can use the alarm command or the alarm-stat profile to list alarms and their status, or acknowledge and clear them. Listing alarms using the alarm command To list the alarms that are enabled for the entire Stinger unit, use the alarm -l command as in the following example: admin> alarm -l...

  • Page 190: Using The Alarm-Stat Profile

    State of the alarm. Following are the valid values: alarm-active—The alarm is active, and appropriate action has been taken (setting status lights or closing relays). alarm-acknowledged—The alarm has been acknowledged by the user. Stinger® Administration Guide...

  • Page 191: Acknowledging Alarms

    If for a remote shelf you configure an alarm to be active by setting its value to yes, an action is triggered and volatile profiles are updated. An emergency level log message is generated whenever the alarm is raised or cleared. Stinger® Administration Guide...

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

    A sensor on the remote shelf indicates failure of the internal fan unit. The failed status is shown in the internal-fan-unit-failed setting of the remote-shelf-stat profile. 8-10 Stinger® Administration Guide...
  • Page 193 LOG emergency, Shelf 1, Controller-1, Time: 14:28:16-- Wed Sep 17 14:28:16 2000 - ALARM: Remote Shelf { 3 } Alarm is: Cleared HOST> alarm -s Type Address State Stinger® Administration Guide 8-11...

  • Page 194: Monitoring Environmental Conditions

    = 30 admin> write THERMAL written Create alarm profiles for low-temperature and high-temperature events and define the list of actions Stinger take if either temperature alarms is raised. admin> new alarm thermal ALARM/thermal read admin> set event = high-temp admin>...

  • Page 195: Setting The Maximum Number Of Alarms In Alarmcleartable

    To delete an alarm model table, delete the corresponding trap profile. Configuring SNMP traps Stinger units generate traps (notifications) for important events. You create and enable traps and specify their destination using a trap profile. When you have configured a trap profile to generate a trap protocol data unit (PDU) on detection of a certain event, if the event occurs, the system sends a PDU to a specified SNMP station.

  • Page 196: Configuring The Trap Profile

    The following sample commands instruct the unit to send traps to an SNMP manager at the IP address 1.1.1.1: admin> read trap remote1 TRAP remote1 read admin> set host-address = 1.1.1.1 admin> write TRAP remote1 written 8-14 Stinger® Administration Guide...

  • Page 197: Trap Classes

    For a Stinger unit to send a trap for the events listed in Table 8-3, accept the default setting of yes for the alarm-enabled parameter and enable the parameter for that specific event.
  • Page 198 Watchdog warning has occurred. watchdog-warning- WatchdogWarning enabled Change in primary control module in a controller- Controllerswitchover unit with redundant control modules. switchover-enabled Change in the state of an E1 or T1 line. wan-line-state- WanLineStateChange change-enabled 8-16 Stinger® Administration Guide...
  • Page 199 Failure in the a communication link trap-enabled between the Stinger SNMP agent and SNMP manager. ascend-link-up-trap- ascendLinkUp Reestablishment of a failed communication enabled link between the Stinger SNMP agent and SNMP manager. ascend-multicast- multicastLinkUpTrap A multicast group join activity has link-trap-enabled occurred. Stinger® Administration Guide...

  • Page 200: Security Class Traps

    A change in the state of a remote shelf. remote-shelf-enabled Security class traps By default, the security class is disabled. To enable the Stinger unit to send one or more of the traps listed in Table 8-4, set the security-enabled parameter to yes: [in TRAP/""] admin>...

  • Page 201: Port Class Trap

    Port class trap By default, the port class is disabled. For the Stinger unit to send the trap listed in Table 8-5, you must set the port-enabled parameter to yes. [in TRAP/""]...

  • Page 202: Ospf Class Traps

    OSPF class traps Stinger units support OSPF class traps as defined in RFC 1850, OSPF Version 2 Management Information Base. By default, OSPF traps are disabled. To generate an OSPF trap when an event shown in Table 8-7 occurs, enable OSPF traps either in the trap profile or by setting the corresponding bit in the MIB object, ospfSetTrap, defined in RFC 1850.
  • Page 203 (for example, from point-to-point to down) or progresses to a terminal state, such as point-to-point. ospf-virt-if-rx-bad-packet A Stinger unit virtual interface received an OSPF OSPF Trap 9 packet that cannot be parsed. ospf-virt-if-tx- An OSPF packet has been retransmitted on a...

  • Page 204: Typical Uses Of Traps And Trap Classes

    OSPFExtLsdbLimit. Example of setting an OSPF trap The following commands cause the system to generate traps when the Stinger unit receives a packet from an OSPF router in which a configuration mismatch (such as an invalid OSPF version number or an address conflict) or an authentication failure occurs: admin>...

  • Page 205: Traps Not Belonging To Any Class

    Monitoring ADSL threshold values Stinger units can generate traps and alarms when certain ADSL line conditions reach specified threshold values. To enable the supported threshold traps in the ADSL MIB,...

  • Page 206: Specifying The Dsl-Threshold Profile

    15-minute performance data collection period, which causes the SNMP agent to send a trap. One trap is sent per interval per interface. A value of 0 disables the trap. Enter a value from 0 through 900. 8-24 Stinger® Administration Guide...

  • Page 207: Lucent-Specific Adsl Threshold Traps

    Errored Second 15-minute interval ascendAdslAtucPerfESsThreshTrap threshold reached at the ATU-C end. Loss of Link 15-minute interval threshold ascendAdslAtucPerfLolsThreshTrap reached at the ATU-C end. Loss of Framing 15-minute interval ascendAdslAturPerfLofsThreshTrap threshold reached at the ADSL transceiver unit-remote (ATU-R) end. Stinger® Administration Guide 8-25...

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

    E3-ATM, DS3-ATM, OC-3/STM-1, OC-12/STM-4 ports trunk ports, and T1 and E1 trunk ports on the Stinger MRT. The system generates a link down trap at boot time only for the physical layer of the trunk port. The system does not generate linkDown traps for LIM ports such as ADSL, SHDSL, and E1 and T1.
  • Page 209 Link state traps are enabled for this port, that is, in the admin-state-phys-if and admin-perm-state-if profiles. A trunk module or TRAM is installed in the Stinger chassis. Linkdown and Linkup traps are enabled in trap profile for this trap destination.

  • Page 210: Configuring Trap Sequencing And Heartbeat Traps

    Trap sequencing and the heartbeat trap You can configure a Stinger unit to add sequence numbers to traps. With the trap sequencing feature enabled, the Stinger unit increments the trap sequence number before sending it, which provides a means for the NavisAccess® management software to detect if any trap was lost in transit.

  • Page 211: Configuring Trap Sequencing And The Sending Of Heartbeat Traps

    The traps are replayed using the notification log MIB and its extension. Therefore, for this feature to work, you must also enable the notification log on the Stinger unit (the notify-log-enabled parameter must be set to yes).

  • Page 212: Enabling Traps For Events On Remote Shelves

    Watchdogs, Alarms, and Traps Configuring SNMP traps Sample configuration The following sample commands configure the Stinger unit to generate traps with sequence numbers and to generate a heartbeat trap 10 minutes after it last sends a trap. admin> new trap navisnlm TRAP/navisnlm read admin>...

  • Page 213: Stinger Trap Optimization

    Configuring SNMP traps Stinger trap optimization You can optimize the number of traps that are generated by the Stinger system to make the traps more meaningful to an end user. A Stinger system can generate a large number of traps whenever a slot status changes. Most traps that are generated by the system are link up or link down traps.

  • Page 214: Trap Optimization

    Displaying information about notification logs The nlmstat debug command shows information about notification logs for a Stinger unit. The nlmstat command is available only in the debug environment. Its syntax is...

  • Page 215: Table 8-10 Description Of Fields For The Output Of The Nlmstat Command

    The value of Limit is the same as the value of notification-log-limit parameter in the trap profile. Logged Number of notifications logged by the Stinger unit for the trap profile. Bumped Number of log entries discarded to make room for a new entry when the total number of entries has exceeded the configured limit specified in the trap profile.

  • Page 216: Table 8-11 Additional Fields Reported By The Nlmstat Ipaddress Command

    Trap version. Reported values can be v1 (SNMPv1) or v3 (SNMPv3). The Stinger unit creates a profile for each of its physical interfaces. The admin-state- phys-if profile contains the following parameters, shown here with sample values: [in ADMIN-STATE-PHYS-IF/{ shelf-1 slot-4 1 }]...
  • Page 217 Down traps are generated for the interface, or to trap-state-disabled if you specify that link Up and link Down traps are not generated for the interface. Stinger® Administration Guide 8-35...

  • Page 219: Working With Ip Traffic

    The ping command is useful for verifying that the transmission path between the Stinger unit and another station is open. Ping sends an ICMP Echo-Request packet to the specified station. If the station receives the packet, it returns an ICMP Echo- Response packet.

  • Page 220: Displaying The Ip Interface Table

    The ping command also supports the -f option, which sets the Don’t Fragment (DF) bit in the IP header of ping packets. Setting the DF bit enables the Stinger unit to discover the datagram size, or path maximum transmission unit (PMTU), of the path from the remote host.
  • Page 221 Network or the target host this interface can reach. Address Address of this interface. Ipkts Number of packets received. Ierr Number of packets that contain errors. Opkts Number of packets transmitted. Oerr Number of transmitted packets that contain errors. Stinger® Administration Guide...

  • Page 222: Displaying And Modifying Ip Routes

    Column Indicates Destination Route’s target address. To send a packet to this address, the Stinger unit uses this route. If the target address appears more than once in the routing table, the Stinger unit uses the most specific route (having the largest subnet mask) that matches that address.

  • Page 223: Modifying The Ip Routing Table

    For syntax information, see the Stinger Reference. Adding a static IP route to the routing table To add a static IP route to the Stinger unit’s routing table, use the iproute add command. For example, the following command adds a route to the network 10.1.2.0 and all its subnets through the IP router located at 10.0.0.3/24.

  • Page 224: Tracing Ip Routes

    Probes start with a TTL of 1 and increase by 1 until one of the following conditions occurs: The Stinger unit receives an ICMP port unreachable message. (The UDP port in the probe packets is set to an unlikely value, such as 33434, because the target host is not intended to process the packets.
  • Page 225 The total-packets-received count includes the total packets dropped. For an explanation of the preceding output, see the Stinger Reference. To displays the protocol statistics, use the the -s option. If no identifiers follow the -s option, the system shows all protocol statistics.
  • Page 226 0 query packets received 0 leave packets received 0 packets transmitted 0 query packets sent 0 response packets sent 0 leave packets sent mcast: 0 packets received 0 packets forwarded 0 packets in error 0 packets dropped 0 packets transmitted Stinger® Administration Guide...

  • Page 227: Displaying Ip Route Cache Information

    Verifying name service settings You can retrieve a host address by using the nslookup command, provided that the Stinger unit has been configured with the address of a name server. If a host has several IP interfaces, the command returns several addresses.

  • Page 228: Displaying The Arp Cache

    IP address sends an ARP response with its MAC address. The Stinger unit maintains a cache of known IP addresses and host MAC addresses. With the arptable command, you can display the ARP table, add or delete ARP table entries, or clear the ARP cache entirely.

  • Page 229: Displaying The Dns Host Table

    DNS fails to successfully resolve a hostname. For information about configuring the DNS host table, see the Stinger T1000 Module Routing and Tunneling Supplement. The DNS host table is not a DNS cache, but a fallback option, listing up to eight host addresses for important or frequently used connections.

  • Page 230: Displaying The Contents Of Ethernet Packets

    Zero (0) is the first Ethernet port for which to display statistics and n is the last. For example: admin> ether-stats 0Scb= 50 InProg= a1a00f6c CuStatus= 1 RuStatus= 4 Handshake 0 Tx good: Maxcollisions: 0 Latecollisions: 0 9-12 Stinger® Administration Guide...

  • Page 231: 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 232 Members ID represents members on the same Ethernet interface as the Stinger unit. All other IDs go to members of each group as they inform the Stinger unit that they have joined the group. If a client is a member of more than one group to which the Stinger unit forwards multicast packets, it has more than one multicast ID.

  • Page 233: Displaying Wan Ip Interface Information

    PPP negotiation problems. The syntax of the command is as follows: wandisplay number-of-octets-to-display If you enter the command while traffic through the Stinger unit is heavy, the resulting amount of output can make your search for information tedious. The screen might even display the message ----- data lost -----, which means that not all the output can be displayed on the screen.

  • Page 234: Displaying Wan Data For A Particular User

    To use the wanopening command, you must first open a session with a LIM. using the open command. Then, enter the wanopening command with the maximum number of octets to display per packet. If you specify 0 (zero), the Stinger unit does not log WAN data.
  • Page 235 Displaying WAN IP interface information [0000]: 7E 21 45 00 03 EE 54 2B 40 00 37 06 BA 09 CF 2B [0010]: 00 86 D0 93 91 90 1A 0A Note that the bytes are displayed in hexadecimal format. Stinger® Administration Guide 9-17...

  • Page 237: Overview Of The Ospf Command

    Size of the OSPF routing table. See “Displaying the OSPF database” on page 10-4. database OSPF database summary. See “Displaying the OSPF database” on page 10-4. OSPF external autonomous system advertisements. See “Displaying OSPF external advertisements” on page 10-6. Stinger® Administration Guide 10-1...

  • Page 238: Displaying General Information About Ospf Routing

    (ABR). Note With the current release, a Stinger unit cannot operate as an ABR, so each Stinger unit’s OSPF interface belongs to the same area. See “Displaying the OSPF link-state database” on page 10-7.
  • Page 239 Ethernet interface. Border router capability. This column displays yes if the AS boundary capability Stinger unit functions as an ASBR or no if it does not function as an ASBR. Attached areas Number of areas to which this Stinger unit attaches.

  • Page 240: Displaying The Ospf Database

    # Dijkstra runs Number of times that the Stinger unit has run the Dijkstra algorithm (short path computation). Number of summary updates that the Stinger unit runs Incremental summ.
  • Page 241 0x80000001 202 0x9f16 ASE5 11.0.0.0 10.103.0.254 0x80000027 250 0x49a6 ASE5 11.103.0.0 10.103.0.254 0x80000121 250 0xfc10 ASE5 14.240.0.0 10.103.0.204 0x800001a4 199 0x0926 ASE5 50.151.0.2 10.103.0.254 0x80000121 250 0xa90a ASE5 101.103.0.0 10.103.0.254 0x80000121 250 0x664c # advertisements: Checksum total: 0x191d3a Stinger® Administration Guide 10-5...

  • Page 242: Displaying Ospf External Advertisements

    0x8000004f 1648 0x9b71 ASE5 10.103.7.0 10.103.0.204 0x8000004f 1642 0x907b ASE5 10.103.8.0 10.103.0.204 0x8000004f 1617 0x8585 ASE5 214.240.0.127 10.103.0.204 0x800001a4 175 0xdb0b ASE5 223.57.40.0 10.103.0.254 0x80000121 226 0x7540 ASE5 223.57.40.244 10.103.0.254 0x80000121 226 0xe3dc # advertisements: Checksum total: 0x1a1d9e 10-6 Stinger® Administration Guide...

  • Page 243: Displaying Ospf Internal Advertisements

    To display the link-state database for the first configured area (or for the only defined area), include the lsdb option with the ospf command. The Stinger unit does not currently operate as an ABR, so each Stinger unit’s OSPF interface belongs to the same area.
  • Page 244 Total number of entries in the link-state database. #advertisements Checksum of the link-state database. Checksum total You can expand each entry in the link-state database to view additional information about a particular LSA, as explained in the next section. 10-8 Stinger® Administration Guide...

  • Page 245: Displaying Ospf Lsas

    You can select the first four fields and paste them in after typing the command. The following sample command shows an expanded view of an LSA from a Stinger unit in area 0.0.0.0 for an external route to the target address 10.5.2.160 from a router at 10.5.2.162:...

  • Page 246: Displaying The Ospf Routing Table

    Area ID of the route. Cost Cost of the route. Flags Hexadecimal number representing an internal flag. Next hop(s) Next hop in the route to the destination. IfNum Number of the interface used to reach the destination. 10-10 Stinger® Administration Guide...

  • Page 247: Displaying Information About Ospf Areas

    Type of authentication: simple password, MD5, or null. Area Type Type of OSPF area: normal, stub, or NSSA. #ifcs Number of Stinger unit interfaces specified in the area. #nets Number of reachable networks in the area. Number of reachable routers in the area.

  • Page 248: Displaying Ospf Interfaces

    The fields in the output contain the following information: Field Setting Ifc Address Address assigned to the Stinger unit’s Ethernet interface. To identify WAN links, use the Type and Cost fields. Phys Name of the interface or the connection profile for WAN links.

  • Page 249: Displaying Information About A Specific Interface

    Number of adjacencies on the interface. #adjs 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 250: Displaying Ospf Neighbors

    # Mcast acks Number of multicast acknowledgments on the interface. Displaying OSPF neighbors To display information about OSPF neighbors to the Stinger unit, include the nbrs option with the OSPF command. For example: admin> ospf nbrs Neighbor ID Neighbor addr...
  • Page 251 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. Neighbor addr IP address of the router used to reach a neighbor (often the same address as the neighbor itself).

  • Page 253: Monitoring Atm Networks

    The following sections describe the commands and profiles that you use to monitor Asynchronous Transfer Mode (ATM) and Private Network-to-Network Interface (PNNI) operations. For more information about the commands described in this chapter, see the Stinger Reference. Monitoring ATM networks Table 11-1 lists the profiles and commands that you use for monitoring ATM operations.

  • Page 254: Using The Atm Status Window

    The atmvccstat command displays an 80-column by 24-row VT100 status window of active virtual channel connections (VCCs). This window behaves similarly to other status windows supported in the Stinger unit, as described in “Using the status window” on page 1-30.

  • Page 255: Determining Atm Line Status

    The top right area of the window displays general status information about the Stinger unit, including its serial number, the version of system software that is running, and the number of cells transmitted and received. This area also shows the current system date and time and how long the system has been running since its most recent restart.

  • Page 256: Displaying The Status Of Atm Internal Lines

    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> atminternallines -a...

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

    For an ATM circuit, the value of this parameter is always connecting (point-to-point connecting). The other possible value is terminating. (For details, see the Stinger ATM Configuration Guide.) The system also creates an atmpvc-stat profile for each configured ATM circuit. Following are the relevant parameters, shown with sample settings:...

  • Page 258: Checking The Status Of A Terminating Pvc

    To display overall ATM virtual channel connection (VCC) information and packet statistics for a particular slot on a Stinger unit, use the atmvccmgr debug command. For the system to respond to this command, your user profile must be enabled with 11-6 Stinger®...

  • Page 259: Displaying Atm Virtual Link Information

    An ATM connection between two devices is a virtual link. A virtual link can be a virtual channel link (VCL) or virtual path link (VPL), depending on whether it is identified by a VPI-VCI pair or the VPI field alone. For more details, see the Stinger ATM Configuration Guide.
  • Page 260 In the preceding examples, the fields report the following information. Field Indicates Intf ATM interface index. Slot Slot number in the Stinger unit. Port Port number on the specified slot. VPI assigned to the link. VCI assigned to the link (atmvcl command only). XConnID Cross-connect ID, which indicates whether the link is cross- connected to another link to form an ATM circuit.
  • Page 261 Cross Connect ID = 1 The output of the preceding examples reports the following information: Field Indicates Physical Address Address of the physical interface in the Stinger unit. Interface ATM interface index. VCC Endpoint Whether the link terminates a virtual connection (yes or no).

  • Page 262: Displaying Atm Virtual Link Cross-Connect Information

    Displaying ATM virtual link cross connect information A cross-connect is a configuration in which the Stinger unit receives a cell stream on one interface and transmits it on another interface. Cross-connects are called ATM circuits in the Stinger command-line interface. For more details, see the Stinger ATM Configuration Guide.

  • Page 263: Displaying Spvc Information

    The spvcc command displays information about soft PVC (SPVC) connections. To display information about SPVCs that use virtual-path switching (SPVPs), use the spvpc command. For syntax information, see the Stinger Reference. With no options on the command line, the commands display the usage statement.
  • Page 264 Field Indicates Profile Name of the profile in which the SPVC or SPVPC is configured. Physical Address Address of the physical interface in the Stinger unit. Interface ATM interface index. OperStatus Current operational status of the SPVC. VCL Vpi VPI value of the initiating PVC.

  • Page 265: Displaying Spvc Target Atm Addresses

    Displaying SPVC target ATM addresses Each trunk port and LIM port that supports ATM has an associated ATM interface. In 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 266: Monitoring Failing Spvcs

    Received Restarts = 0 Transmitted Restarts = 0 Incoming SVCs established = 0 Outgoing SVCs established = 6 Configured Signalling Type = pnni1dot0 Actual Signalling Type = pnni1dot0 Configured UNI Side = other Actual UNI Side = symmetric 11-14 Stinger® Administration Guide...

  • Page 267: Displaying Cac Bandwidth Allocation Statistics

    -c 11 Displaying CAC bandwidth allocation statistics To ensure that the guaranteed characteristics can be delivered, Stinger units use a form of connection admission control (CAC), which keeps track of how much guaranteed bandwidth has been allocated and allows you to specify an oversubscription factor for trunk ports.
  • Page 268 (RT-VBR), 2 for Nonreal-time variable bit rate (NRT-VBR), or 3 for unspecified bit rate (UBR). admin> atmcacstat -c 0 Quality of Service : CBR Connection Stream Peak Rate Sustainable Rate Count vc-6-2-0-70 vc-6-2-0-70 spvc-1-1-1-1.1 11-16 Stinger® Administration Guide...

  • Page 269: Displaying Atm Connection Failures

    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 atmconnectionfailures command. For example: admin> atmConnectionFailures Stinger® Administration Guide 11-17...

  • Page 270: Displaying Qos Statistics

    To display the quality of service (QoS) statistics on ATM connections, use the atmqos command. For syntax information, see the Stinger Reference. To display all ATM connections in a Stinger unit with QoS settings, use the -a option. For example: admin>...

  • Page 271: Verifying The Pnni Link

    The preceding profile indicates that the signaling and PNNI link state are established. For a port that has not been configured for PNNI, those settings indicate that signaling and PNNI links have not been configured. For example: Stinger® Administration Guide 11-19...

  • Page 272: Displaying General Pnni Information

    = up signalling-state = not-configured pnni-link-state = not-configured For details on the parameters, see the Stinger ATM Configuration Guide. Displaying general PNNI information The pnnidisplay command displays general information about PNNI implementation, including internal counters. The command does not have any command options.

  • Page 273: Displaying Pnni Interface Information

    {1 17 1} Cbr Wt RtVbr Wt NrtVbr Wt Abr Wt Ubr Wt 5040 5040 5040 5040 5040 Port PhyAddr IntIndex Node AggrToken VpCap {1 17 2} Cbr Wt RtVbr Wt NrtVbr Wt Abr Wt Ubr Wt Stinger® Administration Guide 11-21...

  • Page 274: Displaying Information About Pnni Logical Links

    PNNI node and the relationship to nodes on the other end of the links. For syntax information, see the Stinger Reference. With no options on the command line, the command prints a summary of all PNNI logical links.
  • Page 275 The value is valid only for LinkType values of Lowest Level Outside Link or Uplink. If the node at the other end of an uplink (upnode) has not yet been identified, or if the LinkType is Lowest Level Horizontal Link, the field displays zero. Stinger® Administration Guide 11-23...

  • Page 276: Displaying Information About The Pnni Hierarchy

    PNNI hierarchy from the perspective of a local node. For syntax information, see the Stinger Reference. With no options on the command line, the command displays information about links between local and remote nodes.
  • Page 277 Rtvbr Out 5040 366792 366792 1574 1554 NrtVbr Out 5040 366792 366792 1574 1554 5040 366792 366792 1574 1554 5040 366792 366792 1574 1554 5040 366792 366792 Rtvbr Out 5040 366792 366792 NrtVbr Out 5040 366792 366792 Stinger® Administration Guide 11-25...
  • Page 278 Maximum cell rate in cells per second for the service category. Available cell rate in cells per second for the service category. Maximum cell transfer delay in microseconds for the service category. Cumulative cell delay variation in microseconds for the service category. 11-26 Stinger® Administration Guide...

  • Page 279: Displaying Details About Neighbor Nodes

    The pnninbrdisplay command displays information about the relationship between the local node and a neighboring node within the same peer group. For syntax information, see the Stinger Reference. With no options on the command line, the command displays the PNNI node ID and state of its neighbor peers.

  • Page 280: Displaying Local Node Information

    Displaying local node information With the current software version, Stinger units support a single logical node, which is always a lowest-level node. The pnninodedisplay command displays information about factors that affect the operation of the PNNI logical node. For syntax information, see the Stinger Reference.
  • Page 281 PglState State of the node regarding peer group leader election with the peer group. Following are valid values: Starting, Awaiting, Awaiting Full, Initial Delay, Calculating, Await Unanimity, Oper PGL, Oper Not PGL, Hung Election, Await Reelection. Stinger® Administration Guide 11-29...

  • Page 282: Displaying Information About Other Nodes

    With the -d option, the command displays additional details about the nodes, as shown in the following sample output: admin> pnninodetopology -d Node MapNodeId 60:a0:39:84:0f:80:01:bc:72:00:01:31:a3:99:30:ff:18:dd:98: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:30:ff:18:dd:98: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 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 11-30 Stinger® Administration Guide...
  • Page 283 (Yes or No). NodeDatabaseOverload Whether the node is currently operating in topology database overload state (Yes or No). IAmLeader Whether the originating node claims to be leader of its peer group (Yes or No). Stinger® Administration Guide 11-31...

  • Page 284: Displaying The Pnni Topology Database

    Displaying the PNNI topology database The pnniptsestatus command displays PNNI topology state elements (PTSEs) in the local node’s topology database. For syntax information, see the Stinger Reference. With no options on the command line, the command displays the current topology database, as shown in the following sample output: admin>...

  • Page 285: Displaying The Pnni Routing Table

    PNNI routing domain to valid addresses and transit networks. For example: admin> pnniroutebase pnniRouteAddrNumber = 161 The pnnireachableaddr command displays a list of all reachable addresses from each node visible to the local node. For syntax information, see the Stinger Reference. Stinger® Administration Guide 11-33...
  • Page 286 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> pnnireachableaddr -a 39:84:0f:80:01:bc:72:00:01:17:fd:27:09 AdvertisedNodeId 60:a0:39:84:0f:80:01:bc:72:00:01:17:fd:27:09:ff:e8:71:75:03:00:00 PortId Index PrefixLength (bits) 11-34 Stinger® Administration Guide...
  • Page 287 ReachableAddr field. Index Arbitrary index used to enumerate the addresses advertised by the advertising node. PrefixLength Number of significant bits in the prefix displayed in the ReachableAddr field. ReachableAddr ATM prefix of the reachable address. Stinger® Administration Guide 11-35...

  • Page 289: Chapter 12 Diagnostic Testing

    Testing DSL copper loops ......... 12-30 OAM testing Stinger units support operations, administration, and maintenance (OAM) F4 and F5 testing. ITU-T I.610 defines OAM functions.

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

    OAM F5 cells operate at the virtual circuit level and use the payload type indicator (PTI) field to distinguish between data and OAM cells. On Stinger units, F5 OAM test flows cover either an end-to-end virtual connection or only a segment of the virtual connection.

  • Page 291: Overview Of The Oam Command

    To run continuity tests, use the following command syntax: oam -C slot port vpi |-c slot port vpi [vci] e|s +|- To display OAM entries in a Stinger system, use the oam -e command. Its syntax is as follows: oam -e [slot] [port] [vpi] [vci]|-p To display a subset of the entries reported by the OAM queries, use the oam -q command.

  • Page 292: Overview Of The Atm-Oam Profile

    To run an F4 test, specify 32769 for the vci value. To run an F5 test, specify a vci value greater than 31. Valid oam-address values You can specify the shelf, slot, port, vpi, and vci values in the following combinations only. All other combinations are invalid. shelf=number, slot=number, port=0, vpi=32768, vci=32769 or vci=32768 12-4 Stinger® Administration Guide...
  • Page 293 Number of loopback-per-test cells to be sent on each ATM circuit to be tested. Specify a number from 1 (the default) through 10. The time interval between transmission of each loopback cell is 1 second. Stinger® Administration Guide 12-5...
  • Page 294 = [ 1 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 + vc-oamf4-support = [ yes yes yes yes yes yes yes yes yes yes yes yes yes yes+ 12-6 Stinger® Administration Guide...

  • Page 295: Enabling F4 Oam On A Lim

    Parameter Description Enables/disables specific F4 segment and end-to-end OAM vc-oamf4- processing on a Stinger VC-switching VPI. With the default support N yes setting, F4 segment and end-to-end processing for the specified VC-switching VPI is enabled. By default, the vc-oamf4-support parameter is enabled for all VP-switching VPIs, including all of the default vc-switching-vpi = 0 elements.
  • Page 296 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(5fe4e0:1.1.35) E2E=FALSE loop(Tx=0, Rx=0) SEG:5fe4e0:F=NORMAL CC(R=NONE:G=STOP M=STOP A=READY:D(P=DEF C=DEF)) 12-8 Stinger® Administration Guide...

  • Page 297: Continuity Check And Monitoring

    While in the default direction state, what happens when a Stinger unit receives an activation request When a Stinger unit is in the default direction and a remote peer sends a continuity check activate request, the Stinger unit accepts any direction that the remote peer specifies.

  • Page 298: Deactivating A Continuity Check Test

    Stinger unit accepts activate requests from the remote peer only if the direction specified by the remote peer is B-to-A. The Stinger direction stays in the A- to-B direction until you deactivate the test locally using the oam command or the atm- oam profile, at which point the direction reverts to default.

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

    Note that the continuity check direction for this continuity check is now set to A-to-B (Stinger unit to the remote peer), and remains in the A-to-B direction until you stop the test using the oam command, as in the example below: admin>...

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

    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 301 OAM: received our F5 OAM segment loopback #0 The following sample commands run an F5 OAM segment loopback test from the SHDSL/HDSL2 LIM in slot 4 of a Stinger unit to the CPE connected to port 25 of the LIM.

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

    ATM-OAM/{{ 1 10 1} 2 35} written Testing multiple ATM circuits The following examples illustrate how multiple ATM circuits can be tested by means of a single profile. Assume that the shelf value is 1 and the slot value is 15. 12-14 Stinger® Administration Guide...

  • Page 303: Specifying That A Trap Is Sent

    Specifying that a trap is sent The error-threshold parameter in the loopback-config subprofile enables the Stinger unit to generate a trap when the number of lost cells is greater than or equal to a specified threshold value. For example: admin> set loopback-config error-threshold = 1 Stinger®...

  • Page 304: Using The Oamloop Command

    (VPI) and virtual channel identifier (VCI) on which to send the 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 305: Displaying Oam Entries

    The oc3-atm-stat, ds3-atm-stat, and e3-atm-stat profiles display the status of the trunk lines. For an explanation about the parameters in these profiles, see the module configuration guide for your device or the Stinger Reference. Displaying OAM entries You can use the oam -e and oam -q commands enable you to display OAM entries in a Stinger system.
  • Page 306 F4-SEG(8373e890:3507.1.3) loop(Tx=0, Rx=0) 8373e890:F=NORMAL CC(R=NONE:G=STOP M=STOP A=READY D(P=DEF C=DEF)) Following is an example of an F4 end-to-end output: F4-E2E(8373eaa0:3507.1.4) loop(Tx=0, Rx=0) 8373eaa0:F=NORMAL CC(R=NONE:G=STOP M=STOP A=READY D(P=DEF C=DEF)) 12-18 Stinger® Administration Guide...
  • Page 307 D: Direction. P: provisioned direction. C: current direction F4-SEG(836ebc10:2.0.3) loop(Tx=0, Rx=0) 836ebc10:F=NORMAL CC(R=NONE:G=STOP M=STOP A=READY D(P=DEF C=DEF)) F4-E2E(836d0ac0:2.0.4) loop(Tx=0, Rx=0) 836d0ac0:F=NORMAL CC(R=NONE:G=STOP M=STOP A=READY D(P=DEF C=DEF)) 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=3 Stinger® Administration Guide 12-19...
  • Page 308 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 D: Direction. P: provisioned direction. C: current direction F5(82048320:3505.0.100) E2E=FALSE loop(Tx=0, Rx=0) 12-20 Stinger® Administration Guide...

  • Page 309: Fault Reporting And Alarms

    Total matching Oam Channels=1 Fault reporting and alarms Stinger systems use SNMP traps to report OAM changes for an OAM end point. Stinger systems implement the standard OAM fault protocol, with the exception that data cells and loopback cells do not clear alarms.

  • Page 310: Traps For Ais/Rdi And Continuity Check Alarms

    Running an internal diagnostic test (IDT) The Stinger unit creates a line-diag profile for each interface or port, which you use to run internal diagnostic tests and bit-error rate tests (BERTs). You use the idt- enable and idt-num-of-msg parameters in the line-diag profile to run an internal diagnostic test.
  • Page 311 Number of erroneous messages received by the control module. (This parameter is read-only.) The following sample commands instruct the Stinger unit to run an internal diagnostic test on port 1 of slot 2: admin> read line-diag {1 2 1} LINE-DIAG/{ shelf-1 slot-2 1 } read admin>...

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

    CPE device is attached. Digital loopback When a line is enabled for digital loopback, data is looped only at the digital circuitry of the modem. Data does not reach the analog circuitry, as shown in Figure 12-1. 12-24 Stinger® Administration Guide...

  • Page 313: Analog Loopback

    This capability is available on the following LIMs with ADSL2plus capability: 72-port ADSL2+ LIM 48-port ADSL2+ LIM 48-port low-power LIM Enabling the built-in self test using the command-line interface To enable the BIST test, set the bist-enabled parameter in line-diag profile to yes. For example: Stinger® Administration Guide 12-25...

  • Page 314: Relay Alarm Testing

    -p : Toggle poll test/external input relay -i : Initialize the test -m : Toggle test input relay open/close mode -(0-7) : Set test input relay status (0=all) -t : Show test input relay status -s : Show external input relay status 12-26 Stinger® Administration Guide...

  • Page 315: Examples Using The Inputrelaytest Command

    Remember to run "inputrelaytest -p" again to return to external input relay alarm mode when finish the test! LOG emergency, Shelf 1, Controller-1, Time: 10:35:05-- Fri May 23 10:35:05 2003 - ALARM: Input Relay No. 1 OPEN Stinger® Administration Guide 12-27...
  • Page 316 -m Set relay OPEN mode admin> inputrelaytest -1 Test input relay 1 open admin> LOG emergency, Shelf 1, Controller-1, Time: 10:46:47-- Fri May 23 10:46:47 2003 - ALARM: Input Relay No. 1 OPEN 12-28 Stinger® Administration Guide...

  • Page 317: Displaying The Status Of Input Relays

    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 318: Testing Dsl Copper Loops

    To determine the status of the BERT, use the get command to display the setting for the bert-operation-state parameter. For a list of all the possible states of the line, see the Stinger Reference. The BERT is complete if the value for the bert-operation-state parameter is stopped. For example: admin>...

  • Page 319: Galvanic Isolation Test

    Physical address of the LIM associated with this profile. clt-slot-number Slot number of the CLT module or PSM installed in the Stinger unit. start-port First port to be isolated during test. This parameter is valid only if specific-ports is set to no.

  • Page 320: Using The Isolate Command

    For example, to isolate ports 3 through 5 on a LIM in slot 5, proceed as follows: admin> isolate 1 5 3 - 5 To isolate ports 3 and 9 only: admin> isolate 1 5 3 9 12-32 Stinger® Administration Guide...

  • Page 321: Multiport Tone Generation Test

    For individual ports: gen-tone shelf slot ext|aux p1 p2 ..To deactivate the test: degen-tone shelf slot For example, to connect test tones to ports 3 through 5 on a LIM in slot 5 using the auxiliary port: Stinger® Administration Guide 12-33...
  • Page 322 To connect test tones to ports 3 and 9 only using the external port, enter the following command: admin> gen-tone 1 5 ext 3 9 To stop the test, enter the following command: admin> degen-tone 1 5 12-34 Stinger® Administration Guide...
  • Page 323 Lucent OnLine Customer Support at http://www.lucent.com/support with any questions or concerns. Enabling debug permissions Before you can access the debug commands, you must log into the Stinger unit with a user profile that specifies debug privileges. To enable debugging privileges: Open a user profile: admin>...

  • Page 324: Appendix A Using Debug Commands

    Setting debug levels Debug levels vary depending on the command. But generally, the lower you set the debug level, the fewer messages the Stinger unit displays. Setting the debug level to 0 (zero) disables the debug output for the command.

  • Page 325: Summary Of Common Debug Commands

    [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. For more information on debug permissions see “Enabling debug permissions”...

  • Page 326: System And Devices Debugging

    Routing entries. If a virtual router name is specified on the command line, the command displays only the table of the virtual router. If no virtual router name is specified, the command displays the tables for all virtual routers. Stinger® Administration Guide...

  • Page 327: Displaying Network Processor Connection Information

    8 1 Connection Handles slot act cPort dPort type uctl udata dctl ddata Y 000000 000000 GE 0/866 0/866 default 0/866 0/866 default Encaps: ETH/ATM - MTU=1500 (50) Control & Data Service Queues: ------------------------------ ControlQID Lport 0008 Stinger® Administration Guide...

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

    000000 12.0.0.0/8 000000 12.12.12.12/32 local 000000 127.0.0.0/8 000000 127.0.0.1/32 local 000000 127.0.0.2/32 000000 135.254.196.0/24 210.210.210.1 000000 210.0.0.0/8 000000 210.210.210.75/32 - local 000000 224.0.0.0/4 mcast 000000 224.0.0.1/32 local 000000 224.0.0.2/32 local 000000 224.0.0.9/32 local 000000 224.0.0.13/32 local 000000 Stinger® Administration Guide...

  • Page 329: Obtaining Detailed Information For A Did

    3075 0 00000001 31 1 02A7EB0D 00000000 3075 0 00000001 32 0 054FD619 00000000 Configuration in NP: ---------------------- RSP Slot: 1 Transmit Queue Id : 8301 Last DID : Yes Begin Delta End Delta SED Script Id SED Script Parameter: ---------------------- Stinger® Administration Guide...

  • Page 330: Displaying Arp Entries

    IP QOS monitoring information for IF 19 IP QOS profile: Pav-Pbit Number of priority Lowest priority Default classification :provided Total Mcast Rules Classified DIDs Classification rules Mapping priority/COS P[0]=x P[1]=5 P[2]=x P[3]=x P[4]=4 P[5]=3 P[6]=2 P[7]=x Main DID list ------------- Stinger® Administration Guide...

  • Page 331: Displaying Bridge Group Information

    Type Learn Tree Act Value Pattern 3123 0 00103237 48 0 00000001 EB010101 The following sample command displays table entries for bridge group 50: admin> info np bridge table 50 Group PortBlock Destination ---------------------------------------------------- 00050 ROUTER 0022 43530 00:00:00:00:00:09 Stinger® Administration Guide...

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

    0 16 LPortId SchedId SchedId SchedId SchedId In the following example, entry 16 shows information for the Gigabit Ethernet interface: admin> info np psl 0 17 2 LPortId SchedId SchedId SchedId SchedId A-10 Stinger® Administration Guide...

  • Page 333: Displaying Information For A Specific Queue

    Type of information to display. Specify one of the following: Information about active connections. conn aal5 AAL5 channel information. Utopia port information. ether Ethernet port or device information. port Port number. conn-id Connection ID Stinger® Administration Guide A-11...

  • Page 334: Displaying Connection Information

    IW Mode : IW MODE BRIDGING qosType cdvt VLAN INFO vlan id : 66 VLAN INFO acceptTagged : 0 VLAN INFO acceptUnTagged: 1 atmChannel : 22 etherInfo IWMode : IW MODE BRIDGING VLAN INFO vlan id A-12 Stinger® Administration Guide...

  • Page 335: Displaying Atm Information

    Atm Bus Width 16-bit Utopia 16-bit Utopia Atm ext header size ATM Idle Cell Discard Discard Idle Cells ATM Lookup Mode Use VPI/VCI values L2 Backgrnd Processing Disabled L2 Background FIFO Size Interworking ForeGrnd Queue Mode Fast Mode Stinger® Administration Guide A-13...

  • Page 336: Displaying Aal5 Channel Information

    Fast Ethernet Trunk module. Without any arguments, the information reported by the info ether command is summarized. For example: fet-1/17> info ether P# DUPLEX SPEED STATS MRU MAC Address 1 FULL 1500 00:d0:52:07:08:09 2 FULL 1500 00:d0:52:10:11:12 A-14 Stinger® Administration Guide...
  • Page 337 VLAN Priority for prio : 4: 0 VLAN Priority Mode prio : 4: ENTRY PASS VLAN Priority for prio : 5: 0 VLAN Priority Mode prio : 5: ENTRY PASS VLAN Priority for prio : 6: 0 Stinger® Administration Guide A-15...

  • Page 338: Displaying Stinger Port Information

    Tx Restart Required : No Tx Frames Displaying Stinger port information The portinfo debug command displays information about the Stinger ports. The portinfo debug command uses the following syntax: portinfo port-number For example, the following command displays port statistics for slot 1: admin>...

  • Page 339: Modifying Stinger Unit Functionality

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

  • Page 340: Using The Acct-Failsafe Debug Command

    This command does not display any information related to the configuration of either your RADIUS authentication server or your RADIUS accounting server. As shown in the following example, a Stinger unit has been configured with two RADIUS servers, 1.1.1.1 and 2.2.2.2. The port has not been changed from its default of 1700.

  • Page 341: Displaying Radius Accounting Session Status

    No accounting request was issued, or the request failed. stop—Session is over. An accounting stop request has been issued. route Internal route ID. sessid Session ID. This setting depends on the route ID. Stinger® Administration Guide A-19...

  • Page 342: Displaying Radius Authentication And Accounting Statistics

    2. This value does not necessarily indicate a problem, but might be the result of the Stinger unit timing out a particular session before receiving an ACK from the RADIUS server. A momentarily heavy traffic load might cause this condition. The value of bad is the number of packets that were formatted incorrectly by either the Stinger unit or the RADIUS server.

  • Page 343: Interface Debugging

    Stinger unit but do not match any expected responses. The Stinger unit keeps a list of sent requests, and expects a response for each request. In the following message, one response was received from the RADIUS server that did not match any of the requests that the Stinger had sent out.

  • Page 344: Using The Eoc Command On Adsl Interfaces

    Stinger MRT unit with 36 ADSL ports 72-port ADSL Annex A LIM 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:...

  • Page 345: Control Module Debugging

    Control module debugging The following sections describe the commands that you use for control module debugging. The Stinger IP2000 Configuration Guide also describes debug commands that are used specifically for the IP2000 control module. 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.

  • Page 346: Displaying Interface Management Information

    Unknown. Cannot be determined. Displaying interface management information The ifmgr debug command displays interface-table entries, toggles the debug display, and marks an interface as enabled or disabled. You can enter this command only from the control module. A-24 Stinger® Administration Guide...
  • Page 347 200.4.4.3/32 192.168.7.133/32 019 1:17 000 - p wan19 m2t81 200.8.1.2/32 192.168.7.133/32 020 1:17 000 - p wan20 200.4.1.2/32 200.6.1.2/32 021 1:16 001 * p wan21 p1321n<>p1 0.0.0.0/32 0.0.0.0/32 [More? <ret>=next entry, <sp>=next page, <^C>=abort] Stinger® Administration Guide A-25...
  • Page 348 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. All the Ethernet interfaces and the interfaces based on connection profiles are permanent. Transient interfaces are those the Stinger unit builds from RADIUS, TACACS, or an answer profile.
  • Page 349 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. The setting of this parameter is shown in the Directed-Bcast field in the ifmgr output.

  • Page 351: Appendix B Stinger Log Messages

    PCMCIA flash card error messages........B-8 The Stinger unit logs fatal and warning error messages to the fatal error log. If the system crashes before creating a log entry, it prints a stack trace to the console serial port.

  • Page 352: 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.
  • Page 353 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)

  • Page 354: Definitions Of Warning Messages

    Definition No priority 2 task This error occurs if the Stinger has not run a priority 2 task in the last minute. Tasks in the Stinger are assigned priorities. Because the main routing task runs at priority 2, this error means that Stinger operation has been suspended for 1 minute.
  • Page 355 Stinger Log Messages Definitions of warning messages Index Definition 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. Buffer bad memory allocation...
  • Page 356 New call without disconnect request Indicates that a Disconnect message to the central office (CO) was not sent. The problem can be caused by conditions on the Stinger or at the CO. When the Stinger encounters the condition, it assumes the CO is correct, and answers the call.

  • Page 357: Fatal Crash Information On The Console

    Stinger Log Messages Fatal crash information on the console Index Definition 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...

  • Page 358: Pcmcia Flash Card Error Messages

    See the UNIX man pages about logger(1), syslog(3), syslog.conf(5), and syslogd(8) for details of the syslog daemon. The Syslog function requires UDP port 514. The Stinger unit can report the following session data about various errors logged via Syslog: Data...

  • Page 359: Load Command Messages

    Table B-2 lists the error messages that might appear when you are using the load command to upload an image to a PCMCIA flash card on a Stinger unit. Table B-2.

  • Page 360: 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...
  • Page 361 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 363: Index

    8-7 logging in as different user 1-2 status, changing 8-8 session statistics A-20 analog loopback 12-25 SNMPv3 7-6 application-specific integrated circuit (ASIC) SNMPv3 features 7-6 integrity tests 4-1 SNMPv3 license 7-6 two levels, enabling 1-7 Stinger® Administration Guide Index-1...
  • Page 364 2-4 CDR reports 3-10 revision A-17 centralized integrity testing 4-4 save 6-1 chassis screen 1-34 slots, explained 2-1 show 2-11 Stinger MRT 2-1 sleep 6-15 clock-source command 1-27 7-22 slot 2-17 traceroute 9-6 commands 12-26 update A-17 acct-failsafe A-18...
  • Page 365 1-4 required status, displaying 2-3 interface, verifying port status 1-4 slot numbering, described 2-2 port, verifying status 1-4 Stinger MRT, numbering for 2-2 statistics, displaying 9-12 system integrity, checking 4-1 ether-stats command, using 9-12 controller-redundancy command A-23...
  • Page 366 9-13 ip-route profile 9-5 multicast clients, displaying information about isolate command 12-32 9-13 ignore-lineup, displaying settings for 5-19 connectivity, testing 5-10 groups, displaying 5-10 ima-tpp command 5-10 keys, authentication and privacy, generating 7-9 Index-4 Stinger® Administration Guide...
  • Page 367 ADSL, displaying interface 5-8 OC3-ATM 12-16 ASIC integrity testing 4-2 LPMs defined 2-2 displaying status for 2-4 displaying status of 2-3 Stinger MRT, for 2-1 displaying types installed 2-4 LSAs operational state of 2-4 displaying 10-2 physical address, displaying 2-3 types 10-6...
  • Page 368 2-17 required state 2-4 required status, displaying 2-3 resetting using the slot command 2-14 entries, displaying 12-17 Stinger MRT, for 2-1 F4 and F5 test, overview 12-2 F4 continuity tests 12-11 temporarily stopping operations of 2-14 F4 loopback tests 12-14...
  • Page 369 SNMPV3-USM-User 7-7 logging in as Admin 1-2 thresh-profile 8-24 typical configurations 1-18 timedate 1-26 timing the saving of 6-15 physical addresses, described for Stinger units trap 8-13 user predefined 1-5 ping command, using 9-1 user, configuring 1-5 PNNI prompt, setting 1-24...
  • Page 370 8-4 slot-info profile, displaying module information with 2-12 resetting modules 2-14 slots unit 1-39 explained for Stinger MRT 2-1 numbering 2-1 restoring configurations 6-6 operational state of 2-4 revision command A-17 slot-state profile 2-14 routes adding static to routing table 9-5...
  • Page 371 7-7 auxilliary-syslog profiles, configuring 3-11 soft IP address, requirement 7-2 configuring 3-10 software configuring Stinger to interact with 3-10 LIMs, updating for 6-16 daemon, configuring 3-12 loading for new modules 6-16 enabling 3-2 loading for specific module 6-15...
  • Page 372 5-7 packet statistics 11-6 displaying status of 2-3 view-based access control (VACM), configuring interfaces, monitoring 5-3 7-13 numbering for Stinger MRT 2-1 required status, displaying 2-3 virtual channel connection. See VCC slot numbering 2-2 virtual link information, displaying 11-7 Index-10...
  • Page 373 1-32 packets during connection setup, displaying 9-16 packets, displaying 9-15 wandisplay command using 9-15 wandsess command 9-16 wanopening command, using 9-16 warning messages definition of B-4 format of B-1 who command 1-38 whoami command 1-25 Stinger® Administration Guide Index-11...

Table of Contents