The Adtran community holiday season is starting next week! The holiday period will span from December 21, 2024 to January 6, 2025. During this time, responses to feedback form submissions may be delayed. If you are encountering product issues, you can reach out to Adtran support at any time.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
msmith
New Contributor

Problems setting up SNMP on 1 of over 30 adtran devices - how to prove is unit is defective

snmp agent

snmp-server engineID remote 172.28.2.55 800002980300a0c83f0ce4

snmp-server user SNMP HCU_GROUP v3 auth sha encrypted 252ced133e2da04fdcae5d4f6a8f51cf3304 priv des encrypted 252ced133e2da04fdcae5d4f6a8f51cf3304

snmp-server group HCU_GROUP v3 priv

Fife#debug snmp pac

Fife#

Received a SNMP packet to be processed.

SNMP V3 RX: REPORT PDU from 172.28.2.55:63228 (community=)

  VRF = -DEFAULT-

SNMP decode_pkt  error: sending an error packet.

SNMP V3 TX: REPORT PDU to 172.28.2.55:161 (community=)

  VRF = -DEFAULT-

0 Kudos
3 Replies
msmith
New Contributor

Re: Problems setting up SNMP on 1 of over 30 adtran devices - how to prove is unit is defective

This is a 1534P version 2 running R12.3.4

jayh
Honored Contributor
Honored Contributor

Re: Problems setting up SNMP on 1 of over 30 adtran devices - how to prove is unit is defective

If it's configured similarly to the other 30 devices with the same firmware version, I'd open a support ticket. I read the release notes for R12.3.4 and don't see this as a known bug. The only SNMP bug relates to missing commands for setting traps on an interface.

msmith
New Contributor

Re: Problems setting up SNMP on 1 of over 30 adtran devices - how to prove is unit is defective

I was able to resolve this - the issue was with my SNMP remote end so the switch itself was ok.