Networks·41,424 discussions

What’s the use of having machines in a same collison domain?

Locked

Is there any advantage over let’s say having all the machines connected to an unique port in a switch? I can think of cost saving (by reducing no.of switches needed), can anyone think of anything other than that?

Topic

Clarifications

In reply to What’s the use of having machines in a same collison domain?

Clarifications

are you talking collision domains or port security

In reply to What’s the use of having machines in a same collison domain?

switches break up collision domains unlike hubs. each port on a switch is its own collision domain.

can’t see how having machines connected to a unique port on a switch will reduce the # of switches needed. Hosts have to connect to the network some way.

Thanks for ur reply

In reply to are you talking collision domains or port security

There’s a difference between “having all the hosts connect to a switch” rather than “having all the machines connected to a hub and then connecting hub the to a switch”, right? In the second case, I guess we save no.of ports needed to just to one.That’s what I meant as saving cost by machines in the same collison domain.{plz correct me if I’m wrong}

So my previous question was, is there any other advantage of having all the machines in a same collision domain?

hubs

In reply to Thanks for ur reply

nobody uses hubs anymore so your question is basically theoretical.

there are no advantages of having computers in the same collision domain. As the name implies, collisions occur because 2 or more hosts in the same collision domain try to send data over the wire at the same time. They both must stop, wait and try to retransmit. Further using a hub, broadcasts are flooded to all hosts within the collision domain. Hubs do not send traffic to a specific host.

[Author]

Replies