Network Traffic - OS Test

This test monitors the incoming and outgoing traffic through each Omnissa Horizon desktop on the cloud.

Target of the test : An Omnissa Horizon desktop on the cloud

Agent deploying the test : A remote agent

Outputs of the test : One set of results for every Omnissa_desktop:network_interface combination

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed.
Host	The nick name of the Omnissa Horizon Desktops component for which this test is to be configured.
Port	Refers to the port at which the specified host listens to. By default, this is NULL.
Sudocmd	This test executes certain privileged VDA (Virtual Desktop Access) commands to pull out the desired metrics from the Omnissa Horizon Desktop. To enable the test to run these commands, you first need to install a sudo package on the Omnissa Horizon Desktop host. The procedure for installing this package is detailed in Pre-requisites for Auto-Discovering VMs and Obtaining their Outside View. Once the package is installed, you need to specify the full path to the install directory of the sudo package in the Sudocmd text box.
Inside View Using	To obtain the 'inside view' of performance of the cloud-hosted Omnissa Horizon desktops - i.e., to measure the internal performance of the Omnissa Horizon desktops - this test uses a light-weight eG VM Agent software deployed on each of the desktops. Accordingly, this parameter is by default set to eG VM Agent (Omnissa Horizon).
Report By User	This flag is set to Yes by default. The value of this flag cannot be changed. This implies that the virtual machines in VDI environments will always be identified using the login name of the user. In other words, in VDI environments, this test will, by default, report measures for every username_on_virtualmachinename.
Report Powered OS	This flag is relevant only for those tests that are mapped to the Inside View of Desktops layer. If this flag is set to Yes (which is the default setting), then the 'inside view' tests will report measures for even those Omnissa Horizon desktops that do not have any users logged in currently. Such desktops will be identified by their name and not by the username_on_virtualdesktopname. On the other hand, if this flag is set to No, then this test will not report measures for those Omnissa Horizon desktops to which no users are logged in currently.
Is Cloud VMs	Since this test runs for 'Omnissa Horizon Desktops' component which is a cloud-hosted desktop group, this flag is set to Yes by default.
Is Full Duplex	By default, this flag is set to Yes, indicating that the incoming and outgoing data traffic is handled in full duplex mode. This means that the network interfaces are sending and receiving data at the same time. If the data traffic in your environment is handled in half-duplex mode, set this flag to No. This means that the network interfaces are not sending and receiving data at the same time; in essence, it is a one-way conversation. In this case, the test halves the value of the Incoming traffic and Outgoing traffic measures.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Incoming traffic	Indicates the rate at which data (including framing characters) is received on a network interface.	Mbps	An abnormally high rate of incoming traffic may require additional analysis.
Outgoing traffic	Represents the rate at which data (including framing characters) is sent on a network interface.	Mbps	An abnormally high rate of outgoing traffic may require additional analysis.
Maximum bandwidth	An estimate of the capacity of a network interface.	Mbps
Bandwidth usage	Indicates the percentage of bandwidth used by a network interface.	Percent	By comparing the bandwidth usage with the maximum bandwidth of an interface, an administrator can determine times when the network interface is overloaded or is being a performance bottleneck.
Output queue length	Indicates the length of the output packet queue (in packets)	Number	If this is longer than 2, delays are being experienced and the bottleneck should be found and eliminated if possible.
Outbound packet errors	The number of outbound packets that could not be transmitted because of errors	Number	Ideally, number of outbound errors should be 0.
Inbound packet errors	The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.	Number	Ideally, number of inbound errors should be 0.
Outbound packet discards	Indicates the number of error-free outbound packets that were discarded by this network interface during the last measurement period.	Number	Ideally, the value of these measures should be zero. These measures may report a non-zero value when an interface runs short of resources – e.g., NIC buffers.
Inbound packet discards	Indicates the number of error-free inbound packets that were discarded by this network interface during the last measurement period.	Number

Note:

If the Network Traffic - OS test is not reporting measures for a desktop, make sure that you have enabled the SNMP service for the desktop.