|
[an error occurred while processing this directive]
|
|
|
|
|
|
|
| ||||||
|
|
|
TELECOM
Answer: In almost all cases, these devices act as conduits and do not calculate the time using a hard-coded clock, so there is a minimal Y2K risk associated with routers, hubs and bridges. This general statement can also be extended to the primary data transfer capabilities of the Internet -- most TCP/IP devices will function fine in the new millennium. However, there are a lot of PCs, servers, workstations and minicomputers acting as TCP/IP routers or which forward IP traffic, and these are susceptible to Y2K problems; so be sure that you have checked the compliance of any device connected to your network.
Many have speculated that networking equipment, which measures the time it takes for other devices to respond to messages, will fail due to Year 2000. Most network devices don�t calculate the time using a date, rather they simply count the time since a packet was sent or received; these devices are Y2K compliant.
Some network devices do use a date, but they usually don�t use the date in a way that would cause a Y2K error. There are two reasons that this isn�t the case:
Of course, there are problems related to date errors, but they are largely confined to reporting and security. The application software or system programming downloaded to a network device can, in almost every instance of Y2K-noncompliance we found, be upgraded to function normally during 2000. Discontinued products are the only area where network device manufacturers may leave a customer hanging. Don�t assume your network hardware is compliant. Do check with the manufacturer to see if you need an upgrade. Some are making upgrading non-complaint hardware very easy. For instance, Bay Networks is offering trade-in rebates on non-compliant devices that range from $10 a port to $500 a port on high-end products. Here�s a list of the Y2K compliance information available from networking hardware companies:
|
|
|||||||||||||||||