(usr-tc) NOTICE - HiPerARC Service Release 4.1.22 (posting complete)
3Com Customers, HiPerARC Service Release v4.1.22 has been posted to the TotalService website ( http://totalservice.3com.com) and the Software Compatibility Matrix has been updated. HiPer ARC 4.1.22 resolves many problems found since 4.1.59-6 including HiPerbomb DOS Attack and SNMP community string security hole. For more information on the details of this Service Release, please reference the release notes. Both the code and release notes can be found on TotalService in the following location: http://totalservice.3com.com/cgi-bin/w3com/start?totalservice+software ( search by Total Control Hubs : Hiper ARC ) This code will be free for download for 90 days. After that 90 days, it will be only be available to customers with a valid service contract. If there are any questions or concerns regarding these changes, please contact 3Com Technical Support toll-free at 1-800-231-8770. If you are calling from an area not handled by this number, the TotalService website has contact information for other countries and regions. Please go to the TotalService website and click on 'Contacting Tech Support' for more information. Chuck Stace Customer Service Product Planning Chuck_Stace@3com.com - 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.
What if we have 4.1.32, should we upgrade/downgrade to 4.1.22? Chuck Stace wrote:
3Com Customers,
HiPerARC Service Release v4.1.22 has been posted to the TotalService website ( http://totalservice.3com.com) and the Software Compatibility Matrix has been updated.
HiPer ARC 4.1.22 resolves many problems found since 4.1.59-6 including HiPerbomb DOS Attack and SNMP community string security hole.
For more information on the details of this Service Release, please reference the release notes. Both the code and release notes can be found on TotalService in the following location:
http://totalservice.3com.com/cgi-bin/w3com/start?totalservice+software ( search by Total Control Hubs : Hiper ARC )
This code will be free for download for 90 days. After that 90 days, it will be only be available to customers with a valid service contract.
If there are any questions or concerns regarding these changes, please contact 3Com Technical Support toll-free at 1-800-231-8770. If you are calling from an area not handled by this number, the TotalService website has contact information for other countries and regions. Please go to the TotalService website and click on 'Contacting Tech Support' for more information.
Chuck Stace Customer Service Product Planning Chuck_Stace@3com.com
- 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.
-- Richard Lorbieski - richard@alpha1.net Chief Technical Officer - Senior System Administrator Alpha1 Internet http://www.alpha1.net 409.731.8236 - 877.4.alpha1 (877.425.7421) - 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.
On Thu, 6 Jan 2000, Richard Lorbieski wrote:
What if we have 4.1.32, should we upgrade/downgrade to 4.1.22?
There are two release trains, the 4.1 train and the 4.2 train. You're probably running 4.2.32-1, so you would not want to upgrade. The 4.2 train adds OSPF, but the 4.1 train is more stable. Brian - 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.
Is the only difference between 4.1 and 4.2 OSPF? ----- Original Message ----- From: "Brian Elfert" <brian@citilink.com> To: <usr-tc@lists.xmission.com> Sent: Thursday, January 06, 2000 3:53 PM Subject: Re: (usr-tc) NOTICE - HiPerARC Service Release 4.1.22 (posting complete)
On Thu, 6 Jan 2000, Richard Lorbieski wrote:
What if we have 4.1.32, should we upgrade/downgrade to 4.1.22?
There are two release trains, the 4.1 train and the 4.2 train.
You're probably running 4.2.32-1, so you would not want to upgrade.
The 4.2 train adds OSPF, but the 4.1 train is more stable.
Brian
- 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.
|-----Original Message----- |From: owner-usr-tc@lists.xmission.com |[mailto:owner-usr-tc@lists.xmission.com]On Behalf Of Mike Wilker |Sent: Thursday, January 06, 2000 4:17 PM |To: usr-tc@lists.xmission.com |Subject: Re: (usr-tc) NOTICE - HiPerARC Service Release 4.1.22 (posting |complete) | | |Is the only difference between 4.1 and 4.2 OSPF? | | For the most part.. There is also support for Frame-Relay, and ATM NICS.. -M - 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.
Thus spake Mike Wilker
Is the only difference between 4.1 and 4.2 OSPF?
And added a couple of new NIC types, one with 2 v.35 wan ports, and one with 4 t1 ports with integrated CSU/DSU...you sacrifice one of your fast ethernet's to get these. Also...as part of adding those NICs, they added frame-relay support. For most people...OSPF is the only real change...and to be honest, I'm not real keen on running OSPF yet...its still rather rough around the edges. -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456 - 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.
What if we have 4.2.32-1? (ne040232.dmf) --Rich Adams, President, Dayton Internet Services Inc., Dayton, Ohio-- --w8mfd@dayton.net--www.dayton.net--www.dayton.com--937-586-2500-- On Thu, 6 Jan 2000, Richard Lorbieski wrote:
What if we have 4.1.32, should we upgrade/downgrade to 4.1.22?
Chuck Stace wrote:
3Com Customers,
HiPerARC Service Release v4.1.22 has been posted to the TotalService website ( http://totalservice.3com.com) and the Software Compatibility Matrix has been updated.
HiPer ARC 4.1.22 resolves many problems found since 4.1.59-6 including HiPerbomb DOS Attack and SNMP community string security hole.
For more information on the details of this Service Release, please reference the release notes. Both the code and release notes can be found on TotalService in the following location:
http://totalservice.3com.com/cgi-bin/w3com/start?totalservice+software ( search by Total Control Hubs : Hiper ARC )
This code will be free for download for 90 days. After that 90 days, it will be only be available to customers with a valid service contract.
If there are any questions or concerns regarding these changes, please contact 3Com Technical Support toll-free at 1-800-231-8770. If you are calling from an area not handled by this number, the TotalService website has contact information for other countries and regions. Please go to the TotalService website and click on 'Contacting Tech Support' for more information.
Chuck Stace Customer Service Product Planning Chuck_Stace@3com.com
- 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.
--
Richard Lorbieski - richard@alpha1.net Chief Technical Officer - Senior System Administrator Alpha1 Internet http://www.alpha1.net 409.731.8236 - 877.4.alpha1 (877.425.7421)
- 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.
|-----Original Message----- |From: owner-usr-tc@lists.xmission.com |[mailto:owner-usr-tc@lists.xmission.com]On Behalf Of Dayton Internet |Sent: Thursday, January 06, 2000 3:58 PM |To: usr-tc@lists.xmission.com |Subject: Re: (usr-tc) NOTICE - HiPerARC Service Release 4.1.22 (posting |complete) | | |What if we have 4.2.32-1? (ne040232.dmf) | 4.2 has the security fixes in it. You do not need to go back to 4.1.22 to get them. If you are experiencing problems with 4.2.32 and you do not need OSPF you may consider moving to the 4.1.22 code. There are instructions included in the ZIP file that discuss the REQUIRED configuration deletion when downgrading code versions. -M - 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.
Don't all versions of the total control units have the ability to assign dns numbers to callers? We have a unit with a netserver, nmc and using quad modems that appears to not be assigning it. I thought they all had the capability for the past couple of years. Thanks, Greg Coffey <gcoffey@vcn.com> Visionary Communications V 307-234-5443 F 307-234-5446 100 N. Center #100, Casper, WY 82601 www.vcn.com - 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.
Thus spake Greg Coffey
Don't all versions of the total control units have the ability to assign dns numbers to callers? We have a unit with a netserver, nmc and using quad modems that appears to not be assigning it. I thought they all had the capability for the past couple of years.
Depends on how far back you want to go to consider it "all." :) Assigned DNS (and WINS) nameservers via IPCP negotiation was written as an informational RFC (note, not standards track) after the original NETServer came out...so...you can go far enough back to not have the support for that...but I seriously doubt you have code that old. :) -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456 - 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.
Auto assigning DNS: I have never got this to work. What is the procedure? KLT -----Original Message----- From: owner-usr-tc@lists.xmission.com [mailto:owner-usr-tc@lists.xmission.com]On Behalf Of Jeff Mcadams Sent: Thursday, January 06, 2000 10:41 PM To: usr-tc@lists.xmission.com Subject: Re: (usr-tc) DNS Server Assigned Question Thus spake Greg Coffey
Don't all versions of the total control units have the ability to assign dns numbers to callers? We have a unit with a netserver, nmc and using quad modems that appears to not be assigning it. I thought they all had the capability for the past couple of years.
Depends on how far back you want to go to consider it "all." :) Assigned DNS (and WINS) nameservers via IPCP negotiation was written as an informational RFC (note, not standards track) after the original NETServer came out...so...you can go far enough back to not have the support for that...but I seriously doubt you have code that old. :) -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456 - 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.
4.1.32 is older code 4.1.22 is newer code. If you are talking about 4.2.32 then its totally a different code. Use 4.2.32 if you want to use ospf. Else you are better off with 4.159 or 4.1.22 code. 4.1.59 has security holes which 4.1.22 fixes. krish On Thu, 6 Jan 2000, Richard Lorbieski wrote:
What if we have 4.1.32, should we upgrade/downgrade to 4.1.22?
Chuck Stace wrote:
3Com Customers,
HiPerARC Service Release v4.1.22 has been posted to the TotalService website ( http://totalservice.3com.com) and the Software Compatibility Matrix has been updated.
HiPer ARC 4.1.22 resolves many problems found since 4.1.59-6 including HiPerbomb DOS Attack and SNMP community string security hole.
For more information on the details of this Service Release, please reference the release notes. Both the code and release notes can be found on TotalService in the following location:
http://totalservice.3com.com/cgi-bin/w3com/start?totalservice+software ( search by Total Control Hubs : Hiper ARC )
This code will be free for download for 90 days. After that 90 days, it will be only be available to customers with a valid service contract.
If there are any questions or concerns regarding these changes, please contact 3Com Technical Support toll-free at 1-800-231-8770. If you are calling from an area not handled by this number, the TotalService website has contact information for other countries and regions. Please go to the TotalService website and click on 'Contacting Tech Support' for more information.
Chuck Stace Customer Service Product Planning Chuck_Stace@3com.com
- 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.
--
Richard Lorbieski - richard@alpha1.net Chief Technical Officer - Senior System Administrator Alpha1 Internet http://www.alpha1.net 409.731.8236 - 877.4.alpha1 (877.425.7421)
- 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.
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.
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.
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.
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.
Good point...how do I add an entry fon an NTP server? ---Marius
-----Original Message----- From: owner-usr-tc@lists.xmission.com [mailto:owner-usr-tc@lists.xmission.com]On Behalf Of Clayton Zekelman Sent: Friday, January 07, 2000 9:48 AM To: usr-tc@lists.xmission.com 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.
- 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.
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.
Thus spake Kevin Benton
Due to this fact, I would strongly suggest that 3Com 1) fix this problem in NTP on the NSC 3.8.1 code,
Too bad they don't have source code to the NETServer/ComOS based code anymore to be able to make such fixes. If this turns out to be true...and I haven't a clue if it is or not...I saw another post indicating that this might not be a problem...perhaps 3Com will finally do the right thing for people with NETServers. Hah...fat chance, I know...but I can dream. -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456 - 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.
Did you do a reset time on the netserver after setting up the NTP server? krish On Fri, 7 Jan 2000, Kevin Benton wrote:
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.
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.
Hmmm, we have 10 units operating at the moment, all using NTP, and they're all spot on. This must either be a really obscure bug, or be configuration dependent.
would require new code for the NetServer. The 3Com case number for this problem is 154529.
Let us all know if they make new code available to fix it :-) ------------------------------------------------------------------------ Bob Purdon, Ground Floor, Marine Board Building Technical Manager (Tas/Vic), 1 Franklin Wharf, Tas 7000 Southern Internet Services. +61 (3) 6234 7444 - 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.
Hi, I haven't touched our one Netserver-based chassis for a while, and it's running: Total Control (tm) NETServer Card V.34/ISDN with Frame Relay V3.7.73 Build date: Mar 19 1998 Build time: 21:32:39 The date/time seems OK (synced via ntp): January 11, 2000 15:54:53 UT For the life of me I can't remember what the update fixed, though... Can someone refresh my memory? Thanks, Charles -- =-----------------= = | Charles Sprickman Internet Channel | | INCH System Administration Team (212)243-5200 | | spork@inch.com access@inch.com | = =----------------= On Sat, 8 Jan 2000, Bob Purdon (Lists) wrote:
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.
Hmmm, we have 10 units operating at the moment, all using NTP, and they're all spot on. This must either be a really obscure bug, or be configuration dependent.
would require new code for the NetServer. The 3Com case number for this problem is 154529.
Let us all know if they make new code available to fix it :-)
------------------------------------------------------------------------ Bob Purdon, Ground Floor, Marine Board Building Technical Manager (Tas/Vic), 1 Franklin Wharf, Tas 7000 Southern Internet Services. +61 (3) 6234 7444
- 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.
participants (17)
-
Bob Purdon (Lists) -
Brian Elfert -
Charles Sprickman -
Cheryl Johnson -
Chuck Stace -
Clayton Zekelman -
Dayton Internet -
Greg Coffey -
Jamie Orzechowski -
Jeff Mcadams -
Kevin Benton -
Kevin Tucker -
Marius Kirschner -
Mike Wilker -
Mike Wronski -
Richard Lorbieski -
Tatai SV Krishnan