Nortel Networks 5399, 8000 User Manual

Version 8.0

Part No. 300861-C Rev. 00
December 1999

4401 Great America Parkway
Santa Clara, CA 95054

Nortel Networks 5399 and
8000 Access Switch SNMP
MIB Reference

Copyright © 1999 Nortel Networks

All rights reserved. Printed inthe USA. December 1999.
The information in this document is subject to change without notice. The statements,configurations, technical data,

and recommendations in this document are believedto be accurate and reliable, but are presented without express or
implied warranty.Usersmust take full responsibility for theirapplications of any products specified in this document.
The information in this document is proprietaryto Nortel Networks NA Inc.

The software described in this documentis furnished under a license agreement and may only be used in accordance
with the terms of that license. A summary of the Software License is included in this document.

Trademarks

NORTEL NETWORKS i s a trademark of Nortel Networks.
Bay Ne tworks, ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FRE, LN, Optivity,Optivity Policy Services, and PPX

are registered trademarks and Advanced Remote Node, ANH, ARN, ASN, BayRS, BaySecure, BayStack, BayStream,
BCC, BCNX, BLNX, Centillion, EtherSpeed, FN, IP AutoLearn,Passport, SN, SPEX, Switch Node, System 5000,
and TokenSpeed are trademarksof Nortel Networks.

Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation.
All other trademarks and registered trademarks are the property of their respective owners.

Restricted Rights Legend

Use, duplication,or disclosure by the United States Government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS252.227-7013.

Notwithstanding any other l icense agreement that may pertain to, or accompany the delivery of, this computer
software, the rights of the United States Government regarding its use, reproduction,and disclosureare as set forth in
the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.

In the interest of improving internaldesign,operational function, and/or reliability, Nortel Networks NA Inc. reserves
the right to make changes to the productsdescribed in this documentwithout notice.

Nortel Networks NA Inc. does not assume any liability that may occur due to the use or application of the product(s)
or circuit layout(s) described herein.

Portionsof the code in this software product may be Copyright © 1988, Regents of the University of California. All
rights reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the
above copyrightnotice and this paragraph are duplicated in all such forms and that any documentation, advertising
materials, and other materialsrelated to such distribution and use acknowledge that such portionsof the softwarewere
developed by the University of California, Berkeley.The name of the Universitymay not be used to endorse or
promote products derived from such portions of the software without specific prior written permission.

SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” A ND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

In addition, the program and information contained herein are licensedonly pursuant to a license agreement that
containsrestrictions on use and disclosure (that may incorporate by referencecertain limitations and notices imposed
by third parties).

Nortel Networks NA Inc. S of tware License Agreement

NOTICE: Please carefullyread this license agreementbefore copying or using the accompanyingsoftware or
installing the hardware unit with pre-enabled software (each of which is referredto as “Software” in this Agreement).
BY COPYING OR USING THE SOFTWARE, YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF
THIS LICENSE AGREEMENT. THE TERMS EXPRESSED IN T HI S AGREEMENT ARE THE ONLY TERMS
UNDER WHICH NORTEL NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept

ii 300861-C Rev. 00

these terms and conditions, return the product,unused and in the original shipping container, within 30 days of
purchase to obtain a credit for the full purchase price.

1. License Grant. Nortel Networks NA Inc. (“Nortel Networks”) grants the end user of the Software (“Licensee”) a
personal, nonexclusive, nontransferable license:a) to use the Software eitheron a single computer or,if applicable, on
a single authorized device identified by host ID, for which it was originally acquired; b) to copy the Software solely
for backup purposes in support of authorized use of the Software; and c) to use and copy the associated user manual
solelyin support of authorizeduseof the Softwareby Licensee.This licenseapplies to the Softwareonlyanddoes not
extend to Nortel Networks Agent software or other Nortel Networks software products. Nortel Networks Agent
software or other Nortel Networkssoftware products are licensed for use under the terms of the applicable Nortel
NetworksNAInc. SoftwareLicense Agreement that accompaniessuchsoftware and upon payment by the end user of
the applicable licensefees for such software.

2. Restrictions on use; reservation of rights. The Software and user manuals are protected under copyright laws.
Nortel Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including
any revisionsmade by Nortel Networks or its licensors. The copyright notice must be reproduced and included with
any copy of any portion of the Software or user manuals.Licensee may not modify,translate, decompile, disassemble,
use for any competitive analysis, reverse engineer, distribute, or createderivative works from the Software or user
manuals or any copy, in whole or in part. Except as expressly providedin this Agreement, Licensee may not copy or
transfer the Software or user manuals,in whole or in part. The Software and user manuals embody NortelNetworks’
and its licensors’ confidential and proprietary intellectualproperty.Licensee shall not sublicense, assign, or otherwise
disclose to any third party the Software, or any information about the operation, design, performance, or
implementation of the Software and user manuals that is confidential to Nortel Networksand its licensors; however,
Licenseemay grant permission to its consultants, subcontractors, and agentsto use the Software at Licensee’s facility,
provided theyhave agreed to use the Software only in accordancewith the terms of this license.

3. Limited warranty. Nortel Networks warrants each item of Software, as delivered by Nortel Networks and properly
installed and operated on Nortel Networkshardwareor other equipment it is originally licensedfor, to function
substantially as described in its accompanying user manual during its warranty period, which begins on the date
Software is firstshippedto Licensee. If any itemof Softwarefailstoso functionduringitswarranty period, as the sole
remedyNortelNetworks will at its discretionprovide a suitablefix, patch, or workaround for the problemthat may be
included in a future Softwarerelease. Nortel Networks further warrants to Licensee that the media on which the
Software is providedwill be free from defectsin materialsand workmanship under normal use for a period of 90 days
from the date Softwareis first shipped to Licensee. Nortel Networks will replace defective media at no chargeif it is
returned to Nortel Networks during the warranty period along with proof of the date of shipment. This warranty does
not apply if the media has been damaged as a resultof accident, misuse, or abuse.The Licensee assumes all
responsibility for selection of the Software to achieve Licensee’s intended results and for the installation,use, and
resultsobtained from the Software. Nortel Networks does not warrant a) that the functions contained in the software
will meet the Licensee’s requirements,b) that the Software will operate in the hardware or software combinationsthat
the Licensee may select,c) that the operation of the Software will be uninterrupted or error free, or d) that all defects
in the operationof the Softwarewill be corrected. NortelNetworksis not obligatedto remedyany Software defect that
cannot be reproduced with the latest Software release. These warranties do not apply to the Software if it has been ( i)
altered, exceptby Nortel Networks or in accordance with its instructions; (ii) used in conjunction with another
vendor’s product, resulting in the defect;or (iii) damagedby improper environment, abuse, misuse, accident, or
negligence. THE FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE
IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY
WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is r esponsible
for the security of its own data and information and for maintaining adequate procedures apart from the Software to
reconstruct lost or altered files, data, or programs.

4. Limitation of liability. IN NO EVENT WILL N ORTEL NETWORKS OR ITS LICENSORS BE LIABLE FOR
ANY COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT,INCIDENTAL, OR CONSEQUENTIAL
DAMAGES; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR
PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN
IF NORTEL NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT

300861-C Rev.00 iii

SHALL THE LIABILITY OF NORTEL NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT
EXCEED THE PRICE PAID TO NORTEL NETWORKS FOR THE SOFTWARE LICENSE.

