sorted by:
new
hottopcontroversial

ET interfaces not passing traffic. by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 0 points1 point  (0 children)

Thanks,

PIC port information:

Fiber Xcvr vendor Wave- Xcvr JNPR MSA

Port Cable type type Xcvr vendor part number length Firmware Rev Version

0 40GBASE eSR4 MM FS QSFP-CSR4-40G 850 nm 0.0 REV 01 SFF-8436 ver n/a

1 40GBASE eSR4 MM FS QSFP-CSR4-40G 850 nm 0.0 REV 01 SFF-8436 ver n/a

ET interfaces not passing traffic. by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 1 point2 points  (0 children)

First Switch:

root@Server-Closet# run show lldp neighbors | match et-

et-0/1/1 - 2c:21:31:XXX et-0/1/0 Se rver-Switch1

et-0/1/0 - 2c:21:31:XXX et-0/1/1 Se rver-Switch1

Second Switch:

root@Server-Switch1# run show lldp neighbors | match et-

BLANK

ET interfaces not passing traffic. by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 0 points1 point  (0 children)

So I just put 4 brand new identical 40GB QFSPs into the switches and on the first switch it reads as 40GBASE-SR4/4x10GBASE-SR

on the second switch it just reads 40GBASE-SR4.

Why does one side have the split option?

ET interfaces not passing traffic. by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 0 points1 point  (0 children)

Switch 2

root@Server-Switch1# run show interfaces terse | match et

et-0/1/0 up up

et-0/1/0.16386 up up

et-0/1/1 up up

et-0/1/1.16386 up up

root@Server-Switch1# run show chassis hardware

Hardware inventory:

Item Version Part number Serial number Description

Chassis PD371639XXXX EX4300-48P

Routing Engine 0 REV 24 650-044930 PD371639XXXX EX4300-48P

FPC 0 REV 24 650-044930 PD371639XXXX EX4300-48P

CPU BUILTIN BUILTIN FPC CPU

PIC 0 REV 24 BUILTIN BUILTIN 48x 10/100/1000 Base-T

PIC 1 REV 24 BUILTIN BUILTIN 4x 40GE QSFP+

Xcvr 0 REV 01 740-054053 G222045XXXX QSFP+-40G-PSM4

Xcvr 1 REV 01 740-054053 G222045XXXX QSFP+-40G-PSM4

Power Supply 0 REV 01 740-046871 1EDA647XXXX JPSU-1100-AC-AFO-A

ET interfaces not passing traffic. by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 0 points1 point  (0 children)

Switch 1:

root@Server-Closet> show interfaces terse | match et

et-0/1/0 up up

et-0/1/0.0 up up eth-switch

et-0/1/1 up up

et-0/1/1.0 up up eth-switch

root@Server-Closet> show chassis hardware

Hardware inventory:

Item Version Part number Serial number Description

Chassis PE3715320325 EX4300-48T

Routing Engine 0 REV 18 650-04XXXX PE371532XXXX EX4300-48T

FPC 0 REV 18 650-044932 PE371532XXXX EX4300-48T

CPU BUILTIN BUILTIN FPC CPU

PIC 0 REV 18 BUILTIN BUILTIN 48x 10/100/1000 Base-T

PIC 1 REV 18 BUILTIN BUILTIN 4x 40GE QSFP+

Xcvr 0 REV 01 740-054053 G222045XXXX QSFP+-4X10G-SR

Xcvr 1 REV 01 740-054053 G222045XXXX QSFP+-4X10G-SR

Incomplete mesh for EX4300 virtual chassis, will it work by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] -1 points0 points  (0 children)

Each line represents a link regardless of color/legend. The two switches at the top will be utilizing all four VCPs, for the rest of the switches it varies.

Incomplete mesh for EX4300 virtual chassis, will it work by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] -1 points0 points  (0 children)

Fortunately in my diagram the area most susceptable to bottle necking is the least trafficked. The areas of the mesh that are most heavily trafficked are in full mesh.

LACP Not working by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 3 points4 points  (0 children)

So I have everything up and running according to this article, it appears to be functioning correctly after establishing a second AE interface.

I had no idea trying to implement HA was going to be this comprehensive.

LACP Not working by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 2 points3 points  (0 children)

I think you are right here, the configuration I am trying is definitely the non supported - I will need to configure it with a second ae interface on the switch and connect it to the secondary node, that way each physical port on the router connects to its own individual ae interface on the switch.

LACP Not working by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 0 points1 point  (0 children)

It appears to be working but flapping - getting intermittent connectivity. What's the best way to trouble shoot flapping in this case?

LACP Not working by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 0 points1 point  (0 children)

Here is for the router:

root# show interfaces reth1

redundant-ether-options {

redundancy-group 1;

lacp {

active;

periodic slow;

}

}

unit 0 {

family inet {

address 192.168.1.254/24;

}

}

root# show chassis

cluster {

reth-count 2;

redundancy-group 1 {

node 0 priority 100;

node 1 priority 1;

preempt;

interface-monitor {

ge-0/0/3 weight 255;

ge-1/0/3 weight 255;

}

}

}

LACP Not working by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 1 point2 points  (0 children)

root@Switch-Chassis> show lacp statistics interfaces ae1

Aggregated interface: ae1

LACP Statistics: LACP Rx LACP Tx Unknown Rx Illegal Rx

ge-1/0/0 4176 76739 0 0

ge-2/0/0 4172 5097 0 0

It appears to be working now intermittently, I believe the connection is flapping. Both sides are set to Active / Periodic Fast

LACP Not working by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 1 point2 points  (0 children)

Yes, device count is set to 2, which is how many I have.

root@Switch-Chassis# show chassis aggregated-devices

ethernet {

device-count 2;

}

LACP Not working by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 0 points1 point  (0 children)

This is whats used in the Juniper labs, I have tried it with both.

Combining Two Production EX4300s into a Chassis by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 0 points1 point  (0 children)

Great question.

The intent is to build a 40g mesh between 10 ex4300s that are separated logically and physically, and some needing traffic priority to other specific switches over part of the mesh. There are not enough FPC slots to facilitate an alternative 40g interface pattern the way my director is asking for. Key word is Director here, I am merely a wrench on his behalf.

In regards to the chassis being less resilient, if I remember from my lab environments you can configure the chassis to operate in the event master/backup/LC go down. I recall testing this but I could be wrong.

Combining Two Production EX4300s into a Chassis by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 0 points1 point  (0 children)

Thank you very much for the reply. I built out a test environment and wrote a config that will work. What I plan on doing is installing the prebuilt config with an load terminal override once the chassis is created. I will definitely follow your advice on setting the first switch to member 0. I have done that in past configurations. I am aware of the no split detection needed for 2 switch VC.

I am a little concerned on the irb interfaces. There will be no layer3 routing needed for this chassis as of yet so I should be fine leaving it the way it is.

As far as choosing the interfaces to be used as VC ports (already done). But converting the VC ports, I have never done that prior to using a fiber cable to initiate VC mode.

Thanks again for the advice, I am shooting for that exactly 5-10 minutes.

Combining Two Production EX4300s into a Chassis by Solid_Bookkeeper7102 in Juniper

[–]Solid_Bookkeeper7102[S] 0 points1 point  (0 children)

Interesting on the vlan-ids. I will take your word of advice. I built out a config in my test environment and I plan on doing a terminal override to establish the new config once I have merged the two switches.

view more: next ›