Brocade Network Advisor IP User Manual v12.3.0 - Manual (Page 965)

Brocade Network Advisor IP User Manual 913
53-1003153-01
Importing parameter values into a configuration
26
2. Enter the user name for the product in the Product Login Account - Username field.
NOTE
If Telnet is used to log in to the device and Telnet only requires a password, then enter the
password in the Password field and leave the Username field blank.
3. Enter the password for the product in the Product Login Account - Password field.
4. (IronWare only) Enter the user name assigned to management privilege levels on the device in
the Product Enable Account - Username field.
NOTE
If a device only requires the enable password, then enter the password in the Password field
and leave the Username field blank.
5. (IronWare only) Enter the password assigned to management privilege levels on the device in
the Product Enable Account - Password field.
6. Click OK on the CLI Template dialog box
Importing parameter values into a configuration
You can define the parameter values in a comma-separated value file (CSV) and then import them
into the CLI template. The CSV file can include a description of the CLI template. The description
must start with a pound sign (#) and cannot be longer than 512 characters.
The first line after the description defines the header for the import. The first entry in the header
must be “Target”, then list all parameters (defined on the CLI Commands tab) to be included in the
import.
The target can be an IP address (IPv4 or IPv6 format), the product group name (such as San Jose
products), or All (all products). The parameters can be included in any order. The application
ignores empty rows or columns during import.
NOTE
All values are case sensitive (including the “Target” header).
For example, if you define the following commands on the CLI Commands tab, Table 88 shows the
CSV file content required for using different values for each target and Table 89 shows the CSV file
content required for using the same values for each target
! Required for LSP egress address in LSP Manager as well as a soft interface for
IP routing
interface loopback $<LOOPBACK_INTERFACE|INTEGER>
enable
ip ospf area $<OSPF_AREA|INTEGER>
ip address $<LOOPBACK_INTERFACE_IP|STRING>