cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
25640
Views
5
Helpful
11
Replies

Uplink port is getting down automatically in switch

Hi All,

In switch 3560, up link port getting down automatically. Respective up link port  which is connecting to up link switch of 6509E both the interface configuration is below,

Note: If we shut and no shut the port its getting up but going down automatically. 

Could someone find out the root cause of it.

Cisco-SW-6509E#sho run int g1/46       

interface GigabitEthernet1/46

switchport

switchport trunk encapsulation dot1q

switchport trunk allowed vlan 1,64,96,128,192,1020

switchport mode trunk

spanning-tree portfast disable

spanning-tree bpduguard disable


Cisco-SW-3560E-acc1#sh run int gi0/49
interface GigabitEthernet0/49
description To DC-1Dctr-6509E-Distr1 g1/46
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,64,96,128,192,1020
switchport mode trunk
end

Advance in Thanks!

Regards,

Chandhuru

Thanks and regards, Chandhuru.M
1 Accepted Solution

Accepted Solutions

Hell0

Have you checked/changed the cabling/sfp module(if applicable) between these two devices

What are the interlace(s) reporting?

res
Paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

View solution in original post

11 Replies 11

Hell0

Have you checked/changed the cabling/sfp module(if applicable) between these two devices

What are the interlace(s) reporting?

res
Paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

Hi Paul,

We have re-jacked the cable in port but the result is no joy. 

We haven't tried to change the cable.

You mean interface reporting status of hardware?

Logically interface is down. Even if we do shut/no shut port it came for few minutes and going down again automatically.

GigabitEthernet0/49 is down, line protocol is down (notconnect)

If you have any other question please let me know. Thanks in advance.

Regards,

Chandhuru

Thanks and regards, Chandhuru.M

Leo Laohoo
Hall of Fame
Hall of Fame

When this happens again, post the complete output to the following commands: 

1.  sh interface status err; 

2.  sh interface <BLAH>; and

3.  sh logs

Hi Leo,

Please find the requested logs below,

L02dc-1MDF-3560E-acc1#sh int gigabitEthernet 0/49 status err-disabled

