Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Watch4net | EMC M&R 6.x - Smarts Solution Pack: What are the differences between Device Availability, Reachability, and Interface Availability (335334)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 3894Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

This article explains the differences between device availability, reachability, and interface availability.

Frequently Asked Questions

Device was down according to Smarts, why am I seeing 100% availability on interface <interface name> on Watch4net Smarts SP report?

Device should be unreachable when device was down, why am I am seeing 100% reachability value on Watch4net Smarts SP report?

Resolution

Device Availability versus Interface Availability

Watch4net separates the reporting for Device Availability from Interface Availability. The data can be found in the following reports:

Device Availability: All>>Report Library>>EMC Smarts>>IP (AM-PM)>>device>>Category>>Health>>Availability
Interface Availability: All>>Report Library>>EMC Smarts>>IP (AM-PM)>>device>>Category>>Containment>>Interfaces>>Traffic>>Availability

Device Availability is based on SysUpTime value (OID 1.3.6.1.2.1.1.3) while Interface Availability is based on ifOperStatus value (1.3.6.1.2.1.2.2.1.8). Below is an example to better illustrate the difference.

Device     = x.y.z.w
sysUpTime  = 109 days, 10:39:55.21 (945599521)
sysContact =
sysName    = XXX
sysLocation= YYY

Interface    | Speed |Admin| IfOperStatus|  In Oper state for ...
-------------| ----- |-----|-------------| ----------------------
ge.1.1       |  100M |   up|           up|  109 days, 10:38:18.65
ge.1.2       |   10M |   up|         down|  109 days, 10:39:55.21
ge.1.3       | 1.00G |   up|           up|   87 days,  2:20:30.00
ge.1.4       |   10M |   up|         down|   51 days,  1:03:44.19
ge.1.5       |   10M |   up|         down|   51 days,  1:00:27.72
ge.1.6       |  100M |   up|           up|  109 days, 10:39:21.27
ge.1.7       |  100M |   up|           up|  109 days,  4:34:39.55
ge.1.8       |  100M |   up|           up|    8 days,  5:46:03.54

In the table above, we have sysUpTime showing up for 109 days. Some of the interfaces are up or down in the IfOperStatus column. The last column called "In Oper state for" is taken from IfLastChange (OID 1.3.6.1.2.1.2.2.1.9). Some of the interfaces that are showing up in ifOperStatus are showing different IfLastChange values. In this scenario, the device itself has been up for 109 days and interfaces are showing up for 8, 51, 87, and 109 days.

In Watch4net, sysUpTime is either translated as up or down (100% or 0%), and an average is taken from the set of data collection. In this case, the device has been up for 109 days and will show 100% Availability. When the device goes down, the sysUpTime resets to 0.

Meanwhile, Interface Availability is being translated by Watch4net from interface/port's Status attribute in Smarts. Availability is reported individually for each interface.

Device Availability versus Reachability versus Interface Availability

Device Availability is also completely independent from Reachability. Watch4net is taking the device reachability from IsUnresponsive status of the device from Smarts. IsUnresponsive is determined by snmpget and ICMP (ping). If snmpget is down and ICMP is up, the device is IsUnresponsive in Smarts. Meanwhile in interface availability, snmpget and ICMP are both down.

In order to better correlate the events in Smarts to Watch4net Smarts Solution Pack reports, it is important to know the nature of the event. This will help determine if you need to look at device availability, reachability, or interface availability.

Related Information

Other topics of interest that may be related to this article:
Watch4net/SRM: Problem with the AvaibilityFilter configuration
Watch4Net 6.2: SolutionPack for EMC Smarts has no Availability metrics or data for devices
EMC M&R / Service Assurance Suite (SAS) SolutionPack (SP): Wrong Availability in "Availability by Device Type"
Smarts IP/Interface status: What OIDs are polled for the Admin and Operational status of interfaces in Smarts IP?

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - Watch4Net/M&R

Take Our Survey

Support Assistant