Jonathan Kaplan
asked on
one Cat5 run or two: Is there any difference?
I've had a discussion with a co-worker about a potential job. The client wants to run a second Cat5 cable between an MDF and IDF in one of his stores. The distance is almost 250ft and the pathway is difficult. If there are switches at both locations and, to save time and money, we use a hub at both locations to split the signal and plug into the proper switch ports, is there any difference to the NOC's view or management of the system? That is, other than the single common point of failure represented by the one CAT5 cable?
If there are switches at both locations and, to save time and money, we use a hub at both locations to split the signal and plug into the proper switch ports, is there any difference to the NOC's view or management of the system?
Don't do that. You will be increasing collision domain, going from full duplex to half-duplex and decreasing the throughput.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You don't mention what switches you are using.
I would suggest replacing the existing line with two cat6 runs, you can use the existing run as a pull cable. Run a pull line along with the new cat6 runs - if you lose a line you'll be able to replace easily.
then use Link Aggregation to combine two ports on each switch.
I would suggest replacing the existing line with two cat6 runs, you can use the existing run as a pull cable. Run a pull line along with the new cat6 runs - if you lose a line you'll be able to replace easily.
then use Link Aggregation to combine two ports on each switch.
ASKER
Thanks for reminding me why it's not a good idea.
So you would only run a second cable to belt and suspender the first.