I want to use PRTG as traplog server, but some logs could not be displayed properly.

SNMPv2-MIB::snmpTrapOID.0 = AIRESPACE-WIRELESS-MIB::bsnDot11StationAssociate
AIRESPACE-WIRELESS-MIB::bsnStationAPMacAddr.0 = ??
AIRESPACE-WIRELESS-MIB::bsnStationAPIfSlotId.0 = 1
AIRESPACE-WIRELESS-MIB::bsnUserIpAddress.0 = 0.0.0.0
AIRESPACE-WIRELESS-MIB::bsnStationUserName.0 = 
AIRESPACE-WIRELESS-MIB::bsnStationMacAddress.0 = |???
AIRESPACE-WIRELESS-MIB::bsnAPName.0 = LAP3702

I have uploaded the correct MIBs, but the issue remains.

I'm changing the traglog server to Solarwind traplog viewer, found it doesn't have this issue

sysUpTime=19 hours 40 minutes 19.00 seconds
snmpTrapOID=AIRESPACE-WIRELESS-MIB:bsnDot11StationAssociate
bsnStationAPMacAddr=D8B1.90B2.A870
bsnStationAPIfSlotId=1
bsnUserIpAddress=0.0.0.0
bsnStationUserName=
bsnStationMacAddress=7CFA.DF88.BE87
bsnAPName=LAP3702

Device: Cisco WLC 2504
Traplog: Client Association

Article Comments

Hello there,

Many thanks for your inquiry, we appreciate your contact regarding this matter!

Unfortunately, our Trap Receiver sensor is currently unable to properly decode hexadecimal values, this results in the characters you're seeing:

AIRESPACE-WIRELESS-MIB::bsnStationAPMacAddr.0 = ??
AIRESPACE-WIRELESS-MIB::bsnStationMacAddress.0 = |???

There's currently no workaround for that. However, depending on what you're after the following may help:

The above is a device template designed to make monitoring Cisco WLC controllers with PRTG easier. Please let us know whenever this helps.

Kind regards,
Birk Guttmann, Tech Support Team


Apr, 2018 - Permalink