no

Device Config Commands

Negates a command or resets values to their default

Supported in the following platforms:

Syntax

no [adopter-auto-provisioning-policy-lookup|adoption-site|alias|application-policy|area|arp|auto-learn-staging-config|autoinstall|bridge|captive-portal| cdp|channel-list|cluster|configuration-persistence|contact|controller| country-code|critical-resource|crypto|database-backup|device-upgrade|dot1x| dpi|dscp-mapping|email-notification|environmental-sensor|events|export| file-sync|floor|geo-coordinates|gre|hostname|http-analyze|interface|ip|ipv6| l2tpv3|l3-lite-table|lacp|layout-coordinates|led|led-timeout| legacy-auto-downgrade|legacy-auto-update|license|lldp|load-balancing|location| logging|mac-address-table|mac-auth|mac-name|management-server|memory-profile| meshpoint-device|meshpoint-monitor-interval|min-misconfiguration-recovery-time| mint|mirror|misconfiguration-recovery-time|mpact-server|noc|nsight||ntp| offline-duration|override-wlan|power-config|preferred-controller-group| preferred-tunnel-controller|radius|raid|rf-domain-manager|router|rsa-key| sensor-server|slot|spanning-tree|timezone|traffic-class-mapping|traffic-shape| trustpoint|tunnel-controller|use|vrrp|vrrp-state-check|wep-shared-key-auth| service]

Parameters

no <PARAMETERS>
no <PARAMETERS> Removes or resets the logged device‘s settings based on the parameters passed

Usage Guidelines

The no command negates any command associated with it. Wherever required, use the same parameters associated with the command getting negated

Example

ap505-13403B(config-device-94-9B-2C-13-40-38)#no area

ap505-13403B(config-device-94-9B-2C-13-40-38)#no contact