Hey..your right. Mine shows: Command> sh time January 23, 1900 21:45: 6 UT ----- Original Message ----- From: Clayton Zekelman <clayton@MNSi.Net> To: <usr-tc@lists.xmission.com> Sent: Friday, January 07, 2000 9:47 AM Subject: RE: (usr-tc) NetServer 3.8.1 not Y2K Compliant
If your Netserver isn't talking to your NTP server properly, it starts life out at 1900. From the date listed, thats what appears to be happening - February? Sounds to me like it was booted 2 months ago.
At 09:49 AM 1/7/00 -0500, you wrote:
Not here....I get:
Command> ver U.S. Robotics Total Control (tm) NETServer Card V.34/ISDN with Frame Relay V3.8.1 Build date: Aug 11 1998 Build time: 13:49:21
Network Interface Card: Ethernet & Frame Relay Combination (26) ISDN Interface Card : MUNICH32 (4) Packet Bus Circuit : Enhanced
Command> sho time February 27, 1900 0:40:15 UT
Strange, everything else is the same??
---Marius
-----Original Message----- From: owner-usr-tc@lists.xmission.com [mailto:owner-usr-tc@lists.xmission.com]On Behalf Of Jamie Orzechowski Sent: Friday, January 07, 2000 9:38 AM To: usr-tc@lists.xmission.com Subject: Re: (usr-tc) NetServer 3.8.1 not Y2K Compliant
looks fine on mine ...
Command> version U.S. Robotics Total Control (tm) NETServer Card V.34/ISDN with Frame Relay V3.8.1 Build date: Aug 11 1998 Build time: 13:49:21
Network Interface Card: Ethernet & Frame Relay Combination (26) ISDN Interface Card : MUNICH32 (4) Packet Bus Circuit : Standard
Command> show time January 7, 2000 14:36:20 UT
----- Original Message ----- From: Kevin Benton <s1kevin@tims.net> To: <usr-tc@lists.xmission.com> Sent: Friday, January 07, 2000 9:29 AM Subject: (usr-tc) NetServer 3.8.1 not Y2K Compliant
The NetServer 3.8.1 code running on two of our tc's is not Y2K Compliant. It's running NTP to accept the time from our time servers and shows the date to be incorrectly something with the year of 1900. Our HARC's are doing just fine via NTP. Want to find out if your netserver is reporting the date correctly? From the Command> prompt, type show time then Enter.
Due to this fact, I would strongly suggest that 3Com 1) fix this problem in NTP on the NSC 3.8.1 code, 2) implement a way to set the date and time from the CLI on the NSC, and 3) remove the YES next to the NetServer PRI 3.8.1 Y2K Compliance check statement until it's fixed. Both of these would require new code for the NetServer. The 3Com case number for this problem is 154529.
Kevin Benton Network Administrator SOTANet LLC, A Voyager.net Company
E-Mail: s1kevin@tims.net Web: http://users.sota-oh.com/~s1kevin/ Unsolicited advertisements processing fee: $50 subject to change without notice
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message.
For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.
--- Clayton Zekelman Managed Network Systems Inc. (MNSi) 875 Ouellette Avenue Windsor, Ontario N9A 4J6
tel. 519-985-8410 fax. 519-258-3009
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.