[c-nsp] Underrun/runt issue on trunk interface between 2 switchs

[Brad Clausen]

I readsomething similar to that.. Which is why I tried using a straight
access port instead of trunk between both switchs. When I did that I started
receiving overruns instead. :(




2011/7/14 Jon Harald Bøvre <jon at bovre.no>

> Hi
>
> We had similar problems with a 3524XL some years ago.
> Server connected using ISL, switch trunking using dot1q.
> Switch strips off ISL header, replace with dot1q. Resulting in runts.
>
> Could be somethibg to consider
>
>
> Jon h bøvre
>
> Sent from my iPad
>
> On 13. juli 2011, at 15:29, Brad Clausen <overkillxx at gmail.com> wrote:
>
> > Hey Guys,
> >
> > I am having a weird issue between 2 switchs that I hope someone can help
> out
> > with.
> >
> >
> > One end of the trunk is a cisco WS-C3548-XL running 12.0(5.3)WC(1) code
> >
> > The other end is a ProCurve J9086A Switch 2610-24/12PWR  software
> Version:
> > R.11.25
> >
> >
> > On the Procurve end I see absolutely nothing in the way of errors. But on
> > the Cisco end I see an excessive amount of runts as per the following:
> >
> > sho int fastEthernet 0/1
> > FastEthernet0/1 is up, line protocol is up
> >  Hardware is Fast Ethernet, address is 0008.2117.b141 (bia
> 0008.2117.b141)
> >  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
> >     reliability 250/255, txload 1/255, rxload 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:23, output 00:00:00, output hang never
> >  Last clearing of "show interface" counters 01:31:18
> >  Queueing strategy: fifo
> >  Output queue 0/40, 0 drops; input queue 0/75, 0 drops
> >  5 minute input rate 5000 bits/sec, 4 packets/sec
> >  5 minute output rate 7000 bits/sec, 7 packets/sec
> >     31492 packets input, 5362556 bytes
> >     Received 14259 broadcasts, 3929 runts, 0 giants, 0 throttles
> >     3929 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
> >     0 watchdog, 2081 multicast
> >     0 input packets with dribble condition detected
> >     41094 packets output, 6605873 bytes, 0 underruns
> >     0 output errors, 0 collisions, 0 interface resets
> >     0 babbles, 0 late collision, 0 deferred
> >     0 lost carrier, 0 no carrier
> >     0 output buffer failures, 0 output buffers swapped out
> >
> >
> > Relevent config for each port is very basic as per the following:
> >
> > Cisco:
> >
> > interface FastEthernet0/1
> > duplex full
> > speed 100
> > switchport trunk encapsulation dot1q
> > switchport mode trunk
> > end
> >
> >
> > HP Procurve:
> >
> > interface 24
> >   speed-duplex 100-full
> >
> > vlan 10
> >   name "X-VLAN"
> >   untagged 13-21,27-28
> >   ip address 10.16.52.245 255.255.255.0
> >   tagged 1-5,22-26
> >   exit
> >
> > I've tried changing the cable between the 2 switchs as well as changing
> the
> > port on both ends. This didn't make any changes. I then decided to change
> it
> > from a trunk to an access port on both sides.. When I did this I again
> saw
> > no errors on the Procurve end of the link. However I then started to see
> > overruns on the Cisco switch as per the following:
> >
> >
> >
> > Hardware is Fast Ethernet, address is 0008.2117.b155 (bia 0008.2117.b155)
> >  MTU 1500 bytes, BW 0 Kbit, DLY 0 usec,
> >     reliability 255/255, txload 1/255, rxload 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:02:32, output 00:02:04, output hang never
> >  Last clearing of "show interface" counters 00:07:56
> >  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
> >     1342 packets input, 166570 bytes
> >     Received 711 broadcasts, 0 runts, 0 giants, 0 throttles
> >     9 input errors, 9 CRC, 0 frame, 9 overrun, 9 ignored
> >     0 watchdog, 118 multicast
> >     0 input packets with dribble condition detected
> >     990 packets output, 168402 bytes, 0 underruns
> >     0 output errors, 0 collisions, 0 interface resets
> >     0 babbles, 0 late collision, 0 deferred
> >     0 lost carrier, 0 no carrier
> >     0 output buffer failures, 0 output buffers swapped out
> >
> > This isn't occuring on any other interface on the Cisco switch. Also, it
> is
> > not occuring on any other switch connecting of the Procurve switch
> either.
> >
> > Does anyone have any ideas what coulld be causing this?
> >
> > Also worth nothing the input counts above are over only 20 or so minutes.
> > The counters were cleared prior.
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>