- 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

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 ELS10-26 is ready for the second file,
which will be somewhat shorter than three minutes.)
5. Tell TFTP to transfer the second file, (dnld_software). This
transfer should take approximately one minute.
The initial one minute waiting may be omitted and this second
transfer may be initiated immediately following the first
transfer; however, that causes the second transfer to take
approximately two minutes, and creates a slightly heavier
network load during the file transfer.
Note:
If the above TFTP sequence is abnormally terminated, there is no
cause for alarm, since the ELS10-26 maintains a back-up set of
software, and the ELS10-26 will not use the incomplete new
software.
Older versions of software may be distributed to an ELS10-26,
provided that the older software is at least Version 2.3. To
distribute the older software to an ELS10-26, the above TFTP
procedure should be altered, with the following step being
performed before the older software is distributed.
If the bulk retrieval of all of the parameters of the ELS10-26 had
been performed while the ELS10-26 was executing that older
software, that retrieved file should be used to do a bulk set of all
parameters (as described below). Otherwise, when the older
software is distributed and the ELS10-26 reboots, the older
software will not understand the format of the ELS10-26’s
parameters.
2










