vRealize Operations Management Pack for Network … · vRealize Operations Management Pack for...

vRealize Operations Management Packfor Network Devices

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-001932-00

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

vRealize Operations Management Pack for Network Devices

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 © 2015 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 Introducing the Management Pack for Network Devices 7

2 Installing and Configuring the Management Pack for Network Devices 9

Installing the Management Pack for Network Devices 9Configure the Network Devices Adapter 10Discovering Leaf and Spine Switches 11

3 Monitoring the Network Environment 13

View Management Pack for Network Devices Dashboards 13Physical Network Overview 14Network Device Connectivity Dashboard 15

4 How to Troubleshoot the Network Device Environment 17

Detect Configuration Problems Between Two Objects 17Spine Switches Are Not Discovered 17

5 Management Pack for Network Devices Alert Definitions 19

Network Devices Adapter Alert Definitions 19

6 Management Pack for Network Devices Capacity Models 23

7 Management Pack for Network Devices Object Types and Metrics 25

Leaf and Spine Switch Metrics - Not Instanced 25Leaf and Spine Switch Port Metrics - Instanced 28Host System Metrics 30

8 Management Pack for Network Devices Property Definitions 31

Leaf and Spine Switch Property Definitions 31Leaf and Spine Switch Port Property Definitions - Instanced 31

9 Management Pack for Network Devices Reports 33

Generate a Report 34

Index 35

VMware, Inc. 3


4 VMware, Inc.

About This Book

The VMware vRealize ®Operations Management Pack™ for Network Devices guide takes you through theprocess of deploying a working instance of the Management Pack for Network Devices within your vCenterenvironment.

Intended AudienceThis information is intended for vSphere and/or network operations managers who require visibility,traceability, and troubleshooting capabilities between their virtual server environment and their physicaldata network.

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.

Introducing the Management Pack forNetwork Devices 1

The VMware vRealize® Operations™ Management Pack for Network Devices extends the operationalmanagement capabilities of the vRealize Operations platform to the areas of physical data centernetworking. This management pack discovers and collects data from the interconnected switch topologybetween vSphere hosts.

This discovered topology is displayed in a leaf/spine hierarchical orientation with object relationships thatmap networking data between virtual machines, VDS/VSS, vSphere hosts, and interconnected adjacentphysical leaf and spine switches.

These discovered relationships provide the operations data model for the following use cases:

n Root cause impact, such as critical, warning, and informational, for many health, performance, andcapacity issues that the physical network may have on the vSphere host environment.

n SNMP-based operations monitoring and vRealize Operation analytics for the discovered leaf and spineswitches.

n Problem alerting on known operation impacts within the physical network topology.

n Physical network connectivity and health troubleshooting between two virtual endpoints.

n Topology visualization that includes any interconnected links.

n Advanced virtual to physical network troubleshooting when theManagement Pack for NSX for vSphere is installed and collecting NSX operations data.

You can use the Management Pack for Network Devices to automatically discover the relationships betweenvirtual and physical networks, and to alert on all operation conditions that may impact virtual machineperformance or reachability issues. This management pack reduces the mean time to restoration, providesend to end visibility for operations managers, and analyzes the data based on operation trends that mayimpact the performance and throughput of virtual machines across a data center leaf and spine topology.

This management pack is not intended for general-purpose SNMP monitoring of many different classes ofnetwork devices, but rather to correlate physical data center leaf and spine health conditions to the virtualserver infrastructure. This management pack leverages standard SNMP protocols including IPv4, read-only-SNMP 2 and 3, LLDP and CDP, it should not be used for collecting data from switches that are notdiscovered as part of the leaf and spine vSphere/NSX topology.

Extending the Functionality of theManagement Pack for Network Devices

You can extend the functionality of the Management Pack for Network Devices by configuring a networktechnology-related partner adapter. You can use automatic discovery, or a proprietary API to discover leafand spine switches.

VMware, Inc. 7

The Network Device Extender adapter is a sample adapter that has been developed for this purpose. Formore information about how this adapter extends the Management Pack for Network Devices, see theNetwork Device Extender Adapter SDK Guide.


8 VMware, Inc.

Installing and Configuring theManagement Pack for NetworkDevices 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 adapter instance.

This chapter includes the following topics:

n “Installing the Management Pack for Network Devices,” on page 9

n “Configure the Network Devices Adapter,” on page 10

n “Discovering Leaf and Spine Switches,” on page 11

Installing the Management Pack for Network DevicesYou can use the Management Pack for Network Devices as a standalone management pack to monitor yourphysical network environment, or together with additional networking management packs.

If you intend to use additional management packs, make sure that you first install theManagement Pack for Network Devices.

Prerequisites

n Save the PAK file from the downloaded solution to a temporary folder on your local system.

Procedure

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

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

