set paragon cluster applications
Syntax
set paragon cluster applications active-assurance test-agent-gateway-vip v4address
set paragon cluster applications active-assurance test-agent-gateway-vip-ipv6 v6address
set paragon cluster applications active-assurance test-agent-gateway-hostname hostname
set paragon cluster applications aiops enable-device-health (true|false)
set paragon cluster applications aiops install-aiml (true|false)
set paragon cluster applications gnmi-term gnmi-term-host v4address-or-hostname
set paragon cluster applications gnmi-term gnmi-term-host-ipv6 v6address-or-hostname
set paragon cluster applications oc-term oc-term-host v4address-or-hostname
set paragon cluster applications oc-term oc-term-host-ipv6 v6address-or-hostname
set paragon cluster applications pathfinder pce-server pce-server-vip pce-server-vip
set paragon cluster applications pathfinder pce-server pce-server-global-default-tls-mode (auto-detect|strict-enable|strict-disable)
set paragon cluster applications pathfinder pce-server pce-server-user-certificate pce-server-use-custom-certificate (true|false)
set paragon cluster applications pathfinder pce-server pce-server-user-certificate pce-server-custom-certificate-filename cert-filename
set paragon cluster applications pathfinder pce-server pce-server-usercertificate pce-server-custom-certificate-key-filename privatekey-filename
set paragon cluster applications routingbot install-routingbot (true|false)
set paragon cluster applications routingbot routingbot-crpd-vip v4-address
set paragon cluster applications web-ui web-admin-password password
set paragon cluster applications web-ui web-admin-user user_e-mail_id
Hierarchy Level
[edit]
Description
Configure the following application parameters:
-
Paragon Active Assurance Test Agent gateway virtual IP (VIP) address and hostname
-
Default Web administrator login credentials. The Web administrator is the first user to log in to the Routing Director GUI and has super user privileges.
-
PCE server VIP address used to set up Path Computational Element Protocol (PCEP) sessions between Routing Director and the devices.
-
Routing observability use case and VIP address.
-
Enable AI/ML (artificial intelligence [AI] and machine learning [ML]) techniques to automatically monitor Key Performance Indicators (KPIs) related to a device's health.
-
Separate IP addresses for gNMI and NETCONF. If not configured, gNMI uses the generic ingress VIP address which is shared between Web GUI, gNMI, and NETCONF.
If you configure application parameters post cluster installation, you must
update the configuration files using the request paragon config
command and redeploy the cluster using the request paragon deploy
cluster command for the configuration to take effect.
Options
| active-assurance test-agent-gateway-vip v4address |
Configure the IPv4 VIP address for the Paragon Active Assurance Test Agent gateway. |
| active-assurance test-agent-gateway-vip-ipv6 v6address |
Configure the IPv6 VIP address for the Paragon Active Assurance Test Agent gateway. |
|
active-assurance test-agent-gateway-hostname hostname |
Configure the hostname for the Paragon Active Assurance Test Agent gateway. |
|
aiops enable-device-health (true | false) |
Configure monitoring of device-health. |
|
aiops install-aiml (true | false) |
Enable or disable AI/ML and related features. This feature is disabled by default. |
|
gnmi-term gnmi-term-host v4address-or-hostname |
Configure a separate VIP address or hostname for gNMI. If not configured, gNMI uses the generic ingress VIP address which is shared between Web GUI, gNMI, and NETCONF. |
|
gnmi-term gnmi-term-host-ipv6 v6address-or-hostname |
Configure a separate virtual IPv6 address or hostname for gNMI. |
|
oc-term oc-term-host v4address-or-hostname |
Configure a separate VIP address or hostname for NETCONF. If not configured, NETCONF uses the generic ingress VIP address which is shared between Web GUI, gNMI, and NETCONF. |
|
oc-term oc-term-host-ipv6 v6address-or-hostname |
Configure a separate virtual IPv6 address or hostname for NETCONF. |
|
pathfinder pce-server pce-server-vip pce-server-vip |
Configure the PCE Server VIP address. If you configure the PCE server VIP address post cluster
installation, use the |
|
pathfinder pce-server pce-server-global-default-tls-mode (auto-detect | strict-enable | strict-disable) |
Enable security between the PCE server and Path Computation Clients (PCC). Options include:
|
|
pathfinder pce-server pce-server-user-certificate pce-server-use-custom-certificate (true | false) |
Enable usage of custom certificates to validate secure PCEP connections between the device and Routing Director. |
|
pathfinder pce-server pce-server-user-certificate pce-server-custom-certificate-filename cert-filename |
Configure the custom certificate file used to validate secure PCEP connections between the device and Routing Director. |
|
pathfinder pce-server pce-server-user-certificate pce-server-custom-certificate-key-filename privatekey-filename |
Configure the custom certificate key used to validate secure PCEP connections between the device and Routing Director. |
|
routingbot install-routingbot (true | false) |
Enable or disable the routing observability feature to monitor routing health in real-time. This feature is enabled by default. |
|
routingbot routingbot-crpd-vip v4-address |
VIP to connect to cRPD for routing observability. |
|
web-ui web-admin-password password |
Configure the password for the Web administrator. Ensure that the password does not start with 'ENC:'. |
|
web-ui web-admin-user user_e-mail_id |
Configure the login e-mail ID for the Web administrator. |
Required Privilege Level
configure
Release Information
Statement introduced in Juniper Paragon Automation Release 2.0.0.
pathfinder option introduced in Juniper Paragon Automation Release
2.1.0.
test-agent-gateway-vip-ipv6 option introduced in Juniper Paragon
Automation Release 2.2.0.
aiops, gnmi-term, oc-term, and
routingbot options introduced in Juniper Paragon Automation
Release 2.4.0.
pce-server-global-default-tls-mode and
pce-server-user-certificate options introduced in Juniper
Routing Director Release 2.5.0.