Both interface using same config as follow : ce1-2/0/0 { description "*** RouterA ***"; clocking external; e1-options { framing unframed; } no-partition interface-type e1; } e1-2/0/0 { description RouterA; mtu 4500; clocking external; encapsulation cisco-hdlc; unit 0 { family inet { address xxx.xxx.xxx.xxx/30; } family iso; family mpls; } }
And the other : e1-1/0/1 { description RouterB; mtu 4500; clocking external; encapsulation cisco-hdlc; e1-options { framing unframed; } unit 0 { family inet { address xxx.xxx.xxx.xxx/30; } family iso; family mpls; } } Transmission using DDF Rgrds, Faizal On Fri, Apr 17, 2009 at 2:53 PM, Sean Clarke <s...@clarke-3.demon.nl> wrote: > And on the other end ? > What is providing the clock ? > What is the box on the other side ? > If they are directly connected, i.e. no SDH or so in the middle ... try > clocking BOTH ends as internal. > > cheers > > > > > On 4/17/09 9:19 AM, Faizal Rachman wrote: > > i use external clocking. > > show configuration interfaces e1-2/0/0 > mtu 4500; > clocking external; > encapsulation cisco-hdlc; > unit 0 { > family inet { > address xx.xx.xx.xx/30; > } > family iso; > family mpls; > } > > On Fri, Apr 17, 2009 at 1:35 PM, Sean Clarke <s...@clarke-3.demon.nl>wrote: > >> On 4/17/09 8:15 AM, Faizal Rachman wrote: >> >> But if we ignore the restarted router, why should i have to unplug/plug E1 >> cable facing to peer router to make it work again. >> I believe that keepalive is kind of setting to make interface know while it >> is up or down. But after several times, link cannot revert back to normal >> until unplug/plug ritual. >> >> >> That should not happen IMO ... there must be something else up .. timing >> ? >> However are you clocking the circuit ? >> > > > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp