User's Guide

• Through your appliance CLI with the import command (see Import/Discover Devices for command
syntax).
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 dierent 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:
• comm_settings - used to import a named Communication Settings Profile into the ADSP system.
• comm_settings_loc - used to apply previously-imported Communication Settings Profiles to a
level in the ADSP (either a folder or specific device).
The fields for the comm_settings record are:
• Import type (must be comm_settings)
• Profile name
• SNMP version (1, 2, or 3)
• SNMP read community
• SNMP write community
• SNMPv3 username
• SNMPv3 authentication passphrase
• SNMPv3 privacy passphrase
• SNMPv3 authentication algorithm (None, MD5, or SHA)
• SNMPv3 privacy algorithm (3DES, DES, AES128, AES192, AES256,or None)
• SNMP port
• SNMP timeout (in milliseconds)
• SNMP number of retries
• Console user
• Console password
• Console enable password
• Console protocol (SSH or Telnet)
• Console port
• HTTP user
• HTTP password
• HTTP protocol (HTTP or HTTPS)
• HTTP port
Communication Settings
Profile Configuration Tab
526 Extreme AirDefense User Guide for version 10.5.