Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
Date: 2018-08-10 16:38:42 UTC When the B came back, some loss has been seen on network 66.70.180.0/24 and 66.70.181.0/24. Everything is back normal now. We had a BGP misconfiguration on these 2x/24 and we corrected the configuration.
Date: 2018-08-10 16:37:39 UTC /var/log/switchs.log:2018-08-10T18:19:03+02:00 10.95.80.3 bhs5-sd1b-n9.qc.ca ba [local7.crit] === : 2018 Aug 10 18:19:01.221 CEST: %SYSMGR-SLOT1-2-LAST_CORE_BASIC_TRACE: core_client_main: PID 1033 with message filename = 0x102_ipfib_log.26844.tar.gz .
/var/log/switchs.log:2018-08-10T18:19:04+02:00 10.95.80.3 bhs5-sd1b-n9.qc.ca bb [local7.err] === : 2018 Aug 10 18:19:02.222 CEST: %TACACS-3-TACACS_ERROR_MESSAGE: All servers failed to respond
/var/log/switchs.log:2018-08-10T18:19:04+02:00 10.95.80.3 bhs5-sd1b-n9.qc.ca ba [local7.crit] === : 2018 Aug 10 18:19:02.223 CEST: %MODULE-2-MOD_DIAG_FAIL: Module 1 (Serial number: SAL1946T100) reported failure due to Service on linecard had a hap-reset in device DEV_SYSMGR (device error 0x17a)
The device is back online.
We will open a case to our manufacturer.
Posted Aug 10, 2018 - 16:27 UTC
This incident affected: Infrastructure || BHS (BHS5).