Maintainance mode

Embed Code

Small

Medium

Large

Extra Large

HTML embed code (iframe)

Steps

This is the main dashboard in the Apstra solution, notice there are no anomalies. For the purpose of this demo, let us perform some maintenance on a device.
There are two Spine devices, and three racks. Two of the racks have redundant switches in them, and the third rack has a single switch in it. Let us perform maintenance on spine two. To begin, click on the staged tab.
Select Spine 2
Note that this is the normal operational state for this device.
Select the drain mode
Click on save icon to confirm the change
The command is being queued into the uncommitted tab and ready to invoke this process.
Commit the change
Abstract aids us in keeping accurate documentation by allowing us to label the maintenance events.
The commit process results in route map adjustments that removes the device as a path and the routing table of all the other devices.
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.
An IBA probe closely watches the interface utilization on during devices. This provides visibility into the point in time when implied traffic has completed its journey.
Choose the Drain status from the drop down menu
Click on Analytics
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
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
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
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
Commit changes
Let us check the active tab
All the devices are back in the deploy mode
A quick review of our top-level dashboard shows that all indications are green, and drain config is not present on any devices.

0/3

There are a few loopholes and inconsistencies (for example {spoiler alert}: how the actual f@#k does the clan keep 3 giant ancient anacondas fed and alive ffs??) in conjunction with a few sub-par performances, but, overall its a pleasant spinoff and accompaniment to the other 2 films in the franchise, and does so with considerably less focus on firearms and more on the action one might expect to see from a strong culturally Japanese standpoint.

1

This is the main dashboard in the Apstra solution, notice there are no anomalies. For the purpose of this demo, let us perform some maintenance on a device.

There are two Spine devices, and three racks. Two of the racks have redundant switches in them, and the third rack has a single switch in it. Let us perform maintenance on spine two.

To begin, click on the staged tab.

Select Spine 2

Note that this is the normal operational state for this device.

Select the drain mode

Click on save icon to confirm the change

The command is being queued into the uncommitted tab and ready to invoke this process.

Let us confirm by pressing the commit button.

Abstract aids us in keeping accurate documentation by allowing us to label the maintenance events.

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

An IBA probe closely watches the interface utilization on during devices. This provides visibility into the point in time when implied traffic has completed its journey.

Choose the Drain status from the drop down menu

Click on Analytics

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

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

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

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.

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

A quick review of our top-level dashboard shows that all indications are green, and drain config is not present on any devices.

1