Import Communications Settings

Examples:

You may import Communications settings for a device using one of the following methods:

Importing communications settings require a separate import file. You should not combine importing communications settings with importing devices. Also, when importing communications settings for a device, the device must be imported into ADSP first.

Comma delimited files are used to import communications settings. There are different ways to create a comma delimited file but the most trouble-free way is to use a text editor, such as Notepad.

The import file is used to populate the fields in the four communication settings tabs. You can populate as many of the fields as you like. The import file fields required the same values as the communication settings in the three tabs.

There are two records associated with communications settings:

The fields for the comm_settings record are:

comm_settings,ProfileName,3,public,private,snmpV3user,snmpV3authpassphr,snmpV3privpassphr,MD5,
3DES,161,300,4,Cisco,Cisco,Cisco,SSH,22,admin,adminpassword,https,443
Note

Note

Although the above example is shown on multiple lines, all entries must be on a single line with no line breaks or carriage returns.

The fields for the comm_settings_loc record are:

Once the communication settings are imported, they will override any inherited settings. To see the new communication settings, go to the device's properties and select Communication Settings.

comm_settings_loc,ProfileName,00:23:04:5e:d3:00,ap
comm_settings_loc,ProfileName,/US/Southeast/AirDefense,folder3
Note

Note

For communications settings applied to a folder, the final field (device type) must be folder.