Cisco 3560G LED not stable

samirshaikh52 · ‎09-06-2010

Recently I've encountered an issue with our Cisco 3560 Catalyst switch.

The LED of the interface Giga 0/25 was turning into orange after few seconds. After reboot the switch,It was working fine.

To prevent this happen in future again, I want to know the cause of the issue and find the resolution

For the this I need experts support

Any help will be highly appreciated.

Reza Sharifi · ‎09-06-2010

Hi,

Can you post the config for interface Gi0/25?

can you issue "sh log" and see if there is an error message?

also, do you have bpduguard enabled on this port?

Reza

samirshaikh52 · ‎09-06-2010

Thanks for your quick response.

interface GigabitEthernet0/25
switchport trunk encapsulation dot1q
switchport mode trunk

no I dont have bpdu guard enable

Below log is after reboot

Sh log

Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes,
0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

    Console logging: level debugging, 74 messages logged, xml disabled,
                     filtering disabled
    Monitor logging: level debugging, 0 messages logged, xml disabled,
                     filtering disabled
    Buffer logging: level debugging, 74 messages logged, xml disabled,
                     filtering disabled
    Exception Logging: size (4096 bytes)
    Count and timestamp logging messages: disabled
    File logging: disabled
    Persistent logging: disabled

No active filter modules.

    Trap logging: level notifications, 68 message lines logged
        Logging to 10.1.2.22 (udp port 514, audit disabled,
              authentication disabled, encryption disabled, link up),
              68 message lines logged,
              0 message lines rate-limited,
              0 message lines dropped-by-MD,
              xml disabled, sequence number disabled
              filtering disabled

Log Buffer (4096 bytes):
p
000035: *Mar 1 03:02:29: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed
state to up
000036: *Mar 1 03:02:29: %LINK-3-UPDOWN: Interface GigabitEthernet0/5, changed
state to up
000037: *Mar 1 03:02:29: %LINK-3-UPDOWN: Interface GigabitEthernet0/10, changed
state to up
000038: *Mar 1 03:02:29: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed
state to up
000039: *Mar 1 03:02:29: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed
state to up
000040: *Mar 1 03:02:29: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi
tEthernet0/25, changed state to up
000041: *Mar 1 03:02:30: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi
tEthernet0/19, changed state to up
000042: *Mar 1 03:02:31: %LINK-3-UPDOWN: Interface GigabitEthernet0/16, changed
state to up
000043: *Mar 1 03:02:31: %LINK-3-UPDOWN: Interface GigabitEthernet0/14, changed
state to up
000044: *Mar 1 03:02:31: %LINK-3-UPDOWN: Interface GigabitEthernet0/15, changed
state to up
000045: *Mar 1 03:02:31: %LINK-3-UPDOWN: Interface GigabitEthernet0/17, changed
state to up
000046: *Mar 1 03:02:31: %LINK-3-UPDOWN: Interface GigabitEthernet0/20, changed
state to up
000047: *Mar 1 03:02:31: %LINK-3-UPDOWN: Interface GigabitEthernet0/18, changed
state to up
000048: *Mar 1 03:02:32: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi
tEthernet0/20, changed state to up
000049: *Mar 1 03:02:33: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi
tEthernet0/16, changed state to up
000050: *Mar 1 03:02:33: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi
tEthernet0/14, changed state to up
000051: *Mar 1 03:02:33: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi
tEthernet0/15, changed state to up
000052: *Mar 1 03:02:33: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi
tEthernet0/17, changed state to up
000053: *Mar 1 03:02:33: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi
tEthernet0/18, changed state to up
000054: *Mar 1 03:02:59: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1,
changed state to up
000055: *Mar 1 03:02:59: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan26
, changed state to up
000056: .Sep 7 00:31:08: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 10.1.2.2
2 Port 514 started - reconnection
000057: Sep 7 01:40:46: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabit
Ethernet0/11, changed state to down
000058: Sep 7 01:40:47: %LINK-3-UPDOWN: Interface GigabitEthernet0/11, changed
state to down
000059: Sep 7 01:40:58: %LINK-3-UPDOWN: Interface GigabitEthernet0/11, changed
state to up
000060: Sep 7 01:40:59: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabit
Ethernet0/11, changed state to up
000061: Sep 7 01:42:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabit
Ethernet0/11, changed state to down
000062: Sep 7 01:42:26: %LINK-3-UPDOWN: Interface GigabitEthernet0/11, changed
state to down
000063: Sep 7 01:42:30: %LINK-3-UPDOWN: Interface GigabitEthernet0/11, changed
state to up
000064: Sep 7 01:42:31: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabit
Ethernet0/11, changed state to up
000065: Sep 7 03:41:01: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabit
Ethernet0/11, changed state to down
000066: Sep 7 03:41:02: %LINK-3-UPDOWN: Interface GigabitEthernet0/11, changed
state to down
000067: Sep 7 03:41:05: %LINK-3-UPDOWN: Interface GigabitEthernet0/11, changed
state to up
000068: Sep 7 03:41:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabit
Ethernet0/11, changed state to up
000069: Sep 7 03:41:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabit
Ethernet0/11, changed state to down
000070: Sep 7 03:41:24: %LINK-3-UPDOWN: Interface GigabitEthernet0/11, changed
state to down
000071: Sep 7 03:41:27: %LINK-3-UPDOWN: Interface GigabitEthernet0/11, changed
state to up
000072: Sep 7 03:41:28: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabit
Ethernet0/11, changed state to up
000073: Sep 7 04:14:10: %SYS-5-CONFIG_I: Configured from console by vty0 (10.1.
26.10)
000074: Sep 7 04:14:46: %SYS-5-CONFIG_I: Configured from console by vty0 (10.1.
26.10)