vRealize Operations Management Pack for NSX for … · The vRealize Operations Management Pack for...

vRealize Operations Management Packfor NSX for vSphere 2.0

This document supports the version of each product listed andsupports all subsequent versions until the document isreplaced by a new edition. To check for more recent editionsof this document, see http://www.vmware.com/support/pubs.

EN-001547-00

http://www.vmware.com/support/pubs

vRealize Operations Management Pack for NSX for vSphere 2.0

2 VMware, Inc.

You can find the most up-to-date technical documentation on the VMware Web site at:

http://www.vmware.com/support/

The VMware Web site also provides the latest product updates.

If you have comments about this documentation, submit your feedback to:

[email protected]

Copyright © 2014 VMware, Inc. All rights reserved. Copyright and trademark information.

VMware, Inc.3401 Hillview Ave.Palo Alto, CA 94304www.vmware.com

http://www.vmware.com/support/

mailto:[email protected]

http://pubs.vmware.com/copyright-trademark.html

Contents

About This Book 5

1 Introduction to the

vRealize Operations Management Pack for NSX for vSphere 7

2 Installing and Configuring the Management Pack 9

Install the Management Pack 9Configure the Management Pack 10Configure the Physical Discovery Adapter (EXPERIMENTAL FEATURE) 11

3 Management Pack for NSX for vSphere Dashboards 13

Displaying Management Pack for NSX for vSphere Dashboards 13NSX-vSphere Main Dashboard 14NSX-vSphere Topology Dashboard 15NSX-vSphere Object Path Dashboard 16NSX-vSphere Troubleshooting Dashboard 16

4 Working with the Management Pack for NSX for vSphere 17

Dashboard to Dashboard Navigation 19Open an External Application 20Run VXLAN Tunnel End Point Connectivity Test 21Run a Physical Path Discovery (EXPERIMENTAL FEATURE) 22

5 Management Pack for NSX for vSphere Alert Definitions 23

6 NSX-vSphere Capacity Models 29

Management Pack for NSX for vSphere Adapter Capacity Models 29Mangement Pack for NSX for vSphere Physical Adapter Capacity Models 33

7 Mangement Pack for NSX for vSphere Object Types and Metrics 35

NSX-vSphere Manager 36NSX-vSphere Controller Cluster 38NSX-vSphere Controller 40NSX-vSphere Transport Zone 42NSX-vSphere Logical Switch 44NSX-vSphere Logical Router 47NSX-vSphere Edge 50NSX-vSphere DHCP Edge Service 53NSX-vSphere DNS Edge Service 54NSX-vSphere Firewall Edge Service 55NSX-vSphere IPSec VPN Edge Service 57

VMware, Inc. 3

NSX-vSphere L2 VPN Edge Service 58NSX-vSphere Load Balancer Edge Service 59NSX-vSphere NAT Edge Service 63NSX-vSphere Routing Edge Service 63NSX-vSphere SSL VPN Edge Service 65Physical Fabric Metrics 66NSX-vSphere Physical Discovery Adapter Switch 66NSX-vSphere Physical Discovery Adapter Router 72NSX-vSphere Physical Discovery Adapter Network Device 74

8 Management Pack for NSX for vSphere Reports 83

Generate a Report 84

Index 85


4 VMware, Inc.

About This Book

The vRealize Operations Management Pack for NSX for vSphere Guide takes you through the process ofdeploying a working instance of the Management Pack for NSX for vSphere within your vCenterenvironment.

The vRealize Operations Management Pack for NSX for vSphere Guide also describes how to monitor theManagement Pack for NSX for vSphere environment.

Intended AudienceThis information is intended for the following users.

n Any network engineer, network administrator, network manager, or network operations manager whois involved with the daily operations related to deployment, configuration, change management,troubleshooting, and capacity management of VMware NSX for vSphere networking technologies.

n Any cloud operations manager, cloud infrastructure manager, or virtual administrator who hasoperation responsibility for troubleshooting virtual infrastructure problems, and within thisinfrastructure NSX for vSphere has been deployed.

VMware Technical Publications GlossaryVMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For definitionsof terms as they are used in VMware technical documentation, go to http://www.vmware.com/support/pubs.

VMware, Inc. 5

http://www.vmware.com/support/pubs


6 VMware, Inc.

Introduction to thevRealize Operations ManagementPack for NSX for vSphere 1

The vRealize Operations Management Pack for NSX for vSphere extends the operational managementcapabilities of the vRealize Operations platform to the areas of virtual and physical data center networking.

The vRealize Operations Management Pack for NSX for vSphere provides the following features:

n Visibility of all NSX networking services deployed in each vSphere cluster, including NSX manager,NSX controllers, and NSX data plane services such as logical switch, routers, firewalls, and so on.Several predefined widgets are used for representing NSX services.

n Visibility of vSphere hosts in NSX transport zones, in or across multiple vSphere clusters, for seeing themobility and routing spans.

n Search and navigate to functions for obtaining the operations health of deployed NSX objects.

n Embedded dependency rules of logical and physical networking relationships for problem alerting androot-cause problem solving. This feature includes detection and alerting of NSX configuration,connectivity, and health problems. All alerts are consolidated in a vRealize Operations alert interface.

n Extension of the core vRealize Operations health and risk analytics engine for the inclusion of NSXobject key performance and health indicators.

n Ability to draw end to end logical network topologies between any two selected virtual machines orNSX objects helps provide visibility into logical connectivity. Physical host and network devicerelationship in this view also helps in isolating problems in the logical or physical network.

n Advanced troubleshooting capabilities such as checking the connectivity between two VirtualTunneling End Points by running a ping between two hosts.

n Report templates to generate reports for NSX for vSphere objects.

VMware, Inc. 7


8 VMware, Inc.

Installing and Configuring theManagement Pack 2

When you install a management pack, you install the PAK file that you downloaded as part of the solution,and you configure the management pack instance.

This chapter includes the following topics:

n “Install the Management Pack,” on page 9

n “Configure the Management Pack,” on page 10

n “Configure the Physical Discovery Adapter (EXPERIMENTAL FEATURE),” on page 11

Install the Management PackA management pack is the part of the solution that you install.

Prerequisites

The solution that you downloaded includes a PAK file. Save that PAK file to a temporary folder on yourlocal system.

Procedure

1 Log in to the vRealize Operations Manager user interface with admin privileges.

2 In the left pane of vRealize Operations Manager, click the Administration icon and click Solutions.

3 On the Solutions tab, click the plus sign.

4 Browse to locate the temporary folder and select the PAK file.

For example, managementpack_name-buildnumber.pak.

5 Click Upload.

The upload might take several minutes.

6 Read and accept the EULA, and click Next.

Installation details appear in the window during the process.

7 Ensure that you install the PAK file on the master node.

8 When the installation is complete, click Finish.

What to do next

Configure an adapter instance for the management pack.

VMware, Inc. 9

Configure the Management PackAfter you install the management pack, configure an instance for the NSX Manager from which you arecollecting data.

Procedure

1 In the left pane of vRealize Operations Manager, click the Administration icon, and click Solutions.

2 Select Management Pack for NSX-vSphere and click the Configure icon.

3 Configure the instance settings.

Field Name Description

Display Name Name for the adapter instance. Use the host name or IP address of the NSXmanager as the adapter instance name.

Description (Optional) Describe the instance.

Collector Collector on which the NSX for vSphere adapter instance will run.

NSX Manager Host Host name or IP address of the NSX Manager from which you arecollecting data.

VC Host Host name or IP address of the vCenter Server to which you areconnecting.

Enable Log Insight integration ifconfigured

If you have vRealize Log Insight configured for use withvRealize Operations Manager, you can associate log files in Log Insightwith NSX for vSphere alerts, and view logging information for selectedalerts and objects in Log Insight.n Select True to enable automatic configuration of log forwarding to

Log Insight.n Select False if you do not want to enable automatic configuration of

log forwarding Log Insight.

4 To add the credentials used to access the NSX manager and the vCenter Server, click the plus sign.

Option Description

Credential name Enter the name by which you are identifying the configured credentials.

NSX Manager User name Enter the user name of the NSX Manager.

NSX Manager Password Enter the password of the NSX Manager

vCenter User Name Enter the user name of the vCenter server.

vCenter Password Enter the password of the vCenter server.

5 Click Test Connection to validate the connection.

6 Accept the NSX Manager certificate.

7 (Optional) The Advanced Settings area includes the Collector drop-down box, in which you can selectthe collector upon which you want to run the adapter instance. A collector gathers objects into itsinventory for monitoring. The collector specified by default has been selected for optimal datacollecting.

8 Click Save Settings.

The adapter instance is added to the Management Pack for NSX-vSphere Solution Details pane.

What to do next

Verify that the adapter is configured and collecting data by viewing application-related data.


10 VMware, Inc.

Table 2‑1. Successful Configuration Indicators

Where to View the Information Information to View

Collection Status and Collection State columns in theManagement Pack for NSX-vSphere Solutions Details paneon the Solutions tab

The strings Collecting or Data receiving appearapproximately five minutes after you have configured theadapter.

Environment Overview The objects related to NSX for vSphere are added to theinventory.

Dashboards Management Pack for NSX for vSphere dashboards areadded to the default vRealize Operations Managerdashboards.n NSX-vSphere Mainn NSX-vSphereTopologyn NSX-vSphere Object Pathn NSX-vSphere TroubleshootingClick the Home icon on the vRealize Operations Managermenu to view dashboards.

Configure the Physical Discovery Adapter (EXPERIMENTALFEATURE)

The Physical Discovery adapter enables you to monitor the Top of the Rack switches in your environment,and view related alerts, metrics and object capacity. You can also troubleshoot issues in your environmentby running a discovery action between two hosts. This action enables you to discover the network devicesbetween two Top of the Rack switches, and identify any problems.

CAUTION The Physical Discovery adapter is currently an experimental adapter. For more information abouthow this may affect your environment, see the release notes.

While Top of the Rack switches are discovered by the NSX for vSphere adapter, they are not monitored. Youmust configure the Physical Discovery adapter in order to monitor the switches and view alerts, metrics andobject capacity. This management pack supports all three versions of SNMP: SNMPv1, SNMPv2, andSNMPv3.

Prerequisites

n To monitor Top of the Rack switches, SNMP must be enabled in your network environment.

n For complete monitoring of your environment, Link Layer Discovery Protocol (LLDP) or CiscoDiscovery Protocol (CDP) must also be enabled on each network device.

Procedure

1 In the left pane of vRealize Operations Manager, click the Administration icon, and click Solutions.

2 Select Physical Discovery Adapter [EXPERIMENTAL], and click the Configure icon.

3 Configure the adapter settings.

Option Description

Display name Name for the adapter instance.

Description (Optional) Describe the instance.

SNMP Read Community Strings User ID or password that allows access to device statistics. The defaultvalue is public.

SNMP Ports Set to UDP port 161 by default.

SNMPv3 Authentication Password SNMPv3 authentication password

SNMPv3 Authentication Protocol SNMPv3 authentication protocol

Chapter 2 Installing and Configuring the Management Pack

VMware, Inc. 11

Option Description

SNMPv3 Privacy Password SNMPv3 privacy password

SNMPv3 User Name SNMPv3 user name

SNMP Version Version of the SNMP protocol used in your environment. Select fromSNMPv1, SNMPv2 or SNMPv3. If you select SNMPv3, enter the settingsspecific to your SNMPv3 environment.

4 Click Test Connection to validate the connection.

5 The Advanced Settings area includes the Collector drop-down box in which you can select thecollector upon which you want to run the adapter instance. This option has been set to the optimalcollector by default.

6 Click Save Settings.

The adapter instance is added to the Management Pack for NSX-vSphere Solution Details pane.

What to do next

n Run a physical path discovery between a pair of hosts or switches so that related switches and routersare monitored, and view related metrics, problem alerts and device capacity. See “Run a Physical PathDiscovery (EXPERIMENTAL FEATURE),” on page 22.


12 VMware, Inc.

Management Pack for NSX forvSphere Dashboards 3

The Management Pack for NSX for vSphere dashboards, enable you to diagnose and troubleshoot problemsin your logical and physical network.

For information about how to configure the options on the dashboard widgets, see thevRealize Operations Manager documentation, at https://www.vmware.com/support/pubs/.


n “Displaying Management Pack for NSX for vSphere Dashboards,” on page 13

n “NSX-vSphere Main Dashboard,” on page 14

n “NSX-vSphere Topology Dashboard,” on page 15

n “NSX-vSphere Object Path Dashboard,” on page 16

