<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Cant ping ap ip in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/cant-ping-ap-ip/m-p/2237386#M133735</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check the arp table on the router?&amp;nbsp; If your using h-reap and the h-reap is on an access port, then the user traffic and the ap management will be on the same vlan which is untagged.&amp;nbsp; If you will have the user traffic different than the ap management, then you need to use a trunk port with the native as the management for the AP and only allow the vlans for your ssids.&amp;nbsp; You will need to enable the native vlan tagging on the AP and also the wlan to vlan mapping.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;BR /&gt; &lt;BR /&gt;Scott &lt;BR /&gt; &lt;BR /&gt;Help out other by using the rating system and marking answered questions as "Answered"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 08 Jul 2013 16:54:18 GMT</pubDate>
    <dc:creator>Scott Fella</dc:creator>
    <dc:date>2013-07-08T16:54:18Z</dc:date>
    <item>
      <title>Cant ping ap ip</title>
      <link>https://community.cisco.com/t5/wireless/cant-ping-ap-ip/m-p/2237383#M133732</link>
      <description>&lt;P&gt;Hello all,&lt;BR /&gt;&lt;BR /&gt;Today I came across a strange issue.&lt;BR /&gt;I have a lightweight ap installed at a remote branch office.&lt;BR /&gt;Flex connect and local switching has been enabled.&lt;BR /&gt;&lt;BR /&gt;The interesting thing is that there were two issues:&lt;BR /&gt;&lt;BR /&gt;A. The clients were disconnecting sporadically and then reconnecting again.&lt;BR /&gt;B. Strangely I could not ping the ap ip address only while I was connected to it through wireless. But rest connectivity was working absolutely fine. I could get an ip address and access the Internet and everything. To make it even more strange, I could ping the ap ip address while connects through wired!!!&lt;BR /&gt;&lt;BR /&gt;Finally after many tries, I found that both the issues seemed to get solved when I enabled central switching!!!&lt;BR /&gt;&lt;BR /&gt;What could be the issue here, any ideas? &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support Android App&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 07:22:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cant-ping-ap-ip/m-p/2237383#M133732</guid>
      <dc:creator>rahul nair</dc:creator>
      <dc:date>2021-07-04T07:22:10Z</dc:date>
    </item>
    <item>
      <title>Re: Cant ping ap ip</title>
      <link>https://community.cisco.com/t5/wireless/cant-ping-ap-ip/m-p/2237384#M133733</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check the arp table?&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jul 2013 14:25:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cant-ping-ap-ip/m-p/2237384#M133733</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2013-07-08T14:25:11Z</dc:date>
    </item>
    <item>
      <title>Re:Cant ping ap ip</title>
      <link>https://community.cisco.com/t5/wireless/cant-ping-ap-ip/m-p/2237385#M133734</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hmm.. No. You mean, check the arp table in the ap?&lt;BR /&gt;I ll check and let you know.&lt;BR /&gt;&lt;BR /&gt;By that time, what could be the reason for random packet drops in local switching?&lt;BR /&gt;I mean I have not set "Vlan support" under hreap tab of the ap, in the controller.&lt;BR /&gt;Should I map it to any vlan?&lt;BR /&gt;&lt;BR /&gt;The switch port connected to the access point has been put in access mode.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support Android App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jul 2013 15:24:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cant-ping-ap-ip/m-p/2237385#M133734</guid>
      <dc:creator>rahul nair</dc:creator>
      <dc:date>2013-07-08T15:24:07Z</dc:date>
    </item>
    <item>
      <title>Cant ping ap ip</title>
      <link>https://community.cisco.com/t5/wireless/cant-ping-ap-ip/m-p/2237386#M133735</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check the arp table on the router?&amp;nbsp; If your using h-reap and the h-reap is on an access port, then the user traffic and the ap management will be on the same vlan which is untagged.&amp;nbsp; If you will have the user traffic different than the ap management, then you need to use a trunk port with the native as the management for the AP and only allow the vlans for your ssids.&amp;nbsp; You will need to enable the native vlan tagging on the AP and also the wlan to vlan mapping.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;BR /&gt; &lt;BR /&gt;Scott &lt;BR /&gt; &lt;BR /&gt;Help out other by using the rating system and marking answered questions as "Answered"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jul 2013 16:54:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cant-ping-ap-ip/m-p/2237386#M133735</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2013-07-08T16:54:18Z</dc:date>
    </item>
  </channel>
</rss>

