Inventory manipulation

From the Fabric Inventory view, you can manage the nodes known to the system. You can modify the basic information about individual nodes, associate any planned nodes to real-world hardware, and manage items by importing and exporting information using a spreadsheet.

Each time you change the device associations for a specific node, the notifications menu indicates a Device Status Change update for each node that has been updated.

Editing node information

You can edit the serial number and description information of individual real nodes in the inventory. For Digital Sandbox nodes, you can only edit the description.

Follow this procedure to edit a node.

  1. Click to open the main menu, then select Inventory.
  2. From the Fabric Elements view, find the node that you want to update and double-click it.
  3. Enter a serial number or edit the existing serial number.
    To edit the serial number, double-click the Serial Number field. Optionally, you can edit the description.

    For real-world hardware and previously associated nodes, you can also edit the RackID.

  4. Click SAVE to save your changes.

Viewing the configuration file for a single node

You can view the configuration file that the system has generated for each node in the inventory. Viewing the configuration file can be helpful for verifying the precise configuration that is planned for the node and possibly revising the configuration if needed.

Follow this procedure to view the current configuration planned for a single node.

  1. Click to open the main menu, then select Inventory.
  2. Find the node and click at the end of its row.
  3. Select Inspect Configuration from the displayed actions list.
  4. Optional: Do any of the following:
    • To save the fabric configuration in a local file, click and choose a location and name for the file.
    • To copy a portion of the fabric configuration, select the portion and click . The selection is added to your clipboard.
    • To find a particular string of text within the fabric configuration, click and enter the text string. The first instance is highlighted; use the arrows to navigate forward or backward to additional instances, or click ALL to highlight all instances simultaneously.
  5. Click at the upper right of the overlay to close the Inspect Configuration overlay.

Planned node and real-world hardware association

When designing a fabric intent, you can incorporate planned nodes into the design. You can use the Inventory view to associate individual, pending nodes with their real-world counterparts. For 100% fabric intent deployment, the planned node should be associated with real-world hardware. However, each planned node does not need to be associated with real-world hardware to deploy the 0% fabric intent.

For SR Linux deployments, when you associate planned nodes and real-world hardware and generate a fabric intent containing those nodes, the system performs the association between the planned and real devices via the node discovery and ZTP processes. A configuration file is generated containing the association details.

For WBX deployments, there is no ZTP. The Fabric Services System supports only the overlay. After you create the fabric intent using the imported manual topology, you associate the management profiles with the WBX nodes and add the IP addresses, then wait for the WBX nodes to transition to the Ready state.

If you provide the management address and serial number first, and there is already a real device ZTP with the same serial number, but with a different management address, the inventory subsystem updates the association with the latest values according to the latest ZTP message.

Associating a planned node

Before you can associate a fabric's planned nodes with hardware:
  • you must have created and saved the fabric intent, and generated the fabric topology.
  • the inventory must include entries for the real-world nodes that correspond to the planned nodes in the fabric intent.
Follow this procedure to associate a planned node with its real-world counterpart. The system can only download the necessary configuration data to a node within the fabric intent after this association has been made.
The inventory can gain entries for nodes in two ways:
  • when the node hardware is installed, the system automatically discovers the hardware through the node discovery process
  • before the node hardware is available, you can pre-load the inventory with information about the anticipated hardware

This procedure describes how to manually associate each node with hardware, one node at a time. You can identify the hardware before it is installed and available or you can select from installed hardware.

Alternatively, you can also bulk-associate a series of nodes using a spreadsheet and then upload the spreadsheet to the Fabric Services System.

  1. Click to open the main menu, then select Fabric Elements.
  2. Find the node that you want to associate.
    If necessary, use the controls at the top of each column to filter the list.
  3. Click the Table row actions icon at the right edge of the row.
  4. Find the node that you want to associate, then click at the end of its row.
    If necessary, use the controls at the top of each column to filter the list.

    • To identify the expected hardware for the node before the hardware is available, go to Step 5.

    • To select from installed hardware, go to Step 6.

  5. Identify the expected hardware for the node before the hardware is available.
    Click Open from the displayed actions list. In the Update Inventory form, set the following parameters. When you are finished, click SAVE.
    • Serial Number - enter the serial number of the real hardware.
      • For SR Linux deployments, this value is required.

        If you provide only a management address for a real device and the ZTP process has completed, the inventory subsystem automatically associates the planned node and real-world hardware.

      • For WBX deployments, leave this field blank if you do not know the serial number
    • Management Address - required for WBX deployments
    • Rack ID - optional
    • Description - optional
  6. Select from installed hardware.
    Click Associate from the displayed actions list. In the Associate Real Device form, select one of the displayed devices, then click ASSOCIATE.
