Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

vLWC Configuration Overview

Once the vLWC vApp is installed, you can now configure the Virtual Lightweight Collector (vLWC). It is recommended that you review the Internal and External Network Requirements before you configure.

You can configure vLWC using one of the following methods:

Internal and External Network Requirements

vLWC requires:

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

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

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

  • A DHCP or static IP address.

  • IP connectivity to the Domain Name Server (DNS), all the direct devices on the network, and bastion hosts used (if applicable) to access the devices.

    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 vLWC 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.

  • Enabled SFTP for the Remote Connectivity Suite over port 22 only for file collection.

    See also Configure Incoming SFTP Connections.

Before connecting the vLWC 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 inform Juniper about it and get it updated. Otherwise, the vLWC might lose connectivity to the external endpoints.

    The vLWC 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 vLWC.

    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