Now that we have identified our issue with data collection and established a possible cause with our hypothesis, we can start our next troubleshooting step: using trial and error to correct the issue.
To correct our issue, we need to remove the invalid route for
192.168.33.11. To do this, we will yet again use the
ip command, this time with the
route del options.
[db]# ip route del 192.168.33.11 [db]# ip route show default via 10.0.2.2 dev enp0s3 proto static metric 1024 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.16 169.254.0.0/16 dev enp0s8 scope link metric 1003 192.168.33.0/24 dev enp0s8 proto kernel scope link src 192.168.33.12
In the preceding example, we used the
ip command with the ...