The switch will create an RMON log entry and the rogue MAC will be ignored when the limit is reached.
NOTE: If the max-vlans value is changed to a different value, the scale of rogue MACs
supported will not change until the next reboot.
Troubleshooting
Switch does not detect the rogue AP TLVs
Symptom
The switch does not detect the rogue AP TLVs that could be sent from the neighboring device.
Cause
The LLDP administrator status of a port is moved from txOnly to tx_rx or rx_only within 120 seconds of the
previous state change to txOnly.
Action
1. Wait for 120 seconds before moving from the state txOnly to the state tx_rx or rx_only.
2. Move the administrator status to disable and then back to tx_rx or rx_only.
Show commands
Use the following show commands to view the various configurations and status.
Command Description
show rogue-ap-isolation
Shows the following information:
• The status of the feature: enabled or disabled.
• The current action type for the rogue MACs detected.
• The list of MAC addresses detected as rogue and the MAC address
of the AP that reported them.
show rogue-ap-isolation
whitelist
Shows the rogue AP whitelist configuration.
Requirements
Only APs directly connected to the switch will be detected.
Limitations
• Only one device type is supported, aruba-ap, and it is used to identify all the Aruba APs.
• You can modify the configuration parameters of the default profile, default-ap-profile, but you cannot
delete it or change its name.
728 Aruba 2930F / 2930M Management and Configuration Guide
for ArubaOS-Switch 16.08
To Next Page
Loading...
Need help?
General