3 On the Solutions tab, click the Add icon.

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

The upload might take several minutes.

5 Read and accept the EULA, and click Next.

Installation details appear in the window during the process.

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

7 When the installation is complete, click Finish.

What to do next

Configure an adapter instance for the management pack.

VMware, Inc. 9

Configure the Network Devices AdapterConfigure the Network Devices adapter so that you can monitor the leaf and spine switches in yourenvironment, and view related alerts, metrics and object capacity.

If you are upgrading from the Management Pack for NSX for vSphere version 2.0, and the Network Devicesadapter is configured in your environment, you must add a new credential in order to connect throughSNMPv2 or SNMPv3 so that the adapter can collect information from the physical network. TheManagement Pack for Network Devices does not support multiple instances of the Network Device adapter.Configure only one instance of the Network Device adapter.

Prerequisites

n Enable SNMP in your network environment so that leaf and spine switches are monitored.

n Enable Link Layer Discovery Protocol (LLDP) or Cisco Discovery Protocol (CDP) on each networkdevice to perform complete monitoring of your environment.

n Enable LLDP on each host when using the vNetwork Distributed Switch

n Enable CDP for each host when using the vNetwork Standard Switch.

Procedure

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

2 Select Management Pack for Network Devices, and click the Configure icon.

3 Configure the adapter settings.

Option Action

Display name Enter a name for the adapter instance.

Description (Optional) Describe the instance.

SNMP Ports Enter a comma-separated list of port numbers. By default, the port is set to161.

SNMP Read Community Strings Enter the SNMP read community strings as comma separated values. Inthis way you can manage multiple data centers in your environment.

SNMP Version Select the version of the SNMP protocol used in your environment. Theavailable options are SNMPv1, SNMPv2 and SNMPv3.

SNMPv3 User Name Enter the SNMPv3 user name.

SNMPv3 Privacy Password Enter the SNMPv3 privacy password.

SNMPv3 Authentication Password Enter the SNMPv3 authentication password.

SNMPv3 Authentication Protocol Enter the SNMPv3 authentication protocol.

Credential Enter the collection configuration settings that the adapter uses toauthenticate the connection on an external data source.Enter the SNMP read community strings as comma separated values. Inthis way you can manage multiple data centers in your environment.If you are upgrading from the Management Pack for NSX for vSphereversion 2.0, and the Network Devices adapter is configured in yourenvironment, add a new credential in order to connect through SNMPv2or SNMPv3.


10 VMware, Inc.

4 Click Test Connection.

If the adapter has already discovered leaf switches, the connection is tested on a randomly selected leafswitch. In situations when leaf switches have not yet been discovered, if the adapter has discoveredhosts, the adapter selects a host, accesses its leaf properties, and tries to connect to the leaf switch. If theadapter has not discovered hosts, the test is successful. In all instances, the connection is tested on onerandomly selected leaf switch and not all devices, and as such the connection is tested partially.

5 From the Collector drop-down box in the Advanced Settings area, select the collector upon which youwant to run the adapter instance.

This option has been set to the optimal collector by default.

6 Click Save Settings.

7 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 theManagement Pack for Network Devices Solution Detailspane on the Solutions page.

The strings Collecting and Data receiving appearapproximately five minutes after you have configuredthe adapter showing that the adapter is collectinginformation.

Environment Overview The objects related to theManagement Pack for Network Devices are added to theinventory. You can view these objects by clickingEnvironment > All Objects, and then clicking NetworkDevices Adapter. Leaf and spine switches appear invRealize Operations Manager after a few collectioncycles.Familiarize yourself with your network environment.Network devices that are not directly connected to hostsare recognized as Spine switches.

Discovering Leaf and Spine SwitchesThe Management Pack for Network Devices uses the Link Layer Discovery Protocol/Cisco DiscoveryProtocol (LLDP/CDP) to perform autodiscovery of leaf and spine switches in your physical network. Inorder for this to occur, there are specific LLDP/CDP properties that must be populated by the vCenteradapter that the management pack uses for creating leaf switches.

LLDP/CDP PropertiesThese properties must be populated by the vCenter adapter.

n managementIpAddress

n systemName

n portName

For example:

n <ops:property name =" net:vmnic1|discoveryProtocol|lldp| managementIpAddress " >

192.168.101.1 </ops:property>

n <ops:property name =" net:vmnic1|discoveryProtocol|lldp|portName " > FastEthernet1/0/1

</ops:property>

n <ops:property name =" net:vmnic1|discoveryProtocol|lldp|systemName " > cisco3750-prmb-una-

i02-02.cisco3750-prmb-una-02.eng.vmware.com </ops:property>

Chapter 2 Installing and Configuring the Management Pack for Network Devices

VMware, Inc. 11

