Hello, friend!
1. When an aggregation group is configured, the ACL delivered has the following differences:
If the system works in active/standby mode, packet filters (the same as other QoS actions) are delivered independently based on ports. The delivered packets take effect on the specified port. Each port in an aggregation group can be delivered independently and takes effect.
When the system works in load balancing mode, ACLs delivered by packet filters (the same as other QoS actions) are delivered to all ports in the aggregation group. For example, if port 0/6/0, 0/6/1, 0/7/0, 0/7/1 is aggregated, port 0/6/0 is the master port. After packet-filter is delivered to port 0/6/0, the OLT splits and delivers the packet-filter to the other three slave ports. The result is that all ports in the LAG deliver the ACL referenced by the packet filter.
In R13 and later versions, this difference is optimized. In load balancing scenarios, ACLs are delivered independently based on ports and take effect only on the port to which the ACLs are delivered, regardless of the LAG.
2. You can run the system ex-mode command to view the working model of the host.
Thanks!