Hi Van,
sr-reroute-network was designed as the last resort that can potentially recover some unexpected scenario.
We do not recommend running it regularly. This command will trigger system-wide route re-computation / re-programming, and can therefore create unnecessary churn.
I would suggest first checking the flows and groups in the scenario where traffic was disrupted, and conduct further investigation from there.
The information described
here may be useful figuring out which flow/group went wrong.
Thanks,
Charles Chan, Ph.D.Member of Technical Staff, Open Networking Foundation