BiPAC 8900AX-2400 - SNMP

[Craigeh]

Hey,

I was wondering if anyone has had success configuring the BiPAC 8900AX-2400 with Cacti?

Ideally I want to graph/monitor 2.4GHz and 5GHz wireless, the first ethernet port (connected to a switch) and the VDSL connection.

Thanks,
Craig

[rhysssmith]

Yep, I set this up yesterday, based on some cacti templates from several years ago from an older billion router, heavily modified. You can grab templates here to import into cacti - https://www.dropbox.com/s/f8pdgli1huez1 ... r.xml?dl=0

This will show:
* Line rate (upstream and downstream)
* Attainable line rate (upstream and downstream)
* Upstream Attainable rate vs Actual rate
* Downstream Attainable rate vs Actual rate
* Attenuation (upstream and downstream) (N.B. upstream always seems to report zero for me)
* SNR (upstream and downstream)

You can then also add traffic graphs per port on the router (i.e. the four LAN ports are eth0-eth3, eth4 is the ewan port, wl0 is the wireless port. ppp1.1 would be the VDSL port. There's also an eth5 (no idea what that is), and a pppoa0, atm0, and cpcs0 which are for other connections methods. So I've got mine graphing eth0-3 (internal lan traffic), wl0 (wifi traffic), and ppp1.1 (internet traffic).

Don't think there's a way to differentiate between 2.4 and 5ghz via SNMP; at least, if there is, it's not obvious to me.

Make sure the SNMP agent is turned on in the router interface (Advanced Setup -> Management -> SNMP Agent -> Enable) and that the parameters match your cacti SNMP polling config, obviously.

[rhysssmith]

Having said that, in the management interface to the router I can see there's a wl0 and a wl1. I assume these relate to the 2.4 and 5GHz radios (but maybe I'm wrong).

SNMP on the router only exposes wl0 though... Maybe the firmware hasn't been updated to include exposing wl1 stats over SNMP?

[billion_fan]

Having said that, in the management interface to the router I can see there's a wl0 and a wl1. I assume these relate to the 2.4 and 5GHz radios (but maybe I'm wrong).

SNMP on the router only exposes wl0 though... Maybe the firmware hasn't been updated to include exposing wl1 stats over SNMP?

For 5ghz we are checking for compatibility with chipset vendor

[rhysssmith]

In the web interface, the router is already dealing with wl0 and wl1 separately, and has separate stats for each (see screenshot)

Screenshot 2017-08-08 11.21.28.png

And of course I now realise that my assumption that wl0 is 2.4GHz and wl1 is 5GHz is correct, as the UI shows that! (Configuration -> Wireless 2.4G (wl0) and Configuration -> Wireless 5G (wl1))

SNMPwalking shows that SNMP is reporting stats for the following interfaces:

Code: Select all

.1.3.6.1.2.1.2.2.1.2.1 = STRING: eth0
.1.3.6.1.2.1.2.2.1.2.2 = STRING: eth1
.1.3.6.1.2.1.2.2.1.2.3 = STRING: eth2
.1.3.6.1.2.1.2.2.1.2.4 = STRING: eth3
.1.3.6.1.2.1.2.2.1.2.5 = STRING: eth4
.1.3.6.1.2.1.2.2.1.2.6 = STRING: eth5
.1.3.6.1.2.1.2.2.1.2.7 = STRING: wl0
.1.3.6.1.2.1.2.2.1.2.8 = STRING: pppoa0
.1.3.6.1.2.1.2.2.1.2.9 = STRING: ppp1.1
.1.3.6.1.2.1.2.2.1.2.10 = STRING: dsl0
.1.3.6.1.2.1.2.2.1.2.11 = STRING: atm0
.1.3.6.1.2.1.2.2.1.2.12 = STRING: cpcs0

(So e.g. wl0 total received bytes corresponds to .1.3.6.1.2.1.2.2.1.10.7 in the SNMP tree).

So it looks like the router already has the stats for wl1 available and accessible, it just doesn't expose them via SNMP, which I assume is just an oversight.

[rhysssmith]

By the way, for those interested in cacti graphing of their router, this is what the above cacti templates would give you:

Screenshot 2017-08-08 11.54.29.png

[billion_fan]

In the web interface, the router is already dealing with wl0 and wl1 separately, and has separate stats for each (see screenshot)

Screenshot 2017-08-08 11.21.28.png

And of course I now realise that my assumption that wl0 is 2.4GHz and wl1 is 5GHz is correct, as the UI shows that! (Configuration -> Wireless 2.4G (wl0) and Configuration -> Wireless 5G (wl1))

SNMPwalking shows that SNMP is reporting stats for the following interfaces:

Code: Select all

.1.3.6.1.2.1.2.2.1.2.1 = STRING: eth0
.1.3.6.1.2.1.2.2.1.2.2 = STRING: eth1
.1.3.6.1.2.1.2.2.1.2.3 = STRING: eth2
.1.3.6.1.2.1.2.2.1.2.4 = STRING: eth3
.1.3.6.1.2.1.2.2.1.2.5 = STRING: eth4
.1.3.6.1.2.1.2.2.1.2.6 = STRING: eth5
.1.3.6.1.2.1.2.2.1.2.7 = STRING: wl0
.1.3.6.1.2.1.2.2.1.2.8 = STRING: pppoa0
.1.3.6.1.2.1.2.2.1.2.9 = STRING: ppp1.1
.1.3.6.1.2.1.2.2.1.2.10 = STRING: dsl0
.1.3.6.1.2.1.2.2.1.2.11 = STRING: atm0
.1.3.6.1.2.1.2.2.1.2.12 = STRING: cpcs0