n “NSX-vSphere Troubleshooting Dashboard,” on page 16

Displaying Management Pack for NSX for vSphere DashboardsManagement Pack for NSX for vSphere dashboards are displayed in the vRealize Operations ManagerHome pane after the management pack is installed. If you have numerous dashboards open invRealize Operations Manager, the NSX for vSphere dashboards may not be visible.

Procedure

1 In the left pane of vRealize Operations Manager click the Home icon.

2 In the right pane, click Dashboard List, and from the drop-down menu point to NSX-vSphere andselect the NSX for vSphere dashboard you want to work with.

The selected dashboard is displayed in the vRealize Operations Manager Home page.

3 To ensure that Management Pack for NSX for vSphere dashboards are always available in the Homepage, click Dashboards List, and ensure that the NSX-vSphere check box is selected.

VMware, Inc. 13

https://www.vmware.com/support/pubs/

NSX-vSphere Main DashboardThe NSX-vSphere Main dashboard widgets provide an overview of the health of the network objects. Usethis dashboard to view network traffic information and NSX-related open alerts.

Table 3‑1. NSX Main Dashboard Widgets

Widget Description

NSX-vSphere Environments Displays a list of the environments that you are currentlymonitoring. When you select an environment in thiswidget, the other widgets in the NSX-vSphere Maindashboard show data for the selected adapter.

Key NSX-vSphere Components Displays a top level view of the following key components:n NSX Manager. Management plane virtual appliance

that helps configure logical switches and connectvirtual machines to these logical switches. It alsoprovides the management user interface and entrypoint for API for NSX, which helps automatedeployment and management of the logical networksthrough a Cloud management platform.

n NSX Controller. Responsible for managing theswitching and routing modules in the hypervisors.Supports an ARP suppression mechanism that reducesthe need to flood ARP broadcast requests across the L2network domain where virtual machines areconnected.

n NSX Edge. Virtual machines that provide logicalservices such as Routing and Network AddressTranslation, Firewall, Load balancing, L2 and L3Virtual Private Networks, and DHCP, DNS and IPaddress management.

n NSX Logical Router. Configures the routing softwareon each individual host in the environment.

The Key NSX-vSphere Components widget providesbadges that use scores to determine the condition of acomponent in a specific area, such as CPU, memory, diskand bandwidth usage. Each badge issues a score through acolored icon that is based on pre-defined badge scorethresholds.Point to a component to view a summary of theinformation that each badge provides.Click a component to open it in the Control Plane whereyou can manage and configure its health, view open alerts,and so on.

Objects Lists all the objects in the selected environment, andenables you to search for an object. Use the Objects widgetto select an object, and navigate to the NSX-vSphereTopology dashboard to view the physical and logicaltopologies of the object. You can also navigate to the ObjectPath dashboard to see how the selected object is connectedto another object.

Open Alerts Displays all the alerts open in the NSX for vSphereenvironment.

Transport Layer Heat map that shows the health of each transport node.Transport nodes are ESX hosts that are registered withNSX, and grouped by transport zones. You can view thehealth, workload, and network workload for each host, aswell as each vSphere distributed switch, by selecting therequired option from the Configurations drop-downmenu.


14 VMware, Inc.

Table 3‑1. NSX Main Dashboard Widgets (Continued)

Widget Description

Top Logical Networks By Traffic (KBps) Lists the five logical switches in the environment that arecurrently experiencing the most network traffic.

Top VMs by Traffic (KBps) Lists the five virtual machines in the environment that arecurrently responsible for the most network traffic.

NSX-vSphere Topology DashboardThe NSX-vSphere Topology dashboard provides you with details about the topology of a selected object,how it connects to the logical elements in the network, and a view of related alerts and metrics.

If you access the NSX-vSphere Topology dashboard directly from the menu bar, the Logical Topologywidget and the Physical Topology widget will not display data. To display data, in the Objects widget clickthe object for which you want to view details. You can also locate the object by searching for it in the Searchbox on the right side of the widget.

Table 3‑2. NSX-vSphere Topology Dashboard

Widget Description

NSX-vSphere Environment Displays a list of all the environments that you arecurrently monitoring. When you select an environment inthis widget, the other widgets in the NSX-vSphereTopology dashboard show data for the selectedenvironment.

Objects Lists all the objects in the selected environment, andenables you to search for a specific object. Use the Objectswidget to select a specific object, and navigate to the NSX-vSphere Topology widget to view the physical and logicaltopologies of the object. You can also navigate to the ObjectPath dashboard to see how the selected object is connectedto another object.

Logical Topology Provides a visual display for how the selected object isconnected to the logical network. Use this widget tonavigate around the network by clicking any of the objectsin the view. The view in the Physical Topology, Top Issuesand Metrics widgets is updated accordingly.Point to an object to view additional information such asthe name of the object, the object type and additionalconfiguration properties.To display an extended view that includes other connectedobjects, right-click an object, select Expand Node, andselect the objects you want to include in the expandedview.

Physical Topology Provides a visual display for how an object is connected tothe physical infrastructure. Click an object in this widget todisplay related open alerts and metrics.Point to an object to view additional information such asthe name of the object, the object type and additionalconfiguration properties.To display an extended view that includes other connectedobjects, right-click an object, select Expand Node, andselect the objects you want to include in the expandedview.

Chapter 3 Management Pack for NSX for vSphere Dashboards

VMware, Inc. 15

Table 3‑2. NSX-vSphere Topology Dashboard (Continued)

Widget Description

Top Issues Displays alerts for objects selected in the PhysicalTopology widget and the Logical Topology widget.

Metrics Displays metrics for objects selected in the PhysicalTopology widget and the Logical Topology widget.

NSX-vSphere Object Path DashboardUse the NSX-vSphere Object Path dashboard to run a visual path between two objects and see how they areconnected to each other, and to other objects in the environment. The resulting visual path enables you todetect possible connectivity problems.

For information on how to run a visual path between two objects, see “Detect Configuration ProblemsBetween Two Objects,” on page 20

Table 3‑3. NSX-vSphere Object Path Dashboard Widgets

Widget Description

NSX-vSphere Environments Displays a list of the NSX-vSphere environments that youare currently monitoring.

Objects Displays a list of objects in the environment.

Logical Path Provides a visual display for how the selected object isconnected to the logical network.

Physical Path Provides a visual display for how an object is connected tothe physical infrastructure.

NSX-vSphere Troubleshooting DashboardUse the NSX-vSphere Troubleshooting dashboard to run a VXLAN Tunnel End Point Connectivity test. Thishelps detect if any configuration problems you may be experiencing are a result of the configuration of thelogical network, or if there is a connectivity problem between two hosts.

For information on how to run a VXLAN Tunnel End Point Connectivity test, see “Run VXLAN Tunnel EndPoint Connectivity Test,” on page 21

Table 3‑4. NSX-vSphere Troubleshooting Dashboard Widgets

Widget Description

NSX-vSphere Environments Displays a list of the NSX-vSphere environments that youare currently monitoring.

NSX-vSphere Logical Switches Displays a list of the logical switches in your environment.

Data Collection Results Displays the results of the selected action.


16 VMware, Inc.

Working with the Management Packfor NSX for vSphere 4

The Management Pack for NSX for vSphere provides you with a high level view of your NSX for vSphereenvironment and enables you to drill down to more object-specific information by navigating from onedashboard to another, and also by opening selected objects in external applications. You can investigateproblems and better analyze the provided information. You can also make configuration changes, asrequired.

VMware, Inc. 17

Table 4‑1. Detect Configuration Problems Workflow

Do this To Example of use

n Navigate from oneNSX for vSphere dashboard toanother.

n AccessvRealize Operations Managertools.

Display object-specific information inmore detail.

n If an object has an alert opened inthe NSX-vSphere Main dashboard,and you want to visualize howthat object is connected in thelogical and physical networks,select the object in the NSX-vSphere Main dashboard andnavigate to the NSX-vSphereTopology dashboard.

n If, after discovering the logical andphysical paths of the object, yourequire more detail, identify anobject, for example, a host, andnavigate to the NSX-vSphereObject Path dashboard where youcan select another host, and load aview of the path between the twohosts. This visual path enables youto detect connectivity problemsbetween the two hosts.

n To displayvRealize Operations Manager tabsthat help you monitor and respondto problems, double-click an objector an alert.

Open an object in an externalapplication. TheManagement Pack for NSX forvSphere supports the followingapplications:n vSphere Web Clientn vRealize Log Insightn NSX Manager

1 Display additional informationabout an object that you cannotget fromvRealize Operations Manager.

2 Make configuration changes, ifrequired.

n When an alert is opened on anNSX for vSphere object, open theobject in Log Insight to see theNSX logs that are associated withthe time of the alert.

n If an alert that is opened on anEdge notifies you that the Edge isnot highly available, open theEdge in vSphere Web Client sothat you can configure the Edgeand make it highly available.

n If an alert that is opened on theNSX manager notifies you that theNSX manager is not using secureFTP backups, from the alert openthe NSX Manager and enable SFTPas the transfer protocol forbackups.

Run a VXLAN Tunnel End PointConnectivity Test

Check if a problem is caused byconfiguration issues between twohosts, or on one or more switches.

If packets are being dropped when onevirtual machine is communicatingwith another virtual machine, theVXLAN Tunnel End PointConnectivity test can be run todetermine if the physical fabricbetween those two virtual machines isconfigured correctly for VXLANtraffic.

Run a physical path discovery Discover the devices connected onthe path between two hosts or twoTop of the Rack switches.

If there is a connectivity issue betweentwo virtual machines, run a physicalpath discovery to monitor all physicalnetwork devices that connect thosetwo virtual machines together.


18 VMware, Inc.

NOTE If you are interested in integrating vRealize Log Insight with theManagement Pack for NSX for vSphere, you can locate an NSX for vSphere Log Insight Content Pack onVMware Solutions Exchange. See https://solutionexchange.vmware.com/store.


n “Dashboard to Dashboard Navigation,” on page 19

n “Open an External Application,” on page 20

n “Run VXLAN Tunnel End Point Connectivity Test,” on page 21

n “Run a Physical Path Discovery (EXPERIMENTAL FEATURE),” on page 22

Dashboard to Dashboard NavigationDashboard navigation enables you to navigate from one Management Pack for NSX for vSphere dashboardto another and view related information for a selected object. This enables you to detect configurationproblems in your environment.

A typical problem-solving workflow starts with a top-level view of your environment in the NSX-vSphereMain dashboard. If you detect a problem in your environment, drill-down to view more object-specificinformation. Navigate first to the NSX-vSphere Topology dashboard, to view the logical and physicalnetworks. If you require more detailed information, navigate to the NSX-vSphere Object Path dashboardwhere you can select another object of the same type and see if there are any connectivity problems on thepath between the two objects.

Access vRealize Operations Manager ToolsIn addition to troubleshooting problems by navigating between Management Pack for NSX for vSpheredashboards, you can also access the vRealize Operations Manager tools. For example, if you double-click anobject or alert in a Management Pack for NSX for vSphere dashboard, you display tabs that help youmonitor and respond to problems. Most useful is the Troubleshooting tab from which you can access theAll Metrics tab which provides a topological map and metrics for the selected object.

Dashboard NavigationYou can use dashboard navigation to navigate from one dashboard to another, and display dashboard-specific information for a selected object. This provides a more detailed view if you are experiencingproblems in your environment.

Dashboard navigation is available between the NSX for vSphere Main, NSX for vSphere Topology, andNSX for vSphere Object Path dashboards.

Procedure

1 Select an object in a widget.

2 In the widget toolbar, click the Dashboard Navigation icon, and select Navigate.

3 Select the dashboard to which you want to navigate.

The selected object is displayed in the dashboard.

What to do next

If you have identified a problem with a specific object in the NSX-vSphere Topology dashboard, navigate tothe NSX-vSphere Object Path dashboard where you can select an object of the same type, and see if there areany connectivity issues between the two objects.

Chapter 4 Working with the Management Pack for NSX for vSphere

VMware, Inc. 19

Detect Configuration Problems Between Two ObjectsIf you detect a problem with an object, and want to visualize the path between the object and another objectof the same type, navigate to the NSX-vSphere Dashboard where you can create a visual path between theobjects, and locate possible connectivity problems.

You can create a path between two virtual machines, two hosts, two logical switches, two edges or twological routers.

This action is run in the NSX-vSphere Object Path dashboard.

Procedure

1 Select the NSX-vSphere Object Path Dashboard.

2 In the NSX-vSphere Environments widget, select the environment to monitor.

3 In the Objects widget, search for the object type by name or type.

