(1) OID network statistics confusion and (2) Simulating SM Re-registration

Products PMP
1

Hello,

Two separate questions:

1. I am trying to gather network throughput statistics on all SM and AP radios (not PPPoE statistics). When I look in the SM Mib I only see OID's for PPPoE (pppoeDataBytesReceived etc.). If I visit the SM's Web Configuration page (Statistics -> Radio) I see values for `inoctets Count` and `outoctets Count`, which is exactly what I want, but I don't see those represented as OID's.

What confuses me is that the AP holds the radio network statistics (correct me if I am wrong) in its own Mib as `linkOutOctets` and `linkInOctets` for each SM.

Example:

$ snmpwalk -v2c -cCanopyro <ap-ip-address> 1.3.6.1.4.1.161.19.3.1.4.1.13
SNMPv2-SMI::enterprises.161.19.3.1.4.1.13.2 = Counter32: 3474848177
SNMPv2-SMI::enterprises.161.19.3.1.4.1.13.3 = Counter32: 3670065471

Returns `linkOutOctets` for two connected SM's, LUID 2 and 3.

Now if I visit the AP's Web Configuration page (Statistics -> Radio) I see values for `inoctets Count` and `outoctets Count` which, again, is exactly what I want but I don't see an OID in the AP Mib for its own in/out octect Count. Is an AP's `inoctets Count` a summation of all connected SM's `outoctect Count`, and vice-verse for `outoctects`. If so, then is your SM Statistics->Radio values are retrieved by SNMP to the AP? How does the SM know it is connected to that AP (I do not see an OID for that).

2. How can I simulate a Re-registration on a SM to an AP? This is strictly for testing purposes to raise an alarm in Cacti.

Pulled from the PMP User Guide:

Typically, a Re-Reg is the case where both:
- an SM attempts to reregister for having lost communication with the AP.
- the AP has not yet observed the link to the SM as being down.

Thank you for your time

1 Like
2

Hi,

1) You can use the standard IF-MIB:

;; Counter32
; Ethernet Interface
IF-MIB::ifInOctets.1=.1.3.6.1.2.1.2.2.1.10.1
IF-MIB::ifOutOctets.1=.1.3.6.1.2.1.2.2.1.16.1
; Radio Interface
IF-MIB::ifInOctets.2=.1.3.6.1.2.1.2.2.1.10.2
IF-MIB::ifOutOctets.2=.1.3.6.1.2.1.2.2.1.16.2

;; Counter64
; Ethernet Interface
IF-MIB::ifHCInOctets.1=.1.3.6.1.2.1.31.1.1.1.6.1
IF-MIB::ifHCOutOctets.1=.1.3.6.1.2.1.31.1.1.1.10.1
; Radio Interface
IF-MIB::ifHCInOctets.2=.1.3.6.1.2.1.31.1.1.1.6.2
IF-MIB::ifHCOutOctets.2=.1.3.6.1.2.1.31.1.1.1.10.2

2) You can drop the SM session from the AP

Drop Session AP
Drop Session AP1902×372 66.7 KB

3

1) Excellent thanks.

2) That counts as a Registration not a Re-registration

 Session Count: 2, Reg Count: 2, Re-Reg Count: 0
4

You can use the "Timed Spectrum Analysis" function on the SM.

5

Again, not getting re-reg.

Session Count: 5, Reg Count: 5, Re-Reg Count: 0

I've enabled the tool and rebooted.

6

You don't need to enable the scan at boot, just press the "Start Timed Spectrum Analysis" button.

7

Are you doing this on your end and seeing re-reg increments?

 Session Count: 9, Reg Count: 9, Re-Reg Count: 0
8

Yep. (in the image: Count | Reg | Re-Reg)

9

Is there a way for you to dump your configuration for the AP/SM and I can replicate it?  Or would it be something else? My setup is a simple AP <-> SM