Ethernet Switching
Reply
Contributor
kshymkiw
Posts: 12
Registered: ‎10-21-2010
0
Accepted Solution

EX4200 - Simple OAM Configuration

[ Edited ]

Hello,

 

i am looking for a simple configuration of 802.3ah Ethernet OAM on an EX4200.  I have read the article (http://www.juniper.net/techpubs/en_US/junos9.4/topics/task/configuration/lfm-ethernet-oam-configurin...

 

I was not sure/aware if all the options need to be defined.  Would there be any downside to a simple configuration such as:

 

 

set protocols oam ethernet link-fault-management interface ge-x/x/x

set protocols oam ethernet link-fault-management interface ge-x/x/x link-discoverey active

set protocols oam ethernet link-fault-management interface ge-x/x/x pdu-interval 2

set protocols oam ethernet link-fault-management interface ge-x/x/x pdu-threshold 5

set protocols oam ethernet link-fault-management interface ge-x/x/x apply-action-profile CUST-PORT


set protocols oam ethernet link-fault-management action-profile CUST-PORT action syslog

set protocols oam ethernet link-fault-management action-profile CUST-PORT action link-down

set protocols oam ethernet link-fault-management action-profile CUST-PORT event link-adjacency-loss

 

 

 

am I missing anything or should this work?

Distinguished Expert
dfex
Posts: 783
Registered: ‎04-17-2008
0

Re: EX4200 - Simple OAM Configuration

That should work just fine.  I use an even simpler template to check for link-loss over some intermediate microwave links one of our customers has:

 

 

set protocols oam ethernet link-fault-management action-profile UDLD event link-adjacency-loss
set protocols oam ethernet link-fault-management action-profile UDLD action syslog
set protocols oam ethernet link-fault-management action-profile UDLD action link-down
set protocols oam ethernet link-fault-management interface ge-0/0/23.0 apply-action-profile UDLD

 

 

Ben Dale
JNCIP-ENT, JNCIS-SP, JNCIE-SEC #63
Juniper Ambassador
Follow me @labelswitcher
Contributor
kshymkiw
Posts: 12
Registered: ‎10-21-2010
0

Re: EX4200 - Simple OAM Configuration

Are you runing Juniper to Juniper 802.3ah, or are you interop with another Vendor?

 

In my scenario I would be interop with another Vendor (not a mjor one), and was wandering how Cross Vendor 802.3ah is working.

Distinguished Expert
dfex
Posts: 783
Registered: ‎04-17-2008
0

Re: EX4200 - Simple OAM Configuration

I have tested in the lab interop between Juniper, Extreme and MRV and it all works just fine.

Ben Dale
JNCIP-ENT, JNCIS-SP, JNCIE-SEC #63
Juniper Ambassador
Follow me @labelswitcher
Contributor
kshymkiw
Posts: 12
Registered: ‎10-21-2010
0

Re: EX4200 - Simple OAM Configuration

 


dfex wrote:

I have tested in the lab interop between Juniper, Extreme and MRV and it all works just fine.


 

Good to hear.  I went ahead and labbed it up yesterday.  I did have to change some Values, as my PDU Interval was too low.  The lowest you can go is 400 ms. 

 

I was able to get a working setup going.  Thanks for the help!

Contributor
kshymkiw
Posts: 12
Registered: ‎10-21-2010
0

Re: EX4200 - Simple OAM Configuration

Sample 802.3ah config for UDLD type applocations:

 

 

set protocols oam ethernet link-fault-management action-profile CUST-PORT event link-adjacency-loss
set protocols oam ethernet link-fault-management action-profile CUST-PORT action syslog
set protocols oam ethernet link-fault-management action-profile CUST-PORT action link-down

set protocols oam ethernet link-fault-management interface ge-0/0/x.0 apply-action-profile CUST-PORT
set protocols oam ethernet link-fault-management interface ge-0/0/x.0 pdu-interval 400
set protocols oam ethernet link-fault-management interface ge-0/0/x.0 link-discovery active
set protocols oam ethernet link-fault-management interface ge-0/0/x.0 pdu-threshold 10

 

This is assuming you want the EX4200 as active.  In my scenario we are using the EX4200 as an Agg. Switch, with CE devices connected to it, via a single fiber solution.  Thus we want the EX4200 as active, so it can drop it's link should it detect an error.

 

Copyright© 1999-2013 Juniper Networks, Inc. All rights reserved.