TCP/IP MIB-II. 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 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 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.
Note: 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.
The MIB tree prefix for reaching the TCP/IP MIB-II is:
1.3.6.1.2.1.
2.1 SYSTEM GROUP
system {mib-2 1}
The TCP/IP System Group parameters are described below. sysDescr
DisplayString Read-Only
{system 1}
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
Object Identifier Read-Only
{system 2}
The identifier 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 identifier 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
TimeTicks Read-Only
{system 3}
The time, in centiseconds, since the ELS10-26 was last booted. sysContact
DisplayString Read-Write
{system 4}
The name and address of the contact person for the ELS10-26. sysName
DisplayString Read-Write
{system 5}
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 configure and monitor status for the ELS10-26.) sysLocation
DisplayString Read-Write
The physical location of the ELS10-26.
{system 6} sysServices
Integer Read-Only
{system 7}
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
Integer Read-Only
{interfaces 1}
The number of ports (whether alive or dead), including the UART.
ifTable
Not Accessible
{interfaces 2}
A list of interface entries; one per port (ifNumber in total). ifEntry
Not Accessible
{ifTable 1}
A set of objects for an interface entry. The individual components are described below. ifIndex
Integer Read-Only
{ifEntry 1}
The port number, beginning with 1 for the first 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
DisplayString Read-Only
{ifEntry 2}
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 (fiber connection)
• Fast Ethenet/802.3u T4 (2 twisted pairs, category 5) ifType
Integer Read-Only
{ifEntry 3}
The type of the port, i.e., one of the following:
• (6) - ethernet-csmacd
• (23) - ppp (for the UART port). ifMtu
Integer Read-Only
{ifEntry 4}
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
Integer Read-Only
{ifEntry 5}
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
TCP/IP MIB-II ifPhysAddress
Physical Address Read-Write
1
{ifEntry 6}
The MAC address of the port. For the UART port, this field should be an octet string of zero length. ifAdminStatus
Integer Read-Write
{ifEntry 7}
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 statistics to be reset
• down (2) - the port is not to be used
• testing (3) - the port is to be put into local loopback (this value is not saved if the unit reboots) ifOperStatus
Integer Read-Only
{ifEntry 8}
The current status of the port, i.e., one of the following:
• up (1) - the port can send/receive NMS packets; however, whether or not the port has its bridging functions enabled is unknown.
• down (2) - the port is broken, or is intentionally physically disabled.
• testing (3) - the port is in local loopback. ifLastChange
TimeTicks Read-Only
{ifEntry 9}
The time, in centiseconds relative to sysUpTime, since the port entered its last state (as defined by ifOperStatus).
1.
The standard MIB definition is Read-Only.
2-5
TCP/IP MIB-II ifInOctets
Counter Read-Only
{ifEntry 10}
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 hardware 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.
ifInUcastPkts
Counter Read-Only
{ifEntry 11}
The number of non-multicast packets received by the port, regardless of the packet’s outcome (i.e., whether the packet was filtered or forwarded). ifInNUcastPkts
Counter Read-Only
{ifEntry 12}
The number of multicast packets received by the port, regardless of the packet’s outcome (i.e., whether the packet was filtered or forwarded). ifInDiscards
Counter Read-Only
{ifEntry 13}
The number of packets received by the port, which were filtered because of a lack of resources to receive the packet (see lxifRxQueues). ifInErrors
Counter Read-Only
{ifEntry 14}
The number of packets received by the port, which were discarded due to hardware reception errors.
Read-Only
This value is always zero.
2-6
TCP/IP MIB-II ifOutOctets
Counter Read-Only
{ifEntry 16}
The total number of bytes transmitted out the port, counting the
MAC header and FCS. ifOutUcastPkts
Counter Read-Only
{ifEntry 17}
The number of non-multicast packets transmitted out the port, regardless of whether or not hardware transmission errors were encountered. ifOutNUcastPkts
Counter Read-Only
{ifEntry 18}
The number of multicast packets transmitted out the port, regardless of whether or not hardware transmission errors were encountered. ifOutDiscards
Counter Read-Only
{ifEntry 19}
The number of packets to be transmitted out the port, but were not transmitted due to non-error reasons. The definition of non-error reasons is implementation dependent. The ELS10-26 defines non-error reasons as packet congestion. Packet congestion occurs when too many packets are to be queued for transmission, or when packets have been awaiting transmission for too long a time period. ifOutErrors
Counter Read-Only
{ifEntry 20}
The number of packets that were to be transmitted out the port, but incurred transmission hardware errors.
2-7
TCP/IP MIB-II ifOutQLen
Gauge Read-Only
{ifEntry 21}
The maximum length ever obtained by the port’s outbound packet queue (in packets) is not available, so this value is always one.
ifSpecific
Object Identifier Read-Only
{ifEntry 22}
The object identifier of the MIB for the type of port, i.e., one of the following:
{dot3}
{ppp} for Ethernet ports (dot3 is defined later, as {transmission 7}). for the UART (ppp is defined later, as
{experimental 18}).
2.3 ADDRESS TRANSLATION GROUP
at {mib-2 3}
The TCP/IP Address Translation Group parameters are minimally supported (i.e., for any parameter in this group, the ELS10-26 returns a GetResponse with a noSuchName ErrorStatus). It is anticipated that the Address Translation Group will be deleted from TCP/IP MIB III, since there will be separate address translation tables for every type of network protocol (indeed,
TCP/IP MIB II already defines the IP Address Translation Table).
The TCP/IP Address Translation Group parameters are described below.
2-8
TCP/IP MIB-II atTable
Not Accessible atEntry
Not Accessible
{at 1}
{atTable 1} atIfIndex
Integer Read-Write
{atEntry 1}
All GetResponse PDUs indicate a noSuchName ErrorStatus. atPhysAddress
Physical Address Read-Write
{atEntry 2}
All GetResponse PDUs indicate a noSuchName ErrorStatus. atNetAddress
Network Address Read-Write
{atEntry 3}
All GetResponse PDUs indicate a noSuchName ErrorStatus.
2.4 IP GROUP
ip {mib-2 4)
The TCP/IP IP Group parameters are described below. ipForwarding
Integer Read-Write
{ip 1}
Whether the ELS10-26 is an IP router. This value is always host (2).
Attempts to write a different value to this field will not change its value, and “badValue” GetResponse PDUs are returned for all such SetRequest PDUs. ipDefaultTTL
Integer Read-Write
{ip 2}
The value, in seconds, to insert into the Time-To-Live field of the IP header when this ELS10-26 creates IP datagrams.
2-9
TCP/IP MIB-II ipInReceives
Counter Read-Only
{ip 3}
The total number of IP packets received from all ports (including the UART). ipInHdrErrors
Counter Read-Only
{ip 4}
The number of packets received that were discarded due to errors in the IP header. ipInAddrErrors
Counter Read-Only
{ip 5}
The number of packets received that were discarded due to an invalid (or nonroutable) destination IP address in the IP header. ipForwDatagrams
Counter Read-Only
{ip 6}
The number of packets received that were routed towards a final
IP destination.
2 ipInUnknownProtos
Counter Read-Only
{ip 7}
The number of packets received that were addressed to this
ELS10-26’s IP, but were discarded because of an unknown or unsupported protocol. ipInDiscards
Counter Read-Only
{ip 8}
The number of packets that were received without error, but were not processed (due to insufficient resources, for example).
2.
This appears to be a typographical error in the TCP/IP MIB, since the name should be ipInForwDatagrams.
2-10
TCP/IP MIB-II ipInDelivers
Counter Read-Only
{ip 9}
The total number of input packets successfully delivered to the IP user-protocol layers. ipOutRequests
Counter Read-Only
{ip 10}
The total number of IP output packets generated by this ELS10-26.
This count does not include any packets represented in ipForwDatagrams. ipOutDiscards
Counter Read-Only
{ip 11}
The total number of output packets which were discarded (due to lack of resources, for example). This counter includes packets which would be included in ipForwDatagrams if any such packets were discarded. ipOutNoRoutes
Counter Read-Only
{ip 12}
The number of packets which were discarded because no route could be found to transmit them to their destination. This counter includes any packets counted in ipForwDatagrams which meet this “no-route” criterion. ipReasmTimeout
Integer Read-Only
{ip 13}
The maximum time, in seconds, that received fragments are held while they are awaiting reassembly within this ELS10-26.
ipReasmReqds
Counter Read-Only
{ip 14}
The number of IP fragments received which needed to be reassembled within this ELS10-26.
2-11
TCP/IP MIB-II ipReasmOKs
Counter Read-Only
{ip 15}
The number of IP datagrams which were successfully reassembled. ipReasmFails
Counter Read-Only
{ip 16}
The number of failures (for whatever reason timed-out, errors, etc.) detected by the IP reassembly algorithm. This is not necessarily a count of discarded IP fragments since some algorithms (notably
RFC 815) can lose track of the number of fragments by combining them as they are received. ipFragOKs
Counter Read-Only
{ip 17}
The number of IP datagrams that have been successfully fragmented within this ELS10-26. ipFragFails
Counter Read-Only
{ip 18}
The number of IP datagrams that have been discarded because they needed to be fragmented but could not be (e.g., because their
“Don’t Fragment” flag was set). ipFragCreates
Counter Read-Only
{ip 19}
The number of IP datagram fragments that have been generated by this ELS10-26.
2.4.1 IP Address Table
The TCP/IP IP Address Table contains the IP addressing information for each port. The parameters are described below.
2-12
TCP/IP MIB-II ipAddrTable
Not Accessible
{ip 20}
A list of IP address entries; one per IP address. If a port has not yet learned its IP address, then an ipAddrEntry might not exist for the port (i.e., having an ipAddrEntry with an IP address of zero is not acceptable). ipAddrEntry
Not Accessible
{ipAddrTable 1}
A set of objects for an ipAddrTable entry. The individual components are described below. ipAdEntAddr
IP Address Read-Only
{ipAddrEntry 1}
The IP address itself. Although this field is Read-Only, the
ELS10-26’s lxifIPAddr parameter can be written to affect changes. ipAdEntIfIndex
Integer Read-Only
{ipAddrEntry 2}
The port number which has the indicated IP address. ipAdEntNetMask
IP Address Read-Only
{ipAddrEntry 3}
The network/subnet mask associated with the IP address. For
SetRequests, a mask of zero may be specified, in which case, the
ELS10-26 will create the correct network mask for a non-subnetted network. For GetRequests, the ELS10-26 will always convert a value of zero into the correct network mask. ipAdEntBcastAddr
Integer Read-Only
{ipAddrEntry 4}
The value for the least significant bit for broadcasts, i.e., the constant 1.
2-13
TCP/IP MIB-II ipAdEntReasmMaxSize
Integer Read-Only
{ipAddrEntry 5}
The largest IP datagram which can be reassembled, i.e., the constant 4470.
2.4.2 IP Routing Table
The TCP/IP IP routing table contains the routing information for each route currently known by the ELS10-26. When adding a row, the entire row must be specified, except for the following defaults:
• ipRouteDest is obtained from the row’s instance identifier.
• ipRouteMetric1 defaults to 0.
• ipRouteMetric2 defaults to lxadminStaticPreference.
• ipRouteMetric3 through ipRouteMetric5 default to -1.
• ipRouteNextHop is obtained from the row’s instance identifier.
• ipRouteType defaults to “direct” if ipRouteNextHop is not specified, or if ipRouteNextHop is specified and it, combined with ipRouteMask, equals the same network as that defined by ipRouteDest.
• ipRouteProto defaults to “netmgmt”.
• ipRouteMask defaults to the standard network class mask based on the row’s instance identifier (except 255.255.255.255 is used if the row’s instance identifier contains a non-zero host portion).
Parameters include the following variables: ipRouteTable
Not Accessible
{ip 21}
A list of routing entries; one per route. An entry is keyed by an IP address (ipRouteDest, defined below). If there are multiple entries
2-14
TCP/IP MIB-II for the same IP address, then only the entry being used by the IP forwarding process is available for SNMP access. ipRouteEntry
Not Accessible
{ipRouteTable 1}
A set of objects for an ipRouteTable entry. The individual components are described below. ipRouteDest
IP Address Read-Write
The destination IP address of this route.
{ipRouteEntry 1}
{ipRouteEntry 2} ipRouteIfIndex
Integer Read-Write
The port number of the next hop. ipRouteMetric1
Integer Read-Write
{ipRouteEntry 3}
The primary routing metric for this route. This is the zero-based hop count to ipRouteDest. That is, a hop count of zero indicates that ipRouteDest is on a directly connected network. ipRouteMetric2
Integer Read-Write
{ipRouteEntry 4}
An alternative routing metric for this route. This must be greater than zero. ipRouteMetric3
Integer Read-Write
{ipRouteEntry 5}
An alternative routing metric for this route. ipRouteMetric4
Integer Read-Write
{ipRouteEntry 6}
An alternative routing metric for this route.
2-15
TCP/IP MIB-II ipRouteNextHop
IP Address Read-Write
The IP address of the route’s next hop.
{ipRouteEntry 7} ipRouteType
Integer Read-Write
{ipRouteEntry 8}
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 route to a directly connected network.
• indirect (4) - the entry is a route to a remote network. ipRouteProto
Integer Read-Only
{ipRouteEntry 9}
The manner in which the route was learned. ipRouteAge
Integer Read-Write
{ipRouteEntry 10}
The number of seconds since the route was last updated or deemed to be correct. ipRouteMask
IP Address Read-Write
{ipRouteEntry 11}
The mask to be combined with the destination IP address using the
AND operator, before being compared to the value in the ipRouteDest field. ipRouteMetric5
Integer Read-Write
{ipRouteEntry 12}
An alternative routing metric for this route.
2-16
TCP/IP MIB-II ipRouteInfo
Object Identifier Read-Write
{ipRouteEntry 13}
A reference to additional MIB definitions, specific to the routing protocol which is responsible 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 Translation Table
The TCP/IP IP address translation table contains mappings of
Internet addresses to MAC addresses, except for the Internet addresses of the ELS10-26 itself. The parameters are Read/Write, according to TCP/IP MIB-II; however, the ELS10-26 has the restriction that a dynamic entry should not be modified, except to be made “invalid” (any other modifications will cause a static entry to be created). When adding a row, the following defaults are used:
• ipNetToMediaIfIndex is obtained from the row’s instance identifier.
• ipNetToMediaPhysAddress defaults to 0.
• ipNetToMediaNetAddress is obtained from the row’s instance identifier.
• ipNetToMediaType defaults to “static”.
Parameters include the following: ipNetToMediaTable
Not Accessible
{ip 22}
A list of IP address translation entries; one per port number and IP address.
2-17
TCP/IP MIB-II ipNetToMediaEntry
Not Accessible
{ipNetToMediaTable 1}
A set of objects for an ipNetToMediaTable entry. The individual components are described below. ipNetToMediaIfIndex
Integer Read-Write
{ipNetToMediaEntry 1}
The port number for which this entry is effective. ipNetToMediaPhysAddress
Physical Address Read-Write
{ipNetToMediaEntry 2}
The MAC address (for the PPP port, this should be a zero length octet string; for Ethernet ports, this should be a little-endian six byte address). ipNetToMediaNetAddress
IP Address Read-Write
{ipNetToMediaEntry 3}
The IP address which corresponds to the ipNetToMediaPhysAddress. ipNetToMediaType
Integer Read-Write
{ipNetToMediaEntry 4}
The type of address mapping, one of the following:
• other (1) - none of the below.
• invalid (2) - the entry should be considered to be non-existent.
• dynamic (3) - the mapping was dynamically learned.
• static (4) - the mapping was statically configured.
2.4.4 IP Additional Objects
The TCP/IP additional IP objects are described below.
2-18
TCP/IP MIB-II ipRoutingDiscards
Counter Read-Only
{ip 23}
The number of valid routing entries that were discarded.
2.5 ICMP GROUP
icmp {mib-2 5}
The TCP/IP ICMP Group parameters are described below. icmpInMsgs
Counter Read-Only
{icmp 1}
The total number of ICMP messages which were received by this
ELS10-26. This includes all messages represented by icmpInErrors. icmpInErrors
Counter Read-Only
{icmp 2}
The number of ICMP messages which were received with errors
(bad checksums, bad length, etc.). icmpInDestUnreachs
Counter Read-Only
{icmp 3}
The number of ICMP “Destination Unreachable” messages received. icmpInTimeExcds
Counter Read-Only
{icmp 4}
The number of ICMP “Time Exceeded” messages received. icmpInParmProbs
Counter Read-Only
{icmp 5}
The number of ICMP “Parameter Problem” messages received.
2-19
TCP/IP MIB-II icmpInSrcQuenchs
Counter Read-Only
{icmp 6}
The number of ICMP “Source Quench” messages received. icmpInRedirects
Counter Read-Only
{icmp 7}
The number of ICMP “Redirect” messages received. icmpInEchos
Counter Read-Only
{icmp 8}
The number of ICMP “Echo (request)” messages received. icmpInEchoReps
Counter Read-Only
{icmp 9}
The number of ICMP “Echo Reply” messages received. icmpInTimestamps
Counter Read-Only
{icmp 10}
The number of ICMP “Timestamp (request)” messages received. icmpInTimestampsReps
Counter Read-Only
{icmp 11}
The number of ICMP “Timestamp Reply” messages received. icmpInAddrMasks
Counter Read-Only
{icmp 12}
The number of ICMP “Address Mask Request” messages received. icmpInAddrMaskReps
Counter Read-Only
{icmp 13}
The number of ICMP “Address Mask Reply” messages received.
2-20
TCP/IP MIB-II icmpOutMsgs
Counter Read-Only
{icmp 14}
The total number of ICMP messages which were sent by this
ELS10-26. This includes all messages counted by icmpOutErrors. icmpOutErrors
Counter Read-Only
{icmp 15}
The number of ICMP messages which this ELS10-26 did not send due to problems discovered entirely within the ICMP subsystem
(such as lack of buffers). icmpOutDestUnreachs
Counter Read-Only
{icmp 16}
The number of ICMP “Destination Unreachable” messages sent. icmpOutTImeExcds
Counter Read-Only
{icmp 17}
The number of ICMP “Time Exceeded” messages sent. icmpOutParmProbs
Counter Read-Only
{icmp 18}
The number of ICMP “Parameter Problem” messages sent. icmpOutSrcQuenchs
Counter Read-Only
{icmp 19}
The number of ICMP “Source Quench” messages sent. icmpOutRedirects
Counter Read-Only
{icmp 20}
The number of ICMP “Redirect” messages sent. icmpOutEchos
Counter Read-Only
{icmp 21}
The number of ICMP “Echo (request)” messages sent.
2-21
TCP/IP MIB-II icmpOutEchoReps
Counter Read-Only
{icmp 22}
The number of ICMP “Echo Reply” messages sent. icmpOutTimestamps
Counter Read-Only
{icmp 23}
The number of ICMP “Timestamp (request)” messages sent. icmpOutTimestampReps
Counter Read-Only
{icmp 24}
The number of ICMP “Timestamp Reply” messages sent. icmpOutAddrMasks
Counter Read-Only
{icmp 25}
The number of ICMP “Address Mask Request” messages sent. icmpOutAddrMaskReps
Counter Read-Only
{icmp 26}
The number of ICMP “Address Mask Reply” messages sent.
2.6 TCP GROUP
tcp {mib-2 6}
The TCP Group is not supported since the ELS10-26 does not support TCP.
2.7 UDP GROUP
udp {mib-2 7}
The TCP/IP UDP Group parameters are described below.
2-22
TCP/IP MIB-II udpInDatagrams
Counter Read-Only
{udp 1}
The total number of UDP datagrams delivered to UDP users. udpNoPorts
Counter Read-Only
{udp 2}
The total number of received UDP datagrams for which there was no application at the destination port. udpInErrors
Counter Read-Only
{udp 3}
The number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port. udpOutDatagrams
Counter Read-Only
{udp 4}
The total number of UDP datagrams sent from this ELS10-26.
2.7.1 UDP Listener Table
The TCP/IP UDP Listener Table parameters are described below. udpTable
Not Accessible
{udp 5}
A table containing UDP listener information. The table has entries for the following UDP port numbers port 69 (default TFTP port number), port 161 (SNMP port number), and port 520 (RIP port number).
udpEntry
Not Accessible
{udpTable 1}
The entry information of the IP address and UDP port combination.
2-23
TCP/IP MIB-II udpLocalAddress
IP Address Read-Only
{udpEntry 1}
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
Integer Read-Only
{udpEntry 2}
The UDP port number, i.e., one of 69, 161, and 520. Note that reception of SNMP Traps (UDP port number 162) is not supported by the ELS10-26.
2.8 EGP GROUP
egp {mib-2 8}
The EGP Group is not supported since the ELS10-26 does not support EGP.
2.9 OIM SUBTREE
cmot {mib-2 9}
The OSI Subtree, as defined in OSI internet management,
Management Information Base, RFC 1214 (L. LaBarre, editor), dated
April 1991, is not supported.
2.10 TRANSMISSION GROUP
transmission {mib-2 10}
The supported TCP/IP Transmission Group parameters are described in later sections of this document. The transmission group supported is: dot3 {transmission 7}
2-24
TCP/IP MIB-II
2.11 SNMP MANAGEMENT GROUP
snmp {mib-2 11}
The TCP/IP SNMP Group parameters are described below. snmpInPkts
Counter Read-Only
{snmp 1}
The number of SNMP PDUs received by the ELS10-26. snmpOutPkts
Counter Read-Only
{snmp 2}
The number of SNMP PDUs created by the ELS10-26. snmpInBadVersions
Counter Read-Only
{snmp 3}
The number of SNMP PDUs received by the ELS10-26 which had an unsupported SNMP version. snmpInBadCommunityNames
Counter Read-Only
{snmp 4}
The number of SNMP PDUs received by the ELS10-26 which had an unrecognized SNMP community name. snmpInBadCommunityUses
Counter Read-Only
{snmp 5}
The number of SNMP PDUs received by the ELS10-26 which had an authentication failure. snmpInASNParseErrs
Counter Read-Only
{snmp 6}
The number of SNMP PDUs received by the ELS10-26 which had an ASN.1 parsing error while being decoded by the ELS10-26.
2-25
TCP/IP MIB-II snmpInBadTypes
Counter Read-Only
{snmp 7}
All GetResponse PDUs indicate a noSuchName ErrorStatus, since this variable is no longer used. snmpInTooBigs
Counter Read-Only
{snmp 8}
Always zero, since the ELS10-26 ignores all SNMP response PDUs. snmpInNoSuchNames
Counter Read-Only
{snmp 9}
Always zero, since the ELS10-26 ignores all SNMP response PDUs. snmpInBadValues
Counter Read-Only
{snmp 10}
Always zero, since the ELS10-26 ignores all SNMP response PDUs. snmpInReadOnlys
Counter Read-Only
{snmp 11}
Always zero, since the ELS10-26 ignores all SNMP response PDUs. snmpInGenErrs
Counter Read-Only
{snmp 12}
Always zero, since the ELS10-26 ignores all SNMP response PDUs. snmpInTotalReqVars
Counter Read-Only
{snmp 13}
The total number of MIB objects which have been successfully retrieved by the ELS10-26 as a result of SNMP GetRequest or
GetNext PDUs.
2-26
TCP/IP MIB-II snmpInTotalSetVars
Counter Read-Only
{snmp 14}
The total number of MIB objects which have been successfully altered by the ELS10-26 as a result of SNMP SetRequest PDUs. snmpInGetRequests
Counter Read-Only
{snmp 15}
The total number of SNMP GetRequest PDUs received by the
ELS10-26, which have been processed with no errors. snmpInGetNexts
Counter Read-Only
{snmp 16}
The total number of SNMP GetNext PDUs received by the
ELS10-26, which have been processed with no errors. snmpInSetRequests
Counter Read-Only
{snmp 17}
The total number of SNMP SetRequest PDUs received by the
ELS10-26, which have been processed with no errors. snmpInGetResponses
Counter Read-Only
{snmp 18}
Always zero, since the ELS10-26 ignores all SNMP response PDUs. snmpInTraps
Counter Read-Only
{snmp 19}
Always zero, since the ELS10-26 ignores all SNMP Trap PDUs. snmpOutTooBigs
Counter Read-Only
{snmp 20}
The total number of SNMP PDUs created by the ELS10-26, with a value of “tooBig” in the PDU’s “ErrorStatus”.
2-27
TCP/IP MIB-II snmpOutNoSuchNames
Counter Read-Only
{snmp 21}
The total number of SNMP PDUs created by the ELS10-26, with a value of “noSuchName” in the PDU’s “ErrorStatus”. snmpOutBadValues
Counter Read-Only
{snmp 22}
The total number of SNMP PDUs created by the ELS10-26, with a value of “badValue” in the PDU’s “ErrorStatus”. snmpOutReadOnlys
Counter Read-Only
{snmp 23}
All GetResponse PDUs indicate a noSuchName ErrorStatus, since this variable is no longer used. snmpOutGenErrs
Counter Read-Only
{snmp 24}
The total number of SNMP PDUs created by the ELS10-26, with a value of “genErr” in the PDU’s “ErrorStatus”. snmpOutGetRequests
Counter Read-Only
{snmp 25}
Always zero, since the ELS10-26 never creates any SNMP request
PDUs. snmpOutGetNexts
Counter Read-Only
{snmp 26}
Always zero, since the ELS10-26 never creates any SNMP request
PDUs. snmpOutSetRequests
Counter Read-Only
{snmp 27}
Always zero, since the ELS10-26 never creates any SNMP request
PDUs.
2-28
TCP/IP MIB-II snmpOutGetResponses
Counter Read-Only
{snmp 28}
The total number of SNMP GetResponse PDUs created by the
ELS10-26. snmpOutTraps
Counter Read-Only
{snmp 29}
The total number of SNMP Trap PDUs created by the ELS10-26. snmpEnableAuthenTraps
Integer Read-Write
{snmp 30}
Whether authentication failures should cause the ELS10-26 to generate authentication-failure Trap PDUs. Values include:
• enabled (1) - generate traps
• disabled (2) - do not generate traps
2.12 CABLETRON INTERFACE GROUP
ctIfTable {ctIf 1}
This table defines an extension to the interface table.
SYNTAX SEQUENCE OF ctIfEntry
ACCESS not accessible
STATUS mandatory ctIfEntry {ctIfTable 1}
This defines each conceptual row within the ctIfTable.
SYNTAX CtIfEntry
ACCESS not accessible
STATUS mandatory
2-29
TCP/IP MIB-II ctIfNumber {ctIfEntry 1}
This defines the interface that is being described. This is the same as IfIndex.
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory ctIfPortCnt {ctIfEntry 2}
This defines the number of ports on the interface that are being described.
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory ctIfConnectionType {ctIfEntry 3}
This defines the specific type of interface connection (BRIM, etc.).
This is defined within ctron-oids. This differs from the nature of the interface as defined by IfType as found in MIB-II.
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS mandatory ctIfLAA {ctIfEntry 4}
This object is used by a device (with Token Ring interface) to set a
Locally Administered Address (LAA) for its MAC hardware 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 will return all zeros. Any write attempt return BADVALUE. For devices that support LAA, valid values are 4000 0000 0000 to 4000 7fff ffff, and 0000 0000 0000
(a value of all zeros causes interface to use the burned in address).
A set (write) with an invalid value, returns BADVALUE. After a write, new values will only become active after the Token Ring
2-30
TCP/IP MIB-II interface has been closed and then opened again. A read of ctIfLAA will always return the same values as IfPhysAddress, 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 read of IfPhysAddress will always return the physical address currently being used by the interface.
SYNTAX OCTET STRING (SIZE (6))
ACCESS read-write
STATUS mandatory ctIfDuplex {ctIfEntry 5}
This defines the capability of the underlying hardware in supporting full duplex. This object will have a value of fullDuplex(3) if all hardware is capable of supporting full duplex operation.
SYNTAX INTEGER {other(1), standard(2), full(3)}
ACCESS read-only
STATUS mandatory
OBJECT IDENTIFIER: 1.3.6.1.4.1.52.4.3.3.2.1.1.5
The OID will actually be 1.3.6.1.4.1.52.4.3.3.2.1.1.5.X where X is the interface number requested. This is what the port is set to, NOT of what it is capable. It will report full (3) or standard (2) on ethernet ports, and other (1) for fast ethernet ports. It will report other (1) on our UART (Local Console Management or PPP) port.
ctIfCapability {ctIfEntry 6}
DESCRIPTION
Defines the capability of the underlying hardware in supporting full duplex. This object will have a value of fullDuplex (3) if all hardware is capable of supporting full duplex operation.
2-31
TCP/IP MIB-II
SYNTAX INTEGER {other (1), standard (2), fullDuplex
(3), fastEthernet (4)}
ACCESS read-only
STATUS 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 report fullDuplex (3) on our ethernet ports, and fastEthernet (4) on our fast ethernet ports. It will report other (1) on our UART (Local
Console Management or PPP) port.
2.13 CABLETRON INTERFACE PORT GROUP
ctIfPortTable {ctIfPort 1}
This table defines an extension to the interface table.
SYNTAX SEQUENCE OF ctIfPortEntry
ACCESS not accessible
STATUS mandatory
DESCRIPTION
This defines each conceptual row within the ctIfPortTable.
SYNTAX CtIfPortEntry
ACCESS not-accessible
STATUS mandatory
OBJECT IDENTIFIER: 1.3.6.1.4.1.52.4.3.3.3.1.1
INDEX ctIfPortIfNumber
2-32
TCP/IP MIB-II ctIfPortPortNumber ctIfPortPortNumber {ctIfPortEntry 1}
This defines the port that is being described.
SYNTAX INTEGER
ACCESS read-only
STATUS 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 where X is the interface number and Y is the port requested. X will increment from 1 to 28 (25 Ethernet, 2 Fast Ethernet, and the LCM port). Y will always be 1 because there is only one port per interface. We will always return a value of 1, because there is only one port on the interface.
ctIfPortIfNumber {ctIfPortEntry 2}
This defines the interface on which the port is being defined.
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
OBJECT IDENTIFIER: 1.3.6.1.4.1.52.4.3.3.3.1.1.2
The OID will actually be 1.3.6.1.4.1.52.4.3.3.3.1.1.1.X.Y where X is the interface number and Y is the port requested. X will increment from 1 to 28 (25 Ethernet, 2 Fast Ethernet, and the LCM port). Y will always be 1 because there is only one port per interface. We will return our port number, which will actually be the same as X.
2-33
TCP/IP MIB-II ctIfPortType {ctIfPortEntry 3}
DESCRIPTION
This defines the specific type of port (EPIM, TPIM). This is defined within ctron-oids.
SYNTAX OBJECT IDENTIFIER
ACCESS read-only
STATUS 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 where X is the interface number and Y is the port requested. X will increment from 1 to 28 (25 Ethernet, 2 Fast Ethernet, and the LCM port). Y will always be 1 because there is only one port per interface. This variable should describe the hardware device itself by media type and type of connection. We have an Ethernet connection to an
RJ45. This means that we will return an OID of
1.3.6.1.4.1.52.3.8.1.1.1.6 to show portRJ45 (CTRON-OIDS): oid_value_assignment.
ctIfPortLinkStatus {ctIfPortEntry 4}
This defines the status of the port connection.
SYNTAX INTEGER {notLinked(1), linked(2), notApplicable(3)}
ACCESS read-only
STATUS mandatory
OBJECT IDENTIFIER: 1.3.6.1.4.52.4.3.3.3.1.1.4
The OID will actually be 1.3.6.1.4.1.52.4.3.3.3.1.1.1.X.Y where X is the interface number and Y is the port requested. We will return the link status for the ethernet and fast ethernet ports. We will return notApplicable (3) for the UART port.
2-34
TCP/IP MIB-II
2.14 CABLETRON COM PORT CONFIGURATION GROUP
ctCpTable
This table defines a Com Port Table.
{ctIfCp 1}
SYNTAX SEQUENCE OF ctCPEntry
ACCESS not accessible
STATUS mandatory
OBJECT IDENTIFIER: 1.3.6.1.4.1.52.4.3.3.4.1
ctCpEntry {ctCpTable 1}
This defines each conceptual row within the ctCpTable.
SYNTAX ctCpEntry
ACCESS not accessible
STATUS mandatory
OBJECT IDENTIFIER: 1.3.6.1.4.1.52.4.3.3.4.1.1
INDEX ctComPort ctComPort {ctCpEntry 1}
This is the index into the Com Port Table and defines the Com Port that is being described. com1 = 1, com2 = 2.
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
OBJECT IDENTIFIER: 1.3.6.1.4.1.52.4.3.3.4.1.1.1
We only have one UART port. This means the OID will always be
OBJECT IDENTIFIER: 1.3.6.1.4.1.52.4.3.3.4.1.1.1.1, and we will always return a value of 1.
2-35
TCP/IP MIB-II ctCpFunction {ctCpEntry 2}
DESCRIPTION
This defines the Com Port Function supported by that Com Port.
SYNTAX INTEGER {lm(1), ups(2), slip(3), ppp(4)}
ACCESS read-write
STATUS 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 UART port. We support LM and PPP simultaneously. If we detect a PPP packet we do negotiations and enter into PPP mode. As long as PPP keeps live messages we’ll stay there. If they don’t we revert back to VT100 emulation. We will sample the port at the time the request comes in and return a value of LM (1), or
PPP (4) depending on what state the port is in at the time of the request.
ctIfNum {ctCpEntry 3}
DESCRIPTION
This defines the interface that is being described. This is the same as ifIndex. This is only valid if ctCpFunction is PPP, otherwise 0.
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
OBJECT IDENTIFIER: 1.3.6.1.4.1.52.4.3.3.4.1.1.3
The OID will actually be 1.3.6.1.4.1.52.4.3.3.4.1.1.3.1 because we only have the one UART port. We will return our port number for the UART port.
2-36
TCP/IP MIB-II ctCpAdminStatus {ctCpEntry 4}
DESCRIPTION
The administrative state of the Com Port.
SYNTAX INTEGER {disabled(1), enabled(2)}
ACCESS read-only
STATUS 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 UART port.
We don’t allow this port to be turned on or off. Because of this, it will be READ-ONLY.
It will always return enabled (2).
2.15 SNMP VERSION GROUP
enableSNMPv1 Not Supported {ctSNMP 1}
This object allows control over the SNMPv1 protocol. If set to a value of disable(1) then the SNMPv1 protocol will not be accepted by the device.
SYNTAX INTEGER {disabled(1), enabled(2)}
ACCESS read-write
STATUS mandatory enableSNMPv2 Not Supported {ctSNMP 2}
This allows control over the SNMPv2 protocol. If set to a value of disable(1) then the SNMPv2 protocol will not be accepted by the device.
SYNTAX INTEGER {disabled(1), enabled(2)}
ACCESS read-write
2-37
TCP/IP MIB-II
STATUS mandatory
2.16 TRAP DESCRIPTION
InterfacePortInsertion Not Supported.
Specific Trap Type Code - 0x1A0
This trap will be generated when it is detected that an interface port has been inserted. The information will include: ctIfPortNumber ctPortType
Specific Trap Type Code - 0x1A1
This trap will be generated when it is detected that an interface port has been removed. The information will include: ctIfNumber ctIfPortPortNumber
{ctIfEntry 1}
{ctIfPortEntry 1}
InterfacePortLinkUp
{ctIfPortEntry 1}
{ctIfPortEntry 3}
Specific Trap Type Code - 0x1A2
This trap will be generated when it is determined that a port on a strictly bridging interface (not “repeater”) has been connected to a
LAN. This is only appropriate for ports that support the concept of a link state. The information will include: ctIfNumber ctIfPortPortNumber
{ctIfEntry 1}
{ctIfPortEntry 1}
2-38
TCP/IP MIB-II
InterfacePortLinkDown
Specific Trap Type Code - 0x1A3
This trap will be generated when a previously attached bridging port has been disconnected from a LAN. This is only appropriate for ports that support the concept of a link state. The information will include: ctIfNumber {ctIfEntry 1} ctIfPortPortNumber {ctIfPortEntry 1}
This trap will be sent when a link goes down.
2.17 CABLETRON MIB 2 EXTENSIONS
ctmib2-ext-mib Cabletron’s extension to the MIB-II
This module provides authoritative definitions for part of the naming tree below: cabletron {enterprises 52}
This module will be extended, as additional sub-sections of this naming tree are defined.
IMPORTS ctronMib2FROM CTRON-MIB-NAMES OBJECT-TYPE
FROM RFC-1212
Textual Convention
DisplayString ::= OCTET STRING
This data type is used to model textual information from the NVT
ASCII character set. By convention, objects of this syntax are declared as having: SIZE (0.255)
2-39
TCP/IP MIB-II
This MIB defines Cabletron extensions to MIB-II. Groups within this MIB refer to the group in which the objects pertain within
MIB-II.
Groups within this MIB are: commonDevOBJECT IDENTIFIER ctIfPortOBJECT IDENTIFIER
{ctronMib2 1}
{ctronMib2 2} ctIfPortOBJECT IDENTIFIER ctIfCpOBJECT IDENTIFIER
{ctronMib2 3}
{ctronMib2 4} ctSNMP OBJECT IDENTIFIER {ctronMib2 5} ctSONET OBJECT IDENTIFIER {ctronMib2 6}
The commonDevice group of this group is an extension to the system group MIB2. It contains similar information to that defined within the system group of MIB-II.
Implementation of this group is optional for Cabletron devices.
comDeviceTime
OBJECT-TYPE
SYNTAX DisplayString(SIZE (8))
ACCESS
STATUS
DESCRIPTION read-write mandatory
The current time of day, in 24 hour format, as measured by the device.
The representation shall use the standard HHMMSS format.
::= {commonDev 1} comDeviceDate
2-40
TCP/IP MIB-II
OBJECT-TYPE
SYNTAX DisplayString(SIZE (8))
ACCESS
STATUS
DESCRIPTION read-write mandatory
The current date, as measured by the device. The representation shall use the standard MMDDYY format.
::= {commonDev 2} comDeviceBoardMap
OBJECT-TYPE
SYNTAXINTEGER
ACCESS
STATUS
DESCRIPTION read-only mandatory
Contains a bit encoded representation of slots that contain MIM boards. If a bit is one, then that slot is occupied by a board.
::= {commonDev 3} ctIF group implementation of this group is optional.
The ctIf group contains information about the type of interface, i.e. the type of BRIM etc. This information is not available in the interface group of MIB-II.
ctIfTable
OBJECT-TYPE
SYNTAXSEQUENCE OF CtIfEntry
ACCESS
STATUS
DESCRIPTION not accessible mandatory
This table defines an extension to the interface table.
2-41
TCP/IP MIB-II
::= {ctIf 1} ctIfEntry
OBJECT-TYPE
SYNTAXCtIfEntry
ACCESS
STATUS
DESCRIPTION
INDEX not accessible mandatory
This defines each conceptual row within the ctIfTable.
{ctIfNumber}
::= {ctIfTable 1}
CtIfEntry::=
SEQUENCE
{ctIfNumber INTEGER, ctIfPortCnt INTEGER, ctIfConnectionType OBJECT IDENTIFIER, ctIfLAA OCTET STRING, ctIfDuplex INTEGER, ctIfCapability INTEGER, ctIfRedundancy INTEGER } ctIfNumber
OBJECT-TYPE
SYNTAXINTEGER
ACCESS
STATUS
DESCRIPTION read-only mandatory
This defines the interface that is being described. This is the same as ifIndex.
2-42
TCP/IP MIB-II
::= {ctIfEntry 1} ctIfPortCnt
OBJECT-TYPE
SYNTAXINTEGER
ACCESS
STATUS
DESCRIPTION
INDEX read-only mandatory
This defines the number of ports on the interface that is being described.
{ctIfNumber}
::= {ctIfEntry 2} ctIfConnectionType
OBJECT-TYPE
SYNTAXOBJECTIDENTIFIER
ACCESS
STATUS
DESCRIPTION
INDEX read-only mandatory
Defines the specific type of interface connection (BRIM etc.). This is defined within ctron-oids. This differs from the nature of the interface as defined by ifType as found in
MIB-II.
{ctIfNumber}
::= {ctIfEntry 3} ctIfLAA
OBJECT-TYPE
SYNTAXOCTET STRING (SIZE (6))
ACCESS read-write
2-43
TCP/IP MIB-II
STATUS
DESCRIPTION mandatory
This object is used by a device (with a Token Ring interface) to set a
Locally Administered Address
(LAA) for its MAC hardware 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 will return all zeroes any write attempt will return BADVALUE
For devices that suport LAA: valid values are 4000 0000 0000 to 4000 7fff ffff, and 0000
0000 0000 (a value of all zeroes causes interface to use the burned-in address).
a set (write) with an invalid value returns BADVALUE.
after a write, new values will only become active after
Token Ring interface has been closed and then opened again.
a read of ctIfLAA will always return the same value as ifPhysAddress, except in the case where; o ctIfLAA has been set, but interface has not yet been closed and re-opened. In this case the last set value is returned.
Note that a read of ifPhysAddress will always return the physical address currently being used by the interface.
::= {ctIfEntry 4} ctIfDuplex
OBJECT-TYPE
SYNTAXINTEGER {other (1), standard (2), full (3)}
ACCESS read-write
2-44
TCP/IP MIB-II
STATUS
DESCRIPTION mandatory
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 return standard (2).
any write attempt will return BADVALUE.
fast ethernet devices will report other (1).
::= {ctIfEntry 5} ctIfCapability
OBJECT-TYPE
SYNTAXINTEGER {other (1), standard (2), full duplex
(3), fastEthernet (4)}
ACCESS read-only
STATUS
DESCRIPTION mandatory
Defines the capability of the underlying hardware in supporting full duplex. This object will have a value of fullDuplex (3) if all hardware is capable of supporting full duplex operation.
::= {ctIfEntry 6} ctIfRedundancy
OBJECT-TYPE
SYNTAXINTEGER {redundant (1), not-redundant (2)}
ACCESS read-only
STATUS mandatory
2-45
TCP/IP MIB-II
DESCRIPTION Defines whether or not an interface supports redundancy.
::= {ctIfEntry 7} ctIfPort group implementation of this group 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. ctIfPortTable
OBJECT-TYPE
SYNTAXSEQUENCEOF CtIfPortEntry
ACCESS not accessible
STATUS
DESCRIPTION
INDEX mandatory
This defines each conceptual row within the ctIfPortTable.
{ctIfPortNumber} ctIfPortPortNumber
::= {ctIfPortTable 1} ctIfPortEntry
OBJECT-TYPE
SYNTAX
ACCESS
STATUS
DESCRIPTION
INDEX
{CtIfPortPortNumber} not accessible mandatory
This defines each conceptual row within the ctIfPortTable.
{ctIfPortNumber} ctIfPortPortNumber
2-46
TCP/IP MIB-II
::= {ctIfPortTable 1} ctIfPortEntry::=
SEQUENCE
{ctIfPortPortNumber INTEGER, ctIfPortIfNumber INTEGER, ctIfPortType OBJECT IDENTIFIER, ctIfPortLinkStatus INTEGER} ctIfPortPortNumber
OBJECT-TYPE
SYNTAX
INTEGER
ACCESS
STATUS
DESCRIPTION read-only mandatory
This defines the port being described.
::= {ctIfPortEntry 1} ctIfPortIfNumber
OBJECT-TYPE
SYNTAX
INTEGER
ACCESS
STATUS
DESCRIPTION read-only mandatory
This defines the interface that the port being described is on.
2-47
TCP/IP MIB-II
::= {ctIfPortEntry 2} ctIfPortType
OBJECT-TYPE
SYNTAX
ACCESS
STATUS
DESCRIPTION
OBJECT IDENTIFIER read-only mandatory
Defines the specific type of the port
(EPIM,TPIM). This is defined within ctron oids.
::= {ctIfPortEntry 3} ctIfPortLinkStatus
OBJECT-TYPE
SYNTAX
INTEGER
ACCESS
STATUS
DESCRIPTION
{not linked (1), linked (2), notApplicable (3).} read-only mandatory
Defines the status of the port connection.
::= {ctIfPortEntry 4} ctIfPort group implementation of this group is optional
The ctIfCp group contains information about the com port configuration on the MMAC Management Modules (i.e., EMME,
TRMM) and on the MMAC-Plus Environmental Module.
ctCpTable
OBJECT-TYPE
SYNTAXSEQUENCEOF CtIfCpEntry
2-48
TCP/IP MIB-II
ACCESS
STATUS
DESCRIPTION
::= {ctIfCp 1} ctCpEntry
OBJECT-TYPE
SYNTAX
ACCESS
STATUS
DESCRIPTION not accessible mandatory
This table defines a Com Port Table.
CtCpEntry not accessible mandatory
This defines each conceptual row within the ctCpTable.
{ctComPort} INDEX
::= {ctCpTable 1} ctCpEntry::=
SEQUENCE
{ctComPort INTEGER, ctCpFunction INTEGER, ctIfNum INTEGER, ctCpAdminStatus INTEGER} ctComPort
OBJECT-TYPE
SYNTAXINTEGER
ACCESS
STATUS
DESCRIPTION read-only mandatory
This is the index into the Com Port
Table and defines the Com Port that
2-49
TCP/IP MIB-II is being described. com1 = 1, com2 = 2
{ctCpEntry 1} ctCpFunction
OBJECT-TYPE
SYNTAXINTEGER {lm(1), Local Management (default), ups (2) UPS, slip (3) SLIP, ppp
(4) PPP}
ACCESS
STATUS
DESCRIPTION read-write mandatory
Defines the Com Port Function supported by that Com Port.
{ctCpEntry 2} ctIfNum
OBJECT-TYPE
SYNTAXINTEGER
ACCESS
STATUS
DESCRIPTION read-only mandatory
This defines the interface that is being described. This is the same as ifIndex. This is only valid if ctCp-
Function is SLIP or PPP, otherwise 0.
{ctCpEntry 3} ctCpAdminStatus
OBJECT-TYPE
SYNTAXINTEGER {disabled (1), enabled (2) (default)}
ACCESS read-write
2-50
TCP/IP MIB-II
STATUS
DESCRIPTION mandatory
The administrative state of the Com
Port.
{ctCpEntry 4}
The SNMP group. Implementation of this group is mandatory when the SNMPv2 protocol is present within the device.
enableSNMPv1
OBJECT-TYPE
SYNTAXINTEGER {disable (1), enable (2)}
ACCESS read-write
STATUS
DESCRIPTION mandatory
This object allows control over the
SNMPv1 protocol. If set to a value of disable (1) then the SNMPv1 protocol will not be accepted by the device.
{ctSNMP 1} enableSNMPv2
OBJECT-TYPE
SYNTAXINTEGER {disable (1), enable (2)}
ACCESS
STATUS
DESCRIPTION read-write mandatory
This object allows control over the
SNMPv2 protocol. If set to a value of disable (1) then the SNMPv2 protocol will not be accepted by the device.
2-51
TCP/IP MIB-II
{ctSNMP 2}
{ctSNMP 3} is obsolete
The ctSonet group is an optional group. It contains information pertaining to the optical connectivity speed.
ctSonetEntry
OBJECT-TYPE
SYNTAXSEQUENCEOF CtSonetEntry
ACCESS not accessible
STATUS
DESCRIPTION
INDEX mandatory
This table defines the Sonet table.
{ctSonetIfIndex}
{ctSonetTable 1}
CtSonetEntry::=
SEQUENCE
{ctSonetIfIndex INTEGER, ctSonetMediumType INTEGER} ctSonetIfIndex
OBJECT-TYPE
SYNTAX
INTEGER
ACCESS
STATUS
DESCRIPTION read-only mandatory
This defines the interface being described. It is the same as IfIndex.
2-52
TCP/IP MIB-II
{ctSonetEntry 1} ctSonetMediumType
OBJECT-TYPE
SYNTAX
INTEGER
ACCESS
STATUS
DESCRIPTION
{sonet (1), sdh (2)} read-write mandatory
This variable identifies whether a
SONET or an SDH signal is used across this interface.
{ctSonetEntry 2}
Trap description
InterfacePortInsertion
Specific Trap Type Code- 0x1A0
This trap will be generated when it is detected that an interface port has been inserted. The interesting information will include: ctIfNumber {ctIfEntry 1}, ctIfPortPortNumber
{ctIfPortEntry 1}, ctIfPortType
{ctIfPortEntry 3}
Trap description
InterfacePortInsertion
Specific Trap Type Code - 0x1A1
This trap will be generated when it is determined that a port has been removed. The interesting information will include: ctIfNumber {ctIfEntry 1}, ctIfPortPortNumber
{ctIfPortEntry 1},
Trap description
InterfacePortLinkUp
2-53
TCP/IP MIB-II
Specific Trap Type 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}, ctIfPortPortNumber
{ctIfPortEntry 1},
Trap description
InterfacePortLinkDown
Specific Trap Type Code - 0x1A3
2-54

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