We are in a testbed configuration, trying to make a system work before it is deployed to the field. Fairly simple configuration, 4 switches, the plan is to have fiber running between them to make a ring (1->2, 2->3, 3->4, 4->1), various end node computers connected to each switch. Switches are configured to factory defaults. The two trunk lines in each switch (ports 47 & 48) are configured with a Cisco Switch role using the Smartports capability of the configuration tool. Because we are in a testbed situation, we can run copper trunk lines between the systems as well for testing purposes. We are using GLC-GE-100FX SPF modules for the fiber interface. There is not much network traffic in our testbed configuration.
When we use all copper for our trunk lines, everything is fine. The ports autonegotiate 1000Mbps, full-duplex. We never get collisions. When we use the fiber, the ports appear to autonegotiate 100Mbps, half-duplex. The port state ultimately ends up with "port as a faulty link". How quickly it reaches that state appears to be related to how many of the trunk lines are fiber (vs. copper). I believe the cause is that we begin registering collisions and I am assuming that the switch sees enough collisions to register a faulty link condition. I do not seem to be able to configure the trunk lines for full-duplex. Duplex doesn't even appear to be an option I can set. The commands I'm using are:
#configure terminal
#interface gi0/48
#duplex full <--- this one fails as an invalid command
I'm speculating that if I could get the port to be full duplex, which according to the SPF module documentation is supported, things would work just fine. At this point, I'm stumped. Any thoughts?
When we use all copper for our trunk lines, everything is fine. The ports autonegotiate 1000Mbps, full-duplex. We never get collisions. When we use the fiber, the ports appear to autonegotiate 100Mbps, half-duplex. The port state ultimately ends up with "port as a faulty link". How quickly it reaches that state appears to be related to how many of the trunk lines are fiber (vs. copper). I believe the cause is that we begin registering collisions and I am assuming that the switch sees enough collisions to register a faulty link condition. I do not seem to be able to configure the trunk lines for full-duplex. Duplex doesn't even appear to be an option I can set. The commands I'm using are:
#configure terminal
#interface gi0/48
#duplex full <--- this one fails as an invalid command
I'm speculating that if I could get the port to be full duplex, which according to the SPF module documentation is supported, things would work just fine. At this point, I'm stumped. Any thoughts?
