92
edits
Border reboot: Difference between revisions
Jump to navigation
Jump to search
→Pre-flight checks
No edit summary |
|||
| (10 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
Note: Throughout this guide <ipv4> and <ipv6> are to be replaced by the correct IP's. | Note: Throughout this guide <ipv4> and <ipv6> are to be replaced by the correct IP's. If you don't know, you can press the 'tab' key (twice) on your keyboard after typing 'neighbors' to get shown the options. | ||
== | == Pre-flight checks == | ||
These checks are to be done on the | These checks are to be done on the '''OTHER''' border (So the border that will stay online), to ensure that when the border that's being rebooted is down the cluster won't lose network connectivity. The commands are to be invoked in `vtysh`. | ||
* Confirm our IPv4 block is announced over BGP with `show ip bgp neighbors <ipv4> advertised-routes` | * Confirm our IPv4 block is announced over BGP with `show ip bgp neighbors <ipv4> advertised-routes` | ||
* Confirm our IPv6 block is announced over BGP with `show bgp neighbors <ipv6> advertised-routes` | * Confirm our IPv6 block is announced over BGP with `show bgp neighbors <ipv6> advertised-routes` | ||
* 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` | ||
These checks are to be done on the host you want to reboot | |||
* Set a maintenance period on Zabbix. | |||
* Post in the Zulip in the relevant topic (incident's topic / 'SRE - General' stream) that the border is going to be rebooted. | |||
== Disabling routing through a border == | == Disabling routing through a border == | ||
* First, perform the pre-flight checks on the '''OTHER''' border. | |||
* Second, set a maintenance period on Zabbix for the border that's being rebooted. | |||
Third, on a border in `vtysh`, update the running configuration by invoking the following: | |||
* config | * config | ||
| Line 21: | Line 28: | ||
* router ospf6 | * router ospf6 | ||
* no default-information originate | * no default-information originate | ||
* exit | |||
* exit | * exit | ||
* exit | * exit | ||
| Line 26: | Line 34: | ||
== Reboot the border == | == Reboot the border == | ||
Execute `reboot` command | * 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 | |||
* 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 == | ||