4 In the list of objects, select an object.

5 Select another object of the same type.

The Logical Path widget and Physical Path widgets display the connection paths between the two objects.

You can also create a visual path from another dashboard. For example, if you have detected a problem inthe NSX-vSphere Topology dashboard, select the object, navigate to the NSX-vSphere Object Pathdashboard, and then select another object to view the path.

What to do next

Check the connection path for configuration-related problems. If the objects on the path look healthy, or youdetect a problem but cannot correct it, run a VXLAN Tunnel End Point Connectivity test to check the healthof the host. See “Run VXLAN Tunnel End Point Connectivity Test,” on page 21.

Open an External ApplicationThe Management Pack for NSX for vSphere includes the ability to link to another application forinformation about an object. Open an object in another application if you need to display information thatyou cannot get from vRealize Operations Manager, or when you need to make configuration changes.

The Management Pack for NSX for vSphere enables you to access more information about specific objects,and configure them if required in vSphere Web Client, view logging information in Log Insight, and accessinformation about NSX-vSphere Manager objects, and configure them if required in NSX Manager.

Open Log InsightIf you have Log Insight configured with vRealize Operations Manager, you can view logging informationfor specific NSX for vSphere objects and alerts. When you configure Log Insight with the Management Packfor NSX-vSphere, the NSX Controller and Manager automatically forward logs to Log Insight.

Prerequisites

n Log Insight is configured for use with vRealize Operations Manager. In Log Insight, click Settings,Administration, vCenter Operations Manager and ensure that the Enable alerts integration andEnable Launch in Context check boxes are selected. For more information about configuring LogInsight for use with vRealize Operations Manager, see the Log Insight documentation at https://www.vmware.com/support/pubs/log-insight-pubs.html.

n Log Insight is integrated with the Management Pack for NSX for vSphere. See “Configure theManagement Pack,” on page 10.


20 VMware, Inc.

https://www.vmware.com/support/pubs/log-insight-pubs.html

Procedure

1 Select an object or an alert in a widget.

2 In the widget toolbar, click the Dashboard Navigation icon, and select View <component> Logs.

Log Insight is opened. Logging information for the selected object or alert is displayed.

Open vSphere Web ClientOpen objects in vSphere Web Client to view additional information about an object, or make configurationchanges.

Procedure

1 Select an object in a widget.

2 In the widget toolbar, click the Dashboard Navigation icon, and select Open <component> in vSphereClient.

vSphere Web Client opens. Information about the object is displayed.

Open NSX ManagerIf you cannot solve a problem in vRealize Operations Manager, or if you require extended monitoringcapabilities, open NSX-vSphere Manager objects in NSX Manager to see the complete configuration of theobject.

Procedure

1 Select a NSX-vSphere Manager object in a widget.

2 In the widget toolbar, click the Dashboard Navigation icon, and select Open in NSX Manager.

The NSX Manager opens. Information about the object is displayed.

Run VXLAN Tunnel End Point Connectivity TestIf you are experiencing connectivity problems between virtual machines, a VXLAN Tunnel End PointConnectivity test helps detect if the problem is with the configuration of the logical network, or if there is aconnectivity problem between the hosts the virtual machines are running on. This connectivity test is run inthe NSX-vSphere Troubleshooting dashboard.

Run a VXLAN Tunnel End Point Connectivity test after checking the visual path between two hosts, twological switches or two Edges for connectivity problems. See “Detect Configuration Problems Between TwoObjects,” on page 20.

The test is run with a default packet size of 1600 bytes. If the test fails when the packet size is set to 1600bytes, lower the packet size to 100 bytes, and run the test again.

Procedure

1 Select the NSX-vSphere Troubleshooting dashboard.

2 In the NSX-vSphere Logical Switches widget, select a logical switch.

3 In the NSX for vSphere Data Collection Results widget, from the Choose Action drop-down menu,select Run VXLAN Tunnel End Point Connectivity Test, and click the Run Action icon.

A dialog box is displayed enabling you to select the two hosts.

4 From the Host System drop-down menu, select one of the two hosts that are connected to the switch.

Chapter 4 Working with the Management Pack for NSX for vSphere

VMware, Inc. 21

5 From the Host System drop-down menu, select the second host.

6 Configure the packet size, and click OK.

Results may take up to two minutes to appear depending on the refresh period specified in the datacollection results. You can reduce the refresh period by clicking the Edit Widget pencil in the DataCollection Results widget, clicking the down arrow to reduce the value in the Refresh Interval option.

Test results are displayed in the Data Collection Results widget. If the test succeeds, this means there is aconfiguration problem on one or more of the switches between the two specified hosts.

Run a Physical Path Discovery (EXPERIMENTAL FEATURE)The Physical Discovery Adapter action enables you to run a physical path discovery between two hosts ortwo Top of the Rack switches, and discover the physical network devices that connect them together. Youcan troubleshoot connectivity by viewing related problem alerts, metrics and capacity models.

CAUTION The Physical Discovery adapter is currently an experimental adapter. For more information abouthow this may affect your environment, see the release notes.

Run this action on only two hosts, or two switches at a time. Ensure that the path between the selected hostsor switches contains no more than seven devices.

Prerequisites

n SNMP is enabled in your environment.

n The Physical Discovery Adapter instance has been configured as part of the Management Pack for NSX-vSphere. For more information, see“Configure the Physical Discovery Adapter (EXPERIMENTALFEATURE),” on page 11.

n The Link Layer Discovery Protocol (LLDP) or Cisco Discovery Protocol (CDP) is enabled on theswitches and routers in your SNMP environment.

Procedure

1 Select either two hosts or two Top of the Rack switches from any widget in which they appear.

2 Click the Action icon, and select Physical Discovery Action (LLDP/CDP Enabled Devices)[EXPERIMENTAL].

3 Select two switches, and click OK.

The task ID is displayed and the action begins to run.

4 To verify if the action is complete, click the Administration icon in the left pane, and select RecentTasks. Find the task name or task ID in the list, and view the action status.

Related devices are categorized in three categories; switches, routers, and network devices. After discoveryhas completed, and the devices have been collected by vRealize Operations Manager, they will be includedin the physical path that is shown between the two virtual machines. In the Physical Topology widget, thePhysical Fabric cloud now includes all discovered devices.

What to do next

View related metrics and alert definitions in the Environment Overview pane.


22 VMware, Inc.

Management Pack for NSX forvSphere Alert Definitions 5

NSX for vSphere alert definitions are a combination of symptoms and recommendations that identifyproblem areas in your environment and generate alerts on which you can act for those areas.

Table 5‑1. NSX -vSphere Alert Definitions

Alert Name Object Type Impact Severity Symptom

Controller is down Controller Health Critical n Fault:nsx.event.controller.status.unknown

Controller resource usage ishigh

Controller Health Warning n Metric: CPU|Usage (%) abovedynamic threshold

n Metric: Memory|Usage (%) abovedynamic threshold

n Metric: Disk|Usage (%) abovedynamic threshold

n Metric: Network|Usage (%) abovedynamic threshold

No syslog server is configured Controller Risk Immediate n Property: Configuration|Syslogserver = none

More than half of theControllers are not active

ControllerCluster

Health Critical n Metric: Status|Active (%) <50

All Controller VMs aredeployed on the same host

ControllerCluster

Risk Warning n Fault:nsx.event.controller.cluster.all.on.same.host

Manager resource usage is high Manager Health Warning n Metric: CPU|Usage (%) abovedynamic threshold


n Metric: Disk|Usage (%) abovedynamic threshold

vCenter inventory connectionhas been lost

Manager Health Critical n Property: Status|vCenterConnection Status = Disconnected

No backup of the environmenthas been recorded

Manager Risk Immediate n Property: Status|Last Backup Time= None

Scheduled backups are notenabled

Manager Risk Immediate Property: Configuration|BackupScheduled = false

No NTP server is configured Manager Risk Critical Property: Configuration|NTP servers =none

No syslog server is configured Manager Risk Warning Property: Configuration|Syslog Server= none

VMware, Inc. 23

Table 5‑1. NSX -vSphere Alert Definitions (Continued)


Manager API calls are failing Manager Health Critical Fault:nsx.event.manager.api.non.responsive

VXLAN segment range hasbeen exhausted

Manager Risk Warning Metric: VXLAN|Usage (%) = 100

Audit logs are excluded frombackup

Manager Risk Critical Property: Configuration|Backup|AuditLogs Excluded = true

System events are excludedfrom backup

Manager Risk Critical Property: Configuration|Backup|System Events Excluded = true

Backups are not using secureFTP

Manager Risk Critical Property: Configuration|Backup|Transfer Protocol

IPv6 is enabled Manager Risk Critical Property: Network:|IPv6 Address !=none

The distributed firewall isallowing all traffic by default

Manager Risk Immediate n Property: Distributed Firewall|Layer2|Rule:Default Rule = Allow

n Property: Distributed Firewall|Layer3|Rule:Default Rule = Allow

NSX Manager is using thedefault password

Manager Risk Critical Fault:nsx.event.manager.pwd.not.changed

Edge resource usage is high NSX Edge Health Warning n Metric: CPU|Usage (%) abovedynamic threshold


n Metric: Disk|Usage Rate (%) abovedynamic threshold

n Metric: Network|Usage (%) abovedynamic threshold

Edge is not highly available NSX Edge Risk Immediate n Property: Status|HA Status = Downn Property: Status|HA Status =

Unstablen Property: Status|HA Status =

Misconfiguration

High availability is not enabledon Edge

NSX Edge Risk Immediate Property: Status|HA Status = Off

One or more Edge interfacesare down

NSX Edge Health Critical Metric: Interface|Status = down

Edge VM is not responding tohealth check

NSX Edge Health Critical Fault:nsx.event.edge.vm.not.responding.to.health.check

Edge is not deployed NSX Edge Health Critical n Fault:nsx.event.gatewayservice.status.unknown

n Metric: Status|Status = undeployed

All Edge VMs are powered off NSX Edge Health Critical Metric: Status|Running = 0

Edge API calls are failing NSX Edge Health Critical Fault:nsx.event.edge.gateway.api.failure


NSX Edge Health Critical Fault:nsx.event.edge.vm.not.responding.to.heath.check

Logical switch is experiencingnetwork contention

Logical Switch Health Immediate Metric: Port|Dropped Packets (%) >1


24 VMware, Inc.



No neighbor relations havebeen formed

Logical Router Health Immediate Fault:nsx.event.logical.router.no.neighbors.relations

One or more Logical Routerinterfaces are down

Logical Router Health Critical Metric: Interface|Status = down

Logical Router is not deployed Logical Router Health Critical Fault:nsx.event.logical.router.status.unknown

Logical Router does not havean uplink interface configured

Logical Router Health Warning Fault: nsx.event.|router.no.connected.uplink.iface

One or more OSPF areas areusing insecure authentication

Logical Router Risk Immediate Fault: OSPF Area|Authentication Type!=MD5

Neither LLDP nor CDPdiscovery are enabled on theTop of the Rack switch

vSphereDistributedSwitch

Risk Warning Fault:nsx.event.dvs.link.discovery.disabled

Host NSX messaginginfrastructure is reporting anissue

Host System Health Immediate Fault:nsx.event.hostssystem.message.infra.status.down

One or more physical NICs arenot connected

Host System Health Immediate Fault:nsx.event.hostsystem.pnic.with.link.down

Management address notreported by Top of the Rackswitch

Host System Risk Warning Fault:nsx.event.hostsystem.cant.read.mgmt.address

Distributed Firewall CPUusage is high

Host System Health Immediate Fault:nsx.event.firewall.cpu.above.threshold

Distributed Firewall memoryusage is high

Host System Health Immediate Fault:nsx.event.firewall.mem.above.threshold

Distributed Firewall connectionrate is high

Host System Health Immediate Fault:nsx.event.firewall.conn.rate.above.threshold

Neither LLDP nor CDPdiscovery are enabled on theTop of the Rack switch

Host System Risk Warning Fault:nsx.event.hostsystem.lldp.or.cdp.not.enabled

A duplicate IP address wasfound for one or more physicalNICs on this host

Host System Health Warning Fault:nsx.event.hostsystem.ip.conflict.exists

Virtual machine IP addresses isnot in the same subnet as thelogical router

Virtual Machine Health Warning Fault:nsx.event.vm.vnic.ip.not.in.lrouter.subnet

Virtual machine defaultgateway does not match theLogical Router

Virtual Machine Health Warning Fault:nsx.event.vm.gateway.no.route.to.lrouter

