Custom CLI Example

This example shows how to use custom CLI variables.

Note

Customization of device values from ADSP requires expert knowledge of what each configuration parameter does and how making changes to those values will affect the device being modified.

The following conditions are assumed:

• A non-default CISCO VLAN configuration is used.
• A Cisco 1230 AP is managed and connected to a licensed ADSP server and the user accessing the configuration has all required permissions. It also implies that the user has a good working understanding of how device configuration is achieved in ADSP.
• VLAN configuration for a Cisco 1230 CLI profile can be modified using a variable defined by the user. ADSP provides for this action through custom variable notation for use inside a CLI profile. The variable notation is in the format that follows: $[variablename].

The following steps lead you through the basic steps required:

1. First you must create a custom variable and use it in a CLI profile. For this example, define the variable $[CustomVLAN].
2. By inserting this variable into a CLI profile, you are able to match the non-default setting in the WLAN Profile.

   

   

3. The following screen shot shows how it is used:
   1. The variable $[CustomVLAN] is inserted directly into the CLI profile that is applied to a device.
   2. When $[CustomVLAN] is first entered into the profile, it becomes available for use in the Variables section as CustomVLAN. This is where you enter the custom VLAN value.

   

   

4. To complete this VLAN customization example for the Cisco 1230 AP, the following modifications need to be made:
   1. interface Dot11Radio0.$[CustomVLAN]
   2. encapsulation dot1Q $[CustomVLAN] native
   3. interface Dot11Radio1.$[CustomVLAN]
   4. encapsulation dot1Q $[CustomVLAN] native
   5. interface FastEthernet0.$[CustomVLAN]
   6. encapsulation dot1Q $[CustomVLAN] native
5. When you apply the values in the custom CLI configuration, they are applied to the configured device.

   

   

6. As with all customizations, you should test it in a lab environment before putting it into production.