Cabletron Systems ELS10-26 User manual

ELS10-26 MIB REFERENCE
GUIDE
9032244-01

Notice
i
NOTICE
Cabletron Systems reserves the right to make changes in specifications and other information
contained in this document without prior notice. The reader should in all cases consult Cabletron
Systems to determine whether any such changes have been made.
The hardware, firmware, or software described in this manual is subject to change without notice.
IN NO EVENT SHALL CABLETRON SYSTEMS BE LIABLE FORANY INCIDENTAL,
INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT
NOT LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATED TO THIS MANUAL OR
THE INFORMATION CONTAINED IN IT, EVEN IF CABLETRON SYSTEMS HAS BEEN
ADVISED OF, KNOWN, OR SHOULD HAVE KNOWN, THE POSSIBILITY OF SUCH
DAMAGES.
 Copyright 1997 by Cabletron Systems, Inc., P.O. Box 5005, Rochester, NH 03866-5005
All Rights Reserved
Printed in the United States of America
Order Number: 9032244-01 September 1997
Cabletron Systems, SPECTRUM, and LANVIEW are registered trademarks and
SmartSTACK , ELS10-26TX , FEPIM , FEPIM-TX and FEPIM-FX are trademarks of
Cabletron Systems, Inc.
All other product names mentioned in this manual may be trademarks or registered trademarks of
their respective companies.
FCC NOTICE
This device complies with Part 15 of the FCC rules. Operation is subject to the following two
conditions: (1) this device may not cause harmful interference, and (2) this device must accept any
interference received, including interference that may cause undesired operation.
NOTE: This equipment has been tested and found to comply with the limits for a Class A digital
device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is operated in a commercial environment.
This equipment uses, generates, and can radiate radio frequency energy and if not installed in
accordance with the operator’s manual, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause interference in which case the user
will be required to correct the interference at his own expense.
WARNING: Changes or modifications made to this device which are not expressly approved by the
party responsible for compliance could void the user’s authority to operate the equipment.
Printed on Recycled Paper

Notice
ii
DOC NOTICE
This digital apparatus does not exceed the ClassA limits for radio noise emissions from digital
apparatus set out in the Radio Interference Regulations of the Canadian Department of
Communications.
Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables
aux appareils numériques de la class A prescrites dans le Règlement sur le brouillage radioélectrique
édicté par le ministère des Communications du Canada.
VCCI NOTICE
This is a Class A product based on the standard of the Voluntary Control Council for Interference by
Information Technology Equipment (VCCI). If this equipment is used in a domestic environment,
radio disturbance may arise. When such trouble occurs, the user may be required to take corrective
actions.
CABLETRON SYSTEMS, INC. PROGRAM LICENSE AGREEMENT
IMPORTANT: Before utilizing this product, carefully read this License Agreement.
This document is an agreement between you, the end user, and Cabletron Systems, Inc. (“Cabletron”)
that sets forth your rights and obligations with respect to the Cabletron software program (the
“Program”) contained in this package. The Program may be contained in firmware, chips or other
media. BY UTILIZING THE ENCLOSED PRODUCT,YOU ARE AGREEING TO BECOME
BOUND BY THE TERMS OF THIS AGREEMENT, WHICH INCLUDES THE LICENSE AND
THE LIMITATION OF WARRANTYAND DISCLAIMER OF LIABILITY. IFYOU DO NOT
AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE UNUSED
PRODUCT TO THE PLACE OF PURCHASE FOR A FULL REFUND.

