...
ISR1100 running IOS-XE in-built subslot 0/0 is reloading and is not being recognized in time which could lead to sub-slot "Out of service"
Control packet loss can happen due to timing issue and if multiple control packets loss happens, subslot will be reloaded. %IOMD-3-MODULE_MESSAGE: C0/0: iomd: 4x1G[0/0] NGIO control packet loss detected: module reloading %IOMD-3-MODULE_MESSAGE: C0/0: iomd: 4x1G[0/0] NGIO control packet loss detected: module reloading %IOMD-3-MODULE_MESSAGE: C0/0: iomd: 4x1G[0/0] NGIO control packet loss detected: module reloading %IOMD-3-MODULE_MESSAGE: C0/0: iomd: 4x1G[0/0] NGIO control packet loss detected: module reloading %IOMD-3-MODULE_MESSAGE: C0/0: iomd: 4x1G[0/0] NGIO control packet loss detected: module reloading %IOMD-3-MODULE_MESSAGE: C0/0: iomd: 4x1G[0/0] NGIO control packet loss detected: module reloading {IOSRP_R0-0}{1}: [iosrp] [24975]: (ERR): *Jan 25 15:22:42.533: %IOMD-3-MODULE_MESSAGE: C0/0: iomd: 4x1G[0/0] NGIO control packet loss detected: module reloading %IOMD-3-MODULE_MESSAGE: C0/0: iomd: 4x1G[0/0] NGIO control packet loss detected: module reloading %IOMD-3-MODULE_MESSAGE: C0/0: iomd: 4x1G[0/0] NGIO control packet loss detected: module reloading %IOMD-3-MODULE_MESSAGE: C0/0: iomd: 4x1G[0/0] NGIO control packet loss detected: module reloading %IOMD-3-MODULE_MESSAGE: C0/0: iomd: 4x1G[0/0] NGIO control packet loss detected: module reloading %IOMD-3-MODULE_MESSAGE: C0/0: iomd: 4x1G[0/0] NGIO control packet loss detected: module reloading %IOMD-3-MODULE_MESSAGE: C0/0: iomd: 4x1G[0/0] NGIO control packet loss detected: module reloading show platform Chassis type: ISR1100-4GLTENA Slot Type State Insert time (ago) --------- ------------------- --------------------- ----------------- 0 ISR1100-4GLTENA ok 03:23:47 0/0 4x1G out of service 00:23:50 <<<< 0/1 F_4GLTENA ok 03:20:45 R0 ISR1100-4GLTENA ok, active 03:23:47 F0 ISR1100-4GLTENA ok, active 03:23:47 Slot CPLD Version Firmware Version --------- ------------------- --------------------------------------- 0 20122333 17.4(2r) R0 20122333 17.4(2r) F0 20122333 17.4(2r)
Reload the router could fix the issue.
This issue seems to affect 17.6.1 and 17.6.2 code.