Overview

About Advanced Wireless Intrusion Prevention System Short Desc With each subsequent arrival of a packet from the same flow, the cache entry is updated. Flow records persist within the line card's cache until they age out due to timer expiration.

About aWIPS profiles

If the rogue AP is attached to non-ACCESS mode interfaces, the network admin must contain the interface either manually or through a CLI command.

Create an aWIPS profile configuration workflow

Ensure that you have write permission from the provision API, scheduler API, and rogue side to perform this procedure.

View an aWIPS profile

test

Assign an aWIPS profile to the network device

Containment is illegal in some countries because it disrupts the communication between the clients attached to a rogue AP. Catalyst Center warns you about the legal consequences while initiating Wireless Rogue AP Containment.

Edit an aWIPS profile

This procedure describes how to start and stop Wireless Rogue AP Containment on wireless clients connected to a rogue AP.

Delete an aWIPS profile

Banner with a green check mark indicates that the Wireless Rogue AP Containment request is submitted successfully to the strongest detecting AP. A red vertical line appears next to the strongest detecting AP based on the RSSI value.

Enable or disable aWIPS or aWIPS forensic capture

After containment is initiated, it takes some time for the Containment Status column to get an update with another wireless containment status.