[169688] in North American Network Operators' Group
RE: [c-nsp] OAM/CFM question on IOS-XR
daemon@ATHENA.MIT.EDU (=?iso-8859-2?Q?Vitkovsk=FD_Adam?=)
Tue Mar 11 08:58:38 2014
From: =?iso-8859-2?Q?Vitkovsk=FD_Adam?= <adam.vitkovsky@swan.sk>
To: Herro91 <herro91@gmail.com>, Cisco-nsp <cisco-nsp@puck.nether.net>,
"nanog@nanog.org" <nanog@nanog.org>
Date: Tue, 11 Mar 2014 12:57:41 +0000
In-Reply-To: <CADkMbJaxg7szxO6Qgbf_iHFoGkC1Duw7idSo78kbec11Og=etg@mail.gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
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 r=
outer
> 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.=20
So in a p2p PW there are going to be only PW endpoints as MEPs for a partic=
ular Level.=20
> 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 c=
an ping to or capture in a traceroute.=20
So in case of an e.g. me3400 connected to your XR box than p2p PW to anothe=
r XR box than another me3400 as CPE.=20
These four boxes form the L2 domain over which you can utilize CFM to pin-p=
oint the failure.=20
You could have the me3400 as MEPs and XR boxes as MIPs for the particular l=
evel.=20
This gets handy as the L2 (aggregation) domain at each end of the MPLS clou=
d gets bigger and it's more difficult to see which L2 box dropped the ball.=
=20
Regarding the MPLS core in between, well you already have tools to identify=
the failed P/core box.=20
adam
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces@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
>=20
> Hi,
>=20
> 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:
>=20
> 1) I "think" I should be seeing MIPs in my traceroute when there is a P r=
outer
> in between the two PEs, correct?
>=20
> 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 autocre=
ate
> all, but it seems to be tied to a service configuration under CFM which w=
ould
> not apply in the case of a transit/P router.
>=20
>=20
> Thanks!
> _______________________________________________
> cisco-nsp mailing list cisco-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
