Hello Ajaz,
Sample configuration is as below (On SRX240):
1) To enable cluster:
On device A:
set chassis cluster cluster-id 1 node 0 reboot
On device B:
set chassis cluster cluster-id 1 node 1 reboot
2) Define group for Node specific configuration & apply it. Includes configuring Management IPs.
On device A:
{primary:node0}
set groups node0 system host-name <name-node0> -Device A's host name
set groups node0 interfaces fxp0 unit 0 family inet address <ip address/mask> -Device A's management IP address on fxp0 interface
set groups node1 system host-name <name-node1> -Device B's host name
set groups node1 interfaces fxp0 unit 0 family inet address <ip address/mask -Device B's management IP address on fxp0 interface
set apply-groups "${node}"
3) Configuring Fabric links. No specific command for control links on branch as for every platform specific predefined interfaces become control port automatically.
On device A:
{primary:node0}
*fab0 is node0 (Device A) interface for the data link
set interfaces fab0 fabric-options member-interfaces ge-0/0/2
*fab1 is node1 (Device B) interface for the data link
set interfaces fab1 fabric-options member-interfaces ge-5/0/2
4) Redundancy Group Configuration for RG0 & RG1 with node specific priorities to decide who will be master & who will be backup.
On device A:
{primary:node0}
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
5) Interface configuration in Layer 2 Mode:
a) In access mode:
On device A:
{primary:node0}
set chassis cluster reth-count 2
set interfaces ge-0/0/4 gigether-options redundant-parent reth0
set interfaces ge-0/0/3 gigether-options redundant-parent reth1
set interfaces ge-5/0/4 gigether-options redundant-parent reth0
set interfaces ge-5/0/3 gigether-options redundant-parent reth1
set interfaces reth0 redundant-ether-options redundancy-group 1
set interfaces reth0 unit 0 family bridge interface-mode access
set interfaces reth0 unit 0 family bridge vlan-id 50
set interfaces reth1 redundant-ether-options redundancy-group 1
set interfaces reth1 unit 0 family bridge interface-mode access
set interfaces reth1 unit 0 family bridge vlan-id 50
b) In Trunk Mode:
On device A:
{primary:node0}
set chassis cluster reth-count 2F
set interfaces ge-0/0/4 gigether-options redundant-parent reth0
set interfaces ge-0/0/3 gigether-options redundant-parent reth1
set interfaces ge-5/0/4 gigether-options redundant-parent reth0
set interfaces ge-5/0/3 gigether-options redundant-parent reth1
set interfaces reth0 redundant-ether-options redundancy-group 1
set interfaces reth0 vlan-tagging
set interfaces reth0 native-vlan-id 10
set interfaces reth0 unit 0 family bridge interface-mode trunk
set interfaces reth0 unit 0 family bridge vlan-id-list 50-60
set interfaces reth1 redundant-ether-options redundancy-group 1
set interfaces reth1 unit 0 family bridge interface-mode trunk
set interfaces reth1 unit 0 family bridge vlan-id-list 50-60
set interfaces reth1 vlan-tagging
set interfaces reth1 native-vlan-id 10
6) Zone configuration:
set security zones security-zone untrust interfaces reth0.0
set security zones security-zone trust interfaces reth1.0
Bridge domains can be configured using link below:
http://kb.juniper.net/InfoCenter/index?page=content&id=KB21421
Security policies, NAT, Routing etc. should be configured as per requirement.
Regards,
Rushi