(So e.g. wl0 total received bytes corresponds to .1.3.6.1.2.1.2.2.1.10.7 in the SNMP tree).

So it looks like the router already has the stats for wl1 available and accessible, it just doesn't expose them via SNMP, which I assume is just an oversight.

OID's that got sent to me from our engineers, see below

BiPAC 8900AX-2400 OID/MIB
--------------------------
P1 Received Total Bytes
OID = 1.3.6.1.2.1.2.2.1.10.1

P1 Received Total Packets
OID = 1.3.6.1.2.1.2.2.1.11.1

P1 Transmitted Total Bytes
OID = 1.3.6.1.2.1.2.2.1.16.1

P1 Transmitted Total Packets
OID = 1.3.6.1.2.1.2.2.1.17.1


P2 Received Total Bytes
OID = 1.3.6.1.2.1.2.2.1.10.2

P2 Received Total Packets
OID = 1.3.6.1.2.1.2.2.1.11.2

P2 Transmitted Total Bytes
OID = 1.3.6.1.2.1.2.2.1.16.2

P2 Transmitted Total Packets
OID = 1.3.6.1.2.1.2.2.1.17.2


P3 Received Total Bytes
OID = 1.3.6.1.2.1.2.2.1.10.3

P3 Received Total Packets
OID = 1.3.6.1.2.1.2.2.1.11.3

P3 Transmitted Total Bytes
OID = 1.3.6.1.2.1.2.2.1.16.3

P3 Transmitted Total Packets
OID = 1.3.6.1.2.1.2.2.1.17.3


P4 Received Total Bytes
OID = 1.3.6.1.2.1.2.2.1.10.4

P4 Received Total Packets
OID = 1.3.6.1.2.1.2.2.1.11.4

P4 Transmitted Total Bytes
OID = 1.3.6.1.2.1.2.2.1.16.4

P4 Transmitted Total Packets
OID = 1.3.6.1.2.1.2.2.1.17.4


P5/EWAN Received Total Bytes
OID = 1.3.6.1.2.1.2.2.1.10.6

P5/EWAN Received Total Packets
OID = 1.3.6.1.2.1.2.2.1.11.6

P5/EWAN Transmitted Total Bytes
OID = 1.3.6.1.2.1.2.2.1.16.6

P5/EWAN Transmitted Total Packets
OID = 1.3.6.1.2.1.2.2.1.17.6


eth4 wl1 5GHz Received Total Bytes
eth4 wl1 5GHz Received Total Packets
eth4 wl1 5GHz Transmitted Total Bytes
eth4 wl1 5GHz Transmitted Total Packets
===> Still not supported


wl0 2.4GHz Received Total Bytes
OID = 1.3.6.1.2.1.2.2.1.10.7

wl0 2.4GHz Received Total Packets
OID = 1.3.6.1.2.1.2.2.1.11.7

wl0 2.4GHz Transmitted Total Bytes
OID = 1.3.6.1.2.1.2.2.1.16.7

wl0 2.4GHz Transmitted Total Packets
OID = 1.3.6.1.2.1.2.2.1.17.7

Line Attainable Rate - Downstream
OID = 1.3.6.1.2.1.10.97.1.1.2.1.9.1

Line Attainable Rate - Upstream
OID = 1.3.6.1.2.1.10.97.1.1.2.1.9.2

Line Rate (Kbps) - Downstream
OID = 1.3.6.1.2.1.10.97.1.1.2.1.10.1

Line Rate (Kbps) - Upstream
OID = 1.3.6.1.2.1.10.97.1.1.2.1.10.2

SNR downstream
OID = 1.3.6.1.2.1.10.97.1.1.2.1.5.1

SNR upstream
OID = 1.3.6.1.2.1.10.97.1.1.2.1.5.2

Firmware version
OID = 1.3.6.1.2.1.1.1.0

System Up Time
OID = 1.3.6.1.2.1.1.3.0

[rhysssmith]

eth4 wl1 5GHz Received Total Bytes
eth4 wl1 5GHz Received Total Packets
eth4 wl1 5GHz Transmitted Total Bytes
eth4 wl1 5GHz Transmitted Total Packets
===> Still not supported

Yes, as suspected... Thanks for checking though!

It'd be nice to get those included in the SNMP output at some point just for completeness. Certainly not something that's exactly urgent though...

[billion_fan]

eth4 wl1 5GHz Received Total Bytes
eth4 wl1 5GHz Received Total Packets
eth4 wl1 5GHz Transmitted Total Bytes
eth4 wl1 5GHz Transmitted Total Packets
===> Still not supported

Yes, as suspected... Thanks for checking though!

It'd be nice to get those included in the SNMP output at some point just for completeness. Certainly not something that's exactly urgent though...

Our engineers will check with the chipset vendor for compatibility with our SNMP agent (as the 5ghz chipset is not Broadcom)