Install DC Netscope

DC Netscope is a virtual appliance. Whatever your platform, its installation takes the same three steps: import the appliance, connect it to your virtualization platform so that it knows your virtual machines, and send it the flows of your network. Pick your platform below to see what each step means for you.

Not sure your infrastructure fits? Check Will it work on my infrastructure? first.

VMware vSphere

OVA
  1. Import the OVA from vSphere Deploy OVF Template in the vSphere Client, with the network and the administrator account in the wizard.
  2. Add a vCenter connector In the Services tab of the administration interface, with a read-only account.
  3. Configure the Distributed vSwitches NetFlow export to DC Netscope on each switch, enabled on each port group.
Full guide for VMware →

Nutanix AHV

OVA
  1. Import the OVA in Prism Central Upload it, then Deploy as VM with the settings given to cloud-init.
  2. Add a Nutanix connector In the Services tab of the administration interface, with a Prism account.
  3. Configure the IPFIX export From the administration interface of DC Netscope, which sets the export up on Nutanix itself.
Full guide for Nutanix →

XCP-ng

XVA
  1. Import the appliance in Xen Orchestra Import > VM, with the settings given to cloud-init.
  2. Add a Xen Orchestra connector In the Services tab of the administration interface, or directly from the cloud-init settings.
  3. Configure the Open vSwitch export NetFlow export set from the command line of each XCP-ng host.
Full guide for XCP-ng →

Other sources of flows

Whatever your platform, DC Netscope also receives the flows of any device that exports them, such as physical switches, routers, firewalls or probes. Point their export to the address of DC Netscope, on the ports listed in Ports to open.

See Supported equipment for the protocols of the usual switches, routers and firewalls. For a FortiGate firewall, see the sFlow export of Fortinet.

Note

The flows tell DC Netscope who talks to whom; the connector to your virtualization platform tells it who is who. The flows of devices outside of it are shown with their IP addresses, which you can name in the External IPs view.

Then

Once the flows come in, activate your license, manage the users, and explore the views.