cancel
Showing results for 
Search instead for 
Did you mean: 

SNMPv3 Issues

SNMPv3 Issues

Ian_Broadway
New Contributor III

Hi All,

I’m getting these SNMPv3 errors on our Extreme Control appliance from random switches;

 SNMP_V3_NOT_IN_TIME_WINDOW(1411) from device: 192.168.64.87 with message: org.snmp4j.asn1.BERInputStream@d5ffd43

 

and

 SNMP_V3_UNKNOWN_SECURITY_NAME(1404) from device: 192.168.231.20 with message: org.snmp4j.asn1.BERInputStream@7688ed06
 

They're talking fine to EMC, no alarms.

 

Any advice on what these errors are caused by please?

 

Thanks

Ian

1 ACCEPTED SOLUTION

Miguel-Angel_RO
Valued Contributor II

Ian,

That could be a duplicate snmp engineid.

What type of switches are causing this?

You can check the snmp engineid issue with this: https://gtacknowledge.extremenetworks.com/articles/Solution/NAC-loses-contact-with-switch-after-chan...

Mig

View solution in original post

10 REPLIES 10

Ian_Broadway
New Contributor III

ok looks to have resolved the issue now thankfully. Still have one switch complaining though

 

2020-10-02 14:44:47,097 WARN  [com.enterasys.tesNb.server.snmp.SnmpManager] (DefaultUDPTransportMapping_0.0.0.0/0:) Reinitializing switch SNMP info: 192.168.231.17
2020-10-02 14:44:56,093 WARN  [com.enterasys.tesNb.server.snmp.SnmpManager] (DefaultUDPTransportMapping_0.0.0.0/0:) Received Authentication Failure: SNMP_V3_NOT_IN_TIME_WINDOW(1411) from device: 192.168.231.17 with message: org.snmp4j.asn1.BERInputStream@20ced8e1
2020-10-02 14:44:56,093 WARN  [com.enterasys.tesNb.server.snmp.SnmpManager] (DefaultUDPTransportMapping_0.0.0.0/0:) Removing USM Time and EngineID: 80:00:07:7c:03:00:04:96:*:*:* for: 192.168.231.17
2020-10-02 14:44:56,093 WARN  [com.enterasys.tesNb.server.snmp.SnmpManager] (DefaultUDPTransportMapping_0.0.0.0/0:) Reinitializing switch: 192.168.231.17
 

its an x440-g2-48p-10ge4, running 22.5.1.7.-patch1-3.

Miguel-Angel_RO
Valued Contributor II

Ian,

I had a similar issue with Industrial switches Extreme ISW where the engineid as the same default value at first boot. This has to be adapted manually per switch.

Regards,

 

Mig

Ian_Broadway
New Contributor III

You are right actually, I have engine id issue which I believe derive from the fact that configs are copied onto switches for ease of configuration and then tweaked.

 

I’ll deal with these first and then let you know if the issues disappear. I'm amending the IDs to match the SW MAC for each switch.

I'm not getting the snmp issues within EMC though, only the NAC appliance.

EMC and NAC are both 8.4.3.24. 

Stefan_K_
Valued Contributor

But he says that XMC can communicate fine with the switches. This wouldn’t be possible.

 

Miguel-Angel_RO
Valued Contributor II

Ian,

That could be a duplicate snmp engineid.

What type of switches are causing this?

You can check the snmp engineid issue with this: https://gtacknowledge.extremenetworks.com/articles/Solution/NAC-loses-contact-with-switch-after-chan...

Mig

GTM-P2G8KFN