- 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-5
lxswCount {lxswFilesetEntry 3}
Integer Read-Only
The number of files in the file set. This number may range from 1
to 255.
lxswType {lxswFilesetEntry 4}
Octet String Read-Only
The types of files within the file set. The size of lxswType may be
determined by lxswCount, since 1 octet is required for each file.
The possible file types are:
• file-nam (1) - the operational software for the ELS10-26’s NAM
processor.
• file-powerup (10) - power-up diagnostics for the entire
ELS10-26.
• file-diagnostics (11) - manufacturing diagnostics for the entire
ELS10-26.
lxswSizes {lxswFilesetEntry 5}
Octet String Read-Only
An array (4 octets per file), containing the size of each of the files.
Each size is encoded as a series of 4 bytes, which should be
converted into a 32-bit integer.
lxswStarts {lxswFilesetEntry 6}
Octet String Read-Only
An array (4 octets per file), containing the software’s execution
starting address of each of the files. Each address is encoded as a
series of 4 bytes, which should be converted into a 32-bit integer.










