close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Overview
- Junos Space User Interface Overview
- Junos Space Home Page Overview
play_arrow Devices
- play_arrow Device Management
- play_arrow Systems of Record
  - Systems of Record in Junos Space Overview
  - Understanding How Junos Space Automatically Resynchronizes Managed Devices
- play_arrow Device Discovery Profiles
- play_arrow Modeling Devices
- play_arrow Device Authentication in Junos Space
- play_arrow Viewing Device Inventory
- play_arrow Exporting Device Inventory
- play_arrow Configuring Juniper Networks Devices
- play_arrow Device Adapter
- play_arrow Device Configuration Management
- play_arrow Adding and Managing Non Juniper Networks Devices
  - Adding Unmanaged Devices
  - Modifying Unmanaged Device Configuration
- play_arrow Accessing Devices
- play_arrow Logical Systems (LSYS)
- play_arrow Tenant System (TSYS)
- play_arrow Device Partitions
- play_arrow Custom Labels
- play_arrow Verifying Template, Image Deployment, Script Execution, and Staged Images on Devices
- play_arrow Device Monitoring
  - Viewing Alarms from a Managed Device
  - Viewing the Performance Graphs of a Managed Device
- play_arrow Device Maintenance
play_arrow Device Templates
- play_arrow Overview
  - Device Templates Overview
- play_arrow Template Definitions
- play_arrow Configuring Devices using Device Templates
- play_arrow Configuring Devices using Quick Templates
- play_arrow Device Template Administration
play_arrow CLI Configlets
- play_arrow Overview
- play_arrow CLI Configlets
- play_arrow Configuration Views
- play_arrow XPath and Regular Expressions
- play_arrow Configuration Filters
play_arrow Images and Scripts
play_arrow Reports
- play_arrow Reports Overview
  - Reports Overview
- play_arrow Report Definitions
- play_arrow Reports
play_arrow Network Monitoring
- play_arrow Overview
  - Network Monitoring Workspace Overview
  - Working with the Network Monitoring Home Page
- play_arrow Managing Nodes
- play_arrow Searching for Nodes and Assets
  - Searching for Nodes or Nodes with Asset Information
  - Working with Node Assets
- play_arrow Managing Outages
  - Viewing and Tracking Outages
  - Configuring Scheduled Outages
- play_arrow Using the Network Monitoring Dashboard
  - Viewing the Network Monitoring Dashboard
- play_arrow Managing and Configuring Events
- play_arrow Managing and Configuring Alarms
- play_arrow Managing and Configuring Notifications
  - Viewing, Configuring, and Searching for Notifications
  - Configuring Event Notifications, Path Outages, and Destination Paths
- play_arrow Managing Reports and Charts
- play_arrow Network Monitoring Topology
- play_arrow Network Monitoring Administration
play_arrow Configuration Files
- play_arrow Overview
  - Managing Configuration Files Overview
  - Viewing Configuration File Statistics
- play_arrow Managing Configuration Files
play_arrow Jobs
- play_arrow Overview
  - Jobs Overview
- play_arrow Managing Jobs
play_arrow Role-Based Access Control
- play_arrow Overview
  - Role-Based Access Control Overview
- play_arrow Roles
- play_arrow User Accounts
- play_arrow User Groups
- play_arrow Domains
- play_arrow Remote Profiles
- play_arrow API Access Profiles
- play_arrow User Sessions
play_arrow Audit Logs
- play_arrow Overview
  - Junos Space Audit Logs Overview
- play_arrow Managing Audit Logs
play_arrow Administration

list Table of Contents

English

Configuring SRX Device Clusters in Junos Space using Secure Console

date_range 21-Jun-21

arrow_backward

arrow_forward

You can create a cluster of two SRX-series devices that are combined to act as a single system, or create a single-device cluster and then add a second device to the cluster later. You can also configure a standalone device from an existing cluster device. You can do this using the Secure Console feature in the Devices workspace.

You can configure an SRX-series cluster in the following modes:

Active/passive clustering
Active/active clustering

In the active/passive mode, the transit traffic passes through the primary node, while the backup node is used only in the event of a failure. When failure occurs, the backup device becomes the primary and takes over all the forwarding tasks.

In the active/active mode, the transit traffic always passes through both the nodes of the cluster.

Note:

To discover and manage an SRX device cluster that is already configured, you must perform the device discovery workflow independently for each cluster node. You can add and discover the cluster devices using the Web UI. The discovery process is common for both standalone devices and cluster devices. For more information, see Running Device Discovery Profiles.

This topic includes the following tasks:

Configuring a Standalone Device from a Single-node Cluster

You can configure a standalone device from device that is currently configured as a single-node cluster.

To configure a single-node cluster as a standalone device:

On the Junos Space Network Management Platform user interface, select Devices > Device Management.
Select the single-node cluster and select Device Access > SSH to Device from the Actions menu.
The SSH to Device pop-up window is displayed.