n <ops:property name =" net:vmnic1|discoveryProtocol|lldp|timeToLive " > -113 </ops:property>

n <ops:property name =" net:vmnic1|discoveryProtocol|lldp|vlan " > 101 </ops:property>

n <ops:property name =" net:vmnic2|discoveryProtocol|cdp|hardwarePlatform " > cisco WS-

C3750-48P </ops:property>

n <ops:property name =" net:vmnic2|discoveryProtocol|cdp|managementIpAddress " > 10.115.4.34

</ops:property>

n <ops:property name =" net:vmnic2|discoveryProtocol|cdp|mtu " > 0 </ops:property>

n <ops:property name =" net:vmnic2|discoveryProtocol|cdp|portName " > FastEthernet1/0/4

</ops:property>

n <ops:property name =" net:vmnic2|discoveryProtocol|cdp|softwareVersion " > unknown

</ops:property>

n <ops:property name =" net:vmnic2|discoveryProtocol|cdp|systemName " />

n <ops:property name =" net:vmnic2|discoveryProtocol|cdp|timeToLive " > 173 </ops:property>

n <ops:property name =" net:vmnic2|discoveryProtocol|cdp|vlan " > 1 </ops:property>

Automatic Discovery SettingsThe Network Device adapter supports autodiscovery of objects. In this way, the adapter continuouslycollects data and discovers leaf and spine switches.

The adapter runs autodiscovery of objects between leaf switches after every specified collection cycles. Bydefault the autodiscovery parameter is set to 5.

The minimum number of physical ports required on a discovered device to create aManagement Pack for Network Devices spine switch object is 18.

You can change the autodiscovery interval property autoDiscoveryCollectionCycleCount=5 and theminimum number of ports property minNumberOfSwitchPorts=18 in theconf/autodiscovery.properties/usr/lib/vmware-

vcops/user/plugins/inbound/universalnetwork_adapter3/conf/autodiscovery.properties file.


12 VMware, Inc.

Monitoring the Network Environment 3You can use the dashboards of the Management Pack for Network Devices to monitor your physicalnetwork devices.

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


n “View Management Pack for Network Devices Dashboards,” on page 13

n “Physical Network Overview,” on page 14

n “Network Device Connectivity Dashboard,” on page 15

View Management Pack for Network Devices DashboardsManagement Pack for Network Devices dashboards are displayed in the vRealize Operations ManagerHome pane after the Management Pack is installed. If you have numerous dashboards open in yourworkspace, the Network Device dashboards may not be visible, and you might have to select them from thelist of dashboards.

Procedure

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

2 From the Dashboard List drop-down menu, make sure the MPND Dashboards checkbox is selected.

3 If you cannot view the dashboards, from the Dashboard List drop-down menu, point to MPNDDashboards, and select the required dashboard.

The selected dashboard is displayed.

VMware, Inc. 13

https://www.vmware.com/support/pubs/vrealize-operations-manager-pubs.html

https://www.vmware.com/support/pubs/vrealize-operations-manager-pubs.html

Physical Network OverviewThe Physical Network Overview dashboard provides an overview of the health of the leaf switches andspine switches in your environment. Use this dashboard to view details about the topology of a selectedobject and how it connects with physical elements in the network, and to view a list of related metrics andalerts.

Table 3‑1. Physical Network Overview Dashboard

Widget Description

Network Device Overview Displays a high level view of your network devicecomponents.NOTE Non-ESXi hosts are not included in the objectsdisplayed in this dashboard. The only hosts displayed arethose that are managed by the vCenter Server.You can point to an object to view high level informationrelating to the performance and condition of yourenvironment.You can click an object to view the object's physicalconnectivity relations. The data in the other dashboardwidgets is updated accordingly. A graphical representationof the object and all related objects and their relationshipsin the inventory is displayed in the Topology Graphwidget, related metrics are displayed in the SparklineChart widget, and open alerts in the Open Alerts widget.

Sparkline Chart Displays graphs that contain metrics for the selected object.

Open Alerts Displays a list of alerts that are open in the network deviceenvironment.You can click an alert to view additional information aboutthe problem including recommendations fortroubleshooting.

Topology Graph Displays a graphical representation of the selected objectand its relationships in the inventory.You can point to an object to view health, risk, andefficiency values as well as information about the objectsuch as its IP address, vendor name, and MAC address.You can double-click the object to analyze the health, risk,and efficiency of the object in the Summary tab.For an extended view that includes other connected objects,you can right-click an object, select Expand Node, andselect the objects you want to include in the expandedview.

Top Spine Switches by Traffic (MBps) Lists the spine switches in the environment that arecurrently experiencing the most network traffic.

Top Leaf Switches by Traffic (MBps) Lists the leaf switches in the environment that are currentlyexperiencing the most network traffic.


14 VMware, Inc.

