IMC
cancel
Showing results for 
Search instead for 
Did you mean: 

Integrating Lancom APs into IMC

 
networker2014
Occasional Collector

Integrating Lancom APs into IMC

Hi,

 

I'm currently trying to integrate some Lancom APs into the trial version of the HP IMC solution (we are currently trying to figure out if we really want to buy it).


Does somebody has an idea  on how to integrate e.g. checks for the maximum number of associated stations into IMC?

 

I'm currently trying to create a customized index (here is another thread about this).

 

So I'm going to IMC >> Resource >> Global Index Settings >> Add Custom Index

 

Name: Lancom WLAN Nutzer

Type: [index1[0]:stations:1:0]

Instance Label Definition: 1.3.6.1.4.1.2356.600.2.54.1.3.51.1.8

Formula: 1.3.6.1.4.1.2356.600.2.54.1.3.51.1.8

 

 

(as I get a correct response when I do a snmpgetnext on the AP, I suppose this OID to be correct)

 

(clicking on Test)

 

Select Device or Enter IP-Address: IP of the accesspoint

 

After clicking on "Resolve" "[stations::.6]" appears in the drop-down box next to "Select instance".

 

If I click on "Start" right now, I get the message that IMC is collecting the data, then (red x) with the message "Collection has finished" and then I'mgetting forwarded to a Remediation Suggestion webpage which is telling me on how to obtain log-files.

 

 

Does anybody have a clue what I can do to get IMC collecting the stats for me?

 

 

Additional information:

 

- I currently don't know where IMC collects the ".6" from (tcpdump logged no result with this number, just requests)

- according to tcpdump IMC received a correct response from my access point.

 

TCPdump:

tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
17:29:50.444710 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 81)
    imc-host.47590 > lancom-ap.snmp: [bad udp cksum 40b0!]  { SNMPv2c { GetNextRequest(36) R=6521  E:2356.600.2.54.1.3.51.1.8 } }
17:29:50.449356 IP (tos 0x0, ttl 59, id 62540, offset 0, flags [none], proto UDP (17), length 85)
    lancom-ap.snmp > imc-host.47590: [udp sum ok]  { SNMPv2c { GetResponse(42) R=6521  E:2356.600.2.54.1.3.51.1.8.6.87.76.65.78.45.49=38 } }
17:29:50.449462 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 82)
    imc-host.38210 > lancom-ap.snmp: [bad udp cksum e0cb!]  { SNMPv2c { GetRequest(37) R=6521  E:2356.600.2.54.1.3.51.1.8.6 } }
17:29:50.451351 IP (tos 0x0, ttl 59, id 62542, offset 0, flags [none], proto UDP (17), length 79)
    lancom-ap.snmp > imc-host.38210: [udp sum ok]  { SNMPv2c { GetResponse(36) R=6521  E:2356.600.2.54.1.3.51.1.8.6=[noSuchObject] } }
17:29:50.451481 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 88)
    imc-host.46876 > lancom-ap.snmp: [bad udp cksum 21cc!]  { SNMPv2c { GetNextRequest(43) R=6521  E:2356.600.2.54.1.3.51.1.8.6.87.76.65.78.45.49 } }
17:29:50.453725 IP (tos 0x0, ttl 59, id 62544, offset 0, flags [none], proto UDP (17), length 85)
    lancom-ap.snmp > imc-host.46876: [udp sum ok]  { SNMPv2c { GetResponse(42) R=6521  E:2356.600.2.54.1.3.51.1.9.6.87.76.65.78.45.49=1 } }
17:29:50.453844 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 82)
    imc-host.40020 > lancom-ap.snmp: [bad udp cksum cec4!]  { SNMPv2c { GetRequest(37) R=6521  E:2356.600.2.54.1.3.51.1.8.6 } }
17:29:50.456275 IP (tos 0x0, ttl 59, id 62546, offset 0, flags [none], proto UDP (17), length 79)
    lancom-ap.snmp > imc-host.40020: [udp sum ok]  { SNMPv2c { GetResponse(36) R=6521  E:2356.600.2.54.1.3.51.1.8.6=[noSuchObject] } }