0% found this document useful (0 votes)
187 views

Cluster Configuration Procedure

The document provides instructions for configuring a cluster on a Juniper SRX5600 device. It involves 4 main steps: 1) licensing both nodes, 2) activating cluster mode and setting the cluster ID, 3) defining fabric links between the nodes, and 4) configuring redundant Ethernet interfaces (RETH) between the nodes. The process is completed by setting monitoring interfaces and applying the configuration groups.

Uploaded by

giotto4528
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
187 views

Cluster Configuration Procedure

The document provides instructions for configuring a cluster on a Juniper SRX5600 device. It involves 4 main steps: 1) licensing both nodes, 2) activating cluster mode and setting the cluster ID, 3) defining fabric links between the nodes, and 4) configuring redundant Ethernet interfaces (RETH) between the nodes. The process is completed by setting monitoring interfaces and applying the configuration groups.

Uploaded by

giotto4528
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Cluster configuration

Device: Juniper SRX5600 Operative system: JunOS 12.1R3.5

Abstract:
This is a step-by-step procedure to come up a SRX 5600 cluster. Hardware Description
node0: -------------------------------------------------------------------------Hardware inventory: Item Version Part number Serial number Description Chassis XXXXXXXXXXXX SRX 5600 Midplane REV 01 710-024804 XXXXXXXX SRX 5600 Midplane FPM Board REV 01 710-024631 XXXXXX Front Panel Display PEM 0 Rev 03 740-023485 XXXXXXXXXXX PS 1.2-1.7kW; 100-240V AC in PEM 1 Rev 03 740-023485 XXXXXXXXXXX PS 1.2-1.7kW; 100-240V AC in PEM 2 Rev 03 740-023485 XXXXXXXXXXX PS 1.2-1.7kW; 100-240V AC in PEM 3 Rev 03 740-023485 XXXXXXXXXXX PS 1.2-1.7kW; 100-240V AC in Routing Engine 0 REV 06 740-023530 XXXXXXXXXXX SRX5k RE-13-20 CB 0 REV 05 710-024802 XXXXXX SRX5k SCB FPC 4 REV 17 750-027945 XXXXXXXX SRX5k FIOC CPU REV 04 710-024633 XXXXXXXX SRX5k DPC PMB PIC 0 REV 09 750-027491 XXXXXX 16x 1GE TX PIC 1 REV 07 750-021378 XXXXXX 4x 10GE XFP Xcvr 0 NON-JNPR XXXXXXXXX XFP-10G-SR Xcvr 1 NON-JNPR XXXXXXXXX XFP-10G-SR Xcvr 2 NON-JNPR XXXXXXXXX XFP-10G-SR Xcvr 3 NON-JNPR XXXXXXXXX XFP-10G-SR FPC 5 REV 18 750-023996 XXXXXXXX SRX5k SPC CPU REV 04 710-024633 XXXXXXXX SRX5k DPC PMB PIC 0 BUILTIN BUILTIN SPU Cp-Flow PIC 1 BUILTIN BUILTIN SPU Flow Fan Tray Left Fan Tray node1: -------------------------------------------------------------------------Hardware inventory: Item Version Part number Serial number Description Chassis XXXXXXXXXXXX SRX 5600 Midplane REV 01 710-024804 XXXXXXXX SRX 5600 Midplane FPM Board REV 01 710-024631 XXXXXX Front Panel Display PEM 0 Rev 03 740-023485 XXXXXXXXXXX PS 1.2-1.7kW; 100-240V AC in PEM 1 Rev 03 740-023485 XXXXXXXXXXX PS 1.2-1.7kW; 100-240V AC in PEM 2 Rev 03 740-023485 XXXXXXXXXXX PS 1.2-1.7kW; 100-240V AC in

PEM 3 Rev 03 AC in Routing Engine 0 REV 06 CB 0 REV 05 FPC 4 REV 09 CPU REV 03 PIC 0 REV 07 PIC 1 REV 11 Xcvr 0 Xcvr 1 Xcvr 2 Xcvr 3 FPC 5 REV 18 CPU REV 04 PIC 0 PIC 1 Fan Tray

740-023485 740-023530 710-024802 750-027945 710-024633 750-027491 750-021378 NON-JNPR NON-JNPR NON-JNPR NON-JNPR 750-023996 710-024633 BUILTIN BUILTIN

XXXXXXXXXXX XXXXXXXXXXX XXXXXXX XXXXXXX XXXXXXX XXXXXXX XXXXXXX XXXXXXX XXXXXXX XXXXXXX XXXXXXX XXXXXXX XXXXXXX BUILTIN BUILTIN

PS 1.2-1.7kW; 100-240V SRX5k RE-13-20 SRX5k SCB SRX5k FIOC SRX5k DPC PMB 16x 1GE TX 4x 10GE XFP XFP-10G-SR XFP-10G-SR XFP-10G-SR XFP-10G-SR SRX5k SPC SRX5k DPC PMB SPU Cp-Flow SPU Flow Left Fan Tray

Procedure
# # # # # Cluster in SRX5600 requires four steps: - License the node - Cluster activation in both nodes - Definition of fabric links ( - interface rethx configuration

# Execute this process in master node and later in secondary node. # You must guarantee that NTP is all the time available to come up with the cluster # licensing already done. # in operational mode user@host> set chassis cluster cluster-id 1 node 0 reboot # after reboot in configuration mode # configure management interfaces from the console port # node 0 - primary set groups node0 system host-name node0-router set groups node0 interfaces fxp0 unit 0 family inet address 192.168.2.21/26 set groups node0 system host-name SRX5800-1 set chassis cluster reth-count 3 set chassis cluster control-ports fpc 5 port 0 set interfaces fab0 fabric-options member-interfaces xe-4/1/0 # in operational mode user@host> set chassis cluster cluster-id 1 node 1 reboot # after reboot in configuration mode # node 1 - secondary set groups node1 system host-name node1-router set groups node1 interfaces fxp0 unit 0 family inet address 192.168.2.22/26 set groups node1 system host-name SRX5800-2 set chassis cluster reth-count 3

set chassis cluster control-ports fpc 11 port 0 set interfaces fab1 fabric-options member-interfaces xe-10/1/0 set set set set set set chassis chassis chassis chassis chassis chassis cluster cluster cluster cluster cluster cluster redundancy-group redundancy-group redundancy-group redundancy-group redundancy-group redundancy-group 0 0 1 1 1 1 node 0 priority 100 node 1 priority 1 node 0 priority 100 node 1 priority 1 preempt gratuitous-arp-count 4

set chassis weight 255 set chassis weight 255 set chassis weight 255 set chassis weight 255

cluster redundancy-group 1 interface-monitor xe-4/1/2 cluster redundancy-group 1 interface-monitor xe-4/1/3 cluster redundancy-group 1 interface-monitor xe-10/1/2 cluster redundancy-group 1 interface-monitor xe-10/1/3

{primary:node0}[edit] admin# set apply-groups node0 {primary:node0}[edit] admin# set apply-groups node1

# - reth interfaces # reth0 - Internal interface set interfaces xe-4/1/2 gigether-options redundant-parent reth0 set interfaces xe-10/1/2 gigether-options redundant-parent reth0 # reth1 - External interface set interfaces xe-4/1/3 gigether-options redundant-parent reth1 set interfaces xe-10/1/3 gigether-options redundant-parent reth1 verification command show chassis cluster ? Possible completions: interfaces Display chassis-cluster interfaces statistics Display chassis-cluster traffic statistics status Display chassis-cluster status

You might also like