topic Re: Who knows this problem with cisco7513 in Network Security

Who knows this problem with cisco7513

zhang.wei — Fri, 21 Feb 2020 07:48:58 GMT

%VIP4-80 RM7000-3-MSG: slot0 VIP-3-MVIP_CYBUSERROR_INTERRUPT: A Cybus Error occurred.

.Dec 17 21:31:52: %VIP4-80 RM7000-1-MSG: slot0 CYASIC Error Interrupt register 0x8

.Dec 17 21:31:52: %VIP4-80 RM7000-1-MSG: slot0 Parity Error internal to CYA

.Dec 17 21:31:52: %VIP4-80 RM7000-1-MSG: slot0 CYASIC Other Interrupt register 0x180

.Dec 17 21:31:52: %VIP4-80 RM7000-1-MSG: slot0 QE RX HIGH Priority Interrupt

.Dec 17 21:31:52: %VIP4-80 RM7000-1-MSG: slot0 QE TX HIGH Priority Interrupt

.Dec 17 21:31:52: %VIP4-80 RM7000-1-MSG: slot0 CYBUS Error Cmd/Addr 0xD001A0A

.Dec 17 21:31:52: %VIP4-80 RM7000-1-MSG: slot0 MPUIntfc/PacketBus Error register 0x0

.Dec 17 21:31:52: %VIP4-80 RM7000-1-MSG: slot0 IOBUS Error Interrupt Status register 0x0

.Dec 17 21:32:04: %VIP4-80 RM7000-3-MSG: slot0 VIP-3-SVIP_RELOAD: SVIP Reload is called.

.Dec 17 21:32:04: %VIP4-80 RM7000-3-MSG: slot0 VIP-3-SYSTEM_EXCEPTION: VIP System Exception occurred sig=22, code=0x0, context=0x60AB4B68

.Dec 17 21:32:05: %DBUS-3-DBUSINTERRSWSET: Slot 0, Internal Error due to VIP crash

.Dec 17 21:32:05: %LB-5-CHAN_MEMBER_OUT: FastEthernet0/0/0 taken out of Port-channel1

marinos_g — Tue, 21 Dec 2004 13:14:57 GMT

Here is what the output interpreter came with:

%DBUS-3-DBUSINTERRSWSET (x1): Slot [dec], Internal Error due to VIP crash

Explanation: A processor reported an error. The processor will be reset and not

used until the next OIR event or microcode download, when it will be retested.

Recommended Action: Reinstall the processor or download the microcode. If this

message recurs, copy the error message exactly as it appears on the console or

in the system log, contact your Cisco technical support representative, and provide

the representative with the gathered information.

Here is another link

%VIP-3-MVIP_CYBUSERROR_INTERRUPT : A Cybus Error occurred.

Check out this bug too

zhang.wei — Thu, 23 Dec 2004 07:35:34 GMT

thanks a lot ,

we have changed the VIP-0 board ,the problem workaround