Use the no command to delete or negate previously-entered configurations or parameters. You can exit a sub-command mode and return to the basic configuration mode or the privileged Exec (enable) mode at any time by executing the exit or end command. When you are in a configuration sub-mode, the command prompt changes to indicate the current sub-mode. Some commands in configuration mode allow you to enter into a sub-mode to configure the commands specific to that mode. Instant Access Point# commit apply Configuration Sub-modes (Instant Access Point)(RF dot11a Radio Profile)# end (Instant Access Point)(RF dot11a Radio Profile)# spectrum-monitor (Instant Access Point)(RF dot11a Radio Profile)# csa-count 2 (Instant Access Point)(RF dot11a Radio Profile)# interference-immunity 3 (Instant Access Point)(RF dot11a Radio Profile)# dot11h (Instant Access Point)(RF dot11a Radio Profile)# no legacy-mode (Instant Access Point)(RF dot11a Radio Profile)# beacon-interval 200 (Instant Access Point)(config)# rf dot11a-radio-profile (Instant Access Point)# commit revert Example: To revert to the earlier configuration, use the following command in the privileged mode.
(Instant Access Point)# show uncommitted-config To view the changes that are yet to be applied, use the following command in the privileged mode: (Instant Access Point)# commit apply no-save To apply the configuration changes to the cluster, without saving the configuration, use the following command in the privileged mode: To apply and save the configuration changes at regular intervals, use the following command in the privileged mode: The CLI does not support the configuration data exceeding the 4K buffer size in a CLI session: therefore, Aruba recommends that you configure fewer changes at a time and apply the changes at regular intervals. The changes configured in a CLI session are saved in the CLI context.
#Sh putty download update#
When you make configuration changes on a master IAP in the CLI, all associated IAPs in the cluster inherit these changes and subsequently update their configurations. You can use the question mark (?) to view the commands available in a privileged mode, configuration mode, or sub-mode.Īlthough automatic completion is supported for some commands such as configure terminal, the complete exit and end commands must be entered at command prompt for successful execution.Įach command processed by the Virtual Controller is applied on all the slave IAPs in a cluster. The Instant CLI allows CLI scripting in several other sub-command modes to allow the users to configure individual interfaces, SSIDs, access rules, and security settings. The configure terminal command allows you to enter the basic configuration mode and the command prompt is displayed as follows: (Instant Access Point)# configure terminal To move from privileged mode to the configuration mode, enter the following command at the command prompt: The configuration commands are available in the configuration (config) mode. The privileged mode provides access to show, clear, ping, traceroute, and commit commands. If the login is successful, the privileged command mode is enabled and a command prompt is displayed. Use the administrator credentials to start a CLI session. On connecting to a CLI session, the system displays its host name followed by the login prompt. Select Enabled from the Terminal access drop-down list. To enable the SSH access to the Instant CLI: 1.įrom the Instant UI, navigate to System > Show advanced options. You can access the Instant CLI through a Secure Shell (SSH). Instant supports the use of Command Line Interface (CLI) for scripting purposes. You are here: Connecting to a CLI Session
0 kommentar(er)