Note:
If you have cleared the Allow users to auto log in to devices using SSH option on the Modify Applications page, the SSH to Device pop-up window is displayed. The IP address is automatically displayed in the IP address field. Enter the username and password in the User name and Password fields respectively.
In the IP Address field, enter a valid IP address for the device.
In the Username field, enter the user name for the device.
In the Password field, enter the password to access the device.
The name and password must match the name and password configured on the device.
In the Port field, enter the port number to use for the SSH connection.
The default value is 22. If you want to change the value, specify a value specified in the SSH port for device connection field on the Modify Application Settings page in the Administration workspace.
Click Connect.
The SSH terminal window is displayed.

Note:
You may receive error messages such as “Unable to Connect”, “Authentication Error”, or “Connection Lost or Terminated”, which are displayed as standard text in terminal window. If you receive an error message, all other functionality in the terminal window is stopped. You should close this terminal window and open a new SSH session.
Enter the set chassis command to remove the cluster configuration:
```
set chassis cluster cluster-id 0 node 0
```
Reboot the device, by entering the command:
```
request system reboot
```

Copy the outbound-ssh configuration from group node to system level, for example:

content_copy zoom_out_map
set system services outbound-ssh client 00089BBC494A device-id 6CFF68

content_copy zoom_out_map
 set system services outbound-ssh client 00089BBC494A secret "$ABC123"

content_copy zoom_out_map
set system services outbound-ssh client 00089BBC494A services netconf

content_copy zoom_out_map
set system services outbound-ssh client 00089BBC494A 10.155.70.252 port 7804 

Copy the system log configuration from group node to system level:
```
set system syslog file default-log-messages any any
```
```
set system syslog file default-log-messages structured-data
```
Copy the fxp0 interface setting from group node to system level, for example:
```
set  interfaces fxp0 unit 0 family inet address 10.155.70.223/19
```
Delete the outbound-ssh configuration from the group node, for example:
```
delete groups node0 system services outbound-ssh
```

Delete the system log configuration from the group node, for example:

content_copy zoom_out_map
delete groups node0 system syslog file default-log-messages any any

content_copy zoom_out_map
delete groups node0 system syslog file default-log-messages structured-data

Delete the interfaces configuration from the group node, for example:
```
delete groups node0 interfaces fxp0 unit 0 family inet address 10.155.70.223/19
```
Commit the configuration changes on the device:
```
commit
```
In the Junos Space user interface, the device connection status will go down and then up again. After the device connection is back up, you can verify that the device you configured displays as a standalone device.
To terminate the SSH session, type exit from the terminal window prompt, and press Enter.
Click in the top right corner of the terminal window to close the window.

Configuring a Standalone Device from a Two-Node Cluster

You can configure a standalone device from the secondary peer device in a cluster.

Note:

You cannot use the primary peer in a two-node cluster to configure a standalone device.

To configure a secondary peer device in a cluster as a standalone device:

On the Junos Space Network Management Platform user interface, select Devices > Device Management.
Select the secondary peer device and select Device Access > SSH to Device from the Actions menu.
The SSH to Device pop-up window is displayed.
Select the single-node cluster and select Device Access > SSH to Device from the Actions menu.
The SSH to Device pop-up window is displayed.

Note:
If you have cleared the Allow users to auto log in to devices using SSH option on the Modify Applications page, the SSH to Device pop-up window is displayed. The IP address is automatically displayed in the IP address field. Enter the username and password in the User name and Password fields respectively.
In the IP Address field, enter a valid IP address for the device.
In the Username field, enter the user name for the device.
In the Password field, enter the password to access the device.
The name and password must match the name and password configured on the device.
In the Port field, enter the port number to use for the SSH connection.
The default value is 22. If you want to change the value, specify a value specified in the SSH port for device connection field on the Modify Application Settings page in the Administration workspace.
Click Connect.
The SSH terminal window is displayed.

Note:
You may receive error messages such as “Unable to Connect”, “Authentication Error”, or “Connection Lost or Terminated”, which are displayed as standard text in terminal window. If you receive an error message, all other functionality in the terminal window is stopped. You should close this terminal window and open a new SSH session.
Disconnect the HA cable from the device that you want to configure as a standalone device.
Enter the set chassis command for the peer device, for example:
```
set chassis cluster cluster-id 0 node 1
```
Reboot the device, by entering the command:
```
request system reboot
```

Copy the outbound-ssh configuration from group level to system level, for example:

content_copy zoom_out_map
set system services outbound-ssh client 00089BBC494A device-id 6CFF68

content_copy zoom_out_map
 set system services outbound-ssh client 00089BBC494A secret "$ABC123"

content_copy zoom_out_map
set system services outbound-ssh client 00089BBC494A services netconf