The system associates the planned nodes with the real-world hardware. In the UI, the status of the node is set to In Discovery. When the process completes, the status of the node is set to Ready.

Associating a planned node using a serial number

Follow this procedure to associate an individual planned node with its real-world counterpart using the Serial Number column. Use this simple method to quickly add a new serial number without opening a series of menus in the UI.

Alternatively, you can bulk-associate a series of nodes by uploading a spreadsheet that provides the association of inventory items.

  1. Open the inventory.
  2. Select a row corresponding to one of the planned nodes and do the following:
    1. Click in the Serial Number column for that row.
    2. Enter the serial number for the real-world node that corresponds to this planned node.
    3. Wait for the real-world node to adopt a Ready state.
    Before the association, the planned node and real-world hardware each appeared on individual rows in the inventory. After the association completes, the planned and real-world hardware combine on the same row, as they are now functional nodes in the fabric.

Disassociating planned nodes from real hardware

If a planned node is associated with a real-world hardware device, and you want to change this association to a different real-world device, you must remove the existing association. If the node is not currently deployed in a fabric intent, the Inventory allows you to perform the disassociation.

Alternatively, you can bulk-disassociate a series of nodes by uploading a spreadsheet that contains the relevant information.

You cannot disassociate a planned node from real-world hardware while the node is in the In Discovery state; the Disassociate action is disabled.

When creating a candidate fabric intent, you can disassociate a planned node from real-world hardware while the node is in the Ready state; however, the node loses all established end service bindings with the real hardware.

If the associated node is deployed as part of a fabric intent, but has not been successfully connected to real-world hardware (that is, the node has never been in the Ready state) you can disassociate it. If you want to replace a node that is part of the deployed fabric intent, you must perform a maintenance operation, that is, create a node replacement maintenance intent.

Follow this procedure to disassociate a planned node from real hardware.

  1. From the main menu Inventory view, locate the planned node and click at the right edge of its row.
    If necessary, use the controls at the top of each column to filter the list.
  2. Select Disassociate from the displayed actions list.
  3. Click OK.
    The system disassociates the planned and real nodes.

After you disassociate a real-world hardware device from a planned node, the real-world hardware item remains in the inventory. It can be re-associated with the planned node. However, if you would like to associate the real-world hardware device to a different planned node, you must update the real-world hardware device's configuration.

When a fabric intent is deployed, if any previous versions of that deployed intent included unassociated real-world hardware items, those hardware items are removed. When a fabric intent is deleted, any associated real-world hardware in that intent is removed from the inventory.

Changes to node associations

When you disassociate a successfully connected planned node from a real-world hardware device (that is, the node has been in the Ready state), you can only continue to use the planned node and hardware device if the hardware device is again reassociated with the same planned node. During the initial association, a configuration file is generated by the system containing configuration information, and the node is discovered by the initial ZTP process. This configuration is unique to the real-world hardware; you cannot associate the planned node with a different real-world hardware device because the certificates do not match. In this scenario, to change the node association, you must manually trigger the ZTP process for the real-world hardware in the management stack so that it receives a new configuration and updated software image. You can then perform a new association.

For example, you cannot change the association of a planned node from one real-world hardware device (leaf-1) to a secondary real-world hardware device (leaf-2). This is true even if the hardware devices (leaf-1 and leaf-2) are the same type (that is, both could be 7220 IXR-D3 chassis). Each node has a unique serial number and system name, which is specified in the configuration file. If you generated a certificate on a node for an initial association, then disassociate the node, and try to re-associate with a different node, the action fails as the certificate provided was intended for the original node.

