Cisco 6000 switch issue with console and ip address

[Rambocious]

Hello,

I have a Cisco Catalyst 6006 switch for my main switch on the network. I also have a server that runs IP MONITOR software. I received an alert that the switch ws not responding to the monitor (the monitor pings the ip address of the switch). I can not telnet or connect via console to it. BUT the switch and the router are working normally. I can log into the Router portion but not the switch portion to see the problem. Any ideas would be helpful.

Thanks!

 

[vipergg]

Sounds like it somehow got into switch-console mode ,from the console try logging into the router portion then issue a " shift ccc and see if it switches back to the l2 side . From the router side if you issue a show cdp neighbor does it see the layer 2 side ? Can you ping the l2 address from the router side ? All else fails you may have to try and reload the box .

 

[Rambocious]

Thanks for respponding.

I can not ping nor does cdp work.

This is from the log-
-------------------------------------------
Sep 15 21:32:47: %SCP-4-DACK_TIMEOUT_MSG: SCP delivery ack timeout for opcode=11
D
Sep 15 21:33:47: %SCP-4-DACK_TIMEOUT_MSG: SCP delivery ack timeout for opcode=11
D
Sep 15 21:34:47: %SCP-4-DACK_TIMEOUT_MSG: SCP delivery ack timeout for opcode=11
D
-------------------------------------------

 

[vipergg]

I think with that code it's time to reload , it looks like it has stopped talking to the l2 side . Ran this thru the output interpretor here is what it says. You might to check and see if there is any known bugs with the versions you are running .

%SCP-4-DACK_TIMEOUT_MSG (x1): SCP delivery ack timeout for opcode=[hex]

Explanation: This message indicates that the route processor did not receive
SCP delivery acknowledgements from the switch processor after two retries. [hex]
identifies the operational code.

Recommended Action: Copy the error message exactly as it appears on the console
or in the system log. Enter the show tech-support command to gather data that may
provide information about the error. If you cannot determine the type of error
from the error message text or from the show tech-support output, contact your
Cisco technical support representative, and provide the representative with the
gathered information.

 

[jeter]

Here is what I found on this problem..


1. %SCP-4-DACK_TIMEOUT_MSG: SCP delivery ack timeout for opcode=[hex]
This message indicates that the route processor did not receive SCP delivery acknowledgements from the switch processor after two retries. [hex] identifies the operational code.

Recommended Action: Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may provide information about the error. If you cannot determine the type of error from the error message text or from the show tech-support output, contact your Cisco technical support representative, and provide the representative with the gathered information.


2. %SCP-4-DACK_TIMEOUT_MSG: SCP delivery ack timeout for opcode=[hex]
The RP did not receive SCP delivery acknowledgment from the SP after two retries.

Recommended Action: Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.




“Reserve your right to think, for even to think wrongly is better than not to think at all”

Fisher CCNP,CCNA Network+