Welcome, Guest. Please login or register.

Author Topic: Re: Bug in 1.4 patch 3 ? (SOLVED, not a Nedi problem)  (Read 1495 times)

sjobergh

  • Newbie
  • *
  • Posts: 24
    • View Profile
Re: Bug in 1.4 patch 3 ? (SOLVED, not a Nedi problem)
« on: March 17, 2015, 01:00:00 AM »
I installed patch 3 and found that when discovering  Wlan controllers
the problem I see is that discovery doesnt find any APs as it did before

Equipment   
Cisco 5508 WLCs with ver 8.0.110.0 and ver 7.6.130.0, needs to be v1 now
Cisco 4400 with ver 7.0.250.0 still works with v2
Cisco 2504 with ver 7.4.110.0 still works with v2
Cisco Wism with ver 7.0.250.0 doesnt work with v1 or v2

Aruba 6000 ctrl with version  6.1.3.2, needs to be v1 now
Aruba 3000 ctrl with version  6.1.3.2, needs to be v1 now
 
Little more details from the discovery process using v2

WLC AP
 ------------------------------------------------------------------------
SNMP:
Connect 111.1.1.1 mycommunity v2 Tout:5s MaxMS:2048 Retry:2 NB:0 WLC :
Walking AP name ERR
:No response from remote host '111.1.1.1'

when forcing  v1

WLC AP ------------------------------------------------------------------------ SNMP
:SNMP
:Connect 111.1.1.1 mycommunity v1 Tout:5s MaxMS:2048 Retry:2 NB:0 WLC
:Walking AP name WLC
:Walking AP location WLC
:Walking AP type WLC
:Walking AP SN WLC
:Walking AP group WLC
:Walking AP bootimage WLC
:Walking AP IP WLC
:Walking IF channel WLC
:Walking IF oper status WLC
:Walking IF admin status WLC
:Walking client user WLC
:Walking client AP WLC
:Walking client radio WLC
:Walking client SSID index WLC
:Walking client SNR WLC
:Walking client IP
AP+ :XXX-YY-ZZZ-APP5-01 (6886a7cac1e0) 192.168.165.40 FGL1706Z0UR AIR-CAP1602I-E-K9 plan5
WDEV:XXX-YY-ZZZ-APP5-01 written to nedi.devices
AP+ :XXX-YY-ZZZ-APP6-01 (04dad28bb420) 192.168.165.42 FGL1706Z0GF AIR-CAP1602I-E-K9 plan6
WDEV:XXX-YY-ZZZ-APP6-01 written to nedi.devices

Any ideas :)
« Last Edit: March 18, 2015, 08:16:18 PM by sjobergh »

sjobergh

  • Newbie
  • *
  • Posts: 24
    • View Profile
Re: Bug in 1.4 patch 3 ? (SOLVED, not a Nedi problem)
« Reply #1 on: March 18, 2015, 08:15:57 PM »
I found the problem,  it wasnt a Nedi problem,  the MTU had been adjusted at the server and was set to low for SNMP V2 packets.
Probably it is the WLCes that cant adjust to low MTU sizes and answers with higher value than the MTU in the server.