RE: Monitoring/Troubleshooting Catalysts : what does this SYSLOG outp ut mean?

[McCallum, Robert]

Title: Monitoring/Troubleshooting Catalysts : what does this SYSLOG output mean?

Make sure that both of the ports are manually set to 100 meg full duplex.  I believe your 5000 cat is auto negotiating and this is your trouble.  do set port speed ?/? 100 then set port duplex ?/? full.  ? being the port on the catalyst.

-----Original Message-----
From: Deloso, Elmer G. [mailto:[EMAIL PROTECTED]]
Sent: 21 September 2000 14:28
To: '[EMAIL PROTECTED]'
Subject: Monitoring/Troubleshooting Catalysts : what does this SYSLOG outp ut mean?

Hi, group.
Just want to know why i'm getting this in my syslog on my 2912
whose port4 is connected by fiber to a 5500. I do know that there's
a lot of trafiic coming into this port and once in a while the LED turns
orange. Please comment on this. Thanks.

Elmer

FastEthernet0/4 is up, line protocol is up
  Hardware is Fast Ethernet, address is 0030.1900.7284 (bia 0030.1900.7284)
  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
     reliability 254/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
  Full-duplex, 100Mb/s
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:02, 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 292000 bits/sec, 114 packets/sec
  5 minute output rate 629000 bits/sec, 149 packets/sec
     429157271 packets input, 2185991621 bytes
     Received 72566224 broadcasts, 562577 runts, 0 giants, 0 throttles
     2317609 input errors, 877616 CRC, 877416 frame, 1391 overrun, 2261 ignored
     0 watchdog, 1251401 multicast
     0 input packets with dribble condition detected
     553912904 packets output, 4116503002 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

Syslog logging: enabled (0 messages dropped, 2488 flushes, 0 overruns)
    Console logging: level debugging, 252136 messages logged
    Monitor logging: level debugging, 0 messages logged
    Buffer logging: level debugging, 124840 messages logged
    File logging: disabled
    Trap logging: level informational, 124845 message lines logged

Log Buffer (4096 bytes):
1/1 (half duplex).
11w4d: %CDP-CLUSTER_MEMBER_3-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/4 (not half duplex), with 067521768(HubB) 1/1 (half duplex).

11w4d: %LINK-CLUSTER_MEMBER_3-4-ERROR: FastEthernet0/4 is experiencing errors
11w4d: %CDP-CLUSTER_MEMBER_3-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/4 (not half duplex), with 067521768(HubB) 1/1 (half duplex).

11w4d: %CDP-CLUSTER_MEMBER_3-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/4 (not half duplex), with 067521768(HubB) 1/1 (half duplex).

11w4d: %LINK-CLUSTER_MEMBER_3-4-ERROR: FastEthernet0/4 is experiencing errors
11w4d: %CDP-CLUSTER_MEMBER_3-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/4 (not half duplex), with 067521768(HubB) 1/1 (half duplex).

11w4d: %LINK-CLUSTER_MEMBER_3-4-ERROR: FastEthernet0/4 is experiencing errors