This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in
any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts, or
licensing, without the express written consent of Lucent Technologies. For permission to reproduce or distribute, please email your request to
techcomm@lucent.com.
Notice
Every effort was made to ensure that the information in this document was complete and accurate at the time of printing, but information is
subject to change.
For latest information, refer to online product documentation at www.lucent.com/support.
This product may utilize zlib for the execution of certain compression functions.
(C) 1995-2002 Jean-loup Gailly and Mark Adler. Provided "AS IS" without warranty of any kind.
European Community (EC) RTTE compliance
Hereby, Lucent Technologies, declares that the equipment documented in this publication is in compliance with the essential requirements and other relevant provisions of the Radio and Telecommunications Technical Equipment (RTTE) Directive 1999/5/EC.
To view the official Declaration of Conformity certificate for this equipment, according to EN 45014, access the Lucent INS online documentation
library at http://www.lucentdocs.com/ins.
Safety, compliance, and warranty Information
Before handling any Lucent Access Networks hardware product, read the Edge Access and Broadband Access Safety and Compliance Guide included
in your product package. See that guide also to determine how products comply with the electromagnetic interference (EMI) and network
compatibility requirements of your country. See the warranty card included in your product package for the limited warranty that Lucent
Technologies provides for its products.
Security statement
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.
Ordering Information
You can order the most up-to-date product information and computer-based training online at http://www.lucentdocs.com/bookstore.
How to comment
To comment on this information product, go to the Online Comment Form (http://www.lucent-info.com/comments/enus/) or email your
comments to the Comments Hotline (comments@lucent.com).
Lucent Technologies
Customer Service
Product and service information, and software upgrades, are available 24 hours a day.
Technical assistance options accommodate varying levels of urgency.
Finding information and software
To obtain software upgrades, release notes, and addenda for this product, log in to
Lucent OnLine Customer Support at http://www.lucent.com/support.
Lucent OnLine Customer Support also provides technical information, product
information, and descriptions of available services. The center is open 24 hours a day,
seven days a week. Log in and select a service.
Obtaining technical assistance
Lucent OnLine Customer Support at http://www.lucent.com/support provides easy
access to technical support. You can obtain technical assistance through email or the
Internet, or by telephone. If you need assistance, make sure that you have the
following information available:
Customer Service
Active service or maintenance contract number, entitlement ID, or site ID
Product name, model, and serial number
Software version or release number
Software and hardware options
If supplied by your carrier, service profile identifiers (SPIDs) associated with your
line
Whether you are routing or bridging with your Lucent product
Type of computer you are using
Description of the problem
Obtaining assistance through email or the Internet
If your services agreement allows, you can communicate directly with a technical
engineer through Email Technical Support or a Live Chat. Select one of these sites
when you log in to http://www.lucent.com/support.
Calling the technical assistance center (TAC)
If you cannot find an answer through the tools and information of
Customer Support
OnLine Customer Support
for a list of telephone numbers inside and outside the United States.
or if you have a very urgent need, contact TAC. Access
at
http://www.lucent.com/support
Lucent OnLine
and click
Contact Us
Lucent
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 iii
Contents
Customer Service ........................................................................................................iii
About This Guide ..............................................................................xix
What is in this guide .................................................................................................xix
What you should know.............................................................................................xix
Index .......................................................................................... Index-1
xivStinger® Administration Guide
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
Stinger® Administration Guide xv
Tables
Table 1-1Permissions and associated commands ........................................... 1-18
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.
What is in this guide
Each chapter in this guide focuses on a particular aspect of Stinger unit
administration and operations. The chapters describe tools for system management,
network management, and SNMP agent management.
To perform many of the tasks in this manual, you must have administrative
permission on the Stinger unit. For instructions on logging into the Stinger unit with
administrative permissions, see “Logging into a Stinger unit” on page 1-2.
Note This manual describes the set of features for Stinger units running software
version TAOS 9.7.0. Some features might not be available with earlier versions or
specialty loads of the software.
Warning Before installing or operating your Stinger unit, be sure to read the safety
instructions in the Edge Access and Broadband Access Safety and Compliance Guide. For
information specific to your unit, see the “Safety-Related Electrical, Physical, and
Environmental Information” appendix in your unit’s Getting Started Guides.
What you should know
This guide attempts to provide enough information to enable an administrator who is
not an expert in a particular network technology to operate and troubleshoot a
Stinger unit. However, this guide does not provide a complete explanation of any
network management topic. For best results, when working with the following
capabilities on a Stinger unit, make sure that you have some applicable general
knowledge:
Line configuration and testing
Connection negotiation and authentication
Connection cost management and accounting
IP routing
Network security
Stinger® Administration Guide xix
About This Guide
Documentation conventions
Documentation conventions
Following are all the special characters and typographical conventions used in this
manual:
ConventionMeaning
Monospace textRepresents text that appears on your computer’s screen, or that
could appear on your computer’s screen.
Boldface
monospace text
ItalicsRepresent variable information. Do not enter the words
[ ]Square brackets indicate an optional argument you might add
|Separates command choices that are mutually exclusive.
>Points to the next level in the path to a parameter or menu
Key1+Key2Represents a combination keystroke. To enter a combination
Press EnterMeans press the Enter or Return key or its equivalent on your
Represents characters that you enter exactly as shown (unless
the characters are also in italics—see Italics, below). If you
could enter the characters but are not specifically instructed to,
they do not appear in boldface.
themselves in the command. Enter the information they
represent. In ordinary text, italics are used for titles of
publications, for some terms that would otherwise be in
quotation marks, and to show emphasis.
to a command. To include such an argument, type only the
information inside the brackets. Do not type the brackets unless
they appear in boldface.
item. The item that follows the angle bracket is one of the
options that appear when you select the item that precedes the
angle bracket.
keystroke, press the first key and hold it down while you press
one or more other keys. Release all the keys at the same time.
(For example, Ctrl+H means hold down the Ctrl key and press
the H key.)
computer.
Introduces important additional information.
Note
Warns that a failure to follow the recommended procedure
Caution
Warning
Warning
xxStinger® Administration Guide
could result in loss of data or damage to equipment.
Warns that a failure to take appropriate safety precautions
could result in physical injury.
Warns of danger of electric shock.
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.
–TAOS Command-Line Interface Guide. Introduces the TAOS command-line
environment and shows you how to use the command-line interface
effectively. This guide describes keyboard shortcuts and introduces
commands, security levels, profile structure, and parameter types.
Installation and basic configuration:
–Getting Started Guide for your Stinger platform. Shows how to install your
Stinger chassis and hardware. This guide also shows you how to use the
command-line interface to configure and verify IP access and basic access
security on the unit, and how to configure Stinger control module
redundancy on units that support it.
About This Guide
Stinger documentation set
–Module guides. For each Stinger line interface module (LIM), trunk module,
or other type of module, an individual guide describes the module's features
and provides instructions for configuring the module and verifying its status.
Configuration:
–Stinger Compact Remote Installation and Configuration Guide. Provides an
overview of the Stinger Compact Remote and provides instructions for the
installation and replacement of its components. This guide also describes how
to configure and manage the Compact Remote as a hosted unit
–Stinger ATM Configuration Guide. Describes how to integrate the Stinger into
the ATM and Digital Subscriber Line (DSL) access infrastructure. The guide
explains how to configure PVCs, and shows how to use standard ATM
features such as quality of service (QoS), connection admission control
(CAC), and subtending.
–Stinger IP2000 Configuration Guide. For Stinger systems with the IP2000
control module, this guide describes how to integrate the system into the IP
infrastructure. Topics include IP-routed switch-through ATM PVCs and RFC
1483 PVCs that terminate on the IP2000, IEEE 802.1Q VLAN, and
forwarding multicast video transmissions on DSL interfaces.
–Stinger Private Network-to-Network Interface (PNNI) Supplement. For the optional
PNNI software, this guide provides quick-start instructions for configuring
PNNI and soft PVCs (SPVCs), and describes the related profiles and
commands.
–Stinger SNMP Management of the ATM Stack Supplement. Describes SNMP
management of ATM ports, interfaces, and connections on a Stinger unit to
provide guidelines for configuring and managing ATM circuits through any
SNMP management utility.
–Stinger T1000 Module Routing and Tunneling Supplement. For the optional T1000
module, this guide describes how to configure the Layer 3 routing and virtual
private network (VPN) capabilities.
Stinger® Administration Guide xxi
About This Guide
Stinger documentation set
RADIUS: TAOS RADIUS Guide and Reference. Describes how to set up a unit to use
the Remote Authentication Dial-In User Service (RADIUS) server and contains a
complete reference to RADIUS attributes.
Administration and troubleshooting: Stinger Administration Guide (this guide).
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.
Reference:
–Stinger Reference. An alphabetic reference to Stinger profiles, parameters, and
–TAOS Glossary. Defines terms used in documentation for Stinger units.
This chapter describes the system administration tasks that you might perform on the
Stinger unit, such as enabling basic security, configuring and managing
administrative access to a system, configuring and displaying basic system settings,
and managing user connections.
1
To use this chapter, you must have performed the tasks described in the Getting
Started Guide for your unit and the Stinger ATM Configuration Guide. You can obtain
Stinger manuals at http://www.lucent.com/support.
Note On a Stinger MRT device, control module and line interface module (LIM)
functions are incorporated into the unit’s chassis. The terms control module and LIM in
this guide refer to the control module and the LIM port functions on a Stinger MRT
and not to physical modules.
About standalone and hosted Stinger systems
In this document, a Stinger FS, Stinger FS+, Stinger LS, Stinger RT, Stinger MS+ or
Stinger MRT unit that does not provide host functions to other Stinger units is
referred to as a standalone unit.
You can provision and manage up to five cascaded Stinger MRT units as a single
hosted system, with a single management interface. Only one of the Stinger MRT
units supports ATM trunk interfaces, and that unit must be the controlling unit (the
host) for the hosted system. The other cascaded units (remote shelves) are included in
the hosted system topology by enabling the remote shelf through a profile for that
shelf ID. For more information about the hosted operations of Stinger MRT units, see
the Stinger MRT Getting Started Guide for your unit.
Stinger® Administration Guide 1-1
Administering a Stinger System
Logging into a Stinger unit
Stinger FS+, Stinger LS, and Stinger RT units with revision 2.0, revision 2.1, and
IP2000 control modules can also support host functions to Stinger Compact Remote
units. The Stinger Compact Remote unit is a small temperature-hardened unit that
extends the reach of host Stinger units located in the central office. For more
information about the hosted operations of a Compact Remote unit, see the Stinger Compact Remote Getting Started Guide.
On hosted systems, provisioning and management of the remote shelves is performed
on the host. The look and feel of the host management interface is very similar to
that of a standalone system, except that some commands require that you specify a
shelf ID in the physical address of a slot or port, and the shelf ID is also displayed in
the output of commands that previously showed only slot and port information. For
more information about shelf, slot, and port addressing on Stinger systems, see
“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.
Note On units with redundant control modules, only one control module is active at
a time. The secondary control module becomes the primary (active) control module if
the primary control module can no longer support the Stinger unit. The unit transfers
any configuration changes that you make on the primary control module to the
secondary control module, except for changes to IP addresses. Each control module
must have a unique IP address.
To administer the system, you can log in from a PC connected to the control module’s
serial port, or from a workstation that has Telnet access to the system. When you log
in, you are prompted for a username:
User:
To log in with administrative privileges, enter the default password (Ascend) assigned
to the Stinger admin login at the factory:
User: admin
Password: Ascend
The name specified in the name parameter of the admin user profile appears as your
system prompt. For example:
admin>
If you are already connected to the Stinger unit as a different user, use the auth
command to log in as the administrator:
admin> auth user
Password:
For additional information about user profiles, see “Managing administrative access
to the unit” on page 1-5.
Enabling basic security measures
The Stinger unit is shipped with certain default parameters set to allow easy access for
the initial configuration. After you have initially logged in as administrator, ensure
that the following three basic security tasks have been completed:
1-2Stinger® Administration Guide
Change the default admin password.
Secure the serial port on both control modules.
Specify one of the Ethernet ports as a management-only port.
You can also manage administrative access to the Stinger unit by specifying the types
of tasks administrative users can perform on the 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. Be sure to write down the password you assign and store it in
a safe place.
To change the password for the admin login, proceed as follows:
admin> read user admin
USER/admin read
admin> set password = top-secret
admin> write
USER/admin written
Administering a Stinger System
Enabling basic security measures
All subsequent administrator logins are required to supply the new password. (For
more information about configuring user profiles, see “Managing administrative
access to the unit” on page 1-5.)
Securing the serial port of each control module
The default settings for the control module allow anyone connecting to the serial port
to access the system as the admin user, without logging in or being authenticated.
Therefore, you must configure each control module to request a username and
password and to automatically log the user out when the terminal session is
terminated.
To secure the serial port on a single or primary control module, proceed as follows:
1Read the serial profile of the primary (or single) control module:
admin> read serial {1 8 2}
The serial profile index refers to a physical port on the control module. The
serial port is always designated as the second physical port of the control module.
2Set the user-profile parameter to null:
admin> set user-profile =
3Set the auto-logout parameter to yes:
admin> set auto-logout = yes
With this setting, the system automatically logs off the current user profile if the
Data Terminal Ready (DTR) signal is lost on the serial port.
4Write the profile:
admin> write
Stinger® Administration Guide 1-3
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.
The following sample commands show how to secure the serial port on a secondary
control module:
admin> read serial {1 9 2}
admin> set user-profile =
admin> set auto-logout = yes
admin> write
Now users connecting to a control module must supply a valid username and
password for access to the Stinger unit.
Specifying a management-only Ethernet interface
You can specify that a control module’s Ethernet interface is for management only.
Following is the relevant parameter, which is shown with its default setting:
Setting the management-only-interface parameter to yes means that incoming traffic
on the interface terminates in the system itself and is not forwarded on any other
interface. In addition, only traffic generated by the system is forwarded onto the
management-only interface. Traffic generated externally is dropped by the interface.
To configure a management interface for each of the control modules, proceed as in
the following example:
You can view the Ethernet’s port status using the ifmgr command. For the system to
respond to this command, your user profile must be enabled with debug privileges.
For information on enabling debug privileges see “Enabling debug permissions” on
page A-1.
To verify that an Ethernet interface has been set for management only, display the
output of the ifmgr -d command, as shown in the following example:
admin> ifmgr -d
bif slot sif u m p ifname host-name remote-addr local-addr
The u column displays an asterisk (*) to indicate that the interface is operational or a
hyphen (-) to indicate that it is disabled.
Securing Telnet access
If the telnet-password parameter in the ip-global profile (without specifying a
user-profile name), you can configure a Stinger system to support mild
authentication for telnet access. When a user attempts to access the system via telnet,
the user must provide a password when prompted. After telnet authentication, the
user goes through the terminal session authentication similar to authentication for
console access.
Administering a Stinger System
Managing administrative access to the unit
User authentication can be internal or external based on system configuration. If the
user-profile parameter in the ip-global profile is set with the name of a user
profile, then the terminal session's user authentication is bypassed. To ensure that the
user is authenticated for telnet access, the user-profile parameter should not be set
to any user profile. See also, “Creating Telnet access control lists” on page 1-15 for
more information about managing Telnet access to the system.
Managing administrative access to the unit
You create and define administrative access to the Stinger unit using user profiles. Do
not confuse them with connection profiles. You configure user profiles to provide
access to the 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.
You can create any number of user profiles and fine-tune the privileges they allow. In
addition to authentication and permission information, user profiles also contain
parameters that affect how the user’s environment appears at login.
A Stinger unit is shipped with the predefined user profiles admin and default. An adminuser profile provides full read-write permissions, while the defaultuser profile
authorizes minimal use of commands.
Many sites choose to create some administrative accounts with read-only
permissions, to allow certain users to check status windows, read log buffers, and
enter diagnostic commands. You need at least one administrative account with readwrite permissions, but you might choose to create several read-only accounts.
Stinger® Administration Guide 1-5
Administering a Stinger System
Managing administrative access to the unit
For information about managing administrative sessions, see “Managing
administrative connections” on page 1-35.
Logging into the Stinger unit
To log into the Stinger unit for administrative tasks, use a profile that has write
permissions, as in the following example:
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:
You use the new user command to create a new administrative profile. You must then
activate and authenticate the new profile.
To creat e a new user profile based on the user profile admin, append admin to the new user command. The following example shows how to create a new user profile
named test, with full administrative privileges:
admin> new user admin
USER/admin read
admin> set name = test
admin> set password = test-pw
admin> write
USER/admin written
To create a new user profile based on the user profile default, use the new user
command with no additional arguments. The following example shows how to create
a new user profile named test2, with default administrative privileges:
admin> new user
USER/default read
admin> set name = test2
admin> set password = my-password
admin> write
USER/test2 written
1-6Stinger® Administration Guide
To activate a user profile, proceed as follows:
admin> read user test
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
You can configure the system to require a second level of authentication for the
following types of access to a Stinger unit or for any combination of the following:
Telnet access using system IP address
system console access
Administering a Stinger System
Managing administrative access to the unit
modem access
opening a session from a remote shelf to a host Stinger unit
By default, the system uses only single-level authentication.
If two-level authentication is enabled, at login, the system prompts the user to log in
twice, each time with a different username and password.
Note After an NVRAM operation, the system defaults to a single level of
authentication.
To enable two-level authentication, you must perform the following tasks, in the
following recommended order:
1Create a second-level user profile and link it to a first level user profile.
2Specify the type of access for which two-level authentication is required,
systemwide.
Note Before enabling two-level authentication for a system, make sure that you
have configured first-level and second-level user profiles for your system. If you
configure the system to require two-level authentication without defining first-level
and second-level user profiles, you might be unable to log into the system.
Settings in the user profile and comparable RADIUS attributes
To configure second-level authentication for a system, configure first and second
level user profiles that define the user name and password for each login level. Then,
specify a first-level profile for the second-level user profile.
You use the following parameters in the user profile to designate the login level for a
user profile and to associate a first-level user profile with a second-level user profile.
The comparable RADIUS attributes are also shown below.
Stinger® Administration Guide 1-7
Administering a Stinger System
Managing administrative access to the unit
Command-line
interface
parameter
RADIUS attributeSpecifies
first-level-userAscend-First-
Level-User
login-level
Ascend-User-LoginLevel
A user cannot use a first-level user profile name and password to login for the second
level of authentication or use a second-level user profile name and password to login
at the first level of authentication.
If you are configuring the system for RADIUS support, keep the following in mind:
If the rad-serv-enable and rad-auth-client parameters are enabled in the
external-auth
by selecting the appropriate setting for the cli-user-auth parameter in the
external-auth profile. If the system is set for single-level authentication, the
system uses the RADIUS server for single level authentication. If the system is
configured for two-level authentication, RADIUS authentication also requires
two levels of authentication.
For all telnet user accounts, first and second level, the attribute Ascend-TelnetProfile 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.
The attributes Ascend-User-Login-Level and Ascend-First-Level-User must be
set as part of the check list items in the telnet user account.
Name of a first-level user profile. The default setting is
null. If possible, do not assign a first-level user profile
to more than one second-level user profile.
Login level for this user profile. Specify one of the
following values:
first-level (the default)—This user profile is to
be used for first level authentication.
second-level—This user profile is to be used for
second level authentication. If the login-level
parameter is set to second-level, you must
specify the name of a valid first-level user profile
for the first-level-user parameter.
profile, external authentication is supported by a RADIUS server
1-8Stinger® Administration Guide
Loading...
+ 344 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.