Step 1: Begin

In this guide, we provide a simple, three-step path, to quickly get you up and running with the Juniper Support Insight (JSI) solution. We’ve simplified and shortened the installation and configuration steps.

Meet Juniper Support Insights

Juniper® Support Insights (JSI) is a cloud-based support solution that gives IT and network operations teams operational insights into their networks. JSI aims to transform the customer support experience by providing Juniper and its customers with insights that help improve the network performance and uptime. JSI collects data from Junos OS-based devices on customer networks, correlates it with Juniper-specific knowledge (such as service contract status, and End of Life and End of Support states), and then curates that into actionable insights.

Virtual Lightweight Collector

The Virtual Lightweight Collector (vLWC) is a VMware-ready data collection tool that gathers operational data from Juniper devices on customer networks. JSI uses this data to provide IT and network operations teams with actionable operational insights into the onboarded Juniper devices on customer networks. The vLWC uses your existing VMWare infrastructure to provide a virtualized solution while offering the capabilities of the LWC.

At a high level, getting started with the JSI solution involves the following steps:

  1. Installing and configuring a Virtual Lightweight Collector (vLWC)

  2. Onboarding a set of Junos devices to JSI to initiate data collection

  3. Viewing notifications about device onboarding and data collection

  4. Viewing operational dashboards and reports

Flowchart of a process with three steps: 1. Deploy and configure a collector. 2. Onboarding devices, data collection, viewing dashboards, and handling requests. 3. Ongoing activities.
Note:

This Quick Start guide assumes that you have ordered the JSI-vLWC solution, which is available as part of Juniper Care support service, and that you have an active contract. If you have not ordered the solution, please contact your Juniper Account or Services teams. Accessing and using JSI is subject to the Juniper Purchase and License Agreement (JPLA). For general information on JSI, see Juniper Support Insights Datasheet.

Install and Configure the Virtual Lightweight Collector

In this guide, we show you how to install and configure the vLWC on a VMWare environment.

Before You Begin

To successfully install and deploy vLWC, you must meet the following requirements:

  • VMware vCenter Server access (using VMware vSphere Client, version 6.7.0 or later)

  • One of the following minimum hardware requirements:

    Table 1: Hardware Requirements
    Configuration Type

    Total Devices Supported

    Number of vCPUs Memory Storage

    Small

    Up to 10,000 devices

    6 CPUs

    16 GB RAM

    400 GB disk space

    Large

    Up to 20,000 devices

    12 CPUs

    32 GB RAM

    400 GB disk space

    Warning:

    The vLWC can experience data collection issues if your system does not meet the minimum requirements. A lack of CPU and/or memory resources can cause the vLWC to go into a holding pattern and stop collecting data.

  • Three VM network interfaces:

    Table 2: Interface Description
    Connectivity Interface Name Description

    Internal

    int

    Internal network to access the Junos devices being monitored by JSI. This network should not have access to the Internet.

    External

    ext

    External network with HTTP/HTTPS and DNS Internet connectivity to connect to Juniper Cloud directly or through an active proxy server.

    Management

    cap

    Connectivity to the management network host services:

    • Port 443/HTTPS for the Captive Portal web page

    • Port 22/SSH for the JSI shell

    Note:

    While configuring the internal, external, and management interfaces, you must ensure that the subnet of the IP address assigned to the internal network port, external network port, and captive (management) portal are different from each other.

  • The vLWC software is provided as a single downloadable OVA file.

    Note:

    There are two end-user scenarios:

    • Customer—A customer can request the vLWC software for themselves.

    • Partner—A partner can request the vLWC software and then either associate it to themselves or to one of their customer accounts.

    To download the vLWC software, visit the vLWC request page on Juniper Support Portal at https://supportportal.juniper.net/s/vlwc-form, submit a form with the requested information, and receive a link over an email to download the vLWC software. Refer Download vLWC Software for more information.

    Note:
    • The OVA file will be created specifically for your installation. It contains your serial number as an encrypted vApp property that will be used during the initial boot process of the VM.

    • You can deploy only one vLWC OVA image with a unique serial number in your network. Deploying multiple vLWC OVA images with the same serial number is not supported. If you want to deploy multiple instances of vLWC in your network (for example, vLWC for production and lab), you must request a separate vLWC OVA image by submitting another request form.

  • Support for VMXNET3 network adapters.

