Cabletron Systems ELS10-26 User Manual

ELS10-26 MIB REFERENCE

GUIDE

9032244-01

Notice

NOTICE

Cabletron Systems reserves the right to make changes in speciﬁcations 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, ﬁrmware, or software described in this manual is subject to change without notice. IN NO EVENT SHALL CABLETRON SYSTEMS BE LIABLE FOR ANY 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.



Order Number: 9032244-01 September 1997

Cabletron Systems, SPECTRUM, SmartSTACK, ELS10-26TX, FEPIM, FEPIM-TX and FEPIM-FX

Cabletron Systems, Inc.

All other product names mentioned in this manual may be trademarks or registered trademarks of their respective companies.

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:

party responsible for compliance could void the user’s authority to operate the equipment.

Changes or modifications made to this device which are not e xpressly appro v ed by the

and

LANVIEW

FCC NOTICE

are registered trademarks and

are trademarks of

Printed on Recycled Paper

Notice

DOC NOTICE

This digital apparatus does not exceed the Class A 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:

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 ﬁrmware, 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. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE UNUSED PRODUCT TO THE PLACE OF PURCHASE FOR A FULL REFUND.

Before utilizing this product, carefully read this License Agreement.

Notice

CABLETRON SOFTWARE PROGRAM LICENSE

1. LICENSE

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

2. OTHER RESTRICTIONS. You may not reverse engineer, decompile, or disassemble the

Program.

3. APPLICABLE LA W. 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.

. You have the right to use only the one (1) copy of the Program provided in this

EXCLUSION OF WARRANTY AND DISCLAIMER OF LIABILITY

1. EXCLUSION OF

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 ACCOMP ANYING WRITTEN MA TERIALS, AND ANY A CCOMP ANYING 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.

WARRANTY. Except as may be specifically provided by Cabletron in

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 deﬁned 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.

iii

Notice

DECLARATION OF CONFORMITY

Application of Council Directive(s):

Manufacturer’s Name:

Manufacturer’s Address:

European Representative Name:

European Representative Address:

Conformance to Directive(s)/Product Standards:

Equipment T ype/Environment:

W e 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

89/336/EEC 73/23/EEC

Cabletron Systems, Inc. 35 Industrial Way

PO Box 5005 Rochester, NH 03867

Mr. J. Solari Cabletron Systems Limited

Nexus House, Newbury Business Park London Road, Newbury Berkshire RG13 2PZ, England

EC Directive 89/336/EEC EC Directive 73/23/EEC EN 55022 EN 50082-1 EN 60950

Networking Equipment, for use in a Commercial or Light Environment.

Industrial

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

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

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

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

vii

Contents

viii

CHAPTER 1

INTRODUCTION

This manual is for system administrators responsible for conﬁguring, monitoring, and maintaining the ELS10-26. Much of the conﬁguration 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 conﬁgure, monitor, and manage your ELS10-26. You should use this manual with the

ELS10-26 User Guide

your NMS.

The contents of each chapter are described below.

and with the documentation provided with

• Chapter 1, 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, variables.

• Chapter 3,

variables.

• Chapter 4,

• Chapter 5,

MIB variables.

• Chapter 6,

MIB variables.

• Chapter 7,

traps.

Introduction

TCP/IP MIB-II

Ethernet MIB

Bridge MIB

PPP MIB

ELS10-26 MIB

Traps

, describes generic and enterprise-speciﬁc

, provides an overview of the SNMP

, describes the standard TCP/IP MIB

, describes the standard Ethernet MIB

, describes the Bridge MIB variables.

, describes the PPP link control and IP table

, describes the Cabletron enterprise

1-1

Introduction

1.1 RELATED DOCUMENTATION

You may need to refer to the following Cabletron documentation:

•

ELS10-26 User Guide

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 ﬁnd the following books helpful:

•

Interconnections, Bridges and Routers,

•

Internetworking with TCP/IP: Principles, Protocols, and Architecture

•