Network Device Connectivity DashboardUse the Network Device Connectivity dashboard to run a visual path between two objects and see how theyare connected to each other, and to other objects in the environment. You can use the resulting visual path todetect possible connectivity problems.

Table 3‑2. Network Device Connectivity Dashboard

Widget Description

Network Resources Displays a list of objects in the environment.

Physical Path Provides a visual display of how the two selected objectsare connected through the physical network.

Chapter 3 Monitoring the Network Environment

VMware, Inc. 15


16 VMware, Inc.

How to Troubleshoot the NetworkDevice Environment 4

You can use the Management Pack for Network Devices to diagnose and troubleshoot problems in yourlogical and physical network. Locate and resolve connectivity issues by creating a visual path between twoobjects, or running a physical path between two objects.


n “Detect Configuration Problems Between Two Objects,” on page 17

n “Spine Switches Are Not Discovered,” on page 17

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 Network Device Connectivity dashboard where you can create a visualpath between the objects, and locate possible connectivity problems.

You can create a path between two virtual machines, two hosts, or two leaf switches.

Procedure

1 In the Network Device Connectivity dashboard, search for the object by name, and select the object.

2 Search for another object by name, and select the object.

The connection paths between the two objects are displayed in the Physical Path widget.

Spine Switches Are Not DiscoveredThe Management Pack for Network Devices does not discover spine switches in your physical networkenvironment.

Problem

Spine switches are not discovered in your environment.

Cause

The number of physical ports does not exceed the defined threshold.

Solution

1 Check the port threshold setting in the /usr/lib/vmware-vcops/user/plugins/inbound/universalnetwork_adapter3/conf/autodiscovery.properties file.

The default threshold is set to 18 ports.

2 If required, reduce the number of ports so that the number of the device's physical ports exceeds thedefined threshold.

VMware, Inc. 17

3 Restart the adapter instance, or the collector.


18 VMware, Inc.

Management Pack for NetworkDevices Alert Definitions 5

vRealize Operations Manager monitors the objects in your environment and notifies you when a problem isdetected in the form of an alert. Alerts are based on alert definitions, a combination of symptoms andrecommendations that identify problems areas in your environment. Alerts are generated when thecollected data is compared to the alert definition and the alert symptoms are evaluated as true.

The Management Pack for Network Devices provides specific alert definitions that notify you when the leafswitch, spine switch, and host objects are exhibiting symptoms that are unfavorable to your environment.

Network Devices Adapter Alert DefinitionsThe Management Pack for Network Devices provides alert definitions that are defined on the leaf switches,spine switches and hosts discovered by the Physical Discovery adapter.

Leaf Switch Alert DefinitionsThe following alert definitions are defined on the Leaf switch objects.

Table 5‑1. Leaf Switch Alert Definitions

Alert Name Symptom Recommendations Impact Severity

A redundant link isdown between hostand switch

Fault Event - Leafswitch redundantlink is down

1 Check the cableconnectionbetween theswitch and host.

2 Verify that thephysical NIC isconfiguredcorrectly on thehost.

3 Verify that theport isconfiguredcorrectly.

Risk Warning

Host System Alert DefinitionsThe following alert definitions are defined on the Host System objects.

VMware, Inc. 19

Table 5‑2. Host System Alert Definitions


(VMware Host)Failover capacity isinsufficient to satisfydemand

net|FailoverInterfaces

1 Upgrade tohigher speedconnections toincrease portcapacity.

2 Add moreredundant portconnections.

Risk Warning

(VMware Host)All switch ports aredown

summary|All SwitchPorts Down

No recommendation. Risk Critical

(VMware Host)Not all but someswitch ports are down

notsummary|AllSwitch Ports Downandnotsummary|AllSwitch Ports Down

No recommendation. Risk Warning

Invalid IP Address forconnected Leaf Switch

IP Address forconnected LeafSwitch is 0.0.0.0

Configure valid IPaddress for LeafSwitch.

Risk Critical

Top of the Rack switchwas not discovered.

LLDP/CDP isdisabled on thevSphere DistributedSwitch

Verify that theLLDP/CDPdiscovery is enabledon the vSphereDistributed Switch.

Health Info

Virtual Machine Alert DefinitionsThe following alert definitions are defined on the virtual machine objects.

Table 5‑3. Virtual Machine Alert Definitions


All switch ports aredown for parent host

Host summary|AllSwitch Ports Down

Norecommendations.

Risk Critical

Not all but someswitch ports are downfor parent host

not summary|AllSwitch Ports Downandnot summary|AllSwitch Ports Up

Norecommendations.

Risk Warning

Leaf Switch and Spine Switch Alert DefinitionsThe following alert definitions are common to both the Leaf switch and the Spine switch objects.

Table 5‑4. Leaf Switch and Spine Switch Alert Definitions