Notice
iii
CABLETRON SOFTWARE PROGRAM LICENSE
1. LICENSE. You have the right to use only the one (1) copy of the Program provided in this
package subject to the terms and conditions of this License Agreement.
You may not copy, reproduce or transmit any part of the Program except as permitted by the
Copyright Act of the United States or as authorized in writing by Cabletron.
2. OTHER RESTRICTIONS. You may not reverse engineer, decompile, or disassemble the
Program.
3. APPLICABLE LAW. This License Agreement shall be interpreted and governed under the laws
and in the state and federal courts of New Hampshire. You accept the personal jurisdiction and
venue of the New Hampshire courts.
EXCLUSION OF WARRANTY AND DISCLAIMER OF LIABILITY
1. EXCLUSION OF WARRANTY. Except as may be specifically provided by Cabletron in
writing, Cabletron makes no warranty, expressed or implied, concerning the Program (including
its documentation and media).
CABLETRON DISCLAIMS ALL WARRANTIES, OTHER THAN THOSE SUPPLIED TO
YOU BY CABLETRON IN WRITING, EITHER EXPRESSED OR IMPLIED, INCLUDING
BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE PROGRAM, THE
ACCOMPANYING WRITTEN MATERIALS, AND ANY ACCOMPANYING HARDWARE.
2. NO LIABILITY FOR CONSEQUENTIAL DAMAGES. IN NO EVENT SHALL
CABLETRON OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER
(INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS,
PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, SPECIAL,
INCIDENTAL, CONSEQUENTIAL, OR RELIANCE DAMAGES, OR OTHER LOSS)
ARISING OUT OF THE USE OR INABILITY TO USE THIS CABLETRON PRODUCT,
EVEN IF CABLETRON HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES. BECAUSE SOME STATES DO NOT ALLOW THE EXCLUSION OR
LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, OR
ON THE DURATION OR LIMITATION OF IMPLIED WARRANTIES, IN SOME
INSTANCES THE ABOVE LIMITATIONS AND EXCLUSIONS MAY NOT APPLY TO
YOU.
UNITED STATES GOVERNMENT RESTRICTED RIGHTS
The enclosed product (a) was developed solely at private expense; (b) contains “restricted computer
software” submitted with restricted rights in accordance with Section 52227-19 (a) through (d) of the
Commercial Computer Software - Restricted Rights Clause and its successors, and (c) in all respects
is proprietary data belonging to Cabletron and/or its suppliers.
For Department of Defense units, the product is licensed with “Restricted Rights” as defined in the
DoD Supplement to the Federal Acquisition Regulations, Section 52.227-7013 (c) (1) (ii) and its
successors, and use, duplication, disclosure by the Government is subject to restrictions as set forth in
subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at
252.227-7013. Cabletron Systems, Inc., 35 Industrial Way, Rochester, New Hampshire 03867-0505.

Notice
iv
DECLARATION OF CONFORMITY
Application of Council Directive(s): 89/336/EEC
73/23/EEC
Manufacturer’s Name: Cabletron Systems, Inc.
Manufacturer’s Address: 35 Industrial Way
PO Box 5005
Rochester, NH 03867
European Representative Name: Mr. J. Solari
European Representative Address: Cabletron Systems Limited
Nexus House, Newbury Business Park
London Road, Newbury
Berkshire RG13 2PZ, England
Conformance to Directive(s)/Product Standards: EC Directive 89/336/EEC
EC Directive 73/23/EEC
EN 55022
EN 50082-1
EN 60950
Equipment Type/Environment: Networking Equipment, for use in a
Commercial or Light
Industrial
Environment.
We the undersigned, hereby declare, under our sole responsibility, that the equipment packaged
with this notice conforms to the above directives.
Manufacturer Legal Representative in Europe
Mr. Ronald Fotino Mr. J. Solari
___________________________________ ___________________________________
Full Name Full Name
Principal Compliance Engineer Managing Director - E.M.E.A.
___________________________________ ___________________________________
Title Title
Rochester, NH, USA Newbury, Berkshire, England
___________________________________ ___________________________________
Location Location

v
TABLE OF CONTENTS
Chapter 1 Introduction
1.1 Related Documentation...................................................1-2
1.2 Getting Help....................................................................1-3
1.3 Document Conventions...................................................1-4
1.4 SNMP Primitives............................................................1-5
1.5 MIB Primitive Types ......................................................1-6
1.6 User Functions................................................................1-7
1.7 Navigating Through the MIBTree Structure...................1-9
1.8 TFTP...............................................................................1-13
1.8.1 Retrieving All Parameters...................................1-15
1.8.2 Setting All Parameters ........................................1-15
1.9 Additional Interfaces.......................................................1-16
Chapter 2 TCP/IP MIB-II
2.1 System Group..................................................................2-1
2.2 Interfaces Group..............................................................2-2
2.3 Address Translation Group.............................................2-8
2.4 IP Group..........................................................................2-9
2.4.1 IP Address Table.................................................2-12
2.4.2 IP Routing Table.................................................2-14
2.4.3 IP Address Translation Table..............................2-17
2.4.4 IP Additional Objects..........................................2-18
2.5 ICMP Group....................................................................2-19
2.6 TCP Group......................................................................2-22
2.7 UDP Group .....................................................................2-22
2.7.1 UDP Listener Table ............................................2-23
2.8 EGP Group......................................................................2-24
2.9 OIM Subtree....................................................................2-24
2.10 Transmission Group........................................................2-24
2.11 SNMP Management Group.............................................2-25
2.12 Cabletron Interface Group ..............................................2-29
2.13 Cabletron Interface Port Group.......................................2-32
2.14 Cabletron Com Port Configuration Group......................2-35

