Introduction. Cabletron Systems ELS10 -26, ELS10-26, SmartSTACK 10 ELS10-26
Below you will find brief information for Network Switch ELS10 ELS10-26. This MIB Reference Guide helps system administrators configure, monitor, and maintain the ELS10-26 network switch using an SNMP-based network management station. It details SNMP MIB variables for configuration, monitoring, and management, complementing the ELS10-26 User Guide.
Advertisement
Advertisement
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-1
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,
Wesley © 1992.
Radia Perlman, Addison
• 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.
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:
Internet mail:
(603) 332-9400 [email protected]
FTP: ctron.com (134.141.197.25)
Login: anonymous
Password: your email address
BBS:
Modem setting:
(603) 335-3358
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: Conveys helpful hints concerning procedures or actions.
Caution: 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 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-5
Introduction
1.5 MIB PRIMITIVE TYPES
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.
Primitive
Counter
DisplayString
Gauge
Integer
IpAddress
MacAddress
OctetString
PhysAddress
PortID
TimeTicks
Table 1-1 Primitive Descriptions
Size
4 bytes max n X 1 byte
4 bytes
4 bytes max
4 bytes
6 bytes n X 1 byte n X 1 byte
2 bytes
4 bytes
Description
Enumerated Integer with possible true (1) or false (2) values; note that the ASN.1
BOOLEAN primitive type is not used
Priority and MAC address used to identify a spanning tree bridge
Unsigned value
Array of printable ascii characters
Non-negative integer
Signed value
Internet address
Ethernet address
Array of bytes
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 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-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 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.
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 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-9
Introduction iso
1 org
3 dod
6 internet
1 mgmt
2 mib-2
1 experimental
3 private
4 enterprise
1 sigma
97 system
1 interfaces
2 add trans
3 ip
4
Figure 1-1 MIB Hierarchical Structure
......
rdbmsMIB
39
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
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.
MIB-II Group
Table 1-2 MIB-II Group Descriptions
Number (1.3.6.1.2.1.)
System
Interfaces
Address Translation
Internet Protocol (IP)
Internet Control Message (ICMP)
Transmission Control Protocol (TCP)
User Datagram Protocol (UDP)
Exterior Gateway Protocol (EGP)
CMIP over TCP (CMOT)
Transmission
SNMP
GenericIF
AppleTalk
Open Shortest Path First (OSPF)
Border Gateway Protocol (BGP)
Remote Network Monitoring (RMON) 16
Bridge 17
8
9
10
11
12
13
14
15
6
7
4
5
1
2
3
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 prefix of 1.3.6.1.4.1, and add the specific
Cabletron ID of 97. The result, 1.3.6.1.4.1.97, is the complete prefix for a Cabletron MIB variable. You would then add the specific object ID to complete the MIB variable.
For example, to find the sysID currently defined in the ELS10-26, you would want to get the sysID variable in the Cabletron MIB group and add it to the prefix 1.3.6.1.4.97. After the prefix, 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 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-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 files have special data encryption, and the ELS10-26 will reject files 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 files 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 files:
• 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 file 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.
2
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.
2.
The software will re-initialize all of the ELS10-26’s parameters to the factory specified 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

Public link updated
The public link to your chat has been updated.
Advertisement
Key features
- SNMP-based management
- TCP/IP MIB-II support
- Ethernet MIB support
- Bridge MIB support
- PPP MIB support
- Cabletron enterprise MIB variables
- TFTP software distribution
- Detailed trap descriptions