Add Devices
Overview
You can add devices to Juniper Security Director Cloud in the following ways:
-
Using Commands - Juniper Security Director Cloud generates commands for adding an individual device, device cluster, or MNHA pair devices. When you copy-paste and commit the commands into the device console, the device, device cluster, or MNHA pair devices are added to the cloud. See Add Standalone Devices, Device Clusters, or MNHA Pair Devices Using Commands. For the list of supported SRX Series firewalls on which MNHA is supported, see the High Availability User Guide.
Note:Juniper Security Director Cloud supports MNHA pair devices running Junos OS Release 22.4R1 or later.
-
Zero Touch Provisioning - You can configure and provision devices automatically without any manual intervention. See Add Devices Using Zero Touch Provisioning.
-
Using J-Web - See Add an SRX Series Firewall to Juniper Security Director Cloud in the J-Web User Guide for SRX Series Firewalls for details.
-
From Security Director - See Add Devices to Security Director Cloud in the Security Director User Guide for details.
-
By scanning QR code - Onboard cloud-ready SRX firewalls by scanning the device QR code. See Add Device by Scanning QR Code.
Before You Begin
-
Ensure that each SRX Series Firewall port can communicate with a Juniper Security Director Cloud FQDN. The FQDN of each region is different.
Table 1: Region to FQDN Mapping Region Purpose Port FQDN North Virginia, US
ZTP
443
jsec2-virginia.juniperclouds.net
Outbound SSH
7804
srx.sdcloud.juniperclouds.net
Syslog TLS
6514
srx.sdcloud.juniperclouds.net
Ohio, US
ZTP
443
jsec2-ohio.juniperclouds.net
Outbound SSH
7804
srx.jsec2-ohio.juniperclouds.net
Syslog TLS
6514
srx.jsec2-ohio.juniperclouds.net
Montreal, Canada
ZTP
443
jsec-montreal2.juniperclouds.net
Outbound SSH
7804
srx.jsec-montreal2.juniperclouds.net
Syslog TLS
6514
srx.jsec-montreal2.juniperclouds.net
Frankfurt, Germany
ZTP
443
jsec-frankfurt.juniperclouds.net
Outbound SSH
7804
srx.jsec-frankfurt.juniperclouds.net
Syslog TLS
6514
srx.jsec-frankfurt.juniperclouds.net
-
Use TCP port 53 and UDP port 53 to connect to Google DNS servers (IP addresses—8.8.8.8 and 8.8.4.4). The Google DNS servers are specified as the default servers in the factory settings of the SRX Series Firewalls. You must use these default DNS servers when you use ZTP to onboard the firewalls. You can use private DNS servers when you use other methods to onboard the firewalls. Note that you must make sure that the private DNS servers can resolve the Juniper Security Director Cloud FQDNs.
-
To discover and manage the device from Juniper Security Director Cloud, ensure that the netconf and ssh rate limit is set to 32 or higher on the device. For more information, see Junos CLI Reference.
Add Standalone Devices, Device Clusters, or MNHA Pair Devices Using Commands
Juniper Security Director Cloud generates commands for adding a standalone device, a device cluster, or a multinode high availability (MNHA) pair devices. You can copy and paste the commands into the device console. When you commit the commands to the device, Juniper Security Director Cloud discovers and adds the device to the cloud. For more information about MNHA, see the High Availability User Guide.
After discovery is complete, the status in the Management Status column changes to Up. If the discovery fails, Discovery failed status is displayed. Hover over the Discovery failed status to see the reason for the failure.
-
If the job fails for an MNHA pair, the deployment mode is not displayed beside the MNHA pair name. You can delete and add the MNHA pair again or initiate the discovery process again.
-
If security certificate installation job failed on a device in the MNHA pair, retry the job from the Jobs page and then reinitiate security logs configuration for the device from the Devices page.
Add Devices Using Zero Touch Provisioning
You can configure and provision devices automatically using Zero Touch Provisioning (ZTP). ZTP reduces the manual intervention for adding devices to a network. To ensure valid devices are onboarded through ZTP, you can configure Juniper Security Director Cloud to prompt you to approve or reject onboarding requests.
ZTP Supported Device | Supported Junos OS Release |
---|---|
SRX300, SRX320, SRX340, and SRX345 firewalls |
Junos OS Release 18.4R3 and later |
SRX380 |
Junos OS Release 20.1R1 and later |
SRX1500 |
Junos OS Release 20.2R1 and later |
SRX1600, SRX2300 |
Junos OS Release 23.4R1 and later |
SRX4300 |
Junos OS Release 24.1R1 and later |
To add other devices models, configure the basic device settings and connectivity, and add the device using Add Standalone Devices, Device Clusters, or MNHA Pair Devices Using Commands.
The devices are added and displayed on the Devices page and the device discovery process is initiated.
If Juniper Security Director Cloud is configured to prompt you to approve or reject onboarding requests for devices through ZTP, a link to approve or reject the request is displayed in the Management Status column. See Approve or Reject Onboarding Requests for ZTP Devices.
Add Device by Scanning QR Code
You can add cloud-ready SRX Series Firewalls to Juniper Security Director Cloud by scanning the QR code available on the firewall. Your SRX Series Firewall is cloud-ready if it has a QR claim code on the front or the back panel.
-
The firewall is powered on.
-
The firewall is not already added in an organization. You can add a firewall in only one organization.
Approve or Reject Onboarding Requests for ZTP Devices
The Approve/reject device onboarding requests toggle button on the Organization page must be enabled to receive onboarding requests.
Zero Touch Provisioning (ZTP) reduces the manual intervention for adding devices to a network. However, to ensure valid devices are onboarded through ZTP, you can configure Juniper Security Director Cloud to prompt you to approve or reject onboarding requests for devices.
When you enter an incorrect serial number, an onboarding request is not generated. It ensures that only devices with valid serial numbers are added in Juniper Security Director Cloud.