5. Government Licensees. This provision applies to all Software and documentationacquired directly or indirectly
by or on behalf of the United States Government.The Softwareand documentation are commercial products,licensed
on the open market at market prices, and were developed entirely at private expense and without the use of any U.S.
Government funds. The license to the U.S. Government is granted only with restricted rights, and use, duplication,or
disclosure by the U.S. Governmentis subject to the restrictionsset forth in subparagraph(c)(1)of the Commercial
Computer Software––Restricted Rights clause of FAR 52.227-19 and the limitations set out in this licensefor civilian
agencies, and subparagraph(c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS

252.227-7013, for agencies of the Departmentof Defense or their successors, whichever is applicable.

6. Use of Software in the European Community.This provision applies to all Softwareacquired for use within the
European Community. If Licensee uses the Software within a country in the European Community, the Software
Directive enacted by the Council of European Communities Directive dated 14 May, 1991, will apply to the
examination of the Software to facilitate interoperability. Licensee agrees to notify Nortel Networksof any such
intended examination of the Software and may procure support and assistance from Nortel Networks.

7. Termand termination. This license is effective until terminated; however, all of the restrictions with respect to
NortelNetworks’ copyrightin the Softwareand user manuals will cease being effective at the date of expiration of the
Nortel Networks copyright; those restrictions relating to use and disclosureof Nortel Networks’ confidential
information shall continue in effect. Licensee may terminate this license at any time. The license will automatically
terminate if Licensee fails to complywith any of the terms and conditions of the license. Upon terminationfor any
reason, Licensee will immediately destroyor return to Nortel Networksthe Software, user manuals, and all copies.
Nortel Networks is not liable to Licenseefor damages in any form solely by reason of the terminationof this license.

8. Export and Re-export. Licensee agrees not to export, directly or indirectly, the Software or related technical data
or information without first obtaininganyrequired export licensesor other governmental approvals.Without limiting
the foregoing,Licensee, on behalf of itself and its subsidiaries and affiliates,agreesthat it will not, without first
obtainingall export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or divert
any such Software or technicaldata, or any direct product thereof, to any country to which such exports or re-exports
are restricted or embargoed under United States export control laws and regulations, or to any nationalor resident of
such restrictedor embargoed countries; or (ii) provide the Software or related technical data or information to any
militaryend user or for any military end use, including the design, development, or productionof any chemical,
nuclear, or biologicalweapons.

9. General. If any provision of this Agreement is held to be invalid or unenforceable by a court of competent
jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement
will be governed by the laws of the state of California.

Should you have any questions concerning this Agreement, contact Nortel Networks,4401 Great America Parkway,
P.O. Box 58185, Santa Clara, California 95054-8185.

LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND
AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS
AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN NORTEL NETWORKS AND
LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND
COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS
AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST NORTEL
NETWORKS UNLESS NORTEL NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN
EXPRESS WAIVEROF THE TERMS OF THIS AGREEMENT.

iv 300861-C Rev. 00

Contents

Preface

Before You Begin .............................................................................................................. ix

Text Conventions ...............................................................................................................x

Acronyms ..........................................................................................................................xii

Hard-Copy Tec hnical Manuals . ........................................................................................ x ii i

How to Get Help ..............................................................................................................xiii

Chapter 1
Simple Network Management Protocol (SNMP)

SNMP Overview .............................................................................................................1-1

SNMP Commands .......................................................................................................... 1-2

Using SNMP set to Send Commands to the RAC ...................................................1-3

Internet Group Management Protocol (IGMP) .........................................................1-3

Chapter 2
Configuring the RAC for SNMP

Configuring the SNMP Agent . . .......................................................................................2-1

Defining the Community String ................................................................................ 2-3

Defining Trap Hosts and Traps .................................................................................2-4

Defining the Contact String ......................................................................................2-5

Defining the Location String ..................................................................................... 2-5

Defining the disabled_modules Parameter ..............................................................2-5

Defining the allow_snmp_sets Parameter ................................................................2-6

Configuring BootP Relay ..........................................................................................2-6

Chapter 3
Private MIBs and Standard MIB Support

StandardRFC MIBs .......................................................................................................3-1

MIB Object Hierarchy ......................................................................................................3-2

Understanding MIB Objec ts ............................................................................................3-3

300861-C Rev.00 v

Restrictions on Standard MIBs .......................................................................................3-3

RFC 1213 MIB-II Restrictions ..................................................................................3-3

RFC 1243 AppleTalk MIB Restrictions .....................................................................3-4

RFC 1643 Ethernet MIB Res trictions .......................................................................3-5

RFC 1724 RIP V2 MIB Restri ctions .........................................................................3-6

RFC 1406 DS1 MIB Restrictions .............................................................................3-6

Private Enterprise MIBs .................................................................................................. 3-7

Location of Private MIB Files ................................................................................... 3-7

Private MIB Filenames .............................................................................................3-7

Chapter 4
Call Management

Active Call Statistics .......................................................................................................4-1

Active Modem Calls .................................................................................................4-2

Active MP Calls ........................................................................................................4-2

Port Action Table ......................................................................................................4-2

Call History Statistics ......................................................................................................4-3

Modem Call History Statistics .................................................................................. 4-3

MP Call History Statistics .........................................................................................4-4

Internet Group Management Protocol (IGMP) ................................................................4-4

Modem MIBs ..................................................................................................................4-4

Modem Identification ................................................................................................4-4

Modem Control .........................................................................................................4-4

Modem Statistics ......................................................................................................4-5

WANStatistics ................................................................................................................4-5

Chapter 5
Error Handling

Error Counters ................................................................................................................5-1

Thresholds ......................................................................................................................5-4

PPP Trace-to-Syslog ......................................................................................................5-5

Trap Configuration .......................................................................................................... 5-6

Proprietary Traps ......................................................................................................5-7

Chapter 6
Troubleshooting

Index

vi 300861-C Rev. 00

Tables

Table 1-1. Supported SNMP Commands .................................................................1-2

Table 2-1. Supported Standard SNMP Traps ...........................................................2-5

Table 3-1. Standard MIBs Supp orted by the RAC ....................................................3-2

Table 3-2. RFC 1213 MIB-II Objects .........................................................................3-4

Table 3-3. RFC 1243 AppleTalk ................................................................................ 3-5

Table 3-4. RFC 1643 Ethernet MIB Objects .............................................................3-6

Table 3-5. RFC 1724 RIP V2 MIB Objects ................................................................3-6

Table 3-6. RFC 1406 DS1 MIB Objects ....................................................................3-7

Table 3-7. Private MIB Filenames . ............................................................................3-8

Table 3-8. Prefixes for MIB Object Names Related to the RAC ................................3-9

Table 5-1. Current Error Counter MIBs .....................................................................5-2

Table 5-2. Interval Error Counter M IBs .....................................................................5-3

Table 5-3. Total Error Counter MIBs .........................................................................5-4

Table 5-4. Threshold MIBs ........................................................................................ 5-5

Table 5-5. Proprietary Traps .....................................................................................5-7

300861-C Rev.00 vii

If you are responsible for developing custom applications for configuring or
managing a Nortel Networks 5399 Access Switch or 8000 Access Switch
(formerly known as Model 5399 and Model 8000 Remote Access Concentrator
(RAC)) using SNMP, you need to read this guide.

Note: The Access S witch product na me appears only on the title page.

Whenever the term Remote Access C oncentrator (RAC) appears in this
document, it refers to the Nortel Networks 5399 or 8000 Access Switch.

Before You Begin

This guide is intended for network administrators and assumes that you have:

Preface

• Basic familiarity with network administration

• An understanding of the basic concepts of Integrated Services Digital
Network (ISDN) and C hannelized T1/E1.

300861-C Rev.00 ix

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

Text Conventions

This guide uses the following text c onventions:

angle brackets (< >) Indicate that you choose the text to enter based on the

description inside the brackets. Do not type the
brackets when entering the command.
Example: If the command syntax is:

ping <

ip_address

ping 192.32.10.12

>, you enter:

bold text

Indicates command names and options and text that
you need to enter.
Example: Enter show ip {al erts | routes}.
Example: Use the dinfo command.

braces ({}) Indicate required elements in syntax descriptions

where there is more than one option. You must choose
only one of the options. Do not type the braces when
entering the command.
Example: If the command syntax is:

show ip {alerts | routes}, you must enter either:
show ip alerts or show ip routes, but not both.

brackets ([ ]) Indicate optional elements in syntax descriptions. Do

not type the brackets when entering the command.
Example: If the command syntax is:

show ip interfaces [-alerts], you can enter either:
show ip interfaces or show ip interfaces -alerts.

x 300861-C Rev. 00

Preface

ellipsis points (...) Indicate that you re peat the last element of the

command as needed.
Example: If the command syntax is:

ethernet/2/1 [<
ethernet/2/1 and as many parameter-value pairs as

parameter><value

>] ..., you enter

needed.

italic text Indicates file a nd directory names, new terms, book

titles, and variables in command syntax descriptions.
Where a variable is two or more words, the words are
connected by an underscore.
Example: If the command syntax is:

show at <

valid_route

valid_route

>

is one variable and you substitute one value

for it.

screen text

Indicates system output, for example, prompts and
system messages.

Example: Set Trap Monitor Filters

separator ( > ) Shows menu paths.

Example: Protocols > IP identifies the IP optionon the
Protocols menu.

vertical line (

| ) Separates choices for command keywords and

arguments. Enter only one of the choices. Do not type
the vertical line when e ntering the command.
Example: If the command syntax is:

show ip {alerts | routes}, you enter either:
show ip alerts or show ip routes, but not both.

300861-C Rev.00 xi

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

Acronyms

This guide uses the following acronyms:

AUI attachment unit interface
BootP Bootstrap Protocol
BRI basic rate interface
CSMA/CD carrier sense multiple access/collision detection
DLCMI Data Link Control Management Interface
HDLC High-level Data Link Control
HTTP Hypertext Transfer Protocol
IGMP Internet Group Management Protocol
IP Internet P rotocol
ISDN Integrated Services Digital Network
ISO International Organization for Standardization
ITU-T International Telecommunication

Union-Telecommunication Standardization Sector

(formerly CCITT)
MAC media access control
MAU media access unit
MDI-X medium dependent interface crossover
NBMA nonbroadcast multi-access
OSPF Open Shortest Path First
PPP Point-to-Point Protocol
RAC Remote Access Concentrator
RADIUS Remote Authentication Dial-In User Service
SMDS Switched Multimegabit Data Service
SNMP Simple Network Management Protocol
STP shielded twisted pair
TPE twisted pair Ethernet
WAN Wide Area Network

xii 300861-C Rev. 00

Hard-Copy Technical Manuals

You can print selected technical manuals and release notes free, directly from the
Internet. Go to support.baynetworks.com/library/tpubs/. Find the product for
which you need documentation. Then locate the specific category and model or
versionfor your hardware or software product. Using Adobe Acrobat Reader,you
can open the manuals and release notes, search for the sections you need, and print
them on m ost standard printers. You can download Acrobat Reader free from the
Adobe Systems Web site, www.adobe.com.

You can purchase selected documentation sets, CDs, a nd technical publications
through the collateral catalog. The catalog is located on the World Wide We b at

support.baynetworks.com/catalog.html a nd is divided into sections arranged

alphabetically:

• The “CD ROMs” section lists available CDs.

• The “Guides/Books” section lists books on technical topics.

• The “Technical Manuals” section lists available printed documentation sets.

How to Get Help

Preface

If you purchased a service contract for your Nortel Networks product from a
distributor or authorized r eseller, contact the technical support staff for that
distributor or reseller for assistance.

If you purchased a Nortel Networks service program, contact one of the following
Nortel Networks Technical Solutions Centers:

Technical Solutions Center Telephone Number

Billerica, MA 800-2LANWAN (800-252-6926)
Santa Clara, CA 800-2LANWAN (800-252-6926)
Valbonne, France 33-4-92-96-69-68
Sydney, Australia 61-2-9927-8800
Tokyo, Japan 81-3-5402-7041

300861-C Rev.00 xiii

Simple Network Management Protocol (SNMP)

This chapter describes the Simple Network Management Protocol (SNMP) and
the SNMP a gent provided by the RAC. This chapter includes the following
sections:

• SNMP Protocol Overview

• SNMP Commands

SNMP Overview

SNMP provides an alternative means of managing the RAC. SNMP ope rates over
the UDP (Unreliable Datagram Protocol), which is part of the TCP/IP protocol
suite.

Chapter 1

• The Structure of M anagement Information (SMI), defined in RFC 1155, is a
framework that describes what kinds of information can be manipulated using
SNMP. Using SMI, objects are placed as nodes in an object tree. The object
tree groups logically related objects into subtrees. Ea ch of these subtrees is
called a MIB (Management Information Base).

• MIBs located on the SNMP Network Management S tation describe the
information that is relayed from the agents.

• The SNMP network management station or application can send queries to
the SNMP a gent located in each RAC.

• Each SNMP agent c ollects information about its RAC and provides that
information to the Network Management Station. The agent process acts as a
server in a typical client-server model.

300861-C Rev.00 1-1

SNMP Commands

The SNMP a gent software in the RAC supports the SNMP commands get,
get-next, set,andtrap a s defined in RFC 1157. Table 1-1 describes these

commands.

Table 1-1. Supported SNMP Commands

Action Description

get Retrieves the value of a specific object from one of the supported

get-next Traverses the MIB tree to retrieve the next object’s management

set Modifies the values of MIB objects. The RAC pri vate enterprise

trap Asynchronously reports significant events.

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

MIBs.

information.

MIB and several objects in the standard MIBs allow you to
configure the RAC from an SNMP management stationon the
network rather than using the na utility or CLI admin command.

When the allow_snmp_sets parameter is e nabled, the RAC accepts SNMP set
commands from IP host addresses and communities that have read-write access
permissions. W hen disabled, the RAC rejects all SNMP set commands; the RAC
SNMPagentreturns the error no such name for the first object in the set command
(for more details, see allow_snmp_sets in the Nortel Networks 5399 and 8000
Access Switch Software Reference).

SNMP version 1 is not a secure protocol. SNMP bypasses the RAC’s security
measures. If security is a concern, the administrator should consider taking the
following security measures:

• Definethe community strings for specificIP addresses with read-write access.

• Disable all other SNMP access by defining none or read-only access.

• Institute filters on any firewall router to block SNMP traffic from outside the
local network. This is good practice in all cases, not just concerning the RAC.

The specifics of using the SNMP commands depend on the management station
(see your SNMP management station documentation). The MIB definitions in the
files provided in the directory /annex_root/src/snmp must be c ompiled and
included in your m anagement station database before you can manage the RAC
using SNMP.

1-2 300861-C Rev. 00

Simple Network Management Protocol (SNMP)

Using SNMP set to Send Commands to the RAC

The private enterprise MIB objects allow you to change the configuration of the
RAC.

Note: For some objects, the configuration changes do not take effect until the

RAC is rebooted.

Using the SNMP set command, you can broadcast a message, reseta port or
subsystem, a nd reboot the RAC.

• To broadcast a message, use SNMP set to write the message to the MIB object
anxcBcastMsg and then set the broadcast type to the MIB object anxcBcast.

• To reset a R AC subsystem, use SNMP set to write the desired type (all,
macros, motd, nameserver, security) to the MIB object anxcReset.

• To reset the RAC, use SNMP set to write the desired value to the MIB object
anxcReset.

• To reset a single internal m odem, use SNMP set to write a value to
mdmCtlReset.

• To reboot the RAC, set the desired image name using the MIB object

anxcBootImage and set any boot warning m essage using the MIB object
anxcBootMsg. For a delayed boot, set the boot time using the MIB object
anxcBootTime. Then set the boot type using the MIB object anxcBoot.

Note: To change the RAC’s configuration using set, SNMP must be enabled

at boot time. M ake sure the argument snmp is not disabled in the
disabled_modules parameter. For more details, see disabled_modulesin the

Nortel Networks 5399 and 8000 Access Switch Software Reference).
You cannot c onfigure filters through SNMP.

