[c-nsp] Line Protocol going down

[Aaron]

Could be a bad port too. Try a new cable first, then try a new port.
Start with the side that is seeing the errors.

Aaron

On Fri, May 11, 2012 at 10:46 AM, Scott Voll <svoll.voip at gmail.com> wrote:
> I have a 2821(15.1(3)T2) connected to a 3560(12.2(55)SE3) and recently i
> have had the Line protocol between the two go down.
>
> The two are connected on a dot1q truck.
>
> Sh int on the router:
>
> GigabitEthernet0/0 is up, line protocol is up
>  Hardware is MV96340 Ethernet, address is 001b.d470.8fa8 (bia
> 001b.d470.8fa8)
>  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
>     reliability 255/255, txload 1/255, rxload 1/255
>  Encapsulation 802.1Q Virtual LAN, Vlan ID  1., loopback not set
>  Keepalive set (10 sec)
>  Full Duplex, 100Mbps, media type is T
>  output flow-control is XON, input flow-control is XON
>  ARP type: ARPA, ARP Timeout 04:00:00
>  Last input 00:00:00, output 00:00:00, output hang never
>  Last clearing of "show interface" counters 13w2d
>  Input queue: 0/75/36/0 (size/max/drops/flushes); Total output drops: 0
>  Queueing strategy: fifo
>  Output queue: 0/40 (size/max)
>  5 minute input rate 55000 bits/sec, 28 packets/sec
>  5 minute output rate 143000 bits/sec, 71 packets/sec
>     1805047870 packets input, 3205641174 bytes, 1 no buffer
>     Received 14405186 broadcasts (3085682 IP multicasts)
>     14 runts, 0 giants, 22 throttles
>     5895 input errors, 49 CRC, 1 frame, 0 overrun, 5831 ignored
>     0 watchdog, 0 multicast, 0 pause input
>     1591540763 packets output, 638093162 bytes, 0 underruns
>     0 output errors, 0 collisions, 0 interface resets
>     269848 unknown protocol drops
>     0 babbles, 0 late collision, 0 deferred
>     50 lost carrier, 0 no carrier, 10 pause output
>     0 output buffer failures, 0 output buffers swapped out
>
> sh int on the switch:
>
> FastEthernet0/1 is up, line protocol is up (connected)
>  Hardware is Fast Ethernet, address is 0017.94ab.8103 (bia 0017.94ab.8103)
>  Description: Router Port
>  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
>     reliability 255/255, txload 1/255, rxload 1/255
>  Encapsulation ARPA, loopback not set
>  Keepalive set (10 sec)
>  Full-duplex, 100Mb/s, media type is 10/100BaseTX
>  input flow-control is off, output flow-control is unsupported
>  ARP type: ARPA, ARP Timeout 04:00:00
>  Last input 00:00:34, output 00:00:00, output hang never
>  Last clearing of "show interface" counters never
>  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 641849
>  Queueing strategy: fifo
>  Output queue: 0/40 (size/max)
>  5 minute input rate 127000 bits/sec, 70 packets/sec
>  5 minute output rate 87000 bits/sec, 32 packets/sec
>     841389935 packets input, 363402231378 bytes, 0 no buffer
>     Received 382643887 broadcasts (382078407 multicasts)
>     7 runts, 0 giants, 0 throttles
>     7 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
>     0 watchdog, 382078407 multicast, 18 pause input
>     0 input packets with dribble condition detected
>     1827233350 packets output, 2184911648917 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 PAUSE output
>     0 output buffer failures, 0 output buffers swapped out
>
> The are directly connected with a 5 foot patch cable.
>
> What are runts?  pause inputs?  unknown protocol drops?
>
> Since I'm seeing Inputs errors and CRC's is this a bad patch cable?  This
> Router and switch when setup did not get hard set for speed and duplex.....
> could that be the issue?
>
> TIA
>
> Scott
> _______________________________________________
> 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/