[j-nsp] Topology failure on EX4200

[Victor Sudakov]

Dear Colleagues,

There is a ring of EX4200 switches, please look at 
http://noc.sibptus.ru/jun1.png

If MUX1 fails, the MSTP topology adjusts and the PCs continue to see
one another just fine.

However, some switches become inaccessible in the management vlan
(vlan3 in this example). For example, you can still ping 192.168.1.3
from 192.168.1.2, but not 192.168.1.4 from 192.168.1.2.

One important note. If MUX1 fails, the corresponding interfaces on
192.168.1.2 and 192.168.1.4 don't go down, it is only the traffic
(including BPDUs) that stops flowing through the mux.

If I shutdown the corresponding interfaces on 192.168.1.2 and
192.168.1.4 (or use OAM to shutdown the interfaces automatically when
the mux fails), the problem disappears and I can ping any switch from
any switch.

What's the theory behind this?

"clear arp" and "clear ethernet-switching table" don't fix the
problem.

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
AS43859
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] MC-LAG on QFX5100

[Matt Freitag]

Is there something preventing you from using VCF or qfabric?

On Jul 9, 2017 7:25 AM, "Vincent Bernat"  wrote:

>  ❦  9 juillet 2017 09:07 GMT, "Jackson, William" <
> william.jack...@gibtele.com> :
>
> > We have been testing an MC-LAG active/active setup on qfx5100 using the
> latest 14.1x53 code.
> > We are seeing issues when using L3 in the MC-LAG.
> > We are using IRB with VRRP on a number of vlans that face the downstream
> client.
> > It seems that in active/active both nodes process traffic even if they
> > are not the VRRP master, so we have taken that into account.
> >
> > The issue we are seeing seems to be that the ARP sync is not working on
> the ICCP between the peers.
> > We can reach downstream nodes via one peer but not the other.
> > And it works correctly on some vlans but not others so isn’t related to
> the downstream client.
> >
> > JTAC is on it albeit at snail’s pace.
> >
> > Has anyone got this working on qfx5100 and can share some config
> > examples?
>
> I ran into similar limitations with the same version. I have tried both
> MAC synchronization and VRRP. When packets hit the "wrong" node (the one
> that didn't learn the neighbor information), they are not
> forwarded. See:
>
>  https://lists.gt.net/nsp/juniper/60956#60956
>
> I got additional private feedback from people with similar issues
> (MC-LAG and L3 forwarding). I didn't try to involve JTAC.
> --
> Don't stop at one bug.
> - The Elements of Programming Style (Kernighan & Plauger)
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] MC-LAG on QFX5100

[Vincent Bernat]

 ❦  9 juillet 2017 09:07 GMT, "Jackson, William"  :

> We have been testing an MC-LAG active/active setup on qfx5100 using the 
> latest 14.1x53 code.
> We are seeing issues when using L3 in the MC-LAG.
> We are using IRB with VRRP on a number of vlans that face the downstream 
> client.
> It seems that in active/active both nodes process traffic even if they
> are not the VRRP master, so we have taken that into account.
>
> The issue we are seeing seems to be that the ARP sync is not working on the 
> ICCP between the peers.
> We can reach downstream nodes via one peer but not the other.
> And it works correctly on some vlans but not others so isn’t related to the 
> downstream client.
>
> JTAC is on it albeit at snail’s pace.
>
> Has anyone got this working on qfx5100 and can share some config
> examples?

I ran into similar limitations with the same version. I have tried both
MAC synchronization and VRRP. When packets hit the "wrong" node (the one
that didn't learn the neighbor information), they are not
forwarded. See:

 https://lists.gt.net/nsp/juniper/60956#60956

I got additional private feedback from people with similar issues
(MC-LAG and L3 forwarding). I didn't try to involve JTAC.
-- 
Don't stop at one bug.
- The Elements of Programming Style (Kernighan & Plauger)
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] MC-LAG on QFX5100

[Jackson, William]

Hi

We have been testing an MC-LAG active/active setup on qfx5100 using the latest 
14.1x53 code.
We are seeing issues when using L3 in the MC-LAG.
We are using IRB with VRRP on a number of vlans that face the downstream client.
It seems that in active/active both nodes process traffic even if they are not 
the VRRP master, so we have taken that into account.

The issue we are seeing seems to be that the ARP sync is not working on the 
ICCP between the peers.
We can reach downstream nodes via one peer but not the other.
And it works correctly on some vlans but not others so isn’t related to the 
downstream client.

JTAC is on it albeit at snail’s pace.

Has anyone got this working on qfx5100 and can share some config examples?

Many thanks



___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp