Smarts MCAST: Device not being discovered by MCAST; MCAST domain is not discovering a device

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


The device was not being discovered by Multi Cast Domain.

Version information:
Version Info:

linux_rhAS50-x86-64/206180000: 
MCAST_SUITE: V8.1.4.5/64(124185), 02-May-2013 22:08:46 Copyright 1995-2013, EMC Corporation - Build 6

Environment

VMware Smart Assurance - SMARTS

Cause

The dxa-am.conf  file,  and dxa-am-lite.conf,  found in Smarts <Basedir>/local/conf/mcast directory,  were filtering out the device name.

Resolution

By adding a filter we allowed the device to be discovered in smarts.

The following files need to to be edited using the below commands: 

#./sm_edit ../local/conf/mcast/dxa_conf

And: 
#./sm_edit ../local/conf/dxa-am-lite.conf

As the device was named tcondor.router we add the filter- "tcore" by appending the line beginning with  "peek Displayname":


*********************
# so as to allow others to copy it to other applications in the future.

##########################################################################
#                                                                        #
# AM classes for import                                                  #
#                                                                        #
##########################################################################

proxy   UnitaryComputerSystem
peek    SupportsSNMP    TRUE
peek    DisplayName     |core*|spe*|inx*|eref*|asbx*|bx*|dis*|eRP*|rp*|ibrs*


We modify the peek Displayname to:

peek DisplayName |core*|spe*|inx*|eref*|asbx*|bx*|dis*|eRP*|rp*|ibrs*|tcore*

please edit this line in dxa-am.conf and dxa-am-lite.conf