Problem with 4510R commutation

[Sergey Aleshinsky]

Hi!

I have a problem with my Cisco4510R.

When i connect a HP server on slot 1 port gi1/17 the port doesn't become at UP state, console log shows me information that cable is not connect. But when i plug cable into 2960 switch port become Up.

What can it be? Best regards, Sergey.

[Rajeev Sharma]

Hey Sergey,

Clearly its a physical layer issue. Check which cable you are using i.e. crossover or straight, later is preferred. Also try hard coding speed and duplex on the interface.

HTH.

Regards,

RS.

[Sergey Aleshinsky]

rajeevsh,

thank you for your answer, but it's very easy

Of course I checked cable and tuned up port to hard 100/full.

Google help me to understand, that problem is more complex than its looks.

There are problem with supervisor WS-X45-SUP7-E.

I found this article:

line cards stop responding to interface changes

Symptom: One or more line cards stop responding to interface changes and ports remain down/down (notconnect) when connected to hosts. Interfaces that are already in the link-up state are not affected.Conditions: The problem only affects WS-X45-SUP7-E supervisors running 03.01.00.SG, 03.01.01.SG, 03.02.00.SG or 03.02.01.SG. The line cards that can be affected are in the WS-X46xx series and the WS-X47xx series. Earlier line cards are not affected.Workaround: Upgrade to 3.2.5SG (3.2.2SG and higher has the fix).Further information Avoid triggering the issue by eliminating link flap. If module < n> is already in the problem state: - reload the linecard module by doing 'hw-module module < n> reset'. OR - if you have dual supervisors, perform a switchover

So that is it, I think. 

[Rajeev Sharma]

Hey Sergey,

In the initial post you mentioned that same interface is coming up when connected to the 2960 switch so i doubt that we are running in to this bug, however it can be confirmed if you may reload the module with 'hw-module module 1 reload' command.

HTH.

regards,

RS.

[Sergey Aleshinsky]

Thank you, for your help!

I successfully reload this module.

I assumed that this problem can be solved without reload command =)