- Cabletron IP Router Reference Guide
Table Of Contents
- Title Page
- Notice
- Contents
- Introduction
- TCP/IP MIB-II
- 2.1 System Group
- 2.2 Interfaces Group
- 2.3 Address Translation Group
- 2.4 IP Group
- 2.5 ICMP Group
- 2.6 TCP Group
- 2.7 UDP Group
- 2.8 EGP Group
- 2.9 OIM Subtree
- 2.10 Transmission Group
- 2.11 SNMP Management Group
- 2.12 Enterasys Interface Group
- 2.13 Enterasys Interface Port Group
- 2.14 Enterasys Com Port Configuration Group
- 2.15 SNMP Version Group
- 2.16 Trap Description
- 2.17 Enterasys MIB 2 Extensions
- Ethernet MIB
- Bridge MIB
- PPP MIB
- ELS10-26 MIB
- 6.1 System Group
- 6.1.1 Hardware Configuration Group
- 6.1.2 LXSW Configuration Group
- 6.1.3 Administration Group
- 6.1.4 Software Distribution Group
- 6.1.5 Addresses Configuration Group
- 6.1.6 Enterasys Interfaces Group
- 6.1.7 Enterasys Dot3 Group
- 6.1.8 Enterasys UART Interface Group
- 6.1.9 Enterasys Protocol Group
- 6.1.10 Enterasys Trunking Group
- 6.1.11 Enterasys Workgroup Management Group
- 6.1.12 Enterasys Trap Management Group
- 6.1.13 Ping Management MIB
- 6.1.14 Traceroute
- 6.1.15 Traceroute Management MIB
- 6.1.16 Port Mirroring
- 6.1 System Group
- Traps

ELS10-26 MIB
6-41
::= {lxpingEntry 12}
lxpingNumReceived OBJECT-TYPE
SYTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION The number of ICMP
ECHO_RESPONSE messages
that have been received as a
result of this ping request.
::= {lxpingEntry 13}
6.1.14 Traceroute
An implementation of traceroute was added in order to add the
ability to orginate a traceroute request from the ELS10-26. The
request can be started from LCM, or from SNMP. If the request is
originated from the LCM, the results are printed out on the LCM
console.
The LCM command is as follows:
traceroute [-m max_ttl] [-q nqueries] [-w wait] host_IP
[data_size]
The traceroute MIB has a variable which indicates the amount of
time the results of a traceroute request is accessible from SNMP. It
also has a table, indexed by NMS IP address, ping destination IP
address, hop count, and probe count which is used to start the
traceroute request and fetch the results. Each entry in the table will
contain the round trip time and state of each particular probe in
each hop.










