blocked by rogue-ap-isolation.
Similarly, any MAC that was added with the
lockout-mac
or
static-mac
command and that is being detected
as rogue will be logged, but not blocked in hardware as it already is set to block. If the MAC is removed from
lockout-mac
or
static-mac
but is still in the rogue device list, it will be blocked back in hardware if the action
type is
block
.
LMA/WMA/802.1X/Port-Security
Any configuration using LMA, WMA, 802.1X, or Port-Security will not be blocked if the Rogue AP isolation feature
is enabled. All these features act only when a packet with the said MAC is received on a port.
If
rogue-ap-isolation
blocks a MAC before it is configured to be authorized, packets from such MACs will be
dropped until one of the following happens:
• Rogue action is changed to LOG.
• Rogue-AP isolation feature is disabled.
• The MAC is not detected as rogue anymore.
• LLDP is disabled on the port (or globally).
Once a MAC has been authorized by one of these features, it will not be blocked by Rogue AP isolation. A RMON
will be logged to indicate the failure to block.
The Rogue AP module will retry to block any such MACs periodically. In the event of the MAC no longer being
authorized, Rogue AP isolation will block the MAC again. No RMON is logged to indicate this event.
Troubleshooting
Dynamic configuration not displayed when using “show running-config”
Symptom
The
show running-config
command does not display the dynamic configuration applied through the device
profile.
Cause
The
show running-config
command shows only the permanent user configuration and parameters
configured through device profile.
Action
Use the specific
show device-profile
command to display the parameters dynamically configured through
the device profile.
The
show run
command displays non-numerical value for untagged-vlan
Symptom
The
show run
command displays one of the following values for
untagged-vlan
:
•
no untagged-vlan
•
untagged-vlan : None
730
Aruba 2930F / 2930M Management and Configuration Guide
for ArubaOS-Switch 16.08