Alert Name Symptoms Recommendations Impact Severity

IP header errors areabnormally high

General|IP InHeader Errors

Verify that theconfiguration on thedevice is correct.

Health Critical

IP address errors areabnormally high

General|IP InAddress Errors

Verify that theconfiguration on thedevice is correct.

Health Critical


20 VMware, Inc.

Table 5‑4. Leaf Switch and Spine Switch Alert Definitions (Continued)


Device not respondingto SNMP

Fault Event - DeviceConnection Statusfailure

1 Verify thatSNMP is enabledon the device.

2 Verify that theadapter instancehas the correctSNMPconfiguration forcommunicatingwith this device.

3 Verify that thereare no firewallsblocking SNMPtraffic betweenthe Collector andthis device.

Health Major

Interface isexperiencing networkcontention on ingresstraffic

Interfaces|IngressDropped Packets

1 Verify there isenoughbandwidthavailable tosatisfy thenetworkdemand.

2 Verify that theinterfaceconfiguration iscorrect.

Health Critical

Interface isexperiencing networkcontention on egresstraffic

Interfaces|EgressDropped Packets

1 Verify there isenoughbandwidthavailable tosatisfy thenetworkdemand.

2 Verify that theinterfaceconfiguration iscorrect.

Health Critical

Interface ingresspacket errors areabnormally high

Interfaces|IngressException Packets

Verify that theinterfaceconfiguration iscorrect.

Health Critical

Interface egress packeterrors are abnormallyhigh

Interfaces|EgressException Packets

Verify that theinterfaceconfiguration iscorrect.

Health Critical

Switch has rebooted msg_event - "Switchhas rebooted"

Check the log files onthe switch

Health Warning

The MTU on one ormore interfaces is lessthan 1600

Interfaces|Mtu <1600

The MTU on one ormore interfaces onthe switch is set toless than 1600, whichis not optimal forVXLANperformance.

Efficiency Warning

Chapter 5 Management Pack for Network Devices Alert Definitions

VMware, Inc. 21

Table 5‑4. Leaf Switch and Spine Switch Alert Definitions (Continued)


One or more PSUshave failed

PSU|Availability = 0 Replace the powersupply unit on theswitch.

Risk Immediate

CPU utilization is high CPU|CPU Usage >90

Reduce the load onthe device.

Health Warning

Memory utilization ishigh

Memory|MemoryUsage > 90

Reduce the load onthe device.

Health Warning

Network device typecould not be detected

general|vendorName =unknownorgeneral|modelName= unknown

Provide thevendor/model of thenetwork device andmake theinformation availableto VMware for futureoperability testing.

Risk Information

Interface is disabled interfaces|ifAdministrativeStatus = down

Confirm that theinterface should bedisabled.

Health Info

Unconnected interfaceis down

interfaces|ifOperationStatus =downinterfaces|ifAdministrativeStatus = upinterfaces|isConnected = false

Verify that theunconnectedinterface should bedisabled.

Health Warning

Connected interface isdown

interfaces|ifOperationStatus =downinterfaces|ifAdministrativeStatus = upinterfaces|isConnected = true

Verify interfacehardware and cable.

Health Critical


22 VMware, Inc.

Management Pack for NetworkDevices Capacity Models 6

The Management Pack for Network Devices provides capacity models that have been defined for the Leafand Spine switches discovered by the Network Device adapter in your network environment.

Leaf and Spine Switch Capacity ModelsThe Management Pack for Network Devices provides definitions for both the Leaf and Spine switchcapacity model.

Table 6‑1. Leaf and Spine Switch Capacity Model

Container Description Use in Workload

Used Interfaces Utilization of ports. No

Uplink Switch Ingress Uplink ingress network utilization ofthe switch, as measured by SNMP.

Yes

Uplink Switch Egress Uplink egress network utilization ofthe switch, as measured by SNMP.

Yes

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

Yes

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

Yes

Switch Total Total network utilization of theswitch, as measured by SNMP.

Yes

Switch Port Ingress Ingress network utilization of theswitch port, as measured by SNMP

Yes

Switch Port Egress Egress network utilization of theswitch port, as measured by SNMP.

Yes

Memory Usage Memory usage. Yes

CPU Usage CPU usage. No

VMware, Inc. 23


24 VMware, Inc.

Management Pack for NetworkDevices Object Types and Metrics 7

Metric definitions provide an overview of how the metric is calculated or derived. TheManagement Pack for Network Devices uses the Network Devices adapter to collect metrics for the objectsin your network environment, and uses formulas to derive statistics from those metrics.


n “Leaf and Spine Switch Metrics - Not Instanced,” on page 25

n “Leaf and Spine Switch Port Metrics - Instanced,” on page 28

n “Host System Metrics,” on page 30

