Identify Network Issues and Accelerate Time to Resolution

Static Title

X Click here to view all steps
Don't show me again
0/23
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

1

1/23
Write
Preview
Write
Preview
Markdown
WYSIWYG
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

%3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E

%3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E

2/23
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

Notice the Route Table anomalies

There are some Route Table anomalies as well.

We will scroll down further to view other details.

3/23
Write
Preview
Write
Preview
Write\<br>
Preview\<br>
Write\<br>
Preview\<br>
Markdown\<br>
WYSIWYG
<br>
Markdown
WYSIWYG
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E

%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E

4/23
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Markdown
WYSIWYG
\\\
\\\
Markdown
WYSIWYG
\<br>
\<br>
Markdown
WYSIWYG
<br>
<br>
Markdown
WYSIWYG
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out
1

Notice there are two BGP anomalies, one cabling anomaly, and nine route table anomalies.

%3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E

%3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E

5/23
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Markdown
WYSIWYG
\\\\\
\\\\\
Markdown
WYSIWYG
\\\
\\\
Markdown
WYSIWYG
\<br>
\<br>
Markdown
WYSIWYG
<br>
<br>
Markdown
WYSIWYG
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

%3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E

%3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E

6/23
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Markdown
WYSIWYG
\\\\\\\\
\\\\\\\\
Markdown
WYSIWYG
\\\\\
\\\\\
Markdown
WYSIWYG
\\\
\\\
Markdown
WYSIWYG
\<br>
\<br>
Markdown
WYSIWYG
<br>
<br>
Markdown
WYSIWYG
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

%3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E

%3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E

7/23
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

Notice the cabling mismatch error

Notice and confirm the cabling mismatch error

8/23
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

Click on the active tab to view the active configuration

9/23
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

Click on the Spine switch

10/23
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

Click on the rootcause tab

11/23
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

Click on connectivity

12/23
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\<br>
\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\

\\\\\\

Markdown
WYSIWYG
\\\\
\\\\
Markdown
WYSIWYG
\\<br>
\\<br>
Markdown
WYSIWYG
\<br>
\<br>
Markdown
WYSIWYG
<br>
<br>
Markdown
WYSIWYG




Markdown
WYSIWYG
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

%3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E

%3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E

13/23
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\<br>
\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\
\\\\\\\\
Markdown
WYSIWYG
\\\\\
\\\\\
Markdown
WYSIWYG
\\\
\\\
Markdown
WYSIWYG
\<br>
\<br>
Markdown
WYSIWYG
<br>
<br>
Markdown
WYSIWYG
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

%3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E

%3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E

14/23
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

Click on links

15/23
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\<br>
\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\
\\\\\\\\
Markdown
WYSIWYG
\\\\\
\\\\\
Markdown
WYSIWYG
\\\
\\\
Markdown
WYSIWYG
\<br>
\<br>
Markdown
WYSIWYG
<br>
<br>
Markdown
WYSIWYG
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

%3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E

%3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E

16/23
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\<br>
\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\
\\\\\\\\
Markdown
WYSIWYG
\\\\\
\\\\\
Markdown
WYSIWYG
\\\
\\\
Markdown
WYSIWYG
\<br>
\<br>
Markdown
WYSIWYG
<br>
<br>
Markdown
WYSIWYG
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

%3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E

%3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E

17/23
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\<br>
\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\
\\\\\\\\
Markdown
WYSIWYG
\\\\\
\\\\\
Markdown
WYSIWYG
\\\
\\\
Markdown
WYSIWYG
\<br>
\<br>
Markdown
WYSIWYG
<br>
<br>
Markdown
WYSIWYG
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

%3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E

%3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E

18/23
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

Click on Uncommited tab

19/23
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

%3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E

%3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E

20/23
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

Click Commit to commit the changes

21/23
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

Click on Dashboard

22/23
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Write
Preview
Markdown
WYSIWYG
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\<br>
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

%3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E

%3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E

