Smarts MCAST: Is it possible to Discover and/or monitor OSPF in non-default VRF
Article ID: 332200
Updated On:
Products
VMware Smart Assurance
Environment
VMware Smart Assurance - SMARTS
Resolution
The EX9200 is a Tier 3 WAN backbone device; which means the configuration will use numerous virtual routing instances (VRFs), with routing adjacencies in each.
When reading the auto-evidence files (e.g.: smarts-ospf.txt and smarts-mcast.txt) becomes apparent that these files only list OSPF and PIM neighbor relationships that exist in the default VRF (or default routing instance, if you prefer). OSPF and PIM neighbor relationships in other VRFs are not reported in these files.
We do not support OSPF discovery/monitoring in non-default VRF in NPM. Also, PIM neighbor in MCAST is supported via CLI but only for discovery. Monitoring of these PIM neighbor is not supported.
When reading the auto-evidence files (e.g.: smarts-ospf.txt and smarts-mcast.txt) becomes apparent that these files only list OSPF and PIM neighbor relationships that exist in the default VRF (or default routing instance, if you prefer). OSPF and PIM neighbor relationships in other VRFs are not reported in these files.
We do not support OSPF discovery/monitoring in non-default VRF in NPM. Also, PIM neighbor in MCAST is supported via CLI but only for discovery. Monitoring of these PIM neighbor is not supported.
Additional Information
ER ER-323 has been submitted to request support for this feature on 3/07/2016
Feedback
Yes
No
Powered by
