Cabletron Systems ATX User manual

ATX
MIB REFERENCE GUIDE
9031872-01

ATX MIB Reference Guide 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 1996 by Cabletron Systems, Inc., P.O. Box 5005, Rochester, NH 03866-5005
All Rights Reserved
Printed in the United States of America
Order Number: 9031872-01 May 1996
All product names mentioned in this manual may be trademarks or registered trademarks of their
respective companies.
Printed on Recycled Paper

Notice
ii ATX MIB Reference Guide
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.
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 equipment is in the 1st Class Category (information equipment to be used in commercial and/or
industrial areas) and conforms to the standards set by the Voluntary Control Council for Interference
by Information Technology Equipment (VCCI) aimed at preventing radio interference in commercial
and/or industrial areas.
Consequently, when used in a residential area or in an adjacent area thereto, radio interference may be
caused to radios and TV receivers, etc.
Read the instructions for correct handling.

Notice
ATX MIB Reference Guide iii
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 WARRANTY AND DISCLAIMER OF LIABILITY. IFYOU DO NOT
AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE UNUSED
PRODUCT TO THE PLACE OF PURCHASE FORA FULL REFUND.
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 DISCLAIMSALL 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.

Notice
iv ATX MIB Reference Guide
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.

ATX MIB Reference Guide v
CONTENTS
CHAPTER 1 INTRODUCTION
1.1 Document Conventions...............................................................1-2
1.2 Related Documentation...............................................................1-3
1.3 Getting Help.................................................................................1-4
1.4 SNMP Primitives..........................................................................1-4
1.5 MIB Primitive Types.....................................................................1-5
1.6 User Functions ............................................................................1-6
1.7 Navigating Through the MIB Tree Structure................................1-7
1.8 TFTP..........................................................................................1-10
1.8.1 Software Distribution.................................................1-10
1.8.2 Retrieving All Parameters..........................................1-11
1.8.3 Setting All Parameters...............................................1-11
1.9 Additional Interfaces..................................................................1-11
CHAPTER 2 TCP/IP MIB-II
2.1 System Group..............................................................................2-1
2.2 Interfaces Group..........................................................................2-3
2.3 Address Translation Group..........................................................2-8
2.4 IP Group......................................................................................2-9
2.4.1 IP Address Table.......................................................2-11
2.4.2 IP Routing Table........................................................2-13
2.4.3 IP Address Translation Table....................................2-16
2.4.4 IP Additional Objects.................................................2-17
2.5 ICMP Group...............................................................................2-17
2.6 TCP Group ................................................................................2-20
2.7 UDP Group................................................................................2-21
2.7.1 UDP Listener Table...................................................2-21
2.8 EGP Group................................................................................2-22
2.9 OIM Subtree..............................................................................2-22
2.10 Transmission Group..................................................................2-22
2.11 SNMP Group.............................................................................2-23
CHAPTER 3 ETHERNET MIB
3.1 Generic Ethernet-Like Group.......................................................3-1
3.2 Ethernet-Like Statistics Group.....................................................3-3
3.3 Ethernet-Like Collision Statistics Group......................................3-5
3.4 Ethernet-Like Tests Group ..........................................................3-5
3.5 Ethernet-Like Errors Group .........................................................3-5
3.6 Ethernet-Like Chipsets Group.....................................................3-6