Internet Group Management Protocol (IGMP)

There are two IGMP limitation configuration parameters available f or the
administrator. The use of the parameters allow an increase or a limit on the
number of pending IGMP events and multicast packets for total num ber of IGMP
events and packets proc essed by the system. Refer to the N ortel Networks 5399

and 8000 Access Switch SoftwareReference.

300861-C Rev.00 1-3

Chapter 2

Configuring the RAC for SNMP

Before an SNMP network management application can monitor or manage the
RAC, the RAC must be c onfigured for SNMP. This entails defining certain
configuration data, including the SNMP agent, the SNMP community string, and
related RAC parameters. This chapter describes how to c onfigure the RAC for
SNMP in the following sections:

• Configuring the S NM P Agent

• Defining the Community String

• Defining Trap Hosts and Traps

• Defining the Contact String

• Defining the Location String

• Defining the disabled_modules Parameter

• Defining the allow_snmp_sets Parameter

• Configuring BootP Relay

Configuring the SNMP Agent

Entries in the gateway section of the configuration file, which is downloaded
during RAC initialization, both enable the SNMP agent and define the ope rating
characteristics of the SNMP daemon that controls the SNMP agent.

The gateway section of the configuration file contains four optional keywords for
configuring the RAC SNMP agent:

• community

• traphost