content_copy zoom_out_map
set system services outbound-ssh client 00089BBC494A 10.155.70.252 port 7804 

Copy the system log configuration from group level to system level:
```
set system syslog file default-log-messages any any
```
```
set system syslog file default-log-messages structured-data
```
Copy the fxp0 interface setting from group level to system level, for example:
```
set interfaces fxp0 unit 0 family inet address 10.155.70.223/19
```
Delete the outbound-ssh configuration from the group level, for example:
```
delete groups node1 system services outbound-ssh
```

Delete the system log configuration from the group level, for example:

content_copy zoom_out_map
delete groups node1 system syslog file default-log-messages any any
delete groups node1 system syslog file default-log-messages structured-data

Delete the interfaces configuration from the group level, for example:
```
delete groups node1 interfaces fxp0 unit 0 family inet address 10.155.70.223/19
```
Commit the configuration changes on the device:
```
commit
```
In the Junos Space user interface, the device connection status will go down and then up again. After the device connection is back up, you can verify that the device you configured displays as a standalone device.

After the device connections are up, verify the following changes in the Manage Devices inventory landing page:
- The device you configured now displays as a standalone device.
- The cluster that formerly included a primary and secondary peer device now displays the primary peer device only.
To terminate the SSH session, type exit from the terminal window prompt, and press Enter.
Click in the top right corner of the terminal window to close the window.

Configuring a Primary Peer in a Cluster from a Standalone Device

You can create a device cluster from two standalone devices. Use the following procedure to configure a standalone device as the primary peer in a cluster.

To configure a primary peer in a cluster from a standalone device:

On the Junos Space Network Management Platform user interface, select Devices > Device Management.
Select the primary peer in the cluster and select Device Access > SSH to Device from the Actions menu.
The SSH to Device pop-up window is displayed.

Note:
If you have cleared the Allow users to auto log in to devices using SSH option on the Modify Applications page, the SSH to Device pop-up window is displayed. The IP address is automatically displayed in the IP address field. Enter the username and password in the User name and Password fields respectively.
In the IP Address field, enter a valid IP address for the device.
In the Username field, enter the user name for the device.
In the Password field, enter the password to access the device.
The name and password must match the name and password configured on the device.
In the Port field, enter the port number to use for the SSH connection.
The default value is 22. If you want to change the value, specify a value specified in the SSH port for device connection field on the Modify Application Settings page in the Administration workspace.
Click Connect.
The SSH terminal window is displayed.

Note:
You may receive error messages such as “Unable to Connect”, “Authentication Error”, or “Connection Lost or Terminated”, which are displayed as standard text in terminal window. If you receive an error message, all other functionality in the terminal window is stopped. You should close this terminal window and open a new SSH session.
For the standalone device, enter the command:
```
set chassis cluster cluster-id 1 node 0
```
Reboot the device, by entering the command:
```
request system reboot
```

Copy the outbound-ssh configuration from the system level to the group level, for example:

content_copy zoom_out_map
set groups node0 system services outbound-ssh client 00089BBC494A device-id 6CFF68 

content_copy zoom_out_map
set groups node0 system services outbound-ssh client 00089BBC494A secret "$ABC123" 

content_copy zoom_out_map
set groups node0 system services outbound-ssh client 00089BBC494A services netconf 

content_copy zoom_out_map
set groups node0 system services outbound-ssh client 00089BBC494A 10.155.70.252 port 7804 

Copy the fxp0 interface configuration from the system level to the group level, for example:
```
set groups node0 interfaces fxp0 unit 0 family inet address 10.155.70.223/19
```

Copy the system log configuration from system level to group level:

content_copy zoom_out_map
set groups node0 system syslog file default-log-messages any any

content_copy zoom_out_map
set groups node0 system syslog file default-log-messages structured-data

Delete the outbound-ssh configuration from the system level, for example:
```
delete system services outbound-ssh
```
Delete the system log configuration from the system level, for example:
```
delete system syslog file default-log-messages any any
```
```
delete system syslog file default-log-messages structured-data
```
Delete the interfaces configuration from the system level, for example:
```
delete interfaces fxp0 unit 0 family inet address 10.155.70.223/19
```
Commit the configuration changes on the device again:
```
commit
```
After the device connection is up, verify the following changes:
- In the Manage Devices inventory landing page:
  - The cluster icon appears for the device.
  - The new cluster device appears as the primary device.
- In the physical inventory landing page, Junos Space Network Management Platform displays chassis information for the primary device cluster.
To terminate the SSH session, type exit from the terminal window prompt, and press Enter.
Click in the top right corner of the terminal window to close the window.

Configuring a Secondary Peer in a Cluster from a Standalone Device

If a device cluster contains only a primary peer, you can configure a standalone device to function as a secondary peer in the cluster. Use the following procedure to ensure that Junos Space Network Management Platform is able to manage both devices.