Contents
vi ATX MIB Reference Guide
CHAPTER 4 TOKEN RING MIB
4.1 Token Ring Group........................................................................4-1
4.1.1 Token Ring Interface Table .........................................4-1
4.1.2 Token Ring Statistics Table.........................................4-4
4.1.3 Token Ring Timer Table ..............................................4-7
4.1.4 Token Ring Tests.........................................................4-7
4.1.5 Token Ring Chipsets ...................................................4-7
CHAPTER 5 FDDI MIB
5.1 SMT Group ..................................................................................5-1
5.1.1 SMT Table ...................................................................5-2
5.2 MAC Group..................................................................................5-6
5.2.1 MAC Table...................................................................5-6
5.3 MAC Counter Group ..................................................................5-12
5.4 PATH Group ..............................................................................5-12
5.4.1 PATH Table ...............................................................5-12
5.4.2 PATH Config Table....................................................5-14
5.5 PORT Group..............................................................................5-15
5.5.1 PORT Table...............................................................5-15
CHAPTER 6 BRIDGE MIB
6.1 Base Group..................................................................................6-1
6.2 Spanning Tree Group ..................................................................6-3
6.3 Source Route Group....................................................................6-8
6.4 Transparent Group.....................................................................6-12
6.5 Static Database Group...............................................................6-15
CHAPTER 7 REPEATER MIB
7.1 Basic Package.............................................................................7-1
7.2 Group Info....................................................................................7-3
7.3 Port Info .......................................................................................7-5
7.4 Monitor Package..........................................................................7-7
7.5 Monitor rptr Info............................................................................7-7
7.6 Monitor Group Info.......................................................................7-7
7.7 Monitor Port Info ..........................................................................7-8
7.8 Address Tracking Package........................................................7-13
7.9 Address Tracking rptr Info..........................................................7-13
7.10 Address Tracking Group Info.....................................................7-13
7.11 Address Tracking Port Info ........................................................7-13

Contents
ATX MIB Reference Guide vii
CHAPTER 8 PPP MIB
8.1 PPP Link Control Table...............................................................8-1
8.2 PPP IP Table...............................................................................8-9
8.3 PPP Bridge Support ..................................................................8-11
CHAPTER 9 APPLETALK MIB
9.1 LLAP Group.................................................................................9-1
9.2 AARP Group................................................................................9-3
9.3 ATPort Group ..............................................................................9-4
9.4 DDP Group..................................................................................9-6
9.5 RTMP Group ...............................................................................9-8
9.6 ZIP Group..................................................................................9-10
9.7 NBP Group................................................................................9-11
9.8 ATEcho Group...........................................................................9-12
CHAPTER 10 CABLETRON MIB
10.1 System Group............................................................................10-1
10.2 Reserved Group........................................................................10-2
10.3 ATX Group.................................................................................10-2
10.3.1 Hardware Configuration Group .................................10-3
10.3.2 Software Configuration Group.................................10-13
10.3.3 Unit Administration Group.......................................10-15
10.3.3.1 Configuration Status Group .................10-15
10.3.3.2 LMA Configuration Group....................10-19
10.3.3.3 PPE Configuration Group ....................10-20
10.3.3.4 Spanning Tree Group ..........................10-26
10.3.3.5 Mesh Group.........................................10-27
10.3.4 Software Distribution Group....................................10-28
10.3.5 Addresses Configuration Group..............................10-30
10.3.6 SNMP/SMT Support Group.....................................10-40
10.3.7 Cabletron Interfaces Group.....................................10-42
10.3.8 Cabletron FDDI Interfaces Group............................10-51
10.3.9 Cabletron UART Interface Group............................10-56
10.3.10 Filter Group .............................................................10-57
10.3.11 Change Reboot Characteristics
Command Group.....................................................10-64
10.3.12 Debug Command Group.........................................10-66
10.3.13 Loopback Command Group....................................10-68
10.3.14 Cabletron WAN Interface Group .............................10-72
10.3.15 Cabletron Repeater Interface Group.......................10-74
10.3.16 Cabletron Repeater Interface Group.......................10-74
10.3.17 Cabletron Protocol Group........................................10-76

Contents
viii ATX MIB Reference Guide
10.3.18 Cabletron IPX Group ...............................................10-81
10.3.18.1 SIPXIF Table........................................10-81
10.3.18.2 Route Table..........................................10-83
10.3.18.3 SAP Table............................................10-84
10.3.19 Router Discovery Group ..........................................10-85
10.3.20 IP Multicasting Group ..............................................10-87
10.3.20.1 IP Multicast Neighbor Table.................10-88
10.3.20.2 IP Multicast Stat Table .........................10-89
10.3.21 IP Circuit Table ........................................................10-89
10.3.22 sipNetToMedia Table...............................................10-91
10.3.23 Trunking Group........................................................10-91
10.3.24 IP Multicast Route....................................................10-94
10.3.24.1 IPM Route Next Hop Table ..................10-96
10.3.24.2 IPM Route Interface Table ...................10-97
10.3.25 IGMP Interface.........................................................10-98
10.4 AppleTalk Group....................................................................10-100
CHAPTER 11 TRAPS
11.1 Generic Traps ............................................................................11-1
11.2 Priority 0 Traps...........................................................................11-2
11.3 Priority 1 Traps...........................................................................11-3
11.4 Priority 2 Traps...........................................................................11-8
APPENDIX A PACKETTRANSLATION PROCEDURE