Contents
vi
2.15 SNMP Version Group.....................................................2-37
2.16 Trap Description .............................................................2-38
2.17 Cabletron MIB 2 Extensions...........................................2-39
Chapter 3 Ethernet MIB
3.1 Generic Ethernet-Like Group .........................................3-1
3.2 Ethernet-Like Statistics Group........................................3-2
3.3 Ethernet-Like Collision Statistics Group........................3-5
3.4 Ethernet-Like Tests Group..............................................3-6
3.5 Ethernet-Like Errors Group............................................3-6
3.6 Ethernet-Like Chipsets Group ........................................3-6
Chapter 4 Bridge MIB
4.1 Base Group......................................................................4-1
4.2 Spanning Tree Group......................................................4-3
4.3 Transparent Group..........................................................4-9
Chapter 5 PPP MIB
5.1 PPP Link Control Table..................................................5-1
5.2 PPP IP Table...................................................................5-10
Chapter 6 ELS10-26 MIB
6.1 System Group..................................................................6-1
6.1.1 Hardware Configuration Group..........................6-2
6.1.2 LXSW Configuration Group...............................6-4
6.1.3 Administration Group.........................................6-6
6.1.4 Software Distribution Group...............................6-11
6.1.5 Addresses Configuration Group .........................6-13
6.1.6 Cabletron Interfaces Group.................................6-16
6.1.7 Cabletron Dot3 Group.........................................6-20

Contents
vii
6.1.8 Cabletron UART Interface Group ......................6-23
6.1.9 Cabletron Protocol Group...................................6-24
6.1.10 Cabletron Trunking Group..................................6-26
6.1.11 Cabletron Workgroup Management Group........6-29
6.1.12 Cabletron Trap Management Group...................6-31
6.1.13 Ping Management MIB.......................................6-35
6.1.14 Traceroute...........................................................6-41
6.1.15 Traceroute Management MIB.............................6-42
6.1.16 Port Mirroring.....................................................6-47
Chapter 7 Traps
7.1 Generic Traps..................................................................7-1
7.2 Enterprise Specific Traps For The ELS10-26.................7-2

viii
Contents

1-1
CHAPTER 1
INTRODUCTION
This manual is for system administrators responsible for
configuring, monitoring, and maintaining the ELS10-26. Much of
the configuration of the ELS10-26 needs to be done using an
SNMP-based network management station. This manual contains
the SNMP MIB variables you may need to configure, monitor, and
manage your ELS10-26. You should use this manual with the
ELS10-26 User Guide and with the documentation provided with
your NMS.
The contents of each chapter are described below.
• Chapter 1, Introduction , provides an overview of the SNMP
primitives, describes the functions the MIB variables can be used
to perform, and describes how to use TFTP to download the
ELS10-26 system software.
• Chapter 2, TCP/IP MIB-II , describes the standard TCP/IP MIB
variables.
• Chapter 3, Ethernet MIB , describes the standard Ethernet MIB
variables.
• Chapter 4, Bridge MIB , describes the Bridge MIB variables.
• Chapter 5, PPP MIB , describes the PPP link control and IP table
MIB variables.
• Chapter 6, ELS10-26 MIB , describes the Cabletron enterprise
MIB variables.
• Chapter 7, Traps , describes generic and enterprise-specific
traps.

