[j-nsp] EX/MX G.8032 with OAM CCM's

[Ben Dale]

Having just done this in the last week (strictly EXs), I'd suggest that neither your OAM and G.8032 are configured correctly - post up some configuration if you can.

Make sure you have your link-fault-management action-profile is set to link-down and that you have an apply-action-profile bound to the interface as well.

My testing (very rough) showed about 0.5 seconds between link down and switch-over - I chalk this up to my test lab being copper interfaces and the slight lag in link-down detection.  

I think the minimum timers for OAM on the EX are 400ms x 3, which is nothing special, so unless you have intermediate Layer 1 devices to detect failure in, I don't think mixing OAM and G.8032 really buys you BFD-like performance. 

I'm hoping this will be improved in the future - I seem to recall Extreme's EAPS clocking in at a order of magnitude or two quicker.

Cheers,

Ben

On 01/06/2012, at 10:21 PM, Ben Boyd wrote:

> Experts, 
> 
> Does anyone out there have any working G.8032 ethernet ring w/ OAM backend configurations/implementations?
> 
> 
> I setup an 8 switch (EX/MX mix) ring in the lab and OAM seems to be complicating things rather than acting like a layer 2 BFD. 
> 
> 
> When I fail a node (not the ring owner) without OAM configured in just a plain G.8032 ring, the convergence time is around 30 seconds. (Seems a bit high.  I've seen better times with RSTP)
> 
> When I fail a node (not the ring owner) with OAM configured, 50-70% of the ring goes to discarding and fluctuates from there, never ultimately converging. 
> 
> Link failures on the other hand, converge in about 45ms.
> 
> 
> 
> If you need configs I can post them, but they're pretty vanilla (from the config examples on Juniper's site).
> 
> 
> 
> -----------------------------------
> Ben Boyd
> ben at sinatranetwork.com
> http://about.me/benboyd
> 
> 
> 
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>