Download: NetOp Agent Installation Manual (PDF) · Rev 1.0 · March 2025 · 14 pages
Prerequisites and deployment process · Applies to NetOp Agent 1.0
About the NetOp Agent
The NetOp Agent is a software application that provides secure, private, and reliable communication between the customer site and the NetOp Cloud services. It is installed on-premises on a commercial off-the-shelf (COTS) server and acts as a lean collector broker, collecting metrics from network appliances and passing them to NetOp for processing.
Audience: technical personnel involved in the design, specification, or deployment of the NetOp Agent at a customer site.
Agent prerequisites
Overview
The NetOp Agent can run on either physical or virtual machines. Using a virtual machine is common and lets customers augment their existing infrastructure with edge intelligence such as the NetOp Agent. The Agent is agnostic to the underlying virtualization technology and works on VMs running on platforms such as Hyper-V and vSphere.
Minimum system requirements
- 1 GHz or faster 64-bit processor with four or more cores
- 8 GB RAM
- 256 GB SSD storage
- 1× 1 Gbps Ethernet NIC (two preferred)
Supported operating systems
- Ubuntu Server 24.04 LTS
- Ubuntu Server 22.04 LTS
Firewall, network, and security settings
As a collector and broker, the NetOp Agent typically sits in the DMZ, with firewall protection toward both the WAN and the LAN. When implemented properly, a DMZ subnet lets an organization isolate its local network from the Internet.
For networks that do not require absolute isolation from the Internet, such as typical enterprise or venue networks, it is common to place the Agent behind the organization's firewall without a DMZ.
To allow network segregation, we recommend using two physical network interfaces on the Agent host machine:
- LAN interface — faces the customer network. Its IP address should be in the same subnet as the customer network devices.
- WAN interface — faces the NetOp cloud. This is the host machine's default gateway.
If the LAN interface and the customer network devices are not on the same subnet, add a routing rule to the host machine's routing table so that all packets destined for those devices use the LAN interface instead of the default gateway.
WAN exposed ports and FQDNs
| To | Protocol | Port |
|---|---|---|
| All outbound communication | HTTPS | 443 |
Initial installation and lifecycle management of the NetOp Agent requires access to these Docker repositories:
docker.iogcr.io/netop-engineering
An additional connection is required to the following FQDN and all of its subdomains:
monitor.opscenter.cloud
LAN exposed ports
| To | Protocol | Port |
|---|---|---|
| Network device | SNMP | 162 |
| Network device | Syslog | 514 |
Installation process
Overview
Installation uses an Ubuntu machine prepared by the customer and a self-installation script that configures the machine environment and installs the NetOp Agent software.
Requirements
Resource access — before you start, verify that:
- You have the sudo password for the Ubuntu machine.
- You have access to the NetOp web application, with permission to add a new Integration for your organization. This is required to obtain the Agent configuration file used during installation. Alternatively, you can obtain an Agent configuration file from the NetOp support team.
Machine OS — the installation procedure applies only to the supported operating systems. Verify your OS version before starting:
lsb_release -a
Step 1: Obtain the configuration file from NetOp
- In the NetOp web UI, select the required customer from the Account menu.
- From the left menu, select the Integrations page.
- Click the large NetOp icon to create a new NetOp Agent integration, and give it a descriptive name. The name is used for display only.
- Click Save.
- Locate the newly created row in the list with the vendor NetOp Agent.
- Download the
registration.conffile using the download button on the Agent row. - Copy the file from your laptop to the machine you will install the NetOp Agent on.
Figure 1 – NetOp Agent integration
Important: Keep
registration.confin a safe place — it holds sensitive information about your Agent's identity. You can only download the file once. If you lose the file before it is used, create a new integration.
Step 2: Copy the config file to the host machine
Place the file on the host machine in the directory where you want to install the Agent, or create a new file there and paste in the file content using vi or a similar editor.
Step 3: Prepare the environment
-
Download the NetOp installation package:
wget https://storage.googleapis.com/netop-agent/release/netop-agent.run
-
Change the file permissions:
chmod +x netop-agent.run
Step 4: Run the installer
Make sure registration.conf is in the same directory as netop-agent.run, then run the Agent installation script:
./netop-agent.run
Follow the instructions of the installation script. When installation finishes, you should see the message "installation complete!"
Figure 2 – Installation complete
Step 5: Clean up
After a successful installation, you can delete registration.conf. It is no longer needed and contains sensitive information.
Start, stop, or uninstall the Agent
The installation package creates a netop-agent directory containing the netopctl.sh script. Use it to start, stop, or uninstall the NetOp Agent:
netop-agent/netopctl.sh start|stop|uninstall
Agent configuration
After a successful installation, the Agent registers with NetOp Cloud and appears under Settings in the NetOp web UI.
- Log in to NetOp using your credentials.
- Select the customer and the site of the Agent you want to configure.
- From the left menu, select Settings → SNMP tab.
- Find the Agent name in the list.
Figure 3 – SNMP settings for the Agent
Agent not listed? If the Agent name does not appear on this page, Agent registration failed. This is often caused by blocked communication from the customer site to the NetOp Cloud services (see WAN exposed ports and FQDNs). For assistance, contact NetOp support.
Automatic SNMP asset discovery
NetOp scans the customer network, discovers devices, and adds them to the site's managed assets. This requires the following configuration.
SNMPv2 credentials
If the site includes devices managed with SNMPv2, add a row for each SNMPv2 community string required.
SNMPv2 community strings are essentially passwords used to access and manage devices on a network. They may be default strings such as "public" or "private", or custom strings, which are generally recommended for security.
NetOp only requires read-only access, hence the default community string is "private".
SNMPv3 credentials
If the site includes devices managed with SNMPv3, add a row for each set of SNMPv3 credentials required.
Device subnets
NetOp scans all the subnets you provide and searches for managed devices using the credentials above. A subnet can be a /32 to specify a single device IP address, or a full range to scan.
Figure 4 – Subnet configuration example
Have feedback on this article? Email info@netop.cloud. Learn more at netop.cloud.
Comments
0 comments
Please sign in to leave a comment.