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 wrote:
> On 4/17/09 8:15 AM, F
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
On Friday 17 April 2009 12:04:31 pm Faizal Rachman wrote:
> Dear All,
> I have problem with J Series router which often restart.
Why does the router often restart? Bad power source?
Mark.
signature.asc
Description: This is a digitally signed message part.
__
I guess so because there are nothing notified in log message indicated with
chassis failure or something.
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
Dear All,
I have problem with J Series router which often restart.
But the problem is that I should unplug/plug port to peer router before link
came up. It is E1 interface.
Is there any knob that link automatically forced to retry or refresh so i
don't need to play physically.
Thank you.
Regards,
5 matches
Mail list logo
