vSRX
Highlighted
vSRX

vSRX 3.0 chassis cluster betwwen two ESXi Host

2 weeks ago

Hi All

I have problem with the chassis cluster configuration for vSRX 3.0 betwwen two ESXi Host. The first is in the HQ site and the second is in the secondary site.  The Fabric vSwitch Properties for em0 and GE0/0/0 are setting  Promiscuous Mode , MAC Address Changes and Forged Transmits.

Please, see the troubleshooting command follow:

 

>show chassis cluster statistics
Control link statistics:
Control link 0:
Heartbeat packets sent: 67573
Heartbeat packets received: 0
Heartbeat packet errors: 0
Fabric link statistics:
Child link 0
Probes sent: 134616
Probes received: 0
Child link 1
Probes sent: 0
Probes received: 0
Services Synchronized:
Service name RTOs sent RTOs received
Translation context 0 0
Incoming NAT 0 0
Resource manager 0 0
DS-LITE create 0 0
Session create 0 0
IPv6 session create 0 0
Session close 0 0
IPv6 session close 0 0
Session change 0 0
IPv6 session change 0 0
ALG Support Library 0 0
Gate create 0 0
Session ageout refresh requests 0 0
IPv6 session ageout refresh requests 0 0
Session ageout refresh replies 0 0
IPv6 session ageout refresh replies 0 0
IPSec VPN 0 0
Firewall user authentication 0 0
MGCP ALG 0 0
H323 ALG 0 0
SIP ALG 0 0
SCCP ALG 0 0
PPTP ALG 0 0
JSF PPTP ALG 0 0
RPC ALG 0 0
RTSP ALG 0 0
RAS ALG 0 0
MAC address learning 0 0
GPRS GTP 0 0
GPRS SCTP 0 0
GPRS FRAMEWORK 0 0
JSF RTSP ALG 0 0
JSF SUNRPC MAP 0 0
JSF MSRPC MAP 0 0
DS-LITE delete 0 0
JSF SLB 0 0
APPID 0 0
JSF MGCP MAP 0 0
JSF H323 ALG 0 0
JSF RAS ALG 0 0
JSF SCCP MAP 0 0
JSF SIP MAP 0 0
PST_NAT_CREATE 0 0
PST_NAT_CLOSE 0 0
PST_NAT_UPDATE 0 0
JSF TCP STACK 0 0
JSF IKE ALG 0 0

 

>show chassis cluster status
Monitor Failure codes:
CS Cold Sync monitoring FL Fabric Connection monitoring
GR GRES monitoring HW Hardware monitoring
IF Interface monitoring IP IP monitoring
LB Loopback monitoring MB Mbuf monitoring
NH Nexthop monitoring NP NPC monitoring
SP SPU monitoring SM Schedule monitoring
CF Config Sync monitoring RE Relinquish monitoring
IS IRQ storm

Cluster ID: 1
Node Priority Status Preempt Manual Monitor-failures

Redundancy group: 0 , Failover count: 1
node0 200 primary no no None
node1 0 lost n/a n/a n/a

{primary:node0}

 

> show chassis cluster information
node0:
--------------------------------------------------------------------------
Redundancy Group Information:

Redundancy Group 0 , Current State: primary, Weight: 255

Time From To Reason
Jun 24 23:07:26 hold secondary Hold timer expired
Jun 24 23:07:42 secondary primary Only node present

Chassis cluster LED information:
Current LED color: Red
Last LED change reason: Peer node: node1 is not present

Failure Information:

Fabric-link Failure Information:
Fabric Interface: fab0
Child interface Physical / Monitored Status
ge-0/0/0 Up / Down

Control-link Failure Information:
Link Status: Up
Dual Control Link Status: Unsupported

Interface Physical / Monitored Status
em0 Up / Down

{primary:node0}

 

TIA
Cristian

3 REPLIES 3
Highlighted
vSRX

Re: vSRX 3.0 chassis cluster betwwen two ESXi Host

2 weeks ago

Your status commands show that the fabric link between the two nodes is not connected.  If the connection were working the commands would show both nodes.

 

You will need to troubleshoot the vswitch connectivity connecting the ports between the two nodes.

 

Steve Puluka BSEET - Juniper Ambassador
IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
http://puluka.com/home
Highlighted
vSRX

Re: vSRX 3.0 chassis cluster betwwen two ESXi Host

2 weeks ago

Dear Steve

Thank yo u for your answer. The vSwitch admin has it the customer. There are some command or log where can I analyze and identify that the problem is the connection to the vSwitch?

TIA
Cristian

Highlighted
vSRX

Re: vSRX 3.0 chassis cluster betwwen two ESXi Host

2 weeks ago

The command you have above

show chassis cluster information

 

Has the link status for the two links you need to connect between node 0 and node 1

This shows that the fabric link ge-0/0/0 between the nodes is not connected.

 

Fabric Interface: fab0
Child interface Physical / Monitored Status
ge-0/0/0 Up / Down

Control-link Failure Information:
Link Status: Up

 

Steve Puluka BSEET - Juniper Ambassador
IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
http://puluka.com/home