Adding a device


This topic provides instructions on manually defining a new device for asset and configuration management by The referenced document [xwiki:Automation-DevSecOps.Network-Automation.TrueSight-Network-Automation.tsna251.TrueSight Network Automation 25\.1._Inclusion-Library._Common-terminology.WebHome] was not found..

After you add a new device, The referenced document [xwiki:Automation-DevSecOps.Network-Automation.TrueSight-Network-Automation.tsna251.TrueSight Network Automation 25\.1._Inclusion-Library._Common-terminology.WebHome] was not found. automatically performs a snapshot span action for this new device. The initial Running and Startup configurations are marked as Trusted.

Scalability Note

Large numbers of devices can be imported manually or on a scheduled basis from a variety of formats, including standards such as CSV seed file, WhatsUp Professional, Entuity Network Analytics, CiscoWorks XML and HP Network Node Manager. See Managing-device-import-tasks. Mass edits can be performed to modify values across multiple devices simultaneously. See Editing-devices.

On the Network > Spans > Devices page, do the following:

  1. Click the Add menu option above the list of devices to open the Add Device page.
     Alternatively, if you want to define a new device by duplicating an existing device and editing its attributes, click Copy Icon_Copy.png next to the required device.
     To find a device with the appropriate attributes, you can click its name and display a summary of the device's attributes.
    1. On the Details tab, enter the following information to define device attributes:

      Note

      If you are creating a quick start configuration, only enter information for the required fields. The required fields are indicated with a red asterisk (*) .

      The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.

  2. Under User Assigned Dynamic Fields, enter values based on the fields defined by the administrator through Admin > System Admin > Dynamic Fields.
    Only those dynamic fields that are applicable to the selected Device Type are available under User Assigned Dynamic Fields. For example, if you select Cisco Nexus as the Device Type, only those dynamic fields that are applicable to the Cisco Nexus device type are visible.
  3. Define the primary interface:

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.

  4. If the device can be reached through an alternate path, select the Auxiliary Interface option.

     For example, a device might normally be managed over the management LAN; but, for emergencies, its console port might also be physically cabled to a terminal server. You could also use the auxiliary interface to connect via a backup device agent, or to use a backup device security profile (such as a factory-default user account).

    Most day-to-day span actions uses the main or primary interface, but you can choose to use the auxiliary interface for any action that connects to the device.
  5. If you selected the Auxiliary Interface option, define parameters for the secondary path:

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.

  6. On the Groups tab, select static groups from the available groups (that are defined in the database) to associate with the device.

    Note

    A device cannot be added or removed from an auto group, as this is performed by The referenced document [xwiki:Automation-DevSecOps.Network-Automation.TrueSight-Network-Automation.tsna251.TrueSight Network Automation 25\.1._Inclusion-Library._Common-terminology.WebHome] was not found. based on the device's attributes (for example Model or Location).

  7. Click Save to add the new device to the database.

Related topic

Device-agent-architecture

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*