Slash MTTR from several days to just minutes.
Transcript: Troubleshooting & Incident Resolution
When something is not reachable in the
network, the first question is always
where the path is actually broken. And
here is where IP fabric end to end path
can support the analysis. I enter here
the source IP and the destination IP
where I know the problem exists and IP
fabric draw the exact path hop by hop
including the information about routing
decision about ACL load balancing for
every device it touch no need to access
via console no need to run in thrice
root to check what is the correct part
but the real power is comparing that to
what I had before
IP fabric take a full snapshot of the
network automatically. So I can rewind
to right before the incident and run the
exact same pat look up and instantly see
what is the difference.
Do I have the same rule set? Do I have
the same routting table? the same
interface configuration or even I can
swap here to the compare view and see
what is changed in the configuration of
the device. I have the diff between the
two snapshot that show exactly what it
moved in my configuration. Maybe a newcl
policy, a route that disappear or a
complete new config pushed just before
the incident.
And that’s help to identify the root
cause without grapping logs across all
the devices.
