The interface hardware went either up or down

majdalani · ‎07-17-2008

Hi.

I'm using Cisco Network Assistant. and under View > System Messages i'm recieving this :

Description: Interface GigabitEthernet0/10, changed state to down

Explanation: The interface hardware went either up or down.

Recommended Action: If the state change was unexpected, confirm the configuration settings\n\ for the interface.

This port is attached to one of my critical servers and i always need this port to be up. any help please.

garytayl · ‎07-17-2008

This could be caused by a million reasons so the question here is, Do you have access to that device in order to gather the show log and the show int gig0/10.

With the information provided is almost impossible to "guess" what is going on.

majdalani · ‎07-17-2008

Hi,

this is the output:

ES-SW15#sh interfaces gigabitEthernet 0/19

GigabitEthernet0/19 is up, line protocol is up (connected)

Hardware is Gigabit Ethernet, address is 0015.c64d.8c13 (bia 0015.c64d.8c13)

MTU 1500 bytes, BW 1000000 Kbit, 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

ARP type: ARPA, ARP Timeout 04:00:00

Last input never, output 00:00:01, 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/40 (size/max)

5 minute input rate 1000 bits/sec, 2 packets/sec

5 minute output rate 1000 bits/sec, 2 packets/sec

35163364 packets input, 824030934 bytes, 0 no buffer

Received 505332 broadcasts (0 multicast)

0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 54 multicast, 0 pause input

0 input packets with dribble condition detected

55486702 packets output, 961910359 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 PAUSE output

0 output buffer failures, 0 output buffers swapped out

garytayl · ‎07-17-2008

Error message is pointing to int gig0/10, this is the output of 0/19 and this one looks very clean. Anything in the show log?

majdalani · ‎07-17-2008

yes, as i'm having this error on multiple ports.

ES-SW15#sh log

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

0 overruns, xml disabled, filtering disabled)

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

filtering disabled

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

filtering disabled

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

filtering disabled

Exception Logging: size (4096 bytes)

Count and timestamp logging messages: disabled

File logging: disabled

Trap logging: level informational, 399 message lines logged

Log Buffer (4096 bytes):

07:57: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/10, chan

ged state to down

000361: *Jul 26 10:07:58: %LINK-3-UPDOWN: Interface GigabitEthernet0/10, changed

state to down

000362: *Jul 26 10:12:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/19, changed state to down

000363: *Jul 26 10:12:26: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed

state to down

000364: *Jul 26 10:12:32: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed

state to up

000365: *Jul 26 10:12:33: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/19, changed state to up

000366: *Jul 26 10:13:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/19, changed state to down

000367: *Jul 26 10:13:09: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed

state to down

000368: *Jul 26 10:13:11: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed

state to up

000369: *Jul 26 10:13:12: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/19, changed state to up

000370: *Jul 27 17:38:00: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/15, changed state to down

000371: *Jul 27 17:38:00: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/14, changed state to down

000372: *Jul 27 17:38:01: %LINK-3-UPDOWN: Interface GigabitEthernet0/15, changed

state to down

000373: *Jul 27 17:38:01: %LINK-3-UPDOWN: Interface GigabitEthernet0/14, changed

state to down

000374: *Jul 27 17:38:03: %LINK-3-UPDOWN: Interface GigabitEthernet0/15, changed

state to up

000375: *Jul 27 17:38:04: %LINK-3-UPDOWN: Interface GigabitEthernet0/14, changed

state to up

majdalani · ‎07-17-2008

000376: *Jul 27 17:38:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/15, changed state to up

000377: *Jul 27 17:38:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/14, changed state to up

000378: *Jul 28 22:04:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/19, changed state to down

000379: *Jul 28 22:04:24: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed

state to down

000380: *Jul 28 22:04:30: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed

state to up

000381: *Jul 28 22:04:31: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/19, changed state to up

000382: *Jul 28 22:05:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/19, changed state to down

000383: *Jul 28 22:05:07: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed

state to down

000384: *Jul 28 22:05:09: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed

state to up

000385: *Jul 28 22:05:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/19, changed state to up

000386: *Aug 3 17:33:31: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/19, changed state to down

000387: *Aug 3 17:33:32: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed

state to down

000388: *Aug 3 17:33:38: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed

state to up

000389: *Aug 3 17:33:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/19, changed state to up

000390: *Aug 3 17:34:13: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/19, changed state to down

000391: *Aug 3 17:34:14: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed

state to down

000392: *Aug 3 17:34:17: %LINK-3-UPDOWN: Interface GigabitEthernet0/19, changed

state to up

000393: *Aug 3 17:34:18: %LINEPROTO-5-UPDOWN: Line protocol on Interface Gigabi

tEthernet0/19, changed state to up

000394: *Aug 3 18:25:19: %SYS-6-CLOCKUPDATE: System clock has been updated from

18:25:19 UTC Tue Aug 3 1993 to 21:25:19 MSK Tue Aug 3 1993, configured from con

sole by on console.

000395: *Aug 3 18:25:19: %SYS-6-CLOCKUPDATE: System clock has been updated from

21:25:19 MSK Tue Aug 3 1993 to 21:25:19 MSK Tue Aug 3 1993, configured from con

sole by on console.

000396: *Jul 17 17:42:00: %SYS-6-CLOCKUPDATE: System clock has been updated from

21:25:19 MSK Tue Aug 3 1993 to 20:42:00 MSK Thu Jul 17 2008, configured from co

nsole by on console.

ES-SW15#

majdalani · ‎07-17-2008

hi again,

would it differ if i used the following command : no shutdown ?

would this command makes the port status always up ?

Jerry Ye · ‎07-17-2008

"no shutdown" will enable the port. "shutdown" will put the port into admin down state.

You might have a physical problem such as bad port on the server, cable problem, even bad port on the switch. If you have service contract, please contact Cisco TAC.

HTH,

jerry