kLWC Configuration Overview

Internal and External Network Requirements

kLWC requires:

• An internal network port that connects the kLWC to the Juniper devices on the network.

• An external network port that connects the kLWC to the Juniper Virtual Private Cloud.

Before connecting the kLWC to the internal network, ensure that you have:

• A DHCP or static IP address.

• IP connectivity to the DNS server, managed devices on the network, and bastion hosts used (if applicable).

  Note:

  Bastion hosts utilize a SOCKS5 proxy server to reach target devices in the customer's network. Bastion hosts also support connection hopping, where an SSH session is first established with a customer's Linux-based device, which then initiates a subsequent SSH session to the target device.

• Enabled NETCONF in the Junos OS configuration of all target Juniper devices. The kLWC uses SSH credentials to connect to the devices on the network and, if used, bastion hosts.

  See also Establish an SSH Connection for a NETCONF Session.

Before connecting the kLWC to the external network, ensure that you have:

• A DHCP or static IP address.

• A DNS server in case you have selected a static address. In case of any subsequent change to the DNS, you must notify your Juniper account's team about it and get it updated. Otherwise, the kLWC might lose connectivity to the external endpoints.

  The kLWC supports real static, private static, or DHCP addresses. It prefers Network Address Translation (NAT).

• Accessibility to the DNS and IP addresses specified in Table 1 through the IP addresses assigned to external port on the kLWC.

  Table 1: Outbound Connectivity Requirements

  Description	DNS Name	IP Address	Port
  Juniper cloud	AWSProxy-prod.jssprod.junipercloud.net	52.223.32.79, 35.71.174.221, 35.164.173.102, 52.26.8.178, 54.149.201.209	443

Note:

The internal and external interfaces must be assigned IP addresses from different subnets.