This KB defines a debugging scenario around vSRX cluster nodes not able to see each other over the fabric link
- vSRX VM is UP as seen on both NFX i.e. node0 and node1
- Both nodes show as Primary
NFX cluster internal connections are as follows:
[ JCP ---Linux --- GWR(vSRX)]
For a cluster, an interface from NFX is directly connected between the 2 nodes. Line connection becomes :
[GWR(vSRX-node0---Linux) --- JCP--- ]===[--- JCP ---Linux --- GWR(vSRX-node1)]
Connected interfaces between the 2 nodes need to be first debugged.
1. Check the Config for the directly connected interface.
Example:
set interface ae0 mtu 2048
set interface ae0 aggregated-ether-options minimum-links 1
set interface ae0 aggregated-ether-options lacp active
set interface ae0 aggregated-ether-options lacp periodic fast
set interface ae0 unit 0 family ethernet-switching interface-mode trunk
set interface ae0 unit 0 family ethernet-switching vlan members CLUSTER-C
set interface ae0 unit 0 family ethernet-switching vlan members CLUSTER-DATA
set vlans CLUSTER-C vlan-id 3000
set vlans CLUSTER-DATA vlan-id 3001
set interface ge-0/0/12 ether-options 802.3ad ae0;
set interface ge-0/0/13 ether-options 802.3ad ae0;
2. Check the hardware details for the said interface and check the xfp details for the said interface.
{master:0}
jdm-sysuser@vjunos0> show chassis hardware
Hardware inventory:
Item Version Part number Serial number Description
Chassis DD2116AF0021 NFX250-S2
Pseudo CB 0
Routing Engine 0 BUILTIN BUILTIN RE-NFX250-S2
FPC 0 REV 03 650-066113 DD2116AF0021 NFX250-S2
CPU BUILTIN BUILTIN FPC CPU
PIC 0 REV 03 BUILTIN BUILTIN 10x10/100/1000 Base-T-2x1G SFP-2x10G SFP+
Xcvr 10 REV 01 740-011782 PAB06FT SFP-SX
Xcvr 11 REV 01 740-031851 AM152428WCZ SFP-SX
Xcvr 12 REV 01 740-031980 AA17483090K SFP+-10G-SR
Xcvr 13 REV 01 740-031980 AA1737309VF SFP+-10G-SR
Power Supply 0
Fan Tray 0 fan-ctrl-0 0, Front to Back Airflow - AFO
Fan Tray 1 fan-ctrl-0 1, Front to Back Airflow - AFO
3. Check the interface config
jdm-sysuser@vjunos0> show interfaces terse
Interface Admin Link Proto Local Remote
ge-0/0/0 up down
ge-0/0/0.16386 up down
sxe-0/0/0 up up
sxe-0/0/0.0 up up eth-switch
ge-0/0/1 up down
ge-0/0/1.16386 up down
sxe-0/0/1 up up
sxe-0/0/1.0 up up eth-switch
ge-0/0/2 up down
ge-0/0/2.16386 up down
ge-0/0/3 up down
ge-0/0/3.16386 up down
ge-0/0/4 up down
ge-0/0/4.16386 up down
ge-0/0/5 up up
ge-0/0/5.0 up up eth-switch
ge-0/0/6 up down
ge-0/0/6.16386 up down
ge-0/0/7 up down
ge-0/0/7.16386 up down
ge-0/0/8 up down
ge-0/0/8.16386 up down
ge-0/0/9 up up
ge-0/0/9.0 up up eth-switch
ge-0/0/10 up up
ge-0/0/10.0 up up eth-switch
ge-0/0/11 up up
ge-0/0/11.0 up up eth-switch
xe-0/0/12 up up
xe-0/0/12.16386 up up
xe-0/0/13 up up
xe-0/0/13.16386 up up
Important: The 12 and 13 interface can host both a 1G or a 10G XFP and depending upon what a user inserts the interface is listed as a ge or xe.
If the config is ge and 10G XFP is plugged in, even if the interface shows as UP, traffic won't flow as the config won't be applied to the correct interface.
So to resolve this:
Replace the 10G XFP with a 1G XFP and config ge interface under "show interface terse" output
xe-0/0/12.0 up up aenet --> ae0.0
xe-0/0/13.0 up up aenet --> ae0.0
2024-06-07 : Article Created - Initial Draft