23/23
Prev
Next
Steps
  • %3Cp%3EThis%20is%20the%20view%20of%20the%20dashboard%20of%20an%20operating%20data%20center%20fabric%20in%20a%20remote%20location.%20Earlier%2C%20one%20of%20the%20devices%20in%20the%20network%20was%20experiencing%20problems%2C%20and%20a%20technician%20replaced%20that%20device.%20This%20display%20reflects%20the%20status%20of%20the%20network%20after%20he%20has%20reactivated%20the%20new%20device.%20At%20a%20glance%2C%20we%20can%20quickly%20see%20few%20BGP%20anomalies%20as%20well%20as%20some%20cabling%20anomalies%3C/p%3E%0A%3Cp%3EWe%20will%20scroll%20down%20further%20to%20view%20other%20details.%3C/p%3E
  • Notice the Route Table anomalies
  • %3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20devices%20appear%20to%20be%20in%20good%20health%20and%20no%20issues%20have%20been%20identified.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cspan%20style%3D%22font-size%3A%2013px%3B%22%3EThe%20red%20dots%20of%20various%20sizes%20indicate%20there%20are%20issues%20in%20certain%20nodes%20in%20the%20network.%20We%20will%20click%20on%20the%20Border%20Rack%20Leaf%201%20to%20view%20more%20details.%3C/span%3E%3C/p%3E
  • %3Cp%3EFor%20example%2C%20border%20rack%20leaf%20one%20has%20two%20BGP%20anomalies%2C%20one%20cabling%20anomaly%2C%20and%20nine%20route%20table%20anomalies.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3E%3Cbr%3EAs%20next%20steps%2C%20let%20us%20click%20on%20the%20Active%20tab%20to%20view%20more%20details.%3C/span%3E%3C/p%3E%0A%3Cp%3E%3Cbr%3E%3C/p%3E
  • %3Cp%3EFrom%20this%20view%20we%20can%20see%20all%20the%20devices%20in%20the%20fabric%20and%20a%20color-coded%20status%20for%20each%20one.%20On%20the%20right%20side%20we%20have%20the%20telemetry%20coming%20from%20all%20devices%20in%20the%20fabric%2C%20this%20reflects%20the%20same%20information%20we%20saw%20in%20the%20dashboard%20view.%3C/p%3E
  • %3Cp%3ELet%20us%20drill%20into%20this%20specific%20leaf%20device%20and%20see%20more%20details.%20We%20notice%202%20route%20anomalies%2C%20meaning%20two%20routes%20are%20missing%20from%20the%20table.%20Apstra%20knows%20from%20the%20intent%20model%20what%20routes%20should%20be%20present%2C%20and%20it%20compares%20the%20current%20state%20to%20the%20intended%20state.%20This%20is%20what%20is%20meant%20by%20intent-based%20networking.%3C/p%3E
  • 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
  • %3Cp%3EWe%20can%20see%20three%20devices%20associated%20with%20the%20root%20causes%2C%20spine%202%2C%20border%20rack%20leaf%20one%2C%20and%20border%20rack%20leaf%202.%26nbsp%3B%3C/p%3E
  • %3Cp%3EThe%20tabular%20View%20provides%20details%20about%20how%20these%20root%20causes%20were%20identified.%3C/p%3E%3Cp%3E%3Cspan%20style%3D%22font-family%3A%20var%28--app-body-font%29%20%3B%22%3ERoot%20Cause%20Identification%20%28RCI%29%20informs%20us%20the%20two%20spine%20leaf%20links%20are%20down.%20It%20was%20deterined%20because%20of%20the%20relationship%20of%20the%20associated%20anomalies%20to%20the%20intent%20based%20model.%3C/span%3E%3Cbr%3E%3C/p%3E
  • Click on links
  • %3Cp%3ETraditionally%2C%20the%20technician%20in%20the%20remote%20location%20would%20have%20to%20go%20to%20the%20location%20in%20person%2C%20and%20examine%20the%20rack%20and%20the%20device%20and%20the%20cables%20that%20he%20installed%2C%20but%20Apstra%20gives%20us%20an%20more%20efficient%20way%20to%20resolve%20this%20problem.%20Click%20on%20the%20links%20tab%20to%20continue%3C/p%3E
  • %3Cp%3EBecause%20we%20can%20pull%20the%20current%20LLDP%20data%20from%20the%20devices%2C%20which%20is%20the%20same%20information%20that%20was%20used%20by%20the%20root%20cause%20identification%20process%20to%20identify%20the%20problems.%2C%20we%20can%20update%20this%20cabling%20map%20from%20that%20data%20instead%20of%20physically%20changing%20the%20cables.%3C/p%3E
  • %3Cp%3EBy%20updating%20%2C%20the%20system%20will%20automatically%20configure%20the%20ports%20for%20the%20appropriate%20devices%20on%20the%20other%20end%3C/p%3E
  • Click on Uncommited tab
  • %3Cp%3EThis%20is%20a%20pre-change%20analysis%20that%20allows%20us%20to%20verify%20what%20is%20going%20to%20happen%20before%20pushing%20the%20changes%20to%20the%20production%20network.%20In%20this%20case%2C%20these%20links%20are%20going%20to%20be%20swapped.%3C/p%3E
  • Click Commit to commit the changes
  • Click on Dashboard
  • %3Cp%3EWe%20can%20see%20that%20all%20the%20anomalies%20are%20cleared%20and%20the%20network%20is%20operating%20in%20the%20intended%20state.%26nbsp%3B%3C/p%3E
  • Anomalies are cleared out

Anomalies are cleared out