J-Series Clustering
Configuring a J-Series router for clustering is a fairly simple process. When clustering is enabled, the physical interfaces are set in order, with node0 starting at x, and node1 starting at x+7. For example, if node0’s physical interfaces were ge-1/0/0 and ge-1/0/1, then node1’s interfaces would become ge-8/0/0 and ge-8/0/1. The detailed steps are explained below.
Diagram
Initial Cluster Configuration
Connect using a serial console. You can not connect via SSH/telnet, as you will lose connection once your management interface changes its name. Configure the cluster with the following (note this is in management mode, and not configuration mode – so you will not see these commands in the configuration).
On J4350-A:
root@J4350-A> set chassis cluster cluster-id 1 node 0
On J4350-B:
root@J4350-B> set chassis cluster cluster-id 1 node 1 reboot
Once node 1 has rebooted and come up fully, reboot node 0. The Juniper documentation has the “reboot” switch on both commands, but in practice it was found that there were issues if it was done that way.
Create Groups
This section creates “groups”, which defines the hostnames and IP addresses of the individual nodes. This section does not get replicated between the nodes. Also configured is the “apply-groups” command, which dictates which hosts will have configuration copied to them.
set groups node0 system hostname J4350-A
set groups node0 interfaces fxp0 unit 0 family inet address 192.168.3.110/24
set groups node0 system hostname J4350-B
set groups node0 interfaces fxp0 unit 0 family inet address 192.168.3.111/24
set apply-groups ${node}
Cluster Configuration
Configure the members of the cluster, and assign them priorities. Redundancy-group 0 is used for the RE. The reth-count command dictates how many redundant Ethernet interfaces (aka VIPs) will be on the router.
set chassis cluster reth-count 2 set chassis cluster heartbeat-threshold 3 set chassis cluster node 0 set chassis cluster node 1 set chassis cluster redundancy-group 0 node 0 priority 100 set chassis cluster redundancy-group 0 node 1 priority 1
Physical Interface Configuration and Tracking
Configure the physical interfaces. Redundancy-group 1 is used for the forwarding plane. Enable node0 to pre-empt.
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 chassis cluster redundancy-group 1 interface-monitor ge-1/0/0 weight 255 set chassis cluster redundancy-group 1 interface-monitor ge-1/0/1 weight 255 set chassis cluster redundancy-group 1 interface-monitor ge-8/0/0 weight 255 set chassis cluster redundancy-group 1 interface-monitor ge-8/0/1 weight 255
Control Plane Configuration and Tracking
(Optional) If both data processing and control plane functions should failover together, use the following commands. Otherwise, skip to the next section.
set chassis cluster redundancy-group 0 interface-monitor ge-1/0/0 weight 255 set chassis cluster redundancy-group 0 interface-monitor ge-1/0/1 weight 255 set chassis cluster redundancy-group 0 interface-monitor ge-8/0/0 weight 255 set chassis cluster redundancy-group 0 interface-monitor ge-8/0/1 weight 255
Logical Interface Configuration
Logical interfaces are created as “reth” interfaces. IP addresses are added, and they are put in redundancy-group 1.
set interfaces ge-1/0/0 gigether-options redundant-parent reth0 set interfaces ge-8/0/0 gigether-options redundant-parent reth0 set interfaces ge-1/0/1 gigether-options redundant-parent reth1 set interfaces ge-8/0/1 gigether-options redundant-parent reth1 set interfaces reth0 redundant-ether-options redundancy-group 1 set interfaces reth0 unit 0 family inet address 10.0.0.1/30 set interfaces reth1 redundant-ether-options redundancy-group 1 set interfaces reth1 unit 0 family inet address 10.0.0.5/30
Add reth interfaces to a security zone
Like regular interfaces, logical reth interfaces must be added to a security zone.
set security zones security-zone Untrust interfaces reth0.0 set security zones security-zone Trust interfaces reth1.0
Leave a Reply