This scenario is true if you use either the Fabric Services System DHCP server or an external DHCP server.

For WBX associations, you can change association at any time, except when it is In Discovery state.

Node associations in candidate fabric intents

If you create a new candidate version of a deployed fabric intent, you can configure new associations between planned nodes and real-world hardware that differ from the associations in the initial version. The system does not enforce any associations established in the initial version of the intent. Rather, in the candidate version, you can disassociate a previously successful connection between a deployed node and real hardware, resulting in loss of connection and services for the deployed nodes.

When creating a candidate fabric intent, the system assigns an incremented version number. Within the candidate version, you can revise the associations between planned nodes and real-world hardware.

Any revised node associations in the candidate version of the fabric intent appear in the dedicated fabric intent inventory and the overall inventory. When you associate a planned node, the association is versionless. For this reason, if you discard the candidate version of the intent, the node associations do not change.

Updating the system name of a node in a fabric inventory

You can update the system name of a single node in a fabric intent inventory. You can also bulk-update a series of nodes by modifying the system name mapping data for a specific fabric intent.

System names cannot be updated from the overall inventory. You must open a fabric intent and update the node's system name from the fabric intent inventory.

You cannot update the system name of a node if it is already associated with real-world hardware or is in the Deployed state.

Follow this procedure to update the system name of a node in a fabric inventory.

  1. Open the fabric intent inventory.
  2. For the node you want to update, at the right edge of the row, click to open the inventory menu.
  3. Select Update SysName from the displayed actions list.
  4. In the editable field, specify the new system name for the node.
  5. Click SAVE.

Viewing platform details for nodes in the inventory

In the Inventory view, you can view specific platform details about each node and the real-world hardware that it is associated with.

For deployed nodes, you can open the Platform Details form to display information about the chassis components, including fans, power supply units (PSUs), control processing modules (CPMs), and line cards. Specifically, you can view the operational state for each chassis component. When the system raises an alarm for any of these components, the platform details shows the precise inventory objects that are affected.

Follow this procedure to view specific platform details on a node in the inventory.

  1. Open the fabric intent inventory.
  2. For the node you want to view, at the right edge of the row, click to open the inventory menu.
  3. Select Show Platform from the displayed actions list.
    Note: The Show Platform action is only selectable if the planned node is associated with real hardware and the node is deployed in a fabric intent.
  4. Observe the details in the form. You can view the operational state for the component.
  5. Click either the CLOSE button or the at the top of the form to return to the list of nodes.
See Alarms for more information about how to create and define specific system alarms.

Inventory items in spreadsheet format

You can export the information from the inventory into a spreadsheet (.csv ) format. The spreadsheet lists either a complete or partial inventory of devices in the network, depending on the selections you make before you export. The exported fabric information shows a list of device names and the serial numbers associated with those devices. In a fabric intent inventory, you can also export a spreadsheet that lists the mapping of system names in the fabric.

The inventory can contain a combination of both actual equipment and pre-planned equipment that is not yet purchased or incorporated into the network.

A fabric inventory spreadsheet can be used when planning and implementing a network. It can be distributed to personnel who do not have access to Fabric Services System. For example, a spreadsheet can be used for device procurement, internal asset management, or can be distributed to data center contractors who perform physical cabling to build the network.

You can export fabric data from either the overall inventory of fabric items or the fabric intent inventory of a specific fabric intent.

Exporting an overall inventory spreadsheet

You can export a spreadsheet containing all of the information listed in the overall inventory of fabric items. The spreadsheet can be distributed to personnel who do not have access to the Fabric Services System UI.

Follow this procedure to export the overall inventory.

  1. Open the overall inventory.
  2. From the inventory, click the menu at the upper right of the page.
  3. Select Export, then CSV export from the resulting list.
  4. When the download completes, either open the CSV file or save it to your local system.
    The resulting spreadsheet displays all of the data shown on the Inventory screen.

Exporting association data from the overall inventory

In the overall inventory of fabric items, you can download an associate mapping file to export the details about the inventory items.

