Table of Contents
Advertisement
Overview
To simplify the deployment of mobility and IoT devices, Aruba switches have a mechanism to automatically detect
devices based on their LLDP signatures and apply configuration to the port to which they are connected. This
reduces the time needed to add, move, or change devices on the network and also eliminates potential
misconfigurations on the port.
Device Profiles allow an administrator to create configuration containers for different classes of devices and
associate them with certain device types. The configuration containers are stored as part of the config, but do not
come into effect until a device with the right LLDP signature is connected to a port on that switch. Device profiles
allow network administrators to apply port settings automatically, eliminating configuration mistakes as well as
reducing the time taken to connect wired devices.
Organization-specific TLVs and subtypes that come as part of LLDP messages are used to detect and apply
profiles to devices. A maximum of 16 devices can be detected and defined using Device Profiles. The following
sections talk about the operational steps that need to be followed to add Mobility and IoT devices as well as
features such as Rogue AP detection that can be used for mobile-first deployments with Aruba APs.
Auto configuring Aruba APs
The auto device detection and configuration detects a directly connected Aruba AP dynamically and applies
predefined configurations to ports on which the Aruba AP is detected.
You can create port configuration profiles, associate them to a device type, and enable or disable a device type.
One of the device types supported is aruba-ap and it is used to identify all the Aruba APs.
When a configured device type is connected on a port, the system automatically applies the corresponding port
profile. Connected devices are identified using LLDP. When the LLDP information on the port ages out, the device
profile is removed.
By default, the device profile feature is disabled. When you enable the device profile support for a device type, if
no other device profile is mapped to the device type, the default device profile default-ap-profile is
associated with the device type. You can modify the AP default device profile configuration but you cannot delete
it. The default-ap-profile command supports only the AP device type.
NOTE: Only APs which are connected directly will be detected.
Associating a device with a profile
To associate an Aruba access point (AP) device-type to a user-defined profile, use the context Switch(device-
aruba-ap)#. All Aruba access points use the identifier aruba-ap.
The [no] form of the command removes the device type association and disables the feature for the device type.
The feature is disabled by default.
device-profile name
Syntax
[no] device-profile name <PROFILE-NAME> [untagged-vlan <VLAN-ID> |
Chapter 21 Simplifying Wireless and IoT Deployments
Simplifying Wireless and IoT Deployments
tagged-vlan <VLAN-LIST> | cos <COS-VALUE> |
ingress-bandwidth <Percentage> |
egress-bandwidth <Percentage> |
Chapter 21
713
Advertisement
Table of Contents
Troubleshooting
