FAS8300 Controller failover of node_name is not possible: unsynchronized log
Applies to
- FAS8300
- ONTAP 9
Issue
- EMS reports controller failover of partner node is not possible with unsynchronized log.
Example:
Tue May 23 09:23:00 [FAS8300B: monitor: monitor.globalStatus.critical:EMERGENCY]: Controller failover of FAS8300A is not possible: unsynchronized log.
- CRC errors are observed on e0a.
Example:
-- interface e0a (699 days, 21 hours, 52 minutes, 26 seconds) -- RECEIVE Total frames: 124m | Frames/second: 2 | Total bytes: 183g Bytes/second: 3030 | Total errors: 143m | Errors/minute: 143 Total discards: 0 | Discards/minute: 0 | Multi/broadcast: 124m Non-primary u/c: 0 | Errored frames: 0 | Unsupported Op: 0 CRC errors: 132m | Runt frames: 0 | Fragment: 337k Long frames: 0 | Jabber: 0 | Length errors: 0 Alignment errors: 0 | No buffer: 0 | Pause: 0 Jumbo: 0 | Error symbol: 10532k | Bus overruns: 0 Queue drops: 0 | LRO segments: 0 | LRO bytes: 0 LRO6 segments: 0 | LRO6 bytes: 0 | Bad UDP cksum: 0 Bad UDP6 cksum: 0 | Bad TCP cksum: 0 | Bad TCP6 cksum: 0 Mcast v6 solicit: 0 | Lagg errors: 0 | Lacp errors: 0 Lacp PDU errors: 0