Abstract: A method that includes retrieving a first list of routing prefixes learned by a border node in a first network fabric and retrieving a second list comprising addresses of nodes in a second network fabric. The method also includes generating a dependency mapping based on the routing prefixes in the first list and the addresses in the second list. The dependency mapping indicates that network traffic to the addresses of the nodes in the second network fabric is affected by the border node in the first network fabric. The method further includes, in response to detecting that the border node in the first network fabric has malfunctioned and based on the dependency mapping, generating an alert indicating that network traffic to the addresses of the nodes in the second network fabric is affected by the border node in the first network fabric malfunctioning.

Abstract: A method that includes retrieving a first list of routing prefixes learned by a border node in a first network fabric and retrieving a second list comprising addresses of nodes in a second network fabric. The method also includes generating a dependency mapping based on the routing prefixes in the first list and the addresses in the second list. The dependency mapping indicates that network traffic to the addresses of the nodes in the second network fabric is affected by the border node in the first network fabric. The method further includes, in response to detecting that the border node in the first network fabric has malfunctioned and based on the dependency mapping, generating an alert indicating that network traffic to the addresses of the nodes in the second network fabric is affected by the border node in the first network fabric malfunctioning.

Abstract: Embodiments herein describe techniques for creating a lightweight snapshot of a network fabric without having to capture snapshots at a predefined interval. Instead, the snapshot system uses a data store to capture state changes to network objects in the network fabric. Because the data store captures these state changes (along with timestamps indicating when these changes occurred), the snapshot system can retroactively generate snapshots of the network fabric at any desired time. In one embodiment, the snapshot system includes an event detector that determines when to capture snapshots. Once an event is identified by the event detector, the snapshot system can use the historical changes in the data store to retroactively generate a first snapshot to capture the overall state of the network fabric before the event and a second snapshot to capture the overall state of the network fabric after the event.

Abstract: Embodiments herein describe techniques for creating a lightweight snapshot of a network fabric without having to capture snapshots at a predefined interval. Instead, the snapshot system uses a data store to capture state changes to network objects in the network fabric. Because the data store captures these state changes (along with timestamps indicating when these changes occurred), the snapshot system can retroactively generate snapshots of the network fabric at any desired time. In one embodiment, the snapshot system includes an event detector that determines when to capture snapshots. Once an event is identified by the event detector, the snapshot system can use the historical changes in the data store to retroactively generate a first snapshot to capture the overall state of the network fabric before the event and a second snapshot to capture the overall state of the network fabric after the event.