What does the sense data that I receive from the show extended channel slot/port subchannel command mean?
A. The sense data denotes this: Byte Bit Meaning Byte 0 0 Command Reject 1 Intervention required 2 Bus-out check 3 Equipment check 4 Data check 5 Overrun 6 Reserved 7 Cancel Byte 1 0 Resetting Event 1 Reserved 2 Reserved 3 Reserved 4 Reserved 5 Reserved 6 Reserved 7 Reserved Q. What do the 4 resyncs mean in this show controller cbus command output from a Cisco 7000 router with Cisco IOS Software Release 11.0(10): CIP 4, hardware version 5.0, microcode version 21.10 Microcode loaded from flash slot0:cipp2110.bin Controller Sync: 4 timeouts, 4 resyncs 0 failures, 0 max phase count The Route Processor (RP) sends commands to the CIP via the Switch Processor (SP). The SP gives the CIP 12 µs to respond. If it does not respond in time, the RP counts a time-out: there were four of them. The RP then retries the request; part of the retry process is to make ensure that the CIP and the RP are synchronized and that the CIP is responding to the correct request. There were four resynchronization att
A. The sense data denotes this: Byte Bit Meaning Byte 0 0 Command Reject 1 Intervention required 2 Bus-out check 3 Equipment check 4 Data check 5 Overrun 6 Reserved 7 Cancel Byte 1 0 Resetting Event 1 Reserved 2 Reserved 3 Reserved 4 Reserved 5 Reserved 6 Reserved 7 Reserved Q. What do the 4 resyncs mean in this show controller cbus command output from a Cisco 7000 router with Cisco IOS Software Release 11.0(10): CIP 4, hardware version 5.0, microcode version 21.10 Microcode loaded from flash slot0:cipp2110.bin Controller Sync: 4 timeouts, 4 resyncs 0 failures, 0 max phase count A. The Route Processor (RP) sends commands to the CIP via the Switch Processor (SP). The SP gives the CIP 12 ??s to respond. If it does not respond in time, the RP counts a time-out: there were four of them. The RP then retries the request; part of the retry process is to make ensure that the CIP and the RP are synchronized and that the CIP is responding to the correct request. There were four resynchronization
