C9407 line protocol up and down issue

[silverdoor12]

I have 2ea C9407 clockwise virtual.

End device is linux server. (no redundancy)

I have log said 

May 25 07:09:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 07:09:47: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 07:11:02: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 07:11:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 07:11:35: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 07:11:43: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 07:39:35: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 07:39:43: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 07:44:30: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 07:44:38: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 07:45:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 07:45:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 07:46:22: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 07:46:29: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 07:52:00: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 07:52:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 07:59:00: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 07:59:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 08:11:19: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 08:11:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 08:21:01: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 08:21:09: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 08:34:37: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 08:34:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 08:40:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 08:40:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 08:47:29: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 08:47:37: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 08:48:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 08:48:11: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 09:02:32: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 09:02:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 09:20:07: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 09:20:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 09:22:33: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 09:22:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 09:23:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 09:23:44: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 09:43:34: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 09:43:42: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 10:05:11: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 10:05:19: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up
May 25 10:16:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to down
May 25 10:16:13: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/0/9, changed state to up

There is up & down log every 7~8 seconds.

show interface gi 1/1/0/9 is below

GigabitEthernet1/1/0/9 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 7c31.xxxx.xxxx (bia 7c31.xxxx.xxxx)
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
Auto-MDIX on (operational: on)
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:00, output hang never
Last clearing of "show interface" counters 10w6d
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 36335
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 1000 bits/sec, 2 packets/sec
359018292 packets input, 312774992848 bytes, 0 no buffer
Received 160677 broadcasts (154194 multicasts)
0 runts, 0 giants, 0 throttles
2 input errors, 2 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 154194 multicast, 0 pause input
0 input packets with dribble condition detected
320159155 packets output, 448790986744 bytes, 0 underruns
Output 291355 broadcasts (0 multicasts)
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
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

 * show run int gi 1/1/0/9 is below

interface GigabitEthernet1/1/0/9
switchport access vlan 25
switchport mode access
speed 1000
duplex full
spanning-tree portfast
!

I checked tdr test and utp cable is OK.

CRC was accumulated previously and is not currently generated.

What shoud I check to resolve this problem??

[silverdoor12]

+++ I tested speed auto and duplex auto, and the log is same....

[paul driver]

Hello
Change the cabling and suggest apply:

int x/x
spanning-tree bpduguard enable
shut
no shut

[silverdoor12]

Thank you, I will try this and leave reply later.

[Flavio Miranda]

@silverdoor12 

 What is the result for this command?

test cable-diagnostics tdr interface X/X

[silverdoor12]

I don't have image or log files, but it was normal (A B C D)

[Leo Laohoo]

---

@Flavio Miranda wrote:
test cable-diagnostics tdr interface X/X

---

No.  Do not rely on the TDR result on any switches on IOS-XE because it is broken.  The result(s) is/are unreliable and inaccurate. Refer to  CSCvw97924 & CSCwd97177. 

Examples of buggy TDR results: 

9300, IOS-XE version 17.9.4a

(Above)  Pair "A" distance is (significantly) more than Pairs B, C and D.

(Above)  Pair A & B distance is "0".

[CSCO11269440]

If it is a physical machine, first check whether the network line is abnormal.
If it is a virtual machine, check whether there are packet losses or network abnormalities within the same ESXI host.

[silverdoor12]

It is a physical machine (OS is linux).

I will double check cable and other things that I can do, and contact server engineer soon.

Thank you

[Leo Laohoo]

Move the connection to a different blade. 

Do not hard-code speed &/or duplex settings.  

[silverdoor12]

Thank you.

I changed a port (same module) already.

You suggest me to change a port in other module??

[Leo Laohoo]

---

@silverdoor12 wrote:
I changed a port (same module) already.

---

Use a different line card.

[CSCO11269440]

Replace the network card of the physical host or replace it with a new network card for testing

[silverdoor12 · Accepted solution]

Thank you for replying.

It was not network issue.

It was server problem.