Reference Guide

12 | Introduction Dell PowerConnect W-Series ArubaOS 6.1 CLI | Reference Guide
you automatically. If the abbreviation is too vague (too few characters), the cursor does not advance and you must
type more characters or use the help feature to list the matching commands.
Deleting Configuration Settings
Use the no command to delete or negate previously-entered configurations or parameters.
 To view a list of no commands, type no at the enable or config prompt followed by the question mark. For
example:
(host) (config) # no?
 To delete a configuration, use the no form of a configuration command. For example, the following command
removes a configured user role:
(host) (config) # no user-role <name>
 To negate a specific configured parameter, use the no parameter within the command. For example, the
following commands delete the DSCP priority map for a priority map configuration:
(host) (config) # priority-map <name>
(host) (config-priority-map) # no dscp priority high
Saving Configuration Changes
Each Dell controller contains two different types of configuration images.
 The running config holds the current controller configuration, including all pending changes which have yet to
be saved. To view the running-config, use the following command:
(host) # show running-config
 The startup config holds the configuration which is used the next time the controller is rebooted. It contains
all the options last saved using the write memory command. To view the startup-config, use the following
command:
(host) # show startup-config
When you make configuration changes via the CLI, those changes affect the current running configuration only.
If the changes are not saved, they are lost after the controller reboots. To save your configuration changes so they
are retained in the startup configuration after the controller reboots, use the following command in enable mode:
(host) # write memory
Saving Configuration...
Saved Configuration
Both the startup and running configurations can also be saved to a file or sent to a TFTP server for backup or
transfer to another system.
Commands That Reset the Controller or AP
If you use the CLI to modify a currently provisioned and running radio profile, those changes take place
immediately; you do not reboot the controller or the AP for the changes to affect the current running
configuration. Certain commands, however, automatically force the controller or AP to reboot. You may want to
consider current network loads and conditions before issuing these commands, as they may cause a momentary
disruption in service as the unit resets. Note also that changing the lms-ip parameter in an AP system profile
associated with an AP group causes all APs in that AP group to reboot.