Hi Victor, Something like this should do the trick once you've configured it on both ends:
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 We had a similar issue to solve at some sites connected via Free-Space Optics units. Cheers, Ben On 11 Jul 2014, at 12:45 pm, Victor Sudakov <v...@mpeks.tomsk.su> wrote: > Colleagues, > > I have pairs of EX4200 switches connected via third party MUXes. When > the actual physical medium goes down, the MUXes do not shutdown their > Ethernet interfaces. So I need some sort of point-to-point L2 link fault > management between the EX4200s. > > I thought OAM could be used for this purpose. However after reading > http://www.juniper.net/techpubs/en_US/junos9.4/topics/task/configuration/lfm-ethernet-oam-configuring-ex-series-cli.html > and references therein I am a bit confused. I don't need those > "remote-loopback" and "allow-remote-loopback" features, profiles and > other complicated stuff, do I? > > All I need from OAM is some kind of L2 keepalive. Do you have a good > configuration example? > > Thanks a lot for any input. > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > sip:suda...@sibptus.tomsk.ru > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp