Nautobot - Update Device

Nautobot - Update Device updates an existing device in Nautobot with:

• Assets returned by the selected query or assets selected on the relevant asset page.

Required Fields

These fields must be configured to run the Enforcement Action.

• Use stored credentials from the Nautobot adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.

  • When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.

    📘

    Note

    To use this option, you must successfully configure a Nautobot adapter connection.

• Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

Additional Fields

These fields are optional. You can update any of the following device properties:

• Device Name - The new name for the device.

• Device Type (UUID) - The UUID of the device type to assign to the device.

• Role (UUID) - The UUID of the device role to assign (for example, Router, Switch).

• Location (UUID) - The UUID of the location to assign to the device. Nautobot 2.x replaced "site" with "location".

• Status - The operational status of the device. Valid values depend on your Nautobot installation (for example, active, planned).

Connection Settings

⚠️

Connection and Credentials

When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

• Host Name or IP Address - The base domain for the Nautobot API. Should contain a prefix of http:// or https://. Do not add any specific endpoints after the domain. Example: https://nautobot.example.com/
• Token - The Nautobot API authentication token. This token must have permission to update devices via the REST API.

• Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

• HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

• HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.

• HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

• Gateway Name - Select the Gateway through which to connect to perform the action.

APIs

Axonius uses the Nautobot REST API - PATCH /api/dcim/devices/{uuid}/

Required Ports

Axonius must be able to communicate via the following ports:

• TCP port 80/443

Required Permissions

• A valid Nautobot REST API token must be configured with write permissions to the /api/dcim/devices/ endpoint.
• The API token must have access to read device types, device roles, and locations to validate UUIDs.
• The token user role must have permission to update devices in Nautobot.

Version Matrix

This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.