cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
424
Views
0
Helpful
4
Replies

Ports Going up and Down

remmus
Level 1
Level 1

HI All,

I'm running a switched environment and have a kiwi syslog server. My logs shows ports going up and down eventhough the workstation connected is not being rebooted. I was wondering what could be triggering this. I've pasted a copy of the log. I hope you guys could give me a feedback regarding this. Any help is much appreiated. Thanks!

2003-07-24 06:28:26 Local5.Error 164.179.168.20 2699: *Mar 11 15:02:26.446 UTC: %LINK-3-UPDOWN: Interface FastEthernet0/17, changed state to up

2003-07-24 06:28:27 Local5.Notice 164.179.168.20 2700: *Mar 11 15:02:26.933 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, changed state to up

2003-07-24 06:28:29 Local5.Error 164.179.168.20 2701: *Mar 11 15:02:29.681 UTC: %LINK-3-UPDOWN: Interface FastEthernet0/17, changed state to down

2003-07-24 06:28:30 Local5.Notice 164.179.168.20 2702: *Mar 11 15:02:29.938 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, changed state to down

2003-07-24 06:28:31 Local5.Error 164.179.168.20 2703: *Mar 11 15:02:31.222 UTC: %LINK-3-UPDOWN: Interface FastEthernet0/17, changed state to up

2003-07-24 06:28:31 Local5.Notice 164.179.168.20 2704: *Mar 11 15:02:31.951 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, changed state to up

2003-07-24 06:28:32 Local5.Error 164.179.168.20 2705: *Mar 11 15:02:32.706 UTC: %LINK-3-UPDOWN: Interface FastEthernet0/17, changed state to down

2003-07-24 06:28:33 Local5.Notice 164.179.168.20 2706: *Mar 11 15:02:32.957 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, changed state to down

2003-07-24 06:28:34 Local5.Error 164.179.168.20 2707: *Mar 11 15:02:34.258 UTC: %LINK-3-UPDOWN: Interface FastEthernet0/17, changed state to up

1 Accepted Solution

Accepted Solutions
4 Replies 4

burleyman
Level 8
Level 8

What are the speed and duplex settings on fe0/17 and the workstation's NIC? make sure they are the same. Also if you have them set to Auto try hard-coding them. Have you moved the work station to another port on the switch? What is the length of cable from the switch to the workstation?

Just a start...

Cheers,

Burleyman

Like says Burleyman,

-> Verify the duplex and speed setting in both sides.

-> Lenght of cable.

-> If the NIC is configure to sleep or not ?

-> Are there errors on this interface (show interface fa0/17) ?

Best Regards.

r.redd
Level 1
Level 1

Also check were you are logging the messages, you might be logged them locally and filling up the que. That will also kill the interface.

Prashanth Krishnappa
Cisco Employee
Cisco Employee

Review Cisco Networking for a $25 gift card