• contact

• location

300861-C Rev.00 2-1

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

Details of these keywords, as well as the parameters you use with SNMP, are
described in the following sections.

A sample entry in the gateway section of the configuration file looks like this:

% gateway

annex 132.245.6.34
host 132.245.1.01 gateway 132.245.7 metric 1 hardwired
net 132.245.9.0 gateway 132.245.2.3 metric 1 hardwired
snmp contact john smith ext 370
snmp location computer room
end

%include snmp_inc_file

Note that the example above includes a file na med snmp_inc_file, and executes
the commands within that file. It is not necessary to use an include file in this
manner. You can simply list all your SNMP commands within the gateway
section of the configuration file.

It is often convenient to use an SNMP include file to define community names,
trap hosts and other SNMP characteristics of the R AC. A sample of what can be
included in an SNMP include file is shown below:

snmp traphost 123.245.1.2
snmp traphost 132.245.6.50:1049
snmp traphost 132.245.33.233:1048 mycommstring

In the first trap host entry,neither a port nor a community string is defined. In this
case, the port defaults to the well-known trap port 162, and the community string
defaults to public.

In the second trap host entry, the trap port is specified as 1049. The community
string is not specified, and a gain defaults to public.

In the last entry, the trap port is specified as 1048, and the community string is
specified as mycommstring.

2-2 300861-C Rev. 00

Defining the Community String

When an SNMP request is received by the agent in the RAC, the agent performs
three tests to authenticate the request. The tests are as follows:

• Each S NMP message contains a community string in its header. The receiving
SNMP agent tries to match the message’s string with an existing community
string list. If there is no match, the SNMP agent discards the message without
responding to the sender and increments the MIB-II object
snmpInBadCommunityNames.

• When the community string match is found, the sender’s IP address is
checked against the IP address for the matching community string(s).If there
is no m atch, the SNMP agent discards the message without responding to the
sender and the MIB-II objectsnmpInBadCommunityNames is incremented.

• If the community string and the IP address in the S NMP request matches one
of the configured community strings, the access mode is checked f or that
community. If the access is read-write, the SNMP r equest is processed. If the
access is read-only and the SNMP is a get or get next, the request is
processed. In all other cases (access is none or access is read-only a nd the
request is a set), an error noSuchName is returned to the sender and the
MIB-II object snmpBadCommunity is incremented.

Configuring the RAC for SNMP

The keyword community defines an SNMP community name from which the
RAC responds to requests. At system start-up, the SNMP agent requires at least
one community string to be defined in the configuration file. If the file does not
contain a community string, the RAC defaults to the community name public
(unless SNMP is disabled in the parameter disabled_modules), and allows read
and write access to all IP addresses.

The SNMP a gent authenticates an SNMP request through the use of a ccess
permissions. The configuration file format for SNMP defines the I P address and
access modes. Security is set by defining community strings that have none,
read-only,orread-write access to the MIB variables. The format is shown below:

snmp community

<string> <IP address> <access>

You can use a wild card (*) to define the IP address. Using a wild card allows
anybody with that community string to have access.

You can specify up to ten SNMP community names in the gateway section of the
configuration file, but each community requires a separate line. The R AC adds
these communities to the SNMP agent’s community table.

300861-C Rev.00 2-3

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

Defining Trap Hosts and Traps

The RAC employs two m ethods for defining the host addresses it uses when
generating S NM P trap messages.

• The first method loads the trap hosts (if any) from the configuration file into
the Trap Host Table. You can modify this table by adding or deleting trap
hosts in the configuration file.

• The second method defines up to ten static trap hosts using the
anxTrapHostTable objects in the proprietary MIB. However, the changes
you make directly through the MIB are lost whe n the RAC reboots. If you
want your changes to be permanent, you m ust use the configuration as
described in the m ethod above.

Traps are unsolicited administrative m essages ge nerated by SNMP agents on the
network. The keyword traphost defines the host to which SNMP traps are sent.
For the RAC to generate traps, one or more trap host addresses must be defined in
the gateway section of the configuration file along with the SNMP community
string. You can a lso temporarily add or modify the trap host definitions using the
anxTrapHostTable objects in the MIB. All generated trap messages use the first
community string defined in the configuration file (if the file does not contain a
community string, the RAC defaults to public).

You can specify up to ten static trap hosts in the configuration file, but each host
requires a separate line. Specify a trap host using its IP a ddress (RFC 1157
provides m ore details on communities and traps). The syntax is:

snmp traphost

<ipaddr>[:udp port number][community string]

You can configure the port number. The following example shows how to use this
feature when specifying a trap host.

snmp traphost 123.245.1.2
snmp traphost 132.245.6.50:1049 mycommstring

In the first trap host entry,neither a port nor a community string is defined. In this
case, the port defaults to the well-known trap port 162, and the community string
defaults to public.

In the second trap host entry,the trap port is specified as 1049, and the community
string is specified as mycommstring.

2-4 300861-C Rev. 00

Table 2-1 describes the standard SNMP traps supported by the RAC. The

proprietary traps and descriptions are provided in Chapter 5, “Error Handling.

Table 2-1. Supported Standard SNMP Traps

Trap Description

coldstart Upon initialization of the SNMP agent at boot time
linkUp Upon initialization of each network interface
linkDown Upon deconfiguration of any network interface

Defining the Contact String

The keyword contactdefines the object that identifies the person responsible for
managing the RAC, as supported by M IB-II. The syntax is:

snmp contact string

The string can include information about how to contact the person, for example,
M. Law, x 370 (MIB-II object contact).

Configuring the RAC for SNMP

Defining the Location String

The keyword location defines the object that describes the RAC’s location, for
example, computer room. Specifying this string defines the value of the MIB-II
object sysLocation.

The syntax is:

snmp location string

Defining the disabled_modules Parameter

The parameter disabled_modules allows you to turn off certain features during
software initialization (for example, enter lat, ppp, slip to turn these features off).
If you disable SNMP, the RAC discards all SNMP messages it receives. By
default, the SNMP agent on the RAC is enabled (for more details, see

disabled_modules in the Nortel Networks 5399 and 8000 Access Software
Reference).

300861-C Rev.00 2-5

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

Defining the allow_snmp_sets Parameter

The RAC’s default setting for the allow_snmp_sets parameter does not permit
parameter value changes because the SNM P set command’s header transmits the
community string in clear text, which may be a security risk. To modify
parameters through SNMP, you must first set allow_snmp_sets to yes using the
na utility, the admin command, or from the ROM m onitor. You cannot set this
parameter using SNMP. If security is a concern, you can take the following
measures:

1. Edit the %gateway section of the configurationfile for the RAC to define

at least one community string with read/write privileges. Change the line:

snmp community public

to:

snmp community config_utility * read-write

The RAC accepts SNMP sets only from sources using the community string
config_utility. You can further restrict the access by including the IP address

of the host system running the management application (for example, the
Config Utility) on the a nnex:

snmp community web_rac_mgr 192.9.200.55 read-write

2. Invoke na, configure the RACto accept and process SNMP command

sets, and exit na:

%na
command: annex 129.9.200.62
command: set annex allow_snmp_sets y
command: quit

3. Enter the selected community string when invoking the Config Utility or

other management applications.

Configuring BootP Relay

The bootp_enable parameter turns the BootP Relay feature on and off. For more
information a bout this parameter, see the xylo-anx.mib file.

2-6 300861-C Rev. 00

Chapter 3

Private MIBs and Standard MIB Support

This chapter describes the private enterprise MIBs for the RAC, and lists the
exceptions and restrictions placed on standard MIBs by the RAC SNMP agent.
This chapter includes:

• MIB Object Hierarchy

• Understanding MIB Objects

• Restrictions on Standard MIBs

• Private Enterprise MIBs

• Internet Group Management Protocol (IGMP) M IBs

• BootP Relay MIB

• Point-to-Point Protocol (PPP) Trace-to-Syslog MIBs

• Port Action Table

Standard RFC MIBs

The RAC supports the standard RFC MIBs listed in Table 3-1 with some
restrictions.

300861-C Rev.00 3-1

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

Table 3-1. Standard MIBs Supported by the RAC