Here's how to install vLWC using the vCenter Server:

  1. Login to the vCenter Server using your username and password in the vSphere Client.
  2. Click Menu > Hosts and Clusters to open the Hosts and Clusters page.

    The Hosts and Clusters page lists all your data centers and vSphere clusters on the left pane.

  3. Right-click your data center and click Deploy OVF Template... from the Actions menu.

    The Deploy OVF Template page opens.

  4. Depending on where your OVA file is available, select the URL option and provide the URL to the OVA file, or select the Local file option and click Choose Files to browse the local drive and upload the vLWC OVA image. Click Next.
    Deploy OVF Template wizard showing step Select an OVF template with Local file selected and vLWC-2.3.0.ova chosen. Next button highlighted to proceed.

    The Select a name and folder page opens.

  5. Enter a unique name for the vLWC vApp. Select the data center where you want the vApp installed and click Next.
    The Select a compute resource page opens.
    The vLWC vApp name that you enter is for easy identification only, and has no effect on the vLWC. The default vLWC vApp name is the OVA file name.
  6. Select the compute resource (a specific host or a cluster) where you want the vApp installed, and click Next.

    The Review details page opens.

  7. Verify the details listed on this page to make sure everything looks correct with the product, version, vendor, downloaded vApp file size, and the storage capacity of the virtual disk. Once you have verified the details, click Next.

    The Select storage page opens.

  8. Select the datastore you want to use for storing the virtual disk of the vLWC. Select Thick Provision Eager Zeroed as the virtual disk format. Select the VM storage policy and click Next.

    The Select networks page opens.

  9. Select the VMWare network to attach to each network interface using the Destination Network drop-down for each of the source network. You can ignore the IP allocation settings as they are not used by the vLWC. Click Next.
    Deploy OVF Template wizard showing Select networks step. Source networks ext, cap, int mapped to destination networks infra0, infra4, infra5. IP allocation is Static - Manual with IPv4 protocol. Navigation buttons Cancel, Back, Next.

    The Customize template page opens.

  10. Specify the network settings for each vLWC interface over a series of 20 vApp properties. For each interface, select the correct address type. For static address, specify the necessary settings for that interface. The internal, external, and management interfaces must each have unique DNS entries.
    Table 3: Supported IP Address Versions for Interfaces
    Interface Supported IP Address

    Internal

    IPv4 or IPv6 address

    External

    IPv4 address only

    Management

    IPv4 address only

    Customize template step in OVF deployment process. Network settings include options for vLWC internal interface IPv4 address type, static interface address, prefix, gateway, and DNS configuration.

    Once you have configured your network, click Next. The Ready to complete page opens.

  11. Verify the configured settings for the vApp deployment and click Finish to start the deployment of the vLWC.
    Final step of Deploy OVF Template wizard in VMware vSphere summarizing configuration details for deploying a virtual machine from an OVF template with provisioning type, VM name, template name, storage, network, IP settings, and finish button to complete deployment.
  12. Wait for VMWare to deploy the vApp. You should see progress bars in the recent tasks section indicating the progress of the vApp deployment. This process can take approximately 30 minutes or more depending on the speed of your cluster, datastores, and your connection to the vSphere.
    Note:
    • If you encounter the error message “Failed to deploy OVF package. ThrowableProxy.cause The operation is not supported on the object. The operation failed due to The operation is not supported on the object.”, ensure that DRS is enabled for the cluster in which you are deploying the vApp.

    • If you encounter any other error when you click Finish, it is possible that you took too long to complete the steps above and the deployment process timed out. You can reattempt the deployment process if this happens and if you encounter an error for the second time, open a Juniper TAC case for assistance.

  13. To start vLWC, you can right-click the newly created vApp and click Power On from the Actions menu.

    The vLWC is now installed and running in your environment. To confirm, you can view the summary page of the ggc-lnx VM located under the vLWC vApp entry. It should show an Ubuntu Linux (64-bit) VM running with VMware  Tools also running along with the IP addresses assigned to the VM in the IP addresses list.

    VMware vSphere Web Client interface showing VM ggc-lnx summary including Ubuntu OS, ESXi compatibility, VMware Tools status, DNS name, multiple IPs, powered-on state, and management actions.

Configure the Virtual Lightweight Collector

Once the vLWC vApp is installed, you can add or modify various vLWC settings through the Captive Portal web page. See, Configure LWC Settings.

Note:

You must connect to the captive portal through the ge-0/0/0 interface from a local IP address.

Accessing the captive portal from a browser will fail if the connection request originates from a non-local network.

Before you configure the Lightweight Collector (LWC), refer to the Internal and External Network Requirements.

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.

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 4 through the IP addresses assigned to external port on the vLWC.

    Table 4: Outbound Connectivity Requirements
    Description DNS Name IP Address Port
    Juniper cloud AWSProxy-prod.jssprod.junipercloud.net 52.223.32.79, 35.71.174.221 443
    Note:
    • The IP addresses assigned to the internal, external, and captive portal interfaces must be from different subnets.

    • The internal, external, and captive portal interfaces must each have unique DNS entries.

      Ensure that these interfaces can reach their respective DNS servers over both UDP and TCP on port 53.

Configure Network Settings through Captive Portal

To configure network settings through Captive Portal, see Configure LWC Settings user guide.