RE: TIME

From: Christopher Larson (clarson@xxxxxxxxxxx)
Date: Tue Feb 06 2001 - 10:18:47 GMT-3


   
HAd the same problems using certificates to authenticate IPSEC peers. If the
router is ever rebooted you lose the time, the router things it's 91 and
invalidates all the certificates because they are stamped with 99 and you
have to go through the whole process of requesting a cert again.

-----Original Message-----
From: Devender Singh [mailto:devender.singh@cmc.cwo.net.au]
Sent: Monday, February 05, 2001 7:17 PM
To: Faris Broussard; ccielab@groupstudy.com
Subject: RE: TIME

As for I know ntp would be the only solution fro router like 2500, As they
donot have battery backup cmos clock circuit to keep clock ticking.

But I think it is good point to note down your discovery (obvious but could
trip us in the lab) " i.e., if we have timed key-chains configured and we
reboot the router, routing protocol will not work because of
authentication".

Devender Singh
BE(Hons), CCNP
IP Solution Specialist

-----Original Message-----
From: Faris Broussard [mailto:FarisB@globaldatasys.com]
Sent: Tuesday, 6 February 2001 10:07
To: ccielab@groupstudy.com
Subject: TIME

Is there anyway to hardcode the time on a 2500 router with out using ntp? If
your using time sensitive stuff( in my case key chains) when you reboot the
router your stuck in 1993 again( and rip stops working.)
        Thanks

        Faris Broussard
        CCDA CCNP R/S + Security
        Global Data Systems
        Advanced Network Design, Implementation and Management
        Cisco Systems Gold Partner
        HP Openview Gold Partner
        www.GetGDS.com



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:38 GMT-3