On Thu, 2011-10-27 at 13:47 -0400, Faraz Syed wrote:
> We have few wireless devices which connects to Cisco 6500 series
> router.

s/router/switch/ ;-)

> We manage those wireless devices by using the trunk ports. We lose the
> management connectivity to certain hosts (wireless devices) for few
> hours and then it come back up by its own. Interesting thing is that
> the wireless link is always up and passing traffic.
> 
> If I check the arp table and it shows the Incomplete ARP entry for
> those hosts. It is not related to one wireless device that I can
> pinpoint there is the issue. There is no common factor in this issue,
> other than that they are all in VLAN101.

You haven't mentioned what the wireless devices are. I would suspect
that those are the real culprits.

> interface FastEthernet1/14
...
>  spanning-tree bpdufilter enable

Please consider if this configuration does what you really want. It
(probably) isn't relevant to the problem at hand but is IMO often an
erroneous configuration. You're preventing STP from working correctly.

The wireless devices we use (Cisco and Trapeze) never try to participate
in STP so the following is suitable:

 spanning-tree portfast trunk
 spanning-tree bpduguard enable

Portfast makes this an edge port so it does not impact topology
calculations and BPDU Guard prevents many common loop scenarios.

> cr.nyc0003.C.ny#sh arp | i Incomplete
...

Only about one in eight of the shown incomplete entries would belong to
Vlan101. That does not help the overall argument. The the list is
"tl;dr" -- you should clean it up and only show a couple of examples to
support your argument.

As said, I would take a long hard look at the wireless devices.

-- 
Peter

_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to