Associates existing policies with this profile. This command is also applicable to the device configuration mode.
Note
The following tables contain the ‘use‘ command parameters for the Profile and Device configuration modes.use [auto-provisioning-policy|bonjour-gw-forwarding-policy| bonjour-gw-query-forwarding-policy|captive-portal|client-identity-group|crypto-cmp-policy| database-client-policy|dhcp-server-policy|dhcpv6-server-policy|event-system-policy| firewall-policy|global-association-list|guest-management|iot-device-type-imagotag-policy| ip-access-list|ipv6-access-list|management-policy|radius-server-policy|role-policy| routing-policy|web-filter-policy] <POLICY-NAME>
use | Associates the specified policies with this profile The specified policies should be existing and configured. |
auto-provisioning-policy <POLICY-NAME> | Associates an auto provisioning policy
|
bonjour-gw-forwarding-policy <POLICY-NAME> | Uses an existing Bonjour GW Forwarding policy with a
profile or device
For more information on Bonjour GW Forwarding policy, see bonjour-gw-forwarding-policy. |
bonjour-gw-query-forwarding-policy <POLICY-NAME> | Uses an existing Bonjour GW Query Forwarding policy with a profile or device
|
captive-portal server <CAPTIVE-PORTAL> | Configures access to a specified captive portal with this profile
|
client-identity-identity-group <CLIENT-IDENTITY-GROUP-NAME> | Associates an existing client identity group with
this profile
For more information on the ‘client-identity‘ and ‘client-identity-group‘ commands, see client-identity and client-identity-group. |
crypto-cmp-policy <POLICY-NAME> | Associates an existing crypto certificate management
protocol (CMP) policy with this profile
For more information on configuring a crypto CMP policy, see CRYPTO-CMP-POLICY. |
database-client-policy <POLICY-NAME> | Associates an
existing database client policy with a profile
For more information on database client policy, see database-client-policy global-config. Applicable only to the NX 95XX, NX 96XX, and VX 9000 model service platforms. |
dhcp-server-policy <DHCP-POLICY> | Associates a DHCP server policy
|
dhcpv6-server-policy <DHCPv6-POLICY> | Associates a DHCPv6 server policy
|
event-system-policy <EVENT-SYSTEM-POLICY> | Associates an event system policy
|
firewall-policy <FW-POLICY> | Associates a firewall policy
|
global-association-list server <GLOBAL-ASSOC-LIST-NAME> | Associates the specified global association list with
the controller profile
Once associated, the controller, using this profile, applies this association list to requests received from all adopted APs. For more information on global association list, see global-association-list. |
guest-management <GUEST-MANAGEMENT-POLICY-NAME> | Associates the specified guest management policy with the controller profile
|
iot-device-type-imagotag-policy <POLICY-NAME> | Associates an IoT Imago Tag policy to an AP‘s profile or device
context.
|
ip/ipv6-access-list <IP/IPv6-ACL-NAME> traffic-shape class <1-4> | Associates an IP and/or IPv6 ACL with this profile and applies it as a firewall for the selected traffic-shape class
|
location-policy <POLICY-NAME> | Associates a location policy to the device profile. The Location policy is
a means to upload site hierarchy to the ExtremeLocation server through the
WiNG controller (NOC,
standalone APs, virtual controllers). The location policy points to the
ExtremeLocation server and provides the Tenant authentication key needed to
authenticate with the server. It is applicable to the following platform profiles: AP-7522, AP 7532, AP 7562, AP 7602, AP-7612, AP 7622, AP7632, AP7662, AP-8432, AP-8533, RFS 4000, NX 5500, NX 7510, NX 95XX, NX 96XX, and VX 9000 .
|
management-policy <MNGT-POLICY> | Associates a management policy
|
radius-server-policy <RADIUS-POLICY> | Associates a device onboard RADIUS policy
|
role-policy <ROLE-POLICY> | Associates a role policy
|
routing-policy <ROUTING-POLICY> | Associates a routing policy
|
web-filter-policy <POLICY-NAME> | Associates an existing Web Filter policy with a profile or device
|
use [auto-provisioning-policy|bonjour-gw-forwarding-policy| bonjour-gw-query-forwarding-policy|captive-portal|client-identity-group|crypto-cmp-policy| database-client-policy|database-policy|dhcp-server-policy|dhcpv6-server-policy| enterprise-ui|event-system-policy|firewall-policy|global-association-list|guest-management| iot-device-type-imagotag-policy|ip-access-list|ipv6-access-list|license|location-policy| management-policy|nsight-policy|profile|radius-server-policy|rf-domain|role-policy| routing-policy|rtl-server-policy|sensor-policy|wips-policy|smart-rf-policy|web-filter-policy] <POLICY-NAME>
use | Associates the following policies with this device: |
auto-provisioning-policy <POLICY-NAME> | Associates an auto provisioning policy
|
bonjour-gw-forwarding-policy <POLICY-NAME> | Uses an existing Bonjour GW Forwarding policy with a
profile or device
For more information on Bonjour GW Forwarding policy, see bonjour-gw-forwarding-policy. |
bonjour-gw-query-forwarding-policy <POLICY-NAME> | Uses an existing Bonjour GW Query Forwarding policy with a profile or device
|
captive-portal server <CAPTIVE-PORTAL> | Configures access to a specified captive portal
|
client-identity-identity-group <CLIENT-IDENTITY-GROUP-NAME> | Associates an existing client identity group with
this device
For more information on the ‘client-identity‘ and ‘client-identity-group‘ commands, see client-identity and client-identity-group. |
crypto-cmp-policy <POLICY-NAME> | Associates an existing crypto certificate management
protocol (CMP) policy
For more information on configuring a crypto CMP policy, see CRYPTO-CMP-POLICY. |
database-client-policy <POLICY-NAME> | Associates an
existing database client policy with a device
For more information on database client policy, see database-client-policy global-config. Applicable only to the NX 95XX, NX 96XX, and VX 9000 model service platforms. |
database-policy <DATABASE-POLICY-NAME> | Associates an existing database policy with this device
|
dhcp-server-policy <DHCP-POLICY> | Associates a DHCP server policy
|
dhcpv6-server-policy <DHCPv6-POLICY> | Associates a DHCPv6 server policy
|
enterprise-ui | Enables
application of the site controller‘s Enterprise user interface (UI) on all
management points (controllers and access points) For example, the site controller is NX 5500 and an AP 7562 is adopted to it. To enable the access point to also use the Enterprise UI: On the AP 7562‘s profile configuration mode execute: use > enterprise-ui On adoption and application of this profile, the AP 7562 access point resets and reboots using the Enterprise UI. Once using the Enterprise UI, on all subsequent adoptions, the AP does not get reset. |
event-system-policy <EVENT-SYSTEM-POLICY> | Associates an event system policy
|
firewall-policy <FW-POLICY> | Associates a firewall policy
|
global-association-list server <GLOBAL-ASSOC-LIST-NAME> | Associates the specified global association list with
the device (controller)
Once associated, the controller applies this association list to requests received from all adopted APs. For more information on global association list, see global-association-list. |
guest-management <GUEST-MANAGEMENT-POLICY-NAME> | Associates the specified guest management policy with this device
|
ip/ipv6-access-list <IP/IPv6-ACL-NAME> traffic-shape class <1-4> | Associates an IP and/or IPv6 ACL with this device and applies it as a firewall for a selected traffic-shape class
|
license <WORD> | Associates a Web filtering license with this device
|
location-policy <POLICY-NAME> | Associates a location
policy to the device self.The Location policy is a means to upload site
hierarchy to the ExtremeLocation server through the WiNG controller (NOC, standalone
APs, virtual controllers). The location policy points to the ExtremeLocation
server and provides the Tenant authentication key needed to authenticate
with the server. It is applicable to the following platform profiles: AP-7522, AP 7532, AP 7562, AP 7602, AP-7612, AP 7622, AP7632, AP7662, AP-8432, AP-8533, RFS 4000, NX 5500, NX 7510, NX 95XX, NX 96XX, and VX 9000 .
|
management-policy <MNGT-POLICY> | Associates a management policy
|
nsight-policy <NSIGHT-POLICY-NAME> | Associates a specified NSight policy with this device
|
profile <PROFILE-NAME> | Associates a profile with this device
|
radius-server-policy <RADIUS-POLICY> | Associates a device onboard RADIUS policy
|
rf-domain <RF-DOMAIN-NAME> | Associates an RF Domain
|
role-policy <ROLE-POLICY> | Associates a role policy
|
routing-policy <ROUTING-POLICY> | Associates a routing policy
|
rtl-server-policy <POLICY-NAME> | Associates a RTL
(Real TIme Locationing) server policy with an access point.
When associated, enables the access point to directly send RSSI feeds to the
third-party Euclid RTL server.
|
sensor-policy <POLICY-NAME> | Associates a sensor policy with an access point or controller. When associated, WiNG controllers and access points function as sensors.
|
wips-policy <WIPS-POLICY> | Associates a WIPS policy
|
web-filter-policy <POLICY-NAME> | Associates an existing Web Filter policy with a profile or device
|
nx9500-6C8809(config-profile-default-rfs4000)#use event-system-policy TestEventSysPolicy nx9500-6C8809(config-profile-default-rfs4000)#show context profile rfs4000 default-rfs4000 mint link ip 1.2.3.4 mint level 1 area-id 88 ..................................................... interface ge3 ip dhcp trust qos trust dscp qos trust 802.1p interface ge4 ip dhcp trust qos trust dscp qos trust 802.1p interface pppoe1 use event-system-policy TestEventSysPolicy use firewall-policy default ntp server 172.16.10.10 prefer version 1 --More-- nx9500-6C8809(config-profile-default-rfs4000)#
no | Disassociates a specified policy from this profile/device |