Link dropping off

kpmgnz · ‎02-20-2007

We are currently using 3560's, we are having intermitant connections drop off, is there a tool or debug I can run on an effected link to try accertain what is going on. The interfaces are dropping off maybe once a day, 3-5 interfaces on a single switch.

Thanks for any advice

spremkumar · ‎02-20-2007

Hi

Logs available in your Cisco 3560 can provide vital info on the why the ports are dropping.

You can verify the same to start the troubleshooting process...

regds

jain.nitin · ‎02-20-2007

Hi, Check the duplex & speed settings on thoes ports & more importantly check what are the devices connected on these port, r they able to negotiate speed & duplex.

I suggest u if it is connected to server/switches then configure speed & duplex manually on these ports.

If it helps, please do rate.

kpmgnz · ‎02-21-2007

Hi here is the output from show logging:

NZAKL2NET3#show logging

Syslog logging: enabled (0 messages dropped, 31 messages rate-limited, 0 flushes

, 0 overruns, xml disabled, filtering disabled)

Console logging: level debugging, 327 messages logged, xml disabled,

filtering disabled

Monitor logging: level debugging, 0 messages logged, xml disabled,

filtering disabled

Buffer logging: level debugging, 357 messages logged, xml disabled,

filtering disabled

Exception Logging: size (4096 bytes)

Count and timestamp logging messages: disabled

File logging: disabled

Trap logging: level informational, 331 message lines logged

Log Buffer (4096 bytes):

/13, changed state to up

000324: *Mar 4 23:42:04: %SYS-CLUSTER_MEMBER_11-5-CONFIG_I: Configured from con

sole by vty0 (10.150.0.210)

000325: *Mar 4 23:43:12: %SYS-CLUSTER_MEMBER_11-5-CONFIG_I: Configured from con

sole by vty0 (10.150.0.210)

000326: *Mar 7 02:19:17: %LINEPROTO-CLUSTER_MEMBER_11-5-UPDOWN: Line protocol o

n Interface FastEthernet0/13, changed state to down

000327: *Mar 7 02:19:18: %LINK-CLUSTER_MEMBER_11-3-UPDOWN: Interface FastEthern

et0/13, changed state to down

000328: *Mar 7 02:19:20: %LINK-CLUSTER_MEMBER_11-3-UPDOWN: Interface FastEthern

et0/13, changed state to up

000329: *Mar 7 02:19:21: %LINEPROTO-CLUSTER_MEMBER_11-5-UPDOWN: Line protocol o

n Interface FastEthernet0/13, changed state to up

000330: *Mar 7 02:20:00: %LINEPROTO-CLUSTER_MEMBER_11-5-UPDOWN: Line protocol o

n Interface FastEthernet0/13, changed state to down

000331: *Mar 7 02:20:01: %LINK-CLUSTER_MEMBER_11-3-UPDOWN: Interface FastEthern

et0/13, changed state to down

000332: *Mar 7 02:20:03: %LINK-CLUSTER_MEMBER_11-3-UPDOWN: Interface FastEthern

et0/13, changed state to up

000333: *Mar 7 02:20:04: %LINEPROTO-CLUSTER_MEMBER_11-5-UPDOWN: Line protocol o

n Interface FastEthernet0/13, changed state to up

000334: *Mar 7 05:50:38: %LINEPROTO-CLUSTER_MEMBER_11-5-UPDOWN: Line protocol o

n Interface FastEthernet0/13, changed state to down

000335: *Mar 7 05:50:40: %LINEPROTO-CLUSTER_MEMBER_11-5-UPDOWN: Line protocol o

n Interface FastEthernet0/13, changed state to up

000336: *Mar 7 05:50:49: %LINEPROTO-CLUSTER_MEMBER_11-5-UPDOWN: Line protocol o

n Interface FastEthernet0/13, changed state to down

000337: *Mar 7 05:50:50: %LINK-CLUSTER_MEMBER_11-3-UPDOWN: Interface FastEthern

et0/13, changed state to down

000338: *Mar 7 05:50:52: %LINK-CLUSTER_MEMBER_11-3-UPDOWN: Interface FastEthern

et0/13, changed state to up

bjw · ‎02-21-2007

Can you provide output of show cluster, show cluster members detail and maybe run, debug cluster and see what the log files trap.

You might want to do this as well on other cluster members.

http://www.cisco.com/en/US/products/hw/switches/ps5528/products_command_reference_chapter09186a00805b5624.html#wp1562364