Border reboot: Difference between revisions
No edit summary |
No edit summary |
||
Line 23: | Line 23: | ||
* exit | * exit | ||
* exit | * exit | ||
== Reboot the border == | |||
Execute `reboot` command | |||
== Troubleshooting == | == Troubleshooting == |
Revision as of 06:38, 19 February 2024
Note: Throughout this guide <ipv4> and <ipv6> are to be replaced by the correct IP's.
Preflight checks
These checks are to be done on the other border (So the border that will stay online). 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 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 received the ROUTED & LAN IPv6 routes from the router with `show ipv6 route`
Disabling routing through a border
On a border in `vtysh`, update the running configuration by invoking the following:
- config
- router bgp
- neighbor <ipv4> shutdown
- neighbor <ipv6> shutdown
- exit
- router ospf
- no default-information originate
- exit
- router ospf6
- no default-information originate
- exit
- exit
Reboot the border
Execute `reboot` command
Troubleshooting
Undoing the shutdown of the neighbors can be done by invoking `no neighbor <ipv4>/<ipv6> shutdown` in the `router bgp` part of the configuration.
And the `no default-information originate` can be undone by invoking `default-information originate` in the corect ospf part of the configuration (ospf or ospf6, depending on which one you wish to re-enable).
A reload/restart of the service will also reset to normal configuration.