1-2
Introduction
1.1 RELATED DOCUMENTATION
You may need to refer to the following Cabletron documentation:
• ELS10-26 User Guide – contains installation, configuration, and
management instructions for the ELS10-26. It also describes how
to use the Local Console Manager (LCM), which is a
non-intelligent terminal interface to the ELS10-26.
If you need internetworking reference material, you may find the
following books helpful:
• Interconnections, Bridges and Routers, Radia Perlman, Addison
Wesley © 1992.
• Internetworking with TCP/IP: Principles, Protocols, and Architecture
(2nd edition), Volumes I and II, Douglas Comer,
Prentice Hall © 1991.
• The Simple Book, An Introduction to Management of TCP/IP-based
internets (2nd edition), Marshall T. Rose, Prentice Hall © 1994.
This manual describes the software interface between the NMS
and the ELS10-26. This is relevant for an ELS10-26 running Version
1.0 software. The NMS communicates with the ELS10-26 software.
The Network Management, or UART, port is the interface to the
Local Console Manager (LCM). LCM is a non-intelligent terminal
interface that can be used to configure and monitor status for the
ELS10-26.

Introduction
1-3
1.2 GETTING HELP
If you need additional support related to the ELS10-26, or if you
have any questions, comments, or suggestions concerning this
manual, contact Cabletron Systems Global Call Center:
Phone: [phone]
Internet mail: [email protected]
FTP: ctron.com (134.141.197.25)
Login: anonymous
Password: your email address
BBS: [phone]
Modem setting: 8N1: 8 data bits, No parity, 1 stop bit
Before calling Cabletron Systems Global Call Center, have the
following information ready:
• Your Cabletron Systems contract number
• A description of the failure
• The serial and revision numbers of all Cabletron Systems
products in the network
• A description of any action(s) already taken to resolve the
problem (e.g., changing mode switches, rebooting the unit, etc.)
• A description of your network environment (layout, cable type,
etc.)
• Network load and frame size at the time of trouble (if known)
• The device history (i.e., have you returned the device before, is
this a recurring problem, etc.)
• Any previous Return Material Authorization (RMA) numbers
For additional information about Cabletron Systems products,
visit our World Wide Web site: http://www.cabletron.com

1-4
Introduction
1.3 DOCUMENT CONVENTIONS
The following conventions are used throughout this document:
LCM commands, prompts, and information displayed by the
computer appear in Courier typeface, for example:
Current Number of Learned Addresses: 133
Information that you enter appears in Courier bold typeface, for
example:
ELS10-26 > status
Information that you need to enter with a command is enclosed in
angle brackets < >. For example, you must enter a port number
and an IP address to execute the
ipaddr <port #> <IP address>
command:
ELS10-26 > ipaddr 6 192.138.217.40
Field value options appear in bold typeface.
The following conventions are also used in this document:
Note: Calls the reader’s attention to any item of information that may be
of special importance.
Tip: Conveys helpful hints concerning procedures or actions.
Caution: Contains information essential to avoid damage to the
equipment.

Introduction
1-5
1.4 SNMP PRIMITIVES
The major software interface between the NMS and ELS10-26
consists of one simple mechanism – the exchange of SNMP (Simple
Network Management Protocol, RFC 1157) datagrams over any
available physical media. The following restrictions apply:
• All datagrams must obey SNMP format.
• All datagrams must be sent via UDP and IP. Thus, all datagrams
will have UDP and IP headers.
• Datagrams may be sent over any of the following physical
media:
- Ethernet/802.3 LAN - the datagram must have an Ethernet
MAC header, with an Ethernet frame type of IP; or, the
datagram must be in 802.3 format with IP-encapsulation as
defined by RFC 1042.
- UART (out-of-band management port) - the datagram must
have a PPP header, which indicates that the datagram
contains an IP packet. (The ELS10-26 automatically detects
the presence of a PPP connection versus being connected to
a non-intelligent terminal.)
The NMS must rely on IP, rather than MAC addressing for all
datagrams sent to an ELS10-26. Therefore:
• All datagrams from the ELS10-26 are addressed to either an
NMS or the broadcast IP address.
• Within the context of this document, the terms “datagram,”
“packet,” and “PDU” are synonymous.

1-6
Introduction
1.5 MIB PRIMITIVETYPES
The MIB definitions in this document may reference the primitive
types that are described in the Structure and Identification of
Management Information for TCP/IP-based Internets, RFC 1155.
RFC 1155 is based on the Specification of Abstract Syntax Notation
One, ASN.1. The primitive types are described in Table 1-1.
Table 1-1 Primitive Descriptions
Primitive Size Description
Boolean 1 byte Enumerated Integer with possible true (1) or false (2) values; note that the ASN.1
BOOLEAN primitive type is not used
BridgeID 8 bytes Priority and MAC address used to identify
a spanning tree bridge
Counter 4 bytes max Unsigned value
DisplayString n X 1 byte Array of printable ascii characters
Gauge 4 bytes Non-negative integer
Integer 4 bytes max Signed value
IpAddress 4 bytes Internet address
MacAddress 6 bytes Ethernet address
OctetString n X 1 byte Array of bytes
PhysAddress n X 1 byte Array of bytes, using the same as a MAC
Address
PortID 2 bytes Priority and port number used to identify a
spanning tree port
TimeTicks 4 bytes Max time counter with a granularity of 1/100th of a second (also known as
centiseconds)

