Network topology???

I was doing a little reading on network topology,and everything's pretty clear to me but one thing.What,if any,advantages does the ring topology have over the star topology?I guess there must be something I'm missing.

As you know in a ring if the cable fails then the whole network may become useless.In a star connection it requires more cable and hub.But failure in the cable will only effect the corresponding machine.But if the hub fails the network too fails. Hope this is some help.

What about speed?It seems a ring topology would be slower than a star because the token is constantly running around in a circle(well sort of).

Well with the ring topology you're 100% that there will be no collision because the device as to wait for the token to send data

look here

Yes this is true ...
But as there is less change of collision there is also more chance of "junk" staying on the ring and slowing down the network (I see a lot of that here at my job) ... then you have to try and locate where it comes from or came from.
There are not alot of advantages in the ring topology.

Gr33tz,

Cemetric

Yeah it's mostly about collision avoidance....
It's pretty much concidered deprecated...

Ammo

There is also a FDDI ring architecture which offers some benefits over the standard ring topolgy, although has the big drawback of cost, and also is better served as the backbone for a network. Still, thought I`d mention it as it is a ring topolgy of sorts.

Ring topology is an advantage for a few machine and high speed links, but otherwise use the star top or something like hub and spoke top. The star is prefferable since the pcs don't have to wait for the token to arrive... Supppose you are dl a 600mgs for a movie and the guys next to you is trying to get a email to his provider .... guess what will happen if the dl starts first.

Star also can take advantages of multi bw capacity and ddr depanding upon the links that you are using and can optimize it too.
check out http://www.cisco.com/en/US/products/...0800e955d.html
btw star top is the most common top used

There is also something to be said for ease of troubleshooting on a ring network. From what I understand, if a node fails, it's pretty easy to determine where the failure occurred (i.e. "I can ping up to this machine, but not beyond it."). Here are some other advantages for a standard ring topology that I found here:

Quote:

---

* Very orderly network where every device has access to the token and the opportunity to transmit
* Performs better than a star topology under heavy network load

---

I don't think you have to worry much about collisions like you used to as most star topologies are now useing switches instead of hubs which drasticly reduces collision possiblity.

a very imortant thing about ring to remember is that the performance of the overall network degrades gracefully instead of just crashing when overloaded (it slows down a lot but not stop) ... this is very imortant in high priority networks (think hospitals, millitary)

The Star topology has, for the most part, replaced the ring topology. However let's look at each in a little depth and see the evolution of where they came from.

First, let's not confuse our physical layer protocol with our network protocol. So I can use TCP/IP and at the physical layer it can be transported on Ethernet which is a collision topology, ATM, FDDI, or many other physical layer protocols.

At one time (late 80's/early 90's) the star topology was a weak topology because the hierarchy was not advanced enough to support larger networks. Routers sucked and switching was not available so if you had 20 computers on a network anytime one of them sent a message out the connection from all of them were blocked for that short period of time. The more computers the greater the chance of collision and the need for retransmission was. The accepted max on a network was around 120 while the suggested was no more than 24. The main method for segmenting a network was the bridge (see also brouter for an interesting historical term) which for star systems was fairly expensive. Routers were available but most didn't work well or were very unstable.

At this same time the Token Ring topology came out. Because it did not use a CSMAC/CD (Carrier Sensing Media Access Control/Collision Detection) system like Ethernet does it could use a higher percentage of the bandwidth. For comparison Ethernet can use up to about 60% of its rated bandwidth before collisions start reducing the effectiveness of the network while Token Ring can effectively use 95% of its rated bandwidth. This is sustained usage not burst or spike.

The way Token Ring operates is that each system when it enters the network sends out a token announcing it presence and it locates its down stream neighbor and its upstream neighbor. Then it becomes part of the ring. Assume the ring has 3 computers on it A,B,C. The ring is established so A sends a message and at the end of the message passes the token along. B gets the message, uses it if needed, retransmits it, finds the token and adds its own message. C receives A's, reads, retransmits, receives B's, reads, retransmits, sees token and adds its own message. A receives its own removes it from the ring, receives B's, reads, retransmits, receives C's, reads, retransmits, sees token and can add its own packet. This continues. No collisions ever happen because the retransmit is always to the next computer up the chain and everything runs like a train.

If two networks have to connect then one of the devices must operate as a Bridge or Gateway (bridge if between like systems, gateway if between dis-similar systems). With this scenario if Ring A wants to communicate with Ring B it sends the message around which is checked and retransmitted on Ring A until it reaches the bridge. The bridge then retransmits it on A and B however on B it makes itself the sending agent. On ring A the packet is removed when it returns to its owner on Ring B it is removed when it returns to the bridge. In this way every device that could possibly want the packet gets it on both rings.

In this manner the original 4 Mbps Token ring could operate as fast or faster than a 10 Mbps Ethernet. When the 16 Mbps Token ring came out it blew the Ethernet out of the water for speed and capability. The drawbacks, however, were that any time a machine was added or removed the ring had to be broken. Ring restoration is fairly quick but this meant that if one system went down the ring went down until it was removed or replaced. However, Token Ring proved to be extremely reliable once set up properly. I have never set one up but what I was told by a few experts is that it was difficult to get them working exactly right but once they were they seemed to work forever or until messed with.

In an attempt to fix some of the inherent problems with the ring the dual ring topology was implemented. FDDI is the best example of the dual ring and while I have worked with FDDI and it seems viable I loathe it with a passion. The theory here is that there is a primary and secondary ring. Data flows on the primary only while the secondary merely maintains itself with beacon packets going in the opposite direction of the Primary ring. If a station goes down then the neighbors to that station loop the primary to the secondary and a single ring is created to re-establish a path. This way hardware can be removed or added and the ring will self heal itself and re-establish full operation automatically. In practice where I worked FDDI proved to be unstable at times and very difficult to troubleshoot. Also its speed (100 Mbps) and range (total ring distance of 100 Km) were overwhelmed by ATM and Gigabit Ethernet (Thank God).

Now with the advent of cheap hubs, switches, routers, and the ASIC (Application Specific Integrated Circuits) the Star topology is much better than the ring. Devices can be added and removed without affecting the topology. Collision domains can be easily created to limit network interference. Troubleshooting becomes much simpler because you can trace from router to switch to port and finally to device. The Star topology can also be built with easily created redundant pathways that lead to a more fault tolerant network. This has only been really available though in the last 5-8 years. Before that is when the real battle between Star vs Ring occurred.

Don't forget that there is a difference between a ring topology, and a token ring network. Although token ring networks are the most common implementation of the ring topology it is not necessarily the only one.

If you remove the 'token' from the ring topology, you get the benefit of always having at least two paths to every machine. Therefore, if one cable was cut all machines on the network could still communicate.

Ring topology is only around because companies can't afford or don't bother to replace it. That is why you see it intergrated into systems today.

Just a little tutorial I wrote on topologies
http://www.antionline.com/showthread...light=topology

The main problem was that it was proprietary (IBM I think) so it cost more. Saw some old token ring network cables they were thick with large connectors you could see why people would prefer to wire cat5 and save on cable.

cwk9, the thick cable had one advantage -> shielding

There are companies that still use Token Ring cables but now with Ethernet by placing so called "baluns" on the connectors. This means you do not need to replace all cables (for instance in walls, cielings, ... mostly in older buildings) but only place balun connectors to connect to the nowadays regular cat5e UTP cabling. So you are using your tokenring cables to run ethernet. (There is however no "convertor" from token ring to ethernet networks. To combine both network topologies You will need a pc acting like a router or bridge or a hardware bridge to accomplish such a task.)



Here's an interesting read about high speed token-ring solutions (100Mbit and gigabit)

This may be wrong, but I have been told that in a Ring Topology, all users get an equal share of the bandwidth. In a Star Topology, one user can bog down the network but taking all the bandwidth but I don't believe this is possible in a Ring Topology.

AcidBurn1213 every one gets an equal share of bandwidth unless it’s set other wise. Token Ring networks use a sophisticated priority system and permits certain user-designated priorities. So you would assign things like servers and your boss’s workstation a higher priority.

Hmmm, maybe I was thinking of a Token Ring network then. Either way I still had stuff screwed up.

well token may work for some but for me star works best all my systems have a direct connection to the router/ hub and i have not had as many peoblems with it. till something better comes out i will stick with it.

Acidburn I would have to agree with you on the star with many stipulations.

In a hub/sharing system everyone in the Collision Domain has access to the bandwidth at all times. Therefore since it is a first come first served basis a single computer on the network can bog down the entire network for everyone. This normally does not happen with standard data since it uses a connection oriented transmission control (TCP in TCP/IP). However many functions using a connectionless (UDP in the TCP/IP stack) protocol can flood the network and cause a DoS to other users. In fact this is the whole point between a DoS attack or a DDoS although these normally occur with incoming rather than generated data.

The most common cause of DoS on a shared star is a bad NIC. These often send runts and orphans or just flood the network. I have seen this on a number of occasions.

A switched Star does not fall prey to this if the switch is setup correctly. With a layer 3 switch data sent to a system on one port goes to that port only and does not affect traffic on the other ports. In this instance the only way to do a DoS to the entire Star would be to flood the backplane of the switch which generally has considerably higher bandwidth than any one port (ideally it would be equal to the max bandwidth of all ports, normally it is equal to the bandwith of more than 50% of the ports). A single port may be affected by bad NIC but not the entire switch.

Unfortunately since most DoS or DDoS attacks use UDP and broadcasts the switch is not as immune as one would like. Broadcasts are meant for every computer and therefore switches send the data to every port. This is where expensive switches with good ASICs (Application Specific Integrated Circuits) shine over cheaper switches. They can be set to block or forward certain types of Broadcast and Multicast signals.

I guess in short it is important to seperate the Topology from the capability and vulnerability. Topology is a layout scheme and currently the Star topology is King. Also don't forget that topologies can be mixed. I think the best overall topology set up is a Semi-Meshed topology for the backbone and a Star for the end users. So your connections between buildings, sites, etc. would not rely on one path but have a minimum of two paths so any one link could go down and no major location would be lost to the network. As you get down to the user level the added cost of meshing is not that critical. The time to remove a switch or fix an individual's problem is not as critical as that same time when fixing 100 people's problem.

So while you study topologies keep in mind you also have to think about implementation of that topology, mixing it with other topologies and implementations and then the protocols and methods used to access the physical topology (hierarchical/flat, Switched/Shared/Routed, Controlled Traffic/Collision Domain, etc). At first this may seem very confusing but think of it like putting lego's together: each lego is a piece of your network, a protocol, topology, or requirement. They can all (through the right equipment) connect to each other to build your network which is only limited by your imagination and what you seek to create.

Does any body even use Token Ring anymore?

Yes, there are a lot of Token Ring networks out there. They tend to be considered legacy now but they are still going. It follows the old, and wise, saying that if it isn't broken don't fix it.

Once a Token Ring network is set up and running they have proven to be very, very stable. So if you needs are fulfilled by a 4 or 16 Mbps network why spend thousands of dollars to switch to a 100 Mbps Ethernet setup which is going to really only effectively double or triple your real bandwidth. Most networks run great on 10 Mbps internally with a T-1 or less going out WAN. It is only in large networks (or in the dreams of us IT professionals) that the 100 Mbps+ networks are required.

I knew one person that wanted OC-12 (622 Mbps ATM) to his desktop. Why? There was no logical reason or requirement but that is what he wanted. Many networks are not designed to current, or even future, need but to current and future technology.

So, yes there are Token Ring networks still running. Lots of them. When you see one you will have to decide if it points to someone afraid to embrace technology (bad) or frugal and wise enough not rush to new technology for its own sake (good). However, the real question and one I cannot answer is: is anyone installing new Token Ring networks and can the equipment still be purchased?

A production comany in this area recently (in the last 3 years) installed a token ring in their plant. I don't know much of the details about it, but it was cheaper then a star/bus, and it works perfect. It allows the production macines to communticate properly, becuase they can not afford to have packet collisions which would mess up the timing on the machines, and it always works in a certain order (ie machine 1 always talkst to machine 2... and so on.