Follow this procedure to export multiple items from the overall inventory to a spreadsheet.

  1. Open the inventory.
  2. Select two or more rows by checking the box at left side of each row.
  3. Click the Download Associate Mapping File icon .
  4. When the download completes, either open the CSV file or save it to your local system.
    The resulting spreadsheet displays information about each inventory item you selected; for related information, see Spreadsheet information for associations and disassociations.

Exporting association data from a fabric intent inventory

In the inventory of a specific fabric intent, you can download an associate mapping file or a system name mapping file to export the details on the inventory items contained within the fabric intent.

Follow this procedure to export multiple items from the fabric intent inventory of a specific fabric intent to a spreadsheet.

  1. Open the inventory.
  2. Select two or more rows by checking the box at left side of each row.
  3. Click either the Download Associate Mapping File icon or Download SysName Mapping File icon .
  4. When the download completes, either open the .csv file or save it to your local system.
    The resulting spreadsheet displays information about the multiple selected items.

    If you downloaded the Associate Mapping File, the spreadsheet name column displays the name of the items and the serialNumber column displays the associated serial numbers (if associated). If you downloaded the SysName Mapping File, the spreadsheet name column displays the name of the nodes and the newSystemName column displays a blank field where you can add a new system name.

Uploads of inventory items

You can upload (import) information from a spreadsheet (CSV) format to the Fabric Services System. The spreadsheet contains information to complete the missing details of planned items in the inventory or update details on existing items. You can upload a spreadsheet of details related to one or more planned fabric items.

After you have exported an inventory spreadsheet and updated it with new information (such as serial numbers, management address, and management profiles to associate specific real-world hardware to each pending item in the inventory), you can import the spreadsheet back into the system to bulk-associate pending nodes with real-world counterparts. Import fabric data from either the overall inventory of fabric items or the fabric intent inventory of a specific intent.

You can also use a spreadsheet to disassociate inventory items from real-world hardware.

Spreadsheet information for associations and disassociations

  • Associations
    An entry for an association must include the following values:
    • name
    • serial number or IP address
    • management profile
  • Disassociations

    The trigger for a disassociation is the absence of a serial number and IP address; therefore, the entries for disassociation should not include a serial number and IP address. An entry for a disassociation should contain only a name and optionally, a management profile.

    If you provide a management profile, note that:
    • if management profile has not changed, you can disassociate it from the real hardware and keep the management profile the same.
    • If the management profile has changed, the planned node updates the new management profile.
    • If the management profile is not present, the planned node deletes the current management profile.

Uploading association data to the overall inventory

Follow this procedure to upload data about new inventory items installed on the network.
  1. Open the inventory.
  2. Click UPLOAD ASSOCIATE MAPPING FILE.
  3. Select the spreadsheet from your local system.
  4. In the selection window, click Open.

Uploading association data to the fabric intent inventory

Follow this procedure to upload data about new inventory items for a specific fabric intent.
  1. Open the fabric intent inventory.
  2. Click UPLOAD ASSOCIATE MAPPING FILE.
  3. Select the spreadsheet from your local system.
  4. In the selection window, click Open.

Modifying the system name of nodes in an existing fabric intent

If you need to change the system name of items in an existing fabric intent, you can download the System Name Mapping file, update the information, then upload the file to add the node names to the fabric intent. The System Name Mapping file allows you to bulk-update the nodes the inventory instead of updating each individually.

Follow this procedure to modify system name mapping data for a specific fabric intent.

  1. Open the fabric intent and download the System Name Mapping file (.csv) by following the procedure in Exporting association data from a fabric intent inventory.
  2. Open the downloaded file on your local system.
    The spreadsheet displays two columns. The name column displays the current names of the nodes and the newSystemName column displays a blank field where you can add the new system names.
  3. In the newSystemName column, enter a new name for each node you would like to change.
  4. Save the updated spreadsheet on your local system.
  5. Click UPLOAD SYSNAME MAPPING FILE and select the updated spreadsheet from your local system to upload the changes.
    The names of the nodes in the inventory are updated as specified in the spreadsheet. You can verify the changes immediately in the Fabric Inventory view.