ATX MIB Reference Guide 1-1
CHAPTER 1
INTRODUCTION
This manual is for system administrators responsible for configuring, monitoring,
and maintaining the ATX. Much of the configuration of the ATX 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
unit.You should use this manual with the ATX 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 ATX 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, Token Ring MIB , describes the Token Ring MIB variables.
• Chapter 5, FDDI MIB , describes the FDDI MIB variables.
• Chapter 6, Bridge MIB , describes the Bridge MIB variables.
• Chapter 7, Repeater MIB , describes the Repeater MIB variables.
• Chapter 8, PPP MIB , describes the PPP link control and IP table MIB
variables.
• Chapter 9, AppleTalk MIB , describes the AppleTalk MIB variables.
• Chapter 10, Cabletron MIB , describes the Cabletron enterprise MIB
variables.
• Chapter 11, Traps , describes generic and enterprise-specific traps.
• AppendixA, PacketTranslation Procedure , describes the canonical format
the ATX uses for translating packets.

Chapter 1: Introduction
1-2 ATX MIB Reference Guide
1.1 DOCUMENT CONVENTIONS
The following conventions are used in presenting information in this manual:
LCM commands, prompts, and information displayed by the computer appear in
Courier typeface.
NOTE
Note symbol. Calls the reader’s attention to any item of
information that may be of special importance.
TIP
Tip symbol. Conveys helpful hints concerning procedures or
actions.
!
CAUTION
Caution symbol. Contains information essential to avoid
damage to the equipment.
Warning symbol.Warns against an action that could result in
equipment damage, personal injury or death.

Related Documentation
ATX MIB Reference Guide 1-3
1.2 RELATED DOCUMENTATION
You may need to refer to the following documentation:
• ATX User Guide – contains installation, configuration, and management
instructions for the ATX. It also describes how to use the Local Console
Manager (LCM), which is a non-intelligent terminal interface to the unit.
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 ATX.
This is relevant for a unit runningVersion 1.0 software. The NMS communicates
with the ATX 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 unit.
1.3 GETTING HELP
If you need additional support related to this device, or if you have any questions,
comments, or suggestions concerning this manual, contact Cabletron Systems
Technical Support:
By phone [phone]
Monday – Friday; 8
A
.
M
. – 8
P
.
M
. Eastern Time
By CompuServe GO CTRON from any ! prompt
By Internet mail [email protected]
By FTP ctron.com (134.141.197.25)
Login anonymous
Password your email address

Chapter 1: Introduction
1-4 ATX MIB Reference Guide
1.4 SNMP PRIMITIVES
The major software interface between the NMS and ATX 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
unit 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 the unit.
• All datagrams from the unit 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.

MIB PrimitiveTypes
ATX MIB Reference Guide 1-5
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 X1 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 X1 byte Array of bytes
PhysAddress n X1 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)

Chapter 1: Introduction
1-6 ATX MIB Reference Guide
1.6 USER FUNCTIONS
The SNMP primitives may be used to accomplish the following functions:
• Obtain the unit’s current value of certain parameters - the NMS uses the
GetRequest or GetNextRequest PDU, and the unit responds with a
GetResponse PDU. If the NMS issues a GetRequest for an unsupported
parameter, the unit sends a GetResponse with a noSuchName ErrorStatus
1
.
If the NMS issues a GetNextRequest for an unsupported parameter, the unit
skips to the next object.
• Change the unit’s value of certain parameters - the NMS uses the SetRequest
PDU, and the unit responds with a GetResponse PDU. The unit will change
both its current value and its local default to be used when the unit 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 init
responds with a GetResponse PDU. For the parameters which are being
obtainedrather than changed, the NMSmust use theASN.1NULLvaluewith
the SetRequest PDU.
• Provide notification of significant events - the unit uses the Trap PDU.
The unit 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 unit returns a badValue error to the NMS; however, the unit
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 unit’s GetResponse will
update the value of the second variable binding to contain the actual contents
of the memory.
1.
If implementing the parameter is required, it might seem more reasonable to return a
GetResponse with no error and theASN.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.