RFC Object Name Description

1213 MIB-II Updated by RFCs 2011, 2012, and 2013.

For restrictions, refer to Table 3-2

1243 Appletalk MIB Support will be r einstated in this release.

For restrictions, refer to Table 3-3

1406 DS1 MIB Describes the MIB that manages DS1 interfaces.

For restrictions, refer to Table 3-6

1643 Ethernet MIB Obsoletes RFC 1623.

For restrictions, refer to Table 3-4

1724 RIP V2 M IB Obsoletes RFC 1389.

For restrictions, refer to Table 3-5

1850 OSPF MIB Used to configure and monitor the O SPF process

running on a RAC. RFC 1850 includes two files,

rfc1850a

definitions, and
definitions.

and

rfc1850b.rfc1850a

rfc1850b

contains OSPF trap

.

.

.

.

.

contains MIB

Note: There are other settable MIB objects included in the standard MIBs

supported by the SNMP agent. The read-only objects defined in the various
MIBs allow the SNMP management station to monitor many MIB variables.

Most parameters do not map to standard MIB objects. Instead, they map to MIB
objects in a proprietary (or pr ivate enterprise) MIB specific to the RAC and other
Remote Annexes. The private M IB also contains objects that provide status and
statistics information to the network manager (see C hapter 4, “Call

Management.”)

MIB Object Hierarchy

MIBs definethe hierarchy of managed objects. MIB objects represent data that the
RAC can retrieve or configuration information that it can modify.

3-2 300861-C Rev. 00

Understanding MIB Objects

RFC 1155 (Structure and Identification of Management Information for
TCP/IP-based Internets) describes the layout and encoding of exchanged data

objects. The SMI uses the ISO standard ASN.1 (Abstract Syntax Notation One) to
define a method for describing a hierarchical name space for m anaged
information.

Each object has:

• A name (also referred to as an Object Identifier [OID]).

• A syntax and an encoding. In addition to the basic integer and octet string data
types, several special types are defined (for example: IP Address, Network
Address,Counter, Gauge, TimeTicks). RFC 1212 (Concise MIB Definitions)is
an easier-to-read form used in most standard MIBs today. It defines the private
enterprise MIB.

Restrictions on Standard MIBs

The SNMP agent does not use all objects in the supported standard MIBs. Also,
there may be restrictions on the standard MIB objects that are supported. This
section lists the supported standard M IBs and outlines the differencesbetween the
RAC parameters and specific standard MIB objects. Table 3-1 lists the supported
standard MIBs.

Private MIBs and Standard MIB Support

RFC 1213 MIB-II Restrictions

The RAC supports RFC 1213’ssystem, interfaces, at, ip, icmp, tcp, udp,andsnmp
groups. It does not support the egp group. In addition, some individual objects
have the restrictions outlined in Table 3-2.

300861-C Rev.00 3-3

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

Table 3-2. RFC 1213 MIB-II Objects

get/set

Object Name

Restrictions Read Object Li mitations

ifAdminStatus Read only Ret urns only
ifOperStatus None Returns only
atEntry Cannot create

new rows

ipRouteEntry Cannot create

new rows

ipRouteProto None Returns only

ipRouteType None Returns only

ipNetToMediaEntry Cannot create

new rows

ipNetToMediaType Writesonly

(2)

,

and

invalid

dynamic (3)

static (4)

RFC 1243 AppleTalk MIB Restrictions

The RAC does not support the llap, rtmp, kip, zip,andnbp groups. It supports the
atport and ddp groups with the restrictions listed in Table 3-3.

None

None

and

and
None

Returns only

,

static (4)

rip (8)

indirect (4)

up (1)

and

down (2)

up (1)

and

down ( 2)

local (2), icmp (4),

invalid (2), direct ( 3),

dynamic (3)

and

3-4 300861-C Rev. 00

Private MIBs and Standard MIB Support

Table 3-3. RFC 1243 AppleTalk

Read Object

Object Name Restrictions

atportType Read only None
atportNetStart Not supported Not applicable
atportNetEnd Not supported Not applicable
atportNetAddress Not supported Not applicable
atportStatus Read only None
atportZone Read only None
atportIfIndex Read only None
ddpOutRequests Not supported Not applicable
ddpInLocalDatagrams Not supported Not applicable
ddpNoProtocolHandlers Not supported Not applicable
ddpBroadcastErrors Not supported Not applicable
ddpShortDDPErrors Notsupported Not applicable
ddpHopCountErrors Not supported Not applicable

Limitations

RFC 1643 Ethernet MIB Restrictions

The RAC supports RFC 1643’s dot3StatsTable and dot3CollTable with the
restrictions outlined in Table 3-4.

300861-C Rev.00 3-5

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

Table 3 -4. RFC 1643 Ethernet MIB Objects

Object Name Restrictions

dot3StatsSQETestErrors Notsupported Not applicable
dot3StatsInternalMac

ReceiveErrors
dot3StatsEtherChipSet Read only None
dot3CollIndex Notsupported Not applicable

Not suppor t ed Not applicable

RFC 1724 RIP V2 MIB Restrictions

The RAC supports rip2GlobalGroup, rip2IfStatTable,andrip2IfConfTable.It
does not support rip2PeerTable. Table 3-5 describes additional restrictions.

Table 3-5. RFC 1724 RIP V2 MIB Objects

Object Name Restrictions

Read Object
Limitations

Read Object
Limitations

rip2IfStatStatus Read only None
rip2IfConfDomain Not supported Not applicable
ripIfConfAuthKey Not supported Not applicable
ripIfConfStatus Read only None

RFC 1406 DS1 MIB Restrictions

All DS 1 MIB objects necessary to configure the RACPRI interface are supported,
but for some objec ts you are limited to setting default values. The RAC supports
this MIB with the restrictions de scribed in Table3-6.

3-6 300861-C Rev. 00

Private MIBs and Standard MIB Support

Table 3-6. RFC 1406 DS1 MIB Objects

Object Name Restrictions

MIB Tables
dsx1CurrentTable Not supported
dsx1IntervalTable Not supported
dsx1TotalTable Not supported
DSX1ConfigTable
dsx1LineType Not supported; use

anxt1dsx1LineType
dsx1TimeElapsed Not supported
dsx1ValidIntervals Not supported
dsx1SendCode Not supported
dsx1CircuitIdentifier Displaystring length limited to

128 bytes
dsx1TransmitClockSource Not supported
dsx1Fd1 Not supported

Private Enterprise MIBs

The private enterprise MIB file provides the object descriptions for the hardware,
software, ports, parameters, and commands groups for all Remote Access
Concentrator products.

Note: RACs support a subset of the private MIB objects or the hardware,

software, por ts, parameters, and commands groups. For example, the RAC
does not support objects related to parallel ports and async ports.

Location of Private MIB Files

The private MIBs reside in the /annex_root/src/snmp directory.

Private MIB Filenames

The software distribution kit provides the MIB files listed in Table 3-7. Ask your
local system administrator for the location of these MIB files on your system.

300861-C Rev.00 3-7

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

Table3-7. PrivateMIBFilenames

MIB Filename Description

xylo.smi Describes the structure of the Remote Access

Concentrator MIBs.

xylo.trp Contains the trap definitionsfor all the private

traps.

xylo-anx.mib Contains MIB objects related to configuring the

Model 8000 RAC and Model 5399 RAC (for
example, RAC-wide configuration settings).

xylo-callmgmt.mib Contains the private MIB active call and call

history objects.

xylo-modem.mib Contains all the private M IB objects for modem

status and configuration.
xylo-protocol.mib Contains the protocol-related private MIB groups.
xylo-trpobj.mib Contains the t rap host table object and all trap

thresholdobjects.
xylo-wan.mib Contains the MIB objects related to WANs ( either

PRI or T1).

Most of the configuration parameters are provided a s objects with read-write
access permission in the private enterprise MIB. A number of these parameters
are in the standard MIBs that the SNMP agent supports.

Most MIB object names for the parameters in the private enterprise MIB are
preceded by the string: “.iso.org.dod.internet.private.enterprises.xylogics.annex.”

MIB Prefixes

All MIB object names have prefixes that are used to organize them into gr oups.

Table 3-8 lists these prefixes and the corresponding MIB files that contain the

