2106 APs and Ping

Unanswered Question
Aug 15th, 2008
User Badges:

I have a WLC 2106 with 4 lightweight WAPs directly connected to it. The 2106 has an 802.1q trunk to a layer 3 device. The WAPs are registered and work fine; however, although I can 'ping' the controller from the layer 3 device I can't ping any of the WAPs.

Is there a setting on the controller that is required to allow WAPs directly connected to it to be 'pinged'??

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Scott Fella Fri, 08/15/2008 - 06:02
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

So the LAP's are up and functional on the 2106, but you can't ping the LAP's from the L3 switch, but you can ping the LAP's from the WLC?

ibrydon Sun, 08/17/2008 - 23:55
User Badges:

Yes the LAPs are up and functional but I cannot ping them from the WLC or anywhere else. Just one thing that may or may not not be relevant; the WAPs are on the same VLAN/subnet as the WLC management and AP management interfaces.

Scott Fella Mon, 08/18/2008 - 06:20
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

That setup is fine, but the port that the wlc is connected to is that configured for native vlan? Also is the management and ap-manager interface configured with a vlan tag of "0"?

ibrydon Mon, 08/18/2008 - 07:31
User Badges:

No, the management and AP management interfaces are not untagged they are assigned to VLAN 20.

Scott Fella Mon, 08/18/2008 - 07:43
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

I think you need this to be untagged for it to work. Just add the switchport mode trunk native vlan 20 to the trunk port.

ibrydon Mon, 08/18/2008 - 07:50
User Badges:

Not sure what you mean by that. The WLC is not connected to a Cisco switch. The connection is to a Checkpoint Edge Firewall. The port on the firewall is set to be an 802.1q trunk and is passing traffic from various other subnets apart from the subnet assigned to VLAN 20. The Edge does not have a concept of 'native VLAN'. If you use VLAN 1 on that device it tags it as VLAN 1 unlike Cisco.

Scott Fella Mon, 08/18/2008 - 07:56
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

Okay.... well the problem is that the wlc doesn't know VLAN tagging and that is why it is best practice to set the wlc to untagged per Cisco's doc. It does work, but you can't configure the switch port on the wlc for vlan 20. I think that is where the problem lies.

ibrydon Mon, 08/18/2008 - 23:50
User Badges:

Thanks for your help, I think you are right.



Scott Fella Tue, 08/19/2008 - 06:04
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

No problem... let me know if you get it to work.

ibrydon Tue, 08/19/2008 - 07:03
User Badges:

I spoke to TAC - they pointed me at bug fix CSCsj3229. Looks like there is a problem with directly connected WAPs to a 2106.

Scott Fella Tue, 08/19/2008 - 07:08
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

Is that the correct bug id? Looks like you are missing a digit.

Actions

This Discussion