Switching

Hello!

 

Can anybody explain how works lldp between SRX and EX ?

Why in one case EX4200 (VC) shows two interfaces of SRX650 (Chassis cluster):

1.

 

{master:0}
vlazarev@EX4200-VC> show lldp neighbors
Local Interface Parent Interface Chassis Id 
ge-0/0/12.0        -                   00:10:db:ff:49:08   ge-2/0/0.0         SRX650-node1
.
.
.
ge-1/0/12.0        -                   00:10:db:ff:49:08   ge-11/0/0.0        SRX650-node1

 

 

2. here the output shows visibility of only one peer of interfaces:

   secondary interface of SRX650 (ge-11/0/4) is connected to interface ge-0/0/35(EX3200). 

Interfaces of EX3200 are not in ae.

 

 

vlazarev@EX3200-single> show lldp neighbors
Local Interface    Parent Interface    Chassis Id          Port info          System Name
ge-0/0/34.0        -                   00:10:db:ff:39:10   ge-2/0/4.0         

 

 

Can you please give the output of the interface  by giving show interfaces terse or show ethernet-switching interfaces (if L2)

Hello!

Right now cannot. I haven't the access to devices. (on monday only)

If you have any assumptions about it, please, share me.

Hi,

 

Since we do not have any outputs to go by, here is my assumption:

 

It looks like in the first case, the two interfaces are part of a reth interface and in the second case, the ge-11/0/4 on SRX is not member of a reth interface. If this is true then the output is expected behavior. In case of a reth interface, a virtual MAC is calculated on the SRX and both member interfaces use the same MAC. During failover, the MAC to port mapping on the switch changes to a different physical interface, probably that's why two interfaces in first output.

 

In second case if the interface is not part of a reth, then it is treated like any other normal standalone interface and you are seeing the expected output. Another possibility in second case is that a failover has not yet occured on the SR650. 

 

I may be completely off in my assumption. Please provide more outputs so that the community and assist you better.

 

Regards,

Srinath 

Hello!

 

In the first case such outputs of EX4200-VirtChass and SRX650-Cluster:

 

{master:0}
vvlazarev@EX4200-VC> show interfaces terse ge-*/0/12
Interface Admin Link Proto Local Remote
ge-0/0/12 up up
ge-1/0/12 up up




{primary:node1}
vvlazarev@SRX650-node1> show configuration | display set | match "redundant-parent reth0"
set interfaces ge-2/0/0 gigether-options redundant-parent reth0
set interfaces ge-11/0/0 gigether-options redundant-parent reth0

{primary:node1}
vvlazarev@SRX650-node1> show interfaces terse reth2.0
Interface Admin Link Proto Local Remote
reth2.0 up up inet 192.168.93.34/27

 In the second case:

{primary:node1}
vvlazarev@SRX650-node1> show configuration interfaces ge-2/0/4 | display set set interfaces ge-2/0/4 gigether-options redundant-parent reth4

{primary:node1}
vvlazarev@SRX650-node1> show configuration interfaces ge-11/0/4 | display set set interfaces ge-11/0/4 gigether-options redundant-parent reth4

{primary:node1}
vvlazarev@SRX650-node1-LPKH> show interfaces terse reth4
Interface Admin Link Proto Local Remote
reth4 up up
reth4.0 up up inet 10.10.10.254/24

vvlazarev@EX3200> show lldp neighbors
Local Interface Parent Interface Chassis Id Port info System Name
ge-0/0/34.0 - 00:10:db:ff:30:00 ge-2/0/4.0 SRX650-node1
ge-0/0/40.0 - 172.17.1.86 Port 1 Cisco IP Phone
ge-0/0/14.0 - 172.17.1.123 Port 1 Cisco IP Phone
ge-0/0/7.0 - 172.17.1.144 Port 1 Cisco IP Phone SPA303


vvlazarev@EX3200> show interfaces terse ge-0/0/34.0
Interface Admin Link Proto Local Remote
ge-0/0/34.0 up up eth-switch

 

Ideally only one interface ge-2/0/0 or ge-11/0/0 should show up as they are part of reth0.
Can you check the age of lldp neighbor and see if the interfaces are flapping?

No any idea how troubleshoot it. Totally hope you here.

 

{master:0}
vvlazarev@EX4200-VC> show lldp neighbors interface ge-0/0/12 | match Age:
LLDP Neighbor Information:
Local Information:
Index: 61 Time to live: 120 Time mark: Mon Apr  6 17:07:58 2015 Age: 3 secs

{master:0}
vvlazarev@EX4200-VC> show lldp neighbors interface ge-1/0/12 | match Age:
LLDP Neighbor Information:
Local Information:
Index: 108 Time to live: 120 Time mark: Mon Apr  6 17:07:54 2015 Age: 9 secs

