Smarts Multicast Manager: Non-Multicast IPNetwork objects are being added to the Smarts Multicast Manager topology

Products

• VMware

Issue/Introduction

Symptoms:




Non-Multicast IPNetwork objects are being added to the Smarts Multicast Manager topology

Environment

VMware Smart Assurance - SMARTS

Cause

This issue is seen when an underlying Smarts AM/PM domain has been added as a source of topology from Multicast Manager. If the only source for Multicast objects is from the Smarts ASAM, then the Multicast domain will contain objects only used for Multicast (IPNetworks in which Multicast objects exist). IPNetworks in which there are no existing Multicast objects will not be created in the Multicast domain. However, if Smarts AM/PM is added as a source for Multicast, then all IPNetworks will be transferred over to the Multicast domain from the AM/PM domain, including many which may not be Multicast-related IPNetwork objects.

If Multicast objects such as PIMInterfaces and IGMPInterfaces only exist in the Alcatel network (only Alcatel routers), then the Multicast domain should only use the ASAM as a topology source and not Smarts AM/PM domains.

Resolution

To resolve this issue, do the following:

1. Remove the Smarts AM/PM domain as a source for the Multicast Manager. 
2. Restart the Multicast Manager domain to clean up the repository.