NSX Edge VM is in a bad state Virtual Machine Health Critical Fault: nsx.event.edge.vm.state.status


Virtual Machine Health Critical Fault:nsx.event.edge.vm.not.responding.to.health.check

DNS Service is not running DNS EdgeService

Health Critical Fault: nsx.event.dns.service.status.down

DHCP Service is not running DHCP EdgeService

Health Critical Fault:nsx.event.dhcp.service.status.down

Chapter 5 Management Pack for NSX for vSphere Alert Definitions

VMware, Inc. 25



One or more IP pools havereached capacity

DHCP EdgeService

Risk Warning Metric: IP Pool|Usage (%) = 100

IP renewals are higher thannormal

DHCP EdgeService

Health Warning Metric: IP Pool|IP Addresses Renewed(last interval) above dynamic threshold

IPSec VPN Service is notrunning.

IPSec VPNEdge Service

Health Critical Fault:nsx.event.ip.sec.service.status.down

One or more IPSec channels aredown.

IPSec VPNEdge Service

Health Critical Property: Channel|Status = down

L2 VPN Service is not running L2 VPN EdgeService

Health Critical Fault:nsx.event.l2.vpn.service.status.down

One or more tunnels are down L2 VPN EdgeService

Health Critical Fault:nsx.event.l2vpn.tunnel.status.down

Load Balancer Service is notrunning.

Load BalancerEdge Service

Health Critical Fault: nsx.event.lb.service.status.down

One or more Load Balancerpool members are down

Load BalancerEdge Service

Health 1 Warning

2 Immediate

n Metric: Pool|Member|Status =DOWN

n Metric: Pool|Active (%) = 0

One or more NAT rules haveno destination

NAT EdgeService

Health Warning Fault:nsx.event.nat.rule.ip.with.no.corresponding.vm

No neighbor relations havebeen formed.

Routing EdgeService

Health Immediate Fault:nsx.event.edge.gateway.no.neighbors.relations

One or more OSPF areas areusing insecure authentication

Routing EdgeService

Risk Immediate Fault: OSPF Area|Authentication Type != MD5

SSL VPN Service is not running SSL VPN EdgeService

Health Critical Fault:nsx.event.sslvpn.service.status.down

Physical Discovery Adapter Alert Definitions (Experimental)Table 5‑2. Physical Discovery Adapter Alert Definitions


IP header errors areabnormally high

Switch, Router, andNetwork Device

Health Critical Metric: General|IP inHeader Errors

IP address errors areabnormally high


Health Critical Metric: General|IP inAddress Errors

Device not respondingto SNMP


Health Critical Fault: Deviceconnection statusfailure

Interface isexperiencing networkcontention on ingresstraffic


Health Critical Metric: Interfaces|Ingress DroppedPackets

Interface isexperiencing networkcontention on egresstraffic


Health Critical Metric: Interfaces|Egress DroppedPackets


26 VMware, Inc.

Table 5‑2. Physical Discovery Adapter Alert Definitions (Continued)


Interface ingresspacket errors areabnormally high


Health Critical Metric: Interfaces|Ingress ExceptionPackets

Interface egress packeterrors are abnormallyhigh


Health Critical Metric: Interfaces|Egress ExceptionPackets

Interface operationalstatus is down


Health Critical Fault: Port failure

Chapter 5 Management Pack for NSX for vSphere Alert Definitions

VMware, Inc. 27


28 VMware, Inc.

NSX-vSphere Capacity Models 6An object's capacity model, combined with policy settings, is used to determine the value of all badges andsub-badges aside from Health.

The NSX for vSphere Capacity model tables describe the capacity models that have been defined for eachobject type according to type of adapter: NSX-vSphere Adapter and Physical Discovery Adapter.

Capacity models have not been defined for the following:

n Physical Fabric

n L2 VPN Edge Services

n DNS Edge Services

n Transport Zones


n “Management Pack for NSX for vSphere Adapter Capacity Models,” on page 29

n “Mangement Pack for NSX for vSphere Physical Adapter Capacity Models,” on page 33

Management Pack for NSX for vSphere Adapter Capacity ModelsThe Management Pack for NSX for vSphere Capacity model table describes the capacity models that havebeen defined for the NSX for vSphere Adapter.

NSX-vSphere ManagerTable 6‑1. NSX-vSphere Manager Capacity Model

Container Description Use in Workload

CPU CPU usage of the Manager's virtualappliance, as measured by NSX

Yes

Memory vRAM usage of the Manager's virtualappliance, as measured by NSX

Yes

Disk Space amount of disk space used by theManager's virtual appliance, asmeasured by NSX

Yes

VXLAN VXLAN segments (i.e. logicalswitches) that have been allocated, asmeasured by NSX

No

VMware, Inc. 29

NSX-vSphere Controller ClusterThe capacity of the controller cluster is represented by the aggregated capacity of all controllers.

Table 6‑2. NSX-vSphere Controller Cluster


CPU Aggregated CPU usage across allController virtual appliances, asmeasured by vCenter.

Yes

Memory Aggregated vRAM usage across allController virtual appliances, asmeasured by vCenter.

Yes

Disk Aggregated disk space used by allController virtual applicances, asmeasured by vCenter.

Yes

Network Aggregated network usage across allController virtual appliances, asmeasured by vCenter. The capacityfor this container uses a maximumvalue approach.

Yes

NSX-vSphere Logical Switch

Table 6‑3. NSX-vSphere Logical Switch

Container Description Use in Workflow

Network|Egress statistics Aggregated egress networkutilization of all Virtual Machinesattached to the Logical Switch, asmeasured by vCenter. The capacityfor this container uses a maximumobserved value approach.

Yes

Network|Ingress statistics Aggregated ingress networkutilization of all Virtual Machinesattached to the Logical Switch, asmeasured by vCenter. The capacityfor this container uses a maximumobserved value approach.

Yes

Network|Usage Aggregated total network utilizationof all Virtual Machines attached tothe Logical Switch, as measured byvCenter. The capacity for thiscontainer uses a maximum observedvalue approach.

Yes

Port Logical ports that have been allocatedon all port groups, as measured byvCenter.

No

NSX-vSphere Logical Router


30 VMware, Inc.

Table 6‑4.


Interface Logical interfaces that have beenconfigured on the router, asmeasured by NSX

No

Route Static routes that have beenconfigured on the router, asmeasured by NSX.

No

NSX-vSphere Edge

Table 6‑5.

Container Description Used in Workload

CPU CPU usage of the Edge's virtualappliance, as measured by vCenter

Yes

Memory vRAM usage of the Edge's virtualappliance, as measured by vCenter.

Yes

Disk Disk space used by the Edge's virtualappliance, as measured by vCenter.

Yes

Network Network usage of the Edge's virtualappliance, as measured by vCenter.The capacity for this container uses amaximum observed value approach.

Yes

NSX-vSphere DHCP Edge Service

Table 6‑6.


Pool IP pools that have been configuredon the DHCP service, as measured byNSX.

No

NSX-vSphere Firewall Edge ServiceThe Network container (and usage metric) is not enabled by default, but can be enabled by editing the activepolicy

Table 6‑7. NSX-vSphere Firewall Edge Service


Network Active connections on the firewallservice, as reported by NSX.

Yes

Rule Firewall rules that have beenconfigured on the firewall service, asmeasured by NSX

No

NSX-vSphere IPSec VPN Edge Service

Chapter 6 NSX-vSphere Capacity Models

VMware, Inc. 31

Table 6‑8. NSX-vSphere IP Sec VPN Edge Service


Tunnel Active tunnels on the IPSec VPNservice, as reported by NSX.

Yes

NSX-vSphere Load Balancer Edge Service

Table 6‑9. NSX-vSphere Load Balancer Edge Service


Pool Load balancer pools configured onthe load balancer service, as reportedby NSX

No

Virtual Server Load balancer virtual serversconfigured on the load balancerservice, as reported by NSX

No

NSX-vSphere NAT Edge Service

Table 6‑10. NSX-vSphere NAT Edge Service


Rule NAT rules that have been configuredon the NAT service, as measured byNSX.

No

NSX-vSphere Routing Edge Service

Table 6‑11. NSX-vSphere Routing Edge Service


Route Static routes that have beenconfigured on the routing service, asmeasured by NSX

No

NSX-vSphere SSL VPN Edge Service

Table 6‑12. NSX-vSphere SSL VPN Edge Service


Network Active clients on the SSL VPNservice, as reported by NSX

Yes


32 VMware, Inc.

Mangement Pack for NSX for vSphere Physical Adapter CapacityModels

The Management Pack for NSX for vSphere Capacity model table describes the capacity models that havebeen defined for the Physical Discovery Adapter

SwitchTable 6‑13. Switch


Ingress Ingress network utilization of theswitch, as measured by SNMP.

Yes

Egress Egress network utilization of theswitch, as measured by SNMP.

Yes

RouterTable 6‑14. Router



Yes


Yes

Network DeviceTable 6‑15. Network Device



Yes


Yes

Chapter 6 NSX-vSphere Capacity Models

VMware, Inc. 33


34 VMware, Inc.

Mangement Pack for NSX for vSphereObject Types and Metrics 7


n “NSX-vSphere Manager,” on page 36

n “NSX-vSphere Controller Cluster,” on page 38

n “NSX-vSphere Controller,” on page 40

n “NSX-vSphere Transport Zone,” on page 42

n “NSX-vSphere Logical Switch,” on page 44

n “NSX-vSphere Logical Router,” on page 47

n “NSX-vSphere Edge,” on page 50

n “NSX-vSphere DHCP Edge Service,” on page 53

n “NSX-vSphere DNS Edge Service,” on page 54

n “NSX-vSphere Firewall Edge Service,” on page 55

n “NSX-vSphere IPSec VPN Edge Service,” on page 57

n “NSX-vSphere L2 VPN Edge Service,” on page 58

n “NSX-vSphere Load Balancer Edge Service,” on page 59

n “NSX-vSphere NAT Edge Service,” on page 63

n “NSX-vSphere Routing Edge Service,” on page 63

n “NSX-vSphere SSL VPN Edge Service,” on page 65

n “Physical Fabric Metrics,” on page 66

n “NSX-vSphere Physical Discovery Adapter Switch,” on page 66

n “NSX-vSphere Physical Discovery Adapter Router,” on page 72

n “NSX-vSphere Physical Discovery Adapter Network Device,” on page 74

VMware, Inc. 35

NSX-vSphere Manager

Table 7‑1. NSX-vSphere Manager Metrics

Name Category Type Unit Description Instanced

vCenterConnection Status

Status Property String Status of theconnectionbetween NSX-vSphereManager andvCenter.

No

Last Backup Time Status Property String Time that the lastbackup of theenvironmenttook place.

No

Provisioned CPU Metric MhZ Amount ofprocessingpower allocatedto the NSX-vSphereManagerappliance.

No

Used CPU Metric MhZ Amount ofprocessingpower currentlybeing used bythe NSX-vSphereappliance.

No

Usage CPU Metric % Percentage ofallocatedprocessingpower currentlybeing used bythe NSX-vSphereManagerappliance.

No

Provisioned Memory Metric KB Amount ofmemoryallocated to theNSX-vSphereManagerapplicance.

No

Used Memory Metric KB Amount ofmemorycurrently beingused by the NSX-vSphereManagerappliance.

No

Usage Memory Metric % Percentage ofmemory powercurrently beingused by the NSX-vSphereManager.

No


36 VMware, Inc.

Table 7‑1. NSX-vSphere Manager Metrics (Continued)


Provisioned Disk Metric GB Amount of diskspace allocatedto the NSX-vSphereManagerappliance.

No

Usage Disk Metric % Percentage ofallocated diskspace currentlybeing use by theNSX-vSphereManagerappliance.

No

Capacity VXLAN Metric Integer Maximumnumber oflogical switchesthat can beconfigured basedon the number ofVXLANsegments thathave beenallocated.

No

Used VXLAN Metric Integer Number oflogical switchesthat have beenconfigured.

No

Usage VXLAN Metric % Percentage oflogical switchesthat have beenconfiguredrelative to thenumber ofVXLANsegments thathave beenattached.

No

Syslog Server Configuration Property String Syslog serverthat NSX-vSphereManager logs arecurrently beingforwarded to.

No

NTP Servers Configuration Property String NTP servers thathave beenconfigured in theNSX-vSphereManager.

No

Backup Scheduled Configuration Property String Whether or notbackups of theenvironmenthave beenscheduled.

No

Chapter 7 Mangement Pack for NSX for vSphere Object Types and Metrics

VMware, Inc. 37