The Simple Book, An Introduction to Management of TCP/IP-based internets

– contains installation, conﬁguration, and

Radia Perlman, Addison

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 conﬁgure and monitor status for the ELS10-26.

1-2

Introduction

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: (603) 332-9400

Internet mail: support@ctron.com

FTP: ctron.com (134.141.197.25)

BBS: (603) 335-3358

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

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:

Caution:

Conveys helpful hints concerning procedures or actions.

Contains information essential to avoid damage to the equipment.

1-4

Introduction

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 deﬁned 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-5

Introduction

1.5 MIB PRIMITIVE TYPES

The MIB deﬁnitions in this document may reference the primitive types that are described in the Structure and Identiﬁcation of Management Information for TCP/IP-based Internets, RFC 1155. RFC 1155 is based on the Speciﬁcation of Abstract Syntax Notation One, ASN.1. The primitive types are described in Table 1-1.

Table 1-1 Primitive Descriptions

Primitive Size Description

Enumerated Integer with possible true (1)

Boolean 1 byte

or false (2) values; note that the ASN.1 BOOLEAN primitive type is not used

BridgeID 8 bytes

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

PortID 2 bytes

TimeTicks 4 bytes

Priority and MAC address used to identify a spanning tree bridge

Array of bytes, using the same as a MAC Address

Priority and port number used to identify a spanning tree port

Max time counter with a granularity of 1/100th of a second (also known as centiseconds)

1-6

Introduction

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

ErrorStatus1. If the NMS

a GetResponse with a noSuchName 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 notiﬁcation of signiﬁcant 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.

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; howev er, leading authorities such as Marshall T. Rose (author of

The Simple Book

existing SNMP management stations do not handle NULL values correctly.

) suggest that noSuchName be returned, because many

1-7

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 speciﬁed 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 ﬁrst parameter.

• The values within the variable bindings of the returned GetResponse may reﬂect meaningful information, rather than being an exact copy of the values from the SetRequest. For example, if a SetRequest contains two variable bindings, the ﬁrst 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.

1-8

Introduction

1.7 NAVIGATING THROUGH 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 speciﬁc 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-9

Introduction

iso

org

dod

internet

mgmt

mib-2

system interfaces add trans ip

234 39

Figure 1-1 MIB Hierarchical Structure

experimental

private

enterprise

......

sigma

rdbmsMIB

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 preﬁx

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 ﬁnd 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

1-10

Introduction

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.

Table 1-2 MIB-II Group Descriptions

MIB-II Group Number (1.3.6.1.2.1.)

System 1 Interfaces 2 Address T r anslation 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

There are additional groups under MIB-II, but all groups are not supported by the ELS10-26.

1-11

Introduction

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 preﬁx of 1.3.6.1.4.1, and add the speciﬁc Cabletron ID of 97. The result, 1.3.6.1.4.1.97, is the complete preﬁx for a Cabletron MIB variable. You would then add the speciﬁc object ID to complete the MIB variable.

For example, to ﬁnd the sysID currently deﬁned in the ELS10-26, you would want to get the sysID variable in the Cabletron MIB group and add it to the preﬁx 1.3.6.1.4.97. After the preﬁx, add the Cabletron MIB, 1.1. As stated above, the zero {0} indicates that this variable is a single instance and only one variable can be returned.

The get command would look like:

get 1.3.6.1.4.1.97.1.1

At the beginning of each chapter in this Reference Guide, the preﬁx for each MIB group is provided. To calculate the speciﬁc MIB variable, you add the speciﬁc object ID to the preﬁx for that MIB group.

1-12

Introduction

1.8 TFTP

TFTP (Trivial File Transfer Protocol, RFC 1350) is used for:

• Distribution of new software.

• Bulk retrieval of all of the parameters of a ELS10-26.

• Bulk setting of all of the parameters of a ELS10-26.

