Understanding LINK-3-UPDOWN & LINEPROTO-5-UPDOWN logs on CISCO2960

[rameshbalachandran]

Hi,

   Please find the attachment for logs from a CISCO2960 Switch (running IOS c2960-lanbasek9-mz.122-55.SE7)

.

My query is,

1) Why is LINK-3-UPDOWN & LINEPROTO-5-UPDOWN logs counts are mismatching?

     LINK-3-UPDOWN (21) & LINEPROTO-5-UPDOWN (71).

2) Desktops only connected with all access ports. they are powered on morning & shutdown on evening.

    As per this logic, only two logs should be generated (LINK3 & LINK5 up/down logs on morning/evening)

     What are all the possibilities to generate multiple up/down logs?

Please somebody help me to understand this issue.

[Leo Laohoo]

Everytime you log in or you log out, you generate at least two sets of Layer 1 and Layer 2 logs.  In both cases you'll see:

1.  line up

2.  protocol up

3.  line up again

4.  protocol up again.

If you log out, same thing ...

[rameshbalachandran]

Thanks for your reply.

In this case, the count of line-up/down & protocol up/down should be equal right?

[Leo Laohoo]

Yes.

[rameshbalachandran]

Thanks for your reply.

In this case,

Why is LINK-3-UPDOWN & LINEPROTO-5-UPDOWN logs counts are mismatching?

     LINK-3-UPDOWN (21) & LINEPROTO-5-UPDOWN (71).

I have checked with Log count ID. No logs missing. I'm confussed with this logs.

Is my switch having any issue? or conf?

[Leo Laohoo]

Ramesh,

Are the event counts happening to the same interface?

If they are, please post the output to the following commands:

1.  sh interface ;

2.  sh controller ethernet

[rameshbalachandran]

Hi,

     This events happening in almost all of my access switches.

I have 10 numbers of CISCO2960 switches in network.

None of switches matching the counts with LINK-3-UPDOWN & LINEPROTO-5-UPDOWN.

SW1#sh int fa0/23

FastEthernet0/23 is up, line protocol is up (connected)

  Hardware is Fast Ethernet, address is 0021.d71a.4197 (bia 0021.d71a.4197)

  Description: RECEPTION-172.16.11.10/24

  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 never, output 00:00:01, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  5 minute input rate 0 bits/sec, 0 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

     8105629 packets input, 1857332354 bytes, 0 no buffer

     Received 41102 broadcasts (549 multicasts)

     0 runts, 0 giants, 0 throttles

     1 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     0 watchdog, 549 multicast, 0 pause input

     0 input packets with dribble condition detected

     14716398 packets output, 9367900912 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

SW1#sh controllers ethernet-controller fastEthernet 0/24

     Transmit FastEthernet0/24                Receive

   2361891161 Bytes                       3016344669 Bytes

     12369076 Unicast frames                13027721 Unicast frames

      3683033 Multicast frames                   615 Multicast frames

      2871432 Broadcast frames                 41614 Broadcast frames

            0 Too old frames              3011192798 Unicast bytes

            0 Deferred frames                  89907 Multicast bytes

            0 MTU exceeded frames            5061964 Broadcast bytes

            0 1 collision frames                   0 Alignment errors

            0 2 collision frames                   0 FCS errors

            0 3 collision frames                   0 Oversize frames

            0 4 collision frames                   0 Undersize frames

            0 5 collision frames                   0 Collision fragments

            0 6 collision frames

            0 7 collision frames             2139857 Minimum size frames

            0 8 collision frames             1329497 65 to 127 byte frames

            0 9 collision frames             1713989 128 to 255 byte frames

            0 10 collision frames             346695 256 to 511 byte frames

            0 11 collision frames             582569 512 to 1023 byte frames

            0 12 collision frames            6957343 1024 to 1518 byte frames

            0 13 collision frames                  0 Overrun frames

            0 14 collision frames                  0 Pause frames

            0 15 collision frames

            0 Excessive collisions                 0 Symbol error frames

            0 Late collisions                      0 Invalid frames, too large

            0 VLAN discard frames                  0 Valid frames, too large

            0 Excess defer frames                  0 Invalid frames, too small

      9170546 64 byte frames                       0 Valid frames, too small

      4140009 127 byte frames

      1615131 255 byte frames                      0 Too old frames

       445136 511 byte frames                      0 Valid oversize frames

       173914 1023 byte frames                     0 System FCS error frames

      3378805 1518 byte frames                     0 RxPortFifoFull drop frame

            0 Too large frames

            0 Good (1 coll) frames

            0 Good (>1 coll) frames

[Leo Laohoo]

Output of the commands requested look fine.