Table 7‑1. NSX-vSphere Manager Metrics (Continued)


Audit LogsExcluded

Configuration|Backup

Property String Whether or notaudit logs havebeen excludedfrom backups ofNSX-vSphere.

No

Transfer Protocol Configuration|Backup

Property String Transfer protocolbeing used forbackups of NSX-vSphere.

No

IPv6 Address Network Property String IPv6 address thatNSX-vSphereManager hasbeen configuredwith.

No

Default rule Firewall|Layer2 Property String Default actionfor the L2distributedfirewall.

No

Default rule Firewall|Layer3 Property String Default actionfor the L3distributedfirewall.

No

NSX-vSphere Controller Cluster

Table 7‑2. NSX-vSphere Controller Cluster Metrics


Controllers Status Metric Integer Number ofcontrollersprovisioned inthe cluster.

No

Active Status Metric % Percentage ofcontrollers in thecluster that arecurrently in anactive state.

No

Provisioned CPU Metric MhZ Amount ofprocessingpower allocatedto all NSX-vSphereControllers in thecluster.

No

Used CPU Metric MhZ Amount ofprocessingpower currentlybeing used by allNSX-vSphereControllers in thecluster.

No


38 VMware, Inc.

Table 7‑2. NSX-vSphere Controller Cluster Metrics (Continued)


Usage CPU Metric % Percentage ofallocatedprocessingpower currentlybeing used by allNSX-vSphereControllers in thecluster.

No

Provisioned Memory Metric KB Amount ofmemoryallocated to allNSX-vSphereControllers in thecluster.

No

Used Memory Metric KB Amount ofmemorycurrently beingused by all NSX-vSphereControllers in thecluster.

No

Usage Memory Metric % Percentage ofmemory powercurrently beingused by all NSX-vSphereControllers in thecluster.

No

Provisioned Disk Metric GB Amount of diskspace allocatedto all NSX-vSphereControllers in thecluster.

No

Used Disk Metric GB Amount of diskspace currentlybeing used by allNSX-vSphereControllers in thecluster.

No

Usage Disk Metric & Percentage ofallocated diskspace currentlybeing used by alNSX-vSphereControllers in thecluster.

No

Max ObservedThroughput

Network Metric KBps Maximumobservednetworkutilization of allNSX-vSphereControllers in thecluster.

No


VMware, Inc. 39

Table 7‑2. NSX-vSphere Controller Cluster Metrics (Continued)


Throughput Network Metric KBps Current networkutilization of allNSX-vSphereControllers in thecluster.

No

Usage Network Metric % Percentage ofnetworkbandwidthcurrently beingused by all NSX-vSphereControllers in thecluster, based onthe maximumobservednetworkutilzation.

No

NSX-vSphere Controller

Table 7‑3. NSX-vSphere Controller Metrics


Status Status Metric String Whether or notthe NSX-vSphereController iscurrentlyavailable andactive.

No

Provisioned CPU Metric MhZ Amount ofprocessingpower allocatedto the NSX-vSphereControllerappliance.

No

Used CPU Metric MhZ Amount ofprocessingpower currentlybeing used bythe NSX-vSphereControllerappliance.

No

Usage CPU Metric % Percentage ofallocatedprocessingpower currentlybeing used bythe NSX-vSphereControllerappliance.

No

Provisioned Memory Metric KB Amount ofmemoryallocated to theNSX-vSphereControllerappliance.

No


40 VMware, Inc.

Table 7‑3. NSX-vSphere Controller Metrics (Continued)


Used Memory Metric KB Amount ofmemorycurrently beingused by the NSX-vSphereControllerappliance.

No

Usage Memory Metric % Percentage ofmemory powercurrently beingused by the NSX-vSphereControllerappliance.

No

Provisioned Disk Metric GB Amount of diskspace allocatedto the NSX-vSphereControllerappliance.

No

Used Disk Metric GB Amount of diskspace currentlybeing used bythe NSX-vSphereControllerappliance.

No

Usage Disk Metric % Percentage ofallocated diskspace currentlybeing used bythe NSX-vSphereControllerappliance.

No


Network Metric KBps Maximumobservednetworkutilization of theNSX-vSphereControllerappliance.

No

Throughput Network Metric KBps Current networkutilization of theNSX-vSphereControllerappliance.

No


VMware, Inc. 41

Table 7‑3. NSX-vSphere Controller Metrics (Continued)


Usage Network Metric % Percentage ofnetworkbandwidthcurrently beingused by the NSX-vSphereControllerappliance, basedon the maximumobservednetworkutilization.

No

Syslog Server Configuration Property String Syslog serverthat NSX-vSphereController logsare currentlybeing forwardedto.

No

NSX-vSphere Transport Zone

Table 7‑4. NSX-vSphere Transport Zone Metrics


Hypervisors Summary Metric Integer Number of hostsregistered withthe NSX-vSphereTransport Zone.

No

Egress BroadcastPackets persecond

Network Metric Integer Rate of outgoingbroadcastpackets across alllogical switchesin the NSX-vSphereTransport Zone.

No

Egress MulticastPackets persecond

Network Metric Integer Rate of outgoingmulticast packetsacross all logicalswitches in theNSX-vSphereTransport Zone.

No

Egress UnicastPackets persecond

Network Metric Integer Rate of outgoingunicast packetsacross all logicalswitches in theNSX-vSphereTransport Zone.

No

Egress DroppedPackets persecond

Network Metric Integer Rate of outgoingpackets thatwere droppedacross all logicalswitches in theNSX-vSphereTransport Zone.

No


42 VMware, Inc.

Table 7‑4. NSX-vSphere Transport Zone Metrics (Continued)


Egress Packets persecond

Network Metric Integer Total rate ofoutgoing packetsacross all logicalswitches in theNSX-vSphereTransport Zone.

No

Egress Traffic Network Metric KBps Outgoingnetwork trafficacross all logicalswitches in theNSX-vSphereTransport Zone.

No

Ingress BroadcastPackets perSecond

Network Metric Integer Rate of incomingbroadcastpackets across alllogical switchesin the NSX-vSphereTransport Zone.

No

Ingress MulticastPackets persecond

Network Metric Integer Rate of incomingmulticast packetsacross all logicalswitches in theNSX-vSphereTransport Zone.

No

Ingress UnicastPAckets persecond

Network Metric Integer Rate of incomingunicast packetsacross all logicalswitches in theNSX-vSphereTransport Zone.

No

Ingress DroppedPackets persecond

Network Metric Integer Rate of incomingpackets thatwere droppedacross all logicalswitches in theNSX-vSphereTransport Zone.

No

Ingress Packetsper second

Network Metric Integer Total rate ofincomingpackets across alllogical switchesin the NSX-vSphereTransport Zone.

No

Ingress Traffic Network Metric KBps Incomingnetwork trafficacross all logicalswitches in theNSX-vSphereTransport Zone.

No

Total Packets persecond

Network Metric Integer Total rate ofpackets across alllogical switchesin the NSX-vSphereTransport Zone.

No


VMware, Inc. 43

Table 7‑4. NSX-vSphere Transport Zone Metrics (Continued)


Dropped Packetsper second

Network Metric Integer Total rate ofpackets thatwere droppedacross all logicalswitches in theNSX-vSphereTransport Zone.

No

Dropped Packets Network Metric KBps Percentage ofpackets thatwere droppedacross all logicalswitches in theNSX-vSphereTransport Zone.

No

Throughput Network Metric KBps Total networktraffic across alllogical switchesin the NSX-vSphereTransport Zone.

No

NSX-vSphere Logical Switch

Table 7‑5. NSX-vSphere Logical Switch Metrics


Egress BroadcastPackets persecond

Port Metric Integer Rate of outgoingbroadcastpackets across allvirtual machinesattached to theNSX-vSphereLogical Switch.

No

Egress MulticastPackets persecond

Port Metric Integer Rate of outgoingmulticast packetsacross all virtualmachinesattached to theNSX-vSphereLogical Switch.

No

Egress UnicastPackets persecond

Port Metric Integer Rate of outgoingunicast packetsacross all virtualmachinesattached to theNSX-vSphereLogical Switch.

No

Egress DroppedPackets persecond

Port Metric Integer Rate of outgoingpackets thatwere droppedacross all virtualmachinesattached to theNSX-vSphereLogical Switch.

No


44 VMware, Inc.

Table 7‑5. NSX-vSphere Logical Switch Metrics (Continued)



Port Metric Integer Total rate ofoutgoing packetsacross all virtualmachinesattached to theNSX-vSphereLogical Switch.

NO

Egress Traffic Port Metric KBps Outgoingnetwork trafficacross all virtualmachinesattached to theNSX-vSphereLogical Switch.

No

Ingress BroadcastPackets persecond

Port Metric Integer Rate of incomingbroadcastpackets across allvirtual machinesattached to theNSX-vSphereLogical Switch.

No

Ingress MulticastPackets persecond

Port Metric Integer Rate of incomingmulticast packetsacross all virtualmachinesattached to theNSX-vSphereLogical Switch.

No

Ingress UnicastPackets persecond

Port Metric Integer Rate of incomingunicast packetsacross all virtualmachinesattached to theNSX-vSphereLogical Switch.

No

Ingress DroppedPackets persecond

PORT Metric Integer Rate of incomingpackets thatwere droppedacross all virtualmachinesattached to theNSX-vSphereLogical Switch.

No

Ingress Traffic Port Metric KBps Incomingnetwork trafficacross al virtualmachinesattached to theNSX-vSphereLogical Switch.

No


Port Metric Integer Total rate ofpackets across allvirtual machinesattached to theNSX-vSphereLogical Switch.

No


VMware, Inc. 45



Dropped Packetsper second

Port Metric Integer Total rate ofpackets across allvirtual machinesattached to theNSX-vSphereLogical Switch.

No

Dropped Packets Port Metric % Percentage ofpackets thatwere droppedacross all virtualmachinesattached to theNSX-vSphereLogical Switch.

No

Througput Port Metric KBps Total networktraffic across allvirtual machinesattached to theNSX-vSphereLogical Switch.

NO

Used Port Metric Integer Number oflogical portscurrently beingused by the NSX-vSphere LogicalSwitch.

No

Capacity Port Metric Integer Maximumnumber oflogical ports thatcan be used bythe NSX-vSphereLogical Switch.

No

Attached VMs Summary Metric Integer Number ofvirtual machinescurrentlyattached to theNSX-vSphereLogical Switch.

No

VXLAN ID Configuration Property String VXLAN IDassigned to theNSX-vSphereLogical Switch.

NO

Control PlaneMode

Configuration Property String Control planemode configuredon the NSX-vSphere LogicalSwitch -Unicast,Multicast, orHybrid

NO


46 VMware, Inc.



Multicast Address Configuration Property String IP address to usefor multicastingby the NSX-vSphere LogicalSwitch. Not validwhen the controlplane modeUnicast

No

Subnet Network Property STRING Subnet in use bythe virtualmachinesattached to theNSX-vSphereLogical Switch.

No

Default Gateway Network Property String IP address of thedefault gatewaybeing used bythe virtualmachinesattached to theNSX-vSphereLogical Switch.

No

NSX-vSphere Logical Router

Table 7‑6. NSX-vSphere Logical Router Metrics


Used Interface Metric Integer Number ofinterfacescurrentlyconfigured onthe NSX-vSphereLogical Router.

No

Used Route Metric Integer Number of staticroutes currentlyconfigured onthe NSX-vSphereLogical Router.

No

Subnet Mask Interface Property String Subnet maskconfigured forthis interface.

Yes

Status Status Metric String Indicates if theNSX-vSphereLogical Router iscurrentlydeployed andavailable.

No

Standby VM Configuration Property String Name of thestandby virtualmachines for theNSX-vSphereLogical Router.Only valid whenhigh availabilityis enabled.

No


VMware, Inc. 47

Table 7‑6. NSX-vSphere Logical Router Metrics (Continued)


Size Configuration Property String Size of the NSX-vSphere LogicalRouter'sappliance.

No

Router ID Configuration Property String ID of the NSX-vSphere LogicalRouter. Onlyvalid for routingmode.

No

Protocol Address Configuration|OSPF

Property String Protocol IPaddressconfigured forOSPF routing onthe NSX-vSphereLogical Router.

No

NSX-vSphereLogical Switch

Bridge Property String Name of thelogical switchthat is used forthe bridge.

Yes

Mode Configuration Property String Indicateswhether theNSX-vSphereLogical Router isconfigured inrouting mode orbridging mode.

No

Management IPAddress

Network Property String IP address usedfor managementof the NSX-vSphere LogicalRouter.