Port Name Status Reason Err-disabled Vlans
Gi0/49 To DC-1Dctr-6509E- notconnect none
L02dc-1MDF-3560E-acc1#sh inter gigabitEthernet 0/49
GigabitEthernet0/49 is down, line protocol is down (notconnect)
Hardware is Gigabit Ethernet, address is 1cdf.0fe3.4331 (bia 1cdf.0fe3.4331)
Description: To DC-1Dctr-6509E-Distr1 g1/46
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Auto-duplex, Auto-speed, link type is auto, media type is 1000BaseSX SFP
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 2d11h, output 2d11h, 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/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
150947980 packets input, 14728780395 bytes, 0 no buffer
Received 129966921 broadcasts (62807582 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 62807582 multicast, 0 pause input
0 input packets with dribble condition detected
313960686 packets output, 25472561074 bytes, 0 underruns
0 output errors, 0 collisions, 7 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
L02dc-1MDF-3560E-acc1#sh log | in 0/49
Aug 4 00:58:26.172: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/49, changed state to down
Aug 4 00:58:28.160: %LINK-3-UPDOWN: Interface GigabitEthernet0/49, changed state to down
.Aug 4 03:52:12.890: %LINK-3-UPDOWN: Interface GigabitEthernet0/49, changed state to up
.Aug 4 03:52:13.905: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/49, changed state to up
Aug 4 04:05:10.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/49, changed state to down
Aug 4 04:05:12.675: %LINK-3-UPDOWN: Interface GigabitEthernet0/49, changed state to down
Aug 4 04:16:04.289: %LINK-3-UPDOWN: Interface GigabitEthernet0/49, changed state to up
Aug 4 04:16:05.304: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/49, changed state to up
Aug 4 04:16:48.680: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/49, changed state to down
Aug 4 04:16:50.676: %LINK-3-UPDOWN: Interface GigabitEthernet0/49, changed state to down
Aug 4 04:21:10.954: %LINK-3-UPDOWN: Interface GigabitEthernet0/49, changed state to up
Aug 4 04:21:11.995: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/49, changed state to up
Aug 5 16:58:31.859: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/49, changed state to down
Aug 5 16:58:33.847: %LINK-3-UPDOWN: Interface GigabitEthernet0/49, changed state to down
Aug 5 18:06:21.122: %LINK-5-CHANGED: Interface GigabitEthernet0/49, changed state to administratively down
Aug 5 18:06:23.244: %LINK-3-UPDOWN: Interface GigabitEthernet0/49, changed state to down
Aug 5 18:07:03.516: %LINK-5-CHANGED: Interface GigabitEthernet0/49, changed state to administratively down
Aug 5 18:07:07.895: %LINK-3-UPDOWN: Interface GigabitEthernet0/49, changed state to down

Regards,

Chandhuru

Thanks and regards, Chandhuru.M

Ok, this is the output for the 3560.  Are you able to furnish me the same command output for the 6500?

Hi Leo,

Please see below,

DC-1Dctr-6509E-Distr1#sh int gi1/46 status err-disabled

Port Name Status Reason
Gi1/46 MDF-1 10.102.0.22 notconnect none

DC-1Dctr-6509E-Distr1#sh int gi1/46
GigabitEthernet1/46 is down, line protocol is down (notconnect)
Hardware is C6k 1000Mb 802.3, address is 5475.d004.510d (bia 5475.d004.510d)
Description: MDF-1 10.102.0.22 g0/49
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 0/255, rxload 0/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is SX
input flow-control is off, output flow-control is off
Clock mode is auto
ARP type: ARPA, ARP Timeout 04:00:00
Last input 2d15h, output 2d15h, output hang never
Last clearing of "show interface" counters 1y4w
Input queue: 0/2000/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
194899749 packets input, 15846120647 bytes, 0 no buffer
Received 185107608 broadcasts (172300658 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
120362181 packets output, 12084246350 bytes, 0 underruns
0 output errors, 0 collisions, 3 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


DC-1Dctr-6509E-Distr1#sh log | in 1/46
693698: .Aug 5 12:58:31.595 EDT: %TRACKING-5-STATE: 1 interface Gi1/46 line-protocol Up->Down

regards,

Chandhuru

Thanks and regards, Chandhuru.M

Something doesn't add up here. 

On the 3560, kindly put the output in a text file and attach to your next reply.  Run the command "sh controll e  Gi0/49". 

On the 6500, kindly put the output in a text file and attach to your next reply.  Run the command "sh counter interface Gi 1/46".

Hello



L02dc-1MDF-3560E-acc1#sh inter gigabitEthernet 0/49
 Keepalive not set
Auto-duplex, Auto-speed, link type is auto, media type is 1000BaseSX SFP
input flow-control is off, output flow-control is unsupported
 


DC-1Dctr-6509E-Distr1#sh int gi1/46
 Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is SX
input flow-control is off, output flow-control is off
Clock mode is auto
 

res
paul


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

Try below steps and let me know if issue still persists

1. Try to run show interfaces status err-disabled and see what is reason of err-disabled.
2. Try to reset both interfaces using default command and add configuration again. Make sure that STP commands would be same from both sides.
3. Enable err-disable auto recovery on both interfaces.
4. Try to connect 3560 Gig 0/49 with 6500 another interface and also try to connect 6500 1/46 interface with 3560 other interface and see if respective ports are working so you can narrow down the investigation to one port.

legacynetwork
Level 1
Level 1
Try below steps and let me know if issue still persists 1. Try to run show interfaces status err-disabled and see what is reason of err-disabled. 2. Try to reset both interfaces using default command and add configuration again. Make sure that STP commands would be same from both sides. 3. Enable err-disable auto recovery on both interfaces. 4. Try to connect 3560 Gig 0/49 with 6500 another interface and also try to connect 6500 1/46 interface with 3560 other interface and see if respective ports are working so you can narrow down the investigation to one port.

Hi All,

Changed SFP module to resolve this issue. Issue resolved now. Thanks a lot for all your support. Thanks!

Sorry for late reply.

Regards,

Chandhuru

Thanks and regards, Chandhuru.M
Review Cisco Networking for a $25 gift card