NavigatingThrough the MIBTree Structure
ATX MIB Reference Guide 1-7
Many parameters are described by existing Management Information Base
(MIB) documents. The meanings of those parameters are not always
implemented exactly by the unit; instead, the parameters are treated as best as can
be correlated to the unit’s parameters. The unit’s parameters that cannot be
correlated are part of a Cabletron proprietary MIB, called:
2
sigma OBJECT IDENTIFIER = {enterprises 97}
The parameters and traps which are supported are described in the chapters that
follow.
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 unit supports.
2.
Usually, it is better to support a standard parameter in a non-standard fashion, than not
support the standard parameter at all. Deciding what constitutes an acceptable deviation is
a gray area.

Chapter 1: Introduction
1-8 ATX MIB Reference Guide
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 ATX 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
The zero at the end (.0), indicates that this is a single instance, and that only one
value can be returned. Whenever you are looking for a variable with only one
value, you must include the .0 at the end. Some variables may have multiple
values, such as an IP address and an associated port number.
......
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
Cabletron
97

NavigatingThrough the MIBTree Structure
ATX MIB Reference Guide 1-9
The Cabletron MIB is under the private enterprise MIB branch. To identify a
variable in the Cabletron MIB, you would start with the private enterprise prefix
of 1.3.6.1.4.1, and add the specific Cabletron Massachusetts ID of 97. The result,
1.3.6.1.4.1.97. , is the complete prefix for an Cabletron MIB variable.You would
then add the specific object ID to complete the MIB variable.
For example, to find the number of filters currently defined in the ATX, you
would want to get the filterCurrentCount variable in the Cabletron MIB filter
group and add it to the prefix 1.3.6.1.4.1.97. After the prefix, add the ATX group
ID {2}, the filter group ID {9}, and the filterCurrentCount ID of {2}. As stated
above, the zero {0} indicates that this variable is a single instance and only one
variable can be returned.
Table 1-2 Branches Under MIB-II
MIB-II Group Number (1.3.6.1.2.1.)
System 1
Interfaces 2
Address Translation 3
Internet Protocol (IP) 4
Internet Control Message (ICMP) 5
Transmission Control Protocol (TCP) 6
User Datagram Protocol (UDP) 7
Exterior Gateway Protocol (EGP) 8
CMIP over TCP (CMOT) 9
Transmission 10
SNMP 11
GenericIF 12
AppleTalk 13
Open Shortest Path First (OSPF) 14
Border Gateway Protocol (BGP) 15
Remote Network Monitoring (RMON) 16
Bridge 17

Chapter 1: Introduction
1-10 ATX MIB Reference Guide
The get command would look like:
get 1.3.6.1.4.1.97.2.9.2.0
At the beginning of each chapter in this Reference Guide, the prefix for each MIB
group is provided. To calculate the specific MIB variable, you add the specific
object ID to the prefix for that MIB group.
1.8 TFTP
TFTP (Trivial File Transfer Protocol, RFC 1350) is used for:
• Distribution of new software.
TFTP has no inherent security provision; however, all files have special data
encryption, and the ATX will reject files that have not been encrypted. In
addition, SNMP primitives may be used to prevent the ATX from accepting
unauthorized TFTP requests, even if the files have the special data encryption.
Refer to the description of the swdis branch of Cabletron’s private MIB for TFTP
security details.
1.8.1 Software Distribution
TFTP is used for the distribution of new software. The new software will be
automatically invoked when a ATX reboots.
New software is released in two files:
• dnld_hdr
• dnld_software
To distribute the new software to a ATX, the TFTP procedure is as follows:
1. Start TFTP on the NMS, or on any other device which can provide TFTP
services. (Typically, TFTP must be started from the same directory that
contains the files to be transferred.) TFTP must be told the IP address of the
remote host (the IP address of the ATX), and the file transfer mode (which
must be “binary”).
2. Use TFTP to retrieve all of the unit’s parameters, as descibed in a subsection
below. This step is not required, but it is recommended if you need to
back-pedal to the software that is currently being executed by the unit.
3. Tell TFTP to transfer (“put”) the first file, (dnld_hdr).
4. Wait at least three minutes, or until the unit sends the SNMP Trap described
in the swdis branch of Cabletron’s private MIB.