Unsolved
This post is more than 5 years old
9 Posts
0
44714
February 17th, 2014 19:00
Copy Running-config startup-config via SNMP (7048/8024)
Hi,
I'm looking for a way to copy our running-config to startup-config via SNMP on our newer powerconnect switches at regular intervals, it's a requirement for PCI compliance.
I've found links on how to do this for older switches via the rlcopy.mib, but this doesn't seem to exist on the newer switches.
I've also found links on how to copy the running-config via tftp using the fastpath switching MIB on the newer switches, which is useful but not quite what I want.
So basically is there a way to issue a series of SNMP commands to copy the running-config to startup-config? My skill in reading the 100 odd MIB files that make up the MIB suite on the newer powerconnects is not up to par.



jskurray
9 Posts
0
February 17th, 2014 21:00
I think I'm getting somewhere with the Dell-LAN-SYSMNG-MIB (.1.3.6.1.4.1.674.10895.5000.1.2 in Dell_SysMng.Rev_1_1.my) but the part of this MIB that does the file copy doesn't seem to exist on the switches despite being in the MIB specification (Everything under dellLanFileSysGroup). Has anyone had any luck with this?
Our switches are on firmware version 4.1.1.9, does this work for anyone on later firmware maybe?
DELL-Josh Cr
Moderator
•
9.4K Posts
0
February 18th, 2014 08:00
Hi,
Can you update to the latest firmware? There are newer mibs included with the newer updates For the 7000 series along with some bug fixes related to them. http://www.dell.com/support/drivers/us/en/04/Product/powerconnect-7024
jskurray
9 Posts
0
February 18th, 2014 16:00
Hi Josh,
We have a 8024-K blade switches in our chassis running version 5.1.0.1 and they exhibit the same behaviour. I'm fairly sure that the MIB implementation isn't on the switches, although it's possible I'm just doing it wrong as I'm working it out on the fly. Basically if I run an SNMPWalk to the 8024-K then I see information for other modules at an equivalent tier of the tree as the actions I want but not in the spot I need. Here's an example:
[user@server ~]# snmpwalk <8024-K IP> -v3 .1 -u -A -x DES -a MD5 -X -c test -l Auth .1.3.6.1.4.1.674.10895.5000
SNMPv2-SMI::enterprises.674.10895.5000.1.2.1.1.0 = INTEGER: 1
SNMPv2-SMI::enterprises.674.10895.5000.1.2.1.2.0 = ""
SNMPv2-SMI::enterprises.674.10895.5000.1.2.3.1.0 = INTEGER: 0
SNMPv2-SMI::enterprises.674.10895.5000.1.2.3.2.0 = STRING: "image1"
SNMPv2-SMI::enterprises.674.10895.5000.1.2.3.2.0 = No more variables left in this MIB View (It is past the end of the MIB tree)
The SNMP view for this user is as follows:
snmp-server view "manage" dellLanSystemMng included
This module is where the management capabilities should be. I've tried SNMP 3 and 2C and neither work. What's the deal here? Can I do it via another option? Even if I can't kick off a copy is there an MIB somewhere that just says if the startup/running config are different?
DELL-Josh Cr
Moderator
•
9.4K Posts
0
February 19th, 2014 08:00
There doesn’t seem to be a copy command in the snmp mibs for these switches, there is a configChanged snmp that would tell you if something changed in the configuration.
jskurray
9 Posts
0
February 19th, 2014 15:00
Thanks Josh. Hopefully that's something that gets implemented in the future as it's in the Dell MIBs. For now I've had to just write an expect script to do this
jskurray
9 Posts
0
February 20th, 2014 17:00
Josh, do you have the MIB path/Name of that config changed check? Is it a trap?
Better yet is there an SNMP reference guide for powerconnects, I can't find one.
Cheers
DELL-Josh Cr
Moderator
•
9.4K Posts
0
February 21st, 2014 07:00
I found it with a mib viewer, the OID is .1.3.6.1.4.1.674.10895.520
It is under Dell-LAN-TRAP-MIB. There isn't a guide that I know of for SNMP for powerconnect.
Kenneth Fortner
1 Message
0
August 20th, 2019 12:00
Not sure if it works on the 7048/8024 but the current MIB has this OID that will do it.
Name: agentSaveConfig
OID: .1.3.6.1.4.1.674.10895.5000.2.6132.1.1.1.3.1
MIB: DNOS-SWITCHING-MIB
Syntax: INTEGER {enable(1),
disable(2)
}
Description: enable(1) will initiate an configuration save to nvram.
Status is returned by the object agentSaveConfigStatus.