MIB objects with these prefixes.

Note: There are other settable M IB objects included in the standard M IBs

supported by the S NM P agent. The read-only objects defined in the various
MIBs allow the SNMP management station to m onitor many MIB variables.

3-8 300861-C Rev. 00

Private MIBs and Standard MIB Support

Table 3-8. Prefixes for MIB Object Names Related to the RAC

Prefix Corresponding MIB File

act xylo-callmgmt.mib
active xylo-callmgmt.mib
anx xylo-anx.mib
anxt1 xylo-wan.mib
call xylo-wan.mib
callhist xylo-callmgmt.mib
gp xylo-wan.mib
gsy xylo-anx.mib
igmp xylo-anx.mib
nfas xylo-anx.mib
ippool xylo-anx.mib
ntp xylo-ntp.mib
mdm xylo-modem.mib
mdmCall xylo-callmgmt.mib
radius xylo-anx.mib
pooling xylo-anx.mib
port xylo-callmgmt.mib
wan xylo-wan.mib

300861-C Rev.00 3-9

Chapter 4

Call Management

The RAC maintains call statistics for active calls and call history statistics for
previous calls. This chapter describes active call statistics,call history statistics,
active call M IBs, history MIBs, modem, and WAN statistics for the RAC.

This chapter includes the following sections:

• ActiveCall S tatistics

• Call History Statistics

•IGMP

• Modem MIBs

• WAN Statistics

Active Call Statistics

The RAC collects statistics for active calls and makes the information available to
management applications through SNMP MIB objects. Active call statistics are
also available through the command line interface (CLI). The statistics are used to
generate call information for monitoring the current state of the RAC, and for
general troubleshooting.

The active call statistics are updated each time you query them, either through the
CLI or SNMP. The MIB object names and descriptions for active call statistics are
listed in the actCallTable in the xylo-callmgmt.mib file, located in the
annex_root/src/snmp directory.

The actCallTa ble contains call information that is common to all devices (async,
sync, TA, MP and VPN).

300861-C Rev.00 4-1

The actCallTa ble is indexed by the activeCallDeviceType and the
activeCallDeviceNumber. The actCallTable is implemented as a sparse table.
Therefore, data is only returned for a ctive calls. Update older applications to use
the actCallTable.

Active Modem Calls

A further level of granularity is provided for active modem calls. The
actCallAsyTable in the xylo-callmgmt.mib file provides additional statistics
specifically for active modem calls. This table is indexed by the
activeCallDeviceNumber, which in this ca se is identical to the modem number.

For example, to get the receive baud rate for an active modem call on modem
number 16, use a MIB browser or other S NM P tool to perform a get actionon the
following MIB object:

activeCallAsyRxBaudRate.16

Active MP Calls

A further level of granularity is also provided f or active MP calls. The
actCallMpTable in the xylo-callmgmt.mib file provides additional statistics
specifically for active MP calls. This is implemented as a sparse table, and is
indexed by the activeCallDeviceNumber.

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

Port Action Table

The portActionTable provides an SNMP interface to port actions such as resetting
a port on a device type. This table provides information on actions on any
supported port on the system. For more information about this table, refer to the
xylo-callmgmt.mib file.

4-2 300861-C Rev. 00

Call History Statistics

The RAC maintains generic call history statistics for terminated calls (both
completed calls and calls that failed to connect) and m akes the information
available to mana gement applications through S NM P MIB objects. The statistics
are used to generate call information for accounting purposes and capacity
planning. The call history MIB object names and descriptions are listed in the
callHistTable in the xylo-callmgmt.mib file, located in the annex_root/src/snmp
directory.

This table is implemented as a sliding window. This means that the starting and
ending indexes will change dynamically. Use callHistStartIdx to find the starting
index and callHistEndIdx to find the last index.

The objects in the callHistTable are indexed by the MIB object callHistIndex
which is a unique index assigned to each call in the order in which it was
terminated.

You can configurethe number of calls that are logged in the callHistTable with the
callHistMaxCalls MIB object. The default value is zero (off).

Call Management

Note: The larger the number specified in callHistMaxCalls, the greater the

memory resources used by the RAC.Each call logged in the callHistTable uses
approximately 600 bytes of m emory.

Modem Call History Statistics

A further level of granularity is provided for modem call history statistics. The
callHistAsyTable in the xylo-callmgmt.mib file provides a dditional call history
statistics specifically for terminated modem calls. The callHistAsyTable is
implemented as a sparse table. The objects in the callHistAsyTable are indexed by
the MIB object c allHistIndex which is a unique index assigned to each call in the
order in which it was terminated.

300861-C Rev.00 4-3

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

MP Call History Statistics

A further level of granularity is provided for MP call history statistics. The
callHistMpTable in the xylo-callmgmt.mib file provides additional call history
statistics specifically for terminated MP calls. The callHistMpTable is
implemented as a sparse table. The objects in the callHistMpTable are indexed by
the MIB object callHistIndex, which is a unique index assigned to e ach ca ll in the
order in which it was terminated.

Internet Group Management Protocol (IGMP)

There are two MIB objects: igmpQueueSize and gmpMaxPendingMcast,
available f or managing the IGMP queues. These parameters define the maximum
elements that can be allocated to the IGMP processing queue and the maximum
number of multicast m essages allowed in the IGMP processing queue. For more
information, see the xylo-anx.mib file.

Modem MIBs

This section describes the three categories of modem MIBs that are in the
xylo-modem.mib file (located in the annex_root/src/snmp directory). All the
tables in this file a re indexed by the modem number (1 through number referenced
by the MIB object totalmodems). The individual MIB objects apply to all
modems in the RAC.

Modem Identification

The objectsin the mdmIdTable identify the hardware and software revisions of the
modems.

Modem Control

There are two MIB objects in the mdmCtlObjects group (mdmCtlResetAll and
mdmCtlReadConfig) that apply to all modems. They allow you to reset a ll
modems and read the modem configuration file, respectively. See the MIB object
descriptions in the xylo-modem.mib file for more details.

The objects in the mdmCtlTable r eset and set the state of individual modems. S ee
the MIB object de scriptions in the xylo-modem.mib file for more details.

4-4 300861-C Rev. 00

Modem Statistics

The objects in the mdmStatTable provide cumulative modem statistics for each
modem. See the MIB object descriptions in the xylo-modem.mib file for more
details.

WAN Statistics

The wanStatTable, indexed by a WAN interface number, provides WAN statistics.
This table is valid for WAN module platforms only. Refer to the xylo-wan.mib
file f or more information about this M IB object.

Call Management

300861-C Rev.00 4-5

This chapter describes error handling and error reporting.
The RAC handles errors and error reporting through the use of a number of error

counters, thresholds, and traps, and the P oint-to-Point Protocol (PPP) syslog.

Error Counters

The RAC makes use of a number of error counter MIB objects for the DS1 WAN
interfaces. The types of error counter MIB objects are:

• Current error counter MIBs

• Interval error counter MIBs

• Total error counter MIBs

Chapter 5

Error Handling

The counters store the error conditions as described in Table 5-1

Table 5-3 respectively.

300861-C Rev.00 5-1

, Table 5-2,and

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

Table 5-1. Current Error Counter MIBs

MIB Object Name Description

anxt1CurrentIndex The i ndex value of the DS1 interface for the current interval.
anxt1CurrentOofs The number of OOF (Out Of Frame) events for the current

interval. (An event begins when any two out of four
consecutive frame synchronizing bits are received from t he
network interface are incorrect.) An OOF state ends when
reframeoccurs.

anxt1CurrentBpvs The number of bipolar violation errors for the current interval.

(Bipolar violation is the occurrence of two consecutive pulses
with the same polarity.)

anxt1CurrentCrcs The number of CRC errors for the currentinterval. (DS1 signal

from incoming call does not agree with DS1 signal from the
network.)

anxt1CurrentCs The number of DS1 frames which are replicated or deleted in

the current interval.

anxt1CurrentRnacs The number of network alarms occurring in the current

interval. (This is expressed in seconds with at least one alarm

occurring per second.)
anxt1CurrentEsfError The extended superframe errors count in the current interval.
anxt1CurrentLofc The loss of framing errors count in the current interval.
dsx1CurrentUASs The number of unavailableseconds encountered by a DS1

