Hi, > Herro91 > Sent: Wednesday, March 05, 2014 6:19 PM > 1) I "think" I should be seeing MIPs in my traceroute when there is a P router > in between the two PEs, correct? It is a L2 form of traceroute so it will record only L2 hops configured as MIPs or MEPs. So in a p2p PW there are going to be only PW endpoints as MEPs for a particular Level.
> 2) If the P router in between these PEs is just a transit node, what > configuration is required to create the MIPs? See CFM is meant for L2 OAM where there are no interface ip addresses you can ping to or capture in a traceroute. So in case of an e.g. me3400 connected to your XR box than p2p PW to another XR box than another me3400 as CPE. These four boxes form the L2 domain over which you can utilize CFM to pin-point the failure. You could have the me3400 as MEPs and XR boxes as MIPs for the particular level. This gets handy as the L2 (aggregation) domain at each end of the MPLS cloud gets bigger and it's more difficult to see which L2 box dropped the ball. Regarding the MPLS core in between, well you already have tools to identify the failed P/core box. adam > -----Original Message----- > From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of > Herro91 > Sent: Wednesday, March 05, 2014 6:19 PM > To: Cisco-nsp; nanog@nanog.org > Subject: [c-nsp] OAM/CFM question on IOS-XR > > Hi, > > I've been working on a basic configuration for E-OAM starting with one > domain. I have CFM working between the PEs (IOS-XR) devices tied to an > EoMPLS instance, but have a few questions below: > > 1) I "think" I should be seeing MIPs in my traceroute when there is a P router > in between the two PEs, correct? > > 2) If the P router in between these PEs is just a transit node, what > configuration is required to create the MIPs? I have seen the MIP autocreate > all, but it seems to be tied to a service configuration under CFM which would > not apply in the case of a transit/P router. > > > Thanks! > _______________________________________________ > cisco-nsp mailing list cisco-...@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/
