Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
CPU overload on this router. We're looking for the source of the issue.
Update(s):
Date: 2015-08-11 08:49:36 UTC The card is again operational. We totally deactivated the faulty card this morning.
Date: 2015-08-11 08:48:53 UTC The card we added this afternoon seems to be faulty. Production switched to the first router. We will correct the faulty router.
Date: 2015-08-07 16:45:45 UTC The router is live. Another fault is stopping us from managing it remotely. We will investigate.
Date: 2015-08-07 16:45:00 UTC We pushed the router's configuration. It's gradually remounting. After we converge the routing protocol, the interfaces will slowly become active again.
No scheduled impact.
Date: 2015-08-07 16:43:53 UTC The router has rebooted.
Date: 2015-08-07 16:43:12 UTC The router is isolated. We will add the additional card.
Date: 2015-08-07 16:42:55 UTC We will isolate the router and add a monitoring card. When the card is ready, we will connect the router to it.
No scheduled downtime. The machines should re-arp.
Date: 2015-08-07 12:06:09 UTC We're getting a new monitoring card ready. We will insert it into another slot in the router. The cards should synchronise with one another so we can do a switch over. If that doens't work, we will need to reload the router. In all cases, we will isolate the router and the traffic will be routed via the 2nd router (rbx-s5-6k).
Date: 2015-08-07 12:04:32 UTC It seems that the issue is linked to the bootdisk configuration. The router is operating as normal, but we can't stay in this state.