Devices are not being discovered by MCAST Domain Manager

Products

• VMware Smart Assurance
• Network Observability

Issue/Introduction

Specific devices was not being discovered by Smarts Multi Cast (MCAST) Domain.

Environment

All supported Smarts releases

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 <Sample Device> we add the filter- "<sample>" 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*|<sample>*

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