TFTP has no inherent security provision; however, all ﬁles have special data encryption, and the ELS10-26 will reject ﬁles that have not been encrypted. In addition, SNMP primitives may be used to prevent the ELS10-26 from accepting unauthorized TFTP requests, even if the ﬁles have the special data encryption. Refer to the description of the sxswdis branch of Cabletron’s private MIB for TFTP security details.

Software Distribution

TFTP is used for the distribution of new software. The new software will be automatically invoked when an ELS10-26 reboots.

New software is released in two ﬁles:

• dnld_hdr

• dnld_software

To distribute the new software to an ELS10-26, 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 ELS10-26), and the file transfer mode (which must be “binary”).

2. Use TFTP to retrieve all of the ELS10-26’s parameters, as described in a subsection below. This step is not required, but it

1-13

Introduction

is recommended if you need to go back to the version of software that is currently being executed by the ELS10-26.

3. Tell TFTP to transfer (“put”) the first file, (dnld_hdr).

4. Wait one minute, or until the ELS10-26 sends the SNMP Trap described in the swdis branch of SMC’s private MIB. (The Trap will be sent when the ELS10-26 is ready for the second file, which will be somewhat shorter than three minutes.)

5. Tell TFTP to transfer the second file, (dnld_software). This transfer should take approximately one minute.

The initial one minute waiting may be omitted and this second transfer may be initiated immediately following the first transfer; however, that causes the second transfer to take approximately two minutes, and creates a slightly heavier network load during the file transfer.

Note:

If the above TFTP sequence is abnormally terminated, there is no cause for alarm, since the ELS10-26 maintains a back-up set of software, and the ELS10-26 will not use the incomplete new software.

Older versions of software may be distributed to an ELS10-26, provided that the older software is at least Version 2.3. To distribute the older software to an ELS10-26, the above TFTP procedure should be altered, with the following step being performed before the older software is distributed.

If the bulk retrieval of all of the parameters of the ELS10-26 had been performed while the ELS10-26 was executing that older software, that retrieved ﬁle should be used to do a bulk set of all parameters (as described below). Otherwise, when the older software is distributed and the ELS10-26 reboots, the older software will not understand the format of the ELS10-26’s

parameters.

1-14

Introduction

1.8.1 Retrieving All Parameters

TFTP is used for retrieval of the parameters of an ELS10-26, as follows

1. Start TFTP (as described earlier). TFTP must be told the IP

address of the remote host (i.e., the ELS10-26), and the file transfer mode (which must be “binary”).

2. Tell TFTP to retrieve (i.e., “get”) the ELS10-26’s Configuration

file (i.e., file name “config”).

3. After about ten seconds, the TFTP operation will complete.

1.8.2 Setting All Parameters

TFTP is used for bulk setting of all of the parameters of an ELS10-26, as follows:

1. Start TFTP (as described earlier). TFTP must be told the IP

address of the remote host (i.e., the IP address of the ELS10-26), and the file transfer mode (which must be “binary”).

2. Tell TFTP to send (i.e., “put”) the ELS10-26’s Configuration file

(i.e., file name “config”).

3. After about twenty seconds, the TFTP operation will complete.

The software will re-initialize all of the ELS10-26’s parameters to the factory

speciﬁed defaults.

1-15

Introduction

1.9 ADDITIONAL INTERFACES

In addition to SNMP and TFTP, the ELS10-26 employs the following protocols, as part of its software interface with an NMS:

• UDP - User Datagram Protocol, RFC 768.

• IP - Internet Protocol, RFC 791.

• ARP - Ethernet Address Resolution Protocol, RFC 826.

• RARP - Reverse Address Resolution Protocol, RFC 903. RARP is

only used when no IP addresses have been assigned to the ELS10-26.

1-16

CHAPTER 2

TCP/IP MIB-II

The ELS10-26 supports the TCP/IP MIB-II, as deﬁned by

Management Information Base for Network Management of TCP/ IP-based Internets MIB-II

