I am trying to automate the management of our Atlases as we have over 20 in our system.
I found that it is possible to use SNMP to request a configuration transfer to a TFTP server. This works well for 800Plus, 550, and 830 but amazingly, not for 890, at least not at the OID the MIB says it should be at.
Am I doing something wrong or did this feature get omitted from the 890?
Using a freeware SNMP tool called SNMPSET to push in the values here are the OID’s necessary to initiate a backup.
I’m also setting the date and time (which works well for all models.) Otherwise the clock drifts and also needs to be set at each time change. Too bad Atlases don't support NTP time sources.
Note:
%atlas% is the IP address of the Atlas being managed.
%backupfile% is the name of the file to backup the configuration to.
----
rem set The IP address of the TFTP server.
snmpset -c:"mycommunitystring" -v:1 -r:%atlas% -o:.1.3.6.1.4.1.664.2.154.1.5.3.2.1.0 -tp:ip -val:"mytftpserver"
rem The name of the file to transfer to the TFTP server.
snmpset -r:%atlas% -c:"mycommunitystring" -o:.1.3.6.1.4.1.664.2.154.1.5.3.2.2.0 -tp:str -val:"%backupfile%"
rem Set value to 1 to transfer the configuration file to the TFTP server.
snmpset -c:"mycommunitystring" -v:1 -r:%atlas% -o:.1.3.6.1.4.1.664.2.154.1.5.3.2.6.0 -tp:int -val:"1"
REM set Time and Date
REM Works for all Atlas Models
set RUNTME=%time:~0,5%
Set RUNTME=%RUNTME: =0%
snmpset -c:"mycommunitystring" -v:1 -r:%atlas% -o:.1.3.6.1.4.1.664.2.155.1.1.0 -tp:str -val:"%RUNTME%"
snmpset -c:"mycommunitystring" -v:1 -r:%atlas% -o:.1.3.6.1.4.1.664.2.155.1.2.0 -tp:str -val:"%date:~4,2%-%date:~7,2%-%date:~12,2%"