To add a standalone device to a cluster:

On the Junos Space Network Management Platform user interface, select Devices > Device Management.
Select the device and select Device Access > SSH to Device from the Actions menu.
The SSH to Device pop-up window is displayed.

Note:
If you have cleared the Allow users to auto log in to devices using SSH option on the Modify Applications page, the SSH to Device pop-up window is displayed. The IP address is automatically displayed in the IP address field. Enter the username and password in the User name and Password fields respectively.
In the IP Address field, enter a valid IP address for the device.
In the Username field, enter the user name for the device.
In the Password field, enter the password to access the device.
The name and password must match the name and password configured on the device.
In the Port field, enter the port number to use for the SSH connection.
The default value is 22. If you want to change the value, specify a value specified in the SSH port for device connection field on the Modify Application Settings page in the Administration workspace.
Click Connect.
The SSH terminal window is displayed.

From the terminal window prompt, you can enter CLI commands to create a standalone device from the device cluster.

Note:
You may receive error messages such as “Unable to Connect”, “Authentication Error”, or “Connection Lost or Terminated”, which are displayed as standard text in terminal window. If you receive an error message, all other functionality in the terminal window is stopped. You should close this terminal window and open a new SSH session.
For the standalone device, enter the command:
```
set chassis cluster cluster-id 1 node 1
```
Enter the command:
```
request system reboot
```

Copy the outbound-ssh configuration from the system level to the group level, for example:

content_copy zoom_out_map
set groups node1 system services outbound-ssh client 00089BBC494A device-id 6CFF68 

content_copy zoom_out_map
set groups node1 system services outbound-ssh client 00089BBC494A secret "$ABC123" 

content_copy zoom_out_map
set groups node1 system services outbound-ssh client 00089BBC494A services netconf 

content_copy zoom_out_map
set groups node1 system services outbound-ssh client 00089BBC494A 10.155.70.252 port 7804 

Copy the fxp0 interface configuration from the system level to the group level, for example:
```
set groups node1 interfaces fxp0 unit 0 family inet address 10.155.70.223/19
```

Copy the system log configuration from system level to group level:

content_copy zoom_out_map
set groups node1 system syslog file default-log-messages any any

content_copy zoom_out_map
set groups node1 system syslog file default-log-messages structured-data

Delete the outbound-ssh configuration from the system level, for example:
```
delete system services outbound-ssh
```
Delete the system log configuration from the system level, for example:
```
delete system syslog file default-log-messages any any
```
```
delete system syslog file default-log-messages structured-data
```
Delete the interfaces configuration from the system level, for example:
```
delete interfaces fxp0 unit 0 family inet address 10.155.70.223/19
```
Commit the configuration changes on the device again:
```
commit
```
Connect the HA cable to each device in the cluster.
Establish an SSH connection to the primary device in the cluster.
On the primary device, make some trivial change to the device, for example, add a description, and commit the change:
```
commit
```
After the device connections are up for both devices in the cluster, verify the following changes:
- In the Manage Devices inventory landing page:
  - Each peer device displays the other cluster member.
  - The cluster icon appears for each member device.
  - One device appears as the primary device and the other as the secondary device in the cluster.
- In the physical inventory landing page, chassis information appears for each peer device in the cluster.
To terminate the SSH sessions, type exit from the terminal window prompt, and press Enter.
Click in the top right corner of the terminal window to close the window.

Configuring a Cluster with Loopback Interface

By default, the SRX devices are configured to be managed through the fxp0 Ethernet management interface.

If the device is managed through non-fxp0 interface (loopback address), add the following additional command to the device so that the SRX device is considered as a cluster in Junos Space:

Command: set chassis cluster network-management cluster-primary

Note:

All other cluster configuration commands remain the same for both the Active/Active mode, and Active/Passive mode.

arrow_backward PREVIOUS Connecting to a Device by Using Secure Console

NEXT arrow_forward Understanding Logical Systems for SRX Series Services Gateways

Workspaces User Guide

ON THIS PAGE

Configuring SRX Device Clusters in Junos Space using Secure Console

Configuring a Standalone Device from a Single-node Cluster

Configuring a Standalone Device from a Two-Node Cluster

Configuring a Primary Peer in a Cluster from a Standalone Device

Configuring a Secondary Peer in a Cluster from a Standalone Device

Configuring a Cluster with Loopback Interface

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Workspaces User Guide

ON THIS PAGE

Configuring SRX Device Clusters in Junos Space using Secure Console

Configuring a Standalone Device from a Single-node Cluster

Configuring a Standalone Device from a Two-Node Cluster

Configuring a Primary Peer in a Cluster from a Standalone Device

Configuring a Secondary Peer in a Cluster from a Standalone Device

Configuring a Cluster with Loopback Interface

Related Documentation

Stay in touch