March 1991. The MIB is divided into groups of parameters. The individual groups are described in the subsections below. You may want to refer to the actual TCP/IP MIB, since this document paraphrases the standard MIB in order to provide ELS10-26-related descriptions.

, RFC 1213 (K. McCloghrie, editor), dated

Note:

The MIB tree preﬁx for reaching the TCP/IP MIB-II is:

The access types of some of the TCP/IP MIB parameters have been extended from Read-Only to Read-Write. However, unless otherwise indicated, the access type of all parameters is as indicated in the standard MIB.

1.3.6.1.2.1.

2.1 SYSTEM GROUP

system {mib-2 1} The TCP/IP System Group parameters are described below.

sysDescr {system 1} DisplayString Read-Only

A textual description of the ELS10-26 is Cabletron “moduleName” Rev “FirmwareRevision” “LinkTimeandDate” i.e., Cabletron ELS10-26 Rev xx:xx:xx 03/04/97--11:30:25

sysObjectID {system 2} Object Identiﬁer Read-Only

The identiﬁer of the variable used to identify the type of entity. Cabletron’s MIB sysID parameter will have a value that indicates that it is a bridge. So sysObjectID contains the object identiﬁer of

2-1

TCP/IP MIB-II

the Cabletron MIB sysID object, i.e., {1 3 6 1 4 1 97 5 7}. Special versions of the ELS10-26, made for third-party vendors may use different values for sysID.

sysUpTime {system 3} TimeTicks Read-Only

The time, in centiseconds, since the ELS10-26 was last booted.

sysContact {system 4} DisplayString Read-Write

The name and address of the contact person for the ELS10-26.

sysName {system 5} DisplayString Read-Write

The Internet name of the contact person for the ELS10-26. The LCM prompt consists of sysName followed by “>”. (LCM is a non-intelligent terminal interface that can be used to conﬁgure and monitor status for the ELS10-26.)

sysLocation {system 6} DisplayString Read-Write

The physical location of the ELS10-26.

sysServices {system 7} Integer Read-Only

The sum of the services supported by the ELS10-26. Values include:

(2) the ELS10-26 is a bridge only

2.2 INTERFACES GROUP

interfaces {mib-2 2} The TCP/IP Interfaces Group parameters are described below.

2-2

TCP/IP MIB-II

ifNumber {interfaces 1} Integer Read-Only

The number of ports (whether alive or dead), including the UART.

ifTable {interfaces 2} Not Accessible

A list of interface entries; one per port (ifNumber in total).

ifEntry {ifTable 1} Not Accessible

A set of objects for an interface entry. The individual components are described below.

ifIndex {ifEntry 1} Integer Read-Only

The port number, beginning with 1 for the ﬁrst port. This number always matches the instance of the ifEntry. For example, {ifIndex 3} contains the value “3”.

2-3

TCP/IP MIB-II

ifDescr {ifEntry 2} DisplayString Read-Only

A textual description of the port. One of the following text strings:

• Ethernet/802.3 TP

• Network Management Port (this is the UART port)

• Fast Ethernet/802.3u TP (twisted pair connection)

• Fast Ethernet/802.3u FX (ﬁber connection)

• Fast Ethenet/802.3u T4 (2 twisted pairs, category 5)

ifType {ifEntry 3} Integer Read-Only

The type of the port, i.e., one of the following:

• (6) - ethernet-csmacd

• (23) - ppp (for the UART port).

ifMtu {ifEntry 4} Integer Read-Only

The size (in bytes) of the largest network datagram which may be sent or received on the port. This does not include the MAC header, LLC header, and FCS. For CSMA/CD ports, the Ethernet Frame Type is considered part of the MAC header, but there is no LLC header. Specifying a value of zero in a SetRequest indicates that the interface is to default to the largest MTU available for that media. The effective value is always returned in the GetResponse.

ifSpeed {ifEntry 5} Integer Read-Only

The port’s estimated MAC-level bandwidth, in bits per second. The bandwidth will be in the range 1,200 - 100,000,000.

2-4

+ 140 hidden pages