Please enable JavaScript.
Coggle requires JavaScript to display documents.
Project 2816: Intent Based ACLs Phase2 - Coggle Diagram
Project 2816: Intent Based ACLs Phase2
VLANS
Create multiple VLANS with same ID and IP Address
Create multiple VLANS with same ID different subnets
Create lot of VLANS on one AW+ device and check how long it takes to import all of the subnets in RADIUS groups
RADIUS Users
Create multiple users and assign imported groups
Create users and assign different groups
Check which IP address users get corresponds to groups/VLANID
Add dynamic VLAN assignment to specific port
When users are moved from another group try to authenticate them
Create users in Vista Manager
Create users in CLI
Import users and assign groups on the same time
Import 5k RADIUS users assign them to two different groups
RADIUS Groups
Import groups in Vista Manager
Check VLANID of imported groups if they are End to End
Delete groups that has users
Assign imported groups to users created by Vista Manager
Assign groups to users created by Vista Manager
Assign groups to users created by CLI
Assign groups to imported users
Import groups and assign users by Vista Manager
Assign more than 3k users to one group
One group that has 3k users try to authenticate 10 random users in it
Change VLANID of imported groups?
Change VLANID to VLAN_Name of imported groups?
Vista Manager should show waring message if user want to change the VLANID of imported group
Imported groups will have specific RADIUS_Group name admin can easily distinguish between them
Imported groups will be e2e only?
Import groups will import only VLANS with associated IP Address only (L2 VLANS would not work)
User cannot change VLAN ID of specific group (1-4096) if user exceed the limit waring message will be displayed
Browsers
MS Edge
Safari for iPad
Chrome
FireFox
Raspberry Pi
Attach Raspberry Pi to AW+ device
Enable Port Auth on specific port
Create different WPA_Supplicant in Pi and authenticate them
End to end networks
Network no long specifies as e2e if same subnets are used with different VLAND ID
Network no long specify as e2e if subnet is using same VLAN ID on different device
If network is previously attached with RADIUS server/batch
Event will be generated indicate that RADIUS group no longer met
Vista manager will still show an association with that network when network is no long qualifies but flagged with a warning
If a e2e network is no longer exists and that is previously associated with RADIUS server/batch event will be generated RADIUS group no longer present
The simplified display name will. no longer be present so vista will display longer name with waring