Unsolved
This post is more than 5 years old
7 Posts
0
41614
Bug in the fastpath-switching-mib on M6220?
Hi,
with the recent upgrade of the firmware (v3.1.2.5) on the M6220 PowerConnect,
i'm not able to backup configuration with snmp anymore.
Before the upgrade, i was able to backup with the following command:
/usr/bin/snmpset $options -c $community -m FASTPATH-SWITCHING-MIB $ip agentTransferUploadServerAddress.0 = $tftpserver agentTransferUploadFilename.0 = $file_name agentTransferUploadDataType.0 i 3 agentTransferUploadStart.0 i 1
With the new mib, i do the following (with agentTransferUploadServerAddressType, agentTransferUploadServerAddress):
/usr/bin/snmpset -v 2c -c $community -m FASTPATH-SWITCHING-MIB $ip agentTransferUploadMode.0 = 1 agentTransferUploadFilename.0 = "test.cfg" agentTransferUploadDataType.0 i 3 agentTransferUploadStart.0 i 1 agentTransferUploadServerAddressType.0 = 1 agentTransferUploadServerAddress.0 = $tftpserver
And i receive error 11.
Any hints?
DELL-Victor
98 Posts
0
February 8th, 2010 14:00
The new firmware version 3.1.2.8 that came out last week seems to work. It is not perfect either, but will allow you can backup your startup config to a tftp server. You will use the same parameters you are using now, only for the agentTransferUploadDataType you will need to use code (2) instead of config (3). This is still a bug that needs to be fixed, but for now this is the work-around.
# 292209 has been opened to address this issue.
The work-around (backup file mentioned above and crossed out) has been found to contain special characters. Attempting to restor it gives a return code of 6: invalidConfigFile. See other possible work-arounds below (using CLI, HTTP, or OMNM)
jenfi
7 Posts
0
February 10th, 2010 14:00
Hi,
thanks for the information.
I will test the new firmware on spare.
If it is really working, maibe i will upgrade in the next few weks.
It's not so evident to upgrade thes materiels when they are in production.
I'm a bit surprised, to see two releases firmware in a so short interval...
jenfi
7 Posts
0
February 23rd, 2010 06:00
Hi,
i'm testing with the new firmware, and i receive the sames errors:
with the agentTransferUploadDataType set to 2, i have this error:
Feb 23 08:09:50 XXXXXXXXXX TRAPMGR[126803728]: traputil.c(618) 11872 %% TFTP of TEST-M1000E_20100223 is started
Feb 23 08:09:50 XXXXXXXXXX TRAPMGR[126803728]: traputil.c(618) 11873 %% TFTP of TEST-M1000E_20100223 is aborted with exit code = 2
with the agentTransferUploadDataType set to 3, i have this error:
Feb 23 08:11:33 XXXXXXXXXX TRAPMGR[126803728]: traputil.c(618) 11916 %% TFTP of TEST-M1000E-_20100223 is started
Feb 23 08:11:33 XXXXXXXXXX TRAPMGR[126803728]: traputil.c(618) 11931 %% TFTP of TEST-M1000E-_20100223 is completed with exit code = 11
I'm missing something?
DELL-Victor
98 Posts
0
February 25th, 2010 11:00
There is no valid work-around for the issue as previously thought. The backup config files resulting from the work-round contains invalid special characters and attempting to restore gives a return code of 6: invalidConfigFile. At this time there is no way to backup the config using SNMP. Until fixed, alternatives are to use http, cli, or OpenManage Network Manager. The OMNM tool also uses CLI, but allows backups to multiple systems at once.
# 292209 is still being worked to address the issue.
-Victor
jenfi
7 Posts
0
March 31st, 2010 04:00
Hi,
is there any chances, we see a firmware upgrade to correct this bug?
Regards.
jenfi
7 Posts
0
April 13th, 2010 05:00
Hi
i recently upgrade a m6220 with the latest firmware (3.1.3.9).
It's appears that the bug is still here.
Any advice to contourn this bug?
Thanks.
jenfi
7 Posts
0
May 3rd, 2010 01:00
Hi,
i can't understand, why thi bug isn't corrected?
Snmp backup is a "basic feature".
Could you explain why the snmp command was functionnal before, and isn't anymore?
We are the 3th May, there was a new firmware, and you don't correct this basical function?