Cluster Configuration For Juniper SRX 210 and EX2200 Virtual Chassis Configuration

You should use fe-0/0/7 as a control link(it is must ) and ge0/0/0 as a fabric link(it is optional) that is necessary for clustering;

Firstly
for srx a ;
root@host> set chassis cluster cluster-id 1 node 0 reboot

for srxb;
root@host> set chassis cluster cluster-id 1 node 1 reboot

set groups node0 system host-name SRXA
set groups node1 system host-name SRXB
set apply-groups "${node}"

set system root-authentication encrypted-password "$1$mBD9U/mY$p22ieordGU1/W9.HlK8lu."

set chassis cluster reth-count 28
set chassis cluster redundancy-group 0 node 0 priority 100
set chassis cluster redundancy-group 0 node 1 priority 1
set chassis cluster redundancy-group 1 node 0 priority 100
set chassis cluster redundancy-group 1 node 1 priority 1
set chassis cluster redundancy-group 1 preempt

set interfaces ge-0/0/1 gigether-options redundant-parent reth0
set interfaces fe-0/0/2 fastether-options redundant-parent reth2
set interfaces fe-0/0/3 fastether-options redundant-parent reth3
set interfaces ge-1/0/0 gigether-options redundant-parent reth1
set interfaces ge-2/0/1 gigether-options redundant-parent reth0
set interfaces fe-2/0/2 fastether-options redundant-parent reth2
set interfaces fe-2/0/3 fastether-options redundant-parent reth3
set interfaces ge-3/0/0 gigether-options redundant-parent reth1

set interfaces fab0 fabric-options member-interfaces ge-0/0/0
set interfaces fab1 fabric-options member-interfaces ge-2/0/0

set interfaces reth0 redundant-ether-options redundancy-group 1
set interfaces reth0 unit 0 family inet address 172.16.0.1/24
set interfaces reth1 redundant-ether-options redundancy-group 1
set interfaces reth1 unit 0 family inet address 172.16.1.1/24
set interfaces reth2 redundant-ether-options redundancy-group 1
set interfaces reth2 unit 0 family inet address 172.16.2.1/24
set interfaces reth3 redundant-ether-options redundancy-group 1
set interfaces reth3 unit 0 family inet address 172.16.3.1/24

set security policies from-zone LOCAL to-zone LOCAL policy LOCALTOLOCAL match source-address any
set security policies from-zone LOCAL to-zone LOCAL policy LOCALTOLOCAL match destination-address any
set security policies from-zone LOCAL to-zone LOCAL policy LOCALTOLOCAL match application any
set security policies from-zone LOCAL to-zone LOCAL policy LOCALTOLOCAL then permit

set security zones security-zone LOCAL host-inbound-traffic system-services all
set security zones security-zone LOCAL host-inbound-traffic protocols all
set security zones security-zone LOCAL interfaces reth0.0
set security zones security-zone LOCAL interfaces reth1.0
set security zones security-zone LOCAL interfaces reth2.0
set security zones security-zone LOCAL interfaces reth3.0

if you want to cancel clustering

set chassis cluster disable reboot

https://www.juniper.net/support/tools/srxha/




-----
Virtual Chassis Configuration for SW



Firstly you should connect two devices with cat cables and that cat cables port will be 23 and 24.

 request virtual-chassis vc-port set pic-slot 0 port 23 (it doesnt necessary at ex3300, you can use fiber port and dont need any configuration you can pass this step)
 request virtual-chassis vc-port set pic-slot 0 port 24 (it doesnt necessary at ex3300)

at master device 
set virtual-chassis preprovisioned
set virtual-chassis no-split-detection
set virtual-chassis member 0 role routing-engine
set virtual-chassis member 0 serial-number GD0216340209
set virtual-chassis member 1 role routing-engine
set virtual-chassis member 1 serial-number GD0216340288

you can see master and backup devices ;

show virtual-chassis status

for removing Virtual-Chassis

delete virtual-chassis
commit

start shell
root@%cd /config/vchassis/ 
root@::0% ls 
vc.db vc.param
vc.tlv.db
root@:LC:0% rm *.*