Enterasys atx Verweisanleitung

 

Introduction

 

The get command would look like:

 

get 1.3.6.1.4.1.97.2.9.2.0

 

At the beginning of each chapter in this Reference Guide, the prefix for each MIB 
group is provided. To calculate the specific MIB variable, you add the specific 
object ID to the prefix for that MIB group. 

 

TFTP (Trivial File Transfer Protocol, RFC 1350) is used for:

•

Distribution of new software. 

TFTP has no inherent security provision; however, all files have special data 
encryption, and the ATX will reject files that have not been encrypted. In 
addition, SNMP primitives may be used to prevent the ATX from accepting 
unauthorized TFTP requests, even if the files have the special data encryption. 
Refer to the description of the swdis branch of Cabletron’s private MIB for TFTP 
security details. 

 

TFTP is used for the distribution of new software. The new software will be 
automatically invoked when a ATX reboots. 

New software is released in two files:

•

dnld_hdr

•

dnld_software

To distribute the new software to a ATX, the TFTP procedure is as follows: 

1.

Start TFTP on the NMS, or on any other device which can provide TFTP 
services. (Typically, TFTP must be started from the same directory that 
contains the files to be transferred.) TFTP must be told the IP address of the 
remote host (the IP address of the ATX), and the file transfer mode (which 
must be “binary”). 

2.

Use TFTP to retrieve all of the unit’s parameters, as descibed in a subsection 
below. This step is not required, but it is recommended if you need to 
back-pedal to the software that is currently being executed by the unit.

3.

Tell TFTP to transfer (“put”) the first file, (dnld_hdr). 

4.

Wait at least three minutes, or until the unit sends the SNMP Trap described 
in the swdis branch of Cabletron’s private MIB.