topic Re: 2106 APs and Ping in Wireless https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088709#M136970 <HTML><HEAD></HEAD><BODY><P>Is that the correct bug id? Looks like you are missing a digit.</P></BODY></HTML> Tue, 19 Aug 2008 14:08:05 GMT Scott Fella 2008-08-19T14:08:05Z 2106 APs and Ping https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088698#M136959 <P>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.</P><P>Is there a setting on the controller that is required to allow WAPs directly connected to it to be 'pinged'??</P> Sat, 03 Jul 2021 23:19:39 GMT https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088698#M136959 ibrydon 2021-07-03T23:19:39Z Re: 2106 APs and Ping https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088699#M136960 <HTML><HEAD></HEAD><BODY><P>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?</P></BODY></HTML> Fri, 15 Aug 2008 13:02:27 GMT https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088699#M136960 Scott Fella 2008-08-15T13:02:27Z Re: 2106 APs and Ping https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088700#M136961 <HTML><HEAD></HEAD><BODY><P>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.</P></BODY></HTML> Mon, 18 Aug 2008 06:55:57 GMT https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088700#M136961 ibrydon 2008-08-18T06:55:57Z Re: 2106 APs and Ping https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088701#M136962 <HTML><HEAD></HEAD><BODY><P>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"? </P></BODY></HTML> Mon, 18 Aug 2008 13:20:28 GMT https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088701#M136962 Scott Fella 2008-08-18T13:20:28Z Re: 2106 APs and Ping https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088702#M136963 <HTML><HEAD></HEAD><BODY><P>No, the management and AP management interfaces are not untagged they are assigned to VLAN 20.</P></BODY></HTML> Mon, 18 Aug 2008 14:31:00 GMT https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088702#M136963 ibrydon 2008-08-18T14:31:00Z Re: 2106 APs and Ping https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088703#M136964 <HTML><HEAD></HEAD><BODY><P>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.</P></BODY></HTML> Mon, 18 Aug 2008 14:43:06 GMT https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088703#M136964 Scott Fella 2008-08-18T14:43:06Z Re: 2106 APs and Ping https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088704#M136965 <HTML><HEAD></HEAD><BODY><P>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.</P></BODY></HTML> Mon, 18 Aug 2008 14:50:32 GMT https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088704#M136965 ibrydon 2008-08-18T14:50:32Z Re: 2106 APs and Ping https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088705#M136966 <HTML><HEAD></HEAD><BODY><P>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.</P></BODY></HTML> Mon, 18 Aug 2008 14:56:17 GMT https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088705#M136966 Scott Fella 2008-08-18T14:56:17Z Re: 2106 APs and Ping https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088706#M136967 <HTML><HEAD></HEAD><BODY><P>Thanks for your help, I think you are right.</P><P></P><P></P></BODY></HTML> Tue, 19 Aug 2008 06:50:54 GMT https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088706#M136967 ibrydon 2008-08-19T06:50:54Z Re: 2106 APs and Ping https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088707#M136968 <HTML><HEAD></HEAD><BODY><P>No problem... let me know if you get it to work.</P></BODY></HTML> Tue, 19 Aug 2008 13:04:23 GMT https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088707#M136968 Scott Fella 2008-08-19T13:04:23Z Re: 2106 APs and Ping https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088708#M136969 <HTML><HEAD></HEAD><BODY><P>I spoke to TAC - they pointed me at bug fix CSCsj3229. Looks like there is a problem with directly connected WAPs to a 2106.</P></BODY></HTML> Tue, 19 Aug 2008 14:03:02 GMT https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088708#M136969 ibrydon 2008-08-19T14:03:02Z Re: 2106 APs and Ping https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088709#M136970 <HTML><HEAD></HEAD><BODY><P>Is that the correct bug id? Looks like you are missing a digit.</P></BODY></HTML> Tue, 19 Aug 2008 14:08:05 GMT https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088709#M136970 Scott Fella 2008-08-19T14:08:05Z Re: 2106 APs and Ping https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088710#M136971 <HTML><HEAD></HEAD><BODY><P>should be CSCsj33229</P></BODY></HTML> Tue, 19 Aug 2008 14:10:48 GMT https://community.cisco.com/t5/wireless/2106-aps-and-ping/m-p/1088710#M136971 ibrydon 2008-08-19T14:10:48Z