Inventory manipulation
From the Inventory, 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
Follow this procedure to edit a node.
- Open the inventory by following one of the procedures in Viewing the overall inventory.
-
At the right edge of the row, click
to open the inventory menu.
- Select Open from the displayed action list.
-
Either 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.
- Click SAVE to save your changes.
Viewing the configuration file for a single node
Follow this procedure to view the current configuration planned for a single node.
- Open the inventory to see the complete list of nodes.
-
Find the row for the node in question. At the right
edge of the row, click
to open the inventory menu.
- Select Inspect Configuration from the displayed actions list.
-
Optionally, 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.
- To save the fabric configuration in a local file,
click
-
Click the
at the upper right of the overlay to return to the list of nodes.
Associating individual planned nodes with real-world hardware
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.
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 process. A configuration file is generated containing the association details (see Node discovery).
Associate a planned node
Alternatively, you can bulk-associate a series of nodes using a spreadsheet. See Uploading data about a series of inventory items.
- Open the inventory by following one of the procedures in Viewing the overall inventory.
-
Find the row for the planned node in question. At the right edge of
the row, click
to open the inventory menu.
If necessary, use the controls at the top of each column to filter the list as described in Lists. -
Do one of the following:
- Select Open from the displayed actions list. In the Update Inventory dialog, update the Serial Number field with the serial number of the real hardware item, then click SAVE.
- Select Associate from the displayed actions list. In the Associate Real Device dialog, 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, then when the process completes, the status of the node is set to Ready.
Associate using the Serial Number column
Alternatively, you can bulk-associate a series of nodes using a spreadsheet. See Uploading data about a series of inventory items.
- Open the inventory by following one of the procedures in Viewing the overall inventory.
-
Select a row corresponding to one of the planned nodes and do the
following:
- Click in the Serial Number column for that row.
- Enter the serial number for the real-world node that corresponds to this planned node.
- 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
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. See Maintenance intents for details on creating a node replacement maintenance intent.
Follow this procedure to disassociate a planned node from real hardware.
- Open the inventory by following one of the procedures in Viewing the overall inventory.
-
Find the row for the planned node in question. At the right edge of the
row, click
to open the inventory menu.
If necessary, use the controls at the top of each column to filter the list as described in Lists. - Select Disassociate from the displayed actions list.
-
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, as described in Associating individual planned nodes with real-world hardware. 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; see Changing node associations.
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.
Changing 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 to 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 will 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, if you would like to change the association of a planned node from one real-world hardware device (leaf-1), to a secondary real-world hardware device (leaf-2), you will be unsuccessful trying to complete this in the system's UI. 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 will fail 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.
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; see Creating a new version of a fabric intent. Within the candidate version, you can revise the associations as described in Associating individual planned nodes with real-world hardware and Disassociating planned nodes from real 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
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.
- Open the fabric intent inventory as described in Viewing the overall inventory.
-
For the node you want to update, at the right edge of the row, click
to open the inventory menu.
- Select Update SysName from the displayed actions list.
- In the editable field, specify the new system name for the node.
- Click SAVE.
Viewing platform details for nodes in the inventory
For deployed nodes, you can open the Platform Details dialog to display information about the chassis components, including fans, power supply units (PSUs), control processing modules (CPMs), and linecards. Specifically, you can view the operational state for each chassis component, and view if there are any current temperature alarms for that 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.
- Open the fabric intent inventory as described in Viewing the overall inventory.
-
For the node you want to view, at the right edge of the row, click
to open the inventory menu.
-
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.
- Observe the details in the dialog. You can view the operational state and if there are any current temperature alarms for the component.
-
Click either the CLOSE button or the
at the top of the dialog to return to the list of nodes.
Exporting data about inventory items
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 that 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 DC contractors that 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
Follow this procedure to export the overall inventory.
- Open the overall inventory by following the procedure in Viewing the overall inventory.
-
From the inventory, click the
menu at the upper right of the page.
- Select Export, then CSV export from the resulting list.
-
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
Follow this procedure to export multiple items from the overall inventory to a spreadsheet.
- Open the inventory by following the procedure in Viewing the overall inventory.
- Select two or more rows by checking the box at left side of each row.
-
Click the Download Associate Mapping File
icon
.
-
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. The name column displays the name of the item and the serialNumber column displays the associated serial number (if associated).
Exporting association data from a fabric intent inventory
Follow this procedure to export multiple items from the fabric intent inventory of a specific fabric intent to a spreadsheet.
- Open the inventory by following one of the procedures in Viewing the overall inventory.
- Select two or more rows by checking the box at left side of each row.
-
Click either the Download Associate Mapping File icon
or Download SysName Mapping File icon
.
-
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.
Uploading data about a series 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 (see either Exporting association data from the overall inventory or Exporting association data from a fabric intent inventory procedures) and updated it with new information (such as serial numbers 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.
Uploading association data to the overall inventory
- Open the inventory by following the procedure in Viewing the overall inventory.
- Click UPLOAD ASSOCIATE MAPPING FILE.
- Select the spreadsheet from your local system.
- In the selection window, click Open.
Uploading association data to the fabric intent inventory
- Open the fabric intent inventory by following the procedure in Viewing the overall inventory.
- Click UPLOAD ASSOCIATE MAPPING FILE.
- Select the spreadsheet from your local system.
- In the selection window, click Open.
Modifying the system name of nodes in an existing fabric intent
Follow this procedure to modify system name mapping data for a specific fabric intent.
- 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.
-
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.
- In the newSystemName column, enter a new name for each node you would like to change.
- Save the updated spreadsheet on your local system.
- 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.