I've got a PCI LanStreamer in my NT domain controller and its been up continuous for about 6 months now (i.e. since the day it was installed and powered up...)
If you've got thousands of feet of cable and a couple of hundred stations on one ring THAT explains your beaconing problems - you're GROSSLY out of spec on allowable cable length - particularly if you try to run that lashup at 16mbps. With all ICS at 4mbps it *might* work sometimes...
"Since the unamplified distance between to NCs is limited this can lead to the "Token Ring Sleeps at Night" Problem, where the token Ring refused to work at night (simply because too many employes turn off there PC after work) "
When you break the rules, you pay the price;-> There are conversin factors for making cable length calculation allowances. ex. MAU is about 15-20' of cable (I've forgotten which), etc.
Stay within the design parameters and you would have been OK.
What about the 4/16/100 Madge and IBM cards? If someone invested in 8228 MAU's all they need to to go to 100mbps T/R is change the cards. Their existing hubs and ICS cabling from 12 years ago STILL WORK FINE
Don't know where you get your info, but its a defective source. T/R architecturally is designed to allow for machines being turned on/off and cables being plugged and unplugged with no impact to the system.
I personally use the old shielded ICS cabling system because of its extreme noise immunity and ability to handle exceptionally long runs of cable (compared to any Ethernet)
If you've got 15K workstations, you need the architectural stability and guaranteed throuput of T/R anyway...
(On a loaded LAN I've personally benchmarked a 4mbps ring with a 486 based server keeping pace with a 100mbps Ethernet and a dual PII server at Prudential) The Ethernet collapsed but the T/R kept on trucking and hauling the goods.
Slashdot Mirror
I've got a PCI LanStreamer in my NT domain controller and its been up continuous for about 6 months now (i.e. since the day it was installed and powered up...)
If you've got thousands of feet of cable and a couple of hundred stations on one ring THAT explains your beaconing problems - you're GROSSLY out of spec on allowable cable length - particularly if you try to run that lashup at 16mbps. With all ICS at 4mbps it *might* work sometimes...
"Since the unamplified distance between to NCs is limited this can lead to the "Token Ring Sleeps at Night" Problem, where the token Ring refused to work at night (simply because too many employes turn off there PC after work) " When you break the rules, you pay the price ;-> There are conversin factors for making cable length calculation allowances. ex. MAU is about 15-20' of cable (I've forgotten which), etc.
Stay within the design parameters and you would have been OK.
What about the 4/16/100 Madge and IBM cards? If someone invested in 8228 MAU's all they need to to go to 100mbps T/R is change the cards. Their existing hubs and ICS cabling from 12 years ago STILL WORK FINE
Protocols that architecturally murder data are brain damaged.
Don't know where you get your info, but its a defective source. T/R architecturally is designed to allow for machines being turned on/off and cables being plugged and unplugged with no impact to the system. I personally use the old shielded ICS cabling system because of its extreme noise immunity and ability to handle exceptionally long runs of cable (compared to any Ethernet)
If you've got 15K workstations, you need the architectural stability and guaranteed throuput of T/R anyway... (On a loaded LAN I've personally benchmarked a 4mbps ring with a 486 based server keeping pace with a 100mbps Ethernet and a dual PII server at Prudential) The Ethernet collapsed but the T/R kept on trucking and hauling the goods.
100mbps T/R has been around for a while now. Even a 16mbps ring will perform QUITE favorably against 100mbps Ethernet when loads go up.