snmpset dropSession.0 "error in packet" issue

Hi,

I'm trying to drop sessions from some PMP450 APs with software 13.2/13.2.1/13.3 but i'm getting the following error:

# snmpset -v2c -c myCommunity 169.254.1.1 .1.3.6.1.4.1.161.19.3.1.1.87.0 s "XX:XX:XX:XX:XX:XX"
Error in packet.
Reason: wrongValue (The set value is illegal or unsupported in some way)
Failed object: WHISP-APS-MIB::dropSession.0

I've the same issue with a old PMP100 with software release 13.1.3.

Hi!

This OID is a MacAddress type which is actually an octet string.  To use it, the argument is still string, but you pass the mac as a string without the colons:

snmpset -v 2c -c Canopy X.X.X.X .1.3.6.1.4.1.161.19.3.1.1.87.0 s 0a003e112233

Hi Aaron,

I already tried this option but I get the following error:

# snmpset -v2c -c Canopy 169.254.1.1 .1.3.6.1.4.1.161.19.3.1.1.87.0 s 0a003e112233
.1.3.6.1.4.1.161.19.3.1.1.87.0: Value out of range (Value does not match DISPLAY-HINT :: {(6)})

Hi,

we still haven't a answer to this after 2 and half years.

NW_WISP

I am sorry that this was missed 2 and a half years ago.

I just ran

snmpset -v2c -c Canopy 169.254.1.1 .1.3.6.1.4.1.161.19.3.1.1.87.0 s 0a003eb42c53

and got the reply

iso.3.6.1.4.1.161.19.3.1.1.87.0 = STRING: "0a003eb42c53"

and I watched the session drop.

The IP address is my Medusa AP running 15.1.3 and the MAC is my SM

If you run the same command (adjusted for your network) and get the same response you got 2 and a half years ago, please capture engineering.cgi and forward to me at  bacuffe1 <at > cambiumnetworks <dot> com

Thanks

1 Like

I think it's great that you can come back to an old thread (that made its way to the interwebz editing floor as it were), and get a near-immediate response from our engineering team.

It's a testament to the dedication of the Cambium team, imho.

2 Likes

following a very helpful email conversation with NW_WISP, we have determined that there _is_ a change to be made in the published MIB, since the OID above works fine but loading the MIB and using dropSession by name fails.

I have targeted the change request for this at the second-to-next release.

Many Thanks NW_WISP

and, again, apologies for missing this first time round

2 Likes