beautypg.com

Using snmp to manage files and software, Copy a file to or from a tftp server – Allied Telesis AlliedWare Plus Operating System Version 5.4.4C (x310-26FT,x310-26FP,x310-50FT,x310-50FP) User Manual

Page 1778

background image

SNMP Introduction

Software Reference for x310 Series Switches

67.20

AlliedWare Plus

TM

Operating System - Version 5.4.4C

C613-50046-01 REV A

Using SNMP to Manage Files and Software

The Allied Telesis Enterprise MIB (

Chapter 69, SNMP MIBs

) includes objects for managing

files and software on the switch. This section includes procedures for using MIB objects on
the switch to perform some common tasks, via an SNMP management application:

“Copy a File to or from a TFTP Server” on page 67.20

“Upgrade Software and Configuration Files” on page 67.22

For more details about the Allied Telesis Enterprise MIB and public MIBs on the switch, see

Chapter 69, SNMP MIBs

.

Copy a File to or from a TFTP Server

Use this procedure to copy a file (for example, a software version file) to the switch from a
TFTP server, or to copy a file (for example, a configuration file) from the switch to a TFTP
server. The MIB objects in this procedure reside in the module atFilev2 { modules 600 },
with object ID 1.3.6.1.4.1.207.8.4.4.4.600

.

For detailed descriptions of the MIB objects used

in this procedure, and other file management MIB objects, see

“AT-FILEv2-MIB” on

page 69.32

.

Other MIB objects can be used in a similar way for moving and deleting files

on the switch.

Table 67-5: Procedure for copying a file to or from a device using a TFTP server

Do this ...

By setting or reading this
MIB object ...

Whose object ID is ...

To this value ...

1.

If the source device is part
of a stack, set the stack
ID.For a standalone switch,
keep the default value, 1.

atFilev2SourceStackId

{ atFilev2Operation 1 }

<stack-id>

2.

If the destination device is
part of a stack, set the
stack ID.

atFilev2DestinationStackId

{ atFilev2Operation 4 }

<stack-id>

3.

Set the source device.

atFilev2SourceDevice

{ atFilev2Operation 2 }

4 (TFTP) or
1 (Flash)

4.

Set the destination device.

atFilev2DestinationDevice

{ atFilev2Operation 5 }

4 (TFTP) or
1 (Flash)

5.

Set the source filename.
Include the path (if any)
but not the device.

atFilev2SourceFileName

{ atFilev2Operation 3 }

<source-filename>
e.g. /awp/config/
admin.cfg

6.

Set the destination
filename. Include the path
(if any) but not the device.

atFilev2DestinationFileName

{ atFilev2Operation 6 }

<dest-filename>
e.g. /config/admin.cfg