User's Guide

Table Of Contents
Adding the Virtual Sensor in ExtremeAnalytics
192 of 218
NOTE: If you enter an IP address included in a range defined in a site, the DNS Server and NTP
Server are automatically populated from that site, if defined.
13. Enter the Root Password for the Virtual Sensor.
14. Enter the Domain name (for example, extremenetworks.com).
15. Enter the DNS Server IP address and NTP Server IP address, if applicable.
16. Click Install.
NOTE: The installation may take several minutes. The Operations panel shows the progress of
the installation. It is normal for the progress to pause at 89 or 90 percent for a short
amount of time. During this time, the OVA is deployed and Extreme Management Center
is waiting for the new Virtual Sensor to be discovered via ZTP+. If Extreme Management
Center is not configured to on-board ZTP+ devices automatically, you need to access to
the Network > Discovered tab, and configure the new Virtual Sensor for Extreme
Management Center.
The Virtual Sensor is installed and displays in the Virtual Sensors table at the top
of the Analytics > Configuration > Virtual Sensors tab.
NOTE: If the installation process takes longer than five minutes, the Operation panel in Extreme
Management Center may incorrectly indicate the installation failed. If the Operations panel
indicates a failure, open the Network > Discovered tab and look for the Virtual Sensor. Continue
to add the Virtual Sensor via this tab. If the Virtual Sensor is NOT listed on the Discovered tab,
the cause may be one of the following:
l Extreme Management Center is not communicating with the management
interface of the Virtual Sensor.
l The Virtual Sensor is configured with the
Use DHCP option selected (step 11),
but the DHCP process did not complete successfully.
Open the Analytics > Application Flows tab to ensure the Virtual Sensor is
collecting flow data. Any fragmented packets the Virtual Sensor receives out of
order are re-ordered for processing and then forwarded in the correct order.
Once flows are collected by the Virtual Sensor, you can create packet captures
for those flows.
NOTES: If the Virtual Sensor receives traffic as it is initializing, packet drops (reported as mbuf
allocation failure) may be observed.