Can the Discovery Engine see the VPN on either side of an MPLS cloud?
The Codima Discovery Engine used by autoAsset can map the network of a L3 VPN on the other side of the MPLS cloud. Why, because to all intents and purposes it is the same as a private network and all the routing tables to access the different parts of the VPN are held in the local PE (provider-edge) router to access the remote parts of the VPN. Unless there are access lists or firewalls in place (unlikely in this scenario) then the ICMP and SNMP traffic associated with the discovery process will be routed as normal. Background information MPLS is basically an efficient transport and administrative mechanism implemented by many xSPs and used in particular for the delivery of MPLS VPNs, also known as IP or Layer 3 VPNS. The autoAsset tool will see throughout the VPN as the VPN is configured at the relevant egress and ingress points of the provider MPLS cloud to provide a seamless virtual private network to a particular customer. How this is done is defined in RFC 2547.
The Codima Discovery Engine used by autoMap and autoAsset can map the network of a L3 VPN on the other side of the MPLS cloud. Why, because to all intents and purposes it is the same as a private network and all the routing tables to access the different parts of the VPN are held in the local PE (provider-edge) router to access the remote parts of the VPN. Unless there are access lists or firewalls in place (unlikely in this scenario) then the ICMP and SNMP traffic associated with the discovery process will be routed as normal. Background information MPLS is basically an efficient transport and administrative mechanism implemented by many xSPs and used in particular for the delivery of MPLS VPNs, also known as IP or Layer 3 VPNS. The autoMap/autoAsset products will see throughout the VPN as the VPN is configured at the relevant egress and ingress points of the provider MPLS cloud to provide a seamless virtual private network to a particular customer. How this is done is defined in RFC
The Codima Discovery Engine used by autoMap can map the network of a L3 VPN on the other side of the MPLS cloud. Why, because to all intents and purposes it is the same as a private network and all the routing tables to access the different parts of the VPN are held in the local PE (provider-edge) router to access the remote parts of the VPN. Unless there are access lists or firewalls in place (unlikely in this scenario) then the ICMP and SNMP traffic associated with the discovery process will be routed as normal. Background information MPLS is basically an efficient transport and administrative mechanism implemented by many xSPs and used in particular for the delivery of MPLS VPNs, also known as IP or Layer 3 VPNS. The autoMap will see throughout the VPN as the VPN is configured at the relevant egress and ingress points of the provider MPLS cloud to provide a seamless virtual private network to a particular customer. How this is done is defined in RFC 2547. Troubleshooting:- If you ha