No

Local AS Configuration|BGP

Property String Localautonomoussystemconfigured forBGP routing onthe NSX-vSphereLogical Router.

Yes

IP Address Interface Property String IP addressconfigured forthe interface.

Yes

ForwardingAddress

Configuration|OSPF

Property String Forwarding IPaddressconfigured forOSPF routing onthe NSX-vSphereLogical Router.

No

Enabled Configuration|OSPF

Property String Whether or notOSPF iscurrentlyenabled on theNSX-vSphereLogical Router.

No


48 VMware, Inc.

Table 7‑6. NSX-vSphere Logical Router Metrics (Continued)


Enabled Configuration|BGP

Property String Whether or notBGP is currentlyenabled on theNSX-vSphereLogical Router.

No

Distributed PortGroup

Bridge Property String Name of the portgroup that isused for thebridge.

Yes

Default Gateway Network Property String Default gatewayaddressconfigured onthe NSX-vSphereLogical Router.

No

Connected Interface Metric Binary Whether or notthe interface iscurrentlyconfigured.

Yes

Total Capacity Interface Property Integer Maximumnumber ofinterfaces thatcan beconfigured onthe NSX-vSphereLogical Router.

No

Total Capacity Route Property Integer Maximumnumber of staticroutes that canbe configured onthe NSX-vSphereLogical Router.

No

Attached VMs Status Metric Integer Number ofvirtual machinesusing the NSX-vSphere LogicalRouter.

No

AuthenticationType

OSPF Area Metric String Type ofauthenticationused for theOSPF area. None,Password, orMD5

Yes

Active VM Configuration Property String Name of theactive virtualmachine for theNSX-vSphereLogical Router.

No


VMware, Inc. 49

NSX-vSphere Edge

Table 7‑7. NSX-vSphere Edge Metrics


Status Status Metric String Indicates if NSX-vSphere Edge iscurrentlydeployed andavailable .

No

HA Status Status Property String Indicates if NSX-vSphere Edge iscurrently highlyavailable. Validvalues are:n Off if high

availability isnot enabled

n Down if thehighavailabilityservice is notrunning

n Misconfigured if bothvirtualmachines areconfiguredto run on thesame host

n Unstable ifthe standbyvirtualmachine isnot running

n Stable ifhighavailability isenabled,running, andconfiguredcorrectly.

No

Attached VMs Status Metric Integer Number ofvirtual machinesusing NSX-vSphere Edge.

No

Running Status Metric Integer Number ofcontrol virtualmachines forNSX-vSphereEdge that arerunning.

No

Size Configuration Property String Size of NSX-vSphere Edgeappliance.

No


50 VMware, Inc.

Table 7‑7. NSX-vSphere Edge Metrics (Continued)


Active VM Configuration Property String Name of theactive virtualmachine forNSX-vSphereEdge.

No

Standby VM Configuration Property String Name of thestandby virtualmachine forNSX-vSphereEdge. Only validwhen highavailability isenabled.

No

IP Address Interface Property String IP addressconfigured forthe interface.

Yes

Subnet Mask Interface Property String Subnet maskconfigured forthe interface.

Yes

Connected Interface Metric Binary Whether or notthe interface iscurrentlyconnected.

Yes


Interface Metric Integer Total rate ofoutgoing packetstransferredacross theinterface.

Yes

Egress Traffic Interface Metric KBps Outgoingnetwork trafficacross theinterface.

Yes

Ingress Packetsper second

Interface Metric Integer Total rate ofincomingpacketstransferredacross theinterface.

Yes

Ingress Traffic Interface Metric KBps Incomingnetwork trafficacross theinterface.

Yes

Max Interface Property Integer Maximumnumber ofinterfaces thatcan beconfigured onNSX-vSphereEdge.

No

Used Interface Metric Integer Number ofinterfacescurrentlyconfigured onNSX-vSphereEdge.

No


VMware, Inc. 51



Status Interface Metric String Current status ofthe interface.

Yes

Provisioned CPU Metric MhZ Amount ofprocessingpower allocatedto the NSX-vSphere Edgeappliance.

No

Used CPU Metric MhZ Amount ofprocessingpower currentlybeing used bythe NSX-vSphereEdge appliance.

No

Usage CPU Metric % Percentage ofallocatedprocessingpower currentlybeing used bythe NSX-vSphereEdge appliance.

No

Provisioned Memory Metric KB Amount ofmemoryallocated to theNSX-vSphereEdge appliance.

No

Used Memory Metric KB Amount ofmemorycurrently beingused by the NSX-vSphere Edgeappliance.

No

Usage Memory Metric % Percentage ofmemory powercurrently beingused by the NSX-vSphere Edgeappliance.

No

Provisioned Disk Metric GB Amount ofmemoryallocated to theNSX-vSphereEdge appliance.

No

Used Disk Metric GB Amount ofmemorycurrently beingused by the NSX-vSphere Edgeappliance.

No

Usage Disk Metric % Percentage ofmemory powercurrentlyallocated to theNSX-vSphereEdge appliance.

No


52 VMware, Inc.




Network Metric KBps Maximumobservednetworkutilization of theNSX-vSphereEdge appliance.

No

Throughput Network Metric KBps Current networkutilization of theNSX-vSphereEdge appliance.

No

Usage Network Metric % Percentage ofnetworkbandwidthcurrently beingused by the NSX-vSphere Edgeappliance, basedon the maximumobservednetworkutilization.

No

AuthenticationType

OSPF Area Metric String Type ofauthenticationused for theOSPF area. None,Password, orMD5. Valid only ifthe routingservice isenabled.

Yes

NSX-vSphere DHCP Edge Service

Table 7‑8. NSX-vSphere DHCP Edge Service Metrics


Service Status Status Metric String Whether or notthe service iscurrentlyrunning.

No

Total Capacity IP Pool Metric Integer Maximumnumber of IPpools that can beconfigured onthe NSX-vSphereDHCP EdgeService.

No

Used IP Pool Property Integer Number of IPpools currentlyconfigured onthe NSX-vSphereDHCP EdgeService.

No


VMware, Inc. 53

Table 7‑8. NSX-vSphere DHCP Edge Service Metrics (Continued)


Usage IP Pool Metric % Percentage of IPpools currentlyconfigured onthe NSX-vSphereDHCP EdgeService.

No

ProvisionedAddresses

IP Pool Metric Integer Number of IPaddresses thatcan be leasedfrom the IP Pool.

Yes

Addresses in Use IP Pool Metric Integer Current numberof IP addressesleased from theIP Pool.

Yes

Addresses in Use IP Pool Metric % Percentage of IPaddresses fromthe IP pool thathave beenleased.

Yes

IP AddressesRenewed (LastInterval)

IP Pool Metric Integer Number of newIP address leasesfrom the IP poolthat weregranted in thelast collectioninterval.

Yes

NSX-vSphere DNS Edge Service

Table 7‑9. NSX-vSphere DNS Edge Service Metrics



No

Enabled Configuration Property String Whether or notthe DNS serviceis enabled onNSX-vSphereEdge.

No

DNS Server 1 Configuration Property String First server touse for DNSlookups byvirtual machinesattached to NSX-vSphere Edge.Only valid if theDNS service isenabled.

No


54 VMware, Inc.

Table 7‑9. NSX-vSphere DNS Edge Service Metrics (Continued)


DNS Server 2 Configuration Property String Second server touse for DNSlookups byvirtual machineattached to NSX-vSphere Edge.Only valid if theDNS service isenabled.

No

Cache Size Configuration Property String Size of the DNScache for NSX-vSphere Edge.Only valid if theDNS service isenabled.

No

NSX-vSphere Firewall Edge Service

Table 7‑10. NSX-vSphere Firewall Edge Service Metrics



No

Connections Rule Metric Integer Current numberof activeconnections forwhich thefirewall rule hasbeen applied to.This collection ofthis metric isdisabled bydefault, but canbe enabled in theactive policy.Note thatcollection of thismetric will havean impact onoverallscalability.

Yes


VMware, Inc. 55

Table 7‑10. NSX-vSphere Firewall Edge Service Metrics (Continued)



Rule Metric Integer Total rate ofpacketstransferred forwhich thefirewall rule wasapplied to. Thiscollection of thismetric isdisabled bydefault, but canbe enabled in theactive policy.Note thatcollection of thismetric will havean impact onoverallscalability.

Yes

Total Traffic Rule Metric Integer Amount ofnetwork trafficfor which thefirewall rule wasapplied to. Thiscollection of thismetric isdisabled bydefault, but canbe enabled in theactive policy.Note thatcollection of thismetric will havean impact onscalability.

Yes

Max Rule Property Integer Maximumnumber of rulesthat can beconfigured onthe NSX-vSphereFirewall EdgeService.

No

Used Rule Metric Integer Number of rulescurrentlyconfigured onNSX-vSphereFirewall EdgeService.

No


56 VMware, Inc.

Table 7‑10. NSX-vSphere Firewall Edge Service Metrics (Continued)


Connections Network Metric Integer Current numberof activeconnectionsthrough NSX-vSphere FirewallEdge Service.This collection ofthis metric sdisabled bydefault, but canbe enabled in theactive policy.Note thatcollection of thismetric will havean impact onoverallscalability.

No

RecommendedConnectionCapacity

Network Metric Integer Recommendedmaximumnumber of activeconnectionsthrough NSX-vSphere FirewallEdge Service.

No

NSX-vSphere IPSec VPN Edge Service

Table 7‑11. NSX-vSphere IPSec VPN Edge Service Metrics



No

Max Tunnel Property Integer Maximumnumber of activeVPN tunnels thatcan beestablished withNSX-vSphereIPSec VPN EdgeService.

No

Active Tunnel Metric Integer Current numberof active VPNtunnelsestablished withNSX-vSphereIPSec VPN EdgeService.

No


VMware, Inc. 57

Table 7‑11. NSX-vSphere IPSec VPN Edge Service Metrics (Continued)


Egress Traffic Tunnel Metric KBps Outgoingnetwork trafficacross all activeVPN tunnelsestablished withNSX-vSphereIPSec VPN EdgeService.

No

Ingress Traffic Tunnel Metric KBps Incomingnetwork trafficacross all activeVPN tunnelsestablished withNSX-vSphereIPSec VPN EdgeService.

No

Total Traffic Tunnel Metric KBps Total networktraffic across allactive VPNtunnelsestablished withNSX-vSphereIPSec VPN EdgeService.

No

Status Channel Metric String Whether theIPSec channel iscurrently up ordown.

Yes

NSX-vSphere L2 VPN Edge Service

Table 7‑12. NSX-vSphere L2 VPN Edge Service Metrics



No

Status Network Metric String Whether the L2VPN connectionis currently up ordown.

No

Egress Traffic Network Metric KBps Outgoingnetwork trafficacross the NSX-vSphere L2 VPNEdge Servicetunnel.

No

Ingress Traffic Network Metric KBps Incomingnetwork trafficacross the NSX-vSphere L2 VPNEdge Servicetunnel.

No


58 VMware, Inc.

Table 7‑12. NSX-vSphere L2 VPN Edge Service Metrics (Continued)


Total Traffic Network Metric KBps Total networktraffic across theNSX-vSphere L2VPN EdgeService tunnel.

No

Mode Configuration Property String Indicateswhether NSX-vSphere L2 VPNEdge Service isconfigured inserver mode orclient mode.

No

IP Address Configuration Property String IP address usedfor the NSX-vSphere L2 VPNEdge Servicetunnel.

No

Port Configuration Property String Port used for theNSX-vSphere L2VPN EdgeService tunnel.

No

EncryptionAlgorithms

Configuration Property String Set of encryptionalgorithms thatcan be used toencrypt trafficacross the NSX-vSphere L2 VPNEdge Servicetunnel.

No

NSX-vSphere Load Balancer Edge Service

Table 7‑13. NSX-vSphere Load Balancer Edge Service Metrics



No

Max Pool Property Integer Maximumnumber of poolsthat can beconfigured onNSX-vSphereLoad BalancerEdge Service.

No

Used Pool Metric Integer Current numberof pools thathave beenconfigured onNSX-vSphereLoad BalancerEdge Service.

No


VMware, Inc. 59

Table 7‑13. NSX-vSphere Load Balancer Edge Service Metrics (Continued)


Status Pool Metric String Indicateswhether the loadbalancer pool isenabled or not.

Yes

Active Pool Metric % Percentage ofpool membersthat are currentlyactive in the loadbalancer pool.

Yes

Egress Traffic Pool Metric KBps Outgoingnetwork trafficfor all membersof the loadbalancer pool.

