Reachability is not reported on for certain Smarts devices
search cancel

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.





Environment

M&R -7.x

Resolution

  1. In this instance the reason for the Reachability metric not being reported on is related to how the metric is collected.
  2. The device in this case is present in both Smarts domains AM/PM and MPLS.
  3. 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.
  4. In MnR what happens is it creates a variable id using certain collected key metrics.
  5. 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.
  • Commenting out the below section within mpls.xml followed by a collector restart will resolve the issue.
    <data id="Device" class="UnitaryComputerSystem"containment="HostsServices ConnectedVia Underlying" start="true"><scripted-property script-id="datagrp-tag" /><property name="DisplayName Name" drop-empty="true"rename="device device" />
<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.