Networking Forums

Networking Forums > Network Hardware > Home Networking > Cable equivalents

Reply
Thread Tools Display Modes

Cable equivalents

 
 
Chris Watts
Guest
Posts: n/a

 
      11-07-2005, 04:53 PM
The literature that I can find on-line (Cisco) says that in planning a
100BaseT wired network, the maximum cable distance between devices should
not exceed 400m. If there is any repeater (switch or hub) in the path, then
this should be considered as contributing 95m to the length. But what
happens if there is a wireless link or access point in the route? How much
cable should this be considered equivalent to?

TIA
Chris



 
Reply With Quote
 
 
 
 
Rob Morley
Guest
Posts: n/a

 
      11-07-2005, 06:19 PM
In article <dko4as$qds$(E-Mail Removed)>,
(E-Mail Removed) says...
> The literature that I can find on-line (Cisco) says that in planning a
> 100BaseT wired network, the maximum cable distance between devices should
> not exceed 400m. If there is any repeater (switch or hub) in the path, then
> this should be considered as contributing 95m to the length. But what
> happens if there is a wireless link or access point in the route? How much
> cable should this be considered equivalent to?
>

There isn't a cable equivalent - the Ethernet limitations are down to
timing issues with signal propagation on the cable, and the cable stops
where it meets the wireless device.
 
Reply With Quote
 
Alex Fraser
Guest
Posts: n/a

 
      11-08-2005, 12:03 AM
"Chris Watts" <(E-Mail Removed)> wrote in message
news:dko4as$qds$(E-Mail Removed)...
> The literature that I can find on-line (Cisco) says that in planning a
> 100BaseT wired network, the maximum cable distance between devices should
> not exceed 400m. If there is any repeater (switch or hub) in the path,
> then this should be considered as contributing 95m to the length.
> But what happens if there is a wireless link or access point in the
> route? How much cable should this be considered equivalent to?


The reason for the limit you mention is to do with collision detection, and
applies only to devices within a collision domain. A collision domain is a
single, half-duplex Ethernet network. Collision domains end at bridges.

A switch is not a repeater, it is a bridge. If, for example, you use two APs
to join two wired networks, each of those APs is a bridge. Thus the limit
does not apply in either of these cases.

Alex


 
Reply With Quote
 
Chris Watts
Guest
Posts: n/a

 
      11-08-2005, 07:27 AM
"Alex Fraser" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed). uk...
> "Chris Watts" <(E-Mail Removed)> wrote in message
> news:dko4as$qds$(E-Mail Removed)...
> > The literature that I can find on-line (Cisco) says that in planning a
> > 100BaseT wired network, the maximum cable distance between devices

should
> > not exceed 400m. If there is any repeater (switch or hub) in the path,
> > then this should be considered as contributing 95m to the length.
> > But what happens if there is a wireless link or access point in the
> > route? How much cable should this be considered equivalent to?

>
> The reason for the limit you mention is to do with collision detection,

and
> applies only to devices within a collision domain. A collision domain is a
> single, half-duplex Ethernet network. Collision domains end at bridges.
>
> A switch is not a repeater, it is a bridge. If, for example, you use two

APs
> to join two wired networks, each of those APs is a bridge. Thus the limit
> does not apply in either of these cases.
>
> Alex

Thanks Alex. I can understand and appreciate that. Indeed I do now see
that two wireless APs will act as a bridge hence what you say must be true.
But CISCO definitely disagree with you about a switch being a bridge - they
say it is a repeater (albeit a selective one) and hence contributes a
latency equivalent to 95m of
cable - their figures.

Chris



 
Reply With Quote
 
Alex Fraser
Guest
Posts: n/a

 
      11-08-2005, 10:20 AM
"Chris Watts" <(E-Mail Removed)> wrote in message
news:43706179$0$63076$(E-Mail Removed)...
[snip]
> Thanks Alex. I can understand and appreciate that. Indeed I do now see
> that two wireless APs will act as a bridge hence what you say must be
> true. But CISCO definitely disagree with you about a switch being a
> bridge - they say it is a repeater (albeit a selective one) and hence
> contributes a latency equivalent to 95m of cable - their figures.


You must be misinterpreting what you've read, or what you've read is wrong.
Switches do contribute latency, but that latency is irrelevant from the
point of view of collision detection because it doesn't appear within a
collision domain.

What exactly have you read?

Alex


 
Reply With Quote
 
Chris Watts
Guest
Posts: n/a

 
      11-08-2005, 01:27 PM
"Alex Fraser" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "Chris Watts" <(E-Mail Removed)> wrote in message
> news:43706179$0$63076$(E-Mail Removed)...
> [snip]
> > Thanks Alex. I can understand and appreciate that. Indeed I do now see
> > that two wireless APs will act as a bridge hence what you say must be
> > true. But CISCO definitely disagree with you about a switch being a
> > bridge - they say it is a repeater (albeit a selective one) and hence
> > contributes a latency equivalent to 95m of cable - their figures.

>
> You must be misinterpreting what you've read, or what you've read is

wrong.
> Switches do contribute latency, but that latency is irrelevant from the
> point of view of collision detection because it doesn't appear within a
> collision domain.
>
> What exactly have you read?
>
> Alex

See 100BaseT cabling guidelines
in
http://www.cisco.com/en/US/products/..._installation_
guide_chapter09186a008007eb00

Chris


 
Reply With Quote
 
Alex Fraser
Guest
Posts: n/a

 
      11-08-2005, 11:30 PM
"Chris Watts" <(E-Mail Removed)> wrote in message
news:4370b619$0$82637$(E-Mail Removed)...
> "Alex Fraser" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > "Chris Watts" <(E-Mail Removed)> wrote in message
> > news:43706179$0$63076$(E-Mail Removed)...

[snip]
> > > But CISCO definitely disagree with you about a switch being a bridge
> > > - they say it is a repeater (albeit a selective one) and hence
> > > contributes a latency equivalent to 95m of cable - their figures.

> >
> > You must be misinterpreting what you've read, or what you've read is
> > wrong.

[snip]
> > What exactly have you read?

>
> See 100BaseT cabling guidelines
> in
>

http://www.cisco.com/en/US/products/..._installation_
> guide_chapter09186a008007eb00


For some reason (cookies probably) that link didn't work, but searching for
"100BaseT cabling guidelines" on Cisco's site resulted in the same URL but
working...

The only source of confusion I can see is that the document is talking about
modules that can be added to a Catalyst 2820. In its basic form the 2820
appears to be a 25 port 10BASE-T switch, but some of the modules are
repeaters - these are distinguished by the term "shared".

Alex


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Computer shuts down when I connect my cable modem through the ethernet cable Jeffrey W. Bowen Broadband Hardware 2 12-06-2008 05:22 PM
Connecting a *cable* router to an AOL *cable* modem (NTL cable) Martin Underwood Broadband 9 01-07-2007 12:01 PM
Connecting a *cable* router to an AOL *cable* modem (NTL cable) Martin Underwood Home Networking 9 01-07-2007 12:01 PM
Can I use/convert the broadband thick white cable as cat5 cable? none Broadband 18 07-01-2005 09:18 PM
Can I convert a FastCat5e network cable into a crossover cable? Sherri & Garry January Windows Networking 10 10-30-2003 04:19 AM



1 2 3 4 5 6 7 8 9 10 11