Solved

Slow connection through switch?

Posted on 2004-10-22
873 Views
Last Modified: 2007-12-19
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
0
Question by:dissolved
    14 Comments
     
    LVL 13

    Expert Comment

    by:Dr-IP
    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.
    0
     
    LVL 79

    Expert Comment

    by:lrmoore
    Do you have them in different VLANs or anything?
    Look at the switch port statistics for error conditions on any port.
    0
     

    Author Comment

    by:dissolved
    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
    0
     
    LVL 79

    Expert Comment

    by:lrmoore
    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...
    0
     

    Author Comment

    by:dissolved
    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)
    0
     
    LVL 13

    Expert Comment

    by:Dr-IP
    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

    0
     
    LVL 79

    Assisted Solution

    by:lrmoore
    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: %RTD-1-LINK_FLAP: FastEthernet0/22 link down/up 5 times per min

    Bingo... link flapping...
    Could be bad crossover cable..


    0
     

    Author Comment

    by:dissolved
    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
    0
     

    Author Comment

    by:dissolved
    Going to test to see if crossover is bad..
    thanks guys
    0
     

    Author Comment

    by:dissolved
    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
    0
     
    LVL 13

    Accepted Solution

    by:
    When you did the show interfaces and the results where clean I’d say that kind of eliminated to likelihood that the crossover cable is bad. On the other had you got LINK_FLAP errors which could indicate a bad port on one of the switches, probably the one of the far side, it could also be related to power issues, are these switches on UPS’s? Also reconfiguring ports can cause those errors, and since you have been working on these two switch’s trying to figure out your workstation problem you might have caused it your self. So just keep an eye on it for now.

    As for clearing the log, it’s “clear log” on and IOS switch, and “clear logging buffer” on a CAT switch. You can also can clear the port counters with “clear counters” for IOS, and “clear counters all” on CAT OS switches.  
     
    0
     

    Author Comment

    by:dissolved
    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)#


    0
     
    LVL 13

    Expert Comment

    by:Dr-IP
    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.
    0
     

    Author Comment

    by:dissolved
    thanks
    0

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Top 6 Sources for Identifying Threat Actor TTPs

    Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

    Suggested Solutions

    In a WLAN, anything you broadcast over the air can be intercepted.  By default a wireless network is wide open to all until security is configured. Even when security is configured information can still be intercepted! It is very important that you …
    This article is a guide to configure bridging on Cisco Routers.  This is something I never knew was possible until after making a few phone calls to Cisco.  Using bridging saved our company money by not requiring us to purchase a new switch.  Bridgi…
    After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
    After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

    913 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    19 Experts available now in Live!

    Get 1:1 Help Now