Reachability is not reported on for certain Smarts devices
book
Article ID: 333130
calendar_today
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
- The Reachability metric for certain Smarts devices is not reported on.
- As per screenshot below, it can be seen that for this specific device, it's Reachability metric is not reported on.

Resolution
- In this instance the reason for the Reachability metric not being reported on is related to how the metric is collected.
- The device in this case is present in both Smarts domains AM/PM and MPLS.
- Since the device metrics are collected from both domain's they are identical.
Note: Its recommended in MnR to collect device metrics from a single Smarts domain only.
- In MnR what happens is it creates a variable id using certain collected key metrics.
- The key metrics are going to be the same as identical device data is collected from MPLS and AM/PM domains.
- What is happening in this instance, is the Reachability metric updates the device associated with the MPLS domain and not the AM/ PM domain.
- The workaround here is found within the following file:
<APG Instance>\Collecting\Smarts-Collector\emc-smarts\conf\mpls.xml.
<property name="Name" rename="deviceid" />
<property name="Name" rename="objid" />
<property name="DisplayClassName Description Model Location Vendor"
rename="devtype devdesc model location vendor" />
<value name="IsUnresponsive" rename="Reachability" unit="%">
<transformation match="false" replace="100.0" />
<transformation match="true" replace="0.0" />
</value>
</data>
This will allow reachability metrics collected from the Smarts AM/PM domain to be committed to the DB and hence reported on within FE Smarts reports.
Feedback
thumb_up
Yes
thumb_down
No