From personal experience, there is no noticable degradation of performance, using Transition Networks media converters versus manufacturer-provided 100FX connections. I ran tests years ago with Cisco 2924C XL switches, and with 3Com SuperStack II 3000 and 3300 switches with 100FX modules. Cisco to Cisco, 3Com to 3Com, Cisco to 3Com, both through the manufacturer's own 100FX ports and through Transition Networks Fast Ethernet media converters. Could not measure a statistically significant difference in one switch port and out the one with fiber. (All switches were configured to use "store-and-forward" versus "cut-through" switching, for purposes of benchmarking. This was just to test the throughput of one connection over fiber, not the whole switch. )
We have lots of K-12 schools running 100-megabit full duplex links between buildings over dark fiber, 2 to 20km, no problem. Also have several ISPs sending 100-megabit full duplex feeds to customers, out to 40km, no problem. (The ISP controls and monitors the bandwidth in the Cisco 10/100 Ethernet port at their end.) One of our customers has a 100-megabit full duplex feed carrying Internet2 traffic over a 75km point-to-point link, no problem at all.
The flexability and versatility of the media converter approach far outweighs the additional point of failure, in my opinion. Buy a few spares, or implement some redundant links (HSRP, STP, or FEC), if you want to protect against failure.
And if you connect central switch over fiber to remote hubs, put bridging media converters out with the remote end so your fiber span can run at full duplex. (Remote switches and central switch can just use the regular media converters.)
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...