Yes

Ingress Traffic Pool Metric KBps Incomingnetwork trafficfor all membersof the loadbalancer pool.

Yes

Total Traffic Pool Metric KBps Total networktraffic for allmembers of theload balancerpool.

Yes

Current Sessions Pool Metric Integer Current numberof active sessionson all membersof the loadbalancer pool.

Yes

Max ObservedSessions

Pool Metric Integer Maximumobservednumber of activesessions on allmembers of theload balancerpool.

Yes

Sessions persecond

Pool Metric Integer Rate at whichsessions wereestablished on allmembers of theload balancerpool for the lastcollectioninterval.

Yes

Max ObservedSessions persecond

Pool Metric Integer Maximumobserved rate atwhich sessionswere establishedon all membersof the loadbalancer pool.

Yes

Status Pool|Member Metric String Indicateswhether the loadbalancer poolmember isenabled or not.

Yes


60 VMware, Inc.



Condition Pool|Member Metric String Indicateswhether the loadbalancer poolmember serviceis enabled or not.

Yes

Egress Traffic Pool|Member Metric KBps Outgoingnetwork trafficfor the loadbalancer poolmember server.

Yes

Ingress Traffic Pool|Member Metric KBps Incomingnetwork trafficfor the loadbalancer poolmember server.

Yes

Total Traffic Pool|Member Metric KBps Total networktraffic for theload balancerpool memberserver.

Yes

Current Sessions Pool|Member Metric Integer Current numberof active sessionson the loadbalancer poolmember server.

Yes


Pool|Member Metric Integer Maximumobservednumber of activesessions on theload balancerpool memberserver.

Yes

Sessions persecond

Pool|Member Metric Integer Rate at whichsessions wereestablished onthe load balancerpool memberserver for the lastcollectioninterval.

Yes


Pool|Member Metric Integer Maximumobserved rate atwhich thesessions wereestablished onthe load balancerpool memberserver.

Yes

Max Virtual Server Property Integer Maximumnumber ofvirtual serversthat can beconfigured onNSX-vSphereLoad BalancerEdge Service.

No


VMware, Inc. 61



Used Virtual Server Metric Integer Current numberof virtual serversthat have beenconfigured onNSX-vSPhereLoad BalancerEdge Service

No

Status Virtual Server Metric String Indicateswhether thevirtual server isenabled or not.

Yes

Egress Traffic Virtual Server Metric KBps Outgoingnetwork trafficfor the virtualserver.

Yes

Ingress Traffic Virtual Server Metric KBps Incomingnetwork trafficfor the virtualserver.

Yes

Total Traffic Virtual Server Metric KBps Total networktraffic for thevirtual server.

Yes

Current Sessions Virtual Server Metric Integer Current numberof active sessionson the virtualserver.

Yes


Virtual Server Metric Integer Maximumobservednumber of activesessions on thevirtual server.

Yes

Sessions persecond

Virtual Server Metric Integer Rate at whichsessions wereestablished onthe virtualserver.

Yes


Virtual Server Metric Integer Maximumobserved rate atwhich sessionswere establishedon the virtualserver.

Yes

Session Rate Limit Virtual Server Metric Integer Configured ratelimit at whichsessions can beestablished onthe virtualserver.

Yes


62 VMware, Inc.



HTTP RequestRate

Virtual Server Metric Integer Rate at whichHTTP requestswere made to thevirtual server.

Yes

Max ObservedHTTP RequestRate

Virtual Server Metric Integer Maximumobserved rate atwhich HTTPrequests weremade to thevirtual server.

Yes

NSX-vSphere NAT Edge Service

Table 7‑14. NSX-vSphere NAT Edge Service Metrics


Service Status Status Metric String Whether or notthe service isrunning.

No

Max Rule Property Integer Maximumnumber of rulesthat can beconfigured onNSX-vSphereNAT EdgeService.

No

Used Rule Metric Integer Current numberof rules that havebeen configuredon NSX-vSphereNAT EdgeService.

No

NSX-vSphere Routing Edge Service

Table 7‑15. NSX-vSphere Routing Edge Service Metrics



No

Max Route Property Integer Maximumnumber of staticroutes that canbe configured onNSX-vSphereRouting EdgeService.

No


VMware, Inc. 63

Table 7‑15. NSX-vSphere Routing Edge Service Metrics (Continued)


Used Route Metric Integer Number of staticroutes currentlyconfigured onNSX-vSphereRouting EdgeService.

No

Router ID Configuration Property String ID of NSX-vSphere RoutingEdge Service.

No

Enabled Configuration|OSPF

Property String Whether or notOSPF iscurrentlyenabled on NSX-vSphere RoutingEdge Service.

No

Protocol Address Configuration|OSPF

Property String Protocol IDaddressconfigured forOSPF routing onNSX-vSphereRouting EdgeService.

No

ForwardingAddress

Configuration|OSPF

Property String Forwarding IPaddressconfigured forOSPF routing onNSX-vSPhereRouting EdgeService.

No

Enabled Configuration|BGP

Property String Whether or notBGP is currentlyenabled on NSX-vSphere RoutingEdge Service.

No

Local AS Configuration|BGP

Property String Localautonomoussystemconfigured forBGP routing onNSX-vSphereRouting EdgeService.

No

Default Gateway Network Property String Default gatewayaddressconfigured onNSX-vSphereRouting EdgeService.

No


64 VMware, Inc.

NSX-vSphere SSL VPN Edge Service

Table 7‑16. NSX-vSphere SSL VPN Edge Service Metrics



No

Egress Traffic Network Metric KBps Outgoingnetwork trafficacross all clientsof NSX-vSphereSSL VPN EdgeService.

No

Ingress Traffic Network Metric KBps Incomingnetwork trafficacross all clientsof NSX-vSphereSSL VPN EdgeService.

No

Total Traffic Network Metric KBps Total networktraffic across allclients of NSX-vSphere SSLVPN EdgeService.

No

AuthenticationFailures perminute

Network Metric Integer Rate at whichauthenticationattempts to NSX-vSphere SSLVPN EdgeService havefailed during thelast collectioninterval.

No

Client Capacity Network Property Integer Maximumnumber of activeclients that canbe established onNSX-vSphereSSL VPN EdgeService.

No

Active Clients Network Metric Integer Current numberof active clientson NSX-vSphereSSL VPN EdgeService.

No


VMware, Inc. 65

Physical Fabric Metrics

Table 7‑17. Physical Fabric Metrics


Top of the RackSwitches

Summary Metric Integer Number of Topof the Rackswitches thathave beendiscovered.

No

NSX-vSphere Physical Discovery Adapter Switch

Table 7‑18. Physical Discovery Adapter Switch Metrics


System Uptime General Metric Integer Number ofseconds thathave elapsedsince the lasttime the devicewas booted.

No

IP in Receives General Metric Integer Total number ofinput datagramsreceived frominterfaces,including thosereceived in error.

No

IP in HeadersErrors

General Metric Integer Number of inputdatagramsdiscarded due toerrors in theirIPv4 headers,including badchecksums,version numbermismatch, otherformat errors,time-to-liveexceeded, errorsdiscovered inprocessing theirIPv4 options.

No


66 VMware, Inc.

Table 7‑18. Physical Discovery Adapter Switch Metrics (Continued)


IP in AddressErrors

General Metric Integer Number of inputdatagramsdiscardedbecause the IPv4address in theirIPv4 headers'destination fieldwas not a validaddress to bereceived at thisentity. This countincludes invalidaddresses, forexample, 0.0.0.0,and addresses ofunsupportedClasses, forexample Class E.For entitieswhich are notIPv4 routers, andtherefore do notforwarddiagrams, thiscounter includesdatagramsdiscardedbecause thedestinationaddress was nota local address.

No

IP ForwardDatagrams

General Metric Integer Number of inputdatagrams forwhich this entitywas not theirfinal IPv4destination, as aresult of whichan attempt wasmade to find aroute to forwardthem to that finaldestination. Inentities which donot act as IPv4routers, thiscounter willinclude onlythose packetswhich wereSource-Routedvia this entity,and the Source-Route optionprocessing wassuccessful.

No


VMware, Inc. 67



IP in Delivers General Metric Integer Total number ofinput datagramssuccessfullydelivered to IPv4user-protocols,including ICMP.

No

Ingress DroppedPackets

General Metric Integer Number ofinbound packetswhich werechosen to bediscarded eventhough no errorshad beendetected toprevent theirbeing deliverableto a higher-layerprotocol. Onepossible reasonfor discardingsuch a packetcould be to freeup buffer space.

No

Speed General Metric bps Total maximumbandwidth of alldevice interfaces.

No

Vendor Name General Property String Name of thedevice's vendor.

No

Model Name General Property String Name of thedevice's model.

No

Ingress Traffic Interfaces Metric Bps Amount ofnetwork trafficreceived fromthe interface.

Yes

Egress Traffic Interfaces Metric Bps Amount ofnetwork trafficsent to theinterface.

Yes

Ingress UnicastPackets

Interfaces Metric Integer Rate of unicastpackets receivedfrom theinterface.

Yes

Ingress Non-Unicast Packets

Interfaces Metric Integer Rate of non-unicast packetssent to theinterface.

Yes

Egress DroppedPackets

Interfaces Metric Integer Rate of outgoingpackets thatwere dropped onthe interface.

Yes

Egress ExceptionPackets

Interfaces Metric Integer Rate of outgoingpackets thatreported an erroron the interface.

Yes


68 VMware, Inc.



Speed Interfaces Metric Bps Interfacepublished maxbandwidth.

Yes

Index Interfaces Property String Unique value,greater thanzero, for eachinterface. It isrecommendedthat values areassignedcontiguouslystarting from 1.The value foreach interfacesub-layer mustremain constantat least from onere-initializationof the entity'snetworkmanagementsystem to thenext re-initialization.

Yes

Description Interfaces Property String A textual stringcontaininginformationabout theinterface. Thisstring shouldinclude the nameof themanufacturer,the productname and theversion of theinterfacehardware/software.

Yes

Type Interfaces Property String Interface typeaccording to theIANAIf Typeenum.

Yes

MTU Interfaces Property String The size of thelargest packetwhich can besent/received onthe interface,specified inoctets. Forinterfaces thatare used fortransmittingnetworkdatagrams, thisis the size of thelargest networkdatagram thatcan be sent onthe interface.

Yes


VMware, Inc. 69



Physical Address Interfaces Property String The interface'saddress at itsprotocol sub-layer. Forexample, for an802.x interface,this objectnormallycontains a MACaddress. Theinterface'smedia-specificMIB must definethe bit and byteordering and theformat of thevalue of thisobject. Forinterfaces whichdo not have suchan address (e.g.,a serial line), thisobject shouldcontain an octetstring of zerolength.

Yes

Admin Status Interfaces Property String The desired stateof the interface.The testing(3)state indicatesthat nooperationalpackets can bepassed. When amanaged systeminitializes, allinterfaces startwithifAdminStatus inthe down(2)state. As a resultof either explicitmanagementaction or perconfigurationinformationretained by themanaged system,ifAdminStatus isthen changed toeither the up(1)or testing(3)states (orremains in thedown(2) state).

Yes


70 VMware, Inc.



Operation Status Interfaces Property String The currentoperational stateof the interface.The testing(3)state indicatesthat nooperationalpackets can bepassed. IfifAdminStatus isdown(2) thenifOperStatusshould bedown(2). IfifAdminStatus ischanged to up(1)thenifOperStatusshould change toup(1) if theinterface is readyto transmit andreceive networktraffic; it shouldchange todormant(5) if theinterface iswaiting forexternal actions(such as a serialline waiting foran incomingconnection); itshould remain inthe down(2) stateif and only ifthere is a faultthat prevents itfrom going to theup(1) state; itshould remain inthe notPresent(6)state if theinterface hasmissing(typically,hardware)components.

Yes


VMware, Inc. 71



Last Change Interfaces Property String The value ofsysUpTime atthe time theinterface enteredits currentoperational state.If the currentstate was enteredprior to the lastre-initializationof the localnetworkmanagementsubsystem, thenthis objectcontains a zerovalue.

Yes

IP Addresses Interfaces Property String IP addresses listconfigured onthis interface.

Yes

Total Ingress Interfaces Metric KBps Total amount ofnetwork trafficreceived from allinterfaces.

Yes

Ingress Capacity Interface Metric KBps Maximumbandwidth thatcan be used forincomingnetwork traffic.

Yes

Total Egress Interfaces Metric KBps Total amount ofnetwork trafficsent to allinterfaces.

