Skip to main content
Cisco SD-WAN
Support
Product Documentation
Viptela Documentation

WiFi Radio

Use the WiFi Radio template for all vEdge router devices that support wireless LANs (WLANs), including the vEdge 100wm router.

To configure WLAN radio parameters using vManage templates:

  1. Create a WiFi Radio template to configure WLAN radio parameters, as described in this article.
  2. Create a Wifi SSID template to configure an SSID and related parameters. See the WiFi SSID help topic.

Navigate to the Template Screen

  1. In vManage NMS, select the Configuration ► Templates screen.
  2. In the Device tab, click Create Template.
  3. From the Create Template drop-down, select From Feature Template.
  4. From the Device Model drop-down, select the vEdge router model that supports wireless LANs (WLANs).
  5. Click the WLAN tab located directly beneath the Description field, or scroll to the WLAN section.
  6. From the WiFi Radio drop-down, click Create Template. The WiFi Radio template form is displayed. The top of the form contains fields for naming the template, and the bottom contains fields for defining WiFi Radio parameters.

When you first open a feature template, for each parameter that has a default value, the scope is set to Default (indicated by a check mark), and the default setting or value is shown. To change the default or to enter a value, click the scope drop-down to the left of the parameter field and select one of the following:

Parameter Scope

Scope Description

Device Specific (indicated by a host icon)

Use a device-specific value for the parameter. For device-specific parameters, you cannot enter a value in the feature template. You enter the value when you attach a Viptela device to a device template.

When you click Device Specific, the Enter Key box opens. This box displays a key, which is a unique string that identifies the parameter in a CSV file that you create. This file is an Excel spreadsheet that contains one column for each key. The header row contains the key names (one key per column), and each row after that corresponds to a device and defines the values of the keys for that device. You upload the CSV file when you attach a Viptela device to a device template. For more information, see Create a Template Variables Spreadsheet.

To change the default key, type a new string and move the cursor out of the Enter Key box.

Examples of device-specific parameters are system IP address, hostname, GPS location, and site ID.

Global (indicated by a globe icon)

Enter a value for the parameter, and apply that value to all devices.

Examples of parameters that you might apply globally to a group of devices are DNS server, syslog server, and interface MTUs.

WLAN Radio Frequency Configuration

The following parameters are required (unless otherwise indicated) to configure WLAN radio parameters on a vEdge router:

Step Parameter Field Procedure
 1. Template Name Enter a name for the template. It can be up to 128 characters and can contain only alphanumeric characters.
 2. Description (Template) Enter a description for the template. It can be up to 2048 characters and can contain only alphanumeric characters.
 3. Select Radio Select the radio band. It can be 2.4 GHz or 5 GHz.
 4. Country

Select the country where the router is installed.

 5. Channel Bandwidth (optional)

Select the IEEE 802.11n and 802.11ac channel bandwidth. For a 5-GHz radio band, the default value is 80 MHz, and for 2.4 GHz, the default is 20 MHz.

 6. Channel (optional)

Select the radio channel. The default is "auto", which automatically selects the best channel. For 5-GHz radio bands, you can configure dynamic frequency selection (DFS) channels.

 7. Guard Interval (optional) Select the guard interval. For a 5-GHz radio band, the default value is the short guard interval (SGI) of 400 ns, and for 2.4 GHz, the default is 800 ns.
 8. Save Click Save to save the feature template.

CLI equivalent:

wlan frequency
  channel channel
  channel-bandwidth megahertz
  country country
  guard-interval nanoseconds

Release Information

Introduced in vManage NMS Release 16.3.

  • Was this article helpful?