1
This is the view of the dashboard of an operating data center fabric in a remote location. Earlier, one of the devices in the network was experiencing problems, and a technician replaced that device. This display reflects the status of the network after he has reactivated the new device. At a glance, we can quickly see few BGP anomalies as well as some cabling anomalies
We will scroll down further to view other details.
This is the view of the dashboard of an operating data center fabric in a remote location. Earlier, one of the devices in the network was experiencing problems, and a technician replaced that device. This display reflects the status of the network after he has reactivated the new device. At a glance, we can quickly see few BGP anomalies as well as some cabling anomalies
We will scroll down further to view other details.
There are some Route Table anomalies as well.
We will scroll down further to view other details.
There are some Route Table anomalies as well.
We will scroll down further to view other details.
The devices appear to be in good health and no issues have been identified.
The red dots of various sizes indicate there are issues in certain nodes in the network. We will click on the Border Rack Leaf 1 to view more details.
The devices appear to be in good health and no issues have been identified.
The red dots of various sizes indicate there are issues in certain nodes in the network. We will click on the Border Rack Leaf 1 to view more details.
For example, border rack leaf one has two BGP anomalies, one cabling anomaly, and nine route table anomalies.
As next steps, let us click on the Active tab to view more details.
For example, border rack leaf one has two BGP anomalies, one cabling anomaly, and nine route table anomalies.
As next steps, let us click on the Active tab to view more details.
Notice there are two BGP anomalies, one cabling anomaly, and nine route table anomalies.
From this view we can see all the devices in the fabric and a color-coded status for each one. On the right side we have the telemetry coming from all devices in the fabric, this reflects the same information we saw in the dashboard view.
From this view we can see all the devices in the fabric and a color-coded status for each one. On the right side we have the telemetry coming from all devices in the fabric, this reflects the same information we saw in the dashboard view.
Let us drill into this specific leaf device and see more details. We notice 2 route anomalies, meaning two routes are missing from the table. Apstra knows from the intent model what routes should be present, and it compares the current state to the intended state. This is what is meant by intent-based networking.
Let us drill into this specific leaf device and see more details. We notice 2 route anomalies, meaning two routes are missing from the table. Apstra knows from the intent model what routes should be present, and it compares the current state to the intended state. This is what is meant by intent-based networking.
Notice and confirm the cabling mismatch error
Notice and confirm the cabling mismatch error
Click on the active tab to view the active configuration
Click on the Spine switch
Click on the rootcause tab
Click on connectivity
We can see three devices associated with the root causes, spine 2, border rack leaf one, and border rack leaf 2.
We can see three devices associated with the root causes, spine 2, border rack leaf one, and border rack leaf 2.
The tabular View provides details about how these root causes were identified.
Root Cause Identification (RCI) informs us the two spine leaf links are down. It was deterined because of the relationship of the associated anomalies to the intent based model.
The tabular View provides details about how these root causes were identified.
Root Cause Identification (RCI) informs us the two spine leaf links are down. It was deterined because of the relationship of the associated anomalies to the intent based model.
Click on links
Traditionally, the technician in the remote location would have to go to the location in person, and examine the rack and the device and the cables that he installed, but Apstra gives us an more efficient way to resolve this problem. Click on the links tab to continue
Traditionally, the technician in the remote location would have to go to the location in person, and examine the rack and the device and the cables that he installed, but Apstra gives us an more efficient way to resolve this problem. Click on the links tab to continue
Because we can pull the current LLDP data from the devices, which is the same information that was used by the root cause identification process to identify the problems., we can update this cabling map from that data instead of physically changing the cables.
Because we can pull the current LLDP data from the devices, which is the same information that was used by the root cause identification process to identify the problems., we can update this cabling map from that data instead of physically changing the cables.
By updating , the system will automatically configure the ports for the appropriate devices on the other end
By updating , the system will automatically configure the ports for the appropriate devices on the other end
Click on Uncommited tab
This is a pre-change analysis that allows us to verify what is going to happen before pushing the changes to the production network. In this case, these links are going to be swapped.
This is a pre-change analysis that allows us to verify what is going to happen before pushing the changes to the production network. In this case, these links are going to be swapped.
Click Commit to commit the changes
Click on Dashboard
We can see that all the anomalies are cleared and the network is operating in the intended state.
We can see that all the anomalies are cleared and the network is operating in the intended state.
Anomalies are cleared out
Welcome! Click to start the walkthrough
You have reached the end of this walkthrough. Thank you!
- This is the view of the dashboard of an operating data center fabric in a remote location. Earlier, one of the devices in the network was experiencing problems, and a technician replaced that device. This display reflects the status of the network after he has reactivated the new device. At a glance, we can quickly see few BGP anomalies as well as some cabling anomalies We will scroll down further to view other details.
- Notice the Route Table anomalies
- The devices appear to be in good health and no issues have been identified. The red dots of various sizes indicate there are issues in certain nodes in the network. We will click on the Border Rack Leaf 1 to view more details.
- For example, border rack leaf one has two BGP anomalies, one cabling anomaly, and nine route table anomalies.As next steps, let us click on the Active tab to view more details.
- From this view we can see all the devices in the fabric and a color-coded status for each one. On the right side we have the telemetry coming from all devices in the fabric, this reflects the same information we saw in the dashboard view.
- Let us drill into this specific leaf device and see more details. We notice 2 route anomalies, meaning two routes are missing from the table. Apstra knows from the intent model what routes should be present, and it compares the current state to the intended state. This is what is meant by intent-based networking.
- Notice the cabling mismatch error
- Click on the active tab to view the active configuration
- Click on the Spine switch
- Click on the rootcause tab
- Click on connectivity
- We can see three devices associated with the root causes, spine 2, border rack leaf one, and border rack leaf 2.
- The tabular View provides details about how these root causes were identified.Root Cause Identification (RCI) informs us the two spine leaf links are down. It was deterined because of the relationship of the associated anomalies to the intent based model.
- Click on links
- Traditionally, the technician in the remote location would have to go to the location in person, and examine the rack and the device and the cables that he installed, but Apstra gives us an more efficient way to resolve this problem. Click on the links tab to continue
- Because we can pull the current LLDP data from the devices, which is the same information that was used by the root cause identification process to identify the problems., we can update this cabling map from that data instead of physically changing the cables.
- By updating , the system will automatically configure the ports for the appropriate devices on the other end
- Click on Uncommited tab
- This is a pre-change analysis that allows us to verify what is going to happen before pushing the changes to the production network. In this case, these links are going to be swapped.
- Click Commit to commit the changes
- Click on Dashboard
- We can see that all the anomalies are cleared and the network is operating in the intended state.
- Anomalies are cleared out