interface in the current 15 minute interval.
dsx1CurrentPCVs The number of path encoding violations encountered by a

DS1 interface in the current 15 minute interval.
dsx1CurrentBESs The number of bursty errored seconds encountered by a DS1

interface in the current 15 minute interval.
dsx1CurrentCSSs The number of controlled slip seconds encountered by a DS1

interface in the current 15 minute interval.
dsx1CurrentESs Thenumber of errored seconds encountered by a DS1

interface in the current 15 minute interval.
dsx1CurrentSEFs The number of severelyerrored framing seconds encountered

by a DS1 interface in the current 15 minute interval.

5-2 300861-C Rev. 00

Error Handling

Table 5-2. Interval Error Counter MIBs

MIB Object Name Description

anxt1IntervalIndex The index value of the DS1 interface for t he s elected interval.
anxt1IntervalNumber A number between 1 and 96, where 1 is the most recently

completed 15 minute interval and 96 is the least recently

completed 15 minute interval (this assumes that all 96

intervals are valid).
anxt1IntervalOofs The numberof OOF eventsfor the selectedinterval. (An event

begins when any two out of four consecutive frame

synchronizing bits received from the network interface are

incorrect.)An OOF state ends when reframe occurs.
anxt1IntervalBpvs The numberof bipolar violation errors f or the selected interval.

(Bipolar violation is the occurrence of two consecutive pulses

with the same polarity.)
anxt1IntervalCrcs Thenumber of CRC errors for the selected interval. (DS1

signal from incoming call does not agree with DS1 signal from

the network.)
anxt1IntervalCs The number of DS1 frames which are replicated or deleted in

the selected interval.
anxt1IntervalRnacs The number of network alarms occurring in the selected

interval. (This is expressed in seconds with at least one alarm

occurring per second.)
anxt1IntervalEsfError Theextended superframe errors count in the selected interval.
anxt1IntervalLofc Theloss of framing errors count in the selected interval.

300861-C Rev.00 5-3

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

Table 5-3. Total Error Counter MIBs

MIB Object Name Description

anxt1TotalIndex The index value of the DS1 interface for the selected interval.
anxt1TotalOofs The number of OOF events for the selectedinterval.(An event

begins when any two out of four consecutive frame

synchronizing bits are received from the network interface are

incorrect.)An OOF state ends when reframe occurs.
anxt1TotalBpvs The number of bipolar violation errors for the selected interval.

(Bipolar violation is the occurrence of two consecutive pulses

with the same polarity.)
anxt1TotalCrcs The number of CRC errors for the selected interval. (DS1

signal from incoming call does not agree with DS1 signal from

the network.)
anxt1TotalCs The number of DS1 frames which are replicated or deleted in

the selected interval.
anxt1TotalRnacs The number of network alarms occurring in the selected

interval. (This is expressed in seconds with at least one alarm

occurring per second.)
anxt1TotalEsfError The extended superframe errorscount i n the selected interval.
anxt1TotalLofc The loss of framing errors count in the selected interval.

Thresholds

The threshold values are user selectableand range from 0 to 65535. When the
MIB counter meets or exceeds the threshold value, the corresponding trap is sent
to the trap hosts. Setting the threshold value to 0 disables the corresponding error
trap while setting the threshold to a higher number reduces the network traffic.

5-4 300861-C Rev. 00

Error Handling

Table 5-4 lists the threshold MIB objects, descriptions, a nd corresponding e rror

counters. (Error counter MIBs are in parentheses.)

Table 5-4. Threshold MIBs

MIB Object Name Description

wanBpvThreshold The t hreshold which, when met or exceeded, triggers the

wanBpvThreshTrap to be sent. (anxt1CurrentBpvs)
wanOofThreshold The threshold which, when met or exceeded, triggers the

wanOofThreshTrap to be sent. (anxt1CurrentOofs)
wanEsThreshold The threshold which, when met or exceeded, triggers the

wanEsThreshTrap to be sent.(dsx1CurrentESs)
wanCvThreshold The t hreshold which, when met or exceeded, triggers the

wanCvThreshTrap to be sent. (dsx1CurrentPCVs)
wanEsfThreshold The threshold which, when met or exceeded, triggers the

wanEsfThreshTrap to be sent. (anxt1CurrentEsfs)
wanSesThreshold The t hreshold which, when met or exceeded, triggers the

wanSesThreshTrap to be sent. (dsx1CurrentSEFs)
wanUasThreshold The threshold which, when met or exceeded, triggers the

wanUasThreshTrap to be sent.(dsx1CurrentUASs)
wanBesThreshold The t hreshold which, when met or exceeded, triggers the

wanBesThreshTrap to be sent. (dsx1CurrentBESs)
wanLofcThreshold The threshold which, when met or exceeded, triggers the

wanLofcThreshTrap to be sent. (anxt1CurrentLofcs)
wanCssThreshold The t hreshold which, when met or exceeded, triggers the

wanCssThreshTrap to be sent. (dsx1CurrentCSSs)
ds0ErrorThreshold This object defines the threshold for number of consecutive

calls that the ds0 fails to accept after which the ds0ErrorTrap

is sent to the trap host(s). Setting this object to zero disables

the trap.

PPP Trace-to-Syslog

Access the ppp_trace_lvl parameter, when debugging connection problems. For
more information about the M IB objects, see the xylo-wan.mib file.

300861-C Rev.00 5-5

Trap Configuration

The RAC generates SNMP traps, which are messages sent to users to inform them
of events. This release includes trap groups that enable and disable certain traps
and a filter to indicate which traps are sent to specific trap hosts. Refer to the
xylo-trpobj.mib file f or more information about these M IB objects.

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

5-6 300861-C Rev. 00

Proprietary Traps

The RAC generates various SNMP traps. Some alarm traps are generated when
the error counters have reached the error threshold. Clear traps are generated after
the associated trap has been sent. By default, all traps are disabled. Table 5-5 lists
the proprietary traps and descriptions.

Table 5-5. Proprietary Traps

MIB Object Name Description

callBeginTrap This trap is generated when an incoming call is detected or

callEndTrap This trap is generated when a call is terminated. The trap is

ds0ErrorThresholdTrap This trap is generated when the number of consecutive

dvsConnectFailure This trap is sent when a DVS connection fails.
forcedCallDisconnectTrap This t rap is generated when a call is disconnected due to

modemErrorTrap This trap is sent to the trap host(s) when a modem failure is

modemUnavailableTrap Thistrap is generated when no modems are avai lable to

Error Handling

an outbound call is generated by the RAC.This trap is sent
to the trap host defined in the configuration file.

sent t o t he trap host defined in the configurationfile. The
trap includes MIB objects as variable bindings. The trapis
controlled by the callENDTrapThresh MIB object.

failures meets or exceeds ds0ErrorThreshold.

inactivity. The RAC has the following activitytimers that
trigger this trap:

cliInactivityTimeout

the RAC waits before hanging up the call.

inactivityTimeout

RAC waits before terminating the call. Uses the value of
gpTimerInactivityTimer.

netActivityTimeout

detected automatically, the modem is busied out due to a
percentage failure threshold over a time period or a
consecutive failure threshold.

handle an incomingcall.

- The amount of time (in minutes) that

- The amount of time (in minutes) that the

- Similar to the activity timeout.

(continued)

300861-C Rev.00 5-7

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

Table 5-5. Proprietary Traps

MIB Object Name Description

unexpectDisconnectTrap This trap is generated when a call is disconnected

unexpectedly. A call is considered to disconnect
unexpectedly when one of the following occurs:

(continued)

protocolError
localHangup
timeoutHDLC
maxLogonTimeout

Or, when a call is handled by a modem, the unexpected
disconnect can be caused by

wanAlarmClearTrap This trap is generated when at least 15 seconds have

elapsed without a Red, Yellow, or Blue alarm.

wanAlarmTrap Thistrap is generated when a Red, Yellow,or Blue alarm is

detected.

wanBesClearTrap This trap is generated when a 15 minute interval is

terminated without the number of bursty errored seconds
meeting or exceeding wanBesThreshold.

wanBesThreshTrap This trap is generated when the number of bursty errored

seconds errors equals or exceeds the threshold defined by
wanBesThreshold.

wanBpvClearTrap This trap is generated when a 15 minute interval is

