|
In the context of abnormal behavior, there are multiple ways to clear or restart the routine engine process.
- Restart the entire routing engine using the below command. It is important to note that this will affect all the traffic in the device hence need to do it during a maintenance window:
execute router restart
- If the issue is only on a specific protocol, clear or restart the respective routing protocol as below:
OSPF:
execute router clear ospf process<----- This will clear all the OSPF processors.
BGP:
execute router clear bgp <options>
all Clear all BGP peers. [Take 0-5 arg(s)] <----- Used for BGP hard reset.
as Clear BGP peer by AS number. [Take 0-6 arg(s)]
dampening Clear route flap dampening information. [Take 0-1 arg(s)]
external Clear all external peers. [Take 0-2 arg(s)]
flap-statistics Clear route flap statistics. [Take 0-1 arg(s)]
ip Clear BGP peer by IP address. [Take 0-6 arg(s)]
ipv6 Clear BGP peer by IPv6 address. [Take 0-6 arg(s)]
After selecting the above option, select more arguments based on the option selected.
Example:
execute router clear bgp all
<args...> Input arguments:
<none>
in
in prefix-filter
out
vrf-leak
vpnv4 unicast soft [in|out]
soft [in|out|vrf-leak]<----- Soft reset of BGP routes IN or OUT and VRF leak.
- BFD session is another option possible to clear using this command:
execute router clear bfd session <Source IP> <Destination IP> <Interface>
BFD session details can be found using the below commands:
get router info bfd neighbor
get router info bfd requests
Related documents:
BFD
Troubleshooting BGP
Basic OSPF example
|
