Brocade Network Advisor SAN + IP User Manual v12.1.0 - Manual (Page 813)

Brocade Network Advisor SAN + IP User Manual 757
53-1002949-01
Layer 2 access control list management
22
8. Click OK on the Device_Name - Layer 2 ACL Configuration dialog box.
The Deploy to Products - Layer 2 ACL dialog box displays. To save the configuration, refer to
“Saving a security configuration deployment” on page 821.
Copying a Layer 2 ACL configuration (IronWare)
To copy a Layer 2 ACL configuration, complete the following steps.
1. Select a device and select Configure > Security > Layer 2 ACL > Product.
The Device_Name - Layer 2 ACL Configuration dialog box displays.
2. Select the ACL configuration you want to copy and click Duplicate.
The Duplicate - Layer 2 ACL Configuration dialog box displays.
3. Enter a number for the ACL in the Number field.
For IronWare 5.4 and later, ACL numbers range from 400 through 1399.
For IronWare 5.3, ACL numbers range from 400 through 599.
For IronWare less than 5.3, ACL numbers range from 400 through 499.
4. Enter a description of the ACL in the Description field.
5. To edit an existing ACL rule, complete the following steps.
a. Select the ACL rule you want to edit in the ACL Entries list and click the left arrow button.
b. Complete step 4 through step 10 in “Creating a Layer 2 ACL configuration (IronWare)” on
page 754.
The updated ACL rule displays in the ACL Entries list. To update additional rules for the
same ACL, repeat
step 5 .
6. To add a new ACL rule, complete step 4 through step 10 in “Creating a Layer 2 ACL
configuration (IronWare)” on page 754.
The new ACL rule displays in the ACL Entries list. To create additional ACL rules, repeat step 4
through step 10 .
7. To delete an ACL rule, select the rule in the ACL Entries list and click the left arrow button.
8. Click OK on the Duplicate - Layer 2 ACL Configuration dialog box.
9. Click OK on the Device_Name - Layer 2 ACL Configuration dialog box.
The Deploy to Products - Layer 2 ACL dialog box displays. To save the configuration, refer to
“Saving a security configuration deployment” on page 821.