Quantcast
Channel: All Ethernet Switching posts
Viewing all articles
Browse latest Browse all 10307

Re: Ex4300 Virtual Chassis member issue

$
0
0

Hi 

 

Thank you very much for your help. I am trying to understand the situation based from what you all said in order to resolve this issue.

 

So here is the chassis status of our SRX. The reth2/RG2 is used for testing and will be for our ISP. So reth0 and reth1 are the connection from SRX to EX. LACP is also not configured on any devices. As far as I understand your reply, I think because the routing engine of our SRX are on active/active, which is why it didn't work on non-AE EX interfaces.

 

Routing Engine 0 status:
State Online Master
Temperature 38 degrees C / 100 degrees F
CPU Temperature 34 degrees C / 93 degrees F

node1:
--------------------------------------------------------------------------
Routing Engine 0 status:
State Online Master
Temperature 38 degrees C / 100 degrees F
CPU Temperature 37 degrees C / 98 degrees F

--------------------------------------------------------------------------------------

root@SRX-B# run show chassis cluster status

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

 

Redundancy group: 0 , Failover count: 0
node0 100 primary no no None
node1 50 secondary no no None

 

Redundancy group: 1 , Failover count: 5
node0 50 secondary yes no None
node1 100 primary yes no None

 

Redundancy group: 2 , Failover count: 1
node0 50 secondary yes no None
node1 100 primary yes no None

-------------------------------------------------------------------------

root@SRX-B# run show chassis cluster interfaces
Control link status: Up

Control interfaces:
Index Interface Status Internal-SA
0 fxp1 Up Disabled

Fabric link status: Up

Fabric interfaces:
Name Child-interface Status
(Physical/Monitored)
fab0 ge-0/0/2 Up / Up
fab0
fab1 ge-5/0/2 Up / Up
fab1

Redundant-ethernet Information:
Name Status Redundancy-group
reth0 Up 1
reth1 Up 1
reth2 Up 2
reth3 Down Not configured

Redundant-pseudo-interface Information:
Name Status Redundancy-group
lo0 Up 0

Interface Monitoring:
Interface Weight Status Redundancy-group
ge-5/0/15 255 Up 1
ge-0/0/15 255 Up 1
ge-5/0/14 255 Up 1
ge-0/0/14 255 Up 1
ge-5/0/7 255 Up 2
ge-0/0/7 255 Up 2

-----------------------------------------------------------------

Here is how we setup the reths:

 

set interfaces ge-0/0/7 gigether-options redundant-parent reth2
set interfaces ge-0/0/14 gigether-options redundant-parent reth0
set interfaces ge-0/0/15 gigether-options redundant-parent reth1
set interfaces ge-5/0/7 gigether-options redundant-parent reth2
set interfaces ge-5/0/14 gigether-options redundant-parent reth0
set interfaces ge-5/0/15 gigether-options redundant-parent reth1

set interfaces reth0 redundant-ether-options redundancy-group 1
set interfaces reth0 redundant-ether-options minimum-links 1
set interfaces reth0 redundant-ether-options lacp active
set interfaces reth0 unit 0 family inet address 10.10.0.1/24
set interfaces reth1 redundant-ether-options redundancy-group 1
set interfaces reth1 redundant-ether-options minimum-links 1
set interfaces reth1 redundant-ether-options lacp active
set interfaces reth1 unit 0 family inet address 10.10.0.2/24
set interfaces reth2 vlan-tagging
set interfaces reth2 redundant-ether-options redundancy-group 2
set interfaces reth2 unit 0 family inet address 210.4.118.114/29
deactivate interfaces reth2 unit 0
set interfaces reth2 unit 60 vlan-id 60
set interfaces reth2 unit 60 family inet address 210.4.118.114/29


Viewing all articles
Browse latest Browse all 10307

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>