vRealize Operations Management Pack for NSX for Multi

Transcription

vRealize Operations Management Pack
for NSX for Multi-Hypervisor
This document supports the version of each product listed and
supports all subsequent versions until the document is
replaced by a new edition. To check for more recent editions
of this document, see http://www.vmware.com/support/pubs.
EN-001575-00
vRealize Operations Management Pack for NSX for Multi-Hypervisor
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:
docfeedback@vmware.com
Copyright © 2014 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
2
VMware, Inc.
Contents
About This Book 5
1 Introduction to the
7
2 Installing and Configuring the
Management Pack for NSX for Multi-Hypervisor 9
Install the Management Pack 9
Configure the NSX for Multi-Hypervisor Instance
10
3 Management Pack for NSX for Multi-Hypervisor Dashboards 13
Displaying Management Pack for NSX for Multi-Hypervisor Dashboards 13
NSX-MH Main Dashboard 14
NSX-MH Topology Dashboard 15
NSX-MH Object Path Dashboard 16
4 Working with the Management Pack for NSX for Multi-Hypervisor 17
Dashboard to Dashboard Navigation
Open an External Application 20
18
5 Management Pack for NSX for Multi-Hypervisor Alert Definitions 21
6 Management Pack for NSX for Multi-Hypervisor Capacity Models 29
7 Management Pack for NSX for Multi-Hypervisor Object Models 31
Object Types and Metrics
31
8 Management Pack for NSX for Multi-Hypervisor Reports 49
Generate a Report
Index
VMware, Inc.
50
51
3
4
VMware, Inc.
About This Book
The vRealize Operations Management Pack for NSX for Multi-Hypervisor Guide takes you through the process of
deploying a working instance of the Management Pack for NSX for Multi-Hypervisor within your vCenter
environment.
The vRealize Operations Management Pack for NSX for Multi-Hypervisor Guide also describes how to monitor
the Management Pack for NSX for Multi-Hypervisor environment.
Intended Audience
This information is intended for the following users:
n
Any network engineer, network administrator, network manager, or network operations manager who
is involved with the daily operations related to deployment, configuration, change management,
troubleshooting, and capacity management of VMware NSX for Multi-Hypervisor networking
technologies.
n
Any cloud operations manager, cloud infrastructure manager, or virtual administrator who has
operation responsibility for troubleshooting virtual infrastructure problems, and within this
infrastructure NSX for Multi-Hypervisor has been deployed.
VMware Technical Publications Glossary
VMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For definitions
of terms as they are used in VMware technical documentation, go to
http://www.vmware.com/support/pubs.
VMware, Inc.
5
6
VMware, Inc.
Introduction to the
vRealize Operations Management
Pack for NSX for Multi-Hypervisor
1
The Management Pack for NSX for Multi-Hypervisor extends the operational management capabilities of
the vRealize Operations platform into the areas of virtual and physical data center networking.
This management pack is designed for high level, and drilled down operations visibility, within highly
virtualized networks, whereby the customer has deployed NSX technologies.
The Management Pack for NSX for Multi-Hypervisor provides the following features:
n
Visibility of all deployed NSX networking components, including NSX manager, NSX controllers, NSX
service nodes, and NSX gateways, and logical objects such as logical switches, logical routers, and
gateway service. Several different pre-defined vRealize Operations widgets are leveraged for
representing health of tunnels between transport nodes.
n
Search and drill down functions for obtaining the operations health of deployed NSX objects.
n
Embedded dependency rules of both logical and physical networking relationships for problem alerting
and root-cause problem solving. This includes detection and alerting of NSX configuration,
connectivity, and health problems. All alerts are consolidated into a vRealize Operations Manager alert
interface.
n
Extension of the core vRealize Operations health and risk analytics engine for the inclusion of NSX
object key performance and health indicators.
n
Report templates to generate reports for NSX for Multi-Hypervisor objects.
VMware, Inc.
7
8
VMware, Inc.
Installing and Configuring the
Management Pack for NSX for MultiHypervisor
2
When you install a management pack, you install the PAK file that you downloaded as part of the solution,
and then you configure the management pack instance.
This chapter includes the following topics:
n
“Install the Management Pack,” on page 9
n
“Configure the NSX for Multi-Hypervisor Instance,” on page 10
Install the Management Pack
A 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 your
local 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 NSX for Multi-Hypervisor Instance
After you install the management pack, add and configure an instance for the NSX Manager from which
you are collecting data.
Procedure
1
In the left pane of vRealize Operations Manager, click the Administration icon and click Solutions.
2
Select Management Pack for NSX-MH, and click the Configure icon.
3
Configure the instance settings.
4
10
Option
Description
Display Name
Name for the adapter instance. You can use the host name or IP address of
the NSX manager.
Description
(Optional) Describe the instance.
NSX Controller Host
IP address of the NSX controller from which you are collecting data. You
can specify multiple controllers in a comma-separated list.
NSX Manager Host
IP address of the NSX manager to which you are connecting. The NSX
Manager Host information is used for ports statistics export, and to enable
you to open an object in the NSX Manager.
vCenter Host
IP address of the vCenter Server to which you are connecting. This field is
optional, but useful if you want to see the vCenter host system and virtual
machine resources. Make sure that this host is identical to the vCenter host
system of the vCenter adapter.
Enable Log Insight integration if
configured
If you have vRealize Log Insight configured for use with vRealize
Operations Manager, you can associate log files in Log Insight with
NSX for Multi-Hypervisor alerts, and view logging information for
selected alerts 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 to Log Insight.
Enable logical statistics export
Determines whether NSX for Multi-Hypervisor exports logical port
statistics to the NSX manager. From the drop-down menu, select True to
enable collection of logical port statistics.
To add the credentials used to access the NSX manager and optionally the vCenter server, click the plus
sign.
Option
Description
Credential name
Enter the name by which you are identifying the configured credentials.
Controller User Name
Enter the user name of the controller.
Controller Password
Enter the password of the controller.
vCenter User Name
Enter the user name of the vCenter server.
vCenter Password
Enter the password of the vCenter server.
Manager User Name
Enter the user name of the Manager.
Manager Password
Enter the password of the Manager.
5
Click Test Connection to validate the connection.
6
Accept the NSX Manager and the NSX Controller certificates.
VMware, Inc.
Chapter 2 Installing and Configuring the Management Pack for NSX for Multi-Hypervisor
7
(Optional) The Advanced Settings area includes the Collector drop-down box, in which you can select
the collector upon which you want to run the adapter instance. A collector gathers objects into its
inventory for monitoring. The collector specified by default has been selected for optimal data
collecting.
8
Click Save Settings.
The adapter instance is added to the Management Pack for NSX-MH Solutions Details pane.
What to do next
Verify that the adapter is configured and collecting data by viewing application-related data.
Table 2‑1. Successful Configuration Indicators
Where to View the Information
Information to View
Collection Status and Collection State columns in the
Management Pack for NSX-MH Solutions Details pane on
the Solutions tab
The strings Collecting or Data receiving appear
approximately five minutes after you have configured the
adapter.
Environment Overview
The objects related to NSX for Multi-Hypervisor are added
to the inventory.
Dashboards
Management Pack for NSX for Multi-Hypervisor
dashboards are added to the default vRealize Operations
Manager dashboards.
n NSX-MH Main
n NSX-MH Topology
n NSX-MH Object Path
Click the Home icon on the vRealize Operations Manager
menu to view dashboards.
VMware, Inc.
11
12
VMware, Inc.
Management Pack for NSX for MultiHypervisor Dashboards
3
The Management Pack for NSX for Multi-Hypervisor dashboards enable you to monitor and troubleshoot
problems in your logical and physical network.
For information about how to configure the options on the dashboard widgets, see the
vRealize Operations Manager documentation, at https://www.vmware.com/support/pubs/.
n
“Displaying Management Pack for NSX for Multi-Hypervisor Dashboards,” on page 13
n
“NSX-MH Main Dashboard,” on page 14
n
“NSX-MH Topology Dashboard,” on page 15
n
“NSX-MH Object Path Dashboard,” on page 16
Displaying Management Pack for NSX for Multi-Hypervisor
Dashboards
Management Pack for NSX for Multi-Hypervisor dashboards are displayed in the
vRealize Operations Manager Home pane after the management pack is installed. If you have numerous
dashboards open in vRealize Operations Manager, the NSX for Multi-Hypervisor 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, from the drop-down menu point to NSX-MH, and select the
NSX for Multi-Hypervisor dashboard you want to work with.
The selected dashboard is displayed in the vRealize Operations Manager Home page.
3
VMware, Inc.
To ensure that Management Pack for NSX for Multi-Hypervisor dashboards are always available in the
Home page, click Dashboard List, and ensure that the NSX-MH check box is selected.
13
NSX-MH Main Dashboard
The NSX-MH Main dashboard provides an overview of the health of the various network objects. This
dashboard enables you to view network traffic information and NSX-related open alerts.
Table 3‑1. NSX-MH Main Dashboard Widgets
Widget
Description
NSX-MH Environments
Displays a list of the environments that you are currently
monitoring. Select an environment to show detailed
information about the environment in the dashboard.
Key NSX-MH Components
Displays a top level view of the following key components:
NSX-MH Controller: Responsible for managing the
switching and routing modules in the hypervisors.
Supports an ARP suppression mechanism that reduces
the need to flood ARP broadcast requests across the L2
and L3 network domains.
n NSX-MH Gateway: A physical x86 appliance that runs
Open vSwitch (OVS) and connects logical networks to
the data center's physical network or to physical
applications (nonvirtualized applications like a large
database server, for example). Gateway functionality is
similar to that of a virtual private network: logical
network traffic is tunneled to the Gateway, which
decapsulates the traffic and sends it via a network
interface card (NIC) to a directly attached physical
network (and conversely the Gateway encapsulates
incoming traffic entering the logical network). For
example, a Gateway can provide access to a physical
upstream router that is connected to the Internet, or
the Gateway can reside in a remote customer premises,
enabling a cloud customer to seamlessly link their
physical and cloud networks. Logical switches and
logical routers attach to Gateways via the Gateway
Service construct in NSX. The Gateway Service may
contain only one Gateway, or, if high availability is a
requirement, the Gateway Service will include
multiple Gateways.
n NSX-MH Service Node: Physical x86 appliances that
run Open vSwitch (OVS) and play an important role in
logical switching because they take care of distributing
multi-destination traffic (such as L2 broadcast and
multicast) belonging to a specific logical switch to all
the transport nodes where that logical switch is
currently active.
The Key NSX Component widget provides badges that use
scores to determine the condition of a component in a
specific area such as CPU, memory, disk and bandwidth.
Each badge issues a score through a colored icon that is
based on pre-defined badge score thresholds.
Point to a component to view a summary of the
information provided by each badge.
Click a component to open it in the Control Plane where
you can manage and configure its health, view open alerts,
and more.
n
14
VMware, Inc.
Chapter 3 Management Pack for NSX for Multi-Hypervisor Dashboards
Table 3‑1. NSX-MH Main Dashboard Widgets (Continued)
Widget
Description
NSX-MH Objects
Lists all the objects in the selected environment, and
enables you to search for an object. Use the NSX-MH
Objects widget to select an object, and navigate to the NSXMH Topology dashboard to view the physical and logical
topologies of the object. You can also navigate to the NSXMH Object Path dashboard to see how the selected object
is connected to another object.
Open Alerts
Displays all the alerts open in the selected environment.
Transport Layer
Displays a heatmap that shows the health of each transport
node. Transport nodes are ESX hosts, non-ESX hosts,
gateways and service nodes. You can view the health,
workload, and network workload for ESX Host, Gateway,
Service Node, and Non-ESX Host components by selecting
the required option from the Configurations drop-down
menu.
Top Logical Networks By Traffic (KBps)
Lists the top logical switches in the environment that are
currently experiencing the most traffic network.
Top Virtual Interfaces and VMs by Traffic (KBps)
Lists the top virtual machines in the environment that are
currently responsible for the most network traffic.
NSX-MH Topology Dashboard
The NSX-MH 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-MH Topology dashboard directly from the menu bar, the Logical Topology widget
and the Physical Topology widget will not display data. To display data, in the Objects widget, click the
object for which you want to display details. You can also locate an object by searching for it in the Search
box on the right side of the Objects widget.
This dashboard includes the following widgets:
Table 3‑2. NSX-MH Topology Dashboard
Widget
Description
NSX-MH Environments
Displays a list of all the environments that you are
currently monitoring. When you select an environment in
this widget, the other widgets in the NSX-MH Topology
dashboard show data for the selected environment.
Objects
Lists all the objects in the selected environment, and
enables you to search for a specific object. Select an object
and view the physical and logical topologies of that object.
You can also navigate to the Object Path dashboard to see
how the selected object is connected to another object.
Logical Topology
Provides a visual display for how the selected object is
connected to the logical network. Use this widget to
navigate around the network by clicking any of the objects
in the view. The view in the Physical Topology, Top issues,
and Metrics widgets is updated accordingly.
Point to an object to view additional information such as
the name of the object, the object type and additional
configuration properties.
To display an extended view that includes other connected
objects, right-click an object, select Expand Node, and
select the objects you want to include in the expanded
view.
VMware, Inc.
15
Table 3‑2. NSX-MH Topology Dashboard (Continued)
Widget
Description
Physical Topology
Provides a visual display for how an object fits within the
physical network. Click an object in this widget to display
related alerts and metrics.
When a transport node is selected in the Physical Topology
widget, tunnels between this node and other transport
nodes (only gateways and service nodes) are shown.
Tunnels to hypervisors are not shown. The color of the
tunnel represents its health.
Point to an object to view additional information such as
the name of the object, the object type and additional
configuration properties.
To display an extended view that includes other connected
objects, right-click an object, select Expand Node, and
select the objects you want to include in the expanded
view.
Top Issues
Displays open alerts for the object selected in the Physical
Topology widget and the Logical Topology widget.
Metrics
Displays a set of pre-configured metrics for the object
selected in the Physical Topology widget and the Logical
Topology widget.
NSX-MH Object Path Dashboard
The NSX-MH Object Path dashboard enables you to run a visual path between two selected objects, and see
how they are connected to each other, and to other objects in the environment. The resulting visual path
enables you to detect possible connectivity problems.
For information about how to run a visual path between two objects, see “Detect Configuration Problems
Between Two Objects,” on page 19.
Table 3‑3. NSX-MH Object Path Dashboard Widgets
16
Widget
Description
NSX-MH Environments
Displays a list of the NSX for Multi-Hypervisor
environments that you are currently monitoring.
Objects
Displays a list of objects in the selected environment.
Logical Path
Provides a visual display for how the selected objects are
connected to the logical network.
Physical Path
Provides a visual display for how the selected objects are
connected to the physical infrastructure.
VMware, Inc.
Working with the Management Pack
for NSX for Multi-Hypervisor
4
The Management Pack for NSX for Multi-Hypervisor provides you with a high level view of your
NSX for Multi-Hypervisor environment and enables you to drill down to more object-specific information
by navigating from one dashboard to another, and also by opening selected objects in external applications.
You can investigate problems and better analyze the provided information. You can also make
configuration changes, as required.
VMware, Inc.
17
Table 4‑1. Detect Configuration Problems Workflow
Do This
n
n
Navigate from one
NSX for Multi-Hypervisor
dashboard to another.
Access
vRealize Operations Manager
tools.
To
Example of Use
Display object-specific information in
more detail.
n
n
n
Open an object in an external
application. The
Management Pack for NSX for MultiHypervisor supports the following
applications:
1 NSX Manager
2 vRealize Log Insight
n
n
Display additional information
about an object that you cannot
get from
vRealize Operations Manager.
Make configuration changes, if
required.
1
2
If an object has an alert opened in
the NSX-MH Main dashboard, and
you want to visualize how that
object is connected in the logical
and physical networks, select the
object in the NSX-MH Main
dashboard and navigate to the
NSX-MH Topology dashboard.
If, after discovering the logical and
physical paths of the object, you
require more detail, identify an
object, for example, a host, and
navigate to the NSX-MH Object
Path dashboard where you can
select another host, and load a
view of the path between the two
hosts. This visual path enables you
to detect connectivity problems
between the two hosts.
To display
vRealize Operations Manager tabs
that help you monitor and respond
to problems, double-click an object
or alert.
When an alert is opened on an
NSX for Multi-Hypervisor object,
open the object in Log Insight to
see the NSX logs that are
associated with the time of the
alerts.
If an alert that is opened on a
Gateway Service notifies you that
the Gateway Service is not highly
available, open the Gateway
Service in NSX Manager so that
you can configure the Gateway
Service and make it highly
available.
n
“Dashboard to Dashboard Navigation,” on page 18
n
“Open an External Application,” on page 20
Dashboard to Dashboard Navigation
Dashboard navigation enables you to navigate from one NSX for Multi-Hypervisor dashboard to another
and view related information for a selected object. This enables you to detect configuration problems in your
environment.
A typical problem-solving workflow starts with a top-level view of your environment in the NSX-MH Main
dashboard. If you detect a problem in your environment, drill-down to view more object-specific
information. Navigate first to the NSX-MH Topology dashboard, to view the logical and physical networks.
If you require more detailed information, navigate to the NSX-MH Object Path dashboard where you can
select another object of the same type and see if there are any connectivity problems on the path between the
two objects.
18
VMware, Inc.
Chapter 4 Working with the Management Pack for NSX for Multi-Hypervisor
Access vRealize Operations Manager Tools
In addition to troubleshooting problems by navigating between NSX for Multi-Hypervisor dashboards, you
can also access the vRealize Operations Manager tools. For example, if you double-click an object or alert in
a NSX for Multi-Hypervisor dashboard, you display tabs that help you monitor and respond to problems.
Most useful is the Troubleshooting tab from which you can access the All Metrics tab which provides a
topological map and metrics for the selected object.
Dashboard Navigation
Use dashboard navigation to navigate from one NSX for Multi-Hypervisor dashboard to another and
display dashboard-specific information for a selected object. This provides a more detailed view if you are
experiencing problems in your environment.
You can navigate from any widget where the Dashboard Navigation icon is available, and between the
NSX-MH Main dashboard, the NSX-MH Topology dashboard, and the NSX-MH Object Path dashboard in
any order.
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-MH Topology dashboard, navigate to the
NSX-MH Object Path dashboard where you can select an object of the same type, and see if there are any
connectivity issues between the two objects.
Detect Configuration Problems Between Two Objects
If you detect a problem with an object, and want to visualize the path between the object and another object
of the same type, navigate to the NSX-MH Object Path dashboard where you can create a visual path
between the objects, and locate possible connectivity problems.
You can create a visual path between two virtual machines, two hosts, or two logical switches.
This action is run in the NSX-MH Object Path dashboard.
Procedure
1
Select the NSX-MH Object Path dashboard.
2
In the NSX-MH Environments widget, select the environment to monitor.
3
In the Objects widget, search for the object by name or type.
4
In the list of objects, select an object.
5
In the list of objects, 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 in
the NSX-MH Topology dashboard, select the object, navigate to the NSX-MH Object Path dashboard, and
then select another object to view the path.
VMware, Inc.
19
Open an External Application
The Management Pack for NSX for Multi-Hypervisor includes the ability to link to another application for
information about an object. Open an object in another application if you need to display information that
you cannot get from vRealize Operations Manager, or when you need to make configuration changes.
The Management Pack for NSX for Multi-Hypervisor enables you to access more information about specific
objects and configure them if required in NSX Manager, and view logging information in Log Insight.
Open Log Insight
If you have Log Insight configured with vRealize Operations Manager, you can view logging information
for specific NSX for Multi-Hypervisor objects and alerts. When you configure Log Insight with the
Management Pack for NSX for Multi-Hypervisor, 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 and
Enable Launch in Context checkboxes are selected. 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 Multi-Hypervisor. For more
information about Log Insight integration with the Management Pack for NSX for Multi-Hypervisor,
see “Configure the NSX for Multi-Hypervisor Instance,” on page 10.
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.
The select object or alert is opened in Log Insight.
NOTE Syslogs for all controllers and managers are forwarded to the Log Insight server. If you want to
forward ovs logs, you need to forward the syslog from each Non-ESX hypervisor node. This action is
dependent on the operating system and on the syslog forwarding software and version, but can be done by
setting the forwarding host in /etc/rsyslog.d/50-default.conf by appending the forwarding information
of the last line of the file.
# tail -1/etc/rsyslog.d/50-default.conf
*.*@@<li-hostname>:514
# service rsyslog restart
Open NSX Manager
If you cannot solve a problem in vRealize Operations Manager, or if you require extended monitoring
capabilities, open select objects in NSX Manager to see the complete configuration of the object.
You can open Gateways, hypervisors, and switches in NSX Manager.
Procedure
1
Select a gateway, hypervisor, or switch in a widget.
2
In the widget toolbar, click Dashboard Navigation, and select View in NSX Manager.
The object is opened in NSX Manager.
20
VMware, Inc.
5
Management Pack for NSX for MultiHypervisor Alert Definitions
Management Pack for NSX for Multi-Hypervisor alert definitions are a combination of symptoms and
recommendations that identify problem areas in your environment and generate alerts on which you can act
for those areas.
Table 5‑1. Management Pack for NSX for Multi-Hypervisor Alert Definitions
Alert Name
Object Type
Impact
Severity
Symptom
Gateway Service is not
highly available
Gateway Service
Risk
Immediate
Self metric: Gateway|
Registered count = 1
L3 Gateway Service
contains multiple
Gateways all
configured in the same
failure zone
Gateway Service
Risk
Immediate
Fault: L3 Gateway
Service contains
multiple Gateways all
configured in the same
failure zone
Gateway physical
interface is down
Gateway
Health
Critical
n
n
Self metric:
Physical Interface|
Link Status =
down AND
Self metric:
Physical Interface
|Admin Status =
enabled
Gateway physical
interface is disabled
Gateway
Health
Warning
Self metric; Physical
Interface|Admin
Status = disabled
Gateway tunnel
interface is down
Gateway
Health
Critical
n
n
Self metric: Tunnel
Interface|
Transmit Status =
down
Self metric: Tunnel
Interface|Receive
Status = down
Gateway OVS process
restarted
Gateway
Health
Warning
Self metric:Process|
Restarts > 0
Gateway is not
communicating with a
Controller
Gateway
Health
Immediate
Self metric: Status|
Status = disconnected
VMware, Inc.
21
Table 5‑1. Management Pack for NSX for Multi-Hypervisor Alert Definitions (Continued)
Alert Name
Object Type
Impact
Severity
Symptom
Gateway resource
usage is higher than
normal
Gateway
Health
Warning
n
n
n
n
n
No syslog server is
configured
Gateway
Risk
Warning
Gateway syslog server
is not defined
Hypervisor physical
interface is down
Hypervisor
Health
Critical
n
n
Hypervisor tunnel
interface is down
Hypervisor
Health
Critical
n
n
22
Self metric: CPU|
Usage is above the
dynamic threshold
Self metric:
Memory|Usage is
above the
dynamic threshold
Self metric:
Filesystem|Usage
is above the
dynamic threshold
Self metric:
Physical interface|
Transmitted
packets is above
the dynamic
threshold
Self metric:
Physical interface|
Received packets
is above the
dynamic threshold
Self metric:
Physical Interface|
Link Status =
down AND
Self metric:
Physical Interface|
Admin Status =
enabled
Self metric: Tunnel
Interface|
Transmit Status =
down
Self metric: Tunnel
Interface|Receive
Status = down
Hypervisor OVS
process restarted
Hypervisor
Health
Warning
Self metric: Process|
Restarts > 0
Hypervisor is not
Controller
Hypervisor
Health
Immediate
VMware, Inc.
Chapter 5 Management Pack for NSX for Multi-Hypervisor Alert Definitions
Alert Name
Object Type
Impact
Severity
Symptom
Hypervisor resource
normal
Hypervisor
Health
Warning
n
n
n
n
n
Service Node physical
interface is down
Service Node
Health
Critical
n
n
Self metric: CPU|
Usage is above the
dynamic threshold
Self metric:
Memory|Usage is
above the
dynamic threshold
Self metric:
Filesystem|Usage
is above the
dynamic threshold
Self metric:
Physical interface|
Transmitted
packets is above
the dynamic
threshold
Self metric:
Physical interface|
Received packets
is above the
dynamic threshold
Self metric:
Physical Interface|
Link Status =
down AND
Self metric:
Physical Interface|
Admin Status =
enabled
interface is disabled
Service Node
Health
Warning
interface admin status
is disabled
Service Node tunnel
interface is down
Service Node
Health
Critical
n
n
Self metric: Tunnel
Interface|
Transmit Status =
down
Self metric: Tunnel
Interface|Receive
Status = down
Service Node OVS
process restarted
Service Node
Health
Warning
Self metric: Process|
Restarts > 0
Service Node is not
Controller
Service Node
Health
Immediate
VMware, Inc.
23
Alert Name
Object Type
Impact
Severity
Symptom
Service Node resource
normal
Service Node
Health
Warning
n
n
n
n
n
No syslog server is
configured
Service Node
Risk
Warning
Service Node syslog
server is not defined
Logical Router fabric
status is down
Logical Router
Health
Critical
Fabric Status = down
Logical Router is
centralized and has no
L3 Gateway
attachment
Logical Router
Health
Critical
Fault: Logical Router
is centralized and has
no L3 Gateway
attachment
Logical Switch port
fabric status is down
Logical Switch
Health
Critical
n
n
24
Self metric: CPU|
Usage is above the
dynamic threshold
Self metric:
Memory|Usage is
above the
dynamic threshold
Self metric:
Filesystem|Usage
is above the
dynamic threshold
Self metric:
Physical interface|
Transmitted
packets is above
the dynamic
threshold
Self metric:
Physical interface|
Received packets
is above the
dynamic threshold
Self metric: Port|
Fabric Status =
down
Self metric: Port|
Link Status =
down
VMware, Inc.
Alert Name
Object Type
Impact
Severity
Symptom
Transport node
tunnels are down
Transport Zone
Health
Critical
n
n
VMware, Inc.
> 10% of all
gateways and
service nodes:
n Child
(Gateway)
Metric: Tunnel
Interface|
Transmit
Status = down
n Child
(Gateway)
Metric: Tunnel
Interface|
Receive Status
= down
n Child (Service
Node) Metric:
Tunnel
Interface|
Transmit
Status = down
n Child (Service
Node) Metric:
Tunnel
Interface|
Receive Status
= down
> 25% of all
hypervisors:
n Child
(Hypervisor)
Metric: Tunnel
Interface|
Transmit
Status = down
n Child
(Hypervisor)
Metric: Tunnel
Interface|
Receive Status
= down
25
Alert Name
Object Type
Impact
Severity
Symptom
Transport node
physical interfaces are
down
Transport Zone
Health
Critical
n
> 10% of all
gateways and
service nodes:
n Child
(Gateway)
metric:
Physical
Interface|Link
Status = down
AND
n
Physical
Interface|
Admin Status
= enabled
Child (Service
Node) metric:
Physical
Interface|Link
Status = down
AND
n
Physical
Interface|
Admin Status
= enabled
> 25% of all
hypervisors:
n Child
(Hypervisor)
metric:
Physical
Interface|Link
Status = down
AND
Physical
Interface|
Admin Status
= enabled
26
VMware, Inc.
Alert Name
Object Type
Impact
Severity
Symptom
Multiple physical
interfaces in the
Transport Zone are
disabled
Transport Zone
Health
Warning
n
n
n
> 10% of all
gateways:
n Child
(Gateway)
Metric:
Physical
Interface|
Admin Status
= disabled
> 10% of all
service node:
n Child (Service
Node) Metric:
Physical
Interface|
Admin Status
= disabled
> 25% of all
hypervisors:
n Child
(Hypervisor)
Metric:
Physical
Interface|
Admin Status
= disabled
Transport Zone
contains a single
Service Node
Transport Zone
Risk
Immediate
Self metric: Transport
Node|Active service
node count = 1
Controller is down
Controller
Health
Critical
Status=disconnected
Controller resource
normal
Controller
Health
Warning
n
n
n
n
n
Controller is in
maintenance mode
VMware, Inc.
Controller
Health
Warning
Self metric: CPU|
Usage is above the
dynamic threshold
Self metric:
Memory|Usage is
above the
dynamic threshold
Self metric:
Filesystem|Usage
is above the
dynamic threshold
Self metric:
Physical interface|
Transmitted
packets is above
the dynamic
threshold
Self metric:
Physical interface|
Received packets
is above the
dynamic threshold
Maintenance mode
=pending
27
28
Alert Name
Object Type
Impact
Severity
Symptom
No syslog server is
configured
Controller
Risk
Warning
Controller syslog
server is not defined
Controllers are
running different
versions of NSX
This alert definition
will be supported in
NSX-MH version 4.2.2
Controller Cluster
Risk
Warning
Controller versions are
mismatched
Active Controllers
percentage below hard
threshold
Controller Cluster
Health
Critical
Self metric: Control
node|Active (%) < 50
Controller Cluster is
not stable
Controller Cluster
Health
Immediate
Status != stable
API call rate is higher
than normal
Controller Cluster
Risk
Immediate
Controller Cluster API
call rate is exceeding
the dynamic threshold
API response time is
higher than normal
Controller Cluster
Health
Warning
Controller Cluster API
response time is
exceeding the
dynamic threshold
API calls are failing
Controller Cluster
Health
Critical
API error rate is
exceeding the hard
threshold
Security Rules are
exceeding capacity
NSX Environment
Health
Warning
Security Rule count is
exceeding the hard
threshold
API calls to vCenter
are failing
NSX Environment
Health
Critical
Self metric: Status|VC
connection =
disconnected
VMware, Inc.
Management Pack for NSX for MultiHypervisor Capacity Models
6
An object's capacity model, combined with policy settings, is used to determine the value of all badges and
sub-badges aside from Health. The Management Pack for NSX for Multi-Hypervisor Capacity model tables
describe the capacity models that have been defined for each object type.
Control Cluster
Table 6‑1. Control Cluster Capacity Model
Container
Description
Use in Workload
CPU
Yes
Filesystem
Yes
Memory
Yes
Swap
No
Control Node
Table 6‑2. Control Node Capacity Model
Container
Description
Use in Workload
CPU
Yes
Filesystem
Yes
Memory
Yes
Swap
No
Hypervisor Gateway
Table 6‑3. Hypervisor Gateway Capacity Model
Container
Description
Use in Workload
CPU
Yes
Filesystem
Yes
Memory
Yes
Swap
Yes
Physical Interface/Ingress Traffic
Yes
Physical Interface/Egress Traffic
Yes
VMware, Inc.
29
Table 6‑3. Hypervisor Gateway Capacity Model (Continued)
Container
Description
Use in Workload
Physical Interface/Ingress Packets
Yes
Physical Interface/Egress Packets
Yes
Logical Queue
Yes
Service Node
Table 6‑4. Service Node Capacity Model
Container
Description
Use in Workload
CPU
Yes
Filesystem
Yes
Memory
Yes
Swap
Yes
Ingress Traffic
Yes
Egress Traffic
Yes
Physical Interface/Ingress Traffic
Yes
Physical Interface/Egress Traffic
Yes
Physical Interface/Ingress Packets
Yes
Physical Interface/Egress Packets
Yes
Capacity models have not been defined for the following objects:
30
n
Gateway Service
n
Virtual Interface
n
Logical Switch
n
Logical Router
VMware, Inc.
7
Management Pack for NSX for MultiHypervisor Object Models
Object Types and Metrics
NSX for Multi-Hypervisor Controller Cluster
Table 7‑1. NSX for Multi-Hypervisor Controller Cluster Metrics
Name
Category
Type
Unit
Description
Instanced
Status
Status
Metric
String
Status of the
cluster.
No
Registered Count
Transport Zone
Metric
Integer
Number of
transport zones
in the cluster.
No
Active Count
Transport Zone
Metric
Integer
Number of
transport zones
in the cluster that
are currently in
an active state.
No
Active
Transport Zone
Metric
%
Percentage of
transport zones
in the cluster that
are currently in
an active state.
No
Errors
Transport Zone
Metric
Integer
Number of
transport zone
errors in the
cluster.
No
Registered Count
Transport Node
Metric
Integer
Number of
transport nodes
in the cluster.
No
Active Count
Transport Node
Metric
Integer
Number of
transport nodes
in the cluster that
are currently in
an active state.
No
Active
Transport Node
Metric
%
Percentage of
transport nodes
in the cluster that
are currently in
an active state.
No
VMware, Inc.
31
Table 7‑1. NSX for Multi-Hypervisor Controller Cluster Metrics (Continued)
32
Name
Category
Type
Unit
Description
Instanced
Errors
Transport Node
Metric
Integer
Number of
transport node
errors in the
cluster.
No
Registered Count
Control Node
Metric
integer
Number of
controllers in the
cluster.
no
Active Count
Control Node
Metric
Integer
Number of
controllers in the
cluster that are
currently in an
active state.
No
Active
Control Node
Metric
%
Percentage of
controllers in the
cluster that are
currently in an
active state.
No
Demand Average
CPU
Metric
Cores
Amount of
processing
power
demanded by all
NSX for MultiHypervisor
Controllers in the
cluster.
No
Usage Average
CPU
Metric
Cores
Amount of
processing
power currenlty
being used by all
NSX for MultiHypervisors
Controllers in the
cluster.
No
Usage
CPU
Metric
%
Percentage of
allocated
processing
power currently
being used by all
Controllers in the
cluster.
No
Capacity
Provisioned
CPU
Metric
Cores
Amount of
processing
power allocated
to all NSX for
MultiHypervisor
Controllers in the
cluster.
No
VMware, Inc.
Chapter 7 Management Pack for NSX for Multi-Hypervisor Object Models
Name
Category
Type
Unit
Description
Instanced
Memory Usage
Process
Metric
KiB
Amount of
memory
currently beings
used by
processes on all
Controllers in the
cluster.
No
Capacity
Provisioned
Filesystem
Metric
KiB
Amount of disk
space allocated
to all NSX-MH
Controllers in the
cluster.
No
Usage
FileSystem
Metric
KiB
Amount of disk
space currenlty
being used by all
Controllers in the
cluster.
No
Usage (%)
Filesystem
Metric
%
Percentage of
allocated disk
space currently
beings used by
all NSX for
MultiHypervisor
Controllers in the
cluster.
No
Capacity
Provisioned
Memory
Metric
kib
Amount of
memory
allocated to all
Controllers in the
cluster.
Usage
Memory
Metric
KiB
Amount of disk
space currently
being used by all
Controllers in the
cluster.
No
Usage %
Memory
Metric
%
Percentage of
memory power
curently being
used by all NSX
for MultiHypervisor
controllers in the
cluster.
No
VMware, Inc.
33
34
Name
Category
Type
Unit
Description
Instanced
Cache
Memory
Metric
KiB
Amount of cache
memory
currently beings
used by all NSX
for MultiHypervisor
controllers in the
cluster.
No
Capacity
Provisioned
Swap
Metric
KiB
Amount of swap
memory
allocated to all
Controllers in the
cluster.
No
Usage
Swap
Metric
KiB
Amount of swap
memory
currently being
used by all NSX
for MultiHypervisor
Controllers in the
cluster.
No
Usage (%)
Swap
Metric
%
Percentage of
swap memory
power currently
beings used by
all NSX for
MultiHypervisor
Controllers in the
cluster.
No
Usage Increase
Rate
Swap
Metric
KiB/S
Rate of swap
memory usage
increase - used
by all NSX for
MultiHypervisor
Controllers in the
cluster.
No
VMware, Inc.
NSX for Multi-Hypervisor Controller
Table 7‑2.
Name
Category
Type
Unit
Description
Instanced
Status
Status
Metric
String
Specifies
whether or not
Controller is
currently
available and
active.
No
Management
Listen Address
Status
Property
String
Management
Listen IP
Address of
Controller.
No
Maintenance
Mode
Status
Metric
String
Specifies
whether or not
Controller is
currently in
maintenance
mode.
No
Version
Status
Property
String
Software version
of
Controller
No
Demand Average
CPU
Metric
Cores
Amount of
processing
power
demanded by
Controller.
No
Usage Average
CPU
Metric
Cores
Amount of
processing
power currently
being used by
Controller.
No
Usage
CPU
Metric
%
Percentage of
allocated
processing
power currently
being used by
Controller.
No
VMware, Inc.
35
Table 7‑2. (Continued)
36
Name
Category
Type
Unit
Description
Instanced
Capacity
Provisioned
CPU
Metric
Cores
Amount of
processing
power allocated
to
Controller.
No
Memory Usage
Process
Metric
KiB
Amount of
memory
currently being
used by all
processes of
Controller.
No
Instances
Process
Metric
KiB
Number of
processes on
Controller.
No
Capacity
Provisioned
Filesystem
Metric
KiB
Amount of disk
space allocated
to
Controller.
No
Usage
Filesystem
Metric
KiB
Amount of disk
space currently
being used by
Controller.
No
Usage (%)
Filesystem
Metric
%
Percentage of
allocated disk
space currently
being used by
Controller.
No
Capacity
Provisioned
Memory
Metric
KiB
Amount of
memory
allocated to
Controller.
No
Usage
Memory
Metric
KiB
Amount of
memory
currently being
used by
Controller.
No
VMware, Inc.
Table 7‑2. (Continued)
Name
Category
Type
Unit
Description
Instanced
Usage (%)
Memory
Metric
%
Percentage of
memory power
currently being
used by
Controller.
No
Cache
Memory
Metric
KiB
Amount of cache
memory
currently being
used by
Controller.
No
Capacity
Provisioned
Swap
Metric
KiB
Amount of swap
memory
allocated to
Controller.
No
Usage
Swap
Metric
KiB
Amount of swap
memory
currently being
used by
Controller.
No
Usage (%)
Swap
Metric
%
Percentage of
swap memory
power currently
being used by
Controller.
No
Usage Increase
Rate
Swap
Metric
KiB/s
Rate of swap
memory usage
increase - used
by
Controller.
No
VMware, Inc.
37
NSX for Multi-Hypervisor Transport Zone
Table 7‑3. NSX for Multi-Hypervisor Transport Zone Metrics
38
Name
Category
Type
Unit
Description
Instanced
Registered Count
Transport Node
Metric
Integer
Number of
transport nodes
in the transport
zone.
No
Active Count
Transport Node
Metric
Integer
Number of
transport nodes
in the transport
zone that are
currently in an
active state.
No
Active (%)
Transport Node
Metric
%
Percentage of
transport nodes
in the transport
zone that are
currently in an
active state.
No
Active Service
Nodes Count
Transport Node
Metric
Integer
Number of
service nodes in
the transport
zone that are
currently in an
active state.
No
Registered Count
Logical Switch
Metric
Integer
Number of
logical switches
in the transport
zone.
No
Active Count
Logical Switch
Metric
Integer
Number of
logical switches
in the transport
zone that are
currently in an
active state.
No
Active (%)
Logical Switch
Metric
%
Percentage of
logical switches
in the transport
zone that are
currently in an
active state.
No
Replication Mode
Service Nodes
Count
Logical Switch
Metric
Integer
Number of
logical switches
in the transport
zone that are
configured in
replication
mode.
No
VMware, Inc.
NSX for Multi-Hypervisor Logical Switch
Table 7‑4. NSX for Multi-Hypervisor Logical Switch Metrics
Name
Category
Type
Unit
Description
Instanced
Fabric Status
Status
Metric
String
Fabric status of
the logical
switch.
No
Egress Packets per
second
Port
Metric
Packets
Rate of outgoing
packets from the
logical switch
port.
Yes
Egress Traffic
Port
Metric
KiBs
Outgoing
network traffic
from the logical
switch port.
Yes
Ingress Packets
per second
Port
Metric
Packets
Rate of incoming
packets into the
logical switch
port.
Yes
Ingress Traffic
Port
Metric
KiBs
Incoming
network traffic
into the logical
switch port.
Yes
Link Status
Port
Metric
String
Link status of the
logical switch
port.
Yes
Fabric Status
Port
Metric
String
Fabric status of
the logical switch
port.
Yes
Admin Status
Port
Metric
String
Admin status of
the logical switch
port.
Yes
Registered Count
Port
Metric
Integer
Number of ports
in the logical
switch.
No
Link Up Count
Port
Metric
Integer
Number of ports
in the logical
switch with a
link state of Up.
No
Link Up (%)
Port
Metric
%
Percentage of
ports in the
logical switch
with a link state
of Up.
No
Fabric Up Count
Port
Metric
Integer
Number of ports
in the logical
switch with a
fabric state of
Up.
No
Fabric Up (%)
Port
Metric
%
Percentage of
ports in the
logical switch
with a fabric
state of Up.
No
VMware, Inc.
39
Table 7‑4. NSX for Multi-Hypervisor Logical Switch Metrics (Continued)
Name
Category
Type
Unit
Description
Instanced
Admin Enabled
Count
Port
Metric
Integer
Number of ports
in the logical
switch with an
admin state of
Enabled
No
Admin Enabled
(%)
Port
Metric
%
Percentage of
ports in the
logical switch
with an admin
state of Enabled
No
Throughput
Port
Metric
KiBs
Total network
traffic across all
virtual machines
attached to
Logical Switch.
No
NSX for Multi-Hypervisor Logical Router
Table 7‑5. NSX for Multi-Hypervisor Logical Router Metrics
40
Name
Category
Type
Unit
Description
Instanced
Fabric Status
Status
Metric
String
Fabric status of
the logical
router.
No
Distributed
Status
Property
String
Specifies
whether the
router is
distributed or
centralized.
Yes
Egress Packets per
second
Port
Metric
Packets
Rate of outgoing
packets from the
logical router
port.
Yes
Egress Traffic
Port
Metric
KiBs
Outgoing
network traffic
from the logical
router port.
Yes
Ingress Packets
per second
Port
Metric
Packets
Rate of incoming
packets into the
logical router
port.
Yes
Ingress Traffic
Port
Metric
KiBs
Incoming
network traffic
into the logical
router port.
Yes
Link Status
Port
Metric
String
Link status of the
logical router
port.
Yes
Admin Status
Port
Metric
String
Admin status of
the logical router
port.
Yes
VMware, Inc.
Table 7‑5. NSX for Multi-Hypervisor Logical Router Metrics (Continued)
Name
Category
Type
Unit
Description
Instanced
Registered Count
Port
Metric
Integer
Number of ports
in the logical
router.
No
Link Up Count
Port
Metric
Integer
Number of ports
in the logical
router with a link
state of Up.
No
Link Up (%)
Port
Metric
%
Percentage of
ports in the
logical router
with a link state
of Up.
No
Admin Enabled
Count
Port
Metric
Integer
Number of ports
in the logical
router with an
admin state of
Enabled.
No
Admin Enabled
(%)
Port
Metric
%
Percentage of
ports in the
logical router
with an admin
state of Enabled.
No
NSX for Multi-Hypervisor Gateway Service
Table 7‑6. NSX for Multi-Hypervisor Gateway Service Metrics
Name
Category
Type
Unit
Description
Instanced
Type
Status
Property
String
Type of gateway
service (L2 or
L3).
No
Registered Count
Gateway
Metric
Integer
Number of
gateways in the
gateway service.
No
Active Count
Gateway
Metric
Integer
Number of
gateways in the
gateway service
that are currently
in an active state.
No
Active
Gateway
Metric
%
Percentage of
gateways in the
gateway service
that are currently
in an active state.
No
VMware, Inc.
41
NSX for Multi-Hypervisor Transport Node
Table 7‑7. NSX for Multi-Hypervisor Transport Node Metrics
42
Name
Category
Type
Unit
Description
Instanced
Admin Status
Status
Metric
String
Admin status of
the transport
node.
No
Status
Status
Metric
String
Specifies
whether or not
the transport
node is currently
available and
active.
No
Management
Listen Address
Status
Property
String
Management
Listen IP
Address of the
transport node.
No
Demand Average
CPU
Metric
Cores
Amount of
processing
power
demanded by
the transport
node.
No
Usage Average
CPU
Metric
Cores
Amount of
processing
power currently
being used by
transport node.
No
Usage
CPU
Metric
%
Percentage of
allocated
processing
power currently
being used by
the transport
node.
No
Capacity
Provisioned
CPU
Metric
Cores
Amount of
processing
power allocated
to the transport
node.
No
Memory Usage
Process
Metric
KiB
Amount of
memory
currently being
used by all
processes of the
transport node.
No
Restarts
Process
Metric
KiB
Number of
processes on the
transport node.
No
Capacity
Provisioned
Filesystem
Metric
KiB
Amount of disk
space allocated
to the transport
node.
No
VMware, Inc.
Table 7‑7. NSX for Multi-Hypervisor Transport Node Metrics (Continued)
Name
Category
Type
Unit
Description
Instanced
Usage
Filesystem
Metric
KiB
Amount of disk
space currently
being used by
the transport
node.
No
Usage (%)
Filesystem
Metric
KiB
Percentage of
allocated disk
space currently
being used by
the transport
node.
No
Capacity
Provisioned
Memory
Metric
KiB
Amount of
memory
allocated to the
transport node.
No
Usage
Memory
Metric
KiB
Amount of
memory
currently being
used by the
transport node.
No
Usage (%)
Memory
Metric
%
Percentage of
memory power
currently being
used by the
transport node.
No
Cache
Memory
Metric
KiB
Amount of cache
memory
currently being
used by the
transport node.
No
Capacity
Provisioned
Swap
Metric
KiB
Amount of swap
memory
allocated to the
transport node.
No
Usage
Swap
Metric
KiB
Amount of swap
memory
currently being
used by the
transport node.
No
Usage (%)
Swap
Metric
%
Percentage of
swap memory
power currently
being used by
the transport
node.
No
Usage Increase
Rate
Swap
Metric
KiBs
Rate of swap
memory usage
increase - used
by the transport
node.
No
Egress Packets per
second
Physical
Interface
Metric
Packets
Rate of outgoing
packets from the
physical
interface.
Yes
VMware, Inc.
43
44
Name
Category
Type
Unit
Description
Instanced
Egress Packets
Demand
Physical
Interface
Metric
Packets
Rate of outgoing
packets demand
from the physical
interface.
Yes
Egress Packets
Max Observed
Physical
Interface
Metric
Packets
Maximum
observed rate of
outgoing packets
from the physical
interface.
Yes
Egress Packets
Contention
Physical
Interface
Metric
%
Contention rate
of outgoing
packets from the
physical
interface.
Yes
Egress Traffic
Physical
Interface
Metric
KiBs
Outgoing
network traffic
from the physical
interface.
Yes
Egress Errors
Physical
Interface
Metric
Errors
Rate of errors in
outgoing packets
from the physical
interface.
Yes
Ingress Packets
per second
Physical
Interface
Metric
Packets
Rate of errors in
incoming
packets into the
Physical
interface
Yes
Ingress Errors
Physical
Interface
Metric
Errors
Rate of errors in
incoming
packets into the
physical
interface.
Yes
Ingress Traffic
Physical
Interface
Metric
KiBs
Incoming
network traffic
into the physical
interface.
Yes
Ingress Packets
Demand
Physical
Interface
Metric
Packets
Rate of incoming
packets demand
into the Physical
interface.
Yes
Ingress Packets
Max Observed
Physical
Interface
Metric
Packets
Maximum
observed rate of
incoming
packets into the
physical
interface.
Yes
Ingress Packets
Contention
Physical
Interface
Metric
%
Contention rate
of incoming
packets from the
physical
interface.
Yes
Link Status
Physical
Interface
Metric
String
Link status of the
physical
interface.
Yes
VMware, Inc.
Name
Category
Type
Unit
Description
Instanced
Admin Status
Physical
Interface
Metric
String
Admin status of
the physical
interface.
Yes
Link Speed
Physical
Interface
Metric
KiBs
Link speed of the
physical
interface.
Yes
Egress Packets per
second
Tunnel Interface
Metric
Packets
Rate of outgoing
packets from the
tunnel interface.
Yes
Egress Packets
demand
Tunnel Interface
Metric
Packets
Rate of outgoing
packets demand
from the tunnel
interface.
Yes
Egress Packets
Max Observed
Tunnel Interface
Metric
Packets
Maximum
observed rate of
outgoing packets
from the tunnel
interface.
Yes
Egress Packets
Contention
Tunnel Interface
Metric
%
Contention rate
of outgoing
packets from the
tunnel interface.
Yes
Egress Traffic
Tunnel Interface
Metric
KiBs
Outgoing
network traffic
from the tunnel
interface.
Yes
Egress Errors
Tunnel Interface
Metric
Errors
Rate of errors in
outgoing packets
from the tunnel
interface.
Yes
Ingress Packets
per second
Tunnel Interface
Metric
Packets
Rate of incoming
packets into the
tunnel interface.
Yes
Ingress Errors
Tunnel Interface
Metric
Errors
Rate of errors in
incoming
packets into the
tunnel interface.
Yes
Ingress Traffic
Tunnel Interface
Metric
KiBs
Incoming
network traffic
into the tunnel
interface.
Yes
Ingress Packets
Demand
Tunnel Interface
Metric
Packets
Rate of incoming
packets demand
into the tunnel
interface.
Yes
Ingress Packets
Max Observed
Tunnel Interface
Metric
Packets
Maximum
observed rate of
incoming
packets into the
tunnel interface.
Yes
Ingress Packets
Contention
Tunnel Interface
Metric
%
Contention rate
of incoming
packets from the
tunnel interface.
Yes
VMware, Inc.
45
Name
Category
Type
Unit
Description
Instanced
Transmit Status
Tunnel Interface
Metric
String
Transmit status
of the tunnel
interface.
Yes
Receive Status
Tunnel Interface
Metric
String
Received status
of the tunnel
interface.
Yes
Connectivity
Status
Tunnel Interface
Metric
Integer
Connectivity
status of the
tunnel interface.
Used for
virtualization of
the tunnel
health.
Yes
Ingress Traffic
Queue
Metric
Integer
Incoming
network traffic
into the logical
queue.
Yes
Min Ingress
Traffic
Queue
Metric
Integer
Minimum
incoming
network traffic
into the logical
queue.
Yes
Max Ingress
Traffic
Queue
Metric
Integer
Maximum
incoming
network traffic
into the logical
queue.
Yes
NSX for Multi-Hypervisor Non-ESX Virtual Interface
NOTE The names that appear for Virtual Interfaces in vRealize Operations Manager correspond to the
UUID of the Virtual Interface in the NSX Manager.
Table 7‑8. NSX for Multi-Hypervisor Non-ESX Virtual Interface Metrics
46
Name
Category
Type
Unit
Description
Instanced
Status
Status
Metric
String
Operation status
of the virtual
interface.
No
Admin Status
Status
Metric
String
Admin status of
the virtual
interface.
No
Usage Average
Network
Metric
KiBs
Average network
usage of the
virtual interface.
No
Transmitted
Average
Network
Metric
KiBs
Average
transmitted
network traffic of
the virtual
interface.
No
VMware, Inc.
Table 7‑8. NSX for Multi-Hypervisor Non-ESX Virtual Interface Metrics (Continued)
Name
Category
Type
Unit
Description
Instanced
Received Average
Network
Metric
KiBs
Average received
network traffic of
the virtual
interface.
No
Egress Packets per
second
Network
Metric
Packets
Rate of outgoing
packets.
No
Ingress Packets
per second
Network
Metric
Packets
Rate of incoming
packets.
No
VMware, Inc.
47
48
VMware, Inc.
Management Pack for NSX for MultiHypervisor Reports
8
A report is a scheduled snapshot of views. The Management Pack for NSX for Multi-Hypervisorprovides a
variety of report templates to enable you to generate reports for NSX for Multi-Hypervisor objects.
Table 8‑1. NSX for Multi-Hypervisor Report Templates
Name of Report
Applies to
Content
NSX-MH Controller Alerts
Controller Cluster
Provides a controllers inventory report
for the specific cluster and a list
counting current alerts triggered on
each controller sorted by alert severity.
NSX-MH Controller Capacity
Controller
Provides a 7 days average list for
controllers CPU/Memory/Disk
Workload percentage. Also provides a
7 day forecast list for the controllers
CPU/Memory/Disk Workload
percentage.
NSX-MH Environment Inventory
NSX-MH Environment
Provides a list counting all objects in
the environment per object type.
NSX-MH Network Traffic by Gateway
Gateway
Provides a list of the egress and ingress
traffic currently measured for all
NSX for Multi-Hypervisor Gateways.
NSX-MH Network Traffic by Logical
Switch
Logical Switch
NSX for Multi-Hypervisor Logical
Switches.
NSX-MH Network Traffic by Logical
Router
Logical Router
NSX for Multi-Hypervisor Logical
Routers.
NSX-MH Network Traffic by Non ESX
Hypervisor
Non ESX Hypervisor
traffic currently measured for all Non
ESX Hypervisors
NSX-MH Network Traffic by Service
Node
Service Node
Service Nodes.
NSX-MH Network Traffic by Virtual
Machine/ Virtual Interface
Virtual Interface, Virtual Machine
Virtual Interfaces or Virtual Machines.
VMware, Inc.
49
Generate a Report
The Management Pack for NSX for Multi-Hypervisor provides a list of report templates from which you can
generate reports.
Procedure
1
In the left pane of vRealize Operations Manager, click the Environment icon.
2
Select theManagement Pack for NSX for Multi-Hypervisor 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 report
template.
What to do next
Download the report by clicking Generated Reports. Select the report from the list of reports, and click the
required format in the Download column.
50
VMware, Inc.
Index
A
alert definitions 21
C
capacity models 29
D
dashboard navigation
access vRealize Operations Manager tools 18
dashboard to dashboard 18
dashboards
displaying 13
NSX-MH main 14
NSX-MH Object 19
NSX-MH Topology 15
NSX-MH Object Path 16
G
glossary 5
I
installing management packs 9
intended audience 5
M
management packs, installing 9
O
object types and metrics 31
open an external application
Log Insight 20
NSX manager 20
R
reports
generate 50
templates 49
VMware, Inc.
51
52
VMware, Inc.

vRealize Operations Management Pack for NSX for Multi

Transcription

Similar documents

ABCs of Science Review PART 1: METRIC SYSTEM Vocabulary

OSHEAN Agenda

Acura Debuts Alex Zanardi Edition NSX

SOLD - Victory Lane

SF161.RT METRIC.indd

How to move on after a divorce

File

Chancey - George R. Stuart Elementary

Introduction to the Metric System Objectives