cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
911
Views
2
Helpful
3
Replies

9800-40 redundancy failed

Netzgruppe SCC
Level 1
Level 1

Hi,

our system with two 9800-40 (version 17.03.05b) is no longer redundant and brings the error message:

%BOOT-3-BOOTTIME_GET_ISSU_INFO_OF_REMOTE_CHASSIS_FAILED: Chassis 1 R0/0: issu_stack: Failed to get ISSU information from remote chassis. Details: Remote sync failed with error code: 10.

but I can't find any further information about it. What could be the reason for this?

Thanks !

Dieter

 

3 Replies 3

Leo Laohoo
Hall of Fame
Hall of Fame

@Netzgruppe SCC wrote:
What could be the reason for this?

Someone attempted, unsuccessfully, to upgrade the firmware using ISSU. 

marce1000
VIP
VIP

 

   - Most likely a bug similar too : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvz31188 , have a try with 17.9.3

      (Appendix1) , this is not directly related but useful :
                - Have a checkup of the current controller configuration (active) controller with the CLI command show tech wireless ; feed the output into : https://cway.cisco.com/wireless-config-analyzer/

    (Appendix2) ; a list of useful commands when troubleshooting HA-SSO 

show redundancy | i ptime|Location|Current Software state|Switchovers
show chassis
show chassis detail
show chassis ha-status local
show chassis ha-status active
show chassis ha-status standby
show chassis rmi
show redundancy
show redundancy history
show redundancy switchover history
show tech wireless redundancy
show redundancy states
show logging process stack_mgr internal to-file bootflash:

show platform hardware slot R0 ha_port interface stats
show interface `redundant interface` (check second line of output concerning Shadow  state)
show platform hardware slot R0 ha_port sfp idprom (show details of SFP in SP)

test wireless redundancy rping
test wireless redundancy packetdump start
test wireless redundancy packetdump start filter port <0-65535>
test wireless redundancy packetdump stop
  

show platform software stack-mgr chassis active R0 peer-timeout
show platform software stack-mgr chassis standby R0 peer-timeout
show platform software stack-mgr chassis active R0 sdp-counters
show platform software stack-mgr chassis standby R0 sdp-counters
show redundancy config-sync failures {bem|mcl|prc}
show redundancy config-sync historic mcl
show redundancy config-sync ignored failures historic mcl
show redundancy switchover history

 M.





 



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Rich R
VIP
VIP

You might need to break SSO - get the software in sync on both and then re-form SSO to get this fixed.
I reckon Leo's suggestion is a good bet, but like Marce says - get off 17.3 and upgrade to 17.9.3 - so many fixes and HA enhancements since 17.3.

Review Cisco Networking for a $25 gift card