User's Guide

Note
You may select multiple Communication Settings Profiles by checking more than one
checkbox. If more than one profile is selected, ADSP will attempt to find the best match to
apply starting at the top of the list and working its way down to the bottom of the list.
Click the Apply button to save your changes. Click the Reset button to discard your changes.
Import Communications Settings
You may import Communications settings for a device using one of the following methods:
• Manually via Menu > Import and Discovery(see Import and Discovery.)
• Through a schedule via Configuration > Appliance Platform > Import/Discover Devices (see
Import/Discover Devices to learn how to set up a schedule)
• 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
Legacy Content
Appliance Platform
Extreme AirDefense User Guide for version 10.5. 1063