Yes

Egress Capacity Interface Metric KBps Maximumbandwidth thatcan be used foroutgoingnetwork traffic.

Yes

NSX-vSphere Physical Discovery Adapter Router

Table 7‑19. NSX-vSphere Physical Discovery Adapter Router



No

IP In Receives General Metric Integer No

IP In HeaderErrors

General Metric Integer No

IP In AddressErrors



72 VMware, Inc.

Table 7‑19. NSX-vSphere Physical Discovery Adapter Router (Continued)


IP ForwardDatagrams


IP In Delivers General Metric Integer No





Speed General Metric BPs No

Vendor Name General Property String Name of devicevendor.

No

Model Name General Property String Name of devicemodel.

No

Ingress Traffic Interfaces Metric Bps Amount ofnetwork trafficreceived fromthe interface.

Yes

Egress Traffic Interfaces Metric Bps Amount ofnetwork trafficsent to theinterface.

Yes


Interfaces Metric Integer Rate of unicastpackets receivedfrom thisinterface.

Yes


Interfaces Metric Integer Rate of non-unicast packetsreceived fromthis interface.

Yes

Ingress droppedpackets

Interfaces Metric Integer Rate of incomingpackets thatwere dropped onthe interface.

Yes

Ingress ExceptionPackets

Interfaces Metric Integer Rate of incomingpackets thatreported an erroron the interface.

Yes

Egress UnicastPackets

Interfaces Metric Integer Rate of unicastpackets sent tothe interface.

Yes

Egress Non-unicast Packets

Interfaces Metric Integer Rate of non-unicast packetssent to theinterface.

Yes


Interfaces Metric Integer Rate of outgoingpackets thatwere dropped onthe interface.

Yes


Interfaces Metric Integer Rate of outgoingpackets thatreported an erroron the interface.

Yes

Speed Interfaces Metric bps Yes


VMware, Inc. 73

Table 7‑19. NSX-vSphere Physical Discovery Adapter Router (Continued)


Index Interfaces Property String Yes

Description Interfaces Property String Yes

Type Interfaces Property String Yes

MTU Interfaces Property String Yes

Physical Address Interfaces Property String Yes

Admin Status Interfaces Property String Yes

Operation Status Interfaces Property String Yes

Last Change Interfaces Property String Yes

Total Ingress Interfaces Property KBps Total amount ofnetwork trafficreceived from allincomingnetwork traffic.

Yes


Yes


Yes


Yes

NSX-vSphere Physical Discovery Adapter Network Device

Table 7‑20. NSX-vSphere Physical Discovery Adapter Network Device Metrics



No

IP in Receives General Metric Integer Total number ofinput datagramsreceived frominterfaces,including thosereceived in error.

No


74 VMware, Inc.

Table 7‑20. NSX-vSphere Physical Discovery Adapter Network Device Metrics (Continued)


IP in HeaderErrors

General Metric Integer Number of inputdatagramsdiscarded due toerrors in theirIPv4 headers,including badchecksums,version numbermismatch, otherformat errors,time-to-liveexceeded, errorsdiscovered inprocessing theirIPv4 options,and more.

No

IP in AddressErrors

General Metric Integer Number of inputdatagramsdiscardedbecause the IPv4address in theirIPv4 headerdestination fieldwas not a validaddress to bereceived at thisentity. This countincludes invalidaddresses (forexample,0.0.0.0.), andaddresses ofunsupportedClasses (forexample, ClassE). For entitieswhich are notIPv4 routers, andtherefore do notforwarddatagrams, thiscounter includesdatagramsdiscardedbecause thedestinationaddress was nota local address.

No


VMware, Inc. 75



IP ForwardDatagrams

General Metric Integer Number of inputdatagrams forwhich this entitywas not theirfinal IPv4destination, as aresult of whichan attempt wasmade to find aroute to forwardthem to that finaldestination. Inentities which donot act as IPv4routers, thiscounter willinclude onlythose packetswhich weresource-routedvia this entity,and the source-route optionprocessing wassuccessful.

No

IP in Delivers General Metric Integer Total number ofinput datagramssuccessfullydelivered to IPv4user-protocols(includingICMP).

No


General Metric Integer Number ofinbound packetswhich werechosen to bediscarded eventhough no errorshad beendetected toprevent theirbeing deliverableto a higher-layerprotocol. Onepossible reasonfor discardingsuch a packetcould be to freeup buffer space.

No


76 VMware, Inc.




General Metric Integer Number ofoutboundpackets whichwere chosen tobe discardedeven though noerrors had beendetected toprevent theirbeingtransmitted. Onepossible reasonfor discardingsuch a packetcould be to freeup buffer space.

No

Speed General Metric bps Total maximumbandwidth of alldevice interfaces.

No

Vendor Name General Property String Name of thedevice vendor

No

Model Name General Property String Name of thedevice model

No

Ingress Traffic Interfaces Metric Bps Amount ofnetwork trafficreceived fromthe interface

Yes

Egress Traffic Interfaces Metric Bps Amount ofnetwork trafficsent to theinterface

Yes


Interfaces Metric Integer Rate of unicastpackets receivedfrom theinterface

Yes


Interfaces Metric Integer Rate of non-unicast packetsreceived fromthe interface

Yes


Interfaces Metric Integer Rate of incomingpackets thatwere dropped onthe interface

Yes

Ingress ExceptionPackets

Interfaces Metric Integer Rate of incomingpackets thatreported an erroron the interface

Yes

Egress UnicastPackets

Interfaces Metric Integer Rate of unicastpackets sent tothe interface

Yes

Egress non-unicastPackets

Interfaces Metric Integer Rate of non-unicast packetssent on theinterface

Yes


VMware, Inc. 77




Interfaces Metric Integer Rate of outgoingpackets thatwere dropped onthe interface

Yes


Interfaces Metric Integer Rate of outgoingpackets thatreported an erroron the interface

Yes

Speed Interfaces Metric bps Interfacepublishedmaximumbandwidth.

Yes

Index Interfaces Property String Unique value,greater thanzero, for eachinterface. It isrecommendedthat values areassignedcontiguouslystarting from 1.The value foreach interfacesub-layer mustremain constantat least from onere-initializationof the entity'snetworkmanagementsystem to thenextreinitialization.

Yes

Description Interfaces Property String Textual stringcontaininginformationabout theinterface. Thisstring shouldinclude the nameof themanufacturer,the productname and theversion of theinterfacehardware/software.

Yes

Type Interfaces Property String Interface typeaccording to theIANAIfTypeenum.

Yes


78 VMware, Inc.



MTU Interfaces Property String Size of thelargest packetwhich can besent/received onthe interface,specified inoctets. Forinterfaces thatare used fortransmittingnetworkdatagrams, thisis the size of thelargest networkdatagram thatcan be sent onthe interface.

Yes

Physical Address Interfaces Property String Interface addressat its protocolsub-layer. Forexample, for an802.x interface,this objectnormallycontains a MACaddress. Theinterface media-specific MIBmust define thebit and byteordering and theformat of thevalue of thisobject. Forinterfaces whichdo not have suchan address, forexample, a serialline, this objectshould containan octet string ofzero length.

Yes


VMware, Inc. 79



Admin Status Interfaces Property String Desired state ofthe interface. Thetesting(3) stateindicates that nooperationalpackets can bepassed. When amanaged systeminitializes, allinterfaces startwithifAdminStatus inthe down(2)state. As a resultof either explicitmanagementaction or perconfigurationinformationretained by themanaged system,ifAdminStatus isthen changed toeither the up(1)or testing(3)states (orremains in thedown(2) state).

Yes


80 VMware, Inc.



Operation Status Interfaces Property String Currentoperational stateof the interface.The testing(3)state indicatesthat nooperationalpackets can bepassed. IfifAdminStatus isdown(2) thenifOperStatusshould bedown(2). IfifAdminStatus ischanged to up(1)thenifOperStatusshould change toup(1) if theinterface is readyto transmit andreceive networktraffic; it shouldchange todormant(5) if theinterface iswaiting forexternal actions(such as a serialline waiting foran incomingconnection); itshould remain inthe down(2) stateif and only ifthere is a faultthat prevents itfrom going to theup(1) state; itshould remain inthe notPresent(6)state if theinterface hasmissing(typically,hardware)components.

Yes


VMware, Inc. 81



Last Change Interfaces Property String Value ofsysUpTime atthe time theinterface enteredits currentoperational state.If the currentstate was enteredprior to the lastreinitialization ofthe local networkmanagementsubsystem, thenthis objectcontains a zerovalue.

Yes

IP Addresses Interfaces Property String IP addresses listconfigured onthis interface.

Yes

Total Ingress Interfaces Metric KBps Total amount ofnetwork trafficreceived from allinterfaces

Yes


Yes


Yes


Yes


82 VMware, Inc.

Management Pack for NSX forvSphere Reports 8

A report is a scheduled snapshot of views. The Management Pack for NSX for vSphere provides a variety ofreport templates.

Table 8‑1. NSX for vSphere Report Templates

Name of Report Applies to: Content:

Network Traffic by Firewall Service NSX Edge Firewall Service Lists the total network traffic, numberof connections, and total packet ratecurrently measured for all firewalledge services.

Network Traffic by Host Host System Lists the total network traffic, egressnetwork traffic, and ingress networktraffic currently measured for all hosts.

Network Traffic by IPSec VPN Service NSX Edge IPSec VPN Service Lists the egress and ingress trafficcurrently measured for all IPSec VPNedge services.

Network Traffic by L2 VPN Service NSX Edge L2 VPN Service Lists the egress and ingress trafficcurrently measured for all L2 VPNedge services.

Network Traffic by Load BalancerService

NSX Edge Load Balancer Service Lists the pool and virtual server egressand ingress traffic currently measuredfor all load balancer edge services.

Network Traffic by Logical Switch NSX Logical Switch Lists the egress traffic, ingress traffic,egress packet rate, ingress packet rate,and dropped packet % currentlymeasured for all logical switches.

Network Traffic by NSX Edge NSX Edge Lists the total network traffic, egressnetwork traffic, ingress network traffic,egress packet rate, and ingress packetrate currently measured for all edges

Network Traffic by SSL VPN Service NSX Edge SSL VPN Service Lists the active clients, egress traffic,and ingress traffic currently measuredfor all SSL VPN edge services.

Network Traffic by Transport Zone NSX Transport Zone Lists the total network traffic, egressnetwork traffic, and ingress networktraffic currently measured for alltransport zones.

Network Traffic by VM Virtual Machine Lists the total network traffic, egressnetwork traffic, and ingress networktraffic currently measured for allvirtual machines.

VMware, Inc. 83

Table 8‑1. NSX for vSphere Report Templates (Continued)

Name of Report Applies to: Content:

NSX Edge Service Deployment Trend NSX Edge Provides a trend report of all types ofedge services provisioned in theenvironment.

NSX Edge Services to VMs NSX Edge Number of virtual machines currentlyusing each edge service in theenvironment.

Generate a ReportThe Management Pack for NSX for vSphere provides a list of report templates from which you can generatereports.

Procedure

1 In the left pane of vRealize Operations Manager, click the Environment icon.

2 Select the Management Pack for NSX for vSphere object for which you want to generate the report.

The Report tab is displayed.

3 From the Report tab, select the required report template, and click the Run Template icon.

When the report is complete, the number of generated reports is updated under the name of the reporttemplate.

What to do next

Download the report by clicking Generated Reports. Select the report from the list of reports, and click therequired format in the Download column.


84 VMware, Inc.

Index

Aalert definitions 23

Ccapacity models 29configuring adapters

NSX for vSphere 10physical discovery adapter (experimental) 11

connectivity testsrun a visual path 20VXLAN Tunnel End Point Connectivity 21

Ddashboards

accessing vRealize Operations Managertools 19

displaying 13navigation 19NSX Main 14NSX Topology 15NSX-vSphere Object Path 16NSX-vSphere Troubleshooting 16

Gglossary 5

Iinstalling management packs 9intended audience 5introduction 7

Mmanagement packs, installing 9

Oobjects and metrics 35open an external application

Log Insight 20NSX manager 21vSphere web client 21

Pphysical discovery adapter (experimental)

configure 11run a physical path discovery 22

Rreports

generating 84templates 83

Ttroubleshooting workflow 17

VMware, Inc. 85


86 VMware, Inc.

Date post:	19-Jul-2018
Category:	Documents
Upload:	truongdieu
View:	228 times
Download:	0 times

vRealize Operations Management Pack for NSX for … · The vRealize Operations Management Pack for...

Documents