Cabletron Systems ELS10-26 manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170

Go to page of

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Cabletron Systems ELS10-26, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Cabletron Systems ELS10-26 one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of Cabletron Systems ELS10-26. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of Cabletron Systems ELS10-26 should contain:
- informations concerning technical data of Cabletron Systems ELS10-26
- name of the manufacturer and a year of construction of the Cabletron Systems ELS10-26 item
- rules of operation, control and maintenance of the Cabletron Systems ELS10-26 item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Cabletron Systems ELS10-26 alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Cabletron Systems ELS10-26, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Cabletron Systems service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Cabletron Systems ELS10-26.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the Cabletron Systems ELS10-26 item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

    ELS10-26 MIB REFERENCE GUIDE 9032244-01[...]

  • Page 2

    [...]

  • Page 3

    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 ha ve been made. The hardware, firmware, or software described in this manual is subject to cha[...]

  • Page 4

    Notice ii 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éri[...]

  • Page 5

    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. Y ou may not copy , reproduce or transmit any part of the Program except as permitted by the Copyright Act of the United States or as author[...]

  • Page 6

    Notice iv DECLARATION OF CONFORMITY Application of Council Directiv e(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 Representativ e Name: Mr. J. Solari European Representativ e Address: Cabletron Systems Limited Nexus House, Newbury Busi[...]

  • Page 7

    v T ABLE OF CONTENTS Chapter 1 Intr oduction 1.1 Related Documentation ................................................... 1-2 1.2 Getting Help .................................................................... 1-3 1.3 Document Conventions ................................................... 1-4 1.4 SNMP Primitives ................................[...]

  • Page 8

    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 ..............................[...]

  • Page 9

    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[...]

  • Page 10

    viii Contents[...]

  • Page 11

    1-1 CHAPTER 1 INTR ODUCTION 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 configur e, monitor , and manage your EL[...]

  • Page 12

    1-2 Introduction 1.1 RELATED DOCUMENTATION Y ou may need to r efer 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 [...]

  • Page 13

    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: (603) 332-9400 Internet mail: support@ctron.com FTP: ctron.com (134.141.197.25) Login: anonymous Password: your email address BB[...]

  • Page 14

    1-4 Introduction 1.3 DOCUMENT CON VENTIONS The following conventions are used thr oughout 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 Inf[...]

  • Page 15

    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 1 157) datagrams over any available physical media. The following restrictions apply: • All datagrams must obey SNMP format. • All datagrams must be sen[...]

  • Page 16

    1-6 Introduction 1.5 MIB PRIMITIVE T YPES The MIB definitions in this document may refer ence the primitive types that are described in the Str ucture and Identification of Management Information for TCP/IP-based Internets, RFC 1 155. RFC 1 155 is based on the Specification of Abstract Syntax Notation One, ASN.1. The primitive types are describe[...]

  • Page 17

    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 s[...]

  • Page 18

    1-8 Introduction The ELS10-26 implements two non-standard featur es 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 retur[...]

  • Page 19

    Introduction 1-9 1.7 NAVIGATING THROUGH THE MIBT REE STRUCTURE The MIB structur e is a hierarchical tr ee structure. Each MIB variable has a numeric value that indicates its place in the hierarchy . The structure was originally cr eated, and is still maintained by the International Organization for Standar dization (ISO) and the International T ele[...]

  • Page 20

    1-10 Introduction Figure 1-1 MIB Hierar chical Structure T able 1-2 pr ovides the branch structur e that is under MIB-II. T o reach any of the MIB-II objects you would start with the pr efix 1.3.6.1.2.1. For example, to reach an object in the system gr oup, you would start with 1.3.6.1.2.1.1. T o find the amount of time the ELS10-26 had been runn[...]

  • Page 21

    Introduction 1-11 The zero at the end (.0), indicates that this is a single instance, and that only one value can be returned. Whenever you ar e 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 addr ess and an associated port number . T able 1-2 MIB-II Group Descr[...]

  • Page 22

    1-12 Introduction The Cabletron MIB is under the private enterprise MIB branch. T o 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 r esult, 1.3.6.1.4.1.97, is the complete prefix for a Cabletron MIB variable. Y ou would then add the speci?[...]

  • Page 23

    Introduction 1-13 1.8 TFTP TFTP (T rivial File T ransfer 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 inher ent security provision; however , all files have special data encryption, and the ELS10-26 [...]

  • Page 24

    1-14 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 ELS1[...]

  • Page 25

    Introduction 1-15 1.8.1 Retrieving All P arameters TFTP is used for r etrieval 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[...]

  • Page 26

    1-16 Introduction 1.9 ADDITIONAL INTERFACES In addition to SNMP and TFTP , the ELS10-26 employs the following protocols, as part of its softwar e interface with an NMS: • UDP - User Datagram Pr otocol, RFC 768. • IP - Internet Pr otocol, RFC 791. • ARP - Ethernet Address Resolution Pr otocol, RFC 826. • RARP - Reverse Address Resolution Pr [...]

  • Page 27

    2-1 CHAPTER 2 TCP/IP MIB-II The ELS10-26 supports the TCP/IP MIB-II, as defined by Management Information Base for Network Management of TCP/ IP-based Internets MIB-II , RFC 1213 (K. McCloghrie, editor), dated March 1991. The MIB is divided into gr oups of parameters. The individual groups ar e described in the subsections below . Y ou may want to[...]

  • Page 28

    2-2 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 differ ent values for sysID. sysUpT ime {system 3} T imeT icks Read-Only The time, in centiseconds, since the ELS10-26 was last booted. sysContact {system 4} DisplayString Read-W rite The name and addr[...]

  • Page 29

    TCP/IP MIB-II 2-3 ifNumber {interfaces 1} Integer Read-Only The number of ports (whether alive or dead), including the UAR T . ifT able {interfaces 2} Not Accessible A list of interface entries; one per port (ifNumber in total). ifEntry {ifT able 1} Not Accessible A set of objects for an interface entry . The individual components are described bel[...]

  • Page 30

    2-4 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 UAR T port) • Fast Ethernet/802.3u TP (twisted pair connection) • Fast Ethernet/802.3u FX (fiber connection) • Fast Ethenet/802.3u T4 (2 twisted pai[...]

  • Page 31

    TCP/IP MIB-II 2-5 ifPhysAddress {ifEntry 6} Physical Address Read-W rite 1 The MAC address of the port. For the UAR T port, this field should be an octet string of zero length. ifAdminStatus {ifEntry 7} Integer Read-W rite The desired state of the port, i.e., one of the following: • up (1) - setting the port’s state to up causes the port’s s[...]

  • Page 32

    2-6 TCP/IP MIB-II ifInOctets {ifEntry 10} Counter Read-Only The total number of bytes received on the port, counting the MAC header and FCS, but not counting the bytes in packets that were rejected due to har dware errors. All counters are 32-bit wide wrap-around counters which can only be reset by restarting the port or by rebooting the ELS10-26. [...]

  • Page 33

    TCP/IP MIB-II 2-7 ifOutOctets {ifEntry 16} Counter Read-Only The total number of bytes transmitted out the port, counting the MAC header and FCS. ifOutUcastPkts {ifEntry 17} Counter Read-Only The number of non-multicast packets transmitted out the port, regar dless of whether or not hardware transmission err ors were encountered. ifOutNUcastPkts {i[...]

  • Page 34

    2-8 TCP/IP MIB-II ifOutQLen {ifEntry 21} Gauge Read-Only The maximum length ever obtained by the port’s outbound packet queue (in packets) is not available, so this value is always one. ifSpecific {ifEntry 22} Object Identifier Read-Only The object identifier of the MIB for the type of port, i.e., one of the following: {dot3} for Ethernet port[...]

  • Page 35

    TCP/IP MIB-II 2-9 atT able {at 1} Not Accessible atEntry {atT able 1} Not Accessible atIfIndex {atEntry 1} Integer Read-W rite All GetResponse PDUs indicate a noSuchName ErrorStatus. atPhysAddress {atEntry 2} Physical Address Read-W rite All GetResponse PDUs indicate a noSuchName ErrorStatus. atNetAddress {atEntry 3} Network Address Read-W rite All[...]

  • Page 36

    2-10 TCP/IP MIB-II ipInReceives {ip 3} Counter Read-Only The total number of IP packets r eceived from all ports (including the UAR T). ipInHdrErrors {ip 4} Counter Read-Only The number of packets received that wer e discarded due to errors in the IP header . ipInAddrErrors {ip 5} Counter Read-Only The number of packets received that wer e discarde[...]

  • Page 37

    TCP/IP MIB-II 2-11 ipInDelivers {ip 9} Counter Read-Only The total number of input packets successfully delivered to the IP user-pr otocol layers. ipOutRequests {ip 10} Counter Read-Only The total number of IP output packets generated by this ELS10-26. This count does not include any packets repr esented in ipForwDatagrams. ipOutDiscards {ip 1 1} C[...]

  • Page 38

    2-12 TCP/IP MIB-II ipReasmOKs {ip 15} Counter Read-Only The number of IP datagrams which wer e successfully reassembled. ipReasmFails {ip 16} Counter Read-Only The number of failures (for whatever r eason timed-out, errors, etc.) detected by the IP r eassembly algorithm. This is not necessarily a count of discarded IP fragments since some algorithm[...]

  • Page 39

    TCP/IP MIB-II 2-13 ipAddrT able {ip 20} Not Accessible A list of IP addr ess entries; one per IP address. If a port has not yet learned its IP addr ess, then an ipAddrEntry might not exist for the port (i.e., having an ipAddrEntry with an IP addr ess of zero is not acceptable). ipAddrEntry {ipAddrT able 1} Not Accessible A set of objects for an ipA[...]

  • Page 40

    2-14 TCP/IP MIB-II ipAdEntReasmMaxSize {ipAddrEntry 5} Integer Read-Only The largest IP datagram which can be reassembled, i.e., the constant 4470. 2.4.2 IP Routing T able The TCP/IP IP routing table contains the routing information for each route curr ently known by the ELS10-26. When adding a row , the entire r ow must be specified, except for t[...]

  • Page 41

    TCP/IP MIB-II 2-15 for the same IP addr ess, then only the entry being used by the IP forwarding pr ocess is available for SNMP access. ipRouteEntry {ipRouteT able 1} Not Accessible A set of objects for an ipRouteT able entry . The individual components are described below . ipRouteDest {ipRouteEntry 1} IP Addr ess Read-W rite The destination IP ad[...]

  • Page 42

    2-16 TCP/IP MIB-II ipRouteNextHop {ipRouteEntry 7} IP Addr ess Read-W rite The IP addr ess of the route’s next hop. ipRouteT ype {ipRouteEntry 8} Integer Read-W rite The type of the route, one of the following: • other (1) - none of the below . • invalid (2) - the entry should be considered to be non-existent. • direct (3) - the entry is a [...]

  • Page 43

    TCP/IP MIB-II 2-17 ipRouteInfo {ipRouteEntry 13} Object Identifier Read-W rite A refer ence to additional MIB definitions, specific to the routing protocol which is r esponsible for this route. This information is not present in the ELS10-26, so ipRouteInfo should be set to the object identifier {0 0}. 2.4.3 IP Address T ranslation T able The T[...]

  • Page 44

    2-18 TCP/IP MIB-II ipNetT oMediaEntry {ipNetT oMediaT able 1} Not Accessible A set of objects for an ipNetT oMediaT able entry . The individual components are described below . ipNetT oMediaIfIndex {ipNetT oMediaEntry 1} Integer Read-W rite The port number for which this entry is effective. ipNetT oMediaPhysAddr ess {ipNetT oMediaEntry 2} Physical [...]

  • Page 45

    TCP/IP MIB-II 2-19 ipRoutingDiscards {ip 23} Counter Read-Only The number of valid routing entries that wer e discarded. 2.5 ICMP GROUP icmp {mib-2 5} The TCP/IP ICMP Group parameters are described below . icmpInMsgs {icmp 1} Counter Read-Only The total number of ICMP messages which wer e received by this ELS10-26. This includes all messages repr e[...]

  • Page 46

    2-20 TCP/IP MIB-II icmpInSrcQuenchs {icmp 6} Counter Read-Only The number of ICMP “Sour ce Quench” messages received. icmpInRedirects {icmp 7} Counter Read-Only The number of ICMP “Redir ect” messages received. icmpInEchos {icmp 8} Counter Read-Only The number of ICMP “Echo (r equest)” messages received. icmpInEchoReps {icmp 9} Counter [...]

  • Page 47

    TCP/IP MIB-II 2-21 icmpOutMsgs {icmp 14} Counter Read-Only The total number of ICMP messages which wer e sent by this ELS10-26. This includes all messages counted by icmpOutErrors. icmpOutErrors {icmp 15} Counter Read-Only The number of ICMP messages which this ELS10-26 did not send due to problems discover ed entirely within the ICMP subsystem (su[...]

  • Page 48

    2-22 TCP/IP MIB-II icmpOutEchoReps {icmp 22} Counter Read-Only The number of ICMP “Echo Reply” messages sent. icmpOutT imestamps {icmp 23} Counter Read-Only The number of ICMP “T imestamp (request)” messages sent. icmpOutT imestampReps {icmp 24} Counter Read-Only The number of ICMP “T imestamp Reply” messages sent. icmpOutAddrMasks {icm[...]

  • Page 49

    TCP/IP MIB-II 2-23 udpInDatagrams {udp 1} Counter Read-Only The total number of UDP datagrams deliver ed to UDP users. udpNoPorts {udp 2} Counter Read-Only The total number of received UDP datagrams for which there was no application at the destination port. udpInErrors {udp 3} Counter Read-Only The number of received UDP datagrams that could not b[...]

  • Page 50

    2-24 TCP/IP MIB-II udpLocalAddress {udpEntry 1} IP Addr ess Read-Only The all zeroes IP address (0.0.0.0), which indicates that the UDP listener is willing to accept UDP datagrams for any IP address associated with the ELS10-26. udpLocalPort {udpEntry 2} Integer Read-Only The UDP port number , i.e., one of 69, 161, and 520. Note that reception of S[...]

  • Page 51

    TCP/IP MIB-II 2-25 2.11 SNMP MANAGEMENT GROUP snmp {mib-2 1 1} The TCP/IP SNMP Group parameters are described below . snmpInPkts {snmp 1} Counter Read-Only The number of SNMP PDUs r eceived by the ELS10-26. snmpOutPkts {snmp 2} Counter Read-Only The number of SNMP PDUs cr eated by the ELS10-26. snmpInBadV ersions {snmp 3} Counter Read-Only The numb[...]

  • Page 52

    2-26 TCP/IP MIB-II snmpInBadT ypes {snmp 7} Counter Read-Only All GetResponse PDUs indicate a noSuchName ErrorStatus, since this variable is no longer used. snmpInT ooBigs {snmp 8} Counter Read-Only Always zero, since the ELS10-26 ignor es all SNMP response PDUs. snmpInNoSuchNames {snmp 9} Counter Read-Only Always zero, since the ELS10-26 ignor es [...]

  • Page 53

    TCP/IP MIB-II 2-27 snmpInT otalSetV ars {snmp 14} Counter Read-Only The total number of MIB objects which have been successfully altered by the ELS10-26 as a r esult of SNMP SetRequest PDUs. snmpInGetRequests {snmp 15} Counter Read-Only The total number of SNMP GetRequest PDUs r eceived by the ELS10-26, which have been processed with no err ors. sn[...]

  • Page 54

    2-28 TCP/IP MIB-II snmpOutNoSuchNames {snmp 21} Counter Read-Only The total number of SNMP PDUs cr eated by the ELS10-26, with a value of “noSuchName” in the PDU’s “ErrorStatus”. snmpOutBadV alues {snmp 22} Counter Read-Only The total number of SNMP PDUs cr eated by the ELS10-26, with a value of “badV alue” in the PDU’s “Err orSta[...]

  • Page 55

    TCP/IP MIB-II 2-29 snmpOutGetResponses {snmp 28} Counter Read-Only The total number of SNMP GetResponse PDUs cr eated by the ELS10-26. snmpOutT raps {snmp 29} Counter Read-Only The total number of SNMP T rap PDUs created by the ELS10-26. snmpEnableAuthenT raps {snmp 30} Integer Read-W rite Whether authentication failures should cause the ELS10-26 t[...]

  • Page 56

    2-30 TCP/IP MIB-II ctIfNumber {ctIfEntry 1} This defines the interface that is being described. This is the same as IfIndex. SYNT AX INTEGER ACCESS read-only ST A TUS mandatory ctIfPortCnt {ctIfEntry 2} This defines the number of ports on the interface that are being described. SYNT AX INTEGER ACCESS read-only ST A TUS mandatory ctIfConnectionT y[...]

  • Page 57

    TCP/IP MIB-II 2-31 interface has been closed and then opened again. A read of ctIfLAA will always return the same values as IfPhysAddr ess, except in the case where; o ctIfLAA has been set, but interface has not yet been closed and reopened, in this case the last set value is returned. Note that a r ead of IfPhysAddress will always return the physi[...]

  • Page 58

    2-32 TCP/IP MIB-II SYNT AX INTEGER {other (1), standard (2), fullDuplex (3), fastEthernet (4)} ACCESS read-only ST A TUS mandatory OBJECT IDENTIFIER: 1.3.6.1.4.1.52.4.3.3.2.1.1.6 The OID will actually be 1.3.6.1.4.1.52.4.3.3.2.1.1.6.X where X is the interface number (port number) requested. It will r eport fullDuplex (3) on our ethernet ports, and [...]

  • Page 59

    TCP/IP MIB-II 2-33 ctIfPortPortNumber ctIfPortPortNumber {ctIfPortEntry 1} This defines the port that is being described. SYNT AX INTEGER ACCESS read-only ST A TUS mandatory OBJECT IDENTIFIER: 1.3.6.1.4.1.52.4.3.3.3.1.1.1 The OID will actually be 1.3.6.1.4.1.52.4.3.3.3.1.1.1.X.Y wher e X is the interface number and Y is the port requested. X will [...]

  • Page 60

    2-34 TCP/IP MIB-II ctIfPortT ype {ctIfPortEntry 3} DESCRIPTION This defines the specific type of port (EPIM, TPIM). This is defined within ctron-oids. SYNT AX OBJECT IDENTIFIER ACCESS read-only ST A TUS mandatory OBJECT IDENTIFIER: 1.3.6.1.4.1.52.4.3.3.3.1.1.3 The OID will actually be 1.3.6.1.4.1.52.4.3.3.3.1.1.1.X.Y wher e X is the interface nu[...]

  • Page 61

    TCP/IP MIB-II 2-35 2.14 CABLETR ON COM PORT CONFIGURATION GROUP ctCpT able {ctIfCp 1} This table defines a Com Port T able. SYNT AX SEQUENCE OF ctCPEntry ACCESS not accessible ST A TUS mandatory OBJECT IDENTIFIER: 1.3.6.1.4.1.52.4.3.3.4.1 ctCpEntry {ctCpT able 1} This defines each conceptual row within the ctCpT able. SYNT AX ctCpEntry ACCESS not[...]

  • Page 62

    2-36 TCP/IP MIB-II ctCpFunction {ctCpEntry 2} DESCRIPTION This defines the Com Port Function supported by that Com Port. SYNT AX INTEGER {lm(1), ups(2), slip(3), ppp(4)} ACCESS read-write ST A TUS mandatory OBJECT IDENTIFIER: 1.3.6.1.4.1.52.4.3.3.4.1.1.2 The OID will actually be 1.3.6.1.4.1.52.4.3.3.4.1.1.2.1 because there is only one UAR T port. [...]

  • Page 63

    TCP/IP MIB-II 2-37 ctCpAdminStatus {ctCpEntry 4} DESCRIPTION The administrative state of the Com Port. SYNT AX INTEGER {disabled(1), enabled(2)} ACCESS read-only ST A TUS mandatory OBJECT IDENTIFIER: 1.3.6.1.4.1.52.4.3.3.4.1.1.4 The OID will actually be 1.3.6.1.4.1.52.4.3.3.4.1.1.4.1 because we only have the one UAR T port. W e don’t allow this p[...]

  • Page 64

    2-38 TCP/IP MIB-II ST A TUS mandatory 2.16 T RAP DESCRIPTION InterfacePortInsertion Not Supported. Specific T rap T ype Code - 0x1A0 This trap will be generated when it is detected that an interface port has been inserted. The information will include: ctIfNumber {ctIfEntry 1} ctIfPortNumber {ctIfPortEntry 1} ctPortT ype {ctIfPortEntry 3} Specifi[...]

  • Page 65

    TCP/IP MIB-II 2-39 InterfacePortLinkDown Specific T rap T ype Code - 0x1A3 This trap will be generated when a previously attached bridging port has been disconnected from a LAN. This is only appr opriate for ports that support the concept of a link state. The information will include: ctIfNumber {ctIfEntry 1} ctIfPortPortNumber {ctIfPortEntry 1} T[...]

  • Page 66

    2-40 TCP/IP MIB-II This MIB defines Cabletron extensions to MIB-II. Gr oups within this MIB refer to the gr oup in which the objects pertain within MIB-II. Groups within this MIB ar e: commonDevOBJECT IDENTIFIER {ctronMib2 1} ctIfPortOBJECT IDENTIFIER {ctronMib2 2} ctIfPortOBJECT IDENTIFIER {ctronMib2 3} ctIfCpOBJECT IDENTIFIER {ctronMib2 4} ctSNM[...]

  • Page 67

    TCP/IP MIB-II 2-41 OBJECT -TYPE SYNT AX DisplayString(SIZE (8)) ACCESS read-write ST A TUS mandatory DESCRIPTION The current date, as measur ed by the device. The repr esentation shall use the standard MMDDYY format. ::= {commonDev 2} comDeviceBoardMap OBJECT -TYPE SYNT AXINTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION Contains a bit encode[...]

  • Page 68

    2-42 TCP/IP MIB-II ::= {ctIf 1} ctIfEntry OBJECT -TYPE SYNT AXCtIfEntry ACCESS not accessible ST A TUS mandatory DESCRIPTION This defines each conceptual row within the ctIfT able. INDEX {ctIfNumber} ::= {ctIfT able 1} CtIfEntry::= SEQUENCE {ctIfNumber INTEGER, ctIfPortCnt INTEGER, ctIfConnectionT ype OBJECT IDENTIFIER, ctIfLAA OCTET STRING, ctIfD[...]

  • Page 69

    TCP/IP MIB-II 2-43 ::= {ctIfEntry 1} ctIfPortCnt OBJECT -TYPE SYNT AXINTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION This defines the number of ports on the interface that is being described. INDEX {ctIfNumber} ::= {ctIfEntry 2} ctIfConnectionT ype OBJECT -TYPE SYNT AXOBJECTIDENTIFIER ACCESS read-only ST A TUS mandatory DESCRIPTION Define[...]

  • Page 70

    2-44 TCP/IP MIB-II ST A TUS mandatory DESCRIPTION This object is used by a device (with a T oken Ring interface) to set a Locally Administered Addr ess (LAA) for its MAC hardwar e address. When set, this LAA will override the default Universally Administered Address or burned-in address of the interface. For devices that do not support LAA: a read [...]

  • Page 71

    TCP/IP MIB-II 2-45 ST A TUS mandatory DESCRIPTION Defines the specific type of interface connection (BRIM etc.). Defines the duplex mode in which the interface is set to operate. For devices that do not support this capability: a read will r eturn standard (2). any write attempt will return BADV ALUE. fast ethernet devices will report other (1).[...]

  • Page 72

    2-46 TCP/IP MIB-II DESCRIPTION Defines whether or not an interface supports redundancy . ::= {ctIfEntry 7} ctIfPort group implementation of this gr oup is optional The ctIfPort group contains information about the type of port on the interface i.e., the type of EPIM,TPIM etc. This information is not available in the interface group of MIB-II. ctIf[...]

  • Page 73

    TCP/IP MIB-II 2-47 ::= {ctIfPortT able 1} ctIfPortEntry::= SEQUENCE {ctIfPortPortNumber INTEGER, ctIfPortIfNumber INTEGER, ctIfPortT ype OBJECT IDENTIFIER, ctIfPortLinkStatus INTEGER} ctIfPortPortNumber OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION This defines the port being described. ::= {ctIfPortEntry 1} ctIfPort[...]

  • Page 74

    2-48 TCP/IP MIB-II ::= {ctIfPortEntry 2} ctIfPortT ype OBJECT -TYPE SYNT AX OBJECT IDENTIFIER ACCESS read-only ST A TUS mandatory DESCRIPTION Defines the specific type of the port (EPIM,TPIM). This is defined within ctron oids. ::= {ctIfPortEntry 3} ctIfPortLinkStatus OBJECT -TYPE SYNT AX INTEGER {not linked (1), linked (2), notAppli- cable (3).[...]

  • Page 75

    TCP/IP MIB-II 2-49 ACCESS not accessible ST A TUS mandatory DESCRIPTION This table defines a Com Port T able. ::= {ctIfCp 1} ctCpEntry OBJECT -TYPE SYNT AX CtCpEntry ACCESS not accessible ST A TUS mandatory DESCRIPTION This defines each conceptual row within the ctCpT able. INDEX {ctComPort} ::= {ctCpT able 1} ctCpEntry::= SEQUENCE {ctComPort INT[...]

  • Page 76

    2-50 TCP/IP MIB-II is being described. com1 = 1, com2 = 2 {ctCpEntry 1} ctCpFunction OBJECT -TYPE SYNT AXINTEGER {lm(1), Local Management (default), ups (2) UPS, slip (3) SLIP , ppp (4) PPP} ACCESS read-write ST A TUS mandatory DESCRIPTION Defines the Com Port Function sup- ported by that Com Port. {ctCpEntry 2} ctIfNum OBJECT -TYPE SYNT AXINTEGER[...]

  • Page 77

    TCP/IP MIB-II 2-51 ST A TUS mandatory DESCRIPTION The administrative state of the Com Port. {ctCpEntry 4} The SNMP gr oup. Implementation of this group is mandatory when the SNMPv2 protocol is pr esent within the device. enableSNMPv1 OBJECT -TYPE SYNT AXINTEGER {disable (1), enable (2)} ACCESS read-write ST A TUS mandatory DESCRIPTION This object a[...]

  • Page 78

    2-52 TCP/IP MIB-II {ctSNMP 2} {ctSNMP 3} is obsolete The ctSonet group is an optional gr oup. It contains information pertaining to the optical connectivity speed. ctSonetEntry OBJECT -TYPE SYNT AXSEQUENCEOF CtSonetEntry ACCESS not accessible ST A TUS mandatory DESCRIPTION This table defines the Sonet table. INDEX {ctSonetIfIndex} {ctSonetT able 1[...]

  • Page 79

    TCP/IP MIB-II 2-53 {ctSonetEntry 1} ctSonetMediumT ype OBJECT -TYPE SYNT AX INTEGER {sonet (1), sdh (2)} ACCESS read-write ST A TUS mandatory DESCRIPTION This variable identifies whether a SONET or an SDH signal is used across this interface. {ctSonetEntry 2} T rap description InterfacePortInsertion Specific T rap T ype Code- 0x1A0 This trap will[...]

  • Page 80

    2-54 TCP/IP MIB-II Specific T rap T ype Code - 0x1A2 This trap will be generated when it is determined that a port on a strictly bridging interface (not a “repeater”) has been connected to a LAN. This is only appropriate for ports that support the concept of a link state. The interesting information will include: ctIfNumber {ctIfEntry 1}, ctIf[...]

  • Page 81

    3-1 CHAPTER 3 ETHERNET MIB The ELS10-26 supports the Ethernet MIB as defined in Definitions of Managed Objects for the Ethernet-like Interface T ypes , RFC 1284 (J. Cook, editor), dated December 1991. The MIB tree pr efix for reaching the GenericIF group is: 1.3.6.1.2.1.12. 3.1 GENERIC ETHERNET-LIKE GROUP dot3T able {dot3 1} Not Accessible A lis[...]

  • Page 82

    3-2 Ether net MIB dot3MACSubLayerStatus {dot3Entry 3} Integer Read-W rite T reated identically to dot3InitializeMAC. V alues include: • enabled (1) • disabled (2) dot3MulticastReceiveStatus {dot3Entry 4} Integer Read-W rite Whether the port is able to receive multicasts. This is always enabled when the port is enabled, and always disabled when [...]

  • Page 83

    Ether net MIB 3-3 dot3StatsT able {dot3 2} Not Accessible A list of interface entries; one per Ethernet port, which correspond to the dot3T able entries. dot3StatsEntry {dot3StatsT able 1} Not Accessible A set of statistics for an Ethernet entry . The individual components are described below . dot3StatsIndex {dot3StatsEntry 1} Integer Read-Only Th[...]

  • Page 84

    3-4 Ether net MIB dot3StatsSQET estErr ors {dot3StatsEntry 6} Counter Read-Only The number of times an SQE failure (i.e., heartbeat lost) occurr ed, since the port was last enabled. dot3StatsDeferredT ransmissions {dot3StatsEntry 7} Counter Read-Only The number of frames for which the first transmission attempt was successful, but delayed because [...]

  • Page 85

    Ether net MIB 3-5 dot3StatsExcessiveDeferrals {dot3StatsEntry 12} Counter Read-Only The number of times that transmission was deferred for an excessive period of time. dot3StatsFrameT ooLongs {dot3StatsEntry 13} Counter Read-Only The number of times a received packet was too long, since the port was last enabled. dot3StatsInRangeLengthErrors {dot3S[...]

  • Page 86

    3-6 Ether net MIB 3.4 ETHERNET-LIKE T ESTS GR OUP dot3T ests {{dot3 6} There ar e no MIB variables in this group. 3.5 ETHERNET-LIKE ERROR S GROUP dot3Errors {dot3 7} There ar e no MIB variables in this group. 3.6 ETHERNET-LIKE CHIPSETS GROUP dot3ChipSets {dot3 8} There ar e no MIB variables in this group.[...]

  • Page 87

    4-1 CHAPTER 4 BRIDGE MIB The ELS10-26 supports the Bridge MIB {mib-2 17} as defined in Definitions of Managed Objects for Bridges, RFC 1286 (Decker , Langille, Rijsinghani, and McCloghrie, editors). The MIB tree pr efix for reaching the Bridge MIB-II is: 1.3.6.1.2.1.17 4.1 BASE GROUP dot1dBase {dot1dBridge 1} dot1dBaseBridgeAddress {dot1dBase 1}[...]

  • Page 88

    4-2 Bridge MIB dot1dBaseT ype {dot1dBase 3} Integer Read-Only Indicates what type of bridging this bridge can perform. If a bridge is actually performing a certain type of bridging this will be indicated by entries in the port table for the given type. The ELS10-26 is always transparent-only (2). dot1dBasePortT able {dot1dBase 4} Not Accessible A t[...]

  • Page 89

    Bridge MIB 4-3 For example, in the case where multiple ports corr espond one-to-one with multiple X.25 virtual circuits, this value might identify an (e.g., the first) object instance associated with the X.25 virtual circuit corr esponding to this port. For a port which has a unique value of dot1dBasePortIfIndex, this object can have the value {0 [...]

  • Page 90

    4-4 Bridge MIB dot1dStpPriority {dot1dStp 2} Integer Read-W rite The value of the write-able portion of the Bridge ID, i.e., the first two octets of the (8 octet long) Bridge ID. The other (last) 6 octets of the Bridge ID are given by the value of dot1dBaseBridgeAddr ess. Any value from 0 to 65535 may be specified. dot1dStpT imeSinceT opologyChan[...]

  • Page 91

    Bridge MIB 4-5 Port number of this bridge’s current spanning tr ee root port, or 0, if this bridge is the current spanning tr ee root bridge. dot1dStpMaxAge {dot1dStp 8} Integer Read-Only The maximum age of Spanning T ree Pr otocol information learned from the network on any port befor e it is discarded, in units of hundredths of a second. This i[...]

  • Page 92

    4-6 Bridge MIB and all others would start using if/when this bridge were to become the root. dot1dStpBridgeMaxAge {dot1dStp 12} T ime T icks Read-W rite The value that all bridges use for MaxAge when this bridge is acting as the root. Note that 802.1d/D9 specifies that the range for this parameter is related to the value of dot1dStpBridgeHelloT im[...]

  • Page 93

    Bridge MIB 4-7 by 802.1d/D9 to be 1 second. An agent may return a badV alue error if a set is attempted to a value which is not a whole number of seconds. The Forward Delay T ime must be at least 4 seconds, and must adhere to the afor ementioned equation involving Max Age T ime and Forward Delay T ime. dot1dStpPortT able {dot1dStp 15} Not Accessibl[...]

  • Page 94

    4-8 Bridge MIB dot1dStpPortState {dot1dStpPortEntry 3} Integer Read-Only The port’s current state as defined by application of the Spanning T ree Pr otocol. This state controls what action a port takes on reception of a frame. If the bridge has detected a port that is malfunctioning it will place that port into the broken (6) state. For ports wh[...]

  • Page 95

    Bridge MIB 4-9 dot1dStpPortDesignatedCost {dot1dStpPortEntry 7} Integer Read-Only The path cost of the Designated Port of the segment connected to this port. This value is compared to the Root Path Cost field in received bridge PDUs. dot1dStpPortDesignatedBridge {dot1dStpPortEntry 8} Octet String Read-Only The Bridge Identifier of the bridge whic[...]

  • Page 96

    4-10 Bridge MIB dot1dTpAgingT ime {dot1dTp 2} Integer Read-W rite The timeout period in seconds for aging out dynamically learned forwarding information. dot1dTpFdbT able {dot1dTp 3} Not Accessible A table that contains information about unicast entries for which the bridge has forwarding and/or filtering information. This information is used by t[...]

  • Page 97

    Bridge MIB 4-11 dot1dTpFdbStatus {dot1dTpFdbEntry 3} Integer Read-Only The status of this entry . The meanings of the values are other (1) none of the following. This would include the case where some other MIB object (not the corresponding instance of dot1dTpFdbPort, nor an entry in the dot1dStaticT able) is being used to determine if and how fram[...]

  • Page 98

    4-12 Bridge MIB dot1dTpPortMaxInfo {dot1dTpPortEntry 2} Integer Read-Only The maximum size of the INFO (non-MAC) field that this port will receive or transmit. The type/length field (2 octets) in Ethernet/802.3 packets are considered to be part of the MAC header . dot1dTpPortInFrames {dot1dTpPortEntry 3} Counter Read-Only The number of frames tha[...]

  • Page 99

    5-1 CHAPTER 5 PPP MIB The ELS10-26 supports RFC 1471 for PPP link contr ol and RFC 1473 for PPP IP support. The MIB tree for r eaching the PPP group is: 1.3.6.1.2.1.10 ppp {transmission 23} 5.1 PPP LINK CONTROL T ABLE pppLCP {ppp 1} pppLinkStatusT able {pppLink1} Not-Accessible A table containing PPP-Link specific variables for this PPP implementa[...]

  • Page 100

    5-2 PPP MIB ifSpecific.987 would contain the OBJECT IDENTIFIER for the serial-port’s media-specific MIB. pppLinkStatusBadAddresses {pppLinkStatusEntry 2} Counter Read-only The number of packets received with an incorr ect address field. This counter is a component of the ifInErrors variable that is associated with the interface that repr esent[...]

  • Page 101

    PPP MIB 5-3 the local PPP entity . The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up). Set to 8192 for the maximum HIOM frame size. pppLinkStatusRemoteMRU {pppLinkStatusEntry 7} Integer Read-only The current value of the MRU for the r emote PPP Entity . This value is the MRU that the local enti[...]

  • Page 102

    5-4 PPP MIB • enabled (1) - supports protocol compr ession. • disabled (2) - no support for protocol compr ession. pppLinkStatusRemoteT oLocalPr otocolCompression {pppLinkStatusEntry 1 1} Integer Read-only Indicates whether the remote PPP entity will use Protocol Compression when transmitting packets to the local PPP entity . The value of this [...]

  • Page 103

    PPP MIB 5-5 entity . The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up). • enabled (1) - supports ACC map compression. • disabled (2) - no support for ACC map compression. pppLinkStatusT ransmitFcsSize {pppLinkStatusEntry 14} Integer Read-only The size of the Frame Check Sequence (FCS) in b[...]

  • Page 104

    5-6 PPP MIB pppLinkConfigInitialMRU {pppLinkConfigEntry 1} Integer Read-W rite The initial Maximum Receive Unit (MRU) that the local PPP entity will advertise to the remote entity . If the value of this variable is 0 then the local PPP entity will not advertise any MRU to the r emote entity and the default MRU will be assumed. Changes to this obj[...]

  • Page 105

    PPP MIB 5-7 pppLinkConfigMagicNumber {pppLinkConfigEntry 4} Integer Read-W rite If true (2) then the local node will attempt to perform magic number negotiation with the remote node. If false (1) then this negotiation is not performed. In any event, the local node will comply with any magic number negotiations attempted by the remote node, per th[...]

  • Page 106

    5-8 PPP MIB pppLqrQuality {pppLqrEntry 1} Integer Read-only The current quality of the link as declar ed by the local PPP entity’s Link-Quality Management modules. No effort is made to define good or bad, nor the policy used to determine it. The not-determined value indicates that the entity does not actually evaluate the link’s quality . This[...]

  • Page 107

    PPP MIB 5-9 pppLqrConfigT able {pppLqr 2} Not-Accessible T able containing the LQR configuration parameters for the local PPP entity . The ELS10-26 always has an empty table. pppLqrConfigEntry {pppLqrConfigT able 1} Not-Accessible LQR configuration information for a particular PPP link. pppLqrConfigPeriod {pppLqrConfigEntry 1} Integer Read-W[...]

  • Page 108

    5-10 PPP MIB pppLqrExtnsT able {pppLqr 3} Not-Accessible T able containing additional LQR information for the local PPP entity . The ELS10-26 always has an empty table. pppLqrExtnsEntry {pppLqrExtnsT able 1} Not-Accessible Extended LQR information for a particular PPP Link. Assuming that this group has been implemented, a PPP Link will have an entr[...]

  • Page 109

    PPP MIB 5-11 pppIpEntry {pppIpT able 1} Not-Accessible IPCP status information for a particular PPP link. pppIpOperStatus {pppIpEntry 1} Integer Read-only The operational status of the IP network pr otocol. If the value of this object is up, then the finite state machine for the IP network protocol has r eached the Opened state. • opened (1) - t[...]

  • Page 110

    5-12 PPP MIB • vj-tcp(2) - the V an Jacobsen TCP/IP header compression protocol is supported. pppIpRemoteMaxSlotId {pppIpEntry 4} Integer Read-only The Max-Slot-Id parameter that the remote node has advertised and that is in use on the link. If vj-tcp header compression is not in use on the link then the value of this object shall be 0. The value[...]

  • Page 111

    PPP MIB 5-13 network protocol’s finite state machine. The ELS10-26 only supports open (1). pppIpConfigCompression {pppIpConfigEntry 2} Integer Read-W rite If none (1), then the local node will not attempt to negotiate any IP Compression option. Otherwise, the local node will attempt to negotiate compression mode indicated by the enumerated val[...]

  • Page 112

    5-14 PPP MIB[...]

  • Page 113

    6-1 CHAPTER 6 ELS10-26 MIB The Cabletron MIB {enterprise 97} is divided into several gr oups of parameters. The individual groups ar e described in the subsections below . The MIB tree pr efix for reaching the private enterprise ELS10-26 MIB is: 1.3.6.1.4.1.97. 6.1 SYSTEM GROUP sigma {enterprise 97} sys {sigma 1} The System Group contains those pa[...]

  • Page 114

    6-2 ELS10-26 MIB sysT rapPort {sys 6} Integer Read-W rite zero, or the UDP port number to which a second copy of SNMP traps should be sent. V alid values ar e 0 through 65535. 6.1.1 Hard ware Configuration Group lxhwDiagCode {lxhw 1} Octet String Read-Only This variable is for Cabletron internal use only . lxhwManufData {lxhw 2} DisplayString Read[...]

  • Page 115

    ELS10-26 MIB 6-3 lxhwPortT ype {lxhwPortEntry 2} Integer Read-Only A value indicating the type of port. The values are defined as: • csma (1) - Ethernet or 802.3 port • uart (6) - UAR T port lxhwPortSubT ype {lxhwPortEntry 3} Integer Read-Only An integer repr esenting port type. The following values have been defined: • csmacd-tpx (13) – [...]

  • Page 116

    6-4 ELS10-26 MIB • true (1) • false (2) lxhwUpLinkManufData {lxhw 6} Octet String Read-Only A 32-byte array that contains the part number , serial number , and hardwar e revision level of the Up-Link I/O module. The array is valid only when the lxhwUpLink value is true. If lxhwUplink is false, it returns an err or . 6.1.2 LXSW Configuration Gr[...]

  • Page 117

    ELS10-26 MIB 6-5 lxswCount {lxswFilesetEntry 3} Integer Read-Only The number of files in the file set. This number may range from 1 to 255. lxswT ype {lxswFilesetEntry 4} Octet String Read-Only The types of files within the file set. The size of lxswT ype may be determined by lxswCount, since 1 octet is requir ed for each file. The possible ?[...]

  • Page 118

    6-6 ELS10-26 MIB lxswBases {lxswFilesetEntry 7} Octet String Read-Only An array (4 octets per file), containing the software’s base loading address of each of the files. Each addr ess is encoded as a series of 4 bytes, which should be converted into a 32-bit integer . lxswFlashBank {lxswFilesetEntry 8} Integer Read-Only The bank number where th[...]

  • Page 119

    ELS10-26 MIB 6-7 lxadminAnyPass {lxadmin 2} Octet String Read-W rite The authentication password (0-24 bytes) which must match the community name in an SNMP Get, Getnext, or Set PDU, in or der for the operation to be performed. A zero length password indicates that any community name is acceptable. lxadminGetPass {lxadmin 3} Octet String Read-W rit[...]

  • Page 120

    6-8 ELS10-26 MIB • false (2) lxadminAuthenticationFailure {lxadmin 8} IP Addr ess Read-Only All nulls, or the IP sour ce address within the last SNMP PDU which caused an SNMP authentication failur e. lxadminNAMReceiveCongests {lxadmin 10} Counter Read-Only Number of packets not received due to internal buf fer congestion. lxadminArpEntries {lxadm[...]

  • Page 121

    ELS10-26 MIB 6-9 lxadminStaticPrefer ence {lxadmin 16} Integer Read-W rite 2 The value to assign to ipRouteMetric2, when adding a statically-defined entry to the IP Routing T able. lxadminRipPrefer ence {lxadmin 17} Integer Read-W rite The value to assign to ipRouteMetric2, when adding a RIP-learned entry to the IP Routing T able. lxadminRipRouteD[...]

  • Page 122

    6-10 ELS10-26 MIB lxadminDisableButton {lxadmin 21} Integer Read-W rite An integer that can be set to prevent the push button on the fr ont of the ELS10-26 from contr olling the LED display . V alues include: • true (1) • false (2) lxadminButtonSelection {lxadmin 22} Integer Read-W rite An integer that indicates which statistic has been selecte[...]

  • Page 123

    ELS10-26 MIB 6-11 lxadminLEDProgramOption {lxadmin 23} Integer Read-W rite Meaning of the LED display when led-programmed has been selected for lxadminButtonSelection. V alue is: program-led-any-err or (1) 6.1.4 Software Distribution Gr oup lxswdisDesc {lxswdis 1} Octet String Read-Only The description (0-32 bytes) of the software set curr ently be[...]

  • Page 124

    6-12 ELS10-26 MIB lxswdisW riteStatus {lxswdis 3} Integer Read-Only The status of the erase/write operation. The possible values are: • in-progr ess (1) - An operation is curr ently in progress. • success (2) - The last operation completed successfully . • config-error (3) - Configuration EPROM encounter ed an error . • flash-error (4) -[...]

  • Page 125

    ELS10-26 MIB 6-13 6.1.5 Addresses Configuration Group The Addresses Configuration Group consists of the parameters described below . lxaddrStatics {lxaddr 1} Counter Read-Only The number of static addresses which ar e currently stored in the ELS10-26. lxaddrDynamics {lxaddr 2} Counter Read-Only The number of learned addresses in the ELS10-26’s [...]

  • Page 126

    6-14 ELS10-26 MIB • entry-none = 26, or this address does not exist. • bit 25 is reserved. • bit 24 is reserved. • bit 31 is reserved. Any combination of the restriction bits (bits 23-21) may be set for any type of entry , except entry-other: • Bit 21 is reserved. • Bits 20-18 are r eserved. Exactly one of the special entry bits (bits 1[...]

  • Page 127

    ELS10-26 MIB 6-15 lxaddrOperation {lxaddr 8} Integer Read-W rite The operation to be performed upon the described address. The possibilities include: • read-random (1) • read-next (2) • update (4) • delete (5) • read-block (6) lxaddrIndex {lxaddr 9} Integer Read-W rite The index number to be used for read-next and r ead-block operations. [...]

  • Page 128

    6-16 ELS10-26 MIB port number . If the port number is zero, then the addr ess is that of a specially configured addr ess; otherwise, the address is a dynamically learned address. This parameter is only used for dumping blocks of MAC addresses. 6.1.6 Cabletron Interfaces Gr oup lxifT able {lxif 1} Not Accessible A list of interface entries; one per[...]

  • Page 129

    ELS10-26 MIB 6-17 lxifThreshold {lxifEntry 4} Integer Read-W rite Reserved. Maximum number of combined receive and transmit packet hardwar e errors before an alarm should be generated. See ifInErrors. lxifThresholdT ime {lxifEntry 5} Integer Read-W rite Reserved. The time period (in seconds) to which sifThreshold applies. A value of zero will disab[...]

  • Page 130

    6-18 ELS10-26 MIB lxifTxStormT ime {lxifEntry 9} T ime T icks Read-W rite The period of time, in centiseconds, which qualifies sifTxStormCnt (not applicable for the UAR T port). llxifFunction {lxifEntry 16} Integer Read-Only The current functional state (pr otocols which have been activated and are operational) of the port. The following values or[...]

  • Page 131

    ELS10-26 MIB 6-19 lxifRxQueues {lxifEntry 19} Counter Read-Only Number of received packets lost because of insuf ficient receive buffers. lxifStatisticsT ime {lxifEntry 27} T ime T icks Read-Only Length of time during which statistics were collected. In particular , the following statistics may be examined to determine the exact utilization rate o[...]

  • Page 132

    6-20 ELS10-26 MIB lxifForwardedChars {lxifEntry 30} Counter Read-Only Number of characters in the forwarded r eceived packets. lxifDesc {lxifEntry 32} lxifGoodRxFrames {lxifEntry 33} Counter Read-Only lxifGoodTxFrames {lxifEntry 34} Counter Read-Only 6.1.7 Cabletron Dot3 Gr oup This group pr ovides additional objects that are not part of the standa[...]

  • Page 133

    ELS10-26 MIB 6-21 lxdot3LedOn {lxdot3Entry 3} Integer Read-Only An integer indicating whether the port’s programmable LED is on. V alues include: • led-on (1) • led-off (2) lxdot3RxCollisions {lxdot3Entry 4} Counter Read-Only Counter indicating the number of receive collisions. Note: 10BASE-T cannot count received collisions. lxdot3RxRunts {l[...]

  • Page 134

    6-22 ELS10-26 MIB lxdot3TxBabbles {lxdot3Entry 8} Counter Read-Only 4 Counter indicating the number of packets transmitted with babble errors. lxdot3TxCollisions {lxdot3Entry 9} Counter Read-Only Counter indicating the total number of transmit collisions. lxdot3SpeedSelection {lxdot3Entry 13} Integer Read-W rite Speed may only be selected for the F[...]

  • Page 135

    ELS10-26 MIB 6-23 • duplex-half (2) • duplex-full (3) 6.1.8 Cabletron U ART Interface Gr oup lxuartT able {lxuart 1} Not Accessible A list of interface entries; one per UAR T port. lxuartEntry {lxuartT able 1} Not Accessible A set of objects for an interface entry . The individual components are described below . lxuartIndex {lxuartEntry 1} Int[...]

  • Page 136

    6-24 ELS10-26 MIB • 38400-baud (7) • 56-kilobits (8) • 1.544-megabits (9) • 2.048-megabits (10) • 45-megabits (1 1) lxsuartAlignmentErrors {lxuartEntry 3} Counter Read-Only Number of received packets with frame alignment err ors, since the port was last enabled. lxsuartOverrunErr ors {lxuartEntry 4} Counter Read-Only Number of received pa[...]

  • Page 137

    ELS10-26 MIB 6-25 lxprotoIfIndex {lxsprotoEntry 1} Integer Read-Only Identifies the interface (port) to which this entry’s information belongs. The value of this variable corresponds to lxifIndex, as well as to most of the other port identification values in related MIBs. lxprotoBridge {lxspr otoEntry 2} Integer Read-W rite Defines the bridgin[...]

  • Page 138

    6-26 ELS10-26 MIB lxprotoT runking {lxsprotoEntry 5} Integer Read-W rite Specifies whether Cabletron’s tr unking protocol (an extension to the standard Spanning T ree) is to be used over this port. V alues include: • enabled (1) • disabled (2) lxprotoT ransmitPacing {lxpr otoEntry 6} Integer Read-W rite When enabled, introduces delays into n[...]

  • Page 139

    ELS10-26 MIB 6-27 lxtrunkState {lxtr unkEntry 2} Integer Read-Only Indicates the trunking condition for this port. V alues include: • off (1) – this link has not been enabled for tr unking. • closed (2) – this link has not yet received any PDUs. • oneway (3) – incoming trunking PDUs do not indicate that the ELS10-26’s PDUs are being s[...]

  • Page 140

    6-28 ELS10-26 MIB • none (1) – no error; the tr unking protocol may r e-start with no error conditions when tr unking is turned on for a port, or when the MIB variable that controls extra tr unk groups is modified. • in-bpdu (2) – a Spanning T ree BPDU was r eceived, indicating that the connection is not point-to-point, or the far end does[...]

  • Page 141

    ELS10-26 MIB 6-29 lxtrunkLinkCount {lxtrunkEntry 7} Integer Read-Only The number of links with the trunk gr oup. lxtrunkLastChange {lxtrunkEntry 8} Integer Read-Only The number of seconds since lxtrunkState changed. 6.1.11 Cabletr on W orkgroup Mana g ement Group lxW orkGr oupNextNumber {lxworkgr oup 1} Integer Read-Only The next available workgrou[...]

  • Page 142

    6-30 ELS10-26 MIB • lxW orkGr oupName Display String Read-W rite • lxW orkGr oupPorts Octet String Read-W rite • lxW orkGr oupT ype Integer Read-W rite • lxW orkGr oupIpAddress IP Addr ess Read-W rite • lxW orkGr oupIpMask IP Address Read-W rite • lxW orkGr oupIpxNetwork Octet String Read-write lxW orkGr oupNumber {lxW orkGroupEntry 1} [...]

  • Page 143

    ELS10-26 MIB 6-31 6.1.12 Cabletr on T rap Management Group This group pr esents the Cabletron MIB variables that are included as varbinds with the traps generated by the ELS10-26. Chapter 7 of this manual describes the traps generated by the ELS10-26. lxtrapControlT able {lxtrapMgt 1} Not Accessible This table contains information about the severit[...]

  • Page 144

    6-32 ELS10-26 MIB • informational (1) • warning (2) • minor (3) • major (4) • critical (5) lxtrapT ext {lxtrapContr ol 4} Display String Read-Only Provides a description of the trap. lxtrapSeverityControlT able {lxtrapMgt 2} Not Accessible This table contains information about whether traps of a particular severity are enabled or disabled[...]

  • Page 145

    ELS10-26 MIB 6-33 • critical (5) lxtrapSeverityEnable {lxtrapSeverityControl 2} Integer Read-W rite Allows you to enable or disable all traps of a given security level. The values are as follows: • enabled (1) • disabled (2) lxtrapIncludeT ext {lxtrapMgt 3} Integer Read-W rite Indicates whether or not a formatted text string is included in th[...]

  • Page 146

    6-34 ELS10-26 MIB lxtrapT able {lxtrapMgt 7} Not Accessible This table contains the latest traps that have been generated. lxtrapEntryIndex {lxtrapEntry 1} Integer Read-Only The sequence of elements in the lxtrapControlT able 1 are shown below . A number repr esenting the order (in time) in which the trap occurred. This 32-bit number can wrap. lxtr[...]

  • Page 147

    ELS10-26 MIB 6-35 • critical (5) 6.1.13 Ping Management MIB lxpingDataT imeout OBJECT -TYPE SYNT AX T imeT icks ACCESS read-write ST A TUS mandatory DESCRIPTION The time, in centiseconds, from the last ping activity (a send or receive of an ECHO_RESPONSE or ECHO_REQUEST message), to when the lxpingEntry infor- mation for that ping request will be[...]

  • Page 148

    6-36 ELS10-26 MIB DESCRIPTION The parameters, state, and results of a ping r equest. INDEX {lxpingNMSAddr ,lxpingDes- tAddr} ::= {lxpingT able 1} lxpingEntry ::= SEQUENCE {lxpingNMSAddr IpAddress, lxpingDestAddr IpAddress, lxpingState INTEGER, lxpingCount INTEGER, lxpingDataSize INTEGER, lxpingW ait T imeT icks, lxpingT imeOut T imeT icks, lxpingOp[...]

  • Page 149

    ELS10-26 MIB 6-37 ::= {lxpingEntry 1} lxpingDestAddr OBJECT -TYPE SYNT AX IpAddress ACCESS read-write ST A TUS mandatory DESCRIPTION The IP addr ess which is to be the destination of the ping ECHO_REQUEST . This variable cannot be set while lxpingOpera- tion is on. ::= {lxpingEntry 2} lxpingState OBJECT_TYPE SYNT AX INTEGER {not-started (1) active [...]

  • Page 150

    6-38 ELS10-26 MIB DESCRIPTION The number of ping requests which are to be sent. This vari- able cannot be set while lxping- Operation is on. ::= {lxpingEntry 4} lxpingDataSize OBJECT -TYPE SYNT AX INTEGER ACCESS read-write ST A TUS mandatory DESCRIPTION The datagram packet size which will be sent with the ECHO_REQUEST in bytes. This variable cannot[...]

  • Page 151

    ELS10-26 MIB 6-39 ST A TUS mandatory DESCRIPTION The time, in centiseconds, since the last ECHO-RESPONSE was received (or the last ECHO-RESPONSE was sent, if there have been no r esponses) when the ping request will time out. This variable cannot be set while the lxpingOperation is on. ::= {lxpingEntry 7} lxpingOperation OBJECT -TYPE SYNT AX INTEGE[...]

  • Page 152

    6-40 ELS10-26 MIB ::= {lxpingEntry 9} lxpingMax OBJECT -TYPE SYNT AX T imeT icks ACCESS read-only ST A TUS mandatory DESCRIPTION The maximum round trip time for the ping requests and responses, in centiseconds. ::= {lxpingEntry 10} lxpingA vg OBJECT -TYPE SYNT AX T imeT icks ACCESS read-only ST A TUS mandatory DESCRIPTION The average round trip tim[...]

  • Page 153

    ELS10-26 MIB 6-41 ::= {lxpingEntry 12} lxpingNumReceived OBJECT -TYPE SYT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION The number of ICMP ECHO_RESPONSE messages that have been received as a result of this ping r equest. ::= {lxpingEntry 13} 6.1.14 T racer oute An implementation of traceroute was added in or der to add the ability to o[...]

  • Page 154

    6-42 ELS10-26 MIB 6.1.15 T raceroute Management MIB lxtraceDataT imout OBJECT -TYPE SYNT AX T imeT icks ACCESS read-write ST A TUS mandatory DESCRIPTION The time, in centiseconds, from the last traceroute activity , (the response to, or timeout of the last probe sent) to when the lxtra- ceEntry information for that trac- eroute r equest will be del[...]

  • Page 155

    ELS10-26 MIB 6-43 ::= {lxtraceT able 1} lxtraceEntry ::= SEQUENCE {lxtraceNMSAddr IpAddress lxtraceDsetAddr IpAddress lxtraceMaxTTL INTEGER lxtraceDataSize INTEGER lxtraceNumProbes INTEGER lxtraceW ait T imeT icks lxtraceOperation INTEGER lxtraceHop INTEGER lxtraceHopAddr IpAddress lxtraceProbe INTEGER lxtraceState INTEGER lxtraceT ime T imeT icks}[...]

  • Page 156

    6-44 ELS10-26 MIB DESCRIPTION The IP addr ess which is to be the destination of the traceroute request. This variable cannot be set while traceOperation is on. ::= {lxtraceEntry 2} lxtraceMaxTTL OBJECT -TYPE SYNT AX INTEGER ACCESS read-write ST A TUS mandatory DESCRIPTION The maximum time-to-live for outgoing traceroute pr obe pack- ets. This deter[...]

  • Page 157

    ELS10-26 MIB 6-45 ST A TUS mandatory DESCRIPTION The number of probes which ar e sent for each hop. This variable cannot be set while lxtraceOpera- tion is on. ::= {lxtraceEntry 5} lxtraceW ait OBJECT -TYPE SYNT AX T imeT icks ACCESS read-write ST A TUS mandatory DESCRIPTION The time to wait in response to a probe. This variable cannot be set while[...]

  • Page 158

    6-46 ELS10-26 MIB ST A TUS mandatory DESCRIPTION The hop count for a set of probes with a particular TTL. ::= {lxtraceEntry 8} lxtraceHopAddress OBJECT -TYPE SYNT AX IpAddress ACCESS read-only ST A TUS mandatory DESCRIPTION The IP addr ess of the host which responded for a pr obe with a particular TTL. ::= {lxtraceEntry 9} lxtraceProbe OBJECT -TYPE[...]

  • Page 159

    ELS10-26 MIB 6-47 completed (5)} ACCESS read-only ST A TUS mandatory DESCRIPTION The current state of the traceroute. ::={lxtraceEntry 1 1} lxtraceProbe OBJECT -TYPE SYNT AX T imeT icks ACCESS read-only ST A TUS mandatory DESCRIPTION Round trip time of a probe for a particular hop. ::= {lxtraceEntry 12} 6.1.16 P or t Mirr oring lxmirrorMode OBJECT [...]

  • Page 160

    6-48 ELS10-26 MIB ::= {lxmirror group 1} lxmirrorT argetPort OBJECT -TYPE SYNT AX INTEGER ACCESS read-write ST A TUS mandatory DESCRIPTION The number of the port whose data will be mirror ed by the spe- cial mirror port. ::= {lxmirror group 2}[...]

  • Page 161

    7-1 CHAPTER 7 T RAPS The unit sends T rap PDUs to the NMS, using the pre-configur ed NMS IP addr ess (see lxadminNMSIP Addr). If no address has been pre-configur ed, then the unit sends the T raps to the source IP address of the last SNMP datagram received from an NMS. If no address has been pr e-configured, and if no datagrams have been receive[...]

  • Page 162

    7-2 T raps authenticationFailure (4) - This trap is generated whenever the community name in a PDU does not match the corresponding password. All SetRequest PDUs must match the configAnyPass (refer to the of lxadminGetPass for SetRequest exceptions), GetRequest PDUs must match either the lxadminGetPass or the configAnyPass. The GetRequest excepti[...]

  • Page 163

    T raps 7-3 lxRxQuesT rap (4) - Sent whenever the number of times that the port’s receiver has missed r eceiving packets due to buffer space shortages has exceeded the port’s limit. Cabletron MIB variables include: • lxT rapSeverity • lxifRxQueues lxTxStormFlagT rap (5) - Sent whenever multicast storm protection has been invoked for the port[...]

  • Page 164

    7-4 T raps • lxT rapSeverity • lxlpbkOperation • lxlpbkErrorNoReceives • lxlpbkErrorBadReceives lxT runkStateT rap (10) - A trunking state change transition has occurred. The possible transitions ar e: • CLOSED-ONW A Y • ONEW A Y -PER TURBED • PER TURBED-JOINED • JOINED-HELDDO WN • CLOSED-HELDDO WN • ONEW A Y -HELDDOWN • PER T[...]

  • Page 165

    T raps 7-5 lxT runkIP AddrT rap (12) - The associated trunking IP addr ess of the remote bridge has changed. Cabletron MIB variables include: • lxT rapSeverity • lxtrunkRemoteIP lxT runkErr orT rap (13) - An err or has occurred in trunking. Cabletron MIB variables include: • lxT rapSeverity • lxtrunkLastErr or lxT runkLinkOr dinalT rap (14)[...]

  • Page 166

    7-6 T raps lxStorageFailureT rap (17) - Sent if the unit’s Configuration EEPROM has failed. Cabletron MIB variables include: • lxT rapSeverity lxPortCongestionT rap (18) - Sent whenever outbound congestion control has been invoked for the port. Cabletron MIB variables include: • lxT rapSeverity • ifOutDiscards lxT opChangeBegunT rap (19) -[...]

  • Page 167

    T raps 7-7 lxStRootIDT rap (22) - The spanning tree r oot bridge ID has changed. Cabletron MIB variables include: • lxT rapSeverity • dot1dStpDesignatedRoot lxStRootCostT rap (23) - The unit’s spanning tree cost to the r oot bridge has changed. Cabletron MIB variables include: • lxT rapSeverity • dot1dStpDesignatedRoot lxStRootPortT rap ([...]

  • Page 168

    7-8 T raps • dot1dStpHelloT ime lxStForwardDelayT rap (27) - The spanning tree forwar d delay time has changed. Cabletron MIB variables include: • lxT rapSeverity • dot1StpForwardDelay lxStDesigRootT rap (28) - The root bridge ID in r eceived spanning tree configuration BPDUs fr om the port has changed. Cabletron MIB variables include: • l[...]

  • Page 169

    T raps 7-9 lxStPortDesigPortT rap (31) - The port ID of the spanning tree des- ignated port of the LAN/W AN to which the port is attached has changed. Cabletron MIB variables include: • lxT rapSeverity • dot1dStpPortDesignatedPort lxStPortStateT rap (32) - The spanning tree state of the port has changed. Cabletron MIB variables include: • lxT[...]

  • Page 170

    7-10 T raps[...]