[-]
  
[-]
  
  
  
  
  
  
  
 
 
[-]
  
  
  
  
[-]
  
 [+]
  
[-]
Monitoring
  
 [+]
 [+]
 [+]
  
[-]
Monitoring guides
  
  
[-]
Templates
  
  
  
[-]
Cloud monitoring
 [+]
  
  
 [+]
Kubernetes
[-]
Network checks
 [+]
  
  
  
[-]
 [+]
  
  
  
  
  
  
 [+]
 [+]
 [+]
 [+]
[-]
CounterMeasures
  
 [+]
 [+]
  
  
[-]
Panopta OnSight
 [-]
   
   
   
   
   
   
   
   
 [+]
[-]
SNMP
 [+]
  
[-]
Alerting
 [+]
 [+]
 [+]
 [+]
 [+]
[-]
Reporting
  
  
  
[-]
Maintenance
  
  
[-]
API
  
  
  
  
[-]
Users, Groups, and Authentication
 [+]
  
  
  
[-]
Billing and Payments
  
  
  
  
  
  
 
[-]
  
  
  
  
  
  
  
  
  
  
  
  
Updated on 9/12/2019
Online Help
OnSight virtual image installation
Direct link to topic in this publication:

To install the OnSight vCollector behind your firewall, perform the following steps:

  1. Select + Add from the main navigation header then select OnSight vCollector.

A new window will open guiding you through the process of installing the OnSight vCollector.

  1. Select the Virtual Appliance tab then follow the on-screen instructions.

    Information

    Looking for AWS?

    If you are in AWS, please read this article instead.

  1. Once you have downloaded OnSight image, import it as a virtual machine on your hypervisor. Once your OnSight is imported and booted, you will see the following screen.
    Warning

    Networking not configured

    If you receive a message stating networking is not configured, your OnSight will not work correctly until you either:
    1. Assign a static IP to the OnSight (see Manually assign a static IP address on the OnSight virtual machine image (Ubuntu))
    2. Enable DHCP on your network

  1. Proceed through the final steps of the OnSight installation process in the Panopta Control Panel, where you can assign things such as the Alert Timeline and Instance Group to use for your new OnSight.
    It will begin syncing immediately after deployment, assuming networking is configured correctly.

Manually assign a static IP address on the OnSight virtual machine image (Ubuntu) 

In order to manually set up networking on the underlying OS of the OnSight, perform the following:
  1. Log in to the OnSight VM via the console by accessing the VM's virtual console via your hypervisor management interface and logging in to the shell using the username panopta.admin.
    The password is the OnSight Key shown on the console (including all the dashes). 
  2. Verify the name of the Ethernet interface that you want to configure by running the following command:
    Information
    Interface name may differ based on hypervisor platform

    Your interface name may differ from eth0 to something else based on your virtualization platform. If it is something different than eth0, maintain that name within the section contents below. 

    JSON
    ifconfig -a

    A list of all available network interfaces will be displayed. In this example, the name of the interface is eth0.
    JSON
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
    inet 10.0.0.7 netmask 255.255.255.0 broadcast 10.0.0.255
    inet6 fe80::20d:3aff:fe1d:8706 prefixlen 64 scopeid 0x20<link>
    ether 00:0d:3a:1d:87:06 txqueuelen 1000 (Ethernet)
    RX packets 13462 bytes 6254842 (6.2 MB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 14557 bytes 3067782 (3.0 MB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10<host>
    loop txqueuelen 1000 (Local Loopback)
    RX packets 1212 bytes 92512 (92.5 KB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 1212 bytes 92512 (92.5 KB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

  3. Open the Netplan configuration file by running the following command:
    JSON
    sudo nano /etc/netplan/50-cloud-init.yaml

    Information Note: In most machines, the Netplan configuration file is 50-cloud-init.yaml. In other instances, the filename could be 01-netcfg.yaml or NN_interfaceName.yaml. If there are no files in /etc/netplan/, create a file called 50-static-ip.yaml
  4. Edit the configuration file as follows:
    JSON
    network:
    ethernets:
    eth0:
    dhcp4: false
    addresses:
    - <enter the IP address and subnet in CIDR notation. For example: 192.168.121.10/32>
    gateway4: <enter the gateway>
    nameservers:
    addresses: <[nameserver IPs]>
    set-name: eth0
    version: 2

    Information Note: The match condition for the interface MAC address may differ or not be mentioned in the Netplan file. Make sure it matches the MAC address from the ifconfig results from the previous step. 

  5. Close and save the file. To apply the changes, run the following command:
    JSON
    sudo netplan apply