Unsolved
This post is more than 5 years old
2 Posts
0
29112
November 15th, 2010 09:00
PowerConnect 5448 Copying Config Via SNMP
I am trying to copy the running-config to/from tftp and to startup-config via SNMP.
Here is the command I'm running:
snmpset -v 2c -c public 10.10.10.2 .1.3.6.1.4.1.89.87.4.1.7 i 2 .1.3.6.1.4.1.89.87.4.1.8 i 3 .1.3.6.1.4.1.89.87.4.1.9 a '10.10.10.50' .1.3.6.1.4.1.89.87.4.1.11 s 'test' .1.3.6.1.4.1.89.87.4.1.16 i 1
And the error I'm getting is:
Error in packet.
Reason: resourceUnavailable (This is likely a out-of-memory failure within the agent)
Failed object: SNMPv2-SMI::enterprises.89.87.4.1.7
I believe I've seen that error before from these Dell switches when trying to set VLANs. I was supposed to simultaneously set another object. Therefore I assume I am supposed to specify the rlCopyRowStatus object first. Is this the OID for that?
.1.3.6.1.4.1.89.87.4.1.6 and how do i use that? Is it an integer or string or other value type?
If I am way out in left field on how to go about copying the the config via snmp, please let me know.
Any help is appreciated.
0 events found
No Events found!
vt1012
212 Posts
0
November 15th, 2010 13:00
What version of the firmware and MIB are you using for the 5448? Have you tried using the tftp MIB located at .1.3.6.1.4.1.89.26.5?
-v
gnfmike
2 Posts
0
November 15th, 2010 15:00
I tried looking into the tftp MIB. I've found the OIDs for it, but I don't see anything in particular to start a tftp copy. My best guess resulted in errors.
$ snmpset -v 2c -c public 10.10.10.2 .1.3.6.1.4.1.89.26.5.1.0 i 15 .1.3.6.1.4.1.89.26.5.2.0 i 60 .1.3.6.1.4.1.89.26.5.3 s 'running-config' .1.3.6.1.4.1.89.26.5.4.0 s 'testtest' .1.3.6.1.4.1.89.26.5.6.0 a 10.10.10.54
Error in packet.
Reason: resourceUnavailable (This is likely a out-of-memory failure within the agent)
Failed object: SNMPv2-SMI::enterprises.89.26.5.3
Do you have any insight on how to use the TFTP MIB? Or perhaps a link to Dell documentation on it?
As far as the firmware version, if the firmware version is the same as the HW version, I'm running 00.00.02. Here is the show version output.
sw01# show version
SW version 2.0.0.35 ( date 27-Jan-2009 time 18:13:34 )
Boot version 2.0.0.0 ( date 12-Nov-2008 time 12:56:52 )
HW version 00.00.02
The MIB I was trying to use is the rlCopy, which I believe to be at .1.3.6.1.4.1.89.87
vt1012
212 Posts
0
November 16th, 2010 06:00
I found this link that appears to explain each oid in the table: http://www.thesafehouse.org/forums/showthread.php?t=26742
Here are some of the details....
I also just re-run my test script for downloading the running-config file from the switch to a remote TFTP server and also to copy the active image to a remote server using SNMP and it works for me.
This is basically what my script does - it use a single SNMP set request using the "rowstatus" create&go method. The script specifies all the following parameters in the request (there are a few others which I didn't use in this script - see the MIB for more info on the other variables):
* set rlCopySourceLocation = set this to the source type (e.g. I set source to local for my testing - see MIB for more info).
* set rlCopySourceUnitNumber = set this to the unit # of the switch in the stack or set to 1 if you are not running stacking.
* set rlCopySourceFileType = set this to the type of file to copy (e.g. running-config or image - see MIB for more info).
* set rlCopyDestinationLocation = set this to the destination type (e.g. I set destination to tftp).
* set rlCopyDestinationIpAddress = set this to the IP address of the TFTP server if you are doing TFTP copy.
* set rlCopyDestinationFileName = set this to the name of the destination file.
* set rlCopyHistoryIndex = set this if you want the history of the copy to be retained (you need a unique history index so use the next free index variable - see MIB).
* set rlCopyRowStatus = set this to "create&go" (value = 4) to create the row in the table and start the copy.
Note that the copy succeed really fast when copying a configuration file and when it completes the row is removed so if you want history save it in the history table. If you copy an image then the row may stay around awhile so you can poll status while the copy executes.
Anyway, my script works so this table is fine. The OID you had was correct - my mistake - I was hand creating the OID (I don't use browser - hand scripting using shell scripts :-)) manually and made a mistake in the encoding.
Cuong.