Leaf and Spine Switch Metrics - Not InstancedThe Management Pack for Network Devices collects metrics for leaf and spine switch objects.

Table 7‑1. Leaf and Spine Switch Metrics

Name Description Unit Category

sysUpTime Number of seconds thathave elapsed since the lasttime the device wasbooted.

centisecond

IP In Receives Total number of inputdatagrams received frominterfaces, including thosereceived in error.

packets/s

IP In Header Errors Number of inputdatagrams discarded dueto errors in their IPv4headers, including badchecksums, versionnumber mismatch, otherformat errors, time-to-liveexceeded, errorsdiscovered in processingtheir IPv4 options, etc.

errors/s

VMware, Inc. 25

Table 7‑1. Leaf and Spine Switch Metrics (Continued)


IP In Address Errors Number of inputdatagrams discardedbecause the IPv4 address intheir IPv4 header'sdestination field was not avalid address to bereceived at this entity. Thiscount includes invalidaddresses (e.g., 0.0.0.0) andaddresses of unsupportedClasses (e.g., Class E). Forentities which are not IPv4routers, and therefore donot forward datagrams,this counter includesdatagrams discardedbecause the destinationaddress was not a localaddress.

errors/s

IP Forward Datagrams Number of inputdatagrams for which thisentity was not their finalIPv4 destination, as a resultof which an attempt wasmade to find a route toforward them to that finaldestination. In entitieswhich do not act as IPv4routers, this counter willinclude only those packetswhich were Source-Routedvia this entity, and theSource-Route optionprocessing was successful.

packets/s

IP In Delivers Total number of inputdatagrams successfullydelivered to IPv4 user-protocols (including ICMP)

packets/s

Ingress Dropped Packets Number of inboundpackets which were chosento be discarded eventhough no errors had beendetected to prevent theirbeing deliverable to ahigher-layer protocol. Onepossible reason fordiscarding such a packetcould be to free up bufferspace.

discards/s

Egress Dropped Packets Number of outboundpackets which were chosento be discarded eventhough no errors had beendetected to prevent theirbeing transmitted. Onepossible reason fordiscarding such a packetcould be to free up bufferspace.

discards/s


26 VMware, Inc.

Table 7‑1. Leaf and Spine Switch Metrics (Continued)


Speed Total maximum bandwidthof all device interfaces

Mbps

Total Ingress Total amount of networktraffic received from allinterfaces.

Mbps

Ingress Capacity Maximum bandwidth thatcan be used for incomingnetwork traffic.

Mbps

Total Egress Total amount of networktraffic sent to all interfaces.

Mbps

Egress Capacity Maximum bandwidth thatcan be used for outgoingnetwork traffic.

Mbps

Port Count Maximum Number of ports

Port Count provisioned(used)

Number of used ports,partner-populated

CPU Usage% partner-populated %

Memory Usage % partner-populated %

Fan Status* partner-populated

Power Supply Status* partner-populated

Unicast Bytes Sent partner-populated Mbps

Multicast Bytes Sent partner-populated Mbps

broadcast bytes sent partner-populated Mbps

Unicast Bytes Received partner-populated Mbps

Multicast Bytes Received partner-populated Mbps

Broadcast Bytes Received partner populated Mbps

Multicast Packets Sent partner populated Mbps

Broadcast Packets Sent partner populated Mbps

Multicast Packets Received partner populated Mbps

Broadcast Packets Received partner populated Mbps

Uplink Ingress Traffic partner populated Mbps

Uplink Egress Traffic partner populated Mbps

Uplink Speed partner populated Mbps

Uplink Ingress Capacity partner populated Mbps

Uplink Egress Capacity partner populated Mbps

Ingress Dropped Packets % partner populated Mbps

Egress Dropped Packets % partner populated Mbps

Ingress Traffic % partner populated Mbps

Egress Traffic % partner populated Mbps

Chapter 7 Management Pack for Network Devices Object Types and Metrics

VMware, Inc. 27

Leaf and Spine Switch Port Metrics - InstancedThe Management Pack for Network Devices collects metrics for leaf and spine switch port objects.

Table 7‑2. Leaf and Spine Switch Port Metrics - Instanced


- unicast bytes sent Partner populated Mbps

- multicast bytes sent Partner populated Mbps

- broadcast bytes sent Partner populated Mbps

- unicast bytes received Partner populated Mbps

- multicast bytes received Partner populated Mbps

-broadcast bytes received Partner populated Mbps

Ingress Traffic Amount of network trafficreceived from the interface.

Mbps

Egress Traffic Amount of network trafficsent to the interface.

Mbps

Ingress Unicast Packets Rate of unicast packetsreceived from the interface.

packets/s

Ingress Non-Unicast Packets Rate of non-unicast packetsreceived from the interface.

packets/s

