[nsp] Strange MSFC error

BALIGANT Francois WANADOO francois.baligant at wanadoo.com
Mon May 5 17:50:50 EDT 2003


	See http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/12_1e/msgguide/emsg.htm#1034844


	Basically, the MSFC cannot send message anymore to the switch supervisor. While layer2 switching
	still *seems* to work, the MSFC cannot sync it anymore with routing changes computed/received
	from routing protocols (BGP/OSPF you name it) and so the MLS table on the Supervisor will slowly
	get out of sync, leading to unreachable hosts.

	Best bet is to take a 'sh tech-support' and then force a complete switchover (sup+MSFC)

	Good luck,
	Francois

-----Message d'origine-----
De : Xavier [mailto:xavier at rootshell.be]
Envoyé : lundi 5 mai 2003 16:25
À : cisco-nsp at puck.nether.net
Objet : [nsp] Strange MSFC error


Yup!

We received the following error msg on console/syslog from the active MSFC on a
C6509 switch:

May  5 16:23:20 [195.74.193.253.202.221] 369: May  5 14:23:19: %SCP-4-DACK_TIMEOUT_MSG: SCP delivery ack timeout for opcode=11D

The supervisor consoles are unavaible! The IP stack of the switch seems "out".
No telnet, no snmp... but it still process its switching tasks!

This problem occured after a 'commit security acl ...' on the switch...
Any idea?

--
http://www.rootshell.be
echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sb20293A2058554E494Csnlbxq'|dc

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list