{master:0}
vvlazarev@EX4200-VC> show lldp neighbors interface ge-0/0/12 | match Age:
LLDP Neighbor Information:
Local Information:
Index: 61 Time to live: 120 Time mark: Mon Apr  6 17:07:58 2015 Age: 7 secs

{master:0}
vvlazarev@EX4200-VC> show lldp neighbors interface ge-1/0/12 | match Age:
LLDP Neighbor Information:
Local Information:
Index: 108 Time to live: 120 Time mark: Mon Apr  6 17:07:54 2015 Age: 13 secs

{master:0}
vvlazarev@EX4200-VC> show lldp neighbors interface ge-0/0/12 | match Age:
LLDP Neighbor Information:
Local Information:
Index: 61 Time to live: 120 Time mark: Mon Apr  6 17:07:58 2015 Age: 10 secs

{master:0}
vvlazarev@EX4200-VC> show lldp neighbors interface ge-1/0/12 | match Age:
LLDP Neighbor Information:
Local Information:
Index: 108 Time to live: 120 Time mark: Mon Apr  6 17:07:54 2015 Age: 16 secs

 

vvlazarev@EX4200-VC> show lldp neighbors

 

ge-0/0/12.0        -                   00:10:db:ff:48:30   ge-2/0/0.0         SRX650-node1
ge-0/0/13.0        -                   00:10:db:ff:48:30   ge-2/0/1.0         SRX650-node1
ge-0/0/14.0        -                   00:10:db:ff:48:30   ge-2/0/2.0         SRX650-node1
ge-0/0/15.0        -                   00:10:db:ff:48:30   ge-2/0/3.0         SRX650-node1
ge-0/0/16.0        -                   00:10:db:ff:48:30   ge-2/0/4.0         SRX650-node1
ge-0/0/17.0        -                   00:10:db:ff:48:30   ge-2/0/5.0         SRX650-node1
ge-0/0/18.0        -                   00:10:db:ff:48:30   ge-2/0/6.0         SRX650-node1
ge-0/0/19.0        -                   00:10:db:ff:48:30   ge-2/0/7.0         SRX650-node1
ge-0/0/5.0         -                   00:10:db:ff:48:30   ge-2/0/8.0         SRX650-node1
ge-1/0/12.0        -                   00:10:db:ff:48:30   ge-11/0/0.0        SRX650-node1
ge-1/0/13.0        -                   00:10:db:ff:48:30   ge-11/0/1.0        SRX650-node1
ge-1/0/14.0        -                   00:10:db:ff:48:30   ge-11/0/2.0        SRX650-node1
ge-1/0/15.0        -                   00:10:db:ff:48:30   ge-11/0/3.0        SRX650-node1
ge-1/0/16.0        -                   00:10:db:ff:48:30   ge-11/0/4.0        SRX650-node1
ge-1/0/17.0        -                   00:10:db:ff:48:30   ge-11/0/5.0        SRX650-node1
ge-1/0/18.0        -                   00:10:db:ff:48:30   ge-11/0/6.0        SRX650-node1
ge-1/0/19.0        -                   00:10:db:ff:48:30   ge-11/0/7.0        SRX650-node1
ge-1/0/5.0         -                   00:10:db:ff:48:30   ge-11/0/8.0        SRX650-node1
ge-1/0/20.0        -                   00:10:db:ff:48:30   ge-11/0/9.0        SRX650-node1
ge-0/0/20.0        -                   00:10:db:ff:48:30   ge-2/0/9.0         SRX650-node1
ge-1/0/10.0        -                   00:10:db:ff:48:30   ge-11/0/10.0       SRX650-node1
ge-0/0/10.0        -                   00:10:db:ff:48:30   ge-2/0/10.0        SRX650-node1
ge-1/0/23.0        -                   00:10:db:ff:48:30   ge-11/0/11.0       SRX650-node1

 

Can you post SRX config and "show chassis cluster information detail" outputs?

Sorry, right now there is no access to devices.(

It wiil be enough for me understand the concept behavior the Chassis Cluster Srx with different combination of juniper switches (here virtual chassis EX4200 and single EX3200) over LLDP. Maybe from your own experience! ) 

Hi Vlazarev,

As per release notes 12.1x46, LLDP is not supported on reth interface. Its an unsupported feature and thats the reason you see inconsistent behavior. It is not recomended to use unsupported configuration.

http://www.juniper.net/techpubs/en_US/junos12.1x46/information-products/topic-collections/release-notes/12.1x46/index.html?topic-82923.html

Hello.

I've seen this restriction for branch srx before. seems strange why EX shows SRX in lldp neighbors ! 

But, let's close this question at last. Thanks!