Ingress Dropped Packets Rate of incoming packetsthat were dropped on theinterface.

packets/s

Ingress Exception Packets Rate of incoming packetsthat reported an error onthe interface.

packets/s

Egress Unicast Packets Rate of unicast packets sentto the interface.

packets/s

Egress Non-Unicast Packets Rate of non-unicast packetssent the interface.

packets/s

Egress Dropped Packets Rate of outgoing packetsthat were dropped on theinterface.

packets/s

Egress Exception Packets Rate of outgoing packetsthat reported an error onthe interface.

packets/s

Speed Interface published maxbandwidth

Mbps

MTU Size of the largest packetwhich can be sent/receivedon the interface, specifiedin octets. For interfaces thatare used for transmittingnetwork datagrams, this isthe size of the largestnetwork datagram that canbe sent on the interface.


28 VMware, Inc.

Table 7‑2. Leaf and Spine Switch Port Metrics - Instanced (Continued)


Admin Status Desired state of theinterface. The testing(3)state indicates that nooperational packets can bepassed. When a managedsystem initializes, allinterfaces start withifAdminStatus in thedown(2) state. As a resultof either explicitmanagement action or perconfiguration informationretained by the managedsystem, ifAdminStatus isthen changed to either theup(1) or testing(3) states (orremains in the down(2)state).

Operation Status Current operational state ofthe interface. The testing(3)state indicates that nooperational packets can bepassed. If ifAdminStatus isdown(2) then ifOperStatusshould be down(2). IfifAdminStatus is changedto up(1) then ifOperStatusshould change to up(1) ifthe interface is ready totransmit and receivenetwork traffic; it shouldchange to dormant(5) if theinterface is waiting forexternal actions (such as aserial line waiting for anincoming connection); itshould remain in thedown(2) state if and only ifthere is a fault thatprevents it from going tothe up(1) state; it shouldremain in the notPresent(6)state if the interface hasmissing (typically,hardware) components.

Operational Status Code Same as Operation Status,only code number isdisplayed instead of stringvalue.

Last Change Value of sysUpTime at thetime the interface enteredits current operationalstate. If the current statewas entered prior to thelast re-initialization of thelocal network managementsubsystem, then this objectcontains a zero value.

centisecond

Uplink Ingress Traffic Incoming traffic fromuplink port.

Mbps

Chapter 7 Management Pack for Network Devices Object Types and Metrics

VMware, Inc. 29

Table 7‑2. Leaf and Spine Switch Port Metrics - Instanced (Continued)


Uplink Egress Traffic Outgoing traffic fromuplink port.

Mbps

Uplink Speed Traffic speed of uplinkport.

Mbps

Uplink Ingress Capacity Incoming traffic capacity ofuplink port.

Mbps

Uplink Egress Capacity Outgoing traffic capacity ofuplink port.

Mbps

Ingress Dropped Packets % Percent of droppedincoming packets.

%

Egress Dropped Packets % Percent of droppedoutgoing packets.

%

Ingress Traffic % Percent of incoming trafficpercent over trafficcapacity.

%

Egress Traffic % Percent of outgoing trafficpercent over trafficcapacity.

%

Host System MetricsThe Management Pack for Network Devices collects metrics for host system objects.

Table 7‑3. Host System Metrics


Network (I/O) | FailoverInterfaces

When the total demandfrom a host is more than asingle connection canhandle, any port or pNICoutage could result inoversubscribing thefailover link. This metricrepresents the number ofinterfaces that could be lostwithout oversubscribingcapacity. The calculationfor this metric is:Math.floor((totalCapacity -totalTraffic) /avarageCapacity);

Summary | All Switch PortsUP

True, if all interface portsare up, false otherwise.

Summary | All Switch PortsDown

True, if all interface portsare down, false otherwise.


30 VMware, Inc.

Management Pack for NetworkDevices Property Definitions 8

Properties are attributes of objects in the VMware vRealize Operations Manager environment. You useproperties in symptom definitions. You can also use properties in dashboards, views, and reports. TheManagement Pack for Network Devices uses the Network Devices adapter to collect properties for targetobjects in your physical network. Property definitions for all objects connected through the NetworkDevices adapter are provided.


n “Leaf and Spine Switch Property Definitions,” on page 31

n “Leaf and Spine Switch Port Property Definitions - Instanced,” on page 31

Leaf and Spine Switch Property DefinitionsThe Management Pack for Network Devices collects properties for leaf and spine switch objects.

Table 8‑1. Leaf and Spine Switch Property Definitions


Vendor Name Name of the device'svendor.

Model Name Name of the device'smodel.

IP Address IP address

Management IP address ipAdEntAddr. bothVMware and partner-populated

# of directly attached hosts(Leaf Switch only)

Calculated in code

