Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Roy_Smith
Collaborator
Jump to solution

R80.40 snmpv3

Hi

Just wondering if anyone else as seen an issue with SNMPv3 after upgrading to R80.40?

We have just upgraded our MDS servers and VSX clusters from R80.30 to R80.40 with JHF take48. We monitored the devices and virtual servers using SNMPv3. After upgrading to R80.40, our monitoring server, which is Solarwinds, cannot connect to the VSX clusters and virtual servers. However, it can connect to the MDS servers fine. 

If I enabled SNMP v2 on the VSX gateways, our Solarwinds server can connect to them. They just cannot connect using v3. Has anyone seen this? Is it likely to be a bug?

Thanks
Roy

35 Replies
genisis__
Leader Leader
Leader

Is this SNMP issue in R81 as well?

0 Kudos
michaelsc
Employee
Employee

The fix for this issue is currently tested by QA before delivery to R81 JHF.

0 Kudos
genisis__
Leader Leader
Leader

We will be upgrade to R81 on the Management layer is a few weeks time, so hopefully a new jumbo is release.

We are actually upgrade a pair of VSX appliances this weekend to R80.40 as well, do we know if CP has addressed this in Jumbo HFA91?

 

Also just to point out that SK168180 does not seem to be available.

0 Kudos
michaelsc
Employee
Employee

The fix for the 'unknown user' issue in SNMP V3 on VSX is included in take 91 of R80.40 JHF.

0 Kudos
genisis__
Leader Leader
Leader

Awesome!

0 Kudos
Kaspars_Zibarts
Employee Employee
Employee

Need add a bit more info that we discovered after one of our VSX appliances died and HW was replaced.

All worked like a clock after backup restore, except SNMP v3 access to actual VSes. VS0 worked fine. Followed both - solution here and sk170993 but it would not work.

Eventually found out that the /etc/snmp/vsx-proxy/snmpd.vsx.proxy.conf was totally empty! No idea why and how as we deleted USM user countless times and stop/started SNMP agent. Even restarted the whole box. Stumbled across it whilst comparing all SNM;P config files one by one between working VSX and the new one.

We just copied contents from working VSX and all started working.

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events