[j-nsp] Ethernet OAM, specifically CFM

[chip]

Thanks for all the input.  I'm beginning to get an understanding here.
 So, the vlan sub-int on the MX could be a MEP.  The port on the
switch where the customer connects can't be a MEP.  We'll have to
assume that I have no administrative control whatsoever over the
customer router.  I can't even insure that it's a router.  Could be an
ASA, could be a server, could be a router, just random device that can
route packets to some extent.  I would like to vlan connections back
up to the MX for layer-3 configurations.  My problem is that if the
customer facing port on the switch goes down, it won't take down the
layer-3 int on the MX, thus sending packets to nowhere.

The IRB instance sounds interesting, I'll try playing with that as well.

Thanks for the input all, much appreciated!

--chip

On Fri, Apr 20, 2012 at 4:57 PM, Keegan Holley
<keegan.holley at sungard.com> wrote:
> CFM wouldn't monitor a link with no MEP on the other end of it.  So you
> can't have a router a switch and then a link from the switch to a customer
> and monitor a link to a customer where the customer isn't running CFM on
> their equipment.
>
> 2012/4/20 Humair Ali <humair.s.ali at gmail.com>
>>
>> Actually CFM would be appropriate with what Chip is trying to achieve,
>>
>> CFM monitor a maintenance session end to end and works a vlan or link
>> level.
>>
>> Why not monitor Cust Rtr interface to MX1 accross the bridge network  via
>> CFM and have an action profile assign to it ?
>>
>> or monitor Cust Rtr 1 to remote end Cust Rtr 2 CFM , since usually you
>> would want to use CFM to guarantee a service.
>>
>>
>> On 20 April 2012 18:20, Keegan Holley <keegan.holley at sungard.com> wrote:
>>>
>>> CFM just performs a continuity check so I'm not sure it will help you
>>> here.  In other words it just checks if the CFM instance on the switch
>>> can
>>> talk to the CFM instance on the router.  If I understand your question
>>> correctly you're trying to verify an access point leading to a customer
>>> and
>>> not your MX.  If there is only one access port per VLAN interface can you
>>> move it down to the switch?
>>>
>>>
>>> 2012/4/20 chip <chip.gwyn at gmail.com>
>>>
>>> > Hi folks,
>>> >
>>> >  I'm trying to figure out if I can create a
>>> > connectivity-fault-management instance between a vlan sub interface on
>>> > an MX and the access port in the same vlan on a down stream switch.
>>> > Possibly this will help: http://imgur.com/MMrZm
>>> >
>>> > Ultimately my goal is to detect an outage on the access port and take
>>> > down the layer-3 interface on the MX so I won't blackhole traffic.
>>> > Since that interface won't go down if the access port on the
>>> > downstream switch does.   Or maybe there's a better solution.  Either
>>> > way, if someone has this setup and can supply some example configs I
>>> > would be ever so grateful.  I can't quite seem to work it out.
>>> >
>>> > Thanks all!
>>> >
>>> > --chip
>>> >
>>> > --
>>> > Just my $.02, your mileage may vary,  batteries not included, etc....
>>> >
>>> > _______________________________________________
>>> > juniper-nsp mailing list juniper-nsp at puck.nether.net
>>> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>>> >
>>> >
>>> _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>>
>>
>>
>> --
>> Humair
>>
>



-- 
Just my $.02, your mileage may vary,  batteries not included, etc....