Leaf and Spine Switch Port Property Definitions - InstancedThe Management Pack for Network Devices collects properties for leaf and spine switch port objects.

Table 8‑2. Leaf and Spine Switch Port Property Definitions - Instanced


- duplex mode (true/false) Partner populated

- Trunk encapsulationparameter (802.1Q)

Partner populated

VMware, Inc. 31

Table 8‑2. Leaf and Spine Switch Port Property Definitions - Instanced (Continued)


- VLAN(s) - In case ofdouble tag, focus on outertag.

Partner populated

Index Unique value, greater thanzero, for each interface. It isrecommended that valuesare assigned contiguouslystarting from 1. The valuefor each interface sub-layermust remain constant atleast from one re-initialization of the entity'snetwork managementsystem to the next re-initialization.

Description Textual string containinginformation about theinterface. This stringshould include the name ofthe manufacturer, theproduct name and theversion of the interfacehardware/software.

Type Interface type according tothe IANAIfType enum

Physical Address Interface's address at itsprotocol sub-layer. Forexample, for an 802.xinterface, this objectnormally contains a MACaddress. The interface'smedia-specific MIB mustdefine the bit and byteordering and the format ofthe value of this object. Forinterfaces which do nothave such an address (e.g.,a serial line), this objectshould contain an octetstring of zero length.

IP Addresses IP addresses list configuredon this interface


32 VMware, Inc.

Management Pack for NetworkDevices Reports 9

A report is a scheduled snapshot of views. The Management Pack for Network Devices provides a variety ofpredefined report templates from which you can generate reports on selected objects.

For more information about using reports in vRealize Operations Manager, see thevRealize Operations Manager documentation.

Table 9‑1. Management Pack for Network Devices Report Templates

Name of Report Template Content

Leaf Switch Capacity Usage Report % 30 Days Forecast A list of leaf switches based on the traffic capacity they areusing, sorted by the current capacity used percentage.Provides a 30 day forecast.

Leaf Switch Capacity Usage Report % 7 Days Forecast A list of leaf switches based on the traffic capacity they areusing, sorted by the current capacity used percentage.Provides a 7 day forecast.

Spine Switch Capacity Usage Report % 30 Days Forecast A list of spine switches based on the traffic capacity theyare using, sorted by the current capacity used percentage.Provides a 30 day forecast.

Spine Switch Capacity Usage Report % 7 Days Forecast A list of spine switches based on the traffic capacity theyare using, sorted by the current capacity used percentage.Provides a 7 day forecast.

Leaf Switch Interface Network Utilization Report Provides a list of leaf switch interfaces (ports) based on inand out traffic and traffic capacity values, sorted by egresstraffic.

Leaf Switch Interface Problem Report Provides a list of problems of different severity thatoccurred on leaf switch interfaces (ports), sorted in order ofcriticality.

Leaf Switch Problems Report Provides a list of problems of different severity thatoccurred on leaf switches, sorted in order of criticality.

Spine Switch Interface Network Utilization Report Provides a list of spine switch interfaces (ports) based on inand out traffic and traffic capacity values, sorted by egresstraffic.

Spine Switch Interface Problem Report Provides a list of problems of different severity thatoccurred on spine switch interfaces (ports), sorted in orderof criticality.

Spine Switch Problems Report Provides a list of problems of different severity thatoccurred on spine switches, sorted in order of criticality.

VMware, Inc. 33

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

Procedure

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

2 In the Inventory Trees list, expand the objects under Physical Network.

3 Select the object for which you want to generate a report, and click the Reports tab.

4 Select a report template, and click the Run Template icon.

When the report is complete, the number of generated reports is updated for the selected reporttemplate.

5 Click Generated Reports, select the report, and in the Download column, select the format in whichyou want to download the report.


34 VMware, Inc.

Index

Aalert definitions 19

Ccapacity models 23configure network devices adapter 10

Ddashboards

displaying 13network device connectivity 15physical network overview 14

detect configuration problems 17discovering leaf and spine switches 11

Gglossary 5

Iinstall the management pack 9installing and configuring the management

pack 9intended audience 5introducing the management pack 7

Mmanagement pack, installing 9metrics

host system 30leaf and spine switch (not instanced) 25leaf and spine switch port 28

monitoring your environment 13

Nnetwork device extender 7network devices adapter alert definitions 19

Oobject types and metrics 25

Pproperty definitions

leaf and spine switch 31leaf and spine switch port 31

Rreports

generating 34templates 33

Ttroubleshooting

detect configuration problems between twoobjects 17

run a physical path discovery 17spine switches are not discovered 17

VMware, Inc. 35


36 VMware, Inc.

vRealize Operations Management Pack for Network … · vRealize Operations Management Pack for...

Documents

Transcript of vRealize Operations Management Pack for Network … · vRealize Operations Management Pack for...