[f-nsp] Brocade ARP Issues

[Kennedy, Joseph]

Salman,

It’s difficult to say without seeing the configurations so pardon me if I ask some silly questions.

1. Gateway exists in VE on the edge FCX in ALL cases or are you bridging a few vlans where necessary(hybrid) in distribution? RSTP on edge vlans?
2. If you’re totally L3 to the edge are you leaving uplinks in the default vlan and marking them route-only, creating two separate vlans and leaving one uplink untagged in each, or tagged between distribution and edge in case you have to bridge later?(I’m assuming you aren’t using route-only globally on the edge and you only uplink each edge switch to distribution by two uplinks, but please correct me if I’m off the mark).
3. Is your distribution layer set to route-only globally or on an interface basis(hybrid edge of course precludes globally)?
4. Have you enabled or disabled global-stp on your distribution and edge switches?
5. Can you confirm that ECMP is working as expected between each of the tiers?
6. Do you run PIM and if so are you running SM or DM?


--JK

On Nov 7, 2013, at 10:48 AM, salman sadiq <salmanravian at gmail.com> wrote:

> Dear Experts,
>              We have a huge Brocade infrastructure deployed in a very hierarchical manner. The core devices (4 fully meshed) are MLX-32s, distribution (FCX,SXR) and access (mostly FCX). Access layer acts as the GW for the end clients and OSPF takes care of all the routing. We have seen a lot of connectivity issues in the network where an end client loses connectivity to the network, ie the client remains connected but cannot access anything. In some cases we have seen one-way voice issues as well. All looks good on the switches but there are repeated instances of problematic connectivity. The arp entry is always there. I've looked at the tcam mapping for some cases and it looks good too. The problem is always resolved by a "clear arp" either on the access switch or in some cases on the distribution device. 
> 
> Problem with the ARP is so fundamental in nature that I find it hard to swallow considering the fact that Brocade has a large customer base. TAC has been trying to root cause the problem but with no success at all. Has anyone else seen such issues? In our network we have to deal with such cases almost on daily basis.
> 
> MLX is 5.4d
> FCX is 7202d and 7.4d
> 
> Thank you.
> Salman 
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp