Enabling Network Management Features - Avaya 8600 Technical Configuration Manual

Site1:5(config)# filter acl ace action 4000 13 permit police 13
Site1:5(config)# filter acl ace 4000 13 enable

For simplicity, the QOS Policy-id was chosen to match the relevant L2 VLAN-id
 In this TCG an 8648GTR(S) would have been used in slot 4. This R(S)-module has 2 10Gig
Lanes with Lane 1 spanning ports 4/1-4/24 and Lane 2 spanning ports 4/25-4/48. The policer is
thus enabled across both Lanes for slot 4 (Lanes 4/1-4/2)

The ACL ACEs had already been created in section 2.2.10.2. To apply a policer to a existing
ACE we need to first disable the ACE and then re-enable it after applying the policer
To verify operation of the L2-VLAN policers refer to section 3.19.

2.2.11 Enabling Network Management features

2.2.11.1 Configuring ACLs to provide per-L2-VLAN statistics
We simply enable count statistics on the same ACL ACE defined in 2.2.10.2.
This will provide inOctets and inPackets for each of the L2-VLANs. These statistics will only include traffic
arriving on the edge L2-VLAN ports and will not include traffic arriving from the Core over the L2-VLANs.
To monitor traffic in the reverse direction, simply create an equivalent ACL of type outPort.
All Sites (only Site1 shown) : L2-VLAN 10 Stats
CLI
Site1:5# config filter acl 4000 ace 10 debug count enable
ACLI
Site1:5(config)# filter acl ace debug 4000 10 count enable
All of Sites 1, 2, 4 and 5 (only Site1 shown) : L2-VLAN 11 Stats
CLI
Site1:5# config filter acl 4000 ace 11 debug count enable
ACLI
Site1:5(config)# filter acl ace debug 4000 11 count enable
All of Sites 2, 3 and 5 (only Site2 shown) : L2-VLAN 12 Stats
CLI
Site2:5# config filter acl 4000 ace 12 debug count enable
ACLI
Site2:5(config)# filter acl ace debug 4000 12 count enable
Network Design Implementation to Provide L2 & L3 VPN Connectivity
November 2010
between Sites using SMLT and IPVPN-Lite for ERS 8600
Technical Configuration Guide
avaya.com
91