58
edits
Border reboot: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 7: | Line 7: | ||
* Confirm that the border receives the ROUTED IPv4 routes from the router with `show ip route` | * Confirm that the border receives the ROUTED IPv4 routes from the router with `show ip route` | ||
* Confirm that the border received the ROUTED & LAN IPv6 routes from the router with `show ipv6 route` | * Confirm that the border received the ROUTED & LAN IPv6 routes from the router with `show ipv6 route` | ||
Set a maintenance period for the host on Zabbix | |||
== Disabling routing through a border == | == Disabling routing through a border == | ||
| Line 26: | Line 28: | ||
== Reboot the border == | == Reboot the border == | ||
After performing the pre-flight checks and disabling the routing, you can choose to wait until traffic has decreased (e.g. using `bmon` to check bandwidth used on interfaces) | * After performing the pre-flight checks and disabling the routing, you can choose to wait until traffic has decreased (e.g. using `bmon` to check bandwidth used on interfaces) | ||
* Execute `reboot` command | |||
Execute `reboot` command | * When the border is back online, execute relavant items (system uptime, operating system, reboot required) to ensure these will not activate a trigger after disabling maintenance mode | ||
* If you do not expect any Zabbix alert related to the reboot to be fired, delete the maintenance period | |||
== Troubleshooting == | == Troubleshooting == | ||