Use the following steps to manually define a new device for asset and configuration management by BMC Network Automation.
After you add a new device, BMC Network Automation automatically performs a snapshot span action for this new device. The initial Running and Startup configurations are marked as Trusted.
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 EYE, 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 Details tab, define device attributes through the displayed fields:
If you are creating a quick start configuration, only enter information for the required fields. The required fields are indicated with a red asterisk (*) .
Specify a unique name for the device. Up to 100 characters in length.
Select the realm to which this device belongs. This field is available when the administrator has created two or more realms.
Select the device type based on the vendor. For example, for a Cisco IOS router, you would select Cisco and Cisco IOS Switch/Router.
Select the device category, defining the general type of equipment.
(Optional) Select the manager for this device. To browse for the manager, click thebutton. This field is displayed only when the device type supports a manager. For example, a Cisco Nexus device that represents a VSG firewall can declare a VNMC device to act as its manager. When this is the case, Deploy to Active operations performed on the VSG worker device actually result in the template in question being pushed out to the VNMC manager device. The template must therefore contain understood by the VNMC, not Nexus commands. The VNMC automatically propagates the changes from those commands down to the VSG it controls. BMC Network Automation performs a trailing snapshot of the worker device afterwards if possible, however in the case of the VSG it does not because you cannot predict exactly how long it will take the VNMC to flush changes to it. Instead the VSG must be configured to send syslog messages back to BMC Network Automation to trigger the trailing snapshot.
(Optional) Places a device in online or offline mode. When a device is offline, the following operations are suspended:
Remote Image File Server
(Optional) Specify which remote file server stores OS image files for this device, if you want to copy OS image files from a service located physically closer to this device on your network. This field is displayed only when you have remote file servers defined under Admin > Remote File Servers.
(Required for firewalls and load balancers) Specifies the security context information for your device. Choose from the following options:
Note: If you select User-Defined, you must identify your security context in the Name field that is displayed below this field.
The following Virtual Data Center (VDC) fields on the Details tab are read-only. They are populated only when VDC is enabled, the Device Category field is set to Load Balancer, Content Cache, Switch, or Firewall, and the device is associated with a pod and is part of a container. Their values come from the number of virtual devices or containers configured on the device.
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 Switch as the Device Type, only those dynamic fields that are applicable to the Cisco Nexus Switch device type are visible.
Define the primary interface through the following fields:
Host Name/IP Address/URL
Specify the host name, IPv4 or IPv6 address, or URL of the device's primary interface. When the access mode is web service, this field must contain the URL for accessing the host or server that is providing the web services interface. For a VMware vSwitch, the URL must be in one of the following formats:
For a device that is accessed via its serial console port connected to a terminal server, include the port number and terminal server host name or IP address in this field, using the following format:
Select the device agent that manages this device. If you do not have any remotely installed Device Agents, select Local (default).
Protocol used by the device agent to log on to the device. SSH2 refers to secure shell protocols. When Auto is selected, the device agent tries all supported modes (for example, SSH2, Telnet) for the device starting with the most secure. It also remembers the successful access setting for subsequent device interaction.
When Access Mode is set to an option other than Auto, the Port option becomes available. You can enter the TCP port number for connecting to the device. If this field is blank, BMC Network Automation uses the default well-known port associated with the access mode (22 for SSH, 23 for Telnet, 80 for HTTP, and 443 for HTTPS).
File Transfer Mode
Protocol used by the device agent to transfer configuration files and OS images to or from the device. When Auto is selected, the device agent tries all supported modes for the device starting with the most secure, and then remembers the successful transfer setting for subsequent device interaction. Examples of supported protocols are Session Control Protocol (SCP), File Transfer Protocol (FTP), Trivial File Transfer Protocol (TFTP), and Tunneled protocol.
Device Security Profile
Specify the device security profile (DSP) used for device login. For example, IOS-account.
(Optional) This parameter is applicable when network address translation (NAT) is used by devices to access the device agent by using TFTP/FTP/SCP to transfer configuration and OS image files.
If you selected the Auxiliary Interface option, define parameters for the secondary path:
Host Name/IP Address/URL
Specify the host name, IPv4 or IPv6 address, or URL of the device's secondary interface.
Select the device agent that can reach the device over the alternate path.
Select the protocol used by the device agent to log on to the alternate host name or IP address.
When Access Mode is set to an option other than Auto, the Port option becomes available. You can enter the TCP port number to use to connect to the device.
File Transfer Mode
Select the protocol used by the device agent to transfer files over the alternate path. Devices that are intended as Pod hosts should use file transfer mode instead of tunneled mode. File transfer mode is faster for firewall updates.
Device Security Profile
Specify the login credentials for the alternate path.
(Optional) Specify any agent IP address necessary to route back to it over the alternate path.
On the Groups tab, select static groups to associate with the device by moving groups from the list of available groups (that is, groups defined in the database) to the list of selected groups.
A device cannot be added or removed from an auto group, as this is performed by BMC Network Automation based on the device's attributes (for example Model or Location).