dissolved
asked on
Slow connection through switch?
Please see this diagram first:
http://mvpbaseball.cc/mynetwork.jpg
When host1 copies a 600mb file from the "server", it takes only 8 minutes.
When host2 copies the same 600mb file, it takes 179 minutes.
I'm assuming host 2 has a 10mb connection to the "server", and Host1 has a 100mb connection.......but why?
I am using 2924XL switches. The router is a cable router with a 10/100 interface. I hardcoded the ports, that connect the two switches together, to full duplex. Thought it would solve problem but didnt. Cat5 cabling is run throughout the network
Thanks
http://mvpbaseball.cc/mynetwork.jpg
When host1 copies a 600mb file from the "server", it takes only 8 minutes.
When host2 copies the same 600mb file, it takes 179 minutes.
I'm assuming host 2 has a 10mb connection to the "server", and Host1 has a 100mb connection.......but why?
I am using 2924XL switches. The router is a cable router with a 10/100 interface. I hardcoded the ports, that connect the two switches together, to full duplex. Thought it would solve problem but didnt. Cat5 cabling is run throughout the network
Thanks
Have you tried moving that host to the other switch to see if the issue you are seeing is related to that host its self.
Do you have them in different VLANs or anything?
Look at the switch port statistics for error conditions on any port.
Look at the switch port statistics for error conditions on any port.
ASKER
Dr IP: I will try to move the host to the other switch to see if that will solve it
lrmoore: I killed all VLANs I had on the switch by issuing "no" commands for each port that was set for VLANs. My hosts are no longer going through a router with subinterfaces to intervlan-route. They are just all in the same network now and using my cable router as the gateway. By the way, how do I view port statistics for the error conditions on the ports??
Also, do you guys think this could be affected by my recent cabling adventures? The main crossover cable that connects the two switches used to be straight through. I changed one end to crossover . Terminated each wire. Just a thought.
Thanks
lrmoore: I killed all VLANs I had on the switch by issuing "no" commands for each port that was set for VLANs. My hosts are no longer going through a router with subinterfaces to intervlan-route. They are just all in the same network now and using my cable router as the gateway. By the way, how do I view port statistics for the error conditions on the ports??
Also, do you guys think this could be affected by my recent cabling adventures? The main crossover cable that connects the two switches used to be straight through. I changed one end to crossover . Terminated each wire. Just a thought.
Thanks
Did you follow TIA/EIA 568 standards to make the crossover?
The web interface is the easiest way to see port statistics/errors.
I don't have one close to tell you exactly where...
The web interface is the easiest way to see port statistics/errors.
I don't have one close to tell you exactly where...
ASKER
Here's one of my switches output. This would be switch A in my diagram (switch on the left). Port 20 is connected to a router I'm not doing routing through at the moment. Port 22 connects to switch B in my diagram (switch on the right).
So port 22 is up and down it looks like.
*And on an unrelated note, port 20 is connecting to a router who is not set to full duplex. I tried to set my 2501 router to full duplex, couldnt do it. config t int e0 duplex full
Thanks
er (4096 bytes):
rA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to up
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to up
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to down
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to down
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to up
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to up
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to down
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to down
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to up
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to up
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to down
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to down
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to up
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to up
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to down
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to up
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to up
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %RTD-1-LINK_FLAP: FastEthernet0/22 link down/up 5 times per min
1d16h: %RTD-1-LINK_FLAP: FastEthernet0/22 link down/up 5 times per min
1d16h: %RTD-1-LINK_FLAP: FastEthernet0/22 link down/up 5 times per min
1d16h: %RTD-1-LINK_FLAP: FastEthernet0/22 link down/up 5 times per min
1d16h: %RTD-1-LINK_FLAP: FastEthernet0/22 link down/up 5 times per min
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex)
So port 22 is up and down it looks like.
*And on an unrelated note, port 20 is connecting to a router who is not set to full duplex. I tried to set my 2501 router to full duplex, couldnt do it. config t int e0 duplex full
Thanks
er (4096 bytes):
rA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to up
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to up
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to down
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to down
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to up
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to up
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to down
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to down
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to up
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to up
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to down
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to down
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to up
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to up
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to down
1d16h: %LINK-3-UPDOWN: Interface FastEthernet0/22, changed state to up
1d16h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/22, changed state to up
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %RTD-1-LINK_FLAP: FastEthernet0/22 link down/up 5 times per min
1d16h: %RTD-1-LINK_FLAP: FastEthernet0/22 link down/up 5 times per min
1d16h: %RTD-1-LINK_FLAP: FastEthernet0/22 link down/up 5 times per min
1d16h: %RTD-1-LINK_FLAP: FastEthernet0/22 link down/up 5 times per min
1d16h: %RTD-1-LINK_FLAP: FastEthernet0/22 link down/up 5 times per min
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex).
1d16h: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/20 (not half duplex), with routerA Ethernet0 (half duplex)
What's on port 0/22 as it seems to be possibly having some problems? Also besides logs, you should do a show interface F0/XX for the ports where the crossover cable is and the workstation you are having issues with. Below a sample of what you should see, and I have added brackets to the line you want to pay attention to. It not uncommon to get a few errors now and then like in this case, but if the number keeps incrementing regularly you have a problem.
FastEthernet0/1 is up, line protocol is up
Hardware is Fast Ethernet, address is 0030.7174.eb42 (bia 0030.7174.eb42)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Auto-duplex (Full), Auto Speed (100), 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1943734 packets input, 469387738 bytes
Received 67740 broadcasts, 0 runts, 0 giants, 0 throttles
[9 input errors, 9 CRC, 0 frame, 0 overrun, 0 ignored]
0 watchdog, 1025 multicast
0 input packets with dribble condition detected
4092869 packets output, 2632251792 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
FastEthernet0/1 is up, line protocol is up
Hardware is Fast Ethernet, address is 0030.7174.eb42 (bia 0030.7174.eb42)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Auto-duplex (Full), Auto Speed (100), 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1943734 packets input, 469387738 bytes
Received 67740 broadcasts, 0 runts, 0 giants, 0 throttles
[9 input errors, 9 CRC, 0 frame, 0 overrun, 0 ignored]
0 watchdog, 1025 multicast
0 input packets with dribble condition detected
4092869 packets output, 2632251792 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Port 22 is the port that connects to the other switch. Here is the sh fa0/22 from switch A and sh fa0/1 from switch B.
FastEthernet0/22 is up, line protocol is up
Hardware is Fast Ethernet, address is 0030.1944.2d56 (bia 0030.1944.2d56)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, Auto Speed (100), 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:48, output 00:00:04, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 1000 bits/sec, 1 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
457311 packets input, 90132452 bytes
Received 7878 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 1876 multicast
0 input packets with dribble condition detected
667305 packets output, 699337480 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
--------------------------
Port 22 on switch A, connects to Port 01 on switch B via cross over
FastEthernet0/1 is up, line protocol is up
Hardware is Fast Ethernet, address is 0090.f244.ae01 (bia 0090.f244.ae01)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive not set
Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:05, output 00:00:49, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 2000 bits/sec, 2 packets/sec
5 minute output rate 2000 bits/sec, 2 packets/sec
5294 packets input, 4794891 bytes, 0 no buffer
Received 1120 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 watchdog, 794 multicast
0 input packets with dribble condition detected
3208 packets output, 449265 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
FastEthernet0/22 is up, line protocol is up
Hardware is Fast Ethernet, address is 0030.1944.2d56 (bia 0030.1944.2d56)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, Auto Speed (100), 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:48, output 00:00:04, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 1000 bits/sec, 1 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
457311 packets input, 90132452 bytes
Received 7878 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 1876 multicast
0 input packets with dribble condition detected
667305 packets output, 699337480 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
--------------------------
Port 22 on switch A, connects to Port 01 on switch B via cross over
FastEthernet0/1 is up, line protocol is up
Hardware is Fast Ethernet, address is 0090.f244.ae01 (bia 0090.f244.ae01)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive not set
Full-duplex, 100Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:05, output 00:00:49, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 2000 bits/sec, 2 packets/sec
5 minute output rate 2000 bits/sec, 2 packets/sec
5294 packets input, 4794891 bytes, 0 no buffer
Received 1120 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 watchdog, 794 multicast
0 input packets with dribble condition detected
3208 packets output, 449265 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
ASKER
Going to test to see if crossover is bad..
thanks guys
thanks guys
ASKER
Ok, the crossover is good. I switched nics in the client, and it is running full speed now. Just curious, could this have caused port 22 going up and down? How do I clear the error messages right now , to see if I get any in the future. What is link flapping lrmoore?
Thanks guys
Thanks guys
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks a lot! Now I just have to figure out how to set my 2500 router's e0 to full duplex
routerA(config)#int e0
routerA(config-if)#duplex full
This command is not supported for Ethernet0.
routerA(config-if)#
routerA(config)#int e0
routerA(config-if)#duplex full
This command is not supported for Ethernet0.
routerA(config-if)#
I think the only choice you have on the 2500 is to set the port on the switch to 10 Megs half duplex. As I have never come across a 2500 that the Ethernet port would operate in full duplex mode.
ASKER
thanks