1

%3Cp%3EThis%20is%20the%20main%20dashboard%20in%20the%20Apstra%20solution%2C%20notice%20there%20are%20no%20anomalies.%20For%20the%20purpose%20of%20this%20demo%2C%20let%20us%20perform%20some%20maintenance%20on%20a%20device.%3C/p%3E

%3Cp%3EThis%20is%20the%20main%20dashboard%20in%20the%20Apstra%20solution%2C%20notice%20there%20are%20no%20anomalies.%20For%20the%20purpose%20of%20this%20demo%2C%20let%20us%20perform%20some%20maintenance%20on%20a%20device.%3C/p%3E

%3Cp%3EThere%20are%20two%20Spine%20devices%2C%20and%20three%20racks.%20Two%20of%20the%20racks%20have%20redundant%20switches%20in%20them%2C%20and%20the%20third%20rack%20has%20a%20single%20switch%20in%20it.%20Let%20us%20perform%20maintenance%20on%20spine%20two.%3C/p%3E%0A%3Cp%3ETo%20begin%2C%20click%20on%20the%20staged%20tab.%3C/p%3E

%3Cp%3EThere%20are%20two%20Spine%20devices%2C%20and%20three%20racks.%20Two%20of%20the%20racks%20have%20redundant%20switches%20in%20them%2C%20and%20the%20third%20rack%20has%20a%20single%20switch%20in%20it.%20Let%20us%20perform%20maintenance%20on%20spine%20two.%3C/p%3E%0A%3Cp%3ETo%20begin%2C%20click%20on%20the%20staged%20tab.%3C/p%3E

Select Spine 2

%3Cp%3ENote%20that%20this%20is%20the%20normal%20operational%20state%20for%20this%20device.%3C/p%3E

%3Cp%3ENote%20that%20this%20is%20the%20normal%20operational%20state%20for%20this%20device.%3C/p%3E

Select the drain mode

Click on save icon to confirm the change

%3Cp%3EThe%20command%20is%20being%20queued%20into%20the%20uncommitted%20tab%20and%20ready%20to%20invoke%20this%20process.%3C/p%3E

%3Cp%3EThe%20command%20is%20being%20queued%20into%20the%20uncommitted%20tab%20and%20ready%20to%20invoke%20this%20process.%3C/p%3E

Commit the change

Let us confirm by pressing the commit button.

%3Cp%3EAbstract%20aids%20us%20in%20keeping%20accurate%20documentation%20by%20allowing%20us%20to%20label%20the%20maintenance%20events.%3C/p%3E

%3Cp%3EAbstract%20aids%20us%20in%20keeping%20accurate%20documentation%20by%20allowing%20us%20to%20label%20the%20maintenance%20events.%3C/p%3E

Click on Acitve tab

The commit process results in route map adjustments that removes the device as a path and the routing table of all the other devices.

Notice the anomalies

As this proceeds, the telemetry table begins to show the effects that are resulting from the mode change. BGP peering sessions to Spine to have dropped, and changes in the route tables of the other devices are being indicated. Spine two is shown as being in the Drain mode. The red anomalies are showing the expected changes and will soon clear as the fabric adjusts to the new state where spine two has been gracefully isolated and all traffic is traversing the other devices in the fabric.

%3Cp%3EAn%20IBA%20probe%20closely%20watches%20the%20interface%20utilization%20on%20during%20devices.%20This%20provides%20visibility%20into%20the%20point%20in%20time%20when%20implied%20traffic%20has%20completed%20its%20journey.%3C/p%3E

%3Cp%3EAn%20IBA%20probe%20closely%20watches%20the%20interface%20utilization%20on%20during%20devices.%20This%20provides%20visibility%20into%20the%20point%20in%20time%20when%20implied%20traffic%20has%20completed%20its%20journey.%3C/p%3E

Choose the Drain status from the drop down menu

Choose%20the%20Drain%20status%20from%20the%20drop%20down%20menu

Click on Analytics

Click on Anomalies

Once the traffic level on Spine drops below a customizable threshold, the probe anomaly clears and indicates the spine two is ready to be serviced. This typically takes a few moments, depending on the level of utilization at the time the process is initiated.

Click on Dashboard

Click on active

Notice Spine 2 is in drain mode

Moving into the Active tab shows that spine two remains in this state, and we can now perform the required maintenance procedure on this switch

Clikc on selection

Now that maintenance is complete, spine two can be returned to operation. The system will return the route maps to their original state, and spine two's capacity will be returned to the fabric. Now we reverse the process we performed earlier, and we return spine two to the deployed state. 

Click to change the mode

Change the mode to Deploy

Click to save the selection

Click on the uncommited tab

As earlier, the instructions for this device are queued. This is reviewed in the uncommitted tab. Pressing commit begins the process of bringing Spine two back into the fabric.

26

Pressing commit begins the process of bringing Spine two back into the fabric.

Commit changes

Let us check the active tab

All the devices are back in the deploy mode

Thank you