Ping to WLC management interface times out

[SuperZook]

Hi all,

I am having a problem with a 2504 WLC. When I ping the management interface I have 35% packet loss on average. Here is my setup:

WLC: 2504

LAP: 1142N

Switch: HP ProCurve 2520G-24-PoE

The management interface on the WLC is the only interface I use, so dynamic AP management is enabled. I've also assigned a VLAN ID. The switchport the WLC is connected to is configured with the same VLAN ID, meaning it's a tagged port. The switchports the LAP's are connected to are untagged.

I've already tried configuring the WLC management interface and the respective switchport without VLAN's with the same result. I've also tried two different software versions on the WLC (7.0.116 and 7.2.103), the switch is running the latest firmware version.

I get the feeling that I am overlooking something simple here, so every comment is much appreciated.

Thanks!

[nikhilcherian]

Configure the managemnet interface vlan as 0 ( untagged) if you are configuring vlan on the switch port

Thanks

NikhiL

[SuperZook]

Hi NikhiL,

if the management interface vlan is configured as untagged and the swichport is tagged, I don't get any replies. If both are untagged I get the same result as described above...

[nikhilcherian]

can you paste the output of show run int  from the switch

and show interface detailed management from the wlc

[Scott Fella]

Just to add... You only have one port from the 2504 connected and are you pinging from a wired or wireless device.

Thanks,

Scott Fella

Sent from my iPhone

[SuperZook]

Hi nikhilcherian,

(Cisco Controller) >show interface detailed management

Interface Name................................... management

MAC Address...................................... d0:c2:82:e2:55:40

IP Address....................................... 10.128.198.251

IP Netmask....................................... 255.255.255.0

IP Gateway....................................... 10.128.198.254

External NAT IP State............................ Disabled

External NAT IP Address.......................... 0.0.0.0

VLAN............................................. 198

Quarantine-vlan.................................. 0

Active Physical Port............................. 1

Primary Physical Port............................ 1

Backup Physical Port............................. Unconfigured

Primary DHCP Server.............................. 10.128.198.251

Secondary DHCP Server............................ Unconfigured

DHCP Option 82................................... Disabled

ACL.............................................. Unconfigured

AP Manager....................................... Yes

Guest Interface.................................. No

L2 Multicast..................................... Enabled

And here is the port and vlan config from the switch (it's an HP switch, so no "sh run int"):

interface 3

   no power-over-ethernet

exit

...

...

...

vlan 198

   name "VLAN198"

   untagged 4-12

   ip address 10.128.198.252 255.255.255.0

   tagged 3,Trk1

   exit

primary-vlan 198

Hi Scott,

only one port from the 2504 is connected and I am pinging from a wired laptop connected to the same vlan on the switch.

Thanks for your help guys!

[nikhilcherian]

can you add the below configuration in the switchport

switchport trunk encapsulation dot1q

switchport trunk

or the equivalent comments in the HP switch

Just wanna make it trunk port with dot1q encapsulation and native vlan as 1

[SuperZook]

the config you posted is a Cisco config but the switch is an HP one. the cisco trunk config is referred to as tagged vlan ports in the HP world. (and a HP trunk is what you'd call an etherchannel on the cisco side, so basically port aggregation)

[SuperZook]

i am not sure about the native vlan part, I'll try changing the primary-vlan-id from 198 to 1...

[SuperZook]

changing the native (primary) vlan didn't help either.

current config:

the wlc management port is tagged (vlan id 198)

the switchport the wlc is connected to is tagged (vlan id 198)

this means dot1q encapsulation is enabled on the switchport...

[Scott Fella · Accepted solution]

Remove the trunk configuration and make it a switchport assigned to vlan 198 and see if that works.

Thanks,

Scott Fella

Sent from my iPhone

[SuperZook]

removed the port aggregation config on my switch and now it's working. not 100% sure why though...

FYI, the aggregated ports were connecting my router/firewall to the switch.

thanks everybody for your help, much appreciated!

[Scott Fella]

Well there is no need to aggregate sine the 2504 doesn't support that. Maybe the HP was trying to negotiate the link aggregation and maybe that was the issue. So what did your final HP switchport configuration end up like.

Thanks,

Scott Fella

Sent from my iPhone

[SuperZook]

The aggregated link that was causing the problem was between the switch and my router, that's why I don't understand why the WLC had the connectivity problem.

I have now removed the trunk (=etherchannel) config on the switch and on my router and I am only using one port on both devices now.

Unfortunately I have no time at the moment to look deeper into this, I'm just glad it's working again and I can move on...

Thanks again!

[Scott Fella]

Thanks for the explanation it will be helpful to others in the future.

Thanks,

Scott Fella

Sent from my iPhone