v4_6_3 upgrade - SNMP has stopped working.

[DCIM_Support]

We've recently upgrade our Netbotz devices to v4_6_3.

Since the upgrade SNMP has stopped working.  v2 and v3 are both effected.

Advanced View shows that the SNMP service is enabled and configured.  

Contact the devices either results in "no response" or connection refused.

Help!

I now have 20+ devices that I can no longer grab remote data from.

Thanks

(CID:137726433)

[DCIM_Support]

Hi Darran,

I'll try testing this (gotta get something v3 ready installed). Can I get the config that you use? Not specifically the user name and password but their lengths would be helpful as well as the protocols and algorithms used.

Thanks,

Steve

P.S. SNMP V2 was purposefully disabled as per the release notes:

PDF Library

SNMPv2c has been disabled to help prevent distributed denial of service (DDOS)attacks.

(CID:137726446)

[DCIM_Support]

Also please note known issues #43 (Not sure if it will apply)

When a user changes any of the SNMPv3 communications parameters on the appliance, attempts to communicate with SNMPv3 under the new parameters are rejected.When making changes to the Authentication Protocol or the Encryption Algorithm settings for the appliance, those changes are recorded but not propagated to the SNMP operating environment until the appliance is rebooted.

(CID:137726467)

[DCIM_Support]

Hi Darran,

Sorry for taking so long on this. I did some testing and had some of the engineers test too. We could not seem to make it fail. It was done in both command line as well as a utility called MGSoft. It may be something specific to your scripts or possibly the bot needs to be re-initialized (lost config?).

Steve

(CID:137731391)

[DCIM_Support · Accepted solution]

Dear Darran Coy,

From the official Release Notes NetBotz v4.6.3.pdf for the new version v.4.6.3:

That is, now NetBotz-4.x only supports SNMPv1 and SNMPv3.

Please, try SNMPv1 first - it should work, for example everything is fine with me.

With respect.

(CID:137726459)

[DCIM_Support]

Thanks for the answers folks. 

I've spent couple of hours visiting the 3rd party scripts I wrote 10+ years ago to utilise SNMP v3 instead of v2.  I figured getting them working with SNMP v1 was a backward step. 

A warning as part of the upgrade would be useful though.  I've spent 3 days thinking it was a config error ☹️

I also couldn't figure out a way to downgrade to the previous version (v4_6_2).  Advanced View would let me browse to the earlier codebase, but wouldn't let me select it to "upgrade".  Is there a special downgrade setting somewhere that I haven't found?

Are we the only place where we wrap security around our devices to make sure DDOS would never get near a Netbotz or APC appliance?

Thanks

Darran

(CID:137726562)

[DCIM_Support]

Dear Darran Coy,

From your comments:

I've spent couple of hours visiting the 3rd party scripts I wrote 10+ years ago to utilise SNMP v3 instead of v2.  I figured getting them working with SNMP v1 was a backward step. 

It was easier for me, since I knew about disabling the SNMPv2c protocol even before upgrading NetBotz-4.x appliances (I just always read the release notes 😀. Since all my NetBotz-4.x are in a strictly isolated LAN, our security policy allows you to use the lightweight and simple protocol SNMPv1. This makes it much easier to set up a huge number of devices and saves a huge amount of time 😀.

I also couldn't figure out a way to downgrade to the previous version (v4_6_2)...

I think this is a bad idea. And for this there are many reasons, for example, with new updates, developers fix many bugs. Staying on the old firmware, you lose it. You also lose the possibility of expanding the functionality of your devices, etc...

With respect.

(CID:137726639)

[DCIM_Support]

Hi Darran,

There's no option in the UI to downgrade the appliance so If you're set on doing that, I suggest trying the TFTP upgrade procedure (works for downgrade too):

http://www.apc.com/us/en/faqs/index?page=content&id=FA176133

I would imagine that everything that was changed would be overwritten so you could try using the "keep" option but if you have issues, I would suggest you may have to try without using that keep option. 

If you're talking about downgrading all of these devices, this will take quite some time as you can only do them individually and you must run tftp on the same subnet as the device.

Steve

(CID:137726566)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.