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

Products

• VMware Smart Assurance

Issue/Introduction

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

Environment

SMARTS-10.1.X

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 domain 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:

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