terminated without the number of bipolar er rors meeting or
exceedingwanBpvThreshold.

wanBpvThreshTrap This trap is generated when the number of bipolar violation

errors in a 15 m inute interval equals or exceeds the
threshold defined by wanBpvThreshold.

wanCssClearTrap This trap is generated when a 15 minute interval is

terminated without the number of controlled slip seconds
meeting or exceeding wanCssThreshold.

wanCssThreshTrap This trap is generated when the number of controlled slip

seconds errors equals or exceeds the threshold defined by
wanCssThreshold.

wanCvClearTrap This t rap is generated when a 15 minute interval is

terminated without the number of CRC6 errors meeting or
exceedingwanCvThreshold.

wanCvThreshTrap This trap is generated when the number of CRC6 er rors

equals or exceeds the threshold defined by
wanCvThreshold.

poorSignalQorfailRetrain

(continued)

.

5-8 300861-C Rev. 00

Error Handling

Table 5-5. Proprietary Traps

MIB Object Name Description

wanEsClearTrap This trap is generated when a 15 minute interval is

terminated without the number of errored seconds meeting
or exceeding wanEsThreshold.

wanEsfClearTrap This trap is generated when a 15 minute interval is

terminated without the number of ESF errors meeting or
exceedingwanEsfThreshold.

wanEsfThreshTrap This trap is generated when the number of ESF errors

equals or exceeds the threshold defined by
anxEsfThreshold.

wanEsThreshTrap This trap is generated when a number of errored seconds

errors equals or exceeds the threshold defined by
wanEsThreshold.

wanFailWanTrap This trapis generated when a WAN module fails initialization

procedures.

wanLofcClearTrap This trap is generated when a 15 minute interval is

terminated without the number of loss of frame count errors
meeting or exceeding wanLofcThreshold.

wanLofcThreshTrap This trap is generated when the number of loss of frame

count er rors equals or exceeds the threshold defined by
wanLofcThreshold.

wanOofClearTrap This trap is generated when a 15 minute interval is

terminated without the number of frame errors meeting or
exceedingwanOofThreshold.

wanOofThreshTrap This t rap is generated when the number of frame errors

equals or exceeds the threshold defined by the
wanOofThreshold.

wanSesClearTrap This trap is generated when a 15 minute interval is

terminated without the number of severely errored seconds
meeting or exceeding wanSesThreshold.

wanSesThreshTrap This trap is generated when the number of severely errored

seconds errors equals or exceeds the threshold defined by
wanSesThresold.

wanUasClearTrap This t rap is generated when a 15 minute interval is

terminated without the number of unavailable seconds
meeting or exceeding wanUasThreshold.

wanUasThreshTrap This trap is generated when the number of unavailable

seconds errors equals or exceeds the threshold defined by
the wanUasThreshold.

(continued)

300861-C Rev.00 5-9

Chapter 6

Troubleshooting

This chapter provides answers to the questions frequently asked when you are
unable to use SNMP to communicate with the RAC.

• Why am I unable to use SNMP to communicate with the RAC?
In order to enable SNMP communication with a RAC, the RAC SNMP agent

must be up and the specified community string must match one of the RAC
community strings. Check the configuration file to make sure that your host is
not disabled through the community string.

To perform operations which change parameters (e.g., the
allow_snmp_sets pa rameter on the RAC must be set to
this parameter only by using the non-SNMP na and admin tools, or by using
the ROM monitor.

• How can I tell if the SNM P agent is running on the RAC?
SNMP cannot be usedto communicate with a R AC unless the RACis running

the SNMP daemon process. You should use the

superuser or administrative mode from the direct c onnection to the RAC,

and then use the CLI proc comm and to find a line for the snmpd process. For
example, this line may read:

407 0 S0 7e8d0 103c 7f7f4 12 12 0 18 0:00.017 ? snmpd.

If there is no snmpd process, check the disabled_modules parameter using
admin or na. If this parameter indicates that SNMP is disabled, the RAC
discards SNMP messages. Remove snmp from the list of disabled modules
and reboot the RAC.

CLI su commandtogotothe

set c ommand), the

Y (Yes). You can set

300861-C Rev.00 6-1

Nortel Networks 5399 and 8000 Access Switch SNMP MIB Reference

• Why can’t I use an SNMP set to change parameters on the RAC?
You may be prevented from changing parameter values based on the value of

the allow_snmp_sets parameter. If allow_snmp_sets is set to

disabled, you

can use the telnet command to reach the RAC and run the superuser CLI

admin

command to set allow_snmp_sets to yes.

The RAC default value does not allow changes to configuration parameters
through SNMP. The RAC SNMP agent uses SNMP version 1. The only
security check performed by the SNMP agent is to match the community
string in an incoming SNMP packet with the defined community strings for
the RAC. Since the community string in the S NMP packet is transmitted in
the clear (not encrypted), there is a potential security risk in allowing changes
to the configuration through SNMP messages. If you wish to configure the
RAC using SNMP, please be aware of this situation.

If the IP address associated with the community string doesn’t m atch, you
may not have access to sets. If the community string and IP address match,
check to make sure that access is r ead/write and not read only.

• Why do I see a “Parameter does not exist” message?
Not all parameters apply to all RAC hardware configurations or all software

releases. Therefore, you may see this message when you use the

show or set

commands.
The community string m ay be wrong. If set, allow_snmp_sets may be set to

no, or the community may not have write privileges.

6-2 300861-C Rev. 00

A

acronyms, xii
actCallAsyTable, 4-2
actCallMpTable, 4-2
actCallTable, 4-1
active call statistics, 4-1
active modem calls, 4-2
active MP calls, 4-2
activeCallDeviceNumbe, 4-2
activeCallDeviceType, 4-2
allow_snmp_setsparameter, 1-2, 2-6

B

Before you begin, ix

C

call history statistics, 4-3
call management,4-1
callHistAsyTable, 4-3
callHistEndIdx, 4-3
callHistIndex, 4-4
callHistMpTable, 4-4
callHistStartId, 4-3
callHistTable, 4-3
communitystring

defining, 2-3

configuration parameters

global port

allow_snmp_sets,1-2

RAC

allow_snmp_sets,1-2

Index

contactstring

defining, 2-5

customersupport,xiii

D

disabled_modules parameter, 1-3, 2-5

G

gateway

entries

for SNMP community, 2-3
for SNMP trap hosts, 2-4

uses for configuring SNMP agent, 2-1

M

mdmCtlObject, 4-4
mdmCtlReadConfig, 4-4
mdmCtlTable, 4-4
mdmStatTable, 4-5
MIBs, 1-1

MIB object hierarchy, 3-2
prefixes for MIB Object Names, 3-8
RAC restrictions on, 3-7

MIBs supported by RAC

AppleTalk M IB, and restrictions, 3-4
DS1 MIB objects, 3-7
DS1 MIB, and object restrictions, 3-6
Ethernet MIB, and object restrictions, 3-5
MIB-II, and object restrictions, 3-3

RIPv2 MIB, and object restrictions, 3-6
modem call history statistics, 4-3
modem MIBs, 4-4

300861-C Rev.00 Index-1

MP call history statistics, 4-4

U

P

Port Actions, 4-2
portActionTable, 4-2
product support, xiii
publications

hard copy, xiii

S

SNMP

commands, 1-2

get, 1-2
get-next, 1-2

set, 1-2
configuring the RAC for, 2-1
definition, 1-1
gateway entry for community string, 2-3
gateways file entry for trap hosts, 2-4
MIB object hierarchy, 3-2
overview, 1-1
SNMP agent configur ation

defining allow_snmp_sets parameter, 2-6

defining community string, 2-3

defining contact string, 2-5

defining disabled_modulesparameter, 2-5

defining location string, 2-5

defining trap hosts and traps,2-4
supported standardtraps, 2-5
understanding MIB objects, 3-3
using set to send commands to RAC, 1-3

standardMIBs supported by RAC

list of, 3-2
restrictions on, 3-3

support, Nortel Networks,xiii

Unreliable Datagram Protocol, 1-1

W

wanStatTable, 4-5

T

technicalpublications, xiii
technicalsupport, xiii
trap hosts

defining, 2-4

troubleshooting, 6-1

Index-2 300861-C Rev. 00