Introduction
1-7
1.6 USER FUNCTIONS
The SNMP primitives may be used to accomplish the following
functions:
• Obtain the ELS10-26’s current value of certain parameters - the
NMS uses the GetRequest or GetNextRequest PDU, and the
ELS10-26 responds with a GetResponse PDU. If the NMS issues
a GetRequest for an unsupported parameter, the ELS10-26 sends
a GetResponse with a noSuchName
ErrorStatus
1
. If the NMS
issues a GetNextRequest for an unsupported parameter, the
ELS10-26 skips to the next object.
• Change the ELS10-26’s value of certain parameters - the NMS
uses the SetRequest PDU, and the ELS10-26 responds with a
GetResponse PDU. The ELS10-26 will change both its current
value and its local default to be used when the ELS10-26 reboots,
unless noted otherwise.
• Obtain the current value of certain parameters and
simultaneously change the value of other parameters - the NMS
uses the SetRequest PDU, and the ELS10-26 responds with a
GetResponse PDU. For the parameters which are being obtained
rather than changed, the NMS must use the ASN.1 NULL value
with the SetRequest PDU.
• Provide notification of significant events - the ELS10-26 uses the
Trap PDU and/or the GetResponse PDU. The NMS uses the
SetRequest PDU to control the frequency that the ELS10-26 may
send Trap PDUs.
1.
If implementing the parameter is required, it might seem more reasonable to
return a GetResponse with no error and the ASN.1 NULL value as the
parameter’s value; however, leading authorities such as Marshall T. Rose (author
of The Simple Book ) suggest that noSuchName be returned, because many
existing SNMP management stations do not handle NULL values correctly.

1-8
Introduction
The ELS10-26 implements two non-standard features with respect
to the SNMP SetRequest:
• The variable bindings within a SetRequest are sometimes
processed sequentially rather than simultaneously. For example,
if a SetRequest contains two parameters with an incorrect value
specified for the second parameter, the ELS10-26 returns a
badValue error to the NMS; however, the ELS10-26 may have
updated its value for the first parameter.
• The values within the variable bindings of the returned
GetResponse may reflect meaningful information, rather than
being an exact copy of the values from the SetRequest. For
example, if a SetRequest contains two variable bindings, the first
specifying that memory should be examined and the second
specifying the contents of the memory, then the ELS10-26’s
GetResponse will update the value of the second variable
binding to contain the actual contents of the memory.

Introduction
1-9
1.7 NAVIGATINGTHROUGH THE MIBTREE STRUCTURE
The MIB structure is a hierarchical tree structure. Each MIB
variable has a numeric value that indicates its place in the
hierarchy. The structure was originally created, and is still
maintained by the International Organization for Standardization
(ISO) and the International Telecommunications Union (ITU), two
international standards organizations. You can get and set MIB
variables by navigating down the tree to a specific MIB, a group or
table within that MIB, and then to the individual variable.
Figure 1-1 shows the path down the MIB tree structure. Under the
“mib-2” and the Cabletron enterprise branch, are all the relevant
MIBs that the ELS10-26 supports.

1-10
Introduction
Figure 1-1 MIB Hierarchical Structure
Table 1-2 provides the branch structure that is under MIB-II. To
reach any of the MIB-II objects you would start with the prefix
1.3.6.1.2.1. For example, to reach an object in the system group, you
would start with 1.3.6.1.2.1.1. To find the amount of time the
ELS10-26 had been running, you would want to get the sysUpTime
variable, which is the third object in the system group. So the get
command would look like:
get 1.3.6.1.2.1.1.3.0
......
iso
1
org
3
dod
6
1
mgmt
2
mib-2
1
experimental private
internet
1
system interfaces add trans ip
234 39
